we can probably re-use them too. I don't think you can make any container layout neutral though, without some absolute positioning tricks. For example a layout for mobile device version will probably very different - e.g. all the little links will be best taken outside into a separate toolbox.
Evgeny (
2010-05-07 11:15:16 -0500
)edit
Should we have any mandatory stuctural elements in skins?
My initial thought was - mark up all pure content elements with some naming convention. For example ab_q_title would be class name for question title, or ab_query_id id of search query input element. Postfix _id would make id's distinct from classes.
The question is - should we also have some mandatory structural blocks? I.e. container types that would group elements like question title, question toolbar (with delete, edit, etc. links), etc.
Originally I though that we shouldn't because structure items like that enforce layout which will make building alternative layouts harder.
What do you think?
1 Answer
Yes, wrappers would be a great thing! I've already come across a few bumps while customizing the default template where a wrapper DIV would have come in very handy.
I think it's possible to make those wrappers "layout neutral" - if necessary, by forcing a "display: inline" on them while customizing. It will require changing two classes instead of just one in case of deeper customizations, but that is an okay price to pay IMO.
Comments
Reliable Askbot Hosting
Create your Q&A site at askbot.com. Managed Askbot hosting at just $15/mo. Dedicated hosting, support contracts, consulting services.
create your Q&A site30 days free trial
Stats
Asked: 2010-05-06 20:37:11 -0500
Seen: 605 times
Last updated: May 07 '10
