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

Project content types: why no 'features' type? #9

Open
nated opened this issue Dec 14, 2010 · 1 comment
Open

Project content types: why no 'features' type? #9

nated opened this issue Dec 14, 2010 · 1 comment

Comments

@nated
Copy link

nated commented Dec 14, 2010

Just wondering if there is any reason why there does not exist a 'feature' project type.

Realizing they are practically the same as modules, it still seems good to have this logical separation. Thoughts?

@cyberwolf
Copy link

AFAIK tools like Drush take into account the project type to know where to put downloaded projects in the Drupal directory structure (either under sites/all/themes/, sites/all/modules/, installation profiles under profiles/, etc.). I guess Drush does not know how to handle any additional categories, although I did not try it myself.

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

No branches or pull requests

2 participants