Content strategy

The One Stop website is one of many UMN systems, tools, and sites used by students, each for different needs. One Stop website content should not duplicate, supersede, or contradict these other essential resources according to their intended purpose in the student user journey.

The One Stop website’s purpose in the UMN content ecosystem:

• Provides objective, publicly available information for students

• Focuses on information and instruction regarding University student business including finances, student records, and registration

• Aligns with the strategy and content delivery methods in MyU due to the student user journey between One Stop and MyU

The One Stop websites have a clean, simple visual design focused on presenting objective information. The visual style supports finding and comprehending information easily. It avoids elements or features that distract users from their task.

The One Stop websites follow guidance provided by University Relations regarding UMN web and brand standards (colors, fonts, headers, footers, spacing, layout, etc.).

All One Stop websites use the Folwell Design System to deliver an accessible user experience and support use on desktop and mobile devices. The sites use the Folwell styling through its content types, components, footers, and any custom pages or views including tables and filters shall adopt the Folwell styling.

If a design pattern is not available for a required feature, all custom development will endeavor to match the UMN pattern library and be consistent with the style, look, and feel of the One Stop sites.

High-level user requirements:

• Content is easy to find (through organic search, in-site search, site menu navigation)

• Content is easy to read and understand in plain language (Plain Writing Act of 2010)

• The website is accessible

• Specific contact information is included (when it is not or is not One Stop)

• Content and links are accurate and up to date

• Site is accessible using desktop and mobile devices

Before you start writing any content, identify the specific user need(s) that the content needs to meet. Start by filling out the page table template or updating the existing one (Google Drive). Make sure to meet the high-level user requirements as you develop the content.

High-level content requirements:

• Every piece of content meets a clearly defined user need with acceptance criteria that aligns with the core strategy statement

  • Documented in a page table

  • Exceptions include legally required information such as terms and conditions, consumer information, or student data and privacy information

    • Legally required information should be formatted and structured to meet user needs when possible.

• Content is structured logically or in a hierarchy

  • Break content into chunks

  • Put the most important information first (based on user needs)

  • Use headers and subheaders in chronological order (H1, H2, H3, and so on) front-loaded with keywords

  • Content follows a logical flow according to user needs/user mental model

• Content follows the One Stop website style guide

The content on the One Stop websites is for today’s specific user needs. Do not use the Drupal content management system to maintain or store source-of-truth information for the long term.

All site pages/content should have a review, deletion, or archival schedule articulated when content requirements were documented.

Content should be deleted or archived from the One Stop websites when:

• It does not meet a valid user need

• It is no longer true or accurate

• It is out of date

• It is no longer relevant or appropriate for the site audience

• It would be more appropriately published elsewhere

• It is currently published elsewhere

Each campus (specifically the content writer in collaboration with the One Stop Council board member and/or subject matter experts) is responsible to delete or archive content for their campus’ site. Establish a regular cadence to review content based on the user and business needs.

Should you delete or archive?

There is no one answer when it comes to deleting or archiving information. It depends on the circumstance—who needs what and when?

The following questions can help you determine what to do:

• Who needs access to the information in the future?

• For how long do you need to keep the information?

• Is there a legitimate legal requirement or compliance reason to keep the information?

• Is the information already stored permanently as a source of truth somewhere else (i.e. PeopleSoft)?

• Does archived information need to be publicly accessible or only for an internal audience?

• Who is responsible or owns the archived information?

• How can or should the archived information be retrieved if needed?

Suggestions for how to archive information

Export a webpage as a PDF to save to:

• Google Drive

• An asset server or shared drive

• University Digital Conservatory

• Other similar data storage location