Type: Documentation
Author: davidwees
Task description:
Utilizing at least a rudimentary understanding of PHP, good XHTML and CSS skills, take the same node form and add fields to it using the CCK module (http://drupal.org/project/cck), then theme this form, making sure to document your work. This is a task that nearly all professional Drupal developers need to know how to do.
Using good coding practice (http://drupal.org/coding-standards) to complete this task, you must:
1. Create a new content type.
2. Add at least 5 different types of fields to the content type.
3. Using the phptemplate theme engine (http://drupal.org/phptemplate), theme the content type you created in 3 visually distinct ways. Note that this task is not about changing the display of the form after it is submitted, but while the user is entering his/her data.
When you have completed this task, you should create a documentation page in the appropriate location in the theming portion of the handbook which describes your changes and provides your code, as well as screen-shots of what the changes look like.
Some resources to help you with this task are:
1. The documentation on the PHPTemplate engine is available here: http://drupal.org/phptemplate
2. General information about creating theme overrides is available here: http://drupal.org/node/55126
3. Information specific to theming a form is available here: http://drupal.org/node/112358
4. If you need help, you can post a question in the forums (http://drupal.org/forum) or contact someone on the #drupal-support channel on irc.freenode.net.
5. When you need to create your screen-shot, read this page first: http://drupal.org/node/11637
I estimate that this task should take about 4-5 days to complete.
Task manager: dwees
Comments
Comment #1
snufkin commentedClaimed by dawehner: http://code.google.com/p/google-highly-open-participation-drupal/issues/...
Comment #2
webchickComment #3
dawehnerIs this ok, shell I write more and do you find English grammar mistakes ? Thx
Comment #4
webchickMarking needs review.
Comment #5
dwees commentedThe structure is good, just have some minor points.
1. 'Contenttyp' should be 'content type'
2. Use
andas your wrappers for your code, since they preserve whitespace,unfortunately removes all the extra whitespace.3. Instead of linking to a code pasting site, put your code in the page, wrapped in
andtags, then it will be around longer. Those code pasting sites tend to disappear pretty easily, we'd rather not lose your code.4. Remove the code from your examples that is commented out.
Once you have done this, I'll mark this task as complete as your code looks sound.
Comment #6
dawehnerso here are my fixes
a need another task :)
Comment #7
dwees commentedAnyone else see this as RTBC? I guess I'll put his text in a page in the appropriate location in the developer's handbook, then once someone else agrees, we can make this as completed.
Comment #8
dwees commentedOkay found some very minor issues.
1. Where does one put this code?
2. Coding standard:
should be
Comment #9
dwees commentedSee http://drupal.org/node/198572
Comment #10
webchickI've marked this task complete in the Google tracker. Good job!
Now I'm moving over to the Documentation list so we can go in and make some minor corrections (grammar/spelling, coding standards, etc.)
Comment #11
dawehneris it possible to use my screenshots?
Comment #12
johnnocChanged the component to reflect the new component categorization.
John
-----------------------
Drupal Norge
Det offisielle norske nettstedet for Drupal
Comment #13
add1sun commented