author: Jane Doe email: email@example.com -- my_content Multi-line embedded content (e.g. markdown) here ... -- my_content states: active = #fff hover = #b6b6b6 # cities Den Haag: 52.069961, 4.302315 Málaga: 36.721447, -4.421291 서울특별시: 37.566984, 126.977041 # cities expanded < cities Springfield: 38.790312, -77.186418
Eno is a data language for all people, not just developers. Its simple syntax and versatile nature welcomes a wide audience, both in regards to cultural background as well as technical ability. Unlike traditional developer- and machine-centric data languages, its type-agnostic design embraces our human superpower - our effortless understanding of context - and thereby makes it one of the easiest data languages to grasp and author content in.
The first draft for what is now known as Eno was sketched out in early 2018 during R&D on a large publishing project around file-based content. It was designed and developed by Simon Repp, and still is to this day. Many contributions were made by people who have offered their cultural, technical and personal insight, reported bugs and submitted code and corrections and set out to develop their own libraries for Eno - I'd like to hereby express my gratitude to you, thanks for your support!
Since mid-2020 a big effort is made to enable usage of Eno with compiled languages (C/C++, Go, Rust, et al). The development of the new C-based reference parser which is the core part of this effort also serves as a vehicle for clearly specifying and thereby resolving the last remaining ambiguities in the specification.
Building on top of the new reference parser, work on a cross-platform parsing code generator is planned for the near-ish future, enabling developers to obtain fully functional data serialization code for multiple languages based on a schema language that is to be defined in the process.
The mid and long term vision is to endeavour for standardization of Eno either through the institutional route or by establishing a de-facto standard through sufficient adoption in a few key projects or products. If you sympathize with this vision, join in to help make it happen!
For concrete technical issues or questions feel free to open issues in the respective repositories. To get in touch directly, write a mail to firstname.lastname@example.org or reach out through the fediverse at @email@example.com.