Platform CLI Use cases
Learn
Developer docs User guide Quickstart CLI and AI agents Blog
Company
Services About Contact Links Get started
Government and public sector

Cadwallow Park: a self-hosted CMS for city parks departments — an open-source .NET city park website

A city park website for a fictional 410-acre municipal park, built like a trailhead kiosk: an illustrated park map drawn from content, gates, sunrise and sunset and every place's open-now status worked out on the server, five blazed trails with elevation profiles, a tree register, what to look for this month, a conditions board, park projects, shelters and fields reserved by phone, and members-only areas for the Friends of the park and park staff. Built on Raytha, a self-hosted, open-source .NET CMS for parks and recreation departments and the agencies that build their sites.

Build time
Under an hour
Built with
Raytha 2.0.1
Industry
Government and public sector
Rebuild
One script, from GitHub
Cadwallow Park: a self-hosted CMS for city parks departments — an open-source .NET city park website
Walkthrough

See it in action

A short, silent tour of the finished site, recorded from the real pages.

Silent walkthrough, 1080pOpen the MP4
The site

Take the tour

10 screens from the finished site, on desktop and on a phone. Use the arrow keys, swipe, or open any screen full size.

01 / 10Home: the trailhead kiosk, with the park map, gates, daylight and what is open now worked out on the server
The write-up

For each Raytha use case we take a realistic brief, build the site on a fresh Raytha instance, and publish what comes out: the site, the files behind it, and a kit you can use to rebuild it yourself. This one is a city park website for a large municipal park run by a parks and recreation department: the page a family checks before driving over on a Saturday, the trail guide a runner reads before tackling the hill, the conditions board a dog walker looks at after a storm, and the members-only pages where volunteer stewards and park crew get their week's work. It is written for city and county parks departments, the city IT teams that host their sites, and the agencies that build for them.

If you are looking for a self-hosted CMS for city parks departments, or an open-source .NET CMS for parks and recreation, this is the kind of site that fits: places, trails, trees, seasonal sightings, conditions, capital projects, events and bulletins as structured content, server-rendered pages, and a volunteer area and a staff area built on Raytha's own user accounts and groups. Built on a fresh Raytha instance, with no client-side app in the layout.

Cadwallow Park is fictional. The park, its city, the people, trees, projects and figures are invented and labeled as such, and phone numbers use the 555 range. There are no booking, payment, volunteer or sign-up forms; the Friends and staff accounts exist only for the demo.

A park site built like a trailhead kiosk

Most people open a park website with one question: is it open, and what is it like right now? So the home page opens on the kind of map board you find at a trailhead, with today's answers beside it.

  • The kiosk map. An illustrated map of the whole park, drawn as SVG on the server. The trail lines come from a path stored with each trail, and every numbered marker from a place's map position, so the parks office moves a marker or reroutes a trail by editing content, not artwork. A "you are here" arrow marks the South Gate.
  • Today at the park. Whether the gates are open, today's approximate sunrise and sunset on a daylight bar, and how many places are open right now. All of it is worked out on the server from the date and time. Nobody edits it each morning.
  • Open now, for every place. Each gate, playground, shelter, field, garden and restroom stores its hours and its season. The status (open, closing soon, opens later, closed for the season) is computed on every page view, including seasons that wrap the new year, like a winter warming hut, and places that close at dusk, where dusk comes from the day's sunset. The places list filters by kind or by "open now" on the server.
  • Trails that follow the blaze. Five trails, each with its own blaze shape and color, length, climb, surface and access. Elevation profiles are drawn on the server from elevations stored with each trail, all on one scale, and each trail page highlights its line on the map and lists any conditions posted against it.
  • Look for this month. Fourteen seasonal sightings (mergansers, witch hazel, ginkgo leaf drop, fireflies) store the months they can be seen. The home page picks this month's on its own, and a year chart shows the whole calendar with any month selectable through a link.
  • Tree register, conditions and projects. Notable trees with numbered tags, a trunk cross-section drawn from the girth and a tree layer on the map; a conditions board with open, caution and closed lights; and capital projects with a five-step phase tracker and a funded-versus-budget bar.
  • Shelters and fields with capacity, season and how to reserve by phone, a fee table and the rules in plain words. Reservations happen through the parks office, not a form.
  • A stewards' shed and a crew board behind sign-in: workdays, the tool shed, adopted plots and minutes for the Friends of the park; work orders, the rota, closure plans and a live status list of every place for park staff.

Design: the trailhead kiosk

