Good day! Please tell me about correct from the point of view of professional practice, layout of static pages. For example, I used to just create a separate template page-pagename.php or just the template - Name Template: templatename do everything in html. I recently saw the template colleagues, and he saw the whole content in an html template file page writes. and in the post, all the content in one post is displayed. I'm a little surprised by this, I'm not used to do so. Later, I reviewed the lesson about the "proper posadku on Wordpress", the user youtube - WebDesignMaster. It does the same thing, only instead of direct html code, sets the UNYSON plugin and makes through it all, there is certainly much more convenient to do so.
After some thought I came I came to the conclusion that it is even more logical and easier, except the plugins are updated, and UNYSON for example expanding, and if you want to add a new item to it, it is necessary to add in the code of the plugin.... In common as much as I thought it was easier, I still don't dare to devote themselves to this topic, I'm not sure in what direction to move.
So, the question about how to implement better and more convenient, as decided by the professionals?
Lessons user WebDesignMaster not worth watching. WordPress he teaches with mistakes. (If you don't believe me, look in my previous answers, periodically answer questions from people who had the misfortune learns in his video. Do not want to repeat).
On the layout:
both of these approaches can be applied to use in each particular case better, you need to watch.
1 layout in the template:
more professional, of course, the whole layout of the to do in the template code. And the content to keep in the database with adding a minimum markup.
The advantages of this approach:
not dependent on the plugin (wanted to change the plugin/engine - no problem, change)
usually, this page will be easier for a search bot
cleaner code (no drag on the page a bunch of unnecessary js/css from the plugin), faster page loads
you need to be able to impose
the customer will not be able to change the design of the page itself (in my opinion, questionable disadvantage. From experience, later the customer himself almost never the design will not change, maybe in the plugin to understand it will be difficult)
2 layout by configuring the plugin:
fast, cheap, lots of functions
immediately there is a handy admin panel to create pages
you can only do what is provided in the plugin to add new functionality can be very expensive
code goes terrible (usually the plugins/paid templates are loading a bunch of styles/scripts), hence we obtain a complexity of support and complexity of task automation (for example adding automatic publication of news from an external source with the desired formatting may take longer in the order)
some customers admin made such plugins, too complicated (occasionally I see orders like "we bought a template with a visual editor, set it to us at least as on demo website")
In a nutshell, with this approach you can quickly make a website of, sorry, g@BHA and sticks, to sell it to the customer and to escape quickly to do another. In some cases the customer this level of performance is quite satisfied.