Over the years, we’ve introduced powerful features and enhancements, but not always with a clear focus on what matters most: helping you build and launch full applications quickly. With Leaf MVC v4 on the horizon, it’s time to double down on what Leaf is truly about—being the framework for Makers.
January wasn’t just a month—it was a launchpad. We kicked off 2025 with a bang, making big moves and setting the stage for even bigger plans ahead. We've got only one day left in January, so it's a perfect time to go through the month and see how we did against our goals.
The first half of 2024 was pretty tough—we were juggling our day jobs with Leaf while dealing with a growing number of issues. We had to step back, re-evaluate our priorities, and by the end of the year, we pushed out a ton of updates to make Leaf more stable and reliable. Now that we’ve checked off most of our 2024 goals, we’re excited to share our 2025 roadmap! Our focus is on making Leaf more reliable, secure, and developer-friendly, with plenty of performance improvements along the way.
We published Leaf Auth v3.3 which brings a lot of usability updates in addition to the long awaited Roles & Permissions feature. Here's everything you need to know about v3.3 (🥀 Sea Buckthorn)
They say the best changes are the ones you don’t see coming, and that's exactly the case here. What started as Leaf MVC v3.8 turned into something much bigger—an idea for a major release we couldn’t ignore. In our last article, we talked about how Leaf MVC had strayed from Leaf's simplicity and had rather started trending in the bloated direction. We promised to fix that, and we did. We pared down the framework to its essentials, making it more modular and flexible, but we couldn't resist the urge to optimize even more, and that's how the idea for Leaf MVC 4 was born. Let's dive into the details of what Leaf MVC 4 will look like and how it will change the way you build web applications with Leaf.
Let's talk about MVC. Leaf has first-class support for the MVC pattern, but we've been thinking about how we can make it better. Is MVC a good pattern for building web applications? Is it too complicated? We'd love to hear your thoughts on this.
Welcome to our September issue of the Leaf Catch-Up! Let's take a look at the progress on implementing some of our RFCs and the cool stuff the team has done since our last catch-up. Let's do this!
Over the last few months, we've been testing out different ways to document, share, and respond to your concerns and questions regarding Leaf and its future. We've been using a combination of GitHub issues, Discord, and occasional tweets to keep you updated on our progress. Unfortunately, this has made it difficult for us to keep you in the loop on what we're working on, and for you to share your thoughts and concerns with us. We've been working on a new way to address this issue, and we're excited to introduce Hangouts and Reports.
The first part of this year was tough for Leaf from a development standpoint. Progress was slow, and we found ourselves burdened with a significant amount of technical debt. But it's not all bad news! We're almost back on track and hitting our stride, making up for lost time and working hard to improve Leaf for everyone. In this article, we will share our plans for the final third of the year and the thought process behind each decision. Let's dive in!
Last month we co-hosted the Build First Conference. We used this platform to talk about Leaf, what it is, why you should use it and how to build simple but powerful applications and APIs using Leaf PHP. The event which was co-hosted with SeevCash was a huge success, and this is our recap for those who missed the event.
The Leaf documentation has been partially re-written with a ton of updates to the content and structure. The new docs include more detailed explanations, more examples. The new docs are also more organized and easier to navigate. The new docs also include merged content from Leaf MVC, Leaf API and Skeleton.
We released Leaf 3 early last year. Since then, we've added a ton of functionality and made Leaf 3 even easier to use. In this article, we'll look at how to get started with Leaf, some useful features and a quick-start to building your first Leaf app.
This month, a whole lot of work has been done to improve Eien which was started earlier in October. We added a bunch of features and improved the way Eien works under the hood. Though still in its early stages, Eien is already showing a lot of promise and we're excited to see what the future holds.
Earlier this year, we shared a roadmap for what we had in store for Leaf throughout the year. This article is to take us through what we've been able to achieve, both listed and unlisted on our roadmap.
Eien is Leaf's implementation of a high-speed, high-performance server based on powerful tools like Open Swoole and Swoole. Eien loads your app in memory and shares a state between requests to achieve amazing speeds, up to 40x. Read the docs @ leafphp.dev/modules/eien
Over the past couple of months, we've talked about our plans for Leaf, but never into details. In this post, we share high-level details of our roadmap, so the community can see our priorities and make plans based off the work we are doing.
The official build of Leaf 3 was released on 15th March, and since then, all our packages are updating to use Leaf 3 as the new default. Make sure to read the breaking changes section to see if you need to make certain changes before the switch to Leaf 3.
We've been planning a new release: version 3 of leaf which has been under development for the past couple of months. This post contains everything you need to know about Leaf 3 ⚡️