[LISP] [Web] Let's work on the new Lispweb! [Standard]

We're all sick of dealing with the verbosity of XML/SGML based languages, the inconsistency of CSS and the overall badness of Javashit. Transcompiling to any of these languages is just a half-assed try at sugarcoating a turd.

Post your ideas for syntax/semantic rules, document structure, protocols, rendering techniques or anything relevant to the topic.

Hopefully we will be able to create a basic clone of /prog/ using the newly designed languages. No need to work on retarded features like animations or ``single page applications'' because this project is aimed exclusively at EXPERT PROGRAMMERS.

>>69
For instance imagine you have a website with French poetry translated to English side-by-side as is often seen in books.

It would make sense to indicate part of the text should not be automatically translated, while the other part should. Leaving it to the browser to detect the language of the entire document and try to translate everything is an inferior approach.

It might make sense to differentiate the language of a piece of text and whether it would make sense for it to be translated; however I didn't want to imply a browser would be forced not to translate something just because it was meant to be taken literally. It's a thin difference so I went with the simpler route.