Symphony.

The first thing I do when installing Symphony is removing extensions distributed with the core that I don't use. I first thought this could be handled easily by just forking the main repository and adding a new branch with my own set of extensions, but it seems like Git is having some hick-ups when you switch branches with differing sets of submodules: it either complains about uncommitted folders or the list of submodules gets messed up.

As I've previously noted on this forum, I think it would be great if Symphony could be distributed as a vanilla install (no workspace, no extension folder) and that special download packages (like the default blog) were made available as separate ensembles (actually this is what I thought ensembles were made for). However, this needs a good interface and we have been talking about a package builder for this website before. And we all know time goes by :)

Until we find a good solution for this, a small change might help with the submodule issue described above: Why don't we make the extensions folder a submodule, too? This way it would be possible to maintain Symphony and the extensions separately and without interferences. At least this would streamline my workflow and I guess that of others, too.

Nils, interesting maybe on Extension screen have a field to search and install by Admin like Wordpress. For designers =) it's more faster than use download zip.

@marciotoledo

have you seen alpacaaa's builder ensemble?