Creating Content

strict warning: Only variables should be passed by reference in /home/newich/public_html/modules/book/book.module on line 560.

"Wow, I've done all this and I still don't have any content on my site!" Well, let's fix that.

First, let me explain that the page your visitor sees first upon entering your site is usually called the "home" page. Drupal calls this the "front" page, much like a newspaper. This page is special to Drupal. I know you're in a hurry, but read about both "pages" and "stories" before you decide which to use to create your front (home) page.

Content Types


Drupal says, "If you want to add a static page, like a contact page or an about page, use a page." If you're used to building web sites with HTML, this is what you've done in the past. In general a "page" is going to stand on its own and will probably have a menu entry. You may also later add it into a book. When I created my first two sites (based on former static HTML sites, I made the front page a "page;" I have since changed to a "story."


Drupal says, "Stories are articles in their simplest form: they have a title, a teaser and a body, but can be extended by other modules. The teaser is part of the body too. Stories may be used as a personal blog or for news articles." Why they say to use it for a blog, I have no idea; they supply a blogging module as part of the core support.

Okay, you've seen the Drupal site and noticed that there are "pieces" all over the place. Look at the front page; you'll see several announcements with space between them - those are "stories."

I have now switched my sites to use stories on the front page. The "welcome" message is one story. I have an announcement story node that any of my admins can edit. If you want to have weather or cartoons, a story is a good idea. Another use is if you are on a net ring - put the ring links into a story.

Book Page

Drupal says, "A book is a collaborative writing effort: users can collaborate writing the pages of the book, positioning the pages in the right order, and reviewing or modifying pages previously written. So when you have some information to share or when you read a page of the book and you didn't like it, or if you think a certain page could have been written better, you can do something about it."

Another way to use a book is to collect related information together. A book has its own navigation, so it can also be used to de-clutter your menu.

Blog Entry

You probably already know what a blog is, but just in case: A blog is a diary, collection of thoughts, or other time-ordered content.


So have you decided what kind of content you want? No, okay, just start with a page; it's easy. As you go create your content, be thinking about the menu as well.


Drupal 7?

If I were to start using Drupal now should we consider using Drupal 7 yet?
I know you suggested Drupal 6 awhile ago.

Thanks again.

Community type website that needs signup tables< A volunteer website I've created which is collaborative using google docs set public with external iframe links.
I am looking for a simpler less fragile and faster solution.

I am learning about drupal, I have also seen something called mojomotor which is simple cms and allows committee leaders to edit "regions"

I would like to have a "signup" table, form, input and display or view, which allows authenticated users to add a "row" or record edit/modify and sometimes to delete the row.

This would probably be another class of authenticated user who does not have access to edit the "regions".
Admin= to install drupal<
Admin1 = top level -can do everything (but log in separately to be a member!) defines regions?
Admin2 = top level -can do everything (but log in separate to be a member) defines regions?
Members-A level = Committee Chairs and Leaders ---> can edit "Regions" and can create "Sub-Regions for signup tables".
Members- B level = Users can only view "Regions" and can only add, edit, modify ROWS in the "sub-Regions for signup tables".
They can also delete only their ROW until a Committee leader turns that feature "off".

Put another way, trying to think like Drupal, without really knowing drupal, with regard to this simple event signup table:
1. Allowing committee leaders to create the table and the fields or header as a part of a "region" or a certain kind of "region".
2. Allowing all authenticated users to add a row and populate it, modify it, and delete the row only (until any one of the committee leaders turns that feature off)

I know that drupal has a mysql database. Is this signup table possible to do?
Would it be difficult? Any suggestions?

I know you say start small and simple!! Which I will do. But I need to know if it is possible to add this on somehow.
Thanks for the great website!


Drupal uses what are called roles. Roles are granted certain permissions. Users are assigned to one or more roles, there by gaining those permissions. Modules set the permissions they need to do certain functions; if someone doesn't have the appropraite permission, they are not allowed to proceed. Permissions may be required to see a menu item, thereby dynamically altering the menu that they see.