Skip to content

Commit b040bdf

Browse files
Clean up the readme a bit
1 parent 195b84a commit b040bdf

File tree

7 files changed

+52
-43
lines changed

7 files changed

+52
-43
lines changed

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
11
/vendor/
22
/features/bootstrap/test_exports/
33
/wordpress/
4+
readme.txt

README.md

Lines changed: 17 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -7,15 +7,6 @@ WP-CLI for Advanced Custom Fields helps you manage your field-groups through WP-
77
The reason we started this project is to make life easier for developers working on Wordpress projects using the Advanced Custom Fields Pro plugin.
88
Fields can now easily be imported, exported and shared over SVN, GIT or comparable systems.
99

10-
11-
### Reasons to start this project
12-
13-
* Advanced custom fields did not interface with WP-CLI
14-
* Sharing field-groups through XML or PHP code caused problems with differences between development, test, staging and production enviroments when shared with XML.
15-
* No direct SVN or GIT support without manually putting the exported PHP or XML into a versioned directory.
16-
* Naming convention for XML files was always the same, resulting in renaming hassle.
17-
* Only using the generated field-groups on runtime through PHP code in functions.php disables the editing mode (which is an awesome UI that we require). So importing should be possible.
18-
1910
## Installation
2011

2112

@@ -27,18 +18,27 @@ Fields can now easily be imported, exported and shared over SVN, GIT or comparab
2718

2819
### How to install
2920

