What a garden studio taught me about hosting a CMS
I built a fictional garden studio to try out EmDash. The public site could live under an examples page, but the editor needed a home of its own.
I wanted one of the Melotte Digital examples to show what happens after a website is built. If you have a garden design studio, you might want to put up a guide to planning a small garden, write about what to plant in autumn, or add photos from a project. Those are useful changes to be able to make yourself. So I made up Hawthorn Garden Studio and built a demo around that idea.
I normally if I need a form of CMS based website I either write my own or use something slightly unusual for example this journal uses Outline for editing and Astro for the public pages. For Hawthorn I wanted to try EmDash, where the editor is part of the website and arguably makes it easier for ‘users’ to update various parts of the website. I started by putting the demo under the main site's examples path, which had worked for simpler demos. The public pages had some routing issues at first, but I could get them to load there. Getting into the editor was a different matter.
The setup page opened, then failed while it was trying to fetch its configuration. Once I got that request working, moving around the editor still produced broken addresses. Parts of EmDash expected the editor to be at a fixed path from the root of the site. Putting it a couple of levels down meant those parts disagreed about where to send the browser.
I moved Hawthorn to its own hostname and took out the routing workarounds. That got the homepage and setup page responding at the addresses EmDash expected. At that point the next step was to create the first editor account and try the full publishing flow. It’s a good reminder of what a demo is for. A homepage can look finished while there’s still work to do on the bit someone will use every week.
The demo is linked from the Melotte Digital examples page.