Benjamin Tinker Team : Web Development Tags : Technology Web Development

Some CMS fields for setting up Standard Content Pages

Benjamin Tinker Team : Web Development Tags : Technology Web Development

Each time I set up a new website there is always a set of fields that I include as my base for all other pages. By having a base set of fields set up I only need one set of code and one set of objects to handle content that is generic enough to be used site wide. From this base I can then expand upon them for more specific content that requires more unique information not considerd Standard Content

Here are some helpful fields to include in your CMS that can be used across all page types:

Title - Simply the title of the page when viewing content. This is usually the field you will use when generating URLs.

Menu Title - Sometimes you may want to show a different title in the menu for your pages that is a shorter version of the main Title.

Published - Each page needs to be turned on and off again.

Summary - A WYSIWYG field for introduction text where you want to show parts of a page. This would be in places such as Search Results, Homepages and anywhere you need snapshots of content without showing it all.

Body - This is your main content for the page. It should always be a WYSIWYG allowing the user full access to your sites CSS, Imagary and Media.

Page Title - This is your SEO stuff. You can allow the user to set their own page titles that appear in the browser for managing their own SEO. It's also a good idea to have defaults in place if this is left blank so there is always some cotent.

Meta Description and Meta Keywords - More SEO control for the user. While these fields are good to have they do not necessarily get used most of the time. It's good to have the option there.

Generally all of the fields above will come into play when setting up web pages. As the function of the page increases such as for Contact Forms, Registration Forms and Search Results pages you can expand upon the fields. If you include the above fields as your base then you can inherit them all the way down the line knowing that code set up once will work across the board.