Leandro Pereira

As far as I can tell this issue is only relevant when creating your own stylesheet, which in Beacon is done by calling `Beacon.Content.create_stylesheet/1` There's no need to escape `:`...

@AZholtkevych we can remove the dependency of BeaconCMS/beacon#95. Here are the technical details: Each site will have its own sitemap.xml which must be resolved dynamically by adding a route `/sitemap.xml`...

> While creating content allow users to select “exclude from sitemap” (default = included) so content can be published but not seo indexed. That would be a new field in...

We can port over some of the dockyard.com sitemap implementation but not everything because either part of the code is very business specific or works in a different way we...

@bcardarella part of it makes sense and we can reuse some code 👍🏻

@TheFirstAvenger thoughts?

@AZholtkevych this issue is a proposal to support `Phoenix.Component`, a way to reuse pieces of templates. That would be the building block of layouts and pages.

> I wouldn't be opposed to just wiping out the my_component support in the same PR @TheFirstAvenger sounds good 👍🏻

> Have the templates string not use `~H` and a bare string means that editors or language support tools will need specialized support to highlight the template as HEEx after...

Closed by https://github.com/BeaconCMS/beacon/pull/423, https://github.com/BeaconCMS/beacon/pull/535, and https://github.com/BeaconCMS/beacon_live_admin/pull/160