Repository
https://github.com/designcise/bitframe
BitFrame PHP Microframework
BitFrame is a free, opensource, PHP microframework that's:
- PSR-15 and PSR-7 compatible middleware microframework for PHP;
- Highly customizable and event driven;
- Simple to learn, use and implement;
- Follows the PSR standards and integrates the best of existing opensource frameworks wherever possible.
BitFrame's approach of making the middleware dispatcher the core component of the framework encourages the developer to use middleware-based services that plug right-in with ease. This allows for great flexibility especially in terms of debugging, replacements and updating. This design pattern is particularly advantageous for long-term and strategic projects because as they grow in complexity the underlying framework helps keep things well-organized, easy-to-manage and very simple.
At the core of BitFrame's development, the focus has been to abide by some simple rules that are mostly found missing in other microframeworks:
- Be well-documented and intuitive;
- Facilitate the developer and be nonintrusive;
- Be free of unnecessary bloat;
- Promote modularity to allow any component of the framework to be easily replaced;
- Provide the flexibility of using existing PSR-15 / PSR-7 middlewares that plug right in easily;
- Provide the ability to share variables and application data seamlessly across all the middlewares.
Requirements
- PHP 7.1.0 or newer
- Webserver with URL Rewriting (such as Apache or nginx)
- Composer
To get started with BitFrame, read the documentation available at the BitFrame Official Website.
Contribute
- File issues at https://github.com/designcise/bitframe/issues
- Issue patches to https://github.com/designcise/bitframe/pulls
- For general inquires, submitting a bug or security issues, requesting to join the dev team or to request a new feature use the contact form at https://www.bitframephp.com/contact
To make contributions to the code, please refer to the following guidelines:
Pull Requests
- Fork the BitFrame Framework repository;
- Create a new branch for each feature or improvement;
- Send a pull request from each feature branch against the version branch for which your fix is intended.
It is very important to separate new features or improvements into separate feature branches, and to send a pull request for each branch. This allows each feature or improvement to be reviewed and merged individually.
Style Guide
All pull requests must adhere to the PSR-2 standard.
Unit Testing
All pull requests must be accompanied by passing unit tests and complete code coverage. The BitFrame Framework uses PHPUnit for testing.
Roadmap
- Update code to be consistently compatible with PSR standards;
- Phase out support for PSR-7 style middlewares when PSR-15 middlewares become widely adopted;
- Create add-ons that assist developers in creating commonly used components (such as a mailer, cache, access control, etc.);
- Optimize to be lighter and faster;
- Branch out event manager to its own repository when PSR-14 draft is accepted.
Hi @designcise, welcome to Utopian! It looks like a cool project - however there are some things I should note about our guidelines, specifically those for the development category.
Currently we only consider commits made in the last 14 days for development contributions when determining its score, so that means that in your case there is only 1 "eligible" commit.
What we normally expect to see in a contribution is for example a newly added feature(s) with all the relevant commits or PRs linked within the body of the post.
Since you want to introduce your project I think the blog category would be a better fit for now, since they are specifically looking for posts that include a project's introduction.
Once you have added e.g. a feature in the last 14 days you can create a development contribution about it of course (I would definitely recommend reading this amazing guide made by one of our moderators before doing so).
Good luck with your future contributions and I hope to see you back in the development category soon!
Need help? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Would editing the tags for this post from "development" to "blog" be a sufficient, or do I need to create a new post altogether?
Thanks!
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
I would recommend you create a new post, because this one has already been marked as reviewed. Maybe you can also contact the blog community manager @roj on Discord (roj#7486) before creating a new post, since he might have some thoughts about how you could edit the above post so it suits the blog category more (always worth a try). Good luck!
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Thanks!
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Thank you for your review, @amosbastian!
So far this week you've reviewed 12 contributions. Keep up the good work!
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Congratulations @designcise! You received a personal award!
You can view your badges on your Steem Board and compare to others on the Steem Ranking
Vote for @Steemitboard as a witness to get one more award and increased upvotes!
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit