The Uniweb Platform
One platform. Every site your institution needs.
Uniweb powers institutional websites, faculty self-service sites, expert directories, and research portals — all from a single managed platform. Built for universities, research institutions, and complex organizations.
What is Uniweb
A modern web platform for institutions that manage complex, multi-site web presences.
Universities, research institutions, and large organizations typically manage dozens — sometimes hundreds — of websites: the institutional homepage, faculty and department sites, lab pages, research centers, administrative units. Most run on aging CMS installations that require constant maintenance and can't share content across sites.
Uniweb takes a different approach. It separates content from code completely, so your web team defines the structure and your content authors maintain the sites — independently, without stepping on each other's work. One platform serves every site in your institution, with shared or independent content as needed.
We call this a Component Content System — an evolution of the traditional CMS built specifically for organizations that manage many sites, many content owners, and many audiences from a single platform. Institutions get Uniweb through Proximify, which provides cloud hosting, SSO integration, SLA-backed support, and deployment management. The underlying framework is open source.
Two audiences. One platform.
Uniweb serves two audiences that use the same architecture but experience it very differently. Understanding both is key to planning an institutional deployment.
Institutional Websites
Your web team builds foundations — React components, layouts, semantic theming, the design language. That's the code behind your main site, faculty sites, department sites. Content authors maintain pages through the Uniweb App within the guardrails IT defines.
- Web/IT team — Builds foundations, components, templates
- Content authors — Maintains pages via visual editor
- Proximify — Manages hosting, security, infrastructure
Uniweb for Academia
Individual faculty and researchers create their own web presence — personal sites, lab sites, research portfolios — using templates and the visual editor. They pick a template, replace sample content with their own, and have a working site. No coding, no IT ticket.
- Faculty & researchers — Create and maintain their own sites
- IT team — Publishes foundations and templates
- Platform — Aggregates data into directories and portals
How They Connect
The institutional web presence and the academic platform aren't separate products. They're layers of the same system.
Each site gets its own foundation
Every site in Uniweb has a foundation — the curated set of building blocks that content authors work with. A university's web presence is typically a main site plus many sub-sites — the library, the school of engineering, the graduate studies office — each mounted at a path or subdomain, each with its own foundation tailored to its content needs. The institutional homepage has building blocks designed for institutional communication. The engineering school has different ones. A chemistry lab site has others still. The web team decides the structure and builds the foundations; content authors work within their site using the tools designed for their context.
Different sites, shared content
What connects these sites isn't shared components — it's a shared content layer. When a researcher adds a publication, it can appear on their personal site, their department's research page, the institutional research portal, and the expert directory — even though each of those sites uses a completely different foundation with a completely different look and completely different authoring tools. The data is the same. The presentation is independent. This is what traditional CMS platforms can't do: they either force everything into one template or silo content into separate installations.
Templates as the bridge
For faculty self-service, templates bridge the web team's world and the academic's world. A template pairs a foundation with sample content — a fully working site that demonstrates what the foundation can do. Research Lab, Faculty Profile, Course Website, Creative Arts Portfolio — each is a real site with real pages, not a wireframe. A professor picks a template, sees a working site instantly, and starts replacing sample content with their own. Every section can be removed, reordered, replaced, or added to. The template is a starting point, not a cage.
Individual effort, institutional value
The institution gets a directory of every site created by its people — what research groups exist, what labs are active, what projects are underway. This directory can be internal or public. When made public through Uniweb's research portal, it becomes a showcase with live previews, search by research area, and browsable categories. Faculty built these sites for their own purposes, using foundations suited to their discipline. The platform aggregates them into institutional value — without extra work from either side.
How It Works
Clear separation of responsibilities. That's the whole idea.
IT builds the components and defines the structure. Content authors maintain the sites. Proximify manages the infrastructure. Nobody steps on anyone else's work.
IT builds
Your developers create components, templates, and page layouts using the open-source Uniweb Framework. Modern tooling. Full creative control. No vendor lock-in.
- Custom components & templates
- Institutional branding & structure
- Permissions & content rules
- Integrations with existing systems
Authors publish
Faculty, communications staff, and department administrators create and maintain content using a visual editor — web or desktop. No coding. No IT tickets. Content stays current because the people closest to it control it.
- Visual drag-and-drop editing
- Web and desktop app
- Works within IT-defined guardrails
- Multilingual content management
Proximify manages
Hosting, security, updates, backups, monitoring, and SLA — handled for you. Your IT team focuses on building great sites, not managing servers.
- Cloud hosting & edge delivery
- SSO / SAML integration
- Uptime SLA: 99.9%
- Security, backups, monitoring
Take all of it. Or start with what you need.
Every institution is different. Some need the full platform — institutional sites, faculty websites, expert directories, and research portals. Others start with one capability and expand. Uniweb is modular. The architecture is the same underneath.
Institutional WebsitesFaculty WebsitesExpert DirectoryResearch Portal
Diego Macrini
Building University Websites with Uniweb
A complete multi-site project — from architecture to deployment
Diego Macrini
Published by Proximify
For Technical Leaders
The complete guide to the Component Content Architecture.
Using a fictional university as a case study, this book builds a complete, production-quality multi-site web presence from scratch. It covers the architecture that separates content from code, lets one foundation serve dozens of sites, and keeps everything maintainable for years — not months.
For developers and technical leads building websites for universities, research institutions, hospitals, government agencies, and any organization where multiple stakeholders share a web presence.
- Institutional homepage with dynamic faculty data, news, and events
- Semantic theming — distinct visual identities from a single configuration file
- Faculty sub-sites sharing one foundation with zero code duplication
- Bilingual support that survives content reorganization
- Full companion project on GitHub
The Uniweb ecosystem
Uniweb Framework
Open-source Component Content Architecture. Developers build foundations, components, and templates with React and modern tooling.
Uniweb App
Visual content editor for web and desktop. Content authors create and maintain pages without coding. Available as a web app and a Tauri desktop app.
Proximify
Managed deployment for institutions. Cloud hosting, SSO integration, SLA-backed support, security, and infrastructure — so IT focuses on building, not managing servers.
If your institution manages a complex web presence, talk to us.
We'll show you how Uniweb works with your organizational structure — faculties, departments, centers, labs, and people.
