With some delay, but I made it. I'm happy to announce that Phoenix Template Engine version 1.0.0 is now available. This is the first version that I consider stable and that comes with the functionalities I wanted. Moreover, I spent time on a complete rebranding, where I redesigned the logo, the presentation website, and the documentation.

What is Phoenix?

Phoenix is an open-source template engine created entirely by me for Spring and Spring Boot that comes with functionalities that don't exist in other market solutions. Furthermore, Phoenix is the fastest template engine, significantly faster than the most used solutions such as Thymeleaf or Freemarker.

What makes Phoenix different?

Besides the functions you expect from a template engine, Phoenix also comes with features that you won't find in other solutions. Just a few of the features offered by Phoenix:

• An easy-to-use syntax that allows you to write Java code directly in the template. It only takes one character (the magical @) to differentiate between HTML and Java code.

• The ability to create components (fragments, for those familiar with Thymeleaf) and combine them to create complex pages. Moreover, you can send additional HTML content to a fragment to customize the result even more.

• Reverse Routing (type-safe routing) allows the engine to calculate a URL from the application based on the Controller and input parameters. This way, you won't have to manually write URLs, and you'll always have a valid URL. Additionally, if the mapping in the Controller changes, you won't need to modify the template.

• Fragments can insert code in different parts of the parent template by defining sections. This way, HTML and CSS code won't mix when you insert a fragment. Of course, you can define whatever sections you want.

• You can insert a fragment into the page after it has been rendered. Phoenix provides REST endpoints through which you can request the HTML code of a fragment. Phoenix handles code generation using SSR, which can then be added to the page using JavaScript. This way, you can build dynamic pages without having to create the same component in both Phoenix and a JS framework.

• Access to the Spring context to use Beans directly in the template. Yes, there is @autowired directly in the template.

• Open-source

• And many other features that you can discover on the site.

Want to learn more?

Phoenix is open-source. You can find the entire code at https://github.com/pazvanti/Phoenix

Source code: https://github.com/pazvanti/Phoenix
Documentation: https://pazvanti.github.io/Phoenix/
Benchmark source code: https://github.com/pazvanti/Phoenix-Benchmarks