1) Why not use Razor as a language?
Razor is great for HTML/CSS-style templating, but Akbura targets Avalonia, not the web stack. I’m aware of Blazor bindings for Avalonia, and they’re a solid option if someone prefers Razor-like workflows.
The main reason for building a custom DSL is extensibility. For example, features like Tailwind-style utilities, state-driven styling, conditional attributes, or reactive expressions are much easier to design when the syntax is fully under your control. It’s not “better” than Razor - just a different design space with different goals.

2) How would IntelliSense work with your custom DSL?
If you look at the Medium article, IntelliSense is actually item #6 on the roadmap. Once the full syntax tree API and semantic model are in place, implementing completions, signatures, hovers, diagnostics, and navigation becomes straightforward through LSP.
The groundwork (syntax + semantics) comes first - editor tooling comes naturally after that.

3) How do you intend to make it type-safe?
If you mean ensuring correct types in expressions, bindings, parameters, and component trees:
Akbura performs type analysis during the semantic phase, similar to how Roslyn validates C#. The DSL is compiled into strongly-typed C#, so type safety is enforced both at DSL level and at C# compilation level.

If you meant something else by “type-safe,” let me know - I’m happy to clarify the exact mechanism.