Contentrain Bridge: export WordPress content to JSON, Markdown and GitHub—for free
by•
We’ve released Contentrain Bridge on WordPress.org.
Choose your WordPress content, review its models, then download a ZIP or send the files to a new branch in your own GitHub repository.
Both options are free. No Contentrain account required.
I’m a co-founder of Contentrain. One part we’d especially like feedback on is the coverage report: it shows what was exported, what was left out, and why.
Bridge exports content files; rebuilding the website is a separate step.
If you were using this for a client project, what would you need to see in that report before trusting the export?
15 views
Replies
Co-founder here, so I’m biased, but I want to answer Sercan’s question with the client-project lens, because that’s where I hear it most.
Before an agency trusts an export, the coverage report should answer three things in one glance:
Counts that match WordPress: posts, pages, media and custom types, side by side with what wp-admin shows.
What was skipped and why, in plain words: “shortcode from plugin X”, “form”, “page-builder widget”, not just a list of IDs.
What breaks if I ignore it: which skipped items are cosmetic and which hold real content.
If those three are clear, you can hand the report to a client and say “this is everything you own, in your GitHub.”
And for anyone who wants the full site rebuilt afterwards, not just the content files, that’s what Contentrain Migrate does: content, URLs (with 301s) and SEO carry over exactly, and the design is modernised on a fast Astro kit with your brand’s colours, fonts and logo.
What would you add to that list?
I'd want a list of files that still depend on the old site. A post can export successfully while its images still point to WordPress. Show which media files are included in the ZIP and which links need attention before the old host is switched off.