I find the lack of syntax highlighting a small thing TBH. You can always take the code,
paste it in a gist and put the link in the design document.
I do however find asciidoc much better for structuring complex documentation. For example,
adding a bullet or numbered point section with code/quote sections inside.
Personally, I'd leave it up to individual contributors to decide what they prefer in
terms of markup language, although I agree that a preferable markup language should be
defined in the documentation.
Cheers,
On Oct 30, 2013, at 8:26 PM, Mircea Markus <mmarkus(a)redhat.com> wrote:
On Oct 30, 2013, at 4:49 PM, Manik Surtani <manik(a)infinispan.org> wrote:
> I only suggested AsciiDoc to be consistent with the markup used for our
documentation. Having two different markup syntaxes in use for the project could get
annoying... but yes, I agree that the lack of syntax highlighting on the wiki can be even
more annoying.
If it's only that let's just use markup as it is more mature on github. I'll
update the docs to state that.
Cheers,
--
Mircea Markus
Infinispan lead (
www.infinispan.org)
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
galder(a)redhat.com
twitter.com/galderz
Project Lead, Escalante
http://escalante.io
Engineer, Infinispan
http://infinispan.org