I had started coding and using the previous WordPress interface back in 2018. Since then, I’ve noticed that Semantic UI is no longer being developed (instead, it continues through various forks), increasing performance issues on the WordPress side (a problem originating from me due to extensive customizations), and problems I’ve encountered while writing (such as tab closures, link disconnections, or issues during version creation, which caused my articles to be sent to void before being saved). As a result, I’ve had a plan for changes for some time now.
My main elements of this change plan were at the top of my Grav and Bulma CSS notes. So, why?
Interface and CMS Change
For more detailed information about Grav, please see my article titled What is Grav?.
Grav - Transition from WordPress
For a long time, I’ve been working with WordPress, creating themes and plugins. However, I was at a new stage of development. The first reason was my desire to store content in a file-based system, rather than a database, allowing me to perform operations easily. This enables me to carry out many text processing tasks via the command line. Additionally, having images and content together simplifies content management. Markdown ensures content is created according to specific template rules. As a result, instead of having different formats within a piece of content, you’re forced to follow a common path. So, why Grav? Of course, there are many content management systems based on text. However, only a few of the alternatives offer multi-language and multi-website capabilities. On the other hand, you can intervene in Grav’s behavior through YAML lines, which means you need very little code. Of course, there are also shortcomings, but you can find a solution in a way.
Given these features, I can confidently say that Grav is tailor-made for UI designers and web design agencies. You can quickly build high-performance websites. Soon, I’ll be sharing an educational session on Grav theme development. As a subscriber to our email newsletter, you’ll be able to stay updated on the latest developments. During this transition process, if you decide to use Grav themes, you can take a look at the Medi and Appco themes, or reach out to me directly via this link to request a new theme.
I’ll also share my experiences during this transition process (such as converting content to Markdown format, cleaning operations, etc.). Particularly, thanks to my Node.js solution, which I previously detailed in my article “Converting WordPress Content to Markdown”, I was able to complete this process very efficiently.
Bulma CSS - Semantic UI Migration
Semantic UI is a CSS framework that offers many features and is quite enjoyable to work with. However, after its last update in January 2018, development of the project was abruptly halted without any explanation. Of course, the project continues through various forks, but as you know, such issues significantly erode confidence in a project and can lead to support challenges, making it time to evaluate alternatives. Among the alternatives were Bulma CSS and Tailwind CSS1. Having previously used both Bulma CSS and Buefy2 in numerous different projects, I decided to go with continuity.
So, what changed with the new interface?
New Features
I’ve expanded the content section with frequent code examples and tables, but I haven’t yet finalized its structure. For now, I’ll present the content in this format, and I’ll implement refinements gradually. You’ll see various icons alongside article headings, representing different content types: videos, podcasts, code samples, and limited content. I’ll reevaluate all content in the most suitable format (video or podcast) over time. Additionally, some article series will be limited and accessible to donors/supporters.
You can easily view the application, plugins, and themes from the homepage. I’ve reorganized the educational content, and you can follow it via the homepage and the trainings page.
Webflow > Jobs3 section’s photo display (one of Webflow’s UI features) really caught my attention. I created a simplified version and used it in the about me section. Due to a small spark it inspired, I’ll gradually add more features (I still need to resolve a few issues on the DOM side), and eventually share the final version.
For now, these are the topics I can share. Don’t forget to leave your comments. If you’d like to contribute to content continuity, you can explore the options via Buy me a coffee.