I’m looking to, just as simply as I can, take an existing html site built with tables and add in some content managable areas. From my limited experimenting and searchings, I don’t see how you can impliment MODx without using it’s wayfarer navigation, and completely rebuilding the site.
Any illumination on this subject would be great. Thanks.
-B
Ben Eriksen
-
MODX Staff
- 10,725 Posts
You can use static HTML content in all of your MODx documents, templates, chunks, etc.; nothing forces you to use Wayfinder or any other snippet of code to automate navigation building or any other functionality, though I find it wonderfully efficient to allow my content editors to simply create a new page and have it show up in various menus throughout the site, with no additional work.
Regardless, I’ve deployed many sites that were simply static HTML pages imported into MODx and contained either a global menu chunk I could edit in one place, or a template variable for the menu which could be customized manually for each section and/or page in the site. The chunk approach is trivial to implement -- just cut out the menu and paste it into a chunk called menu, then place the {{menu}} chunk on your template in place of the markup you just cut out. Identifying and creating template variables for the various editable sections (beyond the main content, if any) should only be slightly more complex, and dependent only on you taking the time to understand what template variables are and how they work.
excellent, thanks -- chunks... i’ll check them out.
Ben Eriksen
This is the general breakdown of the building blocks...
chunks hold basic html
snippets are for php code
TemplateVariables (TV) are for all sorts of things and are a key feature of MODx
