search

gohugoio / hugo

The world’s fastest framework for building websites.
https://gohugo.io
Apache License 2.0
74.81k stars 7.46k forks source link

[Roadmap] Exporters #640

Closed jice-lavocat closed 8 years ago

jice-lavocat commented 9 years ago

Hi all,

Just read the roadmap and saw the line related to Importers (Jekyll/Wp). For WP I have tried successfully Wordpress to Hugo exporter by @SchumacherFM

What would be the requirements for such exporters ?

spf13 commented 9 years ago

Wow. I didn't know that library existed. We really should add a page to the documentation on migrating your site to hugo.

The goal for the exporters is that they would ship with Hugo and be able to take content from various other systems and put them into hugo's format. The work I did on the convert and new features as hugo could be seen as laying the foundation to be able to do this well.

Perhaps a jekyll one would be best done first as it's the closest today and would require very little to change.

The overarching goal is to migrate content:

  1. Without losing any data
  2. With retaining the urls.
bep commented 9 years ago

I had some troubles with that exporter, had to throw it away (read somewhere else that it has some problems with the most recent WP versions - me I didn't get any taxonomies exported).

mohae commented 9 years ago

@bjornerik's experience with the linked exporter makes me wonder if exporters should be standalone with a separate section to the documentation, as @spf13 mentioned, with information on how to convert content from a source CMS to Hugo and links to the various converters, since they bring in their own maintenance and support overhead in terms of keeping up with the source CMS versions.

bep commented 9 years ago

I can add a few of my thoughts about this. There are two kinds of WP exporters:

  1. Those who use WP to do the export (like the above), using plugins etc. to do the rendering before the export.
  2. Exporters going direct to the DB/XML export.

The first SOUNDS like a good idea, but I suspect it in most cases gets too messy -- with Markdown cluttred with HTML. So, like me, the way to go would be some of the Ruby exporters with some regexp filters for categories and tags, and then finish the job with good old Perl.

bep commented 8 years ago

Closing as this is on the roadmap.

github-actions[bot] commented 2 years ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.