I really like this module and the ease of the Latte syntax, but when trying to start my first project (both in Latte & PW) I found the following questions:
Where implement the business logic for the @layout file? if this file is only for output and its not a good practice to include php logic. For example I need to do some processing before printing the site header and the area for the logged user.
Following the previous question, if the option for including Blocks require a more complex data process, where I do that? I have no controller file for Blocks/Chunks and only can pass variables directly inside the Latte view that include it
The multi-language native processwire system does not work, for example the url "sitename.com/es/" causes an include error.
I want to implement my sites using Latte, but now I'm worried if it suits the complexities that can appear during dev
I want to make a language switcher for my site header but I don't want to use the LanguageSupportPageNames module, in this website case I prefer using path siterootpath/services for English and siterootpath/es/services for Spanish, but I can't print the path without $page->localurl() and that function seems to be only available in the LanguageSupportPageNames module .. too if I put siterootpath/es/ in the browser this causes me a 404 error.. How to do this, please?