How you remove redundant non-modular components depends on whether the project contains content.

Projects With Content

If the project contains actively-maintained content, you must install the module and then use a migration script (migrate.py) to migrate the widgets. This script remaps data from a non-modular widget to the appropriate module, and also safely removes non-modular widgets and their associated patterns.

The migrate.py script is available in an EchoInk GitHub repo. For more information, see the following:

The README of the Content Scripts repo provides script installation and usage instructions: https://github.com/inkling/content-scripts
The migrate.py script: https://github.com/inkling/content-scripts/blob/master/modules/migrate.py

Because the script does not migrate non-modular patterns, use either SVN or the pattern-snippets.html.tpls ﬁle to remove or disable these ﬁles. For more information, see the next section.

Projects Without Content

If the project is new and meets the following criteria, you must remove all non-modular components, either before or after you install the module:

Project contains non-modular patterns, or non-modular widget and their associated patterns, or both.
Project does not contain text that you or a Habitat author has entered.

Contact your EchoInk representative if you need help migrating or removing non-modular components.

You can remove the ﬁles for the non-modular components using SVN. For information on using SVN, see the Workstation Applications chapter of the EchoInk Design Guide.

You can remove or comment out non-modular patterns in the pattern-snippets.html.tpls ﬁle of the project, located in SVN at the following URL:

https://habitat.inkling.com/project/<shortname>/theme/files/s9ml/.templates/pattern-snipp