When To Create A Package?
Permalink
If I'm creating a web site and don't intend for parts of it to be otherwise distributed, is it wise, or necessary, to create a package for my customizations? I'm a little unclear as to the problem use of a package.
Perhaps if I'm simply creating a web site, all my customizations and overrides would be best done in the root level folders?
Perhaps if I'm simply creating a web site, all my customizations and overrides would be best done in the root level folders?
yes packages are really to facilitate redistribution. In your case it's probably not needed.
I find it all depends on how much customisation. As well as being useful for distribution (which is not relevant to you), packages are also useful structural components for software design. So even with software that isn't going to be used elsewhere, if there is a lot of it then structuring it into packages can help keep things organised.
Organization is a good point. Perhaps it's just me, but I've been having some trouble keeping track of when a package's files will override something else and when they won't. It seems like the root level folder override is more consistent (always).
Bob
Bob
I was only thinking earlier today that I would like a dashboard page to summarise what is overridden and where.
Also, something like "where's my block" but for block templates and page types, so I can see which are actually in use and where.
Also, something like "where's my block" but for block templates and page types, so I can see which are actually in use and where.
The environnement information includes a list of overrides, it's basic but it lists the files and where they are.
Thanks, I hadn't looked there before; and that does help some. But it doesn't seem to list overrides that occur from within packages. Or does it?
Bob
Bob
For individual customizations such as you make a new block, or you override a script, I wouldn't see any advantage to packages. But when you have a set of things all connected, like a block and an attribute and a couple of script overrides, as others have said a package will keep those things better organized.
I would not want to be working on changes to a system and find the parts of it strewn across all the different site folders where it's mixed in with items that are not relevant to that part of the system, even though they are part of the same site. Say in a practical way you have built some sort of e-learning system and you have some functionality around course registrations. It would be good to package that up otherwise next time you want to change it you might have to sift through bits that are more about displaying courses.
I feel like if you get in a habit of packaging related parts, eventually you use packages the majority of the time and the site folders become just for one-off, smaller customizations.
I would not want to be working on changes to a system and find the parts of it strewn across all the different site folders where it's mixed in with items that are not relevant to that part of the system, even though they are part of the same site. Say in a practical way you have built some sort of e-learning system and you have some functionality around course registrations. It would be good to package that up otherwise next time you want to change it you might have to sift through bits that are more about displaying courses.
I feel like if you get in a habit of packaging related parts, eventually you use packages the majority of the time and the site folders become just for one-off, smaller customizations.
