parse2plone (0.9.9)
- parse2plone download link: http://plone.org/products/parse2plone/releases
- Homepage of parse2plone: http://plone.org/products/parse2plone
- parse2plone repository: https://github.com/aclark4life/Parse2Plone/blob/master/README.txt
- Description source: https://github.com/aclark4life/Parse2Plone/blob/master/README.txt
Parse2Plone is an HTML parser (in the form of a Buildout recipe that creates a script for you) to easily get content from static HTML websites into Plone.
Warning
This is a Buildout recipe for use with Plone; by itself it does nothing. If you do not know what Plone is, please see: http://plone.org. If you do not know what Buildout is, please see: http://www.buildout.org/.
Getting started
Because it always drives me nuts when you have to dig for a recipe's options, here they are:
[import]
recipe = parse2plone
path = /Plone
illegal_chars = _ .
html_extensions = html
image_extensions = gif jpg jpeg png
file_extensiosn = mp3
target_tags = a div h1 h2 p
force = false
publish = false
slugify = false
rename = false
The parameters listed above are configured with their default values. Edit these values if you would like to change the default behavior; they are (mostly) self-explanatory. Now you can just cut and paste to get started or keep reading if you would like to know more.
Explanation
Why did you create Parse2Plone when the following packages already exist:
Here are some reasons:
- Because Parse2Plone is aimed at lowering the bar for folks who don't already know (or want to know) what a "transmogrifier blueprint" is but are able to update their buildout.cfg file; run Buildout; then run a single command all without having to think too much.
- collective.transmogrify provides a framework for creating reusable pipes (whose definitions are called blueprints). Parse2Plone provides a single, non-reusable "pipe/blueprint".
- The author had an itch to scratch; it will be nice for him to be able to say "just go write a script" and then point to an example.
- Transmogrifier and friends appear to be "developer's tools", while the author wants Parse2Plone to be an "end user's tool".
If you are a developer looking to create repeatable migrations, you probably want to be using collective.transmogrifier. If you are an end user that just wants to see your static website in Plone, then you might want to give Parse2Plone a try.
There is also this user comment, which captures the author's sentiment:
Parse2Plone's release was very timely as I need either this or something very
similar - and while I've no doubt I could make transmogrify do the job, it's a
lot of work for a one-shot loading of legacy pages.
-Derek Broughton