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.

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

Moving plugin files into a single contained folder for ease of use. #11

Closed
wants to merge 1 commit into from

Conversation

howardroark
Copy link
Contributor

Many popular Craft plugins keep all core plugin files within a folder of the desired plugin name. This makes it very easy to identify the files which are core to the plugin itself. In build processes that I use, the github tarball is extracted to a vendor folder and then the core folder is symlinked to the craft plugin directory. Reminiscent of how composer would handle things.

I won't take any offence if you reject this... just thought I would propose it!

@thoaionline
Copy link
Contributor

Hi @howardroark, I'm going to disagree with you here. When using composer to install package, it makes more sense to put files at the root folder. Composer has support for craft plugin and the plugin in its current state can be added to a composer managed project as-is.

@howardroark
Copy link
Contributor Author

Fair enough! Are there any special instructions for installing Craft plugins with composer? I'd like to give it a try!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants