Home ›
Porting a site to Drupal the Agaric Way (some notes)Porting a site to Drupal the Agaric Way (some notes)
Submitted by Benjamin Melançon on March 27, 2007 - 3:14pm
Dan showed a new recruit how to do a port to Drupal the Agaric way.
Some points to note:
- the HTML used on the pages (converting some sections of content to lists - "<ul><li>" etc) and the need to make links where the content calls for links
- creating a custom path for a node involves /replacing/ the existing path (a node will always be available at its /node/## address) with the new path-- not adding onto it. Furthermore, the good-looking path process can be automated (grabbed from titles) with the pathauto module.
- it's possible and recommended to move some content into blocks, which are a powerful way of showing some content on every site in the sidebar. This way non-main links don't have to be in the primary link menu.
Class dismissed.
Dan showed a new recruit how to do a port to Drupal the Agaric way.
Some points to note:
- the HTML used on the pages (converting some sections of content to lists - "<ul><li>" etc) and the need to make links where the content calls for links
- creating a custom path for a node involves /replacing/ the existing path (a node will always be available at its /node/## address) with the new path-- not adding onto it. Furthermore, the good-looking path process can be automated (grabbed from titles) with the pathauto module.
- it's possible and recommended to move some content into blocks, which are a powerful way of showing some content on every site in the sidebar. This way non-main links don't have to be in the primary link menu.
Class dismissed.
Comments
Post new comment