RailsPress transfer field guide
RailsPress has two transfer paths: background post archives and synchronous CMS block archives. This public demo keeps the workflows visible without accepting untrusted files.
Public demo policy
Read-only in production
Shared administrator credentials make imports unusually sensitive: post frontmatter may reference remote images, while ZIP files may contain many expanded entries. Production rejects transfer POST requests before request parsing, job enqueueing, network access, or archive extraction.
01
Posts
Exported posts become Markdown files with YAML frontmatter for title, slug, status, publication date, taxonomy, SEO fields, author, and a relative header-image path. RailsPress builds the ZIP in a background job and records progress, successes, and errors.
images/…02
CMS blocks
Content groups, ordered elements, required flags, text, image hints, images, and focal coordinates travel in a ZIP manifest. Re-import matches groups and elements by name, updating or restoring records instead of duplicating them.
content.jsonimages/…Local walkthrough
Sign in and open the stock RailsPress import/export or CMS transfer screen.
Export the seeded baseline and inspect the ZIP manifest and bundled images.
Import that archive again. Names act as stable identities, so CMS records update without duplicates.
Run bin/rails demo:seed to restore the Fieldwork baseline.