Skip to content

Commit

Permalink
Adjust readme
Browse files Browse the repository at this point in the history
  • Loading branch information
atanas-dev committed May 22, 2020
1 parent f8b725a commit 87dde5b
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -97,14 +97,14 @@ _Email any factual inaccuracies to [[email protected]](mailto:[email protected]) so they
WP Emerge does __not__ take over WordPress' routing - it actively works with it. The only exception to this are hardcoded URLs explicitly added by a user.
- Reinventing WordPress APIs using object-oriented interfaces.

WP Emerge does not provide alternative APIs for registering post types, taxonomies or the like for little added benefit. Instead, it provides logical and handy places for developers to use said APIs.
WP Emerge does not provide alternative APIs for registering post types, taxonomies or the like for little added benefit. Instead, it provides logical and handy places for developers to use core APIs.
- Using a third party engine by default.

WP Emerge uses PHP by default in the same way WordPress does but with added features. Using a third party engine is entirely optional and requires installing an extension.
- Include most of Laravel or another framework.

WP Emerge is lean and tuned for WordPress. While inspired by Laravel, it does not come with any `illuminate/*` package. There are only 2 third party production dependencies:
- `pimple/pimple` - The one-file PHP service container.
WP Emerge is lean and tuned for WordPress. While inspired by Laravel, it does not come with any `illuminate/*` packages. There are only 2 third party production dependencies:
- `pimple/pimple` - The single-file PHP service container.
- `guzzlehttp/psr7` - A PSR-7 Request and ServerRequest implementation.

## Requirements
Expand Down

0 comments on commit 87dde5b

Please sign in to comment.