A public site on your own address, created the day you sign up and edited by your own office. No developer to book, no hosting to arrange.
Inside the portal
Showing School website in the Inter-College portal.
A notice, a photo, an exam result — posted from the portal your staff already use, and on the public site straight after.
Home, About, Admissions and the rest each have their own set of fields — a hero, an intro, a card grid, a principal's message. Fill them in and the page is written. Custom pages take rich text, image-and-text, card grids, FAQs and calls to action.
The site is server-rendered and responsive, so a parent opening it on a phone gets a page that is already built rather than one that assembles itself in the browser.
The gallery, notices, events, blog, achievements, downloads, alumni and careers listings are all managed from the portal your office already signs in to. Nothing is typed twice.
The site carries a meta title and description, and so does every individual page — set by your office, not left to a default.
Three steps to a professional school website.
Signing up creates your school's site at your own address on inter-college.com, with its standard pages already there waiting for content.
Open Website → Pages in the portal and work down the fields for Home, About and Admissions. Upload your logo and photos, set your two brand colours, and add your contact details.
Post a notice, add an event, put up gallery photos or a blog piece. The public site picks it up — there is nobody to email and no developer to book.
There is a single school website design. You set your logo, your colours and your content; you do not choose between templates, and there is no board-specific or international-school variant.
The editor is a set of structured fields per page, not a canvas. You cannot move a section by dragging it, change fonts, or alter the layout.
Your site lives at your subdomain on inter-college.com. Pointing your own www address at it is not built — if you need it, tell us and we will discuss doing it by hand.
The admissions page describes your process; it does not collect applications. The site's contact form is a general enquiry form, and it does not feed the admissions pipeline in your portal automatically.
There is a field for a Google Analytics ID in your settings, but nothing on the public site reads it yet, so no traffic is being measured. Treat it as not wired up.
Messages sent through your site's contact form are read from the mobile app on a staff account. There is no inbox for them in the browser portal yet.
Sign up, fill in three pages, and share the address. No developer, no hosting bill.
Start Free Trial