Imperial College of Nursing
Imperial College of Nursing is part of the same group as NDET. Instead of building and paying for a whole new site, we added it to the platform we'd already built, with its own look, content and domain.
- Client
- Imperial College of Nursing
- Live at
- imperialnursing.in
- What we did
- Web developmentUI/UX designSEO
2
colleges, one platform
1
admin panel for both
0
extra servers
1
codebase to maintain
The brief
What they came to us with
Imperial College of Nursing runs one program, a four-year B.Sc Nursing degree, from its campus in Jamuwadag, Khunti. It's affiliated to Ranchi University and run by the same group as NDET.
They needed their own website. Students searching for B.Sc Nursing should land on a page about Imperial, not a group page that lists four other courses.
The office team was already using the NDET admin panel every day. Learning a second system, or paying to host and maintain another site, didn't make sense.
What they needed
- Its own domain, logo, colours and wording
- Focused on one program: B.Sc Nursing
- Separate notices, events and gallery from NDET
- Managed from the same admin panel staff already know
- Good search visibility for nursing colleges in Khunti and Ranchi
What we built
The pieces that make it work
Its own domain
imperialnursing.in serves its own pages, its own sitemap and its own search metadata. To visitors it's simply Imperial's website.
Its own identity
Imperial's logo, a blue colour scheme instead of NDET's green, and copy written for one college with one program.
Content kept apart
Every notice, event and album belongs to one college. The database enforces it, so a post can't show up on the wrong site by accident.
One admin panel
Staff switch between NDET and Imperial with a toggle. Same login, same screens, same habits.
Program details
Eligibility, timeline and career paths for B.Sc Nursing, written for students and parents rather than for a prospectus.
Enquiries to the right desk
Admission enquiries come in tagged with the college, so Imperial's desk only sees Imperial's leads.
One platform, two colleges
Two websites. One thing to look after.
Both colleges run on the same app, server and database. Each domain gets its own branding and content, and staff manage both from one admin panel.
ndet.co.in
Green theme · 4 programs
imperialnursing.in
Blue theme · B.Sc Nursing
One Next.js app
Reads the domain, loads that college's logo, colours, menus and copy.
One database
Every notice, event and album is tagged with its college, and the database enforces it.
One admin panel
A toggle switches between colleges. Same login, same screens.
A closer look
Screens from the live site
Made for phones first
Most visitors arrive on a phone, often on a slow connection. Every screen was designed and tested for that first.
Under the hood
The decisions you don't see
Good software is mostly the parts nobody notices: what happens when a payment fails, a page loads on 2G, or someone clicks the wrong button. Here's some of that.
Built with
- 01
The site is picked by domain
When a request comes in, the platform looks at which domain it was sent to and loads that college's branding, menus and content. Adding a third college would mostly mean writing its content.
- 02
Rendering and writing are kept separate
The domain only decides what a visitor sees. Anything that saves data has to say which college it belongs to, and that's checked on the server. You can't trick the system into posting to the other college.
- 03
Two sites, one bill
One server, one database and one deployment serve both colleges. Every fix and every new feature reaches both sites at once.
Got something similar in mind?
Tell us what you're trying to build. We'll get back to you with honest advice, a rough plan and a timeline. No obligation, no jargon.
Next project
CosmicDrishti