mopires

Yes. But it truly doesn't have angle brackets. At the moment, the features that make it different from pure html are its feature tags and config tags. For example !doctype, meta viewport are built in. Stylesheets and javascripts can be attached with feature tags. Such as style and javascript, respectvely. It may seem that is not that much for now, but as more features are added it will be handy and rubust. One of the goals are to deliver a better development experience.

About that... I think I got ahead of myself and forgot about this detail. I'm working on this. And will comment on this post when it's public.

Thank you for you appreciation! I'm very proud of this project. Thank you for the upvote.

Thank you sir. Closing tags are a very good feedback about the domains of a tag.

Also, if we remove closing markup, the only way to understand if a markup is closed woud be by checking if a new markup is open. That doesn`t seem efficient.

Shorthand definitions would be a good feature to be added, but it needs refinement. We need to think carefully about how to implement in a way that would fit gracefully with the syntax and with the developer experience.

That`s correct. It`s not sensitive to anything. Just open and close tags. It is less noisy that way. Removing the bracktes, not replacing it by something else.

I have answered this in a previous comment. I'll past here for your convinience.

It's a snippet for the post I'll make about this very point.

https://news.ycombinator.com/item?id=41119414

It's not identation based. Removing the closing tags would just not close anything. Everything would be immediately nested hehe

Right... It's not identation based. Why remove the close tags?

That is a very interesting argument and very well presented. It gave me something to think about. Although, have in mind that this is a markup language. It's not a script language where you will make complex logic. It's intended to make visual elements. I do not intend to add logic implementation to it, like a template engine(ifs, loops,...). The incoming features are for visual elements implementations, like built in clip paths configuration.

I see now that the way I present it is vague. In future post I'll improve the presentation of it.

Thank you for you attetion to detail and for the argument. As humans we are prone to error. With that in mind I think this can be a valuable addition to the markups.

Thank you!

I'm not using identation. I'm actually using closing tags with a "/". For example:

table [...] /table

This is a snippet of a article I'll post about it: "[...] popular preprocessors for HTML out there, have one thing in common. They replace the angle brackets, then add some functionalities on top of it. If the symbols of a tag are problems to the experience of developing a frontend, replacing it for something else doesn't fix the problem. Just change the symbol. Pug, Haml, slim, and some others change the angle brackets by indentation or something else. So now, you have to be careful with indentation and not the angle brackets. Please, don’t get me wrong, those are very well developed preprocessors that are also very well maintained by very skilled people. They deliver what they propose. [...]"

I'm currently building the documentation

Thank you for the suggestion, I've done something like this in early versions. But removed thinking the gif would be enough.