TechnicalCollectible prompt

Blog admin with drafts, previews and scheduling

Let your team write, preview, schedule and publish posts without touching code.

LovableClaude CodeCursor

Curated by Nvoka

Nvoka wordmark logo
Nvoka wordmark logoTechnical

Blog admin with drafts, previews and scheduling

Add a content editor for blog posts to my {{tech_stack}} site, so people who don't code can publish. The roles involved: {{user_roles}}. Read the existing code first and show me a short plan before changing files. Each post has a title, slug, excerpt, body, cover image with required alt text, author, category, a status of draft, scheduled or published, publish and updated dates, and an optional search title and description. The editor: - An admin area behind sign-in, where writers draft and editors or owners publish, enforced by database access rules - A rich text or Markdown editor, whichever suits the project, with autosave and a word count - Images resized on upload, with alt text required before saving - A private preview link showing the post exactly as it will look - Slugs generated from the title and editable; if a published slug changes, the old URL redirects - Scheduled posts go live on time without anyone pressing publish - Deleting archives a post instead of erasing it The public site: - Only published posts appear, including in the RSS feed and sitemap - Rendered content is sanitized so it can't run scripts Meet WCAG 2.2 AA in the editor too. When you're done, list the files changed, how to create the first editor account, and anything you assumed.
Technicalnvoka.com/library/nvoka-blog-admin-with-drafts-and-schedulingScan to open
Technical

Blog admin with drafts, previews and scheduling

Let your team write, preview, schedule and publish posts without touching code.

Nvoka logo

Curated by Nvoka

LovableClaude CodeCursorCodex
Add to my library

Make it yours

Fill in the blanks and change any word. Only your copy changes, never the card.

Fill in the blanks

0 of 2 filled

Your prompt

Add a content editor for blog posts to my {{tech_stack}} site, so people who don't code can publish. The roles involved: {{user_roles}}. Read the existing code first and show me a short plan before changing files. Each post has a title, slug, excerpt, body, cover image with required alt text, author, category, a status of draft, scheduled or published, publish and updated dates, and an optional search title and description. The editor: - An admin area behind sign-in, where writers draft and editors or owners publish, enforced by database access rules - A rich text or Markdown editor, whichever suits the project, with autosave and a word count - Images resized on upload, with alt text required before saving - A private preview link showing the post exactly as it will look - Slugs generated from the title and editable; if a published slug changes, the old URL redirects - Scheduled posts go live on time without anyone pressing publish - Deleting archives a post instead of erasing it The public site: - Only published posts appear, including in the RSS feed and sitemap - Rendered content is sanitized so it can't run scripts Meet WCAG 2.2 AA in the editor too. When you're done, list the files changed, how to create the first editor account, and anything you assumed.
See all