Doc to Blog Drafts
Status: Live.
Your muse
Rebuild ofGenerating technical blogs from your docs with Llama and RAG (opens in a new tab)Clean
Turn my product docs into a technical blog post with a header image. This rebuilds Meta's video "Generating technical blogs from your docs with Llama and RAG" (https://dev.meta.ai/llama/resources/videos/generate-technical-blogs-from-your-docs-with-Llama-and-RAG) on current Muse models. It demonstrates: Drafting blog posts from existing documentation with retrieval. Plan: Upload or paste docs and get a draft post with a header image. Most doc sets fit in Spark 1.3's 1M-token context, so there is no retrieval pipeline to build.
Done.
npm run verifyexits 0.Checks found problems
Final screen shows a full blog draft with title, intro, numbered sections, code blocks and closing.
Checks passed, try 2
The plan: Doc to Blog Drafts
Turn product docs into a technical blog draft with header image.
- Paste docs or upload PDFs and add product name and audience
- Choose length, tone and header image style
- Generate draft post from the docs
- Generate header image from the post topic
See the full plan
Who it's for
Developers and technical writers turning docs into posts.
How it works
- Paste docs or upload PDFs and add product name and audience.
- Choose length, tone and header image style.
- Generate draft post from the docs.
- Generate header image from the post topic.
- Edit text, retry image, then copy or download markdown.
Screens
- Docs Input. Paste or upload docs and set audience, tone, length and image style.
- Draft Editor. Read and edit the generated post with title, sections and code blocks.
- Header and Export. Preview header image options and copy or download the final post.
What goes in
- Text: Paste product docs or notes. Plain text or markdown up to about 200k characters.
- PDF (optional): Optional PDF docs. Up to 5 files under 4.5 MB each. Text is extracted for the draft.
What comes out
- Text: Markdown blog draft with title, intro, sections, code blocks and closing.
- Image: Landscape header image generated for the post. Downloadable JPEG.
Models
Model Used for Why Muse Spark 1.3 Draft technical blog post from docs Reads pasted text and PDFs directly and writes a structured draft with headings and code sections. Muse Image Create blog header image Generates original header art from the post topic and style choice. Limits
- Rebuild fit: clean. Same docs to draft demo as the video but uses Spark 1.3 large context instead of a RAG pipeline and uses the current image model for the header.
- No retrieval pipeline or citations index. Very large doc sets over the context limit are truncated.
- Drafts may invent details. User must check facts and code against source docs.
- No publishing to blogs or social networks. Export is copy or markdown download only.
From your inspo
Rebuild of Meta developer video Generating technical blogs from your docs with Llama and RAG. It keeps the core demo of turning product docs into a draft post with a header image.
Takes
- drafting technical blog posts from existing product docs
- simple flow of docs in and draft post plus header image out
Leaves out
- video footage and script
- Meta and Llama names and logos
- exact look of any real product or site
Cost per run: about $0.05 (est.). About 20k input tokens at $1.25 per M is $0.025. About 2.5k output tokens at $4.25 per M is $0.011. One header image at $0.01. Total about $0.046.
Recorded demo