Hi, I am the creator of Glyph, thanks for the mention :-) Glyph can be used in many different ways, either on its own (it can be effectly used as an alternativ

Hi, I am the creator of Glyph, thanks for the mention :-) Glyph can be used in many different ways, either on its own (it can be effectly used as an alternative HTML syntax) or in conjunction with existing lightweight markups like Textile and Markdown. When I originally thought about creating a document authoring framework, all I wanted was to extend Textile so that it could handle section. Soon afterwards, I realized I wanted more than that. I wanted the ability to reuse content through snippets and even the possibility of creating my own macros easily, so I ended up creating a new language. How heavily you use glyph is entirely up to you. If you like Textile and Markdown, you can just use some of the core macros and sections. For example: md_section[ @title[Test Section #1] This is basically a titled div where you can use _markdown_. ] txt_section[ @title[Test Section #2] Here, instead, you can use *Textile*. ] In this way yes, Markdown and Textile are second-class citizens, but this is a good thing, in a way. Glyph is markup-independent so you can use them both, if you like, and even create additional filters if you want. Regarding the syntax, I wanted something very basic (and easy to parse :P) but usable. Sometimes it may get a bit heavy, but on the other hand you can create macros for complex formatting, i.e. custom tables. At any rate, if you have any ideas on how to improve Glyph PLEASE do contact me! I'm always looking for constructive feedback!