Download
2016-12-01, 23:47:40
Two general questions (having to do with i18n, components, dynpages):
1. In my understanding, components are like pages. Especially with dynpages you include them with a shortcode {% mycomponent %}
So, they are not theme-specific, in that they are not switched out if you change theme. Correct me if I am wrong.
There doesn't seem to be a need for theme-specific components anyway, since they usually contain code and can be put in the template as php, js, etc., and called from there at will.
1b. Where would you put supporting files for (site-wide) components? Is it consistent with the GS philosophy to put them into data/uploads/...?
The reason I am asking here and elsewhere, is that with GetSimple it is not generally useful to switch themes and still expect the new theme to sensibly display the same site. There are a few things such as Sidebar, tagline, header, footer, that seem to get some support out of the GS box, but I feel more can be done. The question is: should the matter be addressed by GS, some plugin, or some generally accepted techniques that GS already provides th hooks for (that I am not aware of as a relative newbie with a shallow knowledge of js, php, css)
2. Can you have a component 'mycomponent' and 'mycomponent_fr' where one will be called when the current language is French?
1. In my understanding, components are like pages. Especially with dynpages you include them with a shortcode {% mycomponent %}
So, they are not theme-specific, in that they are not switched out if you change theme. Correct me if I am wrong.
There doesn't seem to be a need for theme-specific components anyway, since they usually contain code and can be put in the template as php, js, etc., and called from there at will.
1b. Where would you put supporting files for (site-wide) components? Is it consistent with the GS philosophy to put them into data/uploads/...?
The reason I am asking here and elsewhere, is that with GetSimple it is not generally useful to switch themes and still expect the new theme to sensibly display the same site. There are a few things such as Sidebar, tagline, header, footer, that seem to get some support out of the GS box, but I feel more can be done. The question is: should the matter be addressed by GS, some plugin, or some generally accepted techniques that GS already provides th hooks for (that I am not aware of as a relative newbie with a shallow knowledge of js, php, css)
2. Can you have a component 'mycomponent' and 'mycomponent_fr' where one will be called when the current language is French?
