3 ms·
I admire your initiative, but "structure" -- at least as you describe it here -- is not a problem. It's a solution to the problem of organizing content. Don't y
by antics 16y ago
I admire your initiative, but "structure" -- at least as you describe it here -- is not a problem. It's a solution to the problem of organizing content. Don't you think?
The question is, are Wikis the best answer to this problem? They're really very good at helping us categorize things that are very differentiable, and very definable. For example: The Hundred Years War make a good article in a wiki. "How to raise angel investors" does not. Instead, people write articles about it, and you take what you want out of them.
Why don't we start with an HN faq, much like the Reddit programming faq [http://code.reddit.com/wiki/help/faqs/programming http://code.reddit.com/wiki/help/faqs/programming], and if that's successful, we can build from there. My philosophy is: address specifically the problem that you (or someone) has (i.e., "I have questions, and don't know where to begin!"), because spreading out too much or being too ambitious can literally kill a project. Don't take my word for it: the svn guys talk about how those sorts of projects were the "worst" parts of SourceForge: [http://code.google.com/events/io/2009/sessions/MythGeniusProgrammer.html http://code.google.com/events/io/2009/sessions/MythGeniusPro... <-- somewhere in there]
So let's start with a specific need and address that. Once again, I'd be happy to help you if you elect to go forward, but we need to attack one thing at a time.
- jdc 16y agoI actually have no attachment to structuring this information as a wiki, but I know of no better readily available, collaborative information sharing software. Problems of structure (front or backend) and organizing the content are the inseparable in my mind.