Adam
Then yeah, I think the question is why the hell they weren't created when Claro was installed. As far as I can tell, they _should_ be! I guess I'd probably...
That code is there for a reason. :) Recipes don't install any config entities automatically; they expect the recipe to explicitly list the config they want. That's an intentional difference...
No, we'll stick with Gin. I don't think having `starshot_admin_theme` install Claro is the proper fix. Whatever's going on here is interesting and we need to figure out the real...
> Gin will install Claro, because Claro is a dependency for Gin theme Ooooh, that changes things! I did _not_ know that! I stand corrected. If Gin has a hard...
Don't hate me :) I'm glad we found the cause! I apologize for my intransigence and lack of understanding. Regarding the recipe system's config installer -- now that I see...
> We should either make the URLs truly hackable (i.e., add Views with the appropriate contextual filters) or remove the directory separators from the URLs I'm wondering what most authors...
I think this pretty much closes #105, then. If we're going to make the URLs hackable, then the `blog` view will be needed!
This sounds like it might be a good follow-up to #114.
I agree that it should be a separate recipe. If it gets added in the same PR, though, that sounds fine to me. I'd also be okay doing it later.
Well, wait a sec. Can we not create an HTML email recipe that builds on top of the other one? Or vice-versa? Surely we could modify the ECA model via...