Global Themes in Revolution 2.0.0 RC3

Well, i’ve take a look at your link SiNNuT.

This already possible with MODx.

In Revolution, you create a template and then use Templates variable to change your layout.

It’s up to the designer to create the containers because MODx doesn’t provide the "block" facility of almost all existing CMS.
But that was my point, it IS the good point of MODx. It does not enforce you to use its facility, you have to build it by yourself.

Since MODx let you choose your markup, it’s not possible to give designers default template behaviour for a common template interface.
We (as designer) can provide guidance that you can anywhere on the web.
But nothing justify the right for MODx to impose the use of "sidebar" instead "aside" or "content" instead of "main".

That’s being said, MODx (Revolution at least) is flexible enough to allow a more fine control "a la concrete5" with the help of a custom manager page.
I’m not saying that it would be easy, but it’s possible.
ExtJS (and little PHP) can easily put up a page like this one:



On top you can imagine the related TVs that are changed when you select a template form the below list.
It may be a good idea to propose something like that to the team with less intrusive behaviour than in concrete5.

Quote from: lossendae at Jul 20, 2010, 02:32 PM

It’s up to the designer to create the containers because MODx doesn’t provide the "block" facility of almost all existing CMS.
But that was my point, it IS the good point of MODx. It does not enforce you to use its facility, you have to build it by yourself.

+1

I always setup a config/settings resource / template with default TV values (Evo). Here client can control the default values of all kinds site wide.
Each "setting" can be assigned many TV’s like value, override local TV etc.
Then use a snippet in the site templates that output the default value depending of local TV is empty or override TV is set to override.

So lossendae, You see the type of functionality I was looking for now. modx is too great in every other way to give up on and use concrete5 for.

mrhaw, are you saying that I could create a TV that would be linked on every page so changing it on one would effectively change it on all? If so this would certainly be an interim way of building this facility into my proposed modx system. Not quite as fancy as the concrete5 interface but better than having users possibly choosing different styles on each page... not good

Ideally, all I am asking is that modx separates the visual from the structure -

therefore users can choose any type of ’structure’ on a page but can only globally choose the ’style’ to be wrapped around those ’structures’

Quote from: mmuller at Jul 20, 2010, 04:35 PM

mrhaw, are you saying that I could create a TV that would be linked on every page so changing it on one would effectively change it on all? If so this would certainly be an interim way of building this facility into my proposed modx system. Not quite as fancy as the concrete5 interface but better than having users possibly choosing different styles on each page... not good

Yes and it’s as fancy as _I want_ it to be! In Evo I use $modx->runSnippet and GetField
and simple if, elsif statements. Haven’t done this in Revo yet. But I’m sure there is many
ways of doing it, as is, why doing it in MODx.

Maybe I’m misunderstanding what you want, but this seems really simple to me in Revo.

A page with screenshots of each theme can set a User Setting for the current user to the theme ID of the image clicked on.

A snippet (call it GetThemeCSS) in each template checks the User Setting and determines the appropriate CSS file for that theme:




Any time the user returns, they get their chosen theme and they can revisit the theme selection page at any time to change it.

Quote from: BobRay at Jul 21, 2010, 12:24 AM

Maybe I’m misunderstanding what you want, but this seems really simple to me in Revo.

A page with screenshots of each theme can set a User Setting for the current user to the theme ID of the image clicked on.

A snippet (call it GetThemeCSS) in each template checks the User Setting and determines the appropriate CSS file for that theme:

<link rel="stylesheet" type="text/css" href="http://yoursite.com/[[!GetThemeCSS]]" />

Any time the user returns, they get their chosen theme and they can revisit the theme selection page at any time to change it.

Bingo Ringo !

Do you not think that this is something that would benefit the whole modxcms community - a global theme selector, and still have page templates for offering different page layouts

As a third party package why not but i don’t want it to be built in.
I don’t want MODx to choose my markup for me.

mmuller,

We do not, by design impose how a site will look you are more than welcome to add any functionality to your site or build a 3rd party add-on to enable others to implement the same functionality. MODx will never include or impose a particular way of doing things but allow developers and designers to make those decisions.

I started using MODx precisely because I controlled the output and functionality. Every site I built for clients was different and only one required a user selectable CSS theme once.

Thanks for your interest and effort to understand how to work in MODx.

Cheers,

Jay

Quote from: mmuller at Jul 21, 2010, 07:06 AM

Do you not think that this is something that would benefit the whole modxcms community - a global theme selector, and still have page templates for offering different page layouts

No, not in the core.

No problem smashingred,

I just want to add that I absolutely love working with modx - it is simply awesome how you can strip down a client website into a CMS in a matter of minutes/hours and I now build my sites (static or otherwise) with modx in mind for a future rollout.

A few of my clients even have it although they don’t know it

Once they start paying up - I will surely donate as it is quite simply one of the best CMS’s to build on.

regards