Re: [Coapp-developers] Awesome documentation for CoApp

2011-12-19 Thread Mateusz Łoskot
2011/12/19 Garrett Serack : > I'll be pushing out the new website today (with a lot of pages to be filled > in over the next couple weeks) Looking forward to trying it out! > It creates pages out of github-flavored-markdown--including the > triple-backtick (```) syntax-highlighed > source code

Re: [Coapp-developers] Awesome documentation for CoApp

2011-12-19 Thread Garrett Serack
; for contributing new documentation (and make any modifications to the website organization if required) G From: Mateusz Łoskot [mate...@loskot.net] Sent: Friday, December 16, 2011 3:44 PM To: Adam Baxter Cc: coapp-developers@lists.launchpad.net; Garr

Re: [Coapp-developers] Awesome documentation for CoApp

2011-12-16 Thread Mateusz Łoskot
2011/12/16 Adam Baxter : > So into the wiki idea, add approved revisions - that way you get the > benefits of wikis with some versioning and publishing. I think it's a good idea. Simply, if there is: a) well-defined workflow of documenting CoApp b) stable frame for documentation structure set then

Re: [Coapp-developers] Awesome documentation for CoApp

2011-12-16 Thread Adam Baxter
So into the wiki idea, add approved revisions - that way you get the benefits of wikis with some versioning and publishing. On Dec 17, 2011 9:52 AM, "Mateusz Łoskot" wrote: > 2011/12/16 Garrett Serack : > > Well, since I'm going to spend the next week or so writing docs, I'll > start by chiming i

Re: [Coapp-developers] Awesome documentation for CoApp

2011-12-16 Thread Mateusz Łoskot
2011/12/16 Garrett Serack : > Well, since I'm going to spend the next week or so writing docs, I'll start > by chiming in. > > The wiki's not a bad place to start (GitHub's wiki is Markdown, so that's a > good thing). GitHub Wiki is great. My concern is about using Wiki in general as a first-con

Re: [Coapp-developers] Awesome documentation for CoApp

2011-12-15 Thread Garrett Serack
Well, since I'm going to spend the next week or so writing docs, I'll start by chiming in. The wiki's not a bad place to start (GitHub's wiki is Markdown, so that's a good thing). But I think since it's so easy to write Markdown, (and we can add images, etc) we should just start creating pages