As a Discourse theme author, I want to be able to specify child/component themes that are required for my theme to work correctly, so the user (Discourse site admin) doesn’t have to manually go out and add/configure it.
We are working on a downstream theme to work alongside the Mozilla theme (thanks @LeoMcA!) but it’d be nice if we didn’t have to manually specify import their theme and manually link them. Could such a relationship be added to the about.json file?
An aside, this would also benefit developers who build themes for clients. It’s becoming a more appealing setup to use a public theme and then tweak it for the client site. But more and more often, they want their customized theme in GitHub for pulling updates and allowing multiple people to work on them. It’d be great to embed the dependency somehow.
Asking for advanced features like this makes me 
, means the system is being used
Not against building this but needs very careful testing
I imagine it’d also be useful for you to be able to specify a particular version/commit that the theme depends on - that way, if we completely change something you’re depending on, it won’t all suddenly break on your end.
Yes, good point … although makes it a bit more complex. 
Maybe. If you can add the dependency as a GitHub link of sorts that allows a specific commit, branch, or tag, it gets easier. But that doesn’t mean the whole feature is easy.
Or any non-GH Git repository 
@vinothkannans acabou de adicionar suporte à listagem inicial de componentes de tema dependentes, o que torna a instalação de um pacote muito mais fácil.
Ele postará aqui com mais detalhes!
Agora, uma lista de componentes de temas filhos pode ser especificada no arquivo about.json para temas de nível superior. Por exemplo:
{
"name": "Material Design Theme",
"about_url": "https://meta.discourse.org/t/material-design-stock-theme/47142",
"license_url": "https://github.com/discourse/material-design-stock-theme/blob/master/LICENSE.txt",
"components": ["https://github.com/discourse/discourse-brand-header", "https://github.com/Chaboi45/Take-a-break-component"]
.
.
.
}
Atualmente, há as seguintes limitações:
about.json posteriormente, o componente de tema filho instalado não será desinstalado.Estou me perguntando se seria possível considerar a opção de definir configurações padrão para componentes de temas integrados.
Por exemplo, alterar os padrões em settings.yml de Discourse Button Styles, para valores específicos a fim de corresponder a um tema de nível superior.
(Atualmente, acredito que seria necessário fazer um fork do componente de tema)
