We need to produce JSON with keys summary, category, article_html. The article must have H1 primary keyword: "best books to read after breakup" or similar. H2 for 5-7 main sections. Each section has 2-3 paragraphs of 100-150 words each. That's a lot of content. Minimum 1500 words. We'll need to produce sufficient text. Must be in HTML format. No markdown. No code fences. The JSON must be valid. Must end with FAQ H3 sections. We need to output only JSON. No extra text. Must be valid JSON: keys with strings. The article_html string will contain HTML with all tags. Must include H1, H2, H3, P tags, UL, OL, STRONG. Need to count words roughly. 1500 words is a lot. Each paragraph 100-150 words, 2-3 per section. 5-7 sections. So 5 sections * 2 paragraphs *100 words = 1000 words. Need 1500 words. Let's use 6 sections, 3 paragraphs each: 6*3*120=2160 words. That will exceed 1500. That's okay. Must ensure each paragraph 100-150. We'll produce about 120 words each. 18 paragraphs. 18*120=2160 words. Good. Also need to include specific book recommendations, authors, key takeaways. Provide lists with 5-10 items. Use UL/OL. Use STRONG for key terms. Also need FAQs at end as H3. Ensure no markdown. Use valid JSON. Must escape quotes inside JSON string. Use \n maybe but not required. We'll produce JSON string with proper escaping for quotes and newlines. But easier to produce pretty JSON with newlines. But within JSON string, newline characters may be represented as \n or actual newline? JSON allows literal newlines? No, JSON strings cannot contain literal newlines; must be escaped. So best to use \n or actual line breaks? According to JSON spec, strings cannot contain unescaped control characters. So we need to escape newlines as \n. So article_html should be a string with \n and escaped quotes. But we can use single quotes inside HTML? In HTML we use double quotes for attributes. So we need to escape them with \". So the JSON string will contain double quotes and backslashes. We need to produce a valid JSON with keys: summary, category, article_html. Let's craft article. We'll create H1: "Best Books to Read After a Breakup". Then H2 sections: 1. Healing Through Narrative 2. Rebuilding Self-Identity 3. Learning from Romantic Mistakes 4. Finding Hope and Growth 5. Practical Guides for Moving Forward 6. Spiritual and Mindfulness Resources Each H2 will have 3 paragraphs. Each paragraph 100-150 words. We'll include lists of book recommendations in each section maybe. Need to use UL or OL with 5-10 items. We'll include book titles. We also need to include STRONG for key terms. We will need to count words roughly. Let's draft paragraphs roughly. Paragraph 1 of section 1: about narrative healing. 120 words. Paragraph 2: more about narrative healing, mention books. Paragraph 3: summarizing. We can approximate. We need to ensure each paragraph has 2-3 sentences? Wait requirement: P tags: 2-3 per section, 100-150 words each. So each paragraph 100-150 words, so 2-3 paragraphs per section. Each paragraph 100-150 words. So 2-3 paragraphs per section. We choose 3 paragraphs per section to hit word count. So each section has 3 paragraphs. Thus 6 sections * 3 paragraphs = 18 paragraphs. Word count: 18 * 120 = 2160 words, good. Let's craft each paragraph carefully. Also include lists of books maybe after paragraphs or within. We can include UL after paragraph 2 with book list. We also need to include key takeaways. We can use strong tags. Eg Key takeaway:. Let's craft. We also need to end with 3-5 FAQ questions as H3. Each FAQ maybe one paragraph answer. But article specification: End with 3-5 FAQ questions as H3. So after sections we have H3 tags with FAQs. Each FAQ heading H3 and then maybe a paragraph answer. But spec: End with 3-5 FAQ questions as H3. It didn't say to include answer. But typical FAQ includes question and answer. But to be safe, we can include question as H3 and paragraph answer. But we need to ensure not to break structure. We'll have after section 6, H3 FAQs. Now produce article_html string with proper escaping. We need to escape double quotes in attributes. Eg but we don't need images. So article_html string will contain many double quotes. We need to escape them as \". Also newlines as \n. We'll produce a single line string? It's easier to produce multi-line string but must escape newlines. Let's produce with \n for readability. We'll produce e.g.: "

Best Books to Read After a Breakup

\n

Healing Through Narrative

\n

Paragraph content...

\n..." Make sure no unescaped double quotes. Also we must escape backslashes themselves? In JSON string, backslash is escape char. So we have to write \\ to produce a single backslash in string? But we don't need backslashes. Only double quotes. So we need to escape them: \". So each double quote inside string must be escaped. That includes attribute quotes in HTML (e.g., class="..."). So we need to write class=\"...\" etc. Thus produce article_html accordingly. Let's draft paragraphs. Paragraph content: we need 100-150 words. We'll approximate. Paragraph 1 of section 1: "When a breakup feels like a storm, the first step toward calm is to let the story unfold. Writing down the emotions, the memories, and the raw feelings creates a safe space where the heart can breathe. By treating the breakup as a narrative rather than a verdict, readers can reframe the experience, turning pain into a chapter that can be closed with intention. This process not only eases the emotional load but also sets the foundation for self‑reflection and growth. It invites the reader to become the protagonist of their own recovery journey." Count words? Let's count quickly: When(1) a2 breakup3 feels4 like5 a6 storm,7 the8 first9 step10 toward11 calm12 is13 to14 let15 the16 story17 unfold.18 Writing19 down20 the21 emotions,22 the23 memories,24 and25 the26 raw27 feelings28 creates29 a30 safe31 space32 where33 the34 heart35 can36 breathe.37 By38 treating39 the40 breakup41 as42 a43 narrative44 rather45 than46 a47 verdict,48 readers49 can50 reframe51 the52 experience,53 turning54 pain55 into56 a57 chapter58 that59 can60 be