loopress★ GitHub

loopress light · from wordpress.org

You installed Light. Here's the other half.

Light is the plugin. The workflow lives in the CLI: it turns your site's configuration into files you keep in Git, review, and push to any environment.

What Light puts in Git

ACF field groups, post types, taxonomies, options pageslps acf pull · push
Navigation menus and their itemslps menu pull · push
Custom post types, declared as JSON fileslps cpt pull · push
Taxonomies, attached to your post typeslps taxonomy pull · push
Post meta keys, declared per post typelps meta pull · push
Custom user roles and their capabilitieslps role pull · push
The options you choose to tracklps option pull · push
Block theme styleslps theme style pull · push

no code, by design: light only moves configuration, through the same APIs you use by hand.

Three commands to start

$ npm i -g @loopress/cli
$ lps project config     # authorize in your browser
$ lps pull               # your site's configuration, as files

lps project config will offer to install Loopress Full. Say no and you stay on Light, everything above keeps working.

Then, the loop

Commit the files. Change a field group locally, open a PR, run lps diff --env stagingto see what would change, then lps push. When someone edits a menu in wp-admin,lps pull brings it back into the repo. Posts, orders and users never move.

When you want Full

Full is the same plugin with the code half switched on. It is free too. WordPress.org doesn't host plugins that deploy code, so Full ships from loopress.dev, and installing it replaces Light. Re-run lps project config and accept the prompt.

LightWordPress.orgFullloopress.dev
configuration
ACFlps acf✓✓
Formslps form✓✓
Menuslps menu✓✓
Post typeslps cpt✓✓
Taxonomieslps taxonomy✓✓
Post metalps meta✓✓
Roleslps role✓✓
Optionslps option✓✓
Global Styleslps theme style✓✓
your code
Hookslps hook·✓
API routeslps api·✓
Appslps app·✓
Pageslps page·✓
Templateslps theme template·✓
Patternslps pattern·✓
Pluginslps plugin·✓
Composerlps composer·✓