Lantern Ramblers: a tribute band site with tour dates, a setlist archive and live song stats
A website for a Grateful Dead tribute band: tour dates that move to past shows on their own, a setlist archive with a song filter, live s...
For each Raytha use case we take a realistic brief, hand it to an AI agent with the raytha CLI, and publish what
comes out: the site, the files behind it, and a kit you can use to rebuild it yourself. This one is the corporate
website for a durable medical equipment (DME) provider: the company that delivers oxygen, CPAP machines,
wheelchairs and hospital beds to patients at home.
The agent built it on a fresh Raytha 2.0.1 instance. Nobody opened the admin. Every template, content type, product, guide, page and menu went in through the CLI, from files in a directory.
What was built
Brightwell Medical Supply is a fictional DME provider with three locations. The site has:
- A home page with a search box, equipment categories with live product counts, the most ordered equipment, a four-step "how ordering works" strip, the insurance plans accepted, a map of locations, patient guides and common questions.
- An equipment catalog you can search by name or HCPCS billing code and filter by category, by whether an item can be rented or bought, and by how it is usually paid for: Medicare, private insurance or self-pay. Every filter is a plain link you can share.
- Product pages with the HCPCS code, rental or purchase options, whether a prescription is needed, a specifications table, what comes in the box, an explanation of coverage and cost, helpful guides and related equipment.
- A page for each of the six categories, with its products and guides.
- Patient resources: plain-language guides on ordering, Medicare and billing, and caring for equipment at home.
- A frequently asked questions page grouped by topic, with a box that filters the questions as you type.
- Location pages with a map, services, parking details and opening hours, with today's hours highlighted.
- How to order and contact pages that explain what a doctor needs to send and who to call.
There are no payment or order forms anywhere. Every product page asks people to call the order desk or email it, and prescribers are given a fax number, which is how most DME orders arrive in practice.
The design is calm and clinical: Plus Jakarta Sans throughout, with a monospace for billing codes, on soft white and mint with deep navy and teal, and a touch of amber. The product illustrations are simple line drawings in SVG, so the catalog looks consistent without stock photos. On a 390px phone the layout stacks into one column, the menu folds away and the phone number stays one tap away.
Features, and the Raytha features behind them
| Feature | How it is built |
|---|---|
| Categories, products, guides, questions and locations | Five content types from one schema document. Products use a relationship field to their category, dropdowns for rent or buy and for coverage, a checkbox for prescription required, an attachment for the illustration and long text fields for specifications and what is in the box. |
| 45 seed items | Content import from JSON Lines. Products point at their category by name, and the illustrations are uploaded during the import. |
| Equipment catalog | A list view at /products. The Liquid template reads ?category=, ?acquire=, ?coverage= and ?q=, checks each value against a known list and builds a filter for get_content_items. |
| Specifications table | Each line of the specifications field is a label and a value. The product template splits the lines and renders a table. |
| Coverage explanation | The product template picks the right explanation from the coverage dropdown, so editors only choose an option. |
| FAQ | A content type with a topic dropdown. The FAQ list view groups questions by topic, and a few lines of script filter them as you type. Home, How to order and Contact show questions from a chosen topic through a widget setting. |
| Locations and hours | A content type with an address, phone, hours and map position. The templates place the pins on an illustrated map, and a short script highlights today's hours. |
| Home, How to order and Contact | Site pages built from 12 custom widget templates (hero with search, categories, featured products, steps, insurance, locations, guides, questions, call band, page header, contact cards, checklist). |
| Navigation | Two menus: the main menu and a footer menu. The footer also lists the categories straight from the content. |
The brief
This is the brief, as given to the agent.
Build a corporate website for a durable medical equipment provider on a fresh Raytha instance with the
raythaCLI. No clicking around the admin.
Look and feel
- Visually impressive, with a design of its own. Display type that is well proportioned, not overly wide.
- Responsive. It has to look good on a phone as well as a desktop.
Content and pages
- Product categories and products, with the details patients and caregivers look for.
- Patient resources, insurance and how-to-order information, FAQs and locations.
- No payment forms.
Done means
raytha checkpasses with no broken routes.- Screenshots of the result on desktop and mobile.
- A kit in the examples repository that rebuilds the site on a fresh install.
How long it took
About 35 minutes of agent time, from an empty install to raytha check passing on every route, including the
visual design, the product illustrations and writing the product pages and guides.
Rebuild it yourself
The theme, schema, seed content and illustrations, page definitions and menus are in the
raytha-examples repository,
with a build.sh that rebuilds the whole site into any Raytha 2.x instance. Point it at your site with
RAYTHA_URL and RAYTHA_API_KEY and run it.
