Steve wrote: "Rewrite/re-org the Installation and configuration book. Make it's primary focus installing and configuring Drupal core."

Steve wrote: "Move the core and contrib module sections into the customization and theming book and treat it like a reference section."

The "core modules" and "contributed modules" chapters have been moved from the "Install and configuration" book to the "Customization and theming" book, about a week ago.

I propose further updates:

1. Rename "Customization and theming" to "Reference"
2. Group theming
3. Group Snippets

I am ready to make this change, but seek feedback first!

Comments

sepeck’s picture

sepeck commented
Status: Needs review » Postponed (maintainer needs more info)

I meant make the focus of that section reference, not change the name. Let's work on the installation handbook first and then turn our attention to the next one.

karldied’s picture

karldied commented
Category: bug » task

I'm OK with leaving this till later. I just think the top level pages could be clearer and reduce the forum load and answer the organization gripes. Especially now that Core and Contributed modules pages are moved to this book.

Where does configuration end, and customization start? Where does customization become development? I know the tiles and terms really didn't help me much when I started.

At the minimum, I still recommend moving "Drupal core modules" to the top and "Contributed modules" to second, and I'd still recommend renaming "Drupal core modules" to "Core modules."

senpai’s picture

senpai commented

Kardied said: Where does configuration end, and customization start? Where does customization become development?

I suppose I'd have to vote for a scenario where Installation and all it's related sub-pages contained ONLY info on Drupal Core. If a page deals specifically with a version of Core, that page would have to be added to or modified every time there was a version upgrade, and the page would have to be categorized for it's old version + the new version. This would make it understandable for users of all related versions, rather than ending up with two sub-pages that dealt with specific versions of Core Installation.

Installation
-- Installing Drupal
-- -- install on Windows
-- -- install on Apache
-- -- install on yada yada
-- Installing Modules
-- -- install core modules
-- -- install third party modules (sub-page, sure, but not related to Core. Navigational structure only)
-- Installing Themes
-- -- install default themes
-- -- install third party themes (sub-page, sure, but not related to Core. Navigational structure only)

Configuration would deal ONLY with Core and ALL of it's options/settings once the initial install was complete. This scenario has the added benefit of allowing those who are installing a new package (see above) to avoid reading about the configuration options until their basic work is done. This section cannot deal with add-on modules, unless those modules get rolled into Core during a new release.

If that happens, we'd simply take the text of the relevant 5.x [Configuration >> Third Party Modules >> Profile Module] page and paste it into [Configuration >> Core Modules >> Profile Module], and then eliminate the 5.x category from the old Profile Module page so that it no longer shows up in a search for 5.x shite.

Configuration
-- Configuring Drupal
-- -- 4.6 options
-- -- 4.7 options
-- -- 5.x options
-- Configuring Modules
-- -- configure core modules
-- -- configure third party modules (sub-page, sure, but not related to Core. Navigational structure only)
-- Configuring Themes
-- -- configuring default themes
-- -- configure third party themes (sub-page, sure, but not related to Core. Navigational structure only)

Now, where does customization become development? I cannot answer this, and I don't think anyone really can. It's such a widely varied gamut...

senpai’s picture

senpai commented
Status: Postponed (maintainer needs more info) » Fixed

I think this has been handled by Sepeck's docs re-org and the new docbook format in CVS.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.