DEV Community

Cover image for The New YINI Homepage Is Live — A Modern, Human-Friendly Config Format
Mr Smithnen
Mr Smithnen

Posted on • Originally published at yini-lang.org

The New YINI Homepage Is Live — A Modern, Human-Friendly Config Format

#config #programming #webdev #opensource

Hey everyone 👋

I’m excited to share that the new homepage for YINI config format↗ is now live!

YINI is a modern, structured, human-friendly configuration format that tries to bring together the simplicity of INI with the flexibility of YAML.

🧩 What Is YINI?

YINI was designed to make configuration files both readable for humans and consistent for machines.

It takes inspiration from INI, YAML, and JSON — but simplifies the rules while still supporting modern features like:

  • Nested sections using clear markers (^, ^^, etc.)
  • Arrays [1, 2, 3] and objects { key: "value" }
  • Inline and full-line comments
  • Strict and lenient parsing modes 
^ App
name = "Demo"
features = ["search", "dark-mode"]

^^ Server
host = "0.0.0.0"
port = 8080
Enter fullscreen mode Exit fullscreen mode

🌐 The New Homepage

The new site — yini-lang.org ↗ — brings everything together:

  • 🧭 Get Started guide
  • ⚙️ Quick Tutorial with examples
  • 📘 Full Specification
  • 💡 FAQ and explanations

It’s built with Astro + Tailwind, and designed to be fast, clean, and accessible — the perfect home for YINI as the ecosystem continues to grow.

📦 The YINI Ecosystem

  • yini-parser-typescript — the official TypeScript parser library
  • yini-cli — a simple CLI for parsing, validating, and converting YINI files
  • Specification — now at v1.0 RC stage, aligning parser behavior with the spec

Both projects are open-source on GitHub under @YINI-lang ↗

🗣️ Feedback Welcome

This is still early days for YINI, and community feedback is incredibly valuable.
If you’d like to try it out, explore the homepage, or contribute ideas, you’re more than welcome!
👉 Visit the homepage → yini-lang.org
👉 Check the parser on GitHub → yini-parser-typescript

Thanks for reading — and for helping shape a cleaner, more predictable future for config files 💡

— Marko Seppänen

Top comments (0)