30-
Install WP-CLI as described on [their website](http://wp-cli.org/ "WP-CLI")
21+
Install WP-CLI as described on [http://wp-cli.org/](http://wp-cli.org/ "WP-CLI")
22+
23+
Using composer:
24+
```
25+
composer require wpackagist-plugin/advanced-custom-fields-wpcli
26+
```
3127

32-
Clone this repo to your plugins directory
28+
By GIT clone in plugins directory:
3329
```
3430
git clone https://github.com/hoppinger/advanced-custom-fields-wpcli.git
3531
```
32+
33+
WordPress plugin installation:
34+
Download zip and put the files in the plugins directory.
35+
3636
* Activate this plugin in the plugin menu or using:
3737
```
3838
wp plugin activate advanced-custom-fields-wpcli
3939
```
4040

41-
Go the wordpress directory in your terminal and try out to:
41+
Go the wordpress directory in your terminal and run:
4242
```
4343
wp acf
4444
```
@@ -64,9 +64,13 @@ Prints the help overview and can be used as a default test to see if the plugin
6464
6565
6666
### Export
67+
68+
Export a field-group to a json file in the directory set by a filter.
69+
```
6770
wp acf export
6871
```
69-
Export a field-group to a json file in the directory set by a filter. You want to export all field-groups all at once you can use:
72+
73+
You want to export all field-groups all at once you can use:
7074
```
7175
wp acf export --all
7276
```
@@ -95,8 +99,6 @@ Do this after you have edited fields-groups from the UI and exported the changes
9599
The acfwpcli_fieldgroup_paths gives you the ability to add more paths where ACF-CLI should load/export from/to.
96100
You should always add at least one path to this filter.
97101
98-
**Example:**
99-
100102
```
101103
add_filter( 'acfwpcli_fieldgroup_paths', 'add_plugin_path' );
102104

readme.txt

Lines changed: 17 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -14,14 +14,6 @@ Manage Advanced Custom Fields through WP-CLI
1414
WP-CLI for Advanced Custom Fields helps you manage your field-groups through WP-CLI.
1515
The reason we started this project is to make life easier for developers working on Wordpress projects using the Advanced Custom Fields Pro plugin.
1616
Fields can now easily be imported, exported and shared over SVN, GIT or comparable systems.
17-
18-
= Reasons to start this project =
19-
20-
* Advanced custom fields did not interface with WP-CLI
21-
* Sharing field-groups through XML or PHP code caused problems with differences between development, test, staging and production enviroments when shared with XML.
22-
* No direct SVN or GIT support without manually putting the exported PHP or XML into a versioned directory.
23-
* Naming convention for XML files was always the same, resulting in renaming hassle.
24-
* Only using the generated field-groups on runtime through PHP code in functions.php disables the editing mode (which is an awesome UI that we require). So importing should be possible.
2517
== Installation ==
2618

2719
= Requirements =
@@ -31,18 +23,27 @@ Fields can now easily be imported, exported and shared over SVN, GIT or comparab
3123

3224
= How to install =
3325

34-
Install WP-CLI as described on [their website](http://wp-cli.org/ "WP-CLI")
26+
Install WP-CLI as described on [http://wp-cli.org/](http://wp-cli.org/ "WP-CLI")
27+
28+
Using composer:
29+
```
30+
composer require wpackagist-plugin/advanced-custom-fields-wpcli
31+
```
3532

36-
Clone this repo to your plugins directory
33+
By GIT clone in plugins directory:
3734
```
3835
git clone https://github.com/hoppinger/advanced-custom-fields-wpcli.git
3936
```
37+
38+
WordPress plugin installation:
39+
Download zip and put the files in the plugins directory.
40+
4041
* Activate this plugin in the plugin menu or using:
4142
```
4243
wp plugin activate advanced-custom-fields-wpcli
4344
```
4445

45-
Go the wordpress directory in your terminal and try out to:
46+
Go the wordpress directory in your terminal and run:
4647
```
4748
wp acf
4849
```
@@ -60,8 +61,6 @@ remove_action('plugins_loaded', 'acf_wpcli_register_groups');
6061
The acfwpcli_fieldgroup_paths gives you the ability to add more paths where ACF-CLI should load/export from/to.
6162
You should always add at least one path to this filter.
6263

63-
**Example:**
64-
6564
```
6665
add_filter( 'acfwpcli_fieldgroup_paths', 'add_plugin_path' );
6766

@@ -82,9 +81,13 @@ Prints the help overview and can be used as a default test to see if the plugin
8281
```
8382

8483
= Export =
84+
85+
Export a field-group to a json file in the directory set by a filter.
86+
```
8587
wp acf export
8688
```
87-
Export a field-group to a json file in the directory set by a filter. You want to export all field-groups all at once you can use:
89+
90+
You want to export all field-groups all at once you can use:
8891
```
8992
wp acf export --all
9093
```

readme/command.txt

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,13 @@ Prints the help overview and can be used as a default test to see if the plugin
1010
```
1111

1212
= Export =
13+
14+
Export a field-group to a json file in the directory set by a filter.
15+
```
1316
wp acf export
1417
```
15-
Export a field-group to a json file in the directory set by a filter. You want to export all field-groups all at once you can use:
18+
19+
You want to export all field-groups all at once you can use:
1620
```
1721
wp acf export --all
1822
```

readme/description.txt

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,3 @@
55
WP-CLI for Advanced Custom Fields helps you manage your field-groups through WP-CLI.
66
The reason we started this project is to make life easier for developers working on Wordpress projects using the Advanced Custom Fields Pro plugin.
77
Fields can now easily be imported, exported and shared over SVN, GIT or comparable systems.
8-
9-
= Reasons to start this project =
10-
11-
* Advanced custom fields did not interface with WP-CLI
12-
* Sharing field-groups through XML or PHP code caused problems with differences between development, test, staging and production enviroments when shared with XML.
13-
* No direct SVN or GIT support without manually putting the exported PHP or XML into a versioned directory.
14-
* Naming convention for XML files was always the same, resulting in renaming hassle.
15-
* Only using the generated field-groups on runtime through PHP code in functions.php disables the editing mode (which is an awesome UI that we require). So importing should be possible.

readme/filters.txt

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,6 @@
55
The acfwpcli_fieldgroup_paths gives you the ability to add more paths where ACF-CLI should load/export from/to.
66
You should always add at least one path to this filter.
77

8-
**Example:**
9-
108
```
119
add_filter( 'acfwpcli_fieldgroup_paths', 'add_plugin_path' );
1210

readme/installation.txt

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,18 +7,27 @@
77

88
= How to install =
99

10-
Install WP-CLI as described on [their website](http://wp-cli.org/ "WP-CLI")
10+
Install WP-CLI as described on [http://wp-cli.org/](http://wp-cli.org/ "WP-CLI")
1111

12-
Clone this repo to your plugins directory
12+
Using composer:
13+
```
14+
composer require wpackagist-plugin/advanced-custom-fields-wpcli
15+
```
16+
17+
By GIT clone in plugins directory:
1318
```
1419
git clone https://github.com/hoppinger/advanced-custom-fields-wpcli.git
1520
```
21+
22+
WordPress plugin installation:
23+
Download zip and put the files in the plugins directory.
24+
1625
* Activate this plugin in the plugin menu or using:
1726
```
1827
wp plugin activate advanced-custom-fields-wpcli
1928
```
2029

21-
Go the wordpress directory in your terminal and try out to:
30+
Go the wordpress directory in your terminal and run:
2231
```
2332
wp acf
2433
```

0 commit comments

Comments
 (0)