What is the best way to integrate Landing Page layout on Modx?

Question

MODX

Hello!
There is a landing for 10 screens, which was asked to be put on cms after layout, in which one could edit anything. I chose modx because I have known it for a long time, I like it, but I mainly did multi-pages on it and without the ability to edit every line of text for the content manager. Therefore, when integrating a simple, but fully editable for km landing page, I faced the question of how to do it better in terms of optimization (I read that if you configure everything through additional fields, the site will slow down a lot) and from the point of view of convenience.
Can anyone share their experience with all the pros and cons?
I saw different tips on the network and through the division of all sections into separate resources, and then editing them through additional. fields, and through the division of all sections into chunks and also through editing through the add. fields, etc. But with sections that is clear. Here, it seems to me, there is not much difference. In any case, this is exactly the content that will always be displayed on the page.
This question began to bother me more because of modal windows, namely because of the amount of content in them. It would be desirable that they, like ordinary pages, were not loaded along with the main one, but were loaded only when called. If you do them through chunks with editable add. fields, so that such windows can be assembled by himself through additional. fields to the template, then in any case, all windows will be created inside the page along with the rest of the content, thereby increasing the page load time. And if through resources then? It’s just that I have never displayed content from resources in modal windows. It's one thing - static pages in resources that you go to via links from the menu, another thing - just a part of the code, broken into chunks for additional fields.
Can you please tell me the best way to organize all this?
As for the entire landing, at the moment I settled on the option: create modal windows with dynamic content through additional fields (the templates for each type of windows are stored in chunks), as well as the added elements in the sections themselves. And the rest of the static elements in sections that do not need to be added, but only edited, such as headings, text, pictures, I decided to do through ClientConfig. I don't know yet how good this will be. For km, it seems to me, it will be convenient. And here is how this will affect the page loading speed, because something is written in the reviews that all such options greatly affect this.

Answer 1

Storing information and displaying it on a page are two different things.
There is a landing page for 10 screens. If there is a lot of information, then 1 screen - 1 resource. If it is small and everything is simple, then migx can be used. Yuzat ClientConfig for titles of pages and pictures - so-so idea. You have 10 headings and 10 pictures. In resources, you have pagetitle and image for this (as a result, only 2 fields, easy to call in a template / chunk, easy to process), and in ClientConfig you will have to create 20 keys. In addition, the block editing process will become more complicated when the content and pictures are in the resource, and the title will need to be edited somewhere else. Use ClientConfig for data that will be the same in each block (telephone, mail, address).
The output of information - it all depends on what and where you need to output. All pop-ups can be called with Ajax, so that they do not load the page (a bunch of ready-made libraries). Optimize all images (for example here: ) make thumbnails through ptumb, and not change the size with css. )) The content itself, if there is a lot of it, you can also load it with Ajax (for example, when scrolling the page).
Avoid large nesting of chunks, complex conditions. Better use femon, it works faster. Do not forget that the standard template engine works outward, that is, for example, if , the template engine will take the code of both chunks, and only then display the one that matches the condition, as a result (if there is a lot of code in chunks) - slower page loading.