On Wednesday, October 24, 2012 at 7:25 PM, John MacFarlane wrote: > Github has wikis for each project. > Example: https://github.com/jgm/pandoc/wiki > > You'd only have to create a 'markdown' project, which needn't have > anything in it but a README.markdown file with a link to the wiki. > Anyone with a github account could edit the wiki. > This seems far easier than any of the other proposals.
I created the markdown (https://github.com/markdown) account on GitHub some time ago. If there's support for John's suggestion, we could create a public repository in that account and use its wiki. David On Wednesday, October 24, 2012 at 7:25 PM, John MacFarlane wrote: > +++ Andrew Pennebaker [Oct 18 12 09:52 ]: > > What I'm saying here is that relying on 3rd parties solutions while a > > very cheap (or even free) VPS would be sufficient is asking for > > unnecessary trouble. > > > > I agree that we should opt for convenient, preferably free hosting. > > I don't mean to start a technical argument about "static" vs "dynamic" > > web pages. What I'm trying to convey is that GitHub, while an > > incredibly easy CMS, only supports static web pages, not wikis, which > > require a running system that can modify a database for wiki edits. > > > > > Github has wikis for each project. > Example: https://github.com/jgm/pandoc/wiki > > You'd only have to create a 'markdown' project, which needn't have > anything in it but a README.markdown file with a link to the wiki. > Anyone with a github account could edit the wiki. > This seems far easier than any of the other proposals. > > _______________________________________________ > Markdown-Discuss mailing list > [email protected] (mailto:[email protected]) > http://six.pairlist.net/mailman/listinfo/markdown-discuss > >
_______________________________________________ Markdown-Discuss mailing list [email protected] http://six.pairlist.net/mailman/listinfo/markdown-discuss
