<rss version="2.0"><channel><title>Carnegie Mellon University CMS News</title><link>http://www.cmu.edu/cms/</link><description>Latest News About the University Templates and CMS.</description><item><title>New Guidelines for Launching Sites</title><link>http://www.cmu.edu/cms//cms-news/guidelines-for-launch.html</link><description><![CDATA[<p>The first time you wish to "go live" with your site, please <a href="http://www.cmu.edu/cms//using-cms/site-launch.html" title="launch guidelines">follow our guidelines</a> and <a href="mailto:cms-help@andrew.cmu.edu" title="CMS Help Center">contact the CMS team</a> at least <strong>one week</strong> prior to launch.&#160; This will give us time to finalize the technical details of the launch and review your site for adherence to best practices for both Carnegie Mellon's CMS and the web in general, and will make suggestions to help you align your site with these best practices if necessary.</p>]]></description><pubDate>Tue, 16 Mar 2010 05:00:00 GMT</pubDate></item><item><title>Update on CMS Evaluation Project</title><link>http://www.cmu.edu/cms//cms-news/update-on-cms-evaluation-project.html</link><description><![CDATA[Colleagues,<br/>
<br/>
In June 2011, I shared early plans to evaluate new web content management tools. I&#8217;d like to provide an update on this work.<br/>
<br/>
Our first step has been to carefully profile our existing implementation of the Cascade CMS. The objectives of this evaluation are to:<br/>
<br/>
&#183;&#160;&#160;&#160;&#160;&#160;&#160; Ensure that we thoroughly understand how people use the system today.<br/>
&#183;&#160;&#160;&#160;&#160;&#160;&#160; Identify needs which are not being met by the current CMS implementation.<br/>
&#183;&#160;&#160;&#160;&#160;&#160;&#160; Determine whether the existing technology can be extended, upgraded or modified to meet these needs, or if a replacement is necessary.<br/>
<br/>
We wanted to give you an update on our search for a new CMS platform.&#160; Our first step has been to carefully profile our existing deployment of Cascade, in part to ensure that we deeply understand how people use the system today and also to be certain that the existing technology cannot be extended (rather than replaced) to meet our needs.&#160; We're planning to conclude this phase of the effort by the end of the 2011is calendar year.&#160; From there, we will be able to provide a more clear roadmap of ourshare a plan for next steps.<br/>
<br/>
As this effort has developed, we realize that we cannot continue the moratorium we imposed on new sites in the CMS.&#160; At the same time, as our service is currently structured, we have (far) more work than we have people to attend to it.&#160; Effective immediately we are lifting the moratorium.&#160; Note that we still request that you publish outside normal working hours whenever possible.<br/>
<br/>
However, in the near future we will be implementing additional processes to streamline our CMS work so we can more effectively meet the needs of the campus community.&#160; In general we will be adding more structure to our engagement process so that we can maintain consistent response times to client requests.&#160;&#160; We'll update you with these changes as they become better defined.<br/>
<br/>
Thanks for your patience as we work through these issues. As always, we welcome your&#160; questions and comments.<br/>
<br/>
Thanks,<br/>
<br/>
Doug Blair<br/>
<br/>
Assistant Director, Computing Services]]></description><pubDate>Fri, 23 Sep 2011 05:00:00 GMT</pubDate></item><item><title>Search for a New CMS Platform Underway</title><link>http://www.cmu.edu/cms//cms-news/search-for-new-cms.html</link><description><![CDATA[The CMS service has grown dramatically in the four years since it was launched.&#160; Today over 600 users are managing over 30,000 pages of content that represent much of the university's official web presence.&#160; In response to both this growth and the need to improve the university's overall web presence, Computing Services is beginning a search for new web content management tools. You will be hearing more about this project in coming months, but there are a few things we wanted to bring to your attention right away.<br/>
<br/>
<h3>1. MORATORIUM ON NEW SITES</h3>
Effective June 1st we will be placing a moratorium on creating new sites in the CMS.&#160; We will also be advising existing clients to postpone any major work on existing sites.<br/>
<br/>
<h3>2. MIGRATION OF EXISTING SITES</h3>
Migration of existing sites to new technologies will be a key criterion in our evaluation process.&#160; We will work out the specifics of this in the implementation plan and share details with you as they become available.<br/>
<h3><br/>
3. RESPONSE TIME</h3>
As our staff begins to spend time gathering requirements for the new system, you may notice a delay in their response time for routine requests.&#160; Please use the following guidelines to set your expectations:<br/>
- 1 week for routine questions<br/>
- 2 weeks for site reviews and site launches<br/>
<br/>
<h3>4. YOUR INPUT</h3>
Rigorous and thoughtful requirements gathering and analysis will be critical to selecting technologies that best meet our needs.&#160; While we can gather much of this information by studying the CMS from our side, we are very interested in your feedback.&#160; Please send your questions, comments, and suggestions to <a href="mailto:cms-feedback@andrew.cmu.edu" target="_blank" title="Mail to CMS Feedback">cms-feedback@andrew.cmu.edu</a><br/>
<br/>
We're excited about this project, and hope you are as well.&#160; We'll be in touch soon and often with more details as we flesh out our project plan.<br/>
<br/>]]></description><pubDate>Wed, 01 Jun 2011 05:00:00 GMT</pubDate></item><item><title>New Publishing Guidelines</title><link>http://www.cmu.edu/cms//cms-news/new-publishing-guidelines.html</link><description><![CDATA[Many of you have contacted us about performance problems with the CMS.&#160; We're painfully aware of this issue.&#160; While performance has been a slowly growing concern for some time, we seem to have passed some threshold and are now seeing serious problems on a regular basis.&#160; We're working on a variety of engineering solutions, some developed locally and others in conjunction with the vendor.&#160; We realize that the service has become a critical tool for the community (with roughly 600 users and over 250 sites), and are treating this problem with the priority it deserves. While we work on the problem, our investigations to date have turned up one thing you can do to help: 
<h2>Please avoid publishing during business hours.&#160;</h2>
<p>We can't emphasize this point strongly enough.&#160; If you must publish, please be selective in the folders/files that you publish.&#160; Publishing an entire folder for a change to a single page is inefficient and hurts system performance.&#160; When the system is only being used for editing, it remains usable (albeit sometimes slow); it is the publishing of sites that pushes the load from sluggish to glacial. &#160;<br/>
<br/>
We'll update you as we make progress on this issue.&#160; Questions and comments welcome. &#160;<br/>
<br/>
Thanks for your cooperation and patience.</p>]]></description><pubDate>Tue, 15 Feb 2011 06:00:00 GMT</pubDate></item><item><title>Switching Page Types in Version 4</title><link>http://www.cmu.edu/cms//cms-news/v4-condition.html</link><description><![CDATA[<p>If you need to change the Content Type of an existing page, be sure that you hit SUBMIT before you populate the page. Otherwise you may lose your content. For example, if you switch a page from a 2-column to a 3-column, or from a 3-column to an expand-collapse, do not start populating specific fields until you hit SUBMIT.</p>
<p>To change the type of page you have, go to Edit&amp;gt; System and click on <strong>Content Type</strong>. Select the new content type and hit CONFIRM. It is important that you then hit SUBMIT before you begin entering content.</p>]]></description><pubDate>Mon, 15 Nov 2010 06:00:00 GMT</pubDate></item><item><title>Best Practices for Links</title><link>http://www.cmu.edu/cms//cms-news/links.html</link><description><![CDATA[<p>Effective links are well labeled (verbally), well positioned (visually), and match the users' expectations (behaviorally.)</p>
<h2>When to open links in a new window<br/>
</h2>
<p>Links to Carnegie Mellon sites should open in the same window. Non-Carnegie Mellon sites should open in a new window.</p>
<h2>Links that open documents or launch applications</h2>
<p>Documents, such as PDFs and MOVs, should open in a new window and be labeled [.pdf] or [.mov] in the link, for example:<br/>
<br/>
<a href="http://www.cmu.edu/cms//cms-news/links.html" title="links">Watch Professor Smith&#8217;s lecture [.mov]</a></p>
<h2>Language to use for labeling</h2>
<p>Links should be relevant text. Do not link words like "click here," "this page," etc. Search engines will not be looking for the word "here"; they will be searching for the words in the subject. For example:<br/>
<br/>
For more audio and video, see our <a href="http://www.cmu.edu/cms//cms-news/links.html" title="links">multimedia archive</a>.&#160; <strong>Correct</strong><br/>
<br/>
See the multimedia archive <a href="http://www.cmu.edu/cms//cms-news/links.html" title="links">here</a>.&#160; <strong>Incorrect</strong></p>]]></description><pubDate>Mon, 29 Mar 2010 05:00:00 GMT</pubDate></item><item><title>Tips on Moving and Renaming Files</title><link>http://www.cmu.edu/cms//cms-news/moving-files.html</link><description><![CDATA[When moving or renaming a published page, file, or folder in the CMS, it is important to unpublish it first. The CMS does not automatically unpublish assets when they are moved, which results in&#160; the content at the original URL remaining on the web indefinitely. When that happens, The content becomes "orphaned" and is no longer manageable from within the CMS. This can lead to problems such as stale content being returned in search engine results. 
<h2>How to Unpublish a File<br/>
</h2>
1. With the folder, file or page open in the CMS, select the <strong>Publish</strong> tab.<br/>
2. On the <strong>Publish</strong> tab, select the destination(s) that the asset has been published to, and then select the <strong>Un-publish</strong> radio button.<br/>
3. Click <strong>Submit</strong>. 
<h2>Removing a Page from the Navigation</h2>
If you are moving a page or folder that is part of the navigation, you will need to <strong>republish the folder</strong> containing that asset so that the moved content no longer appears in that section of the navigation. 
<h2>Finding and Removing "Orphaned" Pages<br/>
</h2>
If your site is served on www.cmu.edu and you want to check to see if it contains any "orphaned" content, we have tools that can help with this. Please contact <a href="mailto:cms-help@andrew.cmu.edu" title="CMS Help Center">cms-help@andrew.cmu.edu</a> for more information.]]></description><pubDate>Wed, 10 Mar 2010 06:00:00 GMT</pubDate></item><item><title>Publishing Etiquette</title><link>http://www.cmu.edu/cms//cms-news/publishing-etiquette.html</link><description><![CDATA[Much like a shared printer, the publish queue is shared by everyone who uses the CMS and the publisher processes one job at a time, in the order received. Whether you are publishing your site to be viewed live or on the staging server, there are over 500 people who all have access to the same queue. <br/>
<br/>
<h2>Submit your Job Once, Then Check Your Place in Line</h2>
Once you submit a job to be published, it is wise to find your place in the line of jobs waiting to be published. Depending on traffic, it may take longer than you expect to see the published changes you make to your website. To check the publish queue, go to Tools &amp;gt;&amp;gt; Publisher &amp;gt;&amp;gt; Active Jobs. You will be able to watch the progress of all the jobs that are spooling through the publish queue.<br/>
<br/>
<h2>Publish large collections [100+ pages] after hours!</h2>
<br/>
Large collections of files should be published after hours (after 5:30 p.m. or before 6 a.m.). Large publish jobs may delay another user's time-sensitive publish job and can also put a load on the server and affect overall system performance. When possible, publish single pages or a smaller group of files.<br/>]]></description><pubDate>Thu, 04 Mar 2010 06:00:00 GMT</pubDate></item></channel></rss>
