Thereare other approaches to developing documentation and commentary for ST.Don't Bother
Between the forums and README.txt files in packages, do we need another space? It might be we don't do anything special.Existing SVN/markdown wiki
The current solution, using Google Subversion for source control, and markdown for writing pages. Limited by Google's 1GB hosting allowance.Google Wiki
Google code includes a wiki folder (http://code.google.com/p/sublime-text-c ... /#svn/wiki
) which appears as a wiki at http://code.google.com/p/sublime-text-c ... ges/w/list
I could just mirror this wiki at sublimetextwiki.com, which would mean that you edit using the site at google code. More wiki-like, but text-only, and so offers no real support for embedded resources like images and screencasts.Custom Wiki
This is the one that most intrigues me, but would be the most work. The features would be;
- ST as the editor -- no editing in cramped little textareas; the 'edit' link spawns ST, and saving in ST submits the page content back to the site. This gives you syntax highlighting and the power of packages.
- Editing locked to ST owners -- to combat spam, all submissions would have to come from a purchased copy of Sublime Text. This should block all spam but not block any user who had something to contribute.
- local SVN storage. Rather than using Google Code, I'd set up a SVN repo on my web host, and any submission would go through that. Large resources could be uploaded without going into Subversion.Thoughts?
Those are the ideas I've had so far. I knocked up the current system knowing that it would take me about an hour and would do the job. If we want something better, I'll happily ponder it.