I'm on my school Chromebook, which means there's no plugins enabled, and I open the homepage to.. this?
Not to be rude, but personally, I liked the old buttons style, still present on the login page and project page, better than the new :/
I'm on my school Chromebook, which means there's no plugins enabled, and I open the homepage to.. this?
This is indeed how the website now looks (apparently). I personally like the colored buttons, it's more inviting than ugly grey buttons (ok, they weren't ugly, but you get my point). I feel like the snap dev in charge of the website it trying to make the website look a bit more modern, and a lot more friendly. I did see that they are just using bootstrap, which I'm not a huge fan of, because it can make many websites look the same, but here, it looks good.
In addition to making the site look better, one of Michael's goals is to get us away from bespoke software into standard software to make things more maintainable.
Honestly I've heard much better things about tailwind css, so I think Michael should use that instead of bootstrap (since tailwind give a lot more freedom).
(my pc cannor fit the image and the buttons and the header)
I swear a few hours ago I didn't even see how the buttons were unstyled! Only now I noticed something changed. I should get off the editor thinking about what cool things to do with the Beetle...
Don't worry, I only ever go to the forum and the editor, I never go to the main site.
At some point, I'm planning to write something. But really, with classes starting soon (for me and everyone else), I'd rather get into the process of rolling out smaller changes.
The home page buttons are a hack -- primarily because 5 actions is too much. My goal with changing the colors at least for now, is that I'd like to kind of group actions. I don't think it's perfect, but if you're looking to open the editor, that's where you can get to more easily.
As far as tools: Tailwind is very cool. I've played with it, but less familiar. But mostly, in its current state, Bootstrap is a better fit because we don't yet have internal "components" that would make tailwind a little more effective. It was easier to get started w/Bootstrap without needing to setup the build + compile pipeline for CSS.
A lot of the initial micro-level details of the Snap! site were inherited primarily from Yahoo's pure css library, but we've never done a ground-up design of the community site. I'd love to, but, frankly, it's just not our priority or the best use of our limited time. However, once we get the rest of the site migrated to new styles (which will take some time...), I would like to start customizing and cleaning up the default bootstrap styling. Most people don't heavily customize Bootstrap's style, and I think the 0 to 'good enough' is a strength. But, customizing Bootstrap in the way that you can with tailwind and others is totally possible, too. I'd like to get there eventually.
(For example: If you look closely, you'll note that we have at least 4 blues we've used... the snap logo, the greyish-blue backgrounds, there's the Berkeley blue colors in a couple places, and the default blues of Pure / Bootstrap. Oops. We can simplify that. :))
I assume part of this is discussion, but we definitely do want people to use it more for what is it. 
I absolutely understand. Plus, I'm probably not the average user, since I only help people on the forum, and do most of my programming outside snap (although searching through all my projects is faster in the editor...).
Ah, I see. I've never used tailwind before, I've only heard people like it more, so I don't really know.
That's great to hear.
I never go to the site either, except when I need to use the admin features. I'd like it better if "See code" opened the editor in the same tab, instead of a new tab; once I'm in the editor, why would I want to go back to the project page? I guess it depends on whether you spend time browsing the project space.
PLEASE NO IM ACTUALLY BEGGING YOU NOT TO USE TAILWIND
It's better than bootstrap.
Okay. So. I know you shouldn't really care that much, but pleeeeaase don't use Tailwind.
It is just soo annoying to work with when making extensions BECAUSE there isn't just a few classes specific to only a few elements to use dom selectors with, there's now a bunch of classes being used with those elements AND unrelated elements (does this make sense?)
Edit: the pure-button class doesn't exist anymore 
If it makes anyone feel better, I can no longer get the forum to look anywhere near how I like it. As we speak I am typing in white on gray, with baby blue highlights. And that flash-and-fade effect drives me crazy! Some epileptic somewhere is going to die because of it; then they'll fix it. (Whenever someone uses the word "modern" in connection with a web site I always want to cower under my bed.)
At least for you the actual text background is dark gray.
Edit: For some reason the screenshot looks way darker than when I'm actually typing...
I don't know how you have that color theme, but I need it. This is horrible
Edit: No, my color theme is light gray, yours is dark?
Ouch
Listen, @cycomachead, maybe I'm just blinded by nostalgia, or just scared of change, but please don't do the buttons like this
I'm sure you know what you're doing, but mann
Edit: I like the rest of the changes, but the buttons imo just don't fit the snap "feel" imho (also please don't use Tailwind, or if you do, pls give a bunch of the elements unique Ids so we don't have to use dom selectors that will break at the first new addition of a div)