Templates

Template naming conventions (top-level templates in /views/:

Template name	Path	Usage
[thing]-view.html	/[thing]/id	View article
[thing]-edit.html	/[thing]/id/edit	Edit contents of article
[thing]-localize.html	/[thing]/id/localize	Translate article (either single-column or side-by-side)
[thing]-view-localize.html	/[thing]/localize-view	Translate static text of view template
[thing]-edit-localize.html	/[thing]/localize-edit	Translate static text of edit/form template
[page]-view.html	/[page]	View static page
[page]-edit.html	/[page]/edit	Edit contents of static page
[page]-localize.html	/[page]/localize	Translate contents of static page
[page]-view-localize.html	/page/localize-edit	Translate static text of form for editing page

Partial naming conventions (partial templates in /views/partials):

Note: editing partials don't always follow the same component naming as view partials because they specify not only the type of component, but the desired editing widget. Some editing widget require additional attributes when including the partials in your top-level template.

For List vs. Grid views in search results, we may be able to handle the difference in CSS, in which case we can merge the two.

Template name	Usage
view-[component].html	Use in view templates to show data from the database
edit-[component].html	Use in edit templates to edit data from the database
footer.html	The page footer (needs some cleanup)
header.html	The page header
map.html	The map component
pagecount.html	page count for search results
search-grid-card.html	individual results when grid view is selected
search-grid-list.html	individual search results when list view is selected
tabnav.html	The control to select types of articles to get search results for