Since I added the "remove" keyword logic, fixed the "add" keyword logic, and since some team dev forgot to use the twig {{ registerTemplateCssFile(''mystyle.css') }} function, I've updated the Wiki about creating a theme from scratch.

I explained more in details all the logic of the manifest "files" section, and how recursivity works for CSS and JS files.


www.limesurvey.org/manual/New_Template_S...a_theme_from_scratch

Feel free to fix my frenglish, and to ask here for some questions if anything is not clear.

Hi Louis, didn't start currently a new theme. But since github.com/LimeSurvey/LimeSurvey/commit/...764aa0873fb8619dR424 applications/views/ is always readed at end of all template twig file : maybe we can move some vanilla files from vanilla to core ? Or create more really simple twig for core (without any options/javascript hack etc …).

Then, for example : a theme dev can create a new template from scratch but without all functionality (register/survey listing/optin/optout etc …).

What it's your opinion on such system ? For 4.0 or can start now ?

yeah a "skeleton" theme for limesurvey without any option, nor the ajax system, is needed for easy learning of the theme engine.

OK, i create a mantis issue with

1. What twig file we can move to app/views/ without updating
2. What twig file we must rewrite before moving to app/views/