The look is park wayfinding: routed timber signs in brown with cream lettering, deep forest green, a kraft-paper background, and blaze colors on white trail markers. Headings are set in Overpass, a typeface drawn from highway signage, body text in Literata, and times, tags and labels in Overpass Mono. There are no wide display fonts. The map, place illustrations and tree tags are generated, so no real park, person or tree is pictured. It shares nothing with the Juniper Falls city government example, a city hall site built around services, council meetings and notices.

Why a parks department looks at a self-hosted CMS

  • It can live with the city's other systems. Many city IT teams run Windows servers, Microsoft 365 and a private cloud, and want the parks site under the same patching, backup and security review. Raytha is ASP.NET Core with PostgreSQL, so it can run on the city's own servers or private cloud, with single sign-on, role-based admin permissions and audit logs built in. You can also deploy it on Railway.
  • Volunteer and staff areas without a second product. Raytha has public user accounts and user groups. Events and bulletins carry an audience, and templates check CurrentUser.UserGroups on the server, so a work order or a Friends board paper is never sent to a browser that should not see it. The same feature runs both areas.
  • No per-seat pricing. Seasonal crew change every summer, and a Friends group can have hundreds of volunteers. Every crew lead, the arborist, the reservations office and every steward can have an account, and Raytha has no seat licensing.
  • The city owns the code and the content model. Raytha is open source. Places, trails, trees and projects are content types the department defines, and the templates and content are files the city can keep in its own repository, hand to the next agency, or move to a new server without renegotiating a contract.
  • Public records stay public, and quick. Pages are server-rendered HTML that work without JavaScript, carry no tracking or advertising scripts, and are easy to archive. That helps on a phone with weak signal at a trailhead, and it helps with accessibility reviews.
  • Works next to the reservation system. If the department already uses a recreation management or permits system, it stays where it is. Raytha runs the public site and the members-only areas around it, and its REST API and webhooks can bring in conditions, closures or event listings from other systems.

Raytha fits parks departments, and the agencies and city IT teams that build for them, that want to own their stack: the code is open source, the content model is yours, and the site can run on servers the city controls, with staff and volunteer accounts kept in-house. If the department would rather not run it, Raytha can be fully hosted and managed for you under contract. Where another platform may suit you better is if you need a large plugin marketplace, or an all-in-one recreation suite with registration, payments and a resident CRM built in. For fair comparisons with platforms cities and .NET teams often evaluate, see Raytha vs WordPress, Raytha vs Umbraco, Raytha vs DNN and Raytha vs Kentico.

How the members-only areas work

  • Two user groups: friends (the Friends of Cadwallow Park) and staff (park crew). Each sees its own area; admins see everything.
  • Events and bulletins have an audience field (everyone, Friends, staff). The detail template reads it and the signed-in user's groups and renders either the content or a lock panel with a sign-in link. Lists show the titles of members-only items with a lock and leave their contents out, and so does search. The page description in the HTML head falls back to a generic line for members-only items, so no summary leaks there either.
  • The stewards' shed at /stewards is a site page with its own template: signed out, it shows a lock panel; signed in as a Friend, it shows a steward badge with the next workday, today's sunset (work stops half an hour before), the workdays, plans, tool shed notes, minutes and adopted plots.
  • The crew board at /crew shows a crew badge with tonight's lock-up and dusk, the live status of every place, open work orders, the rota and closure plans, everything closed or under caution on the public board, staff events and this week's assignments, only for staff accounts. A signed-in Friend sees a short note pointing back to the stewards' shed, and the other way round.
  • Sign-in uses Raytha's built-in login page, restyled to match. There is no registration form: in the story, the volunteer coordinator opens an account for each steward after a first workday, and the parks office does the same for staff. For more on the pattern, see creating a members-only website.

What is in the kit

Eight content types (places, trails, trees, sightings, conditions, projects, events, bulletins), two user groups, site pages for the park map, Plan a visit, Shelters and fields, About, Search, the stewards' shed and the crew board, menus, and generated place illustrations, all rebuildable with one command from the kit in the examples repository. Route check: 99 routes checked, 0 failed.

Run it yourself

Run this on your own Raytha

Raytha is free and open source (MIT). Deploy your own copy on Railway, with PostgreSQL included, then load this site into it from the rebuild kit.

  1. Deploy RaythaThe Railway template sets up Raytha, PostgreSQL and a volume for uploads. Open the new site and create your administrator.
  2. Create an API keyIn the admin: People, Admins, open your account, then Create API key.
  3. Import the kitInstall the Raytha CLI, set RAYTHA_URL and RAYTHA_API_KEY, and run the kit's build.sh on the fresh site.

Prefer your own server? Raytha also runs with Docker.

Share Post LinkedIn

Build yours on Raytha

Free, open source and ready to deploy in minutes. Bring a brief and an AI agent.