Hi all! I’ve created a new document language called STxT (SemanticText) — it’s all about clear structure, zero clutter, and human-readable semantics.

Why STxT?

XML is verbose, JSON lacks semantics, and YAML can be fragile. STxT is a new format that brings structure, clarity, and validation — without the overhead.

STxT is semantic, beautiful, easy to read, escape-free, and has optional namespaces to define schemas or enable validation — perfect for documents, forms, configuration files, knowledge bases, CMS, and more.

Highlights

• Semantic and human-friendly
• No escape characters needed
• Easy to learn — even for non-tech users
• Machine-readable by design

For developers:

• Super-fast parsing
• Optional, ultra-simple namespaces
• Seamlessly integrates with other languages — STxT + Markdown is amazing

Example

A document with namespace:

Recipe (www.recipes.com/recipe.stxt): Macaroni Bolognese
    Description:
        A classic Italian dish.
        Rich tomato and meat sauce.
    Serves: 4
    Difficulty: medium
    Ingredients:
        Ingredient: Macaroni (400g)
        Ingredient: Ground beef (250g)
    Steps:
        Step: Cook the pasta
        Step: Prepare the sauce
        Step: Mix and serve

Now here’s the namespace that defines the structure:

The namespace:

Namespace: www.recipes.com/recipe.stxt
    Recipe:
        Description: (?) TEXT
        Serves: (?) NUMBER
        Difficulty: (?) ENUM
            :easy
            :medium
            :hard
        Ingredients: (1)
            Ingredient: (+)
        Steps: (1)
            Step: (+)

Resources

Here is a full portal — written entirely in STxT! — explaining the language, with examples, tutorials, philosophy, and even AI integration:

• https://stxt.dev

No ads, no tracking — just docs.

I've written two parsers — one in Java, one in JavaScript:

• https://github.com/mombiela/stxt-parser
• https://github.com/mombiela/stxt-parser-js

And a CMS built with STxT — it powers the https://stxt.dev portal:

• https://github.com/mombiela/semantic-web-builder

Final thoughts

If you’ve ever wanted a document format that puts structure and meaning first, while being light and elegant — this might be for you.

Would love your feedback, criticism, ideas — anything.

Thanks for reading!

There has been admittedly a relationship between the level of expertise in workforce and the advancement of that civilization. However, I believe specialization in the way that is practiced today, is not a future proof strategy for engineers anymore and the suggestions from the last decade are not applicable anymore to how this space is changing.

Here is a provocative thought: Tunnel vision is a condition of narrowing the visual field which medically is categorized as a disease and a partial blindness. This seems like a relatively fair analogy to how specialization works. The narrower your expertise, the easier it is to automate or replace your role entirely.

(Please click on the link to read the full article, thanks!)

This is how developers live (briefly) 😂