Public website
Home, accommodation, restaurant, destination, services, galleries and contact pages for prospective guests.
Use case · Websites and content managementA venue websitethe staff runthemselves
We built the public website and content system for a hospitality venue with accommodation and a restaurant. Guests browse the rooms, the menu and the area and send an enquiry. The venue’s staff change pages, photos and floor plans from an admin area, without calling a developer.
Since 2018live and looked after by CBOS5page editors the venue’s staff use themselves
Who this is for
Venues whose rooms, food and spaces change through the year, and the people who have to keep the website in step.
Guest houses and lodgesBoutique hotelsRestaurants with roomsWedding and function venuesConference venuesCountry estatesGuest houses and lodgesBoutique hotelsRestaurants with roomsWedding and function venuesConference venuesCountry estates
Owners and general managersFront of house and reservationsRestaurant managersEvents coordinatorsWhoever “does the website” on the sideOwners and general managersFront of house and reservationsRestaurant managersEvents coordinatorsWhoever “does the website” on the side
The problem
Guests judge the venue by a website your staff can’t change
A venue’s website goes stale fast when every new photo, menu change or updated floor plan has to go through a web developer. Each request sits in someone else’s queue, guests read last season’s information in the meantime, and after a while the staff stop asking for changes at all.
The menu on the site is last season’s
The kitchen changed the menu weeks ago, but the site still lists dishes you no longer serve. Guests arrive asking for them and front of house has to apologise.
Every photo waits for a developer
New rooms, a refreshed restaurant or a good season’s photos sit in someone’s inbox until the agency gets to them, and the gallery keeps showing the venue as it looked years ago.
Floor plans that don’t match the building
An events planner works from a floor plan with a wall that’s since come down or a room that’s been split. You find out on the site visit, or on the day.
Enquiries in five different places
Some come by email, some by phone, some through social media and some through a form that emails someone who’s on leave. The ones nobody sees turn into bookings somewhere else.
Photos saved wherever someone left them
The good shots live on a phone, a laptop and an old shared drive. When the site needs one, someone loses an afternoon looking for it or settles for whatever’s to hand.
Small fixes need a request and an invoice
Changing opening hours or a phone number means logging a job with an outside developer and paying for it, so the small fixes pile up and the site drifts further from the venue.
The people who know what changed at the venue are the only ones who can’t change the website.
Before and after
From a developer queue to staff in charge
Flip the switch to see the same six jobs with the admin area in place.
BeforeWith the system
- Content changes queued with a developerStaff edit pages, photos and galleries themselves
- Menus and restaurant details out of dateStaff update the restaurant page when the menu changes
- Facility details and floor plans out of dateFloor plans and factsheets updated from the admin area
- Enquiries scattered across channelsThe contact form sends every enquiry to the venue’s email
- Photos stored wherever someone saved themOne asset library behind the whole site
- Staff stop asking for changesThe people who know the venue keep the site current
Every new photo, menu and floor plan waits in a developer’s queue.
The people who run the venue keep its website current.
A week at the venue
One menu change, two ways the week can go
The kitchen changes the menu on Monday. The top line waits on a developer, and the bottom line has the admin area.
Swipe sideways to follow the week.
How it works
What happens when something at the venue changes
Four parts of the system, each doing one job. Click through them.
01Staff edit a page
02Photos come from one library
03Floor plans and factsheets stay current
04Enquiries reach the venue
Step 01
Staff edit a page
Someone on the team signs in to the secure admin area, opens the home, destination, gallery, restaurant or services page and changes the words or photos. Saving it updates the public site.
Step 02
Photos come from one library
Staff upload photos and files to one asset library, and the pages and galleries draw from it. Nobody has to hunt through phones and laptops for the right shot.
Step 03
Floor plans and factsheets stay current
When a room is split, a space is refurbished or a facility changes, staff update the floor plan and the factsheet in the admin area, so planners and guests see the venue as it is now.
Step 04
Enquiries reach the venue
A guest fills in the contact form on the site and the enquiry is emailed to the venue, so it lands in the inbox the team already works from.
What we built
The site, its editors and the hosting underneath
A public website for guests, an admin area for staff, and the hosting that keeps both running.
Page editors
Staff edit the home, destination, gallery, restaurant and services pages from a secure admin area.
Asset library
One place for the photos and files the site uses, managed by staff.
Facilities and floor plans
Facility information, floor plans and factsheets that staff keep up to date.
Enquiry handling
The contact form captures guest enquiries and emails them to the venue.
Hosting and deployment
The site and its API run in containers on Azure, with automated build and release pipelines.
Hover over a card for more.
What changes
What’s different for the people at the venue
Front of house
The site shows what the venue offers now, so the answers on the phone and the answers on the page agree.
The restaurant
When the kitchen changes the menu, someone on the team puts it on the restaurant page.
Events and functions
Planners work from the current floor plan and factsheet, kept up to date by the people who manage the spaces.
Owners and managers
Every enquiry from the contact form arrives in the venue’s email, and CBOS looks after the site underneath.
Built with
The stack
.NET 8AngularSQL ServerEntity Framework CoreDockerMicrosoft AzureAzure PipelinesTerraform
Before you call
How we’d start, and what venues usually ask
How we’d start
- 01
Discovery
We look at your current site and ask what your team changes most often: menus, photos, rooms, floor plans or events.
- 02
First release
The public pages and the editors for the things you change most, on hosting we look after.
- 03
Build out
More editors, galleries, factsheets and enquiry handling as the venue needs them, with us maintaining the site year after year.
Questions
Do we have to rebuild our whole website?
In discovery we look at what you have and what your team changes most, then recommend whether to build new or work with what’s there. For this venue we built the public site and the admin area together.
Will our staff manage it?
The editors follow the pages your team already thinks in (the home page, the restaurant, the gallery), so changing one means opening that page and editing it.
Where do the enquiries go?
The contact form emails each one to the venue, so your team answers from the inbox it already uses.
Who looks after hosting and updates?
We do. CBOS has looked after this venue’s site since 2018. It runs in containers on Azure with automated build and release pipelines.
Quick check
Sound like your business?
Tick what sounds familiar.
You wait on a developer or agency to change a photo or a line of text on your website.
Your website shows menus, rates or facilities that are out of date.
Guest enquiries arrive through too many channels and some get missed.
You’ve got floor plans or factsheets that change and need to be on the site.
You’d like one partner to host, maintain and improve your site year after year.
of 5 ticked
0 to 1 ticked
Your website is probably serving you well. If that changes, we’re happy to talk about what a self-managed site would look like.
2 to 3 ticked
Your team is losing time and bookings to a site they can’t update. A few editors and a proper enquiry flow would change that.
4 to 5 ticked
Talk it through with us
You need the kind of site we built here, one your staff run day to day while we host and look after it.
More case studies
All case studies Other businesses we’ve built for
Let’s talk
Is your website still showing last season’s venue?
Tell us what your team needs to change most often and we’ll show you how they could do it themselves.
Use case · Websites and content managementA venue websitethe staff runthemselves
We built the public website and content system for a hospitality venue with accommodation and a restaurant. Guests browse the rooms, the menu and the area and send an enquiry. The venue’s staff change pages, photos and floor plans from an admin area, without calling a developer.
Since 2018live and looked after by CBOS5page editors the venue’s staff use themselves
Who this is for
Venues whose rooms, food and spaces change through the year, and the people who have to keep the website in step.
Guest houses and lodgesBoutique hotelsRestaurants with roomsWedding and function venuesConference venuesCountry estatesGuest houses and lodgesBoutique hotelsRestaurants with roomsWedding and function venuesConference venuesCountry estates
Owners and general managersFront of house and reservationsRestaurant managersEvents coordinatorsWhoever “does the website” on the sideOwners and general managersFront of house and reservationsRestaurant managersEvents coordinatorsWhoever “does the website” on the side
The problem
Guests judge the venue by a website your staff can’t change
A venue’s website goes stale fast when every new photo, menu change or updated floor plan has to go through a web developer. Each request sits in someone else’s queue, guests read last season’s information in the meantime, and after a while the staff stop asking for changes at all.
The menu on the site is last season’s
The kitchen changed the menu weeks ago, but the site still lists dishes you no longer serve. Guests arrive asking for them and front of house has to apologise.
Every photo waits for a developer
New rooms, a refreshed restaurant or a good season’s photos sit in someone’s inbox until the agency gets to them, and the gallery keeps showing the venue as it looked years ago.
Floor plans that don’t match the building
An events planner works from a floor plan with a wall that’s since come down or a room that’s been split. You find out on the site visit, or on the day.
Enquiries in five different places
Some come by email, some by phone, some through social media and some through a form that emails someone who’s on leave. The ones nobody sees turn into bookings somewhere else.
Photos saved wherever someone left them
The good shots live on a phone, a laptop and an old shared drive. When the site needs one, someone loses an afternoon looking for it or settles for whatever’s to hand.
Small fixes need a request and an invoice
Changing opening hours or a phone number means logging a job with an outside developer and paying for it, so the small fixes pile up and the site drifts further from the venue.
The people who know what changed at the venue are the only ones who can’t change the website.
Before and after
From a developer queue to staff in charge
Flip the switch to see the same six jobs with the admin area in place.
BeforeWith the system
- Content changes queued with a developerStaff edit pages, photos and galleries themselves
- Menus and restaurant details out of dateStaff update the restaurant page when the menu changes
- Facility details and floor plans out of dateFloor plans and factsheets updated from the admin area
- Enquiries scattered across channelsThe contact form sends every enquiry to the venue’s email
- Photos stored wherever someone saved themOne asset library behind the whole site
- Staff stop asking for changesThe people who know the venue keep the site current
Every new photo, menu and floor plan waits in a developer’s queue.
The people who run the venue keep its website current.
A week at the venue
One menu change, two ways the week can go
The kitchen changes the menu on Monday. The top line waits on a developer, and the bottom line has the admin area.
Swipe sideways to follow the week.
How it works
What happens when something at the venue changes
Four parts of the system, each doing one job. Click through them.
01Staff edit a page
02Photos come from one library
03Floor plans and factsheets stay current
04Enquiries reach the venue
Step 01
Staff edit a page
Someone on the team signs in to the secure admin area, opens the home, destination, gallery, restaurant or services page and changes the words or photos. Saving it updates the public site.
Step 02
Photos come from one library
Staff upload photos and files to one asset library, and the pages and galleries draw from it. Nobody has to hunt through phones and laptops for the right shot.
Step 03
Floor plans and factsheets stay current
When a room is split, a space is refurbished or a facility changes, staff update the floor plan and the factsheet in the admin area, so planners and guests see the venue as it is now.
Step 04
Enquiries reach the venue
A guest fills in the contact form on the site and the enquiry is emailed to the venue, so it lands in the inbox the team already works from.
What we built
The site, its editors and the hosting underneath
A public website for guests, an admin area for staff, and the hosting that keeps both running.
Public website
Home, accommodation, restaurant, destination, services, galleries and contact pages for prospective guests.
Page editors
Staff edit the home, destination, gallery, restaurant and services pages from a secure admin area.
Asset library
One place for the photos and files the site uses, managed by staff.
Facilities and floor plans
Facility information, floor plans and factsheets that staff keep up to date.
Enquiry handling
The contact form captures guest enquiries and emails them to the venue.
Hosting and deployment
The site and its API run in containers on Azure, with automated build and release pipelines.
Hover over a card for more.
What changes
What’s different for the people at the venue
Front of house
The site shows what the venue offers now, so the answers on the phone and the answers on the page agree.
The restaurant
When the kitchen changes the menu, someone on the team puts it on the restaurant page.
Events and functions
Planners work from the current floor plan and factsheet, kept up to date by the people who manage the spaces.
Owners and managers
Every enquiry from the contact form arrives in the venue’s email, and CBOS looks after the site underneath.
Built with
The stack
.NET 8AngularSQL ServerEntity Framework CoreDockerMicrosoft AzureAzure PipelinesTerraform
Before you call
How we’d start, and what venues usually ask
How we’d start
- 01
Discovery
We look at your current site and ask what your team changes most often: menus, photos, rooms, floor plans or events.
- 02
First release
The public pages and the editors for the things you change most, on hosting we look after.
- 03
Build out
More editors, galleries, factsheets and enquiry handling as the venue needs them, with us maintaining the site year after year.
Questions
Do we have to rebuild our whole website?
In discovery we look at what you have and what your team changes most, then recommend whether to build new or work with what’s there. For this venue we built the public site and the admin area together.
Will our staff manage it?
The editors follow the pages your team already thinks in (the home page, the restaurant, the gallery), so changing one means opening that page and editing it.
Where do the enquiries go?
The contact form emails each one to the venue, so your team answers from the inbox it already uses.
Who looks after hosting and updates?
We do. CBOS has looked after this venue’s site since 2018. It runs in containers on Azure with automated build and release pipelines.
Quick check
Sound like your business?
Tick what sounds familiar.
You wait on a developer or agency to change a photo or a line of text on your website.
Your website shows menus, rates or facilities that are out of date.
Guest enquiries arrive through too many channels and some get missed.
You’ve got floor plans or factsheets that change and need to be on the site.
You’d like one partner to host, maintain and improve your site year after year.
of 5 ticked
0 to 1 ticked
Your website is probably serving you well. If that changes, we’re happy to talk about what a self-managed site would look like.
2 to 3 ticked
Your team is losing time and bookings to a site they can’t update. A few editors and a proper enquiry flow would change that.
4 to 5 ticked
Talk it through with us
You need the kind of site we built here, one your staff run day to day while we host and look after it.
More case studies
All case studies Other businesses we’ve built for
Let’s talk
Is your website still showing last season’s venue?
Tell us what your team needs to change most often and we’ll show you how they could do it themselves.
Let's Connect
Interested in building a smarter, more connected operation? Contact us to discuss how AI can support your business goals.