We need to produce a JSON object with keys summary, category, article_html. The article must be HTML, with exactly one H1 at start containing primary keyword. Primary keyword likely "best books to read" or "top 10 best books to read in life". Let's use "top 10 best books to read in life" as primary keyword. H1 should contain that. Then H2 for 5-7 main sections. We'll have 7 H2 sections: "1. Classic Literature", "2. Modern Fiction", "3. Self-Help & Personal Growth", "4. Biography & Memoir", "5. Science & Innovation", "6. Philosophy & Thought", "7. Poetry & Short Stories". Each H2 corresponds to a category. Under each H2, we can have H3 subsections if needed: maybe list of specific books with brief description. Each section should have 2-3 p tags, each 100-150 words. Each p 100-150 words. Need to ensure word count >1500. 7 sections * 3 p tags * 125 words avg = 2625 words. That's fine. We must include UL/OL lists (5-10 items). Each list could be the top 10 books within that category? But that would exceed 10 total books overall. But requirement: top 10 best books overall. So maybe we should have a list of 10 books in one section, but each book description as a paragraph. But we also need 5-10 items list in some section. Use list under "Top 10 Books" section. But we also need 5-10 items list somewhere else. Could be a list of key takeaways or tips. Let's plan: H1: "Top 10 Best Books to Read in Life" Then H2: "Top 10 Books: The Ultimate List" Under that, we have H3 for each book? That would be many H3. But we can include each book as a paragraph, perhaps with UL list of 10 items: each item with book title and a short description. But requirement: 2-3 p tags per section. So the section must have 2-3 p tags. We can use one p tag for introduction to the list, then one p tag for the list itself (but list is not a p). But we can still satisfy with 2 p tags: first intro, second after list summarizing. That meets 2-3 p tags requirement. We'll create UL with 10 items. Each item inside

includes the title bolded and a short description. That's okay. Then we might have other sections with 5-7 H2. Each section will have 2-3 p tags. Each p 100-150 words. We'll incorporate book recommendations within those p tags. We must ensure 1500 words total. Let's approximate: 7 sections * 3 p tags * 120 words = 2520 words. Good. Also need to end with 3-5 FAQ questions as H3. So after the last H2 section, we add H3s for FAQs. Make sure no markdown, only plain JSON. article_html must be a string containing HTML. Must escape quotes? Since JSON string uses double quotes, we need to escape internal double quotes. But easier to use single quotes in HTML? HTML doesn't care about quotes. We'll use double quotes for attributes, but we need to escape them in JSON? In JSON, double quotes inside a string must be escaped with backslash. So we need to escape every double quote within the article_html string. That is tedious. Alternatively, we can use single quotes for attributes like , but still JSON string uses double quotes for outer string. Single quotes inside are fine. Use single quotes to avoid escapes. However, HTML attributes usually use double quotes but can use single quotes. We'll use single quotes. We also need to ensure the JSON string is valid. All apostrophes inside string are fine. But we must escape backslashes, newlines? We can keep line breaks inside string but JSON may require them to be escaped as \n? Actually JSON string can have literal newlines? They must be escaped. So better to use \n for line breaks. But we may just put the entire HTML in a single line, no line breaks, to avoid escape issues. But readability is not important. We can produce one long line string with no line breaks. That may be easier. But we need to ensure we don't accidentally include unescaped double quotes, but we will use single quotes in attributes. Also no double quotes inside at all. Avoid double quotes in text. But we might need to use double quotes for the JSON key names and string delimiter. So all double quotes inside the article_html string must be escaped. We'll use single quotes for attributes and text, and avoid double quotes. Also in the article text, we might use contractions like "it's" which includes apostrophe. That's fine. We need to include specific book recommendations, authors, key takeaways. We'll mention authors. We need to include 5-10 items lists. We'll include a UL with 10 items in the top 10 list section. Also maybe a UL in a section. Word counts: we need to ensure each

100-150 words. We'll write paragraphs with roughly 120 words each. Let's approximate 120 words each. 3 paragraphs per section -> 360 words per section. 7 sections -> 2520 words. Good. But we also have the Top 10 list section with 2

tags: intro and recap. That's 2 paragraphs. They need 100-150 words each. So we need 240 words. That plus 2520 words = 2760 words. Good. But 10 items list inside UL. That is not counted as paragraph. Fine. Now, we need to embed tags for key terms. We'll use for "best books", "self-help", etc. Also need to end with H3 FAQs: 3-5 questions. We'll include 4 H3 questions. Let's craft the article. We should ensure we don't use double quotes anywhere. We'll use single quotes for attributes. For example: link. For

, etc. Good. Now produce final JSON: keys: summary (150-160 chars). We'll craft a short meta description: "Discover the top 10 best books to read in life, from classics to modern fictions and self‑help gems. Dive into author insights, key takeaways, and actionable reading tips." Count characters: Let's count quickly: "Discover the top 10 best books to read in life, from classics to modern fictions and self‑help gems. Dive into author insights, key takeaways, and actionable reading tips." That's about 158 characters. Good. Category: "howto". Now article_html string: We need to escape double quotes? Since we are using only single quotes inside, there are no double quotes inside. But we might need to escape backslashes? Not needed. We'll produce a normal string. Just ensure no double quotes inside. Let's double-check: Use tags, no double quotes