It all depends on your programming style and patterns used. There are many ways to display HTML. It is best to have a single style in your application.
I prefer to output HTML like this:
echo <<<HTML div class="coming_soon"> <div class="icon"></div> <p>Здесь скоро появится новый урок...</p> </div> HTML;
This helps when navigating through files. It is enough to include search in <<<HTML .
But if you use the MVC pattern, then the logic should be separate, and the views separately. Since often the coder does not know PHP and vice versa.
Part of the PHP file controller:
<?php if ($time == 1) { return include $this->viewsPath.'_comming_soon.php'; }
View _comming_soon.php :
<div class="coming_soon"> <div class="icon"></div> <p>Здесь скоро появится новый урок...</p> </div>
<?php if ($time == 1) : ?>and close as<?php endif; ?><?php endif; ?>or<?php foreach ($time as $item) : ?>and close like<?php endforeach; ?><?php endforeach; ?>and so on ... so that you can see the correspondence between each other ............ php.net/manual/ru/control-structures.alternative-syntax.php - Alexey Shimanskyт.к. их сложно уследить при разрывет.к. их сложно уследить при разрыве- yes no, any IDE will highlight it for a long time, click after the curly bracket, you will see the end. Yes, and with whom I talked - nobody wants to see the BASIC; in general, for the first time, I see someone who likesendif;:) - Goncharov Alexanderя не могу быть не правым - т.к. это на вкус и цветя не могу быть не правым - т.к. это на вкус и цвет.... it’s a contradiction, so for a second ;-) ...... you can negotiate anything within the company, at least about inserting unicode raccoon drawings between the lines. This does not make it common practice. If you look at the queries of the search engine "alternative php syntax" you will not see in the responses to the request of braces, because the common practice is different. Including php.net shows exactly this practice (via endforeach, etc.) ... in general, I expressed myself - Alexey Shimansky