[documentation] snippets book

[Liza Sabater]

I am probably the most impatient of 'power users' in Drupal and I  
have to say that I have fallen in love with this section. Just give  
me more please!

I have a question : IHas anybody compared blow-by-blow an MT template  
or WordPress theme against a Drupal one? Blog designers are not all  
like ScriptyGoddess who, well, is a coder and designer. Breaking down  
a template might be making it easy for people to transition from  
designing and customizing blogs to Drupal. At least it would have  
made it easier for me :) I can work on the MT example.

/ liza

On Dec 01 2005, at 10:01, Charlie Lowe wrote:

> Does anyone disagree with this structure? It seems like a good  
> improvement to separate these out and it will make it much easier  
> to find the PHP Snippets.
>
> If there are no real concerns, can I suggest creating a  
> documentation issue for this reorganization? And let me know if I  
> can help.
>
> Farsheed wrote:
>> I would suggest keeping the name "PHP Snippets" for
>> snippets of PHP code, because that's what they are. Also remember  
>> hack has a negative connotation, i.e.
>> "It's hacked together" and it also suggests that it
>> takes some skill to hack. I think it's important to
>> describe things as simply and accurately as possible.
>> I also agree with Nick about Configuration and
>> Customization being top level books. Maybe something
>> like:
>> Customization
>> -PHP Snippets
>> --block snippets
>> --page snippets
>> -Theme building
>> --theme tricks and methods
>> -Module building
>> --module testing and tricks (how did you start
>> learning to code modules?)
>> -Other tricks
>> Configuration
>> -How to get your site going once installed
>> --roles, permissions
>> --general settings
>> --theme config
>> --adding new modules
>> --module config
>> --block config
>> -User submitted configurations/descriptions of their
>> drupal site
>> -etc...
>
> -- 
> [ documentation | http://lists.drupal.org/listinfo/documentation ]
>