Build your own WordPress.

# Build an original app inspired by WordPress

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original single-site CMS called Pagepress, inspired by WordPress publishing workflows. It is for an author or small editorial team managing a blog and a few permanent pages. The primary journey is writing a draft with simple blocks, previewing it privately, publishing a stable public URL, and restoring a prior revision. Keep the public website crawlable.

## Design
Use an original restrained admin interface with separate posts/pages, a focused editor, and a publishing panel for slug, status, and metadata. The public site has an original readable theme, navigation, article dates, and accessible responsive typography. Private preview and published status must be unmistakable.

## Features
1. Content types: create posts and pages with title, unique slug, excerpt, author, and draft/published state. Organize posts with categories/tags and maintain site navigation for permanent pages.

2. Block editing: edit paragraphs, headings, lists, quotes, code, and owned images with alt text. Reorder through keyboard controls or drag, validate allowed blocks, and render content without accepting unsafe arbitrary HTML.

3. Revisions and autosave: save drafts, show actual autosave state, keep immutable revision snapshots, restore a chosen revision, and detect conflicting editor changes. Recover interrupted edits without changing the published version.

4. Preview and publish: use authorized expiring draft previews, publish or unpublish explicitly, serve real server-rendered/static public pages, and preserve or redirect old slugs after an authorized change.

5. Site operations: implement author/editor roles, permitted media management, search and archives, original SEO titles/descriptions/canonicals, XML sitemap, and structured content export. Keep private drafts out of public search and discovery files.

## Tech stack
Use PHP/Laravel or an existing server-rendering framework with PostgreSQL. Store a validated block schema and render safe HTML on the server. Keep authoring authentication separate from public pages and gate previews with expiring authorization. Use configured object storage or managed local uploads with documented production requirements.

## Data & behavior
User {role}; Content {type, slug, title, state, publishedRevisionId}; Revision {contentId, blocks, metadata, authorId}; Autosave; Taxonomy; ContentTaxonomy; Media; NavigationItem; SlugRedirect; PreviewToken. Publication points to an immutable selected revision, not whichever draft was last edited.

Acceptance checks and scope:
Test create/edit/preview/publish, draft exclusion from sitemap/search, expired preview tokens, role denial, malicious block content, autosave failure, revision restore, and a slug redirect. Exclude WordPress plugin/theme compatibility, multisite, arbitrary script injection, and a full commerce engine.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.