I’m using a wiki for a similar use case.
The good thing: You can build the site architecture/organization/navigation yourself.
The bad thing: You have to build the site architecture/organization/navigation yourself.
Almost any wiki should be suitable for your case, but it’s worth looking into details you care about.
Wikipedia has a list and comparison of wiki software. The site wikimatrix.org allows to compare wikis based on selected features/requirements.
Don’t underestimate the look and feel. For such a wiki to really make sense, you should visit and edit it often. But if editing is no fun (i.e., not easy/quick, ugly, bad usability) for you, you might defer it or stop after the first few days of enthusiasm.
Personally, I’m using WikkaWiki (
daily hourly for several years, have created around 2000 pages with more than 35000 edits):
- PHP, MySQL.
- Fast, little cruft.
- Comes with syntax for code blocks (
%% your code here %%) and supports syntax highlighting (
%%(php) your PHP code here %%). You can even specify a file name (which also allows to download the code file) and starting line numbers (
%%(php;15;test.php) your "test.php" here, starting from line 15 %%).
- Its default editor supports Tab (if you like to indent code that way).
- Because the URLs are "beautiful", you’ll be able to directly enter the URLs of pages you want to visit/edit (which saves a lot of time, thanks to browser’s autocomplete):
Possible drawbacks: rather slow developing process (which is good for me, as long as the project is not dead); no full Unicode support (the next version, 1.4, will switch to full UTF-8; but almost everything should work just fine even now).
DokuWiki is another nice wiki. It’s also FLOSS, uses PHP, but it doesn’t require a database (saves all wiki pages in text files).