{"id":6466,"date":"2026-11-21T07:58:43","date_gmt":"2026-11-21T07:58:43","guid":{"rendered":"https:\/\/www.cmsgalaxy.com\/blog\/?p=6466"},"modified":"2026-11-21T08:00:43","modified_gmt":"2026-11-21T08:00:43","slug":"studio-that-built-its-website-in-public","status":"publish","type":"post","link":"https:\/\/www.cmsgalaxy.com\/blog\/studio-that-built-its-website-in-public\/","title":{"rendered":"The Web Studio That Built a Client Site Out in the Open"},"content":{"rendered":"<p>This is a story about a small web studio, a family hardware shop and a site rebuild that nearly went sideways. It is fictional, but anyone who has worked on websites will recognise the beats. The short version: the studio&#8217;s wisest decision was to stop hiding the work in progress, and the project got calmer the moment it did.<\/p>\n<h2>The setup<\/h2>\n<p>The studio had four people: a designer, two developers and a project lead who also answered the phone. Their client was a family-run hardware shop with a tired website, a messy contact page and a habit of sending feedback in bursts, usually late on Friday. The studio&#8217;s usual routine was familiar. Work for two weeks in private, send a big preview link, wait for reactions, repeat.<\/p>\n<p>The first preview went badly. The client hated the colour scheme, the product pages were not what had been discussed, and a whole section that took three days to build turned out to be unnecessary. Everyone felt worn out. The project lead called a short meeting and put one idea on the table: let the client see each step the moment it happened.<\/p>\n<h2>The experiment: a page anyone could open<\/h2>\n<p>The team set up a plain progress page. It had three lists, &#8220;Next&#8221;, &#8220;In progress&#8221; and &#8220;Done&#8221;, and a notes section at the bottom. The designer posted rough screenshots with a caption that read &#8220;unfinished, just for direction&#8221;. The developers added a line each morning about what they would tackle. The project lead made sure the page needed no login, so the client&#8217;s staff, the shop owner&#8217;s relatives and even the person who handled their accounts could look in.<\/p>\n<p>Nobody expected much. The page was ugly and the first entries were embarrassingly rough. But within a day the shop&#8217;s staff began leaving comments, and they were useful ones: &#8220;customers always ask about opening hours first&#8221;, &#8220;the van delivery area needs to be on the front page&#8221;. These were things no briefing document had captured.<\/p>\n<h2>How the first fortnight felt<\/h2>\n<p>The mood shifted. Feedback arrived in small pieces instead of one large complaint. A wrong turn on navigation was caught on the second day, not the tenth. The designer noticed that the staff reacted most strongly to photographs of the real shopfront, so those moved to the top of the layout. The developers stopped building features nobody asked for because the &#8220;Next&#8221; list made priorities visible to all.<\/p>\n<p>Planning got easier too. Ahead of the redesign, the team had read through a walkthrough on <a href=\"https:\/\/www.cmsgalaxy.com\/blog\/how-to-plan-a-business-website-before-development-starts-a-complete-step-by-step-guide\/\">laying the groundwork for a company website prior to development<\/a>, and the progress page turned its checklist into something alive. Each planning item became a card, and the client could tick comments onto it directly.<\/p>\n<h2>The awkward moment<\/h2>\n<p>A word first about the daily rhythm. Each morning the project lead spent ten minutes tidying the page: moving cards, trimming old notes, replying to comments. At first this felt like overhead. By the second week it had replaced a weekly status call, and the calendar got lighter, not heavier. The client&#8217;s staff, who had never joined a call anyway, started reading the page over their morning tea.<\/p>\n<p>It was not all smooth. One afternoon the page showed a half-built checkout screen that looked broken. A relative of the shop owner saw it, assumed the site was going live that way and called in a panic. The project lead handled it calmly, added a banner reading &#8220;pages marked in progress are not final&#8221; and began labelling every screenshot with its status. The lesson stuck: open work needs plain labels, because outsiders do not share your sense of what &#8220;rough&#8221; means.<\/p>\n<p>There was a second lesson about boundaries. A developer had pasted a test account detail into the notes by mistake. A teammate spotted it within minutes, it was removed, the details were changed and the team wrote a short rule for the top of the page: no logins, no private contact details, no financial figures. Open does not mean careless.<\/p>\n<h2>Where the shop&#8217;s own listings came in<\/h2>\n<p>As the build progressed, the shop owner asked a practical question: how could customers find out what was actually on the shelves? The studio pointed to how a local-shopping site called <a href=\"https:\/\/buymlocal.com\/\">BuyMLocal<\/a> works, where nearby sellers publish their own availability on a board that shoppers can search by place. The studio did not copy it, since the shop&#8217;s needs were smaller, but the idea shaped a simple &#8220;this week in store&#8221; section on the new site, updated by the staff and visible to anyone.<\/p>\n<h2>The structure that came out of it<\/h2>\n<p>By the end of the month, the pages had settled into a shape the shop recognised: a homepage with the shopfront and hours, a page for services such as key cutting, a page for delivery areas and a contact page. When the team compared their result with a checklist on <a href=\"https:\/\/www.cmsgalaxy.com\/blog\/essential-pages-every-business-website-should-include-a-complete-structural-guide\/\">which pages a business website normally needs<\/a>, they found the open process had brought them to nearly the same list, only faster and with fewer arguments.<\/p>\n<h2>The launch, and what the team kept<\/h2>\n<p>Launch day was uneventful, which is the outcome every launch should aim for. There was no last-minute scramble because nothing on the page had been a surprise for weeks. The client had already seen every screen, commented on most of them and watched each decision get made.<\/p>\n<p>Afterwards the studio kept the habit. Every new project now begins with a progress page, a short rule list and a status label on every screenshot. The project lead summarised the change in a sentence the team still repeats: &#8220;Surprises belong at birthday parties, not in project reviews.&#8221;<\/p>\n<h2>Takeaways you can borrow<\/h2>\n<ul>\n<li><strong>Start the page on day one.<\/strong> An ugly early page earns more trust than a polished late one.<\/li>\n<li><strong>Label everything.<\/strong> Say whether an item is a sketch, a draft or final.<\/li>\n<li><strong>Agree what stays private.<\/strong> Credentials, personal data and money figures never go on the page.<\/li>\n<li><strong>Read the comments daily.<\/strong> Replies from outsiders are the main prize.<\/li>\n<li><strong>Keep it short.<\/strong> A few lines a day beats a long report nobody reads.<\/li>\n<\/ul>\n<p>The studio&#8217;s story is made up, but the pattern is not. Work shown early gets corrected early, and clients who watch the build rarely feel like strangers when the site goes live.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A fictional studio stops hiding its work-in-progress and lets a hardware shop watch the site take shape, with surprising results for feedback and trust.<\/p>\n","protected":false},"author":14,"featured_media":6467,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1455],"tags":[],"class_list":["post-6466","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web-development"],"_links":{"self":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/6466","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/comments?post=6466"}],"version-history":[{"count":1,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/6466\/revisions"}],"predecessor-version":[{"id":6547,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/6466\/revisions\/6547"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/media\/6467"}],"wp:attachment":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/media?parent=6466"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/categories?post=6466"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/tags?post=6466"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}