Manage content with the CMS and locales

Separate collections from entries

A collection defines a repeatable content structure. It is a good fit for blog posts, documentation, customer stories, and other content that shares the same fields. An entry is one item inside that collection.

For example, a documentation collection might contain summary, body, category, and order fields. Each guide is created as a separate entry using that structure.

Connect the collection to dynamic pages

A list page loads several entries, while a dynamic detail page displays the entry that matches the URL slug. Creating a collection alone does not create a public detail page. The collection must be bound to a page, and the page must compile successfully.

Create content for each locale

NeoPress separates site locales from entry locales. Create a localized entry for each language and connect translations of the same document. Review the title, summary, body, image alt text, and calls to action in every locale.

If one translation is incomplete, keep that entry in draft. Avoid publishing a document that mixes languages and fixing it later.

Follow the publishing order

1. Confirm the collection schema.
2. Create an entry for each locale.
3. Review the entry content.
4. Publish only the entries that are ready.
5. Publish the site as well if page code or the collection schema changed.

Entry publish and site publish are separate operations. A content-only change requires entry publish. A page or schema change also requires site publish.