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

What is a Content Management System?


The traditional model for a web site has been a file for each page. The 'home page' might be a file named index.html, and for the About Us page, another file named about.html. This model works fine for an unchanging (static) 'Hello—here is what we do—come see us—Bye' site, but for a site where the content changes often, or a site where showcasing content is what you do, it's a horrible model for someone who is not a web site developer to maintain.

With a CMS, the goal is to segregate the content (the text and images) from all of the cryptic computerese, so that in many cases, adding and editing content is no more complicated than creating a document in your favorite text editor.