I have attached a theme I created, starting with Framework and removing the lines/borders.

This is useful when you want a totally blank start to make a theme from PSD with CSS.

I grew weary of constantly resetting the styles with Framework standard.

Place admin and menu blocks (use a NiceMenu for Navigation) in the footer, set visibility hidden for anon and auth user (or only enable for developer/admin role)

I am not sure if this needs to be its own project, or it is better included in the Framework distro

CommentFileSizeAuthor
#3 blank.zip21.2 KBdecibel.places
blank.zip25.49 KBdecibel.places

Comments

andregriffin’s picture

andregriffin commented

I completely agree that a blank theme would be better for consistent theme developing, but beginning themers usually benefit from seeing all the parts sectioned off. I plan on discontinuing the included dark theme as it is pretty easy for someone to make one themselves. Instead, I may include a blank version.

I don't plan on changing any of the default menu or block functionality, but thanks for your feedback and thanks for using Framework.

andregriffin’s picture

andregriffin commented
Assigned: Unassigned » andregriffin
decibel.places’s picture

decibel.places commented
StatusFileSize
new blank.zip21.2 KB

andre,

yes, the borders help show the sections, but they quickly become unwanted relics as the theme develops

perhaps you could recommend using Firefox with the Firebug and Web Developer add ons in the README

Using these tools (particularly Firebug) a beginning themer can quite clearly see sections and subsections

Oh, I realized there are a couple of unnecessary files in the zip I uploaded, automatic .bak files my editor creates. I am attaching a clean version

andregriffin’s picture

andregriffin commented
Status: Active » Closed (won't fix)

Upon loading up your theme, it didn't seem very blank to me. There were still layout borders, backgrounds, etc. Also, node teaser H2 titles appeared to be missing, which caused the administrative tabs (View, Edit) to run into/on top of the breadcrumb. I'm just pointing these things out so that you don't run into any problems when you're developing.

After giving it some thought, I decided that further customization of the Framework theme is best left to the individual user. That way, the user will be able to choose what they want to keep and what they don't. Any theme developer should be more than capable of handling their own version of Framework. Also, I won't have 4 versions of the CSS file to keep synchronized, consistent, and maintained ;-)

I would rather not have another project of Framework created for distribution, as there is no way I could guarantee consistency with the 'official' version. Also, there's no practical means for me keeping track of every line changed between releases, thus making it harder for someone else to sync their distro with mine.

I hope you understand by reasoning. Thanks for your effort and for being active in the development of Framework.

decibel.places’s picture

decibel.places commented
Component: CSS/HTML markup » Code

yes, I removed the node titles so the view would be just the content

there may be some elements I didn't get around to "vanilla" - izing (removing borders/backgrounds)

this is the current implementation: http://stevenmeier.com/

no problem about not including the blank option, I agree with your reasoning totally, I can of course keep a local copy of the stripped theme for further use

Grammarian’s picture

Grammarian commented
Component: Code » CSS/HTML markup

The link posted for "current implementation" (http://leadtracker.decibelplaces.com/) doesn't work.

decibel.places’s picture

decibel.places commented
Component: Code » CSS/HTML markup

That link was "current" as of 2008 since then a new CTO came in and threw out the Drupal site because he likes Joomla better. Anyway I updated the demo link with a more stable web site.