It is worth thinking deeply about the relationship between text, humans, human language, language design, code, and computers — in the past, in the present, and in the near future. A great deal is happening in that space, and the pace of change is accelerating.
Let’s begin with something simple: the humble word and the: - Use of Markdown
As an example, the emphasis above demonstrates how Markdown enables both a natural reading experience and an additional layer of structure. A reader can either follow the text sequentially, or visually scan and pick out the author’s intended highlights. This dual readability — plain text and stylized — is one of Markdown’s quiet strengths.
For beauty and spectacle we require: - Beauty and Spectacle
For the community engagement, and content authoring we require the following functionality: - Text Requirements
Regarding our sense of direction and future goals, we aim to demonstrate a closer integration of code and text through a human-centered interface—one capable of expressing intent through either speech or writing. Our objective is to make the governance of powerful technologies accessible to citizens by enabling participation through carefully constrained natural language systems.
# Conclusion
At present I see no significant disadvantage regarding standardising on markdown, except for those frameworks and languages that are weak at processing text.
For such an environment, it is an additional effort to do the required engineering. However, the wiki should not lack those capabilities — and therefore we should take the path of strengthening our use of and integration with markdown.
# See - Yam and Kson