A visual sitemap editor that forces you to design structure before UI

Name: A visual sitemap editor that forces you to design structure before UI
Availability: InStock
Author: epic_ai

by epic_ai·Mar 1, 2026·3 points·2 comments

Visit Project View on HN

AI Analysis

●MidEye CandySolve My Problem

Sitemap-first design is sensible pedagogy, but it's a niche workflow without retention data.

Strengths

•Cognitive reframing: forcing structure before UI prevents later chaos
•Drag-drop canvas with auto-layout arrows makes navigation flows tangible and visual
•JSON export integrates with no-code builders (Webflow, etc.) and custom tools

Weaknesses

•Core problem already solved: FigJam, Lucidchart, Whimsical do sitemaps with more features
•Tool is adjacent to a design tool (EPIC), not the core product — feels like a feature demo

Post Description

Most web tools start with UI. Templates. Components. AI layouts. But structure — the sitemap, the navigation logic — usually comes later. So I built a tool: https://no-edit.lovable.app A browser-based visual sitemap + navigation editor where you design the hierarchy first, before touching visuals. Core idea: Pages are nodes Navigation is explicit Hierarchy is visible at all times You can’t “accidentally” create structural chaos Instead of designing a homepage first, you design the map. Then the UI sits on top of that structure. What I’ve noticed: Users spend time reorganizing structure before styling Navigation clarity reduces later edits Thinking in hierarchy changes how features are added I’m curious: For those who’ve built CMSs, IDEs, or large web apps — Should structure be a first-class citizen in design tools? Or is it something users only care about at scale? Would love technical feedback on the approach. Link in comments.