Develop a Frontend Theme System
Poll Created Wed 12 Sep 2012 12:48AM
Develop a Frontend Theme System Closed Wed 26 Sep 2012 10:33PM
We'll look at this one again in the future.
One of the major issues with Diaspora at the moment is the fact that all of the code is tied together on one frontend, using bootstrap. The code for rendering how the site looks is currently also partially paired with the logic of the site. There's only one theme, and therefore only one set of templates dictating how the site is laid out. In conjunction with the proposal to separate federation from our foundation base in regards to encouraging modularity, I'd like to push that thought a bit further.
PROPOSED STRUCTURE (subject to change):
A theme's directory could use SASS/SCSS for actual CSS code, a file containing metadata about the theme, a screenshot of what it looks like, and a separate directory for templates, allowing for themes to look wildly different from one another for little breakage.
MyTheme.tar.gz would contain the following:
-/sass (or just css)
To get to a point that we can do themeing like that, we need to first consider a way to boil down Diaspora's frontend to bare-bones components. These components could be summed up as the following:
1.) Federation, dealing with how pods talk to one another.
2.) System logic, basically the controllers that dictate how the different parts of a pod work
3.) Frontend, which deals with how the actual interface itself is rendered.
4.) Backend, administration tools, pod customization.
With Rails, it is possible to switch between different themes and templates using the Deface Rails gem. It's a tried-and-true piece of Spree, a Rails commerce platform. Alternatively, we could try Disguise, which has also been recommended before.
We can see what other options out there, and if worse comes to worst, we could just end up trying to roll our own.
It would be also useful to consider designing a new "official theme" for Diaspora, to exist as a powerful example of how a theme can be customized.
|Results||Option||% of points||Voters|
|Undecided||0%||46||MS AA S CB GC AX T DY|
7 of 53 people have voted (13%)
Wed 12 Sep 2012 5:08AM
Once we're fully switched over to Bootstrap (no more Blueprint), I don't think it would be too hard to convert some of the Bootswatch themes to SASS (or even create our own).
Wed 12 Sep 2012 9:32AM
I think this is a good idea but definitely not a priority. A good protocol first !
And CSS modification is enough to do anything. So a theme could be only one css file, it will be great.
Wed 12 Sep 2012 6:49PM
Long term yes. Might be a good idea if the author of this proposal draws a proper blueprint or something technical to the wiki for example - otherwise this idea will get lost here since no one will have time to work on it for a long time ;)