funnelweb-1.1.1-2.lbn13.noarch

Funnelweb is also very flexible as it uses a modular collective.transmogrifier framework underneath which advanced users can use if they they need further steps added to their conversion process.

The work performed by the funnelweb script can be broken down into four sections:

1. Crawling the site including caching locally so subsequent crawls are quicker and filtering out unwanted content 2. Remove boilerplate/templates (automatically or via rules) so just content remains 3. Analysing the site structure to improve the content quality including working out titles, default views, types of objects to create, what to show in navigation etc 4. Uploading to the CMS such as Plone, or saving cleaned HTML to local directory

FunnelWeb now has two modes of operation:

1. Within Plone itself via the mr.migrator plugin. see mr.migrator for how to install. 2. A command line script which can be installed via zc.buildout. Content is uploaded into Plone via it's web services API.