A university or college can have a website for every faculty, department, and programme. Each team wants to publish its own news, events, and course details, and the institution wants all of it to look and work the same way.
When every faculty builds its own site, the result is different layouts, different formats for the same information, and students who can't compare courses side by side.
Space for each faculty
In Visor, each faculty or department site has its own record, theme, and editors. Permissions keep each team inside its own sites, and editors switch between the sites they work on from the sidebar.
Shared building blocks
Developers build widgets and layouts once. Editors put pages together from those parts in Page Builder and preview them with the site's real theme before publishing. Every faculty gets the same tools, so pages stay consistent across the institution.
A clear path from draft to published
Each site can have its own approval workflow. A faculty editor drafts a page, a reviewer approves it, and it goes live when it is published. Every page shows where it stands, so nobody has to ask what is waiting for review.
Course pages students can compare
Programmes live in a collection with the same fields for every course: faculty, level, duration, entry requirements, and intake dates. Students filter courses by faculty, level, and intake in a course finder.
With Chocolate Factory, an AI assistant on the page can answer questions about a programme. It reads the institution's published pages through a read-only token, so it can't change anything.
What changes
Faculties keep control of their own content. Students find the same details in the same place on every course page, and the institution runs one platform for all of it.
