wiki

Is there any simple language similar to Markdown or one of the Wiki Markups that gets converted into HTML form elements? For example: name* = ___________ sex = (x) Male () Female phones = [] Android [x] iPhone [] Blackberry city = {BOS, (SFO), NYC} Would get converted to: <label>Name (required):</label><input type="text" name="name" id="name"/> <label>Sex:</label><input type="radio" name="sex" value="Male" checked="checked"/> <input type="radio" name="sex" value="Female"/> <label>Phones:</label><input type="check" name="phones" value="Android"/> <input type="check" name="phones" value="iPhone"

I was recently put in charge of the wiki for the development team. The wiki is still in its infancy, so I have a lot of room to work with. It goal is to house internal to the development team. Currently, the main piece of information that the wiki holds is Coding Standards. What are some best practices your dev team uses for its internal wiki? What information is important to have on a dev wiki? If you were to go to the wiki for your dev team what information would you expect to see? Is there some information that shouldn't go on the wiki even though it seems like a good idea? -- edit -- Also,

I am collecting quite a lot of material in a GitHub wiki. I really like to use the wiki to cooperate with other people and IMHO the platform is really nice, I like it! So, I would like to keep using the GH wiki to collect stuff, edit, save,etc but I also would like to export the content in order to create a pdf file that we can call "a manual". I would like to generate an updated version of the manual automatically everytime I want just running a couple of scripts, I can not put too much effort on this. I guess it is possible to export the content somehow and the use pandoc ( http:/

Basic requests are: human readable / text format (for easy version control) online (for collaboration) easy formatting (markdown ok, html is too much) strict formatting (so authors don't invent new types of titles, bullets etc.) exportable to PDF, HTML easy backup and deployment (so we can "deploy" to customers site as read only version) We are thinking about using some kind of wiki engine, but it would need to use files for storage or have other means of "deployment" to customer and be easy to install/maintan. Also, it would have to be free / cheap (confluence is way too expensive) Any

If you look here: http://en.wikipedia.org/wiki/Stack_Overflow You'll notice there's a little "Content" section, if you click on one of the links, it will send you to a specific section on the page. How do I do this in GitHub wiki? With Markdown or whatever they use? It is nicely demonstrated in the Table of Contents of the Markdown Cheatsheet . ##### Table of Contents [Headers](#headers) [Emphasis](#emphasis) ...snip... <a name="headers"/> ## Headers If you hover over a Header in a GitHub Markdown file, you'll see a little link simple to the left of it, you can also use that link. The format

I'm looking for a pure javascript, open-sourced, wiki implementation, preferably one using NodeJS. Where might I find it? Rob Raisch I'd suggest jingo thanks to its nice design (with very sane typography), use of git as backing datastore, format compatibility with the markdown format used by github ( gollum ), and the fact that it's somewhat actively developed. As of Jan 2017, Matterwiki is also actively developed. Wiki.js is also being actively developed. It's using a git datastore, has a markdown editor, search engine and assets management. Tiddlywiki can generate static HTML . Npmjs and

How to convert XML to something else using xslt stylesheet? In C++ C# PHP or ActionScript? For example I have this html2wiki xslt stylesheet I want to send to my programm my XML (in this case HTML file ) and get back a file (in this case Wiki mark up text ) So How to translate one text file into another text file using XSLT stylesheet in any language? Pseudocode: Load SOURCE file as XML Load STYLESHEET file as XML Apply STYLESHEET to SOURCE, generating RESULT Write RESULT out to file as XML In Python, libxml and libxslt are my personal choices for this kind of functionality. (Edit) Here is a

I use trac to manage my projects and I'd like to organize wiki pages the same way trac project does, i.e. by category, subcategory, etc. TitleIndex page on trac site gives a good explanation of the result I want to obtain. How do I achieve this? First of all, you can create hierarchically wiki pages, just by modifying the url, and press enter. It is also possible to create a wikilink first, and then press the red link. For example, when your trac home page is http://trac.server.local/project/wiki , you can type /customers at the end of the url, and press enter. So the new url would be http:/