There have been some updates to the template since their first release. Depending on when the templates were downloaded some changes may be required. For information on these changes refer to the Template Updates page.
In addition to changes to the template code many changes have been made to the associated style sheets. As long as the style sheets are referenced at their original location, no modifications to the template code is necessary for style sheet changes.
The Unit/Organization link is in place to associate a page with it's sponsoring department. This link is not necessary on the departmental or organizational homepage, but it is recommended on all other pages within the site.
The Missouri State template itself is XHTML 1.0 strict compliant. Ensuring that the content inserted into the template complies with XML, HTML and CSS standards will eliminate many issues that might arise during the development process; however, it is not required.
The new template has shifted away from utilizing global navigation. Instead the link bar should point only to pages which are relevant to that particular page. Visitors can use the breadcrumb links to navigate back through the site if needed.
The absolute path to the global and campus style sheets are as follows:
It is strongly recommended that developers not save these style sheets locally. Referring to these pages using the path above will allow for centralized updates to the style sheets.
The Missouri State web templates include the necessary accessibility markup for the template's content and layout. It is important to note that all content inserted into the template also needs to be accessible. For more information on making web pages accessible refer to the Web Access Compliance Team web site.
Web Press is a Web Content Management System offered to units in the Missouri State University system.
Most WYSIWYG web page editors can make changes to the template. WYSIWYG editors will work; however, caution should be taken during the developing process as the following problems can arise:
It is strongly recommended that developers not save the global and campus style sheets locally to their site. Referring to original path will allow for centralized updates to the style sheets.
If a customized style sheet is required, add the link to the customized local style sheet in the code below the other style sheets. Placing it last will cause the custom style sheet to override the global and campus style sheets when any conflicts occur.
Most WYSIWYG web page editors have trouble rendering cascading style sheet content. To preview what your site will look like, you must preview it in a browser.
The most frequent cause for a section of the template wrapping or being pushed down when content is too large for an area. The second most likely cause is accidentally assigning fixed widths to the containers.
The template layout consists of 4 columns, each one 179 pixels wide with a 10 pixel gutter between columns. The various versions and sections of the template are created by merging one or more of those columns to create different layout effects.
Removing a <DIV> tag or other critical element of the template is one of the most common errors that breaks the template. Text editing in a WYSIWYG can place content in the wrong container or delete critical code. If you are experiencing issues with the template, ensure that each section of the template is still present and in the correct order. If you are unable to determine the cause of the error, it is often best to copy the page contents into a fresh copy of the template.