Tools like Userdoc (https://userdoc.fyi) help in a few ways, you can easily create requirements (stories, personas, journeys, test cases), but also reverse engineer existing source code into detailed docs, then ask natural language questions etc. AI helps us plan our product in Userdoc, and our devs connect via MCP to bring those requirements directly in to Cursor (full disclaimer, I work at Userdoc - but we eat... - Source: Hacker News / about 1 year ago

Userdoc has versioning of stories and acceptance criteria, aimed to at helping this exact issue https://userdoc.fyi (transparency: I’m the founder). - Source: Hacker News / over 1 year ago

I'm interested to hear how other people are using tools to help them, we've been playing with userdoc.fyi and having good success, but there are just so many AI related tools I feel like I can't keep up! Source: about 3 years ago

Great read, I spent years thinking requirements should live somewhere like Jira, and I feel for many teams this is the case. But as the author mentions, Jira contains tasks related to bugs, text changes, colour changes etc.. These are not product requirements per se. Like the author, I came to the conclusion requirements are best kept in a requirements management system, that integrates with your project... - Source: Hacker News / about 3 years ago

I built Userdoc (https://userdoc.fyi) a requirements management system for software projects. After running a development consultancy for 8 years, I wanted a dedicated system for gathering and confirming requirements, and only syncing them with project management tools like Jira when they are ready (but keeping them in Userdoc as the living documentation and source of truth. Things are going well, we have some... - Source: Hacker News / about 3 years ago

I had wanted to use Gitbook for blog/wiki[0] but then discovered that it's not opensource anymore. After not finding anything for a long while finally found something close that will work for me: Docsify[1]. Docsify is git-backed but not a static site generator. Instead it reads the markdown as-is and renders to HTML/DOM (don't know the details) in the browser. I had 2 problems with it, first the sidebar... - Source: Hacker News / 11 months ago

I built a fast, responsive, and lightweight static documentation site powered by Docsify, hosted on AWS S3 with a CloudFront CDN for global distribution. The entire infrastructure is managed using Pulumi YAML, allowing me to declaratively define and deploy resources without writing any imperative code. - Source: dev.to / over 1 year ago

Okay new plan, does anyone know how to do this docsify on github? I obviously am a noob on github and recently on reddit. I'd like to help where I can but my knowlegde seems to be my handycap. I could provide you a trash-mail, if you need one, but I need a PO (product owner) to manage the git... I have no clue about this yet (pages and functions and stuff). Source: about 3 years ago

Good idea. Instead of bookstack, I recommend something like Docsify The content is all in Markdown and can be managed in a git repo. Easy to deploy the whole website to any simple static HTTP server - or even Github pages. This way you can review contributions and have good version control. Source: about 3 years ago

The tools to author it aren't that important, frankly. Ask your audience what they're most comfortable using and try to meet them there. If the stakeholders are technical, you have more options. If they aren't, I hope you like Google Docs or Word, because if you give them anything other than that or a PDF, they'll probably complain. At worst, yeah, write it in a long Markdown text file and use tools like pandoc to... - Source: Hacker News / over 3 years ago