Template or whole website?

I'm just about ready to package up my first complete template package, based on the ItFits template, as used in the MODXpo presentation and my own site at the moment. It will include three templates, a not-found page, a contact page and various chunks and template variables, as well as the supporting image, .css and .js files.

I can use BobRay's most excellent MyComponent to package up just the template and its support files, or I can use Vapor to package an entire site, templates, add-ons, resources and all. Or do both. Thoughts?

Entire site imo. You can always update the core and add-ons and repack it when/if need be.

Entire site +1

Entire site in my opinion. Makes it simpler for first time MODXers.

you can also export Resources and subpackages and all this , what is needed for a startup-package with myComponent.
So I think a package build with myComponent should be enough and you can build upgrade-packages when needed.

So I can have a myComponent that will include the various packages that the whole enchilada uses (Wayfinder, SimpleSearch, FormIt, MIGx)?

yes, with myComponentMigxUI its allready possible to select which packages to export with the main-package.

They will be in the target-packages-folder, but not be installed after installing your package.
They have to search locally for new packages and install them, by default.

I think it should be possible to create resolvers, which does also the installation of this subpackages.

Hm. Don't like that; no easy upgrade. Well, I'll think it over and decide what to do. Probably both, a smaller package with just the templates and support files, and then the whole Vaporized site package. I just got the latest MacHeist nano bundle, which includes a very nice little application called Clarify, for making HTML or PDF screen-capture tutorials. So I'll be including some of these in my packages.

I know what mycomponents do, but what does myComponentMigxUI do?

Quote from: DesignByWilliam at Apr 18, 2013, 06:12 AM

I know what mycomponents do, but what does myComponentMigxUI do?

A not yet ready (working for me so far, but may not for others) UI for myComponent with some little additional features like copying files from core/compontents assets/components to the assets/mycomponents - folder and copying subpackages to the myComponent-package.
http://www.revo222.webcmsolutions.de/index.php?id=51 [ed. note: Bruno17 last edited this post 13 years, 6 months ago.]