Give sports fans one public portal where they can follow their teams and join the conversation.
This past digital experience project delivered a sports and fan portal for a media production company. We built it on SharePoint.
Para's internal portfolio describes a college football portal where fans could rate and comment on what they saw.
The case matters because it shows consumer and community digital experience. Our work is not limited to employee intranets or enterprise workflow portals.
Audience portals become communities when you design for participation from the start. One-way pages are not enough.
Why this matters
Sports and media experiences need more than a content catalog. Fans want to find their teams and react to what happens. They want to feel part of a shared community.
This project combined content publishing with social features. It gives Para proof of audience-facing experience design beyond corporate portals.
Using SharePoint here also shows that Para has adapted enterprise platforms for public community use when it made sense.
- Sports and college football content.
- A portal structure built around teams and fans.
- Ratings and comments.
- Social and community interaction patterns.
- Content publishing in a media setting.
- A public digital experience built on SharePoint.
Media & Sports Community Portal Pattern
Teams & Content
Fans / Audience
Ratings & Comments
Social Interaction
Publishing
Community Experience
What the work looks like
Organize content around the audience domain
Teams and fan interests shape the portal, not a corporate department structure.
The information model must support both published content and the community activity around it.
Add participation to the content experience
Ratings and comments let users react to content and teams instead of just reading.
Support publishing in a media context
Editorial teams need controlled content creation and publishing. Meanwhile, the public sees a simpler fan-facing interface.
Keeping publishing work apart from public use is a reusable digital experience pattern.
Para point of view
Community is a product behavior, not an image style
Letting fans take part changes what it takes to run a portal.
Content and interaction need a shared information model
Users need a clear link between each team and the conversations around it.
Publishing and moderation are separate jobs
Audience engagement needs governance on top of editorial content management.
What was delivered
Audience and content model
How teams, content, and fan activity fit together in the portal.
Portal information architecture
Navigation and discovery around sports and media content.
Participation features
Ratings and comments within the validated scope.
Publishing model
The editorial process for creating content and showing it to the audience.
Governance requirements
The moderation and ownership rules that community features need.
Experience roadmap
A phased path for public content and participation features.
Where it fits
This showcase adds media and audience-facing digital experience proof to Para's portal portfolio.
Digital Experience & Channels
A public portal where the audience takes part.
Content Collaboration & Portals
Publishing and portal architecture.
Customer Service / CX
Audience engagement and interaction patterns.
Modern Apps
A possible path forward when you need richer front-end experiences.
Explore related capabilities
Related advisory
- Digital Experience Advisory
- Information Architecture
- Enterprise Architecture & Roadmapping
Related solutions
Related platforms & assets
- Audience portal patterns
- Community-interaction patterns
- Content-publishing patterns
Need a public content experience that lets your audience take part instead of only read?
Talk to Para about your audience and how you want them to take part. The design can keep editorial publishing and fan activity apart, each with its own rules.