-
Notifications
You must be signed in to change notification settings - Fork 660
Theming basics #819
Comments
Good question. @justinfagnani @frankiefu @notwaldorf do you all have a preference on how apps should be themed? In PSK 1 we had a separate default-theme.html that would let folks turn a few dials without having to go too deep into the rest of the CSS. We could do this same approach for PSK2 unless it's confusing for folks |
Right now, for theming we only have |
No really strong opinion myself. On one hand, I might keep it simple and put the theme in app.html. On the other having it be an import means it's really easy to switch, in case you wanted to provide more than one theme to show off. Incidentally, the themes could easily be part of a library... have you thought about splitting PSK into to a reusable library that's imported by PSK-based apps? That is, part is cloned to be customized, and part is imported. |
I created a pull request that solves this in the most consistent possible way (in my own humble opinion!) |
Unrelated, @robdodson you are turning into my best friend. I spent all day yesterday on your polycasts, and will do so again today and tomorrow... funny how videos create a sense of close familiarity! Nice work, I couldn't have submitted 3 PRs today without watching them (I am especially thick) |
I would like them to be smack in the middle of the index page, because all basic style settings are there too
Does style settings are the most global basic color theme settings of the entire infrastructure, not just the psk app. Think of it this way, if every browser would support css variables you would hard code them in the first paint style tag anyway. None of the elements should have a import theme.html, not even psk-app, only index.html |
One of the goals of PSK2 was to make something extremely simple for folks to play around with Polymer. It's a good bare bones starting point, but we don't want it to grow in complexity because then it makes it difficult for new users to play around. I'm going to close this issue because I don't think this is something PSK2 should be opinionated on. Instead I think folks should start to look at things like https://github.com/StartPolymer/progressive-web-app-template which attempt to be more of production-ready app template |
@robdodson then how do we migrate from PSK1? I've got a 50+ elements app that all depend on |
@nicholaswmin you can use the same approach as PSK1 in PSK2 if you like |
@robdodson I think the underlying theme overrides are a bit different in PSK2 Previously, setting Unless I'm missing something. |
In PSK2 there is no sot for the usual theming options.
At the moment I am putting here in the psk-app.html, within
:host
, the usual:Is this a good spot? (it kind of makes sense). Questions:
Would it be better to make an external "theme" file and include within
psk-app.html
?If so, would you like me to make up a PR with it?
If you DO want me to make a PR, shall I make it following the same format as
default-theme.html
in paper-styles? (with the -light and -dark themes)The text was updated successfully, but these errors were encountered: