1
2 Comments

Feedback on my documentation?

Hey all!

I released the documentation for Nodewood last week, and I'd love some feedback on it. The marketing site is a fairly heavily-customized VuePress instance, so I'm not really looking for feedback about style or layout (unless that's confusing and can be improved without, say, switching to an entirely different tool).

More specifically, I'm interested in if the actual documentation itself is confusing or lacking. Do I need more code examples? Less? Did I not explain basic concepts before jumping into advanced ones? I know that because I'm so close to the subject matter, things that seem obvious to me might not be obvious to first-timers.

I know this is a big ask (since that's a lot of text to read), so any feedback, even small feedback is welcome. I'd just love a chance to hear about it and fix it before I launch and actual users start trying to use it.

Thanks!

  1. 1

    Funny - I was just about to write a post on where to find examples of good documentation online.

    Yours is brilliant! I'll definitely use it as inspiration if you don't mind.

    1. 1

      I don't mind at all! And if you have any VuePress questions (if you do go with VuePress), don't hesitate to ask! There's a lot of weird little edge cases I found out about only through trial and error.

Trending on Indie Hackers
Getting first 908 Paid Signups by Spending $353 ONLY. 24 comments I talked to 8 SaaS founders, these are the most common SaaS tools they use 20 comments What are your cold outreach conversion rates? Top 3 Metrics And Benchmarks To Track 19 comments How I Sourced 60% of Customers From Linkedin, Organically 12 comments Hero Section Copywriting Framework that Converts 3x 12 comments Join our AI video tool demo, get a cool video back! 12 comments