Ask HN: How do you keep track of links/docs/assets relating to a project?
For a given project, we always create directory pages. We used to use Confluence for this, then we moved to GitHub Wiki pages, and now Dropbox Paper. We add links to Figma mockups, Miro boards, Google docs, Trello boards, contact info for clients, etc.
I feel like there must be a better way though. We end up with long documents where you have to scroll and scroll, and everyone has different ideas about how to organize them, well-meaning overzealous teammates litter in links to very peripheral resources, things get out of date, and it all devolves.
Is this a problem other people have? What tools and techniques do you use to keep it manageable?
5 comments
[ 2.6 ms ] story [ 24.7 ms ] threadIt suffers from many of the same problems, but having it be in the same directory/editor that I'm making a code change makes it more likely that I'll update.
But often it's a project manager or a designer or a researcher adding meeting notes, or recordings of usability testing sessions, etc, and at that point the repo seems less obvious a choice.
As a dev, I still want easy/quick access to all of that (and I want to know and be reminded that it all exists in the first place), but the repo, and even the GitHub wiki for the repo both seem not quite right for this.
It's a wiki / google doc crossover. It has a hierarchical side-navigation, tracks edits, supports inline tables/embeds, multiple users, sharing documents.
Nice editing system. It uses "blocks" of content that can be indented.
It has a full desktop app on Windows and OS X.
(Apparently there was a mention in an similar thread 10 mos ago: https://news.ycombinator.com/item?id=18112140)