-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Markdown Importer #51
Comments
This kind of thing would be brilliant! What kind of structure would/could something like this look like within the ZIP file?
|
Yes and yes :) also markdown hrefs would be preserved as WordPress links |
I like this a lot ! |
I'd like to add another level, the root level should be post_type followed by pages/subpages. That would allow to import any kind of content, may it be deeply nested hierarchical pages or posts with no hierarchy at all. Or whatever custom post type someone's (documentation) website would need. |
WordPress for Docs require a markdown importing pipeline. Let's integrate one with Playground, see also https://github.com/adamziel/site-transfer-protocol
Furthermore, migrating existing projects into Playground/based workflow would be much easier if there was a markdown importer — upload a zipped directory structure with markdown files inside (optionally including frontmatter), and get a hierarchy of WordPress pages with valid blocks.
Cc @jordesign as This sounds like a data liberation project.
Let's also do this while we are working on git imports WordPress/playground-tools#314
The text was updated successfully, but these errors were encountered: