Re: [Tikiwiki-artwork] Tiki.org (community) subpages theme mockup

[Torsten <tik...@tw...>]

Hi,

I agree, that functionality in general should not be added into a legacy
layout - this recalls for me, why I have been not liking the specific
approach of the social navbar at the first place.

*BUT*

We have the selfcontained themes now with a different directory
structure and there is space for custom templates.

*SO*

What do you all think to simply change the 'social navbar' to a 'social
theme' => /themes/socialtheme/templates/layout_view.tpl (<- social
navbar layout).

*Additionally *

Couldn't this be an opportunity to create a section in themes.tiki.org
for custom layout files for certain purposes?
The layout files (actually the code) could be provided as code plugins
on wiki pages.

Aditionally a documentation section where we describe how to play around
with the different templates and styles and how to customise.

Just thinking.

T.




On 16.01.2015 18:36, Nelson Ko wrote:
> Thought I'd chime in on my opinion as well (though I am not sure if I
> understand all the issues involved)...
>
> I think layouts serve an important purpose in that they set the
> overall framing of the site, and they can also be useful to get from
> zero to different variants of quite a bit of functionality rather
> quickly for new sites/admins,
>
> However, when there is a functionality that is added, it should first
> be added as a module, and then into a layout. This is not to say that
> a particular layout cannot come with modules "baked into" it though
> (as that provides a quick way to shorten the process to getting useful
> functionality working for new users/site admins without having to go
> through all the modules), but it should be possible in other layouts
> to get the functionality too by adding modules after the fact.
>
> Does this make sense?
>
>
>