| 5 | | There's no great UI/API for this yet, though. It's literally just an option that saves the name of the registered theme compat, with a drop down to choose from one of them. I think this is fine enough for a v1, and we can look into fancying up the place when we're happy with how it's working. |
| | 5 | It then allows us to always have a default/canonical set of fallback template parts that we can constantly update without the bp-default burden that we have today. At some point the metaphor still breaks down (I want this to look like this, but this to look like that) but that's unavoidable unless we split all the templates up, which I'm not keen on doing as a v1. |
| | 6 | |
| | 7 | There's no great UI/API for this yet like there is with !WordPress themes; it's literally just an option that saves the name of the registered theme compat, with a drop down to choose from one of them. I think this is fine enough for a v1, and we can look into fancying up the place when we're happy with how it's working. |