Would it be possible to add a sticky post which contains all responsive themes we have? It should contain download locations as well.
As far as I am aware, I see theses themes:
- 2k11
- Bartleby
- Clean Blog
- Resy
- S9yPr
- Timeline
Cheers
Dirk
What's S9yPr? There's also Next.Lux wrote:As far as I am aware, I see theses themes:
- 2k11
- Bartleby
- Clean Blog
- Resy
- S9yPr
- Timeline
I see what you want to achieve by that, I just don't think it is necessary or worth the effort. Yes, it makes sense to educate people about responsive themes. I cringe every time I see a s9y site using an outdated theme. But the reality is, we can not really influence which themes people want to use.Lux wrote:It would be great to have a possibility to sort the templates in the backend as well (responsive first).
S9yPr: http://board.s9y.org/viewtopic.php?f=5&t=20615yellowled wrote: What's S9yPr? There's also Next.
We will never have all themes in the care or on Spartacus.yellowled wrote: All other responsive themes (as far as I know) are on Spartacus. There is no need to download any of them from a third-party site, so …?
I do not want to educate anyone, but I want to distinguish between modern - read: responsive - and outdated templates.yellowled wrote: I see what you want to achieve by that, I just don't think it is necessary or worth the effort. Yes, it makes sense to educate people about responsive themes. I cringe every time I see a s9y site using an outdated theme. But the reality is, we can not really influence which themes people want to use.
Absolutely agreed, even though I think it would neither take a lot time to make a sticky post nor to sort the templates.yellowled wrote: I think our devs' time can be spent better than to discuss and implement something that will (hopefully sooner than later) become obsolete anyway.
In /templates/next/, but I do not remember in which 2.0.x we added it.Lux wrote:I do not know Next, where can I find it?
Well, if it's not in the core or on Spartacus, it's an “inofficial” third-party theme. If a theme is “finished” and meets certain characteristics, there is absolutely no reason to not put it at least on Spartacus, unless the author objects.Lux wrote:We will never have all themes in the care or on Spartacus.
Yeah, because it's not on Spartacus.Lux wrote:As example: You did not remember about S9ypr ...
I'm happy to make a sticky post, I just don't want to maintain it, and unfortunately, it is a tad more complicated to sort themes in the backend than you think. Starts with the fact that we need a way to tell that a theme is responsive. We'd need some kind of new field for that, and that will become obsolete at some point as well …Lux wrote:Absolutely agreed, even though I think it would neither take a lot time to make a sticky post nor to sort the templates.
Initally added to the core repository in February 2015, which makes me think it was released with 2.0.1 or maybe 2.0.2. But I think it was not mentioned specifically in the release blog post. Soft release.yellowled wrote:In /templates/next/, but I do not remember in which 2.0.x we added it.Lux wrote:I do not know Next, where can I find it?
Perfect. Thank you!onli wrote:I suggested before (don't know where) to separate in the backend between modern and legacy themes. Should be easy enough to do. Since it is now not only me wanting that I'd add it to my todo list (but if someone has time to implement it, please go ahead).
Before you get started on implementing anything, I would really like to discuss what you consider to be “modern” and “legacy”. Because I think those categories don't really say much. From a certain point of view, even 2k11 is “legacy” now. (And please remember that it will need to be implemented on the Spartacus website as well. It does not make sense to have this only in the backend.)onli wrote:I suggested before (don't know where) to separate in the backend between modern and legacy themes. Should be easy enough to do. Since it is now not only me wanting that I'd add it to my todo list (but if someone has time to implement it, please go ahead).
Fine, then go ahead and implement it the way you think it should be. I will not try to dicuss something you very obviously do not even want to discuss. That to me appears to be a waste of time.onli wrote:I don't think we should overdiscuss this.