ReadyTheme vs ReadyThemes

[lesliekirk]

Props on adding the ReadyTheme icon to the home page and moving the link in the menu tree.

Going to <mvt:rant> a little bit. This forum was created for ReadyTheme functionality questions (see the description: Questions regarding the new ReadyTheme functionality in Version 9), but there is still a bit of crossover with ReadyThemes questions. I pled my case that ReadyTheme should be renamed ReadyTools but that seems to have fallen on deaf ears. I'm sure I'm not the only one that has to explain the difference? </mvt:rant>

[Brennan]

Re: ReadyTheme vs ReadyThemes

Are you talking about the difference between a ReadyTheme you download and install vs the section in the admin where you administer/customize your Theme?

I do agree with you it can be slightly confusing, however we've typically seen customers "get it" in the first few minutes and never look back. What have you been experiencing?

[alphabet]

Re: ReadyTheme vs ReadyThemes

I think of a Ready Theme as Global Content.

It took me a few minutes to get it because I relate the word theme to framework which to me is style and grid.

I find a ready theme is similar to a page template that doesn't have items assigned or a url footprint.

Which begs to a larger question, what is a page? Is a page - a page, is a page - a content item, is a page - a template, or is a page all of the above?

I try to avoid using pages for content or templates but sometimes I have to because it is easier to assign items to. Content items and ready themes don't have a url structure and you can't assign items to them. So I get concerned about the url structure of using pages as content.

For the DRY principal, I find myself using the ready theme (global content) more often but I have to use more mvt:do functions. I find myself using the content item as a template on pages that don't need to be globally managed.

I hope that makes sense.

[Bruce - PhosphorMedia]

Re: ReadyTheme vs ReadyThemes

I think the main point of confusion is that ReadyThemes are not really frameworks in the standard sense that they are independent of content and only possess the functional framework of a site. Understandably, cause otherwise a "ready theme framework in this sense would have to have an entirely new layer beneath the current page templates merchant use.

The other item I see many struggle with, is that ReadyThemes are not really suited to be a starting place for a custom design, yet many who intend to do a custom design start with a ReadyTheme because of the functionality they inherently posses. (And yes, you can co opt that functionality within say the Base Ready or even standard CSSUI templates, but that's not very obvious.)

What might make this all clearer is to perhaps document the "Ready Theme Functionality" components OUTSIDE the context of the ReadyThemes Miva provides.

[lesliekirk]

Re: ReadyTheme vs ReadyThemes

Are you talking about the difference between a ReadyTheme you download and install vs the section in the admin where you administer/customize your Theme?

I do agree with you it can be slightly confusing, however we've typically seen customers "get it" in the first few minutes and never look back. What have you been experiencing?

Yes I am

I've even seen confusion in forum posts. Sure the customers "get it" AFTER it's explained to them, but how about offering clarity that doesn't need explaining?