You're rebuilding only the marketing pages, right? Not our bookshop.org order flow? +
Yes. The rebuild is the website at lymebookshop.com: the homepage, Local Books, Events, Our Other Shops, Contact, and a new About page. The bookshop.org storefront (uk.bookshop.org/shop/lymeregisbooks) is a separate platform you don't own the code for, and it stays exactly where it is. We add a clean "Buy online" button on the rebuild that routes to your bookshop.org page. No catalogue migration, no order data move, no risk to running sales.
How do we handle the "Established" wording when the shop predates Kevin and Jayne? +
The current homepage uses "A bookshop for over 40 years, the present owners Kevin and Jayne Ramage took over in December 2020." The rebuild keeps that posture exactly. The hero reads "Forty years on Broad Street." The heritage strip names Kevin and Jayne as the current keepers, dated December 2020, and leaves the founders unnamed (because they are unnamed by the shop's own copy). If you give me the founding year and the founders' names by email I will write them in; if not, the heritage block rests on the verifiable forty-year claim and the literary citations.
The Mary Anning angle is obvious, but is it tasteful? You're an out-of-towner saying it. +
It is tasteful only if it's sparing. The rebuild treats Anning the way the Lyme Regis Museum does: she is a citation, not a marketing hook. One block on the homepage names her, the statue, the year 2022, the unveiling. The Local Books page restores the "Mary Anning, Fossils & Dinosaurs" category that's currently commented out of your own HTML. No Anning silhouette in the logo, no ammonite icon overused (although the existing logo is itself an ammonite, which I keep). It is a citation of fact, not a co-opting of her story.
The shop is open seven days a week and short-staffed in winter. How much CMS editing does this need? +
The rebuild renders from a small JSON file: hours, address, phone, current events, current book-club pick. Updating the homepage hours when winter starts is editing one file, two seconds. The Events page lists from a folder of markdown files, one per event. The bookseller adds a file, the page rebuilds. No CMS login, no plugin updates. If you want a one-page admin form, that's an extra week and £200; most shops with one or two updates a month prefer the JSON.
You're in Switzerland. How does that work for a Dorset bookshop? +
Fully remote, fully asynchronous. I've worked this way for nine years as a British developer. Everything is by email and the occasional video call at a time that suits the shop's short trading day. I do not need to be in Lyme for any of the build. If you want fresh launch photography I can recommend a Dorset photographer; not a condition. Phone +44 7884 442 651 for anything urgent, including DNS cutover day.