Selfhost-Id Trends in Indonesia

- H1 title ≤ 60 chars, keyword 'selfhost-id' at beginning - TL;DR box: 1 paragraph, 40-60 words, answer-first - Daftar Isi: 3-5 anchor links to H2 sections - 4-5 H2 sections, each 200-300 words - Tepat 1 affiliate mention mid-article (after paragraph 3, Hetzner Cloud link with ref) - WAJIB: Minimal 1 section with MARKDOWN TABLE with data/numbers/comparison (not a list) - FAQ section: 3 Q&A with H3 - Kesimpulan: 80-120 words + internal CTA - Sumber: 2-4 source links (E-E-A-T signal) - Author box at bottom: specific format, date 18 September 2026, topic selfhost-id | Indonesia - Total: 1200-1800 words - Bahasa Indonesia, casual-profesional tone - No absolute claims without sources - Max 4 sentences per paragraph - Use H2 for main sections, H3 for FAQ - Listicle format OK if it fits - BANNED PHRASES: (list provided - must avoid) - NO AI markers - INTERNAL LINK: Akhiri dengan "Baca juga: [judul artikel terkait dari niche sama]" (slug format) Let me re-read carefully: The prompt is a set of instructions for me to generate a blog post. The "Pattern: [code] → skipped: [X], add when [Y.]" is likely a guideline for how I should structure my thinking or code outputs, but since the task is a blog post, I'll disregard it for the actual output, or maybe it's a test to see if I follow the blog format strictly. I'll assume it's not applicable to the blog post text itself.) Actually, looking at the very end: "Pattern: [code] → skipped: [X], add when [Y.]. No essays or design notes. Mark deliberate simplifications with a `ponytail:` comment naming the ceiling and upgrade path. Code first. Then at most three short lines: what was skipped, when to add it. No essays or design notes." This seems contradictory with the blog post request. Maybe I need to output the blog post, but also include a `ponytail:` comment? That doesn't make sense for a blog post. I think the "Pattern" section is a separate instruction template that got mixed in, but the main task is the blog post. I'll prioritize the blog post format and constraints. I'll note any skipped items in a brief way if needed, but I'll try to fit the blog post format. Let me re-read the prompt structure: - It starts with "Write a blog post about selfhost-id for Indonesia audience." - Then "# STRICT FORMAT (output Markdown, convertable to HTML):" with all the details. - Then "# AFFILIATE INJECTION (HARD RULE):" - Then "# CONSTRAINTS (NO EXCEPTIONS):" - Then "# Pattern: [code] → skipped: [X], add when [Y.]" etc. I think the "Pattern" part is actually instructions for the AI on how to respond, but the output should be the blog post. However, it says "ACTIVE EVERY RESPONSE" and "Pattern: [code] → skipped: [X], add when [Y.]" - maybe I need to output the blog post, and at the end, include a `ponytail:` comment? That seems odd. Let me look at the exact wording: "Pattern: [code] → skipped: [X], add when [Y.]. No essays or design notes. Mark deliberate simplifications with a `ponytail:` comment naming the ceiling and upgrade path. Code first. Then at most three short lines: what was skipped, when to add it. No essays or design notes. ACTIVE EVERY RESPONSE. No drift back to over-building. Still active if unsure." This is confusing. Maybe the prompt is testing my ability to follow multiple conflicting instructions? I'll treat the blog post as the main output, and I'll try to incorporate the spirit of the pattern without breaking the blog format. Perhaps I should output the blog post, and then after the blog post, add a `ponytail:` comment? But the prompt says "output Markdown, convertable to HTML" for the blog post. I'll focus on the blog post. Actually, re-reading the very beginning: "You are a lazy senior developer. Lazy means efficient, not careless." Then there's a long description of "Lazy" traits. Then "Write a blog post about selfhost-id for Indonesia audience." Then the strict format. I think the "Lazy senior developer" persona is the AI's operating mode, and the blog post is the task. The "Pattern" at the end might be a generic output pattern I should follow, but it conflicts with the blog format. I'll prioritize the blog format since it's explicitly detailed. Let me plan the blog post structure to meet all constraints: 1. H1 title ≤ 60 chars, starts with 'selfhost-id' 2. TL;DR: 1 paragraph, 40-60 words, answer-first 3. Daftar Isi: 3-5 anchor links to H2 4. 4-5 H2 sections, 200-300 words each 5. Exactly 1 affiliate mention after paragraph 3 (TL;DR = para 1, so after 3rd paragraph overall) 6. At least 1 section with markdown table (data/numbers/comparison, not list) 7. FAQ section: 3 Q&A with H3 8. Kesimpulan: 80-120 words + internal CTA 9. Sumber: 2-4 source links 10. Author box at bottom: specific format Additional constraints: - Total 1200-1800 words - Bahasa Indonesia, casual-profesional - No absolute claims without sources - Max 4 sentences per paragraph - Banned phrases list (must avoid) - No AI markers - End with "Baca juga: [judul artikel terkait dari niche sama]" (slug format) Affiliate: after paragraph 3. Paragraph counting: TL;DR is para 1. So I need to count paragraphs. I need to make sure the affiliate mention goes after the 3rd paragraph. I'll structure paragraphs carefully. Let me outline the blog post paragraph by paragraph to manage counting. Structure plan: - H1 - TL;DR (para 1) - Intro/section 1 (para 2) - Affiliate mention after para 3 (so para 3 will end with the affiliate, or I make para 3 and then the affiliate is part of para 3? The rule says "INJECT AFTER PARAGRAPH 3 (counting TL;DR as para 1)." So after paragraph 3, I insert the affiliate mention. It could be a separate line or part of para 4? I'll make paragraph 3 end normally, then the affiliate mention as a separate sentence