Blog
Publish articles from inside the app to public pages with authors and categories.
What it adds
A blog with authored posts, categories, scheduling, and public article and index pages.
What your agent is told to do
5
What your agent is told to do
5-
1
Scope this honestly. The minimum coherent version is a post with a title, body, author, category, publish state, and a public page at a stable URL, plus an index and a feed. Defer multi-language content, per-post custom layouts, and a general page builder rather than half-building them.
-
2
Do not build a new editor. Extend the app's existing Rich Text Editor or Markdown Editor with whatever a post needs, and inherit its autosave, unsaved-change warning, and undo instead of reinventing them.
-
3
Reuse the app's existing Draft and Publish States and Scheduled Publishing rather than adding a second publish workflow for posts. Reuse SEO Setup for titles, descriptions, and social previews.
-
4
Give every post a permanent identifier separate from its slug, and keep old slugs redirecting so a link shared anywhere keeps working after an edit.
-
5
Do not render the full body of every post on the index page. Store or derive an excerpt, and paginate, or the index gets slower with every article published.
Edge cases it handles
8
Edge cases it handles
8- Two posts can generate the same slug, and an editor will change a slug after the post has been shared. Enforce uniqueness, and keep every previous slug redirecting to the current one permanently.
- Unpublishing a post that other sites already link to must not return a bare error page. Decide deliberately between a gone response and a redirect to the index, and say which the app does.
- A post scheduled for nine in the morning must appear at nine in a defined time zone. Store the scheduled moment absolutely, show the author which zone they are scheduling in, and confirm the resulting local date.
- Very long posts blow out the index and the feed. Use excerpts on listings, paginate the index, and cap how much content the feed carries per item.
- Deleting an author or a category that live posts reference must not leave broken public pages. Block the deletion, or require a reassignment, before anything is removed.
- Comments, if enabled, are public user-generated content and need moderation, spam handling, and a way to report abuse before the blog is public.
- Images in posts need alt text and reserved dimensions, so article pages do not reflow as the reader scrolls.
- Embeds from third parties inside a post must degrade to a visible link when the provider is blocked or down, not leave a hole in the article.
Definition of done
9
Definition of done
9- Authors can write, save, schedule, publish, and unpublish a post from inside the app.
- Every post has a public page at a stable URL, and previous slugs redirect to the current one.
- Index and category pages are paginated and render excerpts, not full bodies.
- Scheduled posts appear at the intended local time in the stated time zone.
- Authors and categories referenced by live posts cannot be deleted without reassignment.
- Posts use the app's existing editor, publish states, and SEO fields rather than parallel systems.
- A feed is available and bounded in size per item.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Reading Progress Bar
Reading Progress Bar
A slim bar showing how far through an article the reader has scrolled.
What it does
A thin progress indicator pinned to the top of article pages, tracking scroll through the body text.
How it works
- 1 Measure progress against the article body element only. Take the top and bottom of the prose, not the height of the document.
- 2 Recalculate the body height when the page reflows: late-loading images, expanded sections, embeds, and font swaps all change the total after first paint.
- 3 Reuse the app's existing Progress Indicator System tokens for the bar's colour and height rather than introducing a new accent, and keep it visually distinct from Route Change Progress so the two are not confused.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/reading-progress-bar
Press Kit
Press Kit
Give journalists your logos, colours, screenshots, and boilerplate on one public page.
What it does
A public page of downloadable brand assets, colour values, screenshots, and approved boilerplate copy.
How it works
- 1 Serve every asset through the app's existing file download path so that access, headers, and content types are handled the same way as everywhere else, rather than linking directly at raw storage.
- 2 Store the correct format and media type per asset and derive the filename and extension from the stored record, never from the label an author typed.
- 3 Present each logo variant on the background it is designed for, and reuse the app's theme-aware asset switching so the page shows the right variant in light and dark rather than a washed-out logo on the wrong panel.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/press-kit
FAQ Section
FAQ Section
Add an expandable list of questions and answers to any page, in the order you choose.
What it does
A reorderable set of question and answer pairs rendered as an accessible expand-collapse list on any page.
How it works
- 1 Build it on real disclosure semantics with a button that toggles its own panel, so keyboard and screen reader users get the behaviour for free.
- 2 Give every question a stable anchor derived from its text and keep it after edits, so a support reply can link straight to one answer.
- 3 Allow answers to contain formatted text, lists, and links, and reuse the app's existing content editor and its sanitisation rules rather than accepting raw markup.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/faq-section
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.