Design for interface to allow adding in and building your own version of _s

Automattic / underscores.me

https://underscores.me

GNU General Public License v2.0

210 stars 118 forks source link

Design for interface to allow adding in and building your own version of _s #31

Open karmatosed opened 9 years ago

karmatosed commented 9 years ago

This is taking the conversation over here https://github.com/Automattic/_s/issues/659 to underscores.me and hopefully kicks off the things discussed. I thought I'd start the ball rolling with a speed mockup session. This is just a short rough idea but hopefully means we can have a starting point.

underscoresme_options

A few points:

There are 2 methods of display and I've done that because as things grow perhaps grouping should happen.
I didn't have the font so that needs to be added in to fit. I went with default Arial to ease.
I've kept the branding, simply adding a block if you want to customise.
Wording is just there for now, we can decide on that but it's to demonstrate.

mattwatsoncodes commented 9 years ago

@karmatosed this is great. I guess one of the first things to do is decide what is classed is the 'minimum' _s build and what are optional extras.

I can think of a few, obviously SCSS and maybe Jetpack features such as infinite scroll. Perhaps even which column layout the downloader prefers.

Let me have a think, I will follow this up with my starter for 10 of things I think we could have as 'optional' configurations.

obenland commented 9 years ago

underscores.me doesn't necessarily have to continue to look the way it currently does.

mattwatsoncodes commented 9 years ago

I think with this configuration, the 'generate' option should give you a recommended build. For example, it could come with Jetpack infinite scroll by default, unless you 'Roll Yer Own' and untick that option.

Just because there would be a bare minimum build possible, that doesn't necessarily mean thats the one everyone gets. It could still be a pretty standard build if you don't want to customise anything.

The modernizr builder does this in a similar way: http://modernizr.com/download/ whereby you untick what you don't want from the standard build.

karmatosed commented 9 years ago

@mwtsn, I'm not so keen on the tick off method. I would like to see people tick to have on. That way we're encouraging a light base.

ianstewart commented 9 years ago

I would prioritize selecting a layout over everything as a first iteration. Or next step. There are 5 or 6 layouts hiding in the revisions to /layouts. It's the most "root-level" change for probably most everyone using _s to build a theme that can have the biggest impact. More so than Less, resets, or anything else. Based on what we have now it'd be a great first step too. Offer layout selection, get it out there, watch stats, iterate on feedback.

mrpritchett commented 9 years ago

Love this idea! My question is what level of customization is desired? Do we go with a level similar to bootstrap where users can add font defaults in? Or simple options like some of those mocked up?

alaczek commented 9 years ago

Here's an iteration on @karmatosed mockup, created with scalability in mind.

The Default tab does not contain any customization options: underscores_tabs_default All customization options live in separate tab, which should give us plenty of space to grow: underscores_tabs_customize

stebrech commented 9 years ago

:thumbsup: I like that tab solution