Skip to app details
Back to app library
APPNEURAL APP FAMILYContent & Files

Books

Write it, publish it, let people read it

Write a book, publish it, and let people read it online: chapters in an editor, covers, editions that never change, and EPUB export.

01 / OVERVIEW

See where it fits in your day.

Books have a title, authors, language, description and a cover, uploaded or made in the brand colours. The manuscript is parts and chapters in the same rich-text editor as Writer, with front and back matter templates, autosave that refuses a stale save, versions per chapter, chapter states (draft, in review, final), comments, word counts that handle Hindi, a word target and find across the book; one person edits a chapter at a time. Import from Markdown, plain text or one Writer document; there is no .docx import. Publishing makes an edition that never changes, enforced by the database; the reader audience is public, anyone with the link, signed-in members or a password, with optional sample chapters, unpublishing and a gate on chapters that are not final; locked chapters carry no text in the page. The reader at /read/<slug> works on phones with contents, next and previous, text size, light, sepia and dark themes and the place remembered on the device; /library lists the domain's published books; both can be switched off. Export as EPUB 3, Markdown and an A5 or 6 x 9 inch print layout, with the PDF coming from the browser's print dialog. Numbers show opens and chapter reads per day and how far readers get, without personal data. Optional Claude features write an outline, improve or proofread a passage, back-cover text and title ideas, in the brand voice, and only suggest. API /api/v1/books and chapters of published editions with an API key or the workspace key, and a change feed; webhooks book.published and edition.published. Not built: selling a book, listing in Ebooks, live co-editing, comments anchored to words. Pictures are stored in the database, up to 600 KB each, and a made SVG cover is ignored by some social crawlers.

A LOOK INSIDEExample layout · sample content
Manuscript
T
ChapterIntroduction
Chapter 1
Chapter 2
02 / CAPABILITIES

Built around the work you do.

What Books does for you.

01

Write

Parts and chapters in a rich-text editor with comments, version history and word counts; Hindi and other Indic scripts included.

02

Publish

Each edition never changes; choose who reads: everyone, anyone with the link, members or a password, with optional sample chapters.

03

Read and export

A reader at /read/<slug> with font size and themes, a library at /library, and export as EPUB, Markdown or a print layout.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Books. What you can do depends on your access in the app.

01

Create

Title, cover and chapters.

02

Publish

Pick the audience and publish an edition.

03

Share

Send the reader link or the EPUB.

YOUR NEXT MOVE

Make Books part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE— items
P2PARTIALLY VERIFIEDPUBLISHED
Overview

Purpose and boundaries

Books have a title, authors, language, description and a cover, uploaded or made in the brand colours. The manuscript is parts and chapters in the same rich-text editor as Writer, with front and back matter templates, autosave that refuses a stale save, versions per chapter, chapter states (draft, in review, final), comments, word counts that handle Hindi, a word target and find across the book; one person edits a chapter at a time. Import from Markdown, plain text or one Writer document; there is no .docx import. Publishing makes an edition that never changes, enforced by the database; the reader audience is public, anyone with the link, signed-in members or a password, with optional sample chapters, unpublishing and a gate on chapters that are not final; locked chapters carry no text in the page. The reader at /read/<slug> works on phones with contents, next and previous, text size, light, sepia and dark themes and the place remembered on the device; /library lists the domain's published books; both can be switched off. Export as EPUB 3, Markdown and an A5 or 6 x 9 inch print layout, with the PDF coming from the browser's print dialog. Numbers show opens and chapter reads per day and how far readers get, without personal data. Optional Claude features write an outline, improve or proofread a passage, back-cover text and title ideas, in the brand voice, and only suggest. API /api/v1/books and chapters of published editions with an API key or the workspace key, and a change feed; webhooks book.published and edition.published. Not built: selling a book, listing in Ebooks, live co-editing, comments anchored to words. Pictures are stored in the database, up to 600 KB each, and a made SVG cover is ignored by some social crawlers.

Books written and published for a connected domain: parts and chapters in a rich-text editor with comments and versions, editions that never change, a public library and reader, access by link, members or password, and EPUB, Markdown and print export.

Selling a book belongs to Payments and Store; short documents belong to Writer; the directory of ebooks is Ebooks.

Priority
P2
Portfolio
Content & Files
Capability
Content & Files
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-16T04:17:52.314Z
Semantic inventory

Every number says what it counts

—Count unavailabletrackedEntityCount · catalog-api:unavailable
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

book schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

books.appneural.com DEPLOYED

books.appneural.com

Worker
book-catalog
Health
HEALTHY
Last deployment
2026-11-15 15:22:08
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

Repository provider is not connected. Existing references remain unverified.

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is partially verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app