Sorry about the slow reply. ParkGrades is a GREAT idea. There's similar things put up by the city, but they typically pale in comparison. This also does a prett

Sorry about the slow reply. ParkGrades is a GREAT idea. There's similar things put up by the city, but they typically pale in comparison. This also does a pretty decent job of find all of our local parks near us (which many sites like this have failed miserably at). Excellent call to action. "Search for Parks" is the #1 thing to do at your site and you put that basically front-and-center all over the place. Many developers tend to miss this. Good job! A few things that I thought were curious: - After searching, I see "Museum Amenities" and then filter-like links which will reduce the result set to locations with certain characteristics. The title/purpose of this block here creates some end-user conflict on how to interact with it. You might consider changing the name to reflect it's purpose rather than it's description. (like "Filter by Amenity") - On the park search page, consider a different way to your "Advanced Search" description underneath. I'm not sure what you're trying to tell me to do, so you might want to have some sort of text fields with greyed-out, pre-populated examples. Try to use common conventions anywhere possible. Look at advanced search forms and try to get good ideas on how to lay them out. - The links to connect to Facebook, Twitter, RSS on the main page is offset from the elements themselves. In other words, the area to actually click a link is about 10px left of where they would line up with the image they represent. This was giving me unusual visual feedback on what was clickable and made me "miss" the click when I tried to click through. You're probably losing some valuable click-throughs here. - It looks like you're using Drupal for this site. I've noticed lots of areas where the design could be "tightened up". If you're still testing the market, that's one thing, but consider paying attention to this in the near future before any large-scale launches. Additionally, I think Drupal is a VERY extensible and fantastic CMS, but it's a BITCH to configure and manage. Keep this in mind going forward as you don't want to be too invested in a product that will ultimately hold back your site's long-term ambitions. Once you've validated the market, you should be thinking about how your technical choices will affect your product in the medium-long-term (1-3 years). Many people will say It's hard to plan this far ahead (especially with technology's current pace) but if you know that your site will really require the flexibility of Drupal versus a simpler CMS, you'd be better off knowing that sooner than later. - Open up your comments! There's no reason you can't use something like Disqus for handling it. You get better engagement and is one less hurdle for eventually acquiring users. (I've seen an implementation somewhere which onboards a Disqus account into a native user registration after a certain amount of repeat engagement with a user.) These are just a few suggestions off the top of my head. I can go into detail about any of these if I was ambiguous.