Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Original Theme for 2019 (and 2018) #289

Open
jeffmcneill opened this issue Dec 14, 2018 · 4 comments

Comments

@jeffmcneill
Copy link

commented Dec 14, 2018

WordPress traditionally has a new yearly theme named by year. Currently ClassicPress is shipping with 2015, 2016, and 2017. That's fine, but it does seem to give the impression that the release is old (no 2018, and no 2019). It may be an interesting differentiator to have yearly themes, but named not by year but something else. One random idea is to name the theme by the Chinese Animal for the given year. This year and next year would be "Year of the Dog" (2018), and "Year of the Pig" (2019). Of course Pig might not sound sexy, but it could be "Year of the Boar" with a wild boar-like creature. The idea here really only has to do with naming differently, and also ensuring there is some new free theme that is moderately interesting for people to play with as a default, included option.

@ginsterbusch

This comment has been minimized.

Copy link

commented Dec 14, 2018

AFAIK discussion is going on about removing all these "numbered" themes and replacing them with a decent default one, eg. Susty. Others just point out adding a default theme and leave the numbers in ..

I'd suggest posting this issue in CP slack in #themes or #core, and get a healthy discussion going on ;)

cu, w0lf

@nylen

This comment has been minimized.

Copy link
Member

commented Jan 8, 2019

See also #6.

@nylen nylen added this to the Future milestone Jan 8, 2019

@zulfgani

This comment has been minimized.

Copy link

commented Mar 5, 2019

What are your thoughts on a streamlined version of StoreFront without the WC bloat as a starting point. Or has it been settled that Susty is the way forward?

@nylen

This comment has been minimized.

Copy link
Member

commented Mar 6, 2019

@zulfgani this has not been settled yet, we're just using Susty as the base for our internal sites and we're pretty happy with it there.

As we've been discussing on Slack, I've set up a repository for a fork of Storefront: https://github.com/ClassicPress-research/classicpress-storefront

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.