Doc fixes
parent
dfd71b31dc
commit
8bf03aea07
|
@ -12,7 +12,6 @@ This is common if your package is intended for a specific framework such as
|
|||
CakePHP, Drupal or WordPress. Here is an example composer.json file for a
|
||||
WordPress theme:
|
||||
|
||||
```
|
||||
{
|
||||
"name": "you/themename",
|
||||
"type": "wordpress-theme",
|
||||
|
@ -20,7 +19,6 @@ WordPress theme:
|
|||
"composer/installers": "*"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
Now when your theme is installed with Composer it will be placed into
|
||||
`wp-content/themes/themename/` folder. Check the
|
||||
|
@ -33,7 +31,6 @@ Drupal multisite setup where the package should be installed into your sites
|
|||
subdirectory. Here we are overriding the install path for a module that uses
|
||||
composer/installers:
|
||||
|
||||
```
|
||||
{
|
||||
"extra": {
|
||||
"installer-paths": {
|
||||
|
@ -41,7 +38,6 @@ composer/installers:
|
|||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
Now the package would be installed to your folder location, rather than the default
|
||||
composer/installers determined location.
|
||||
|
|
Loading…
Reference in New Issue