News for hackers. Stuff that matters.

epic_ai

Please get me some feedback

Show HN: A visual sitemap generator that maps any website's full navigation tree

I built EPIC(https://no-edit.lovable.app)that crawls a website and generates a clean, interactive visual sitemap. You enter a URL → it maps the full structure: Page hierarchy Navigation depth Internal linking paths Structural clusters It’s useful for: Auditing bloated navigation Understanding competitor site structure Debugging complex product sites Refactoring legacy architectures I originally...

( Read More... | 1 comment | 2 points | on HN )
Would love to get feedback from you guys

Show HN: A visual sitemap generator for planning site structure

I built EPIC (https://no-edit.lovable.app) to make planning website and SaaS navigation less messy. I used to outline everything in docs: Home – Features – Pricing – Blog It works at first, but once the hierarchy grows, it becomes hard to scan, restructure, or share clearly. This tool converts a simple list of pages into a visual sitemap instantly. You can reorganize hierarchy, see nesting...

( Read More... | 6 comments | 3 points | on HN )
Re: on Tuesday March 03, 2026 @07:51AM (#47231552)
I’ve reviewed dozens of early-stage SaaS products over the last year. The most common issue wasn’t design quality. It wasn’t performance. It wasn’t even lack of features. It was structure. Typical problems I kept seeing: 6–8 items in the main navigation with no hierarchy Features scattered across unrelated sections Upgrade pages buried 3 levels deep Duplicate pages doing similar jobs Onboarding flows disconnected from the core product The result? Users don’t explore. They don’t understand the product depth. They leave. Before redesigning UI, I started mapping products as simple visual sitemaps — page by page, level by level. That single exercise usually revealed: Pages that shouldn’t exist Missing conversion bridges Overcomplicated user journeys Broken logical grouping But existing sitemap tools are mostly built for: SEO crawling XML exports Enterprise documentation Not for product thinking. So I built a simple visual navigation/sitemap maker focused on product structure, not SEO. You can: Visually map every page and subpage See hierarchy instantly Detect over-nesting Identify conversion dead-ends Plan upgrade flow properly Redesign structure before touching UI What surprised me most: Users are spending several minutes just reorganizing structure. Not designing. Not styling. Just thinking clearly. Because clarity is leverage. When structure improves: Copy improves Onboarding improves Feature discovery improves Retention improves I’m curious: Do you map your entire product structure before building? Or does navigation evolve organically as you ship? Would love to hear how other builders approach this.

Show HN: A visual sitemap tool to simplify SaaS navigation

Many SaaS products lose conversions because their navigation is too deep or confusing. Common issues: Important pages buried 3–4 levels down Multiple paths to the same feature Orphan pages No clear flow from landing → core action I built a simple visual sitemap tool inside EPIC(https://no-edit.lovable.app)to fix this. It lets you: Map your full navigation structure See hierarchy depth...

( Read More... | 3 comments | 3 points | on HN )

Show HN: A visual sitemap tool to see your website structure in seconds

Most small design tools focus on components, templates, or AI generation. But when traffic grows, structure becomes the real bottleneck. I built a visual sitemap tool EPIC(https://no-edit.lovable.app) that maps your entire website into a clean navigational tree — so you can instantly see: Broken hierarchy Orphan pages Overloaded navigation Conversion dead-ends It started as an internal tool...

( Read More... | 2 comments | 4 points | on HN )
Thanks
Thanks man, I really appreciate your support

Show HN: I built design tool with a visual sitemap maker

I’m a student founder building EPIC (https://no-edit.lovable.app)— a browser-based design tool (posters, presentations, logos, templates) with manual editing and optional AI mode. But the interesting part isn’t the editor. It’s the navigation + visual sitemap tool inside it. Most small projects struggle with structure. Pages get messy. Navigation grows randomly. Conversions drop because the...

( Read More... | 4 comments | 3 points | on HN )
Try the TOOL and let me know

Show HN: I stopped wireframing pages – I design SaaS products as visual sitemaps

When building small SaaS tools, I kept running into the same problem: I’d design beautiful pages… Then completely rethink navigation later. So I flipped the workflow. Now I design the entire product structure first as a visual sitemap. Not a text list. Not a static diagram. A drag-and-drop map of every page and connection. What changed: I cut unnecessary pages before writing code Navigation...

( Read More... | 5 comments | 3 points | on HN )
Oh. Thanks. I really appreciate it

Show HN: I built a design tool for people who find Canva too bloated

I’ve always found modern design tools overwhelming. Between the endless sidebars, layers, and "pro" upsells, I just wanted something that let me generate a professional asset and get out.> I built EPIC (https://no-edit.lovable.app) to be a "fast-path" alternative.> Key features:> * Navigation Maker: A drag-and-drop tool to plan site structures and export sitemaps (built this because...

( Read More... | 2 comments | 2 points | on HN )
oh, glad you liked it man
Re:HeadElf-Mvidia: Executive Intelligence Template on Saturday February 28, 2026 @09:51PM (#47203135)
oh, i got it earlier in a chat

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

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...

( Read More... | 2 comments | 3 points | on HN )
Try now , great tool

Show HN: I built a Canva-like editor at 14 – it ranked #4 organically in 30 days

I’m a 14-year-old builder from India, and I’ve been working on a design editor called EPIC ( https://no-edit.lovable.app ) It’s not an AI image generator. It’s more focused on navigation + structured design workflows (posters, presentations, logos). Instead of competing on “AI magic,” I tried something different: Manual editing first AI optional (not forced) Lightweight UI Fast load times Clear...

( Read More... | 2 comments | 3 points | on HN )
Re: on Saturday February 28, 2026 @07:33AM (#47194543)
Thats good enough
Re:OpenAI raises $110B on $730B pre-money valuation on Saturday February 28, 2026 @07:32AM (#47194526)
So many things are going on man, The Ai system is only broken.
The best tool

Show HN: We analyzed 312 landing pages – most navigation flows are broken

We’ve been building a small design + navigation planning tool(https://no-edit.lovable.app) over the last few months, and while testing it, we ended up manually analyzing 312 landing pages across SaaS, indie projects, and AI tools. The original goal was simple: understand how people structure navigation before designing UI. What we found surprised us. 1. 68% of pages had unclear primary...

( Read More... | 2 comments | 3 points | on HN )
Try and give feedback now.

Show HN: Drag/drop your site's user navigation map, export to code in seconds

Hey HN,Bootstrapping from Assam, India: EPIC turns messy site ideas into clean navigation maps. Drag pages, nest sub-flows, visualize user journeys—then one-click export to HTML navbars, XML sitemaps, or Figma JSON.Unlike bloated builders (Webflow/Slickplan), this is pure UX planning:Real-time drag/drop canvas for hierarchies & flows.��AI hints for optimal paths (e.g., "ecom checkout...

( Read More... | 4 comments | on HN )
Re: on Thursday February 26, 2026 @10:24AM (#47167310)
This week I ran a small performance experiment out of curiosity. I tested 25 popular websites across news, SaaS, e-commerce, and developer tools. Method: Chrome DevTools (Performance + Network tabs) Lighthouse (default settings) Throttled to “Fast 4G” 4× CPU slowdown Cold cache Measured until first reliable user interaction I wasn’t trying to embarrass specific sites, so I won’t name them individually. A few patterns stood out: 1. JavaScript payload size Median JS transferred: ~1.8MB Several exceeded 3MB A few crossed 5MB This is before any meaningful user action. For comparison, many early 2010s sites shipped <200KB total (HTML + CSS + JS combined). 2. Time to interactive Many pages visually loaded in 1–2 seconds. But: Main thread blocking frequently exceeded 400–900ms Multiple long tasks >50ms Hydration delayed input responsiveness The UI appeared ready, but input latency was noticeable. 3. Third-party script impact Common stack per site: Analytics Tag managers A/B testing Chat widgets Ads or tracking pixels In multiple cases, third-party scripts accounted for ~30–50% of total blocking time. 4. Framework baseline cost Modern frontend stacks introduce structural overhead: Hydration runtime Component abstraction layers Client-side routing Polyfills Even “simple” pages often include a non-trivial runtime footprint. 5. Perception vs reality Skeleton loaders and progressive rendering improve perceived speed. But CPU work and memory usage remain significantly higher than minimal server-rendered pages. This isn’t a critique of any specific framework. We’ve gained: Rich interactivity Real-time collaboration Complex client-side apps But we’ve also normalized multi-megabyte initial payloads as acceptable. Curious how others think about this tradeoff. Is this simply the cost of modern UX expectations, or are we under-optimizing by default?

Older »