Web Content

Ideally the content on a site should be updated at least once a week. While it may not be possible to create new articles or images every week, there are ways to achieve this goal outlined below. If these techniques cannot be used then it is important to review content at least monthly to ensure that: all links are still working; content doesn’t appear to be out-of-date; and date specific events are clearly understandable to the reader.

Creating a website for an annual special event has unique opportunities. An annual event website requires special attention after the event to ensure the reader knows that the event has already occurred. If the event truly recurs annually, then proper maintenance of the site can help increase attendance for the future events.

Prior to the event:

• Be sure that you’re building the site with content that clearly shows that the event is in the future. Add the year into the copy so that the reader is sure that they aren’t reading a stale site. For example you might say, “The 2023 Science Everywhere” instead of “This year’s Science Everywhere.”
• If you are using images from previous years, it may look dated because of the season, or some other identifying element. Therefore, be sure to identify the timing of the image in the caption, i.e. “Transforming liquid into gas was a show stopper at the 2019 Science Everywhere festival.”

After the event:

• This is when the real work pays off. Go through the site and remove anything that was projecting forward in time for the event. Even the tense in verbs can cause the reader to wonder if the event has already occurred or is upcoming.
• Take out content that is specific to the past event.
• Update the introduction and invite the reader to the next year’s event. Give a date of the event if possible even if it is tentative (and say so).
• Thank sponsors but be clear which year’s event they sponsored (also a great time to start reaching out to new sponsors for the upcoming event.)
• Update contact information.
• Remove any links to outside sites that may no longer apply or that you suspect may become broken.
• If you want to show a recap of the event via video or an article be clear that you’re speaking of a past event. Recap the event within one month following the date of the event, unless there is a unique news angle or novelty related to the timing of the recap.

Year-round websites for ongoing events don’t require the concerted post-event clean up that an annual event requires. But year-round sites can make taking the time to review the site harder to schedule.

Look for ways to add new content near the top of the page near the “front” of the site as easily as possible.

Tips for this include:

• Republishing content you’re already creating for another distribution method.
• Put in a newsfeed from an outside source, or another one of your sites, to automatically post content.
• Add images showing events or changes in the office if you don’t have time to write articles.
• Publish a feed from your social media channels.

Whether you do this or not you should review your site once a month to ensure it isn’t looking stale to the reader.

Key things to look for here are:

• Images that “look” out of season. Don’t show winter scenes on your homepage when it is July. Outdated images communicate to the reader that you haven’t updated the images, and often makes them wonder if the content is no longer accurate too.
• Watch for events that don’t show the year. An article that gives the date of an event as March 15th is confusing when someone is reading the site in October. They wonder if this is a story about the upcoming event or last year’s event.
• Links that are broken because content has moved.
• Key personnel that are referenced but are no longer on staff. These can be edited to say “former director” or you can use the opportunity to get a new quote from an existing staff member.
• Test forms to ensure that they are still working and the recipients are handling them properly.
• Key responsibilities have not changed. If your department is no longer monitoring the parking lot then update that story to help the reader know who is now responsible.
• Redirect any pages that you have to remove or change their URL. Many times other sites will build what is called a Backlink into your site if they find content that they feel their readers would be interested in. If you remove a page with one of these Backlinks then when their reader tries to visit your site they get a “page not found” error. It would be a better user experience if they were automatically redirected to a similar page or to your homepage so that they could find more content from you. You do this through a 301 redirect.
• Style changes that haven’t been kept up. Has the organization changed brand style and your site no longer looks like the rest of the University? Have trends changed and the way your site is styled looks dated and gives the impression to the reader that no one is working on the site? Has technology changed and you’re still using tools and techniques that don’t reflect the current capabilities?

Navigation on websites and other electronic communications should be styled in all upper case Sofia Pro with Arial as a substitute. (font-family: Sofia Pro, Arial, sans-serif;)

Sidebar headings and sub-headings should utilize Sofia Pro. All other text and/or navigation elements in a sidebar should be displayed in the Sofia Pro in appropriate case, with Arial as a secondary option: (font-family: Sofia Pro, Arial, sans-serif;)

Body copy on websites and other electronic communications should be styled in the san-serif font Sofia Pro with Arial as a substitute option. In most instances, body copy should be set as flush left. Font size for the content part of a web page is set at .75em in the UNCG global styles which will make content copy sized at 75 percent of the visitor’s default browser font size. The content copy line spacing (or line-height in CSS terminology) should be 1.7.

• font-family: Sofia Pro, Arial, sans-serif;
• font-size: .75em;
• line-height: 1.7

In most cases, when web developers use the UNCG web assets including the global style sheet, body font styling should default to the above CSS. In situations where it is not possible to directly use the UNCG web assets, developers should approximate this font styling as closely as possible.

Readers may have difficulty when text, images, and the background color are too close together in the color spectrum. The measure of this variation is contrast ratio. A good example of this is that you would not want to put navy blue text on a black background because there is not enough contrast ratio to allow good separation between the text and the background. It is best practice to ensure that text and backgrounds have a contrast ratio of 4.5:1 and there are tools on the web to help determine the contrast ratio.

Accessibility tests can be performed using tools such as webaim.org/wave.

Abbreviations on web pages can help convey a message quickly and efficiently. 

However, they can also be confusing, especially for first-time visitors who may not be familiar with your program. Additionally, abbreviations can cause confusion for visitors who have different accessibility needs and may be using adaptive technology. 

In consultation with Accessibility Resources at UNCG, the following guidelines should be followed to ensure online content is available to all users:

• Organizations, departments, programs, etc. should be spelled out on first reference. For example, the College of Arts and Sciences should be spelled out on first reference, and then CAS can be used on subsequent references if necessary. 
• Avoid less common techniques such as adding periods between letters or spelling phonetically, as these are not the generally accepted style and will probably be more confusing than helpful. 
• Keep your audience in mind. If there is a chance for confusion, take the time to provide clarification within the sentence or paragraph. Make sure to consider adaptive technology and test with screen readers and braille readers if possible. 

The copyright in the footer of the webpage should be kept current to reflect the current year. This helps the reader know that the page has been updated and kept current.