You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
-
# Entity-Centric API integration for Wordpress 4
1
+
# Entity-Centric API integration for WordPress 4
2
2
3
-
A set of utilities for handling and consuming data sources for ECApi from within a Wordpress installation
3
+
A set of utilities for handling and consuming data sources for ECApi from within a WordPress installation
4
4
5
5
## Requirements
6
6
7
7
To __build__ the project you will need to have [Bower](http://bower.io) and [Composer](http://getcomposer.org) installed. At the risk of stating the obvious, this is because this package does _not_ come with the PHP and JavaScript dependencies of the project bundled with it.
8
8
9
-
To __run__ the project after building it, you will need a Wordpress installation (so far only [version 4.2](https://codex.wordpress.org/Version_4.0.x) has been tested), and by extension a *AMP stack.
9
+
To __run__ the project after building it, you will need a WordPress 4 installation (so far only [version 4.3](http://codex.wordpress.org/Version_4.3) has been tested), and by extension a *AMP stack.
10
10
11
11
## Building
12
12
From within the root dir of the project:
@@ -19,4 +19,4 @@ Then, assuming Composer is installed either there or globally on your system:
19
19
20
20
The above command will also run Bower automatically as a post-install hook.
21
21
22
-
Finally, stage the whole `ecapi` directory into the `wp-content/plugins` of your Wordpress.
22
+
Finally, stage the whole `ecapi` directory into the `wp-content/plugins` of your WordPress.
0 commit comments