Wolff

Ridiculously small PHP framework for building web apps 🐺

2 followers

Ridiculously small PHP framework for building web apps 🐺

2 followers

Wolff is a ridiculously small and lightweight PHP framework with useful functions and utilities. It's small, fast, scalable and easy. The perfect solution for building small and medium-sized web applications.

Launch tags:Web App•Productivity•Developer Tools

Launch Team

CloudflareYour next app belongs on Cloudflare Workers. Deploy for free

Promoted

What motivated you to create a PHP framework vs using one that exists? How does Wolfff compare with Leaf PHP? I look forward to looking into Wolfff. There's always something to learn from new frameworks :)

Report

7yr ago

Wolff

Maker

@rayliverified Yes you are right! There's always something new to learn from other frameworks :) Wolff originally started as an experiment, I just wanted to reinvent the wheel after using CMS like opencart and seeing frameworks like Yii, I tought it was fun to play with a system made by myself. But after some time I discover that I could build a robust system with just more hard work and time, I could make a hobby out of it (and yes, the first version of Wolff reaaaally sucked to a point that it didn't even use composer or followed any type of standard). After all that time I decided to use Wolff instead of other frameworks because of it's ease of use, size, speed and multiple utilities, all of this while maintaining a good looking syntax without doing too much magic (like Laravel does some times). I guess that Wolff complies with a space that hasn't been fully covered regarding of PHP frameworks, and that space is about 'medium sized frameworks'... I mean, Wolff it's not small enought like Slim or Leaf PHP because it comes fully bundled with a good number of utilities and features that are necessary most of the time, but it's not too big or 'complicated' like Laravel or Symfony, even its codebase is quite small for what it does (~6k lines of code). For me its size is perfect and I hope more people find it useful :) I just read about Leaf PHP, it seems really great but I guess both Wolff and Leaf are different, the points that I made in the response to @usmc_saluki can be applied in this case too :)

Report

7yr ago

@usmc_saluki @usbac Thanks for the explanation! I took a look last night at Wolfff and it is _very_ lightweight! Great work on the clean documentation and structure. Wolfff would be a great starting place for someone learning PHP frameworks. I like the dependency injection system :) Any plans to add more "magical" features to Wolfff to help it stand out?

Report

7yr ago

Wolff

Maker

@rayliverified Thank you so much for your comments and support. :) And yes! Currently a new authentication feature has just been added. For the future I'm thinking about optimizing the current performance of the framework, adding new functions to the standard library and improving the routing system (with things like attaching views to routes directly). I even have some ideas for the 3.x version that should be released in a more distant future.

Report

7yr ago

@usbac That's really cool! I starred the repo on Github so I'll definitely be following along. Another part of Wolfff I like is the caching. I'm doing a lot of work with code generation so that component was fun to read though. A "magical" feature I'm thinking about is generating a static site skeleton which is distributed to CDNs and then auto generating JS hooks to fill in the dynamic content. What are your thoughts on JAMstack vs PHP?

Report

7yr ago

Wolff

Maker

@rayliverified Great! :) and that feature is a really interesting idea. Regarding the JAMstack, looks like a great solution for building small static sites. I think that both PHP and JAMstack can exists together, yes PHP can partially accomplish what JAM does, but not the other way, I see the JAMstack as a more 'natural' developer tool for building static sites than PHP. In my opinion both technologies are not quite comparable, so both can co exists at the same time without any problem since they have different objectives.

Report

7yr ago

?makers Are there any authorisation/login features out of the box? Or what's the best way to implement it?

Report

7yr ago

Wolff

Maker

@danjames26 The closest feature to it, is the \Utilities\Validation class (http://getwolff.com/doc/2.x/vali...), which you can use to test an array against another array with rules, to verify if the first array meets every rule. But a login utility is currently being done, it should be finished soon for the next versions :)

Report

7yr ago

Wolff

Maker

@danjames26 Hi! I'm glad to announce you that the Authentication utility has been added to Wolff and is available at the new version 2.4. :) docs: http://getwolff.com/doc/2.x/auth

Report

7yr ago

As a regular user of Slim, why should I switch? (Will definitely check this out though)

Report

7yr ago

Wolff

Maker

@usmc_saluki That is a very good question! I haven't read too much about Slim so you are free to correct me :) Both frameworks have a similar routing system and share some other similarities, but Wolff is ahead of Slim in some points and one of them is the abstraction layer builded on top of PHP, like the Core\{Database, Session, Request, Response} classes, those include some useful methods while maintaining a cleaner syntax than pure PHP. If that isn't enough, Wolff comes with a multi language system, a secure template engine, logging utility, maintenance mode, cache for views and a standard library with useful functions related to debugging, strings, numbers and validation. Most of those elements are optimized and even optional, so the performance isn't affected. I see Wolff more like a full bundled framework with a small codebase than a micro framework like Slim.

Report

7yr ago

@usbac I appreciate the added information!

Report

7yr ago

Report

6yr ago

Pros

Cons

Reviews