Jinya Dev Blog

Latest

First version of Jinya Fonts released 🥳

Today we release the first version of a new tool in the Jinya family, Jinya Fonts. Now you probably wonder what Jinya Fonts is. To make it short, it is a drop in replacement for Google Fonts, that doesn't track your users. Public instance We always publish the

Jinya CMS Version 22.1.0 released 🥳

Version 22.1.0 doesn't feature any gigantic changes but rather two improvements for the blog. TG-105 [https://taiga.imanuel.dev/project/jinya-cms/us/105] Add id to category selection This change was small but important, the blog categories allowed to have duplicate names. The issue was, that

Jinya CMS Version 22.0.0 released 🥳

Jinya CMS Version 22.0.0 released 🥳

I am happy to announce, the new release of Jinya CMS version 22.0.0. Lets see what changed in this version user story by user story. TG-76 [https://taiga.imanuel.dev/project/jinya-cms/us/76] Blog feature The most important feature of this release is the blog feature. With

Jinya CMS Version 21.0.0 released 🥳

Jinya CMS Version 21.0.0 released 🥳

It has been half a year since the last major release of the Jinya CMS, and hell did we work on features. Lets go User Story by User Story down the road of new features. #22 [https://taiga.imanuel.dev/project/jinya-cms/us/22] Use proper OPCache config resolution This

Cosmo CSS gets a dark mode

Cosmo CSS gets a dark mode

I always said, adding a dark mode to a website is easy with the new media queries. But I myself didn't deliver that in Cosmo for a nearly eight months. Today Cosmo finally gets its dark mode. What does that mean for Jinya CMS and Jinya Backup? First

releases.jinya.de gets a fresh design

releases.jinya.de gets a fresh design

For most of it existence releases.jinya.de had only a JSON output, which wasn't even delivering the correct mime type. Today the site got a new outfit. I built a simple startpage with a short info what the page is for and buttons to take the user

Jinya CMS unstable

Deploying the current development state of Jinya is rather difficult, you have to update from the main branch on Github by hand everytime a new push happend. That made it rather impossible to keep a consistent development or unstable state for testing in real world cenarios. That is the reason