Ability to have multiple HTML override packages

[ryanbelisle]

I understand T3 has a set of HTML Overrides that override the Joomla Core output built into the T3 Plugin. I was wondering if we could allow for multiple HTML Overrides in the plugin that then would be selectable in the Plugin or via the Theme interface?

Scenario 1:

X Theme company wants to create their own HTML Override's specific to there needs. They might be wanting to move to the T3 Framework, and to ease the Template conversion process, move their existing overrides to T3. They wouldn't want these overrides to be in each template, but in the plugin so there is only 1 code base to update for all their templates.

Scenario 2:

X Developer just might not agree with the HTML coding approach of T3 and want to create there own. They wouldn't want to modify the T3 Core HTML Overrides because this would cause updating issues. They also would want their overrides to rest in the plugin, and not in the individual templates so there is only 1 code base/copy they need to worry about.

Scenario 3 (Soapbox Specific):

Similar to Scenario 1, we have tons of templates on J1.5 Custom HTML overrides. It would be nice to create a setup of our own overrides that mimic our J1.5 HTML as closely as possible so the conversion to T3 is easier. So sites that we are porting from our old platform, we can just easily change a parameter from using the T3 Overrides to using our J1.5 setup in the plugin. This would be great because we wouldn't have to re-write all our CSS for those sites making the switch.

[raramuridesign]

This is a good approach and if this can be adopted it would help tremendously.
Thanks for suggesting.

[joomlart]

Currently, the core theme is put in folder "base" in the plugin. We should provide multiple core theme feature as an addon package of the plugin. IMO, the feature could be implemented as:

1. upload a base theme to folder plugins/system/t3/newbase
2. declare the new base theme in templateDetails.xml

---

<fieldset name="general_params" label="T3_GENERAL_LABEL" description="T3_GENERAL_DESC">
    <field name="coretheme" type="hidden" default="newbase" />
</fieldset>

---

How do you think about this approach ?

[raramuridesign]

The issue is the template overrides.
I think there should be a plugin inside to allow override of overrides or not, when updating the framework.

[joomlart]

The framework provides only default base theme. Developers can provide their own base themes and declare to use it in template. Therefore, when upgrading framework, their work is not lost.

[locii]

I like this idea but I guess as soon as folks start adding their own overrides to the plugin then they are technically forking the plugin and potentially need to update each time the install an update for the plugin. There would be a way to not touch the new overrides when installing the plugin but seems better to move the override fiels outside of the plugin all together.

Perhaps we could check the media folder for possible overrides? So these are just folders that get uploaded to media/t3/ and the plugin checks there before it checks the plugin?

Perhaps the priority should be:

1. template
2. media
3. plugin

What do you think?

[raramuridesign]

I think this approach could work.

[ryanbelisle]

Either approach works for me.

[joomlart]

@locii : the new overrides are not part of T3, therefore it will not be overridden when upgrade the plugin. However, put it in media folder is a good idea. We may allow developers add their own override name so we can have multiple overrides on the same site.

[joomlart]

The feature has been implemented in T3 1.2.0 now. New HTML base is put in media/t3/themes/[name] and declare in templateDetails.xml as:

---

<t3>
    <base>[name]</base>
</t3>

---