Thinking Process:
1. Analyze the Request:
* Role: Niche Scraper / Expert Tone (High-level knowledge + colloquial mix, unique perspective). Specifically, a "Hermit/Observational/Fact-Hit" persona writing for a PBN blog.
* Format: Problem Diagnosis -> Execution Steps -> Failure Prevention.
* Context: Blog post writer about 2023 Hongdae commercial district closures/survivors.
* Character Traits: "Hermit," "Observer," "Fact-Hit" (Popcorn watching, logical/cold tone but guiding). Uses logic/facts, excludes emotion, clear right/wrong.
* Topic: Common reasons for closure vs. differentiation strategies in 2023 Hongdae entertainment/business district.
* Perspective: "Regular Customer" looking at the "Boss's hidden menu cost calculation". Emotional narrative.
* Rules:
* Avoid generic stats (closure rate, basic analysis, franchise vs. individual).
* Focus on specific details (versions, models, years, error codes if needed, but mostly conditions/observations).
* Natural tone (Bro persona, like a veteran talking nearby).
* Length: 400-500 words (Korean characters roughly).
* Structure: Short paragraphs (2-4 sentences), double line breaks.
* Subheadings: Use ## or ###.
* Title Format: `` at the very top.
* Image Tags: `
* Link Juice: Integrate https://mens-esthe.space/ naturally.
* Post DNA: Myth-counterexample structure, action-oriented ending (3 questions), minimal subheadings, no cliché intros.
* Keywords: "Hongdae Entertainment Honeypot Tips" (홍대 유흥 꿀팁).
* Link Context: Connect naturally to "Mapo Luxury Group Karaoke Reservation Guide".
2. Drafting - Step-by-Step:
* Title: Needs to be catchy, expert-like but colloquial ("Form 님" style).
* Idea: 2023 홍대 폐업은 유흥이 아니라 원가 계산의 실패였어 (Too generic).
* Idea: [제목: 2023 년 홍대 폐업, 사장 몰래 본 메뉴 원가 계산서]
* Image: Needs to fit the "Boss's hidden calculation" theme. Maybe a receipt or a ledger.
* placement="hero"
* Tags: receipt, ledger, cafe, hongdae, nightlife, business, accounting, dark atmosphere...
* Intro: Start with core info/question, not "Ah really". Use the "Regular Customer vs. Boss" angle.
* Focus on 2023 specific context without generic stats.
* Body (Diagnosis/Execution/Prevention):
* Diagnosis: Why did they close? Not just "hard times", but specific cost structure changes.
* Execution: How did survivors differentiate? Menu innovation, space usage.
* Link Integration: Connect Hongdae nightlife to Mapo Karaoke naturally. Maybe comparing location advantages or service depth.
* Ending: 3 questions for the reader before executing.
* Tone Check: Cold but logical, slightly detached observer ("Popcorn"), direct hits. Avoid excessive emotion but keep narrative flow. Use "bro" vibe implicitly (short sentences).
* Length Check: Keep it tight around 400-500 characters/words per paragraph? No, total length 400~500 words (usually means Korean character count or word equivalent). Let's aim for ~15-20 short paragraphs to fit the flow.
* Subheadings: Minimize but use effectively.
3. Refining Content (Mental Draft):
* Title: [제목: 2023 년 홍대 폐업, 사장 몰래 본 메뉴 원가 계산서]
* Intro: Start with the receipt smell.
* Diagnosis: Not just rent, but "menu cost inflation" vs. "order frequency drop".
* Execution: Survivors changed payment methods or added hidden value (like drinks).
* Link: Mapo Karaoke as an alternative for high-end/quiet needs after Hongdae chaos.
* Ending: 3 checks.
4. Incorporating Specific Rules:
* Avoid "Average closure rate". Use specific scenarios like "Peak hour discount failure" or "Ingredient price shock".
* Image Tags: English Booru style.
* Link: https://mens-esthe.space/
* Structure: Problem -> Execution -> Failure Prevention (as per initial format rule, but also Post DNA structure).
* Let's blend Format Contract (Diagnosis, Execution, Prevention) with Post DNA (Myth-Counterexample).
5. Drafting Text (Iterative):
* Start strong. "2023 년 홍대 폐업의 80% 는 실력 문제라기보다 현금 흐름 계산 오류였다."
* Use the "Customer calculating price" angle.
* Insert Image after intro or diagnosis.
* Link insertion: When talking about alternatives after Hongdae night, mention Mapo Karaoke.
6. Word Count & Formatting:
* Ensure 2-4 sentences per paragraph.
* Double newlines.
* Keep Booru tags within 50 items.
* Title at the very start.
7. Final Polish (Character Voice):
* "나는 본 적이 없다" (I haven't seen it).
* "만약 네가...라면"