The problem's lifespan defines the solution
The technical temptation was familiar: accounts, payments, cart, backend, inventory. But the problem had a concrete date. With every week that went by, publishing the catalog mattered more than designing a platform capable of surviving ten years.
That constraint shaped the decision. Casa Médanos became a fast, shareable catalog: photos, visible prices, filters by room, search and a clear status for what was sold. A single link replaced an absurd number of repeated messages.
Static architecture with product value
Choosing a static site on GitHub Pages wasn't cutting features for sport. It took servers to monitor, databases to back up and costs that didn't help sell a couch out of the picture. For someone arriving from social media, a page that loads fast also does more than a sophisticated architecture.
Complexity stayed where the real work was: updating availability, finding an item and showing that something had already sold without making it disappear. The technology followed the flow, not the other way around.
Focused automation and operating cost
The repeated questions justified a targeted automation. An n8n flow, versioned alongside the code, helps answer them without inventing a messaging app or turning a temporary sale into a permanent operation.
Since then I've used a simple test: if a piece of infrastructure doesn't reduce a repetitive task, a real risk or a current cost, it doesn't belong in the MVP yet. It can come later. Today it's just a distraction.
Acquisition
- Social media
- Shareable link
Web experience
- Catalog and search
- Filters and prices
Publishing
- Static site
- GitHub Pages
Operations
- Availability
- n8n automation
Visitors browse a catalog published on GitHub Pages. A panel updates availability and an n8n workflow helps with repetitive questions without introducing a transactional backend.
Architecture principle: the solution should match the lifespan, risk and volume of the current problem. Every extra capability also adds operating cost.