I call BS. This appears to be a new take on "Show HN"...trying to get attention. The site works, looks OK, and you appear to have users, so it doesn't really suck. If you thought the concept sucked, then you wouldn't have done the site in the first place. If this were a legit post, I would say this: I think this is a relatively crowded niche you're in. I'm also sure that you dramatically overspent if you actually spe…
We put $200k into a site that sucks. Please destroy us with your criticism
101–110 of 138 posts
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#102Re: We put $200k into a site that sucks. Please destroy us with your criticism
#103Earlier quoted context omitted.
To clarify, for the `.buy-button` class, is that where one should put super-specific styles like `margin-left: 12px`? Also, is there a good place I can learn these kind of things? I'm a programmer trying to get better at CSS (SCSS now that we've setup the asset pipeline)—so far I've been reading random A List Apart and The Sass Way articles, but I feel like I could use a more holistic, in-depth understanding of CSS i…
To answer your first question, yes that is exactly where you should put your super-specific styles. You want to put your communal styles in your placeholder, styles that all types have but are different in the mixin (background color, etc) and the rest on the class itself. The best way to get better at Sass is to follow people who are active in the community (which unfortunately is not me). Start with Chris Coyier an…
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#104Brilliant marketing stunt. Take my point.
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#105When the list first loads, it is not visible on the screen but instead pushed down by a large margin. Also I believe many of your hits will come from google searches vs friend shares. Maybe make 100 SOE lists in house.
Also, what is a "SOE list"?
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#106I think the idea is great - I actually had the same idea last summer and built www.curate.im which ended up getting absolutely nowhere (log in with username 'test' and pw 'test' if you wanna see inside). In terms of your actual site, the focus seems to be less on the content itself and more on sharing/commenting on things, almost trying to force people to interact with the site. Not a huge fan of the content on there…
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#107I think HN is the wrong kind of audience to seek feedback from for your specific site. It appears to be pop-culture/teen culture focused, which you won't find here in HN.
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#108Oh man, not another "11 sexy girls with star wars tattoos"... Normally I would follow "if you don't have anything nice to say" but since you literally asked for it: Your site tries to build a better mousetrap in one of the worst corners of the internet (better means 'worse' in this case). "List sharing" is a known cheap trick for internet marketers who are the bottom of the barrel, exploitative of both original conte…
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#109I'll take a different tilt: Your biggest problem is that you have 4 people listed on your team page yet there are two with the title 'Project Manager'. From what I can tell from playing with the site, it just lets you build 'top 10' style lists and allows people to vote/comment on them. Frankly, this is a weekend project for a good developer or for a better outcome, a good developer/designer pair. What exactly are th…
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#110You seem to be resizing the footer in javascript (I haven't looked at the code so could be off base) and sometimes it seems to go a little crazy. When I first scrolled to the bottom there was a huge empty space below the "blog browse about... " stuff. About 800 pixels I would estimate. It seemed to go away when I refreshed and resized the page, but something caused it to happen at least one time, so under the same co…