[development] strategy for naming module/theme/profile
Simon Hobbs
info at urbits.com
Mon Oct 8 15:44:42 UTC 2007
Inspired by Boris Mann, I was going to start adding my company's
standard install profile / module / theme in CVS.
I've had issues in the past with a theme and module sharing the same
name. Is this still an issue? Was this ever a recognised issue?
Can I do this in D5 without any repurcussions when it comes to installation?
module - "emspace" - support code and snippets for our install profile
profile - "emspace" - our default install profile
theme - "emspace" - our site's theme including an admin variation.
Or to avoid issues described above, should I be doing:
"emspace_code"
"emspace_profile"
"emspace_theme"
Any suggestions are welcome.
Simon
More information about the development
mailing list