Utah Valley University

Story op1 Story op2
Category Index News Students Community Resources Innovation
Schools Index

school layout(s)

CHSS (school layout) CET (school layout)

area layout(s)

CHSS (area layout) CET (area layout)
Guide Index Architecture (master guide) Academic Taxonomy (guide)

guides

Home (guide) Category (guide) Story (guide) School (guide) School (area guide)

intake forms

Home (intake form) Category (intake form) Story (intake form)

Category Page Guide

This guide defines the purpose, required content, organization rules, and page structure for category pages used across News, Students, Community, Resources, and Innovation.

Guide Purpose

Use this page to keep category pages consistent, scalable, easy to browse, and aligned with future story system needs.

1. Overview

A category page should do more than display stories. It should define what belongs in the category, provide a clear entry point for browsing, surface the strongest current story, and help users move into related topics, archives, and adjacent categories.

Category Overview
Category Primary Purpose Main Story Focus Typical Audience Suggested Tone
News Broad campus updates and timely developments Research, planning, academics, leadership, campus-wide updates All campus audiences Clear, timely, informative
Students Student-centered stories and experiences Achievement, support, involvement, wellness, opportunity Current and prospective students Human, supportive, encouraging
Community Regional connection and public engagement Outreach, service, arts, partnerships, public events Community members, families, partners Welcoming, civic, outward-facing
Resources Helpful and service-oriented content Guides, support tools, service updates, how-to content Students, families, support seekers Practical, direct, helpful
Innovation Applied ideas and forward-looking work Projects, startups, experiments, creative technology, solutions Students, faculty, partners, industry Progressive, active, solution-focused

2. Required Page Sections

Each category page should share the same overall layout so users can move between categories without relearning the page structure.

Required Category Page Sections
Section Required Purpose What It Should Include
Hero / Intro Area Yes Define the category and orient the user Category label, page title, short summary, update details or story count
Featured Story Card Yes Highlight the most important or representative story 16:9 image, label, title, summary, CTA
Browse Topics Sidebar Yes Support topic-level navigation Sub-categories, tags, archive links, related categories
Latest Stories Grid Yes Show current supporting stories Minimum four cards with sub-category, title, summary, link
Category Spotlight Recommended Support a secondary feature or theme Image, title, summary, primary CTA, optional secondary CTA
Archive Section Yes Support deeper browsing Older story links with short descriptions
Pagination Yes Navigate longer content collections Previous, current, next, page numbers

3. Required Content Fields

These are the core fields needed to create, maintain, and scale a category page within a larger story system.

Required Content Fields
Field Required Description Notes
Category Name Yes Top-level category label News, Students, Community, Resources, Innovation
Category Title Yes Main page heading in the hero May be more descriptive than the category name
Category Summary Yes Short statement of what belongs in the category Use one concise paragraph
Featured Story Yes Main highlighted story for the page Should feel timely, strong, or representative
Sub-Categories Yes Editorial groupings within the category Used in story labels and browse topics
Tags Yes Reusable cross-linking terms Should support filtering and related content
Latest Stories Yes Newest or most relevant supporting stories Minimum four items
Archive Links Yes Older story access Link text should remain descriptive
Update Date Recommended Freshness indicator for the page Supports trust and maintenance
Story Count Optional Estimated number of stories in the category Useful for browsing context

4. Content Length Rules

These ranges help maintain visual consistency across cards, spotlights, topic labels, and supporting story modules.

Content Length Guide
Field Ideal Working Target Hard Max
Main Category Tab 1 word 4–12 characters 14 characters
Sub-Category Label 1–2 words 12–24 characters 30 characters
Feature Title 5–8 words 35–55 characters 68 characters
Feature Text 14–22 words 100–140 characters 170 characters
Supporting Title 4–7 words 30–45 characters 58 characters
Supporting Text 12–18 words 85–115 characters 135 characters
Tag 1–2 words 8–14 characters 20 characters
Tags per Story 3–4 tags 3–4 tags 4 tags

5. Category Structure and Taxonomy

Categories provide the top-level editorial buckets. Sub-categories define the story lanes inside each bucket. Tags connect related stories across the entire system.

Category and Sub-Category Map
Category Suggested Sub-Categories Best Use
News Research Updates, Campus Planning, Academic Growth, Leadership News, Institutional Updates Timely campus-wide updates and general stories
Students Student Life, Student Achievement, Wellness Support, Career Development, Student Voices Student-centered stories and lived experiences
Community Education Outreach, Arts and Culture, Service Projects, Civic Engagement, Community Partnerships Regional impact, outreach, and public-facing work
Resources Academic Support, Financial Support, Technology Help, Accessibility Services, Advising Resources Helpful support content and service navigation
Innovation Assistive Design, Startup Support, Creative Technology, Health Training, Applied Research Forward-looking ideas, experimentation, and solutions
Tag Taxonomy Guide
Tag Type Purpose Examples Use Rule
Topic Tags Describe the main subject of the story Research, Scholarships, Mentorship, Outreach, Startups Use 1–2 per story
Audience Tags Show who the story matters to most Students, Families, Faculty, Community Use when audience clarity adds value
Department Tags Connect to units, schools, or offices Library, Engineering, Student Affairs, Business Use sparingly
Impact Tags Show why the story matters Student Success, Career Prep, Community Impact, Campus Life Use 1 when helpful
Event Tags Connect stories to recurring programs or events Service Week, Lecture Series, Internship Fair Use only when event-specific

6. Image and Media Standards

Media should be simple, consistent, and reusable across feature areas, spotlight modules, and video-based content.

Image Standards
Image Type Standard Ratio Recommended Use Notes
Banner Image 16:9 Featured stories, spotlights, hero support Use a clear focal point that remains readable when cropped responsively
Video Thumbnail 16:9 Video previews, media cards, featured video content Use strong contrast and simple composition for overlays or play icons

8. Category Page Checklist

Use this checklist before publishing or reviewing a category page.

Category Page Review Checklist
Check Required Review Notes
Category title and summary are clear Yes Defines what belongs in the category in plain language
Featured story matches category purpose Yes Should feel representative, useful, and current
Sub-categories are accurate and stable Yes Avoid unnecessary one-off labels
Latest stories follow content length limits Yes Check title, summary, and tag ranges
Tags are reusable and not redundant Yes Do not repeat the same meaning with multiple tags
Images use 16:9 ratio Yes Confirm crop, subject clarity, and alt text
Archive links remain descriptive Yes Avoid vague or repetitive link text
Page supports browsing and discovery Yes Topics, tags, archive, and related categories should help exploration

9. Summary

Category pages should balance editorial clarity, browsing utility, and system consistency. They should help users understand what belongs in each category, discover related stories, and move confidently through current, supporting, and archived content.

  • Define the category clearly
  • Use consistent sub-categories
  • Keep titles and summaries within length targets
  • Use reusable tags for cross-linking
  • Maintain 16:9 media standards
  • Support both scanning and deeper browsing