Book Image

Drupal 6 Content Administration

By : J. Ayen Green
Book Image

Drupal 6 Content Administration

By: J. Ayen Green

Overview of this book

Often a company hires a web designer to build its Drupal site, and then takes over running the site in house. This book is for the Content Editors concerned with the ongoing creation and maintenance of the site content. In a few hours, you'll have the knowledge needed to maintain and edit your web site as a content-rich place that visitors return to again and again. There are many books available to help you administer a Drupal site, but this is the only one specifically for Content Editors. This book doesn't cover designing or creating a site. However, anybody who has built their own site but needs some help using the article management features will also benefit from it. This book is a quick-start guide, aimed at Content Editors. The author's experience enables him to explain in an efficient and interactive manner how you can keep your site up to date. The book begins with a discussion of content management and Drupal and then teaches you how to create content, add elements to it, and make the content findable. You will then learn to set up the framework for a creative team and the various options for editing content offline, their benefits and pitfalls. This book helps you to quickly and easily solve problems, and manage content and users for a web site. It will help you become a more effective and efficient manager of Drupal-based web sites.
Table of Contents (15 chapters)
Drupal 6 Content Administration
Credits
About the Author
About the Reviewers
Preface

Node Content types


The default installation of Drupal contains two Node Content types namely: Page and Story. Some modules, when activated, create additional Node Content types. One such example is the Blog entry, and another is an Event, which is used when using an event calendar.

Note

We're using the term Node Content to differentiate content nodes in Drupal, such as Pages and Stories, from other non-node types of content, such as Blocks, which is the generic term for anything on the page.

What is the purpose of having different Node Content types? If we want a feature writer to be able to create Features, then how do we accomplish that?

Currently, we have Stories and Pages as our Node Content types. So, if we give the Feature writer the ability to create a Page, then what differentiates that Page from any other Page on our site? If we consider a Page as a Feature, then anyone who can create a Page has created a Feature, but that's not right, because not every Page is a Feature.

Activity...