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—Page


If having 'content' as a keyword in Drupal isn't confusing enough, then how about Page also being a keyword? To avoid confusion in our work, we'll capitalize the word, when it is being used in the Drupal context and not to mean a generic page.

Drupal looks at a Page as being Node Content that will not be published automatically in the Node Content area of the front page, as the story that we just created was. Instead, it sees the Page as being something that is, perhaps, relatively static, such as an About Us page. The default Publication settings for a Page reflect this, as the Promoted to front page option is not selected.

That said, there is no real difference between a Story and a Page. In fact, you are free to change the default settings for either Node Content type so that there is no difference at all, or, for example, so that a Story acts like a Page, and a Page like a Story. Even by leaving the default settings as they are, you can choose to (un)publish or...