Is it something I install?
No. It is the content system behind websites we build with Astro. We host and maintain the CMS; your website is hosted where you choose.
eLan Central CMS is the content system behind the Astro websites we build. Editors update pages, posts, media and settings in one dashboard, then publish. The website is rebuilt as static files and uploaded to its own hosting, so visitors always get fast pages and never touch the CMS.
Product answer
No. It is the content system behind websites we build with Astro. We host and maintain the CMS; your website is hosted where you choose.
A website with a heavily bespoke content model or strict isolation needs can run on its own separate instance of the same system.
Publishing rebuilds only your website. Changes are usually live within a few minutes.
Privacy built into the product scope
A shared content platform holds several organisations’ content behind one login page, so access is limited by role and by website.
Each editor should sign in with their own account. Client editors are limited to their own website; creating or removing a website is restricted to eLan administrators.
Where form submissions are stored in the CMS, decide who may view and export them and how long they are kept.
Upload only files that are meant to be public. The website publishes what the CMS holds.
Analytics IDs, email and other integrations are enabled only when scoped, with their providers and data fields documented.
Scope note: The platform supports agreed access and publishing workflows. It does not by itself guarantee privacy or accessibility compliance; each organisation remains responsible for the content it publishes.
Key Features
eLan Central CMS is Payload CMS, customised by us. It manages the content of the Astro websites we build.
Each website has its own space inside one CMS. Our team can move between sites; a client editor sees only their own.
Pages are assembled from a shared block library: hero, rich text, services grid, feature list, gallery, testimonials, FAQ, stats, call to action, contact, logo strip, and map or embed.
Posts with categories, authors and SEO fields, for websites that publish articles.
Logo, contact details, social links, header and footer menus, default SEO and analytics IDs, managed for each website.
Title, meta description, canonical URL, Open Graph and structured data come from CMS fields. The sitemap and robots file are generated when the site is built.
Images and files are managed in the CMS, and alt text is required, which supports accessibility from the first upload.
Old-to-new URL redirects are managed in the CMS and written into the website when it is built.
Form submissions can be stored against the website they came from.
Products, doctors, projects, team members, testimonials and FAQs are switched on only for the websites that need them.
How publishing works
An editor updates content in the CMS.
One click on Publish starts a rebuild of that one website.
Astro builds the website as static files, using only that website’s content.
The files are uploaded to the website’s own hosting.
Visitors only ever load static pages from the website’s own hosting. If the CMS is offline, live websites keep working; only editing pauses.
Who It's For
Update pages, posts and images without asking a developer for each change.
Manage more than one website from the same dashboard.
The website is static files, so it runs on standard shared hosting. No Node.js is needed on the website’s server.
We plan content migrations so that existing URLs are kept.
Book a guided walkthrough with sample data and your own workflow in mind.
Technology
This is the stack of the current product build. Hosting and further integrations are agreed for each implementation.
FAQs
It is the content system behind the Astro websites we build. Editors update pages, posts, media and settings in one dashboard and publish. The website is then rebuilt as static files and uploaded to its own hosting.
Yes. It is Payload CMS, which is open source, customised by us with a shared block library, per-website spaces and editor roles. The database is PostgreSQL.
No. Visitors load static pages from your website’s own hosting. If the CMS is offline, the live website keeps working and only editing pauses.
Yes. Your editors get accounts limited to your website. They can update pages, posts, media and settings, then publish.
Any hosting that can serve static files, including standard shared hosting. No Node.js is needed on the website’s server.
Yes, as a scoped migration. We map your existing content to the CMS and plan the move so that existing URLs are kept.
Yes, on request. We walk you through the editor with sample content.
It is quoted as part of the website project. The written proposal states what is included and any recurring charges.
Explore More
A configurable property portal foundation with listings, agent dashboards, maps and lead capture, adapted to each client’s operating model.
Learn more →A configurable portal for medical conference registration, abstracts, speakers, schedules and certificates.
Learn more →A configurable member portal for medical associations, with memberships, events, documents and payments.
Learn more →A configurable operations portal for resorts and boutique stays, covering bookings and selected day-to-day workflows.
Learn more →A configurable project management system for agencies and service businesses, covering clients, projects, tasks, billing, enquiries and renewal reminders.
Learn more →A configurable management portal for insurance agencies, covering LIC, health, motor and general policies, deposits, renewals, commissions, sub-agents and customer records.
Learn more →