Skip to content
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

Import Feature #627

Open
mchavezi opened this issue Oct 29, 2024 · 2 comments
Open

Import Feature #627

mchavezi opened this issue Oct 29, 2024 · 2 comments

Comments

@mchavezi
Copy link

Is your feature request related to a problem? Please describe.
Users coming from WordPress most likely would like to import their posts, post types, and media uploads.

Describe the solution you'd like
A side bar item labeled: "Import". Import page allows you to select import source, ie: WordPress json endpoint and allow an assign function to ETL into Beacon.

Additional context
Originally was thinking of having import sources listed like: WordPress, Jekyll, etc, but I think simply putting a URL and using assigns function might be an elegant scalable solution.

@leandrocp
Copy link
Contributor

Hey @mchavezi have you used such Importers in other platforms that you could share? I wonder how other platforms support the conversion between data types and fields, for eg converting from ACF. We also need to find the balance between technical flexibility to allow developers work with different set of data versus the UX for end-users to actually use the Importers, for example it's interesting to have a list like you said because end-users are familiar with those names, it's like saying "hey click here to bring your WP site into Beacon" but at the same time under the hood it should have be flexible enough to import and sanitize data as best as possible.

@mchavezi
Copy link
Author

mchavezi commented Nov 4, 2024

Hi @leandrocp, I haven't used any importers recently but have been exploring moving my headless WP/Next.js site to Statamic. The Statamic Importer Addon uses concept called "Blueprints" that maps CSV or XML file to content fields. The CSV or XML file can include ACF fields as well, so that would just be another mapping to the Blueprint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants