Building a Sitecore Base Page Template


Sitecore is a Web Content Management system on the C# Microsoft .Net framework. If you’re not familiar with it then this posts isn’t going to make much sense to you.  I’m playing around with the it for fun and thought I’d throw out there what your basic page template should look like from both a C# and Sitecore point of view .

If something in Sitecore has a Layout(.aspx) then it’s almost always a Page. I say almost always because I’ve played around with using a page to stream a resource as a lazy mans http handler but I didn’t roll that to a production site and later rewrote it to be use a HTTP Handler.

Pages all have some basic things so why not build a base page template and a base C# Class to support these functions.

Video Demo

I’ll give some guidance on how to implement it, feel free to give your own thoughts and throw out some things I could be missing in the comments.

Title : Every Page has a title. This is the text that shows up in the top of the browser window.

Description : At a minimum you want this for SEO. It’ll show up as the text next to your link in a search engine if gets indexed. Maybe your page will get indexed, maybe it won’t, but leave that up to the business and content authors to decide and make sure you have code in there to support it.  A lot of navigation controls have items next to them with some short description text. So you can use this in some of your own display modules.

Keywords: Another thing you want for SEO but it may also come in handy if you want to some day implement search within your site.

Show in Navigation : At some point you’re going to build out navigation objects and you are going to want to check to see if the item should be shown in the menu. Rather than code against template types you can just check to see if the item inherits the ‘Page’ template and check to see if this option is checked.

Navigation Image : This can be used to display an image that represents the page as part of some type of navigation area. Might need a large and a small depending on requirements but if you have none I say it’s worth it to put something in at 30 by 30.

CSS and Javascript Files: In an ideal solution you have code with CSS and Javascript that stays on the server that belongs to the programmers and you have seperate CSS and JS script files that belong to the Content Authors that is seperate from the developers code.  If you can store this in sitecore you can deploy these objects without needing to push code to a server. In some enviornments that takes time. You wouldn’t believe how many times someone in marketing tells me they got a javascript api they’d like to implement on some pages today and they can’t wait for a release so they are pasting a ton of javascript into a html field.  This will give them a place to put the javascript that they can reuse without waiting for a build. I’d like CSS in there because I think a talented author could do a lot with it.

Read more of this post

Advertisements

Accelerate Content Delivery with a CDN


Life is too short to wait for pages, images and other content to download.  A Content Delivery Network exists for the sole purpose of maximizing the speed in which you can deliver content to as large an audience as possible. If you’re delivering content across the country or world you need to familiarize yourself with CDN’s.

Read more of this post