Managing themes

Bastian · 2006-02-23 12:23:24

I was not in touch with themes, just read themes on textbook.

Just an idea, not more not less:

How about to add a table txp_themes to db including all themes with pages, forms and css.
And if a theme is activated, copying all entries belonging to that theme to txp_page, txp_form and txp_css.

The themes themselfe are not included to txp-core, but using txp for the acitive one.
That should match to the requirements in textbook

Jeremie · 2006-02-23 12:42:55

If you want to test it without erasing all your hard work, we we’ll need a automated backup system for existing pages-forms-etc.

And in that system, how do we take a small bit from a theme, another bit from another theme, and so on ?

Bastian · 2006-02-23 14:27:29

Are you working on a theme manager or who does?

Jeremie · 2006-02-23 14:43:28

Look on the persistent post on this forum, and this thread. We are taking the first steps to describe it fully, so that a dev may code it.

Bastian · 2006-02-23 15:36:44

Opps, next time i first read and the write :)

zem · 2006-02-23 21:56:20

we’ll need a automated backup system for existing pages-forms-etc.

Once possibility is that we make every page/form/css belong to a theme. Including user-created stuff, not just those installed via the theme manager. Existing things go in “my site theme” or similar. The user can create a new theme at any time, and copy things from one theme to another.

Perhaps we could also make it possible to refer to things in other themes, e.g. form="othertheme.headline".

Last edited by zem (2006-02-23 21:58:10)

Jeremie · 2006-02-23 22:50:00

Everything belong to a theme, that would work but need some careful UA work not to confuse the beginners.

The idea of refering outside the loaded theme is quite nice however :)

hakjoon · 2006-02-23 23:08:07

I like the idea of everything belonging to a theme. And no one seems to have much of problem with that concept in Wordpress if you look at the endless numbers of kubrick sites out there.

I think it could simplify management tremendously specially if one could copy pages/forms/styles between themes or the theme as a whole to start a new variant. Seems much simpler then managing revsions or backups.

hcgtv · 2006-02-23 23:19:50

I like the idea of everything belonging to a theme also, that’s what I’ve become accustomed to in Nucleus.

In Nucleus, a skin/template combination is an XML file that is imported via the admin area. Unlike TXP, the CSS is kept on disk along with the images in a seperate /skins/ subdirectory. A skin in Nucleus is like a page in TXP and a template is a form, very similar methods to achieve a unique design.

Last edited by hcgtv (2006-02-23 23:20:12)

Skubidu · 2006-02-24 08:37:39

<blockquote>zem wrote:

Once possibility is that we make every page/form/css belong to a theme. Including user-created stuff, not just those installed via the theme manager. Existing things go in “my site theme” or similar. The user can create a new theme at any time, and copy things from one theme to another.

Perhaps we could also make it possible to refer to things in other themes, e.g. form="othertheme.headline".
</blockquote>

These are both very nice ideas!
But if the sections are separated from this (as you are talking about pages, forms and css) I think it’s going to be confusing for beginners.

Last edited by Skubidu (2006-02-24 08:39:47)

NyteOwl · 2006-02-24 16:13:12

I already have a headache ;p

zem · 2006-02-26 00:37:53

But if the sections are separated from this (as you are talking about pages, forms and css) I think it’s going to be confusing for beginners.

Can you elaborate on this? Why is that confusing, exactly? For end users or template designers? What would the alternative be, and how would that be less confusing?

Jeremie · 2006-02-26 00:47:14

Maybe because sections are labeled “presentation” in the backend (of course it’s really not the case, but you won’t learn that until you have quite toyed with TXP :p) and in some beginners mind a theme include all things “presentation” ?

However, I don’t quite share the sentiment, and more and more disagree with my first assessment of the would-be tool. Sections in it might very well be a bad idea.

Skubidu · 2006-02-26 09:17:33

Can you elaborate on this? Why is that confusing, exactly? For end users or template designers? What would the alternative be, and how would that be less confusing?

Okay, I’ll try :)
The presentation is separated in two parts: The webdesign (pages, forms, styles) und the webstructure (sections). So if you just take the webdesign you will need to give many advices for the user how to set up the webstructur / the sections. It might help to have new tags that output certain navigation elements, but what about special subpages (about, colophon) or something which you have to set up manually as section. What about the section settings, too? What to show on frontpage etc. That might be important for a theme, too (mostly if the themes are getting more complicated). It’s not a problem for a advanced user to handle all this but I think most of the theme users will be newbies.
If only pages, forms and styles belong to a theme, what happens if you switch? Different themes need different section settings…

So, you ask about an alternative. Well, I have to say, I don’t know. I don’t say your idea is bad, but I remember all the question we had and have on the German TXP Blog and that why I supose that there will be some new user problems.

Hope you understand what I’m trying to say – it a difficult topic and it’s not so easy to explain the own thoughts in a forreign language if you’re not quite sure about a solution yet.

zem · 2006-02-26 09:32:41

I don’t really think it’s the job of a template (or template designer) to specify the site structure. Sure, link to special sections (about, contact) if they exist; but I don’t think a template should come with a “create sections” step, whether it’s automatic or manual.

Textpattern CMS

Textpattern CMS support forum

#1 2006-02-23 12:23:24

Managing themes

#2 2006-02-23 12:42:55

Re: Managing themes

#3 2006-02-23 14:27:29

Re: Managing themes

#4 2006-02-23 14:43:28

Re: Managing themes

#5 2006-02-23 15:36:44

Re: Managing themes

#6 2006-02-23 21:56:20

Re: Managing themes

#7 2006-02-23 22:50:00

Re: Managing themes

#8 2006-02-23 23:08:07

Re: Managing themes

#9 2006-02-23 23:19:50

Re: Managing themes

#10 2006-02-24 08:37:39

Re: Managing themes

#11 2006-02-24 16:13:12

Re: Managing themes

#12 2006-02-26 00:37:53

Re: Managing themes

#13 2006-02-26 00:47:14

Re: Managing themes

#14 2006-02-26 09:17:33

Re: Managing themes

#15 2006-02-26 09:32:41

Re: Managing themes

Board footer