5 ms·

Oh wow. That cooking stackexchange is hideous. There is no visual connection between the topic and the design - why use blue gridlines and pencil shaded widgets

Oh wow. That cooking stackexchange is hideous. There is no visual connection between the topic and the design - why use blue gridlines and pencil shaded widgets for a food and cooking site? It seems more of a drafting or a tailoring site. I don't need fancy backgrounds or images, but perhaps use the site colour scheme to allude to the wonderful colours, senses, flavours, tastes, and pure enjoyment that you get from cooking and eating. For example, chowhound uses small splashes of red to give their site some "flavour". There is no joy in that cooking stackexchange. It is like cooking for computers.

username3 16y ago
It's beta. That's how the other beta stackexchange sites look like.
- barkingcat 16y ago
  I'm not sure that's a real excuse for a cooking site to look like that, even if it were in beta. But I accept, perhaps the people who run the site didn't have time (or money) and just applied the default templates, and tried running it to see whether it will work.
- slantyyz 16y ago
  It's beta. That's how the other beta stackexchange sites look like. That's part of the problem. If you look at the StackExchange FAQ, this is what they say about the Beta phase: Beta. Perhaps the most important phase. This is the actual, live site set up on a "probationary" basis to see if people will use it. If you can't customize the user experience in a manner appropriate to the subject matter, you're being set up to fail. That's why I personally have a strong dislike for the Area51 'vetting' process.
  - edanm 16y ago
    The idea isn't to customize it now. It's to customize it together, as a community, during the beta phase. Remember that the site is about a week old, most MVPs don't look nearly as good on their first week, nor have nearly as much traffic driving them right away.
    - amyt 16y ago
      Right but which community is going to customize the cooking site? It won't be foodies who aren't terribly techie because they'll be turned off immediately and won't pass go. So it will be developer types customizing it, even though the potential audience is so much wider.

username3 16y ago

It's beta. That's how the other beta stackexchange sites look like.

barkingcat 16y ago
I'm not sure that's a real excuse for a cooking site to look like that, even if it were in beta. But I accept, perhaps the people who run the site didn't have time (or money) and just applied the default templates, and tried running it to see whether it will work.
slantyyz 16y ago
It's beta. That's how the other beta stackexchange sites look like. That's part of the problem. If you look at the StackExchange FAQ, this is what they say about the Beta phase: Beta. Perhaps the most important phase. This is the actual, live site set up on a "probationary" basis to see if people will use it. If you can't customize the user experience in a manner appropriate to the subject matter, you're being set up to fail. That's why I personally have a strong dislike for the Area51 'vetting' process.
- edanm 16y ago
  The idea isn't to customize it now. It's to customize it together, as a community, during the beta phase. Remember that the site is about a week old, most MVPs don't look nearly as good on their first week, nor have nearly as much traffic driving them right away.
  - amyt 16y ago
    Right but which community is going to customize the cooking site? It won't be foodies who aren't terribly techie because they'll be turned off immediately and won't pass go. So it will be developer types customizing it, even though the potential audience is so much wider.