Implementor

1. Review all created pages to make sure there are enough of them.
2. Check if the correct templates are applied to the pages.
3. Review the page content and replace repeating elements with snippets, and necessary blocks with Custom Modules - for ease of management.
4. Check if forms are displayed correctly.
5. Fill in SEO for pages.

Link to Pages documentation

1. Check what Templates were created for the page. Usually, a separate template is used for the main page (Home) because it differs significantly from the others. In addition, there should be a generic template that is applied to all other pages of the site.
2. Additionally, determine if there are Templates for different pages and whether they are needed. It often happens that separate Templates are required for pages without main banners or some repeating elements. Sometimes, Template variants with different widths of the main content block or divided into several columns (main content and sidebar) are also needed.
3. If the same elements are used in templates, for example, a static banner, you need to check if they are moved to separate snippets (elements).
4. Make sure that the generic template is selected as the default, since it is the default template that is initially applied to system pages (for these pages, Settings -> System Pages)

Link to Content Template documentation

1. Check if the "head", "header", and "footer" elements are moved to separate Snippets.
2. If there are frequently repeating elements on the site, for example, CTA Banners, make sure they are moved to a separate snippet so that the content of these elements can be changed in one place, and not on each page or template separately.
3. If the site should have functionality for OSE (On-Site Editor), for convenience in Snippets, you can add buttons for OSE integration:
4. In the "head" Snippet, check if the paths to CSS, JS files and fonts, images, etc. are specified correctly.
5. In the "header" Snippet, check if the main site navigation is moved to a separate menu module (Content -> Menu). Make sure there is a link to the Home page on the logo.

Link to Snippets documentation

1. In the Menu tab (Content -> Menu), check if the Items for the menu are specified correctly: whether the links are correct, whether all necessary attributes, classes, etc. are specified. Also, check the correct use of layout to display the menu itself, menu items, and dropdown items. Also in the Menu tab, check if navigation is created for the footer if it is needed. In addition, make sure there is a separate navigation for the mobile version of the site if it is required.

Link to Menus documentation

1. If there are forms in the site design, it is necessary to check if the implementor created them correctly ( in the Forms tab). The implementor creates the form, fields, and applies the layout from the markup, setting the correct name and action so that the form is sent correctly. Also, reCAPTCHA is always added.
2. In the Form Builder tab, you need to check if all the necessary default and custom fields are present, as well as if the required flags are set.
3. In the Edit Layout tab, review if the layout from the markup is correctly applied to the form and its fields, as well as if all the necessary parameters for the fields and other settings are present.
4. In the Settings tab, if necessary, specify the required workflow for the form, as well as configure the member area, autoresponder, and other parameters as needed.
5. Forms can be displayed anywhere you need - in snippets, pages, templates, and so on.

Link to Forms documentation

1. The next step is to create Custom Modules (so that the site is not hard-coded). Custom Modules can be used to create simple or complex data structures to dynamically manage content on your site or web application. From a simple page with employee profiles or a detailed image gallery to a complex real estate catalog, custom modules help consistently display datasets, simplifying content management for administrators and even providing the ability to safely post user-generated content.
2. Most often, Custom Modules include banners from the main page (Home), banners from other pages (since they usually have the same structure), reviews, and other boxes for sliders, services, and galleries. You can also move snippets to Custom Modules, for example, CTA Banners, if they have the same structure but different content, and so on.
3. For blogs (news), events, galleries, and FAQ, there are separate tabs, so they don't necessarily need to be created as separate Custom Modules.
4. In the Settings tab, the module name is specified, and you can also rename the URL and connect various additional settings.
5. Custom Module, you can configure Properties (Item Properties tab), Content (Properties) that can be changed through OSE (On-Site Editor Settings tab), as well as Layouts for displaying elements on different pages or blocks, and Layouts for displaying an element in a list or on a separate detail page of the element. In addition, you can configure the display view of elements directly in the platform (Table tab).
6. In the Properties tab, you can select default properties that the element will have, as well as create custom properties with various field types, such as string, number, boolean, checkboxes, radio buttons, media, and others for convenient item content management.
7. In the Layouts tab, you can add the necessary templates (layouts) for displaying elements. By default, there are always two templates (layouts): for the detail page (detail) and for the list page (list).
8. In the Table tab, you can configure the display order of the element's properties for quick and convenient search.
9. After creating a Custom Module, it is easy and convenient to display it on any page, template, snippet, other custom module, and so on.
10. When displaying elements (items) through Custom Modules, it is easy to manage their display order, filtering, selected layout, and other settings.
11. You can also fill in SEO for the detail pages of custom module items if necessary.

Link to Custom Modules documentation

1. For greater convenience, you can configure Site Globals. Site Globals, under 'Settings', is where you can set up customised data points for your website that will then become globally available throughout the site, wherever Liquid mark-up can be used. Typical use-cases for Site Globals might be to store the company name, address, contacts, logo, etc. in one handy location and render that information throughout the site via Liquid. Providing a more maintainable set of data if, say, a phone number or email address changes and needs to be updated site-wide.
2. Properties (Properties) in Site Globals can also be changed in OSE (On-Site Editor) mode.

Link to Site Globals documentation

1. Separately, make sure that the correct Template is set for System Pages, and also, if necessary, complete or redo their Content or code.
2. Fill in SEO for pages if necessary.

Link to System Pages documentation

1. If necessary, you can configure the On-Site Editor. A detailed description of OSE settings is available in the documentation at the link above.
2. OSE can be added to Custom Modules, additionally selecting which properties will be available for editing in OSE mode.
3. Also, OSE can be connected for text elements on pages and in snippets, as well as for Site Globals.
4. To enable editing and deleting, adding elements on the page, it is necessary to add Edit, Delete, and Add buttons in Custom Modules and on pages. In normal page display mode, these buttons will not be visible, only in On-Site Editor mode.
5. To enable editing of Site Globals, it is necessary to set the flag in the item group settings so that they can be edited in OSE mode.

Link to OSE documentation