Move templates & themes into Chime proper and out of starter

[phae]

@norris and whoever will probably need to work on this together to make sure the right bits are on the right sides of the line.

[norrishung]

@frances @wpietri

Tomas and I are doing task tidying and we are trying to figure out what the priority of this task is. Is this something we need to do for bootcamp/oakland sites?

Last time we discussed, the idea was to move Chime Starter and all associated themes into Chime and have a separate place where Chime users can override the CSS. @wpietri, we'll probably need to your help in architecting how this would work.

[wpietri]

Hi! It would be good to do this for Bootcamp, but it's not mandatory. The alternative is that any time you want to update the styles, you will have to manually fiddle stuff on all boxes.

Glad to talk about architecture. We can do a phone call today or a meeting tomorrow. It looks like Jekyll doesn't natively do multiple source directories, so the obvious thing to do is to copy templates and user content into one source directory before running jekyll. (Another reason we may want our own custom generator.) Then the user content should work pretty much like it does now.

[migurski]

We talked about this during task tidying, and I’m advocating for prioritizing this just after bootcamp. It’s a big change to make during a time we’re running toward stability.

[wpietri]

Fine by me. I'll take this as a sign we need better tests. Which is what I'm mainly working on today.