Improvements

[ziadoz]

Future Improvements

• [x] Split out Text and Numbers category into Strings and Numbers.
• [x] Add Configuration category.
• [x] Add Functional Programming category.
• [x] Break out Code Analysis into Debugging where applicable.
• [x] Rename ORM and Datamapper category to Database.
• [x] Split out password libraries into own category.
• [x] Add all major PHP framework components to the list (https://github.com/ziadoz/awesome-php/issues/90).
• [ ] Add C/PECL extensions category (https://github.com/ziadoz/awesome-php/issues/2).
• [ ] Display license for each project (https://github.com/ziadoz/awesome-php/issues/14).
• [x] Add community members section.
• [ ] Add a conferences section.
• [x] Add Framework Bundles category (SF2, LV4, ZF2).
• [ ] Build a website for the project (https://github.com/ziadoz/awesome-php/issues/94). Flatfiles. JSON files. Compiled into a website via a template.
• [x] Work out how to support multiple languages (possibly related to building a website).
• [x] Move 'Contributing' text to the top of the document (https://github.com/ziadoz/awesome-php/pull/220).
• [x] Go through all categories and perform a cleanup and cull.
• [ ] Add legend/dagger for paid components and framework components.
• [x] Remove PHP Reading (often end up outdated), Other Websites and Other Books (too broad) sections. ***
• [ ] Add a pull request template.
• [ ] Link to other Awesome PHP lists (https://github.com/FriendsOfCake/awesome-cakephp, https://github.com/jakoch/awesome-composer).
• [ ] Add Awesome branding badge.
• [ ] Consider Github discussions section.

[ziadoz]

C/Pecl Extensions Swoole: https://github.com/matyhtf/swoole (https://github.com/ziadoz/awesome-php/issues/108) SCrypt: https://github.com/DomBlack/php-scrypt (https://github.com/ziadoz/awesome-php/pull/91) PThreads: https://github.com/krakjoe/pthreads Graceful/ViolentDeath (https://github.com/ziadoz/awesome-php/pull/118, https://github.com/ziadoz/awesome-php/pull/119) DoubleMetaPhone: http://pecl.php.net/package/doublemetaphone (https://github.com/ziadoz/awesome-php/issues/102) Asynchronous Resolver: http://pecl.php.net/package/ares LibSodium: https://pecl.php.net/package/libsodium PHPTrace: https://github.com/ziadoz/awesome-php/pull/341

Framework Bundles SF2 Gearman Bundle: https://github.com/ziadoz/awesome-php/pull/141 SF2 Elcodi and PaymentSuite: https://github.com/ziadoz/awesome-php/pull/140

[bordoni]

@ziadoz love the idea of license display.

How to list all framework components? This page would get too long, Am I wrong??

[ziadoz]

@bordoni I'm not sure if I'll do this yet. I'm concerned it might clutter the list and be difficult to keep track of.

[ziadoz]

French PHP Resources: https://github.com/ziadoz/awesome-php/pull/334 https://github.com/ziadoz/awesome-php/pull/335

[Arteneko]

@ziadoz about framework components, why not make a subdirectory of md files, each of them dedicated to a framework and listing components with some infos like the README.md ?

[dereuromark]

Or those frameworks project their own list you can link to - e.g. awesome-cakephp for CakePHP. Depends on the framework and if they already have their own list. Ideally, the frameworks should own those specific lists, and it will also be less work for you to mainain them (they would otherwise become outdated over time).

[rudinandrey]

https://fatfreeframework.com/3.6/home look at this amazing framework F3. This is the best of the best :-)

[ziadoz]

Or those frameworks project their own list you can link to - e.g. awesome-cakephp for CakePHP. Depends on the framework and if they already have their own list. Ideally, the frameworks should own those specific lists, and it will also be less work for you to mainain them (they would otherwise become outdated over time).

@dereuromark Linking to separate awesome lists for framework specific bits sounds like a good idea. If you open a PR I'll take a look. Thanks!

[aman00323]

@ziadoz I have a thought in my mind to make this package more accurate.

• Some of the packages might have not been maintained for too long or they have been archived.

Suggestion

• We will have a cron job running which will be checking for the last commit, archived or not, etc.
• If it is been archived and most popular then we can have a separate section there which will be automatically updated by the bot. (which we need to develop :smile: )
• Also we can display when the last version is released beside package names.

Let me know what do you think about this idea.

[ziadoz]

@aman00323 What you are suggesting is an interesting idea, and it's something that has crossed my mind - I actually wrote a prototype, a long time ago. However, I think it's beyond the scope of this project. I already struggle to maintain this list in a timely manner, without the addition of code.

Perhaps it would be better to open an issue or pull request on the Awesome Bot repository? That's the bot we use to validate links in our Github Actions workflow. Then other Awesome Lists can benefit from the same functionality. Thanks.

[tslol]

Bramus Router is a good router to use, one that I have been using in some of my projects. A little older but not a bad option