page-carbajal / wpexpress
Requires
- php: >=7.4
- page-carbajal/wpexpress-query: ^1.1.0
- dev-development
- 2.0.7
- 2.0.6
- 2.0.5
- 2.0.4
- 2.0.3
- 2.0.2
- 2.0.1
- 2.0.0
- 1.3.7
- 1.3.6
- 1.3.5
- 1.3.4
- 1.3.3
- 1.3.2
- 1.3.0
- 1.2.5
- 1.2.4
- 1.2.3
- 1.2.2
- 1.2.0
- 1.1.0
- 1.0.0
- 0.6.1
- 0.6.0
- dev-main
- dev-master
- dev-query-streamline
- dev-meta-boxes
- dev-new-models
- dev-settings-page-render-error
- dev-ui-streamline
- dev-version-one
- dev-fix/license-issue-and-update
This package is auto-updated.
Last update: 2024-12-13 05:16:12 UTC
README
For all of you my fellow developers who are not familiar with WordPress.
Instead of trying to sell you into WordPress I'll ask you to do a google search for why wordpress.
Then do the same for other Content Management Systems, read a little, then decide what's better for you.
I will however tell you why I use WordPress to run my Websites.
WordPress powers +25% of the websites on the Internet. This means that 1 of every 4 websites are using it.
Some of the bennefits it gives me:
- Improved time to market
- Easily create Content Networks
- Thousands of themes free and premium
- Thousands of plugins free and premium
- It is already a great blogging platform
- Great UX
- BuiltIn API
- Runs on apache or nginx
- It runs 1/4 of the Internet's websites
- And it is Open Source
What is WPExpress
I like using frameworks like Rails, Laravel and Symfony.
They make me love writing code.
Very smart people wrote hundreds of thousands of lines of code to implement concepts such as Separation of Concern, Convention over Configuration and so on.
I love rake, and artisan. I am infatuated with how Symfony is structured as a set of components rather than a full fledged Framework.
And I also have a thing for composer, autoloading and depedency management.
Last but not least. I worship Mustache and Twig
When you get to know and work in environments as cool as those I have talked about, going back to monolite-style code writing is, HARD.
I found myself having to write similar code across different projects and I decided I wanted to focus on writing meaningful code and abstract the repetitive stuff as much as possible.
I wanted to go from this
$args = array(); $query = new WP_Query( $args ); wp_reset_post_data();
To this
$posts = Query::Posts->limit(10)->meta('field', 'value')->get();
I wanted to use composer, abstraction and chainable methods, and every other thing I love in modern PHP within WordPress. But here's the compromise. I do not want to change WordPress.
I do not want to write my own queries, I do not want to alter the core. I want WordPress to be kept intact. I just want a Framework which will allow me to do more with less.
Less configuration, less plugins, less time to market.
Finally I am writing this framework to allo my self to focus on writing meaningful code.
Quick Start
This small WordPress Frmework is designed to be easy to use.
Start by reading our documentation.
Framework Structure
- Database WPExpress\Query
- Query
- Post
- Taxonomy
- User
- UserRole
- Model
- BaseModel
- BaseTaxonomy
- BaseUser
- BaseUserRole
- BaseRelation May Be
- Contracts
- BaseWordPressFilters (Maybe TBD)
- Admin
- BaseSettingsPage
- BaseWidget
- BaseAPI
- UI WPExpress\UI
- BaseResources
- FieldCollection
- MetaBoxCollection
- HTMLFieldParser
- RenderEngine
- ReactJS (TBD)