Facilitate development of plugin in existing WordPress dev environment

[westonruter]

It is difficult to hack on this plugin on an existing WordPress development environment. For example, Gutenberg, AMP, and PWA plugins all can just be cloned into wp-content/plugins of any existing WordPress install and then with npm install and npm run build they can be activated in-place.

Can that be implemented for Quicklink as well? Part of this would include making setup-local-env.sh optional.

[Luehrsen]

It can certainly be done.

This stems just from our taste to separate build/repo files from actual plugin files. If we want to use existing setups we usually do a symlink.

But we can certainly restructure the repo to fit these needs if you see it necessary. 🙂