Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Facilitate development of plugin in existing WordPress dev environment #80

Closed
westonruter opened this issue Jan 24, 2019 · 1 comment
Closed

Facilitate development of plugin in existing WordPress dev environment #80

westonruter opened this issue Jan 24, 2019 · 1 comment

Comments

@westonruter
Copy link

westonruter commented Jan 24, 2019 •
edited
Loading

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.
@westonruter
Copy link
Author

Accidentally raised here instead of https://github.com/luehrsenheinrich/quicklink/issues/6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@westonruter