My New Website - Please Let Me Know What You Think!

Discussion in 'Website Creation' started by michael_marks|2, Feb 20, 2016.

  1. I have been a photo.net member and reader for a while but not active. I recently launched my website so I finally decided it was time to introduce myself and get your feedback!

    My website is dedicated to black and white film photography, the magic of the darkroom, and the community that loves it.

    I hope you will take a look at it and let me know what you think.

    www.michaelmarksphoto.com

    Many thanks in advance and best wishes,

    Michael
     
  2. Overall excellent. A pleasant almost old-fashioned (OK, OK, conservative!) design style, which to me ideally suits your style(s) of photography. Obviously you are a words man with an enjoyable, chatty style. A little more tight editing may suit some of your blog posts, but on the whole, if you read this and opt to leave everything as it is, I would go along with that. In summing up, if (when) I eventually get around to setting up my new web site, I would be closely following what you have done. Good one!
     
  3. JayDann,
    Many thanks for your kind words and critique. It took be awhile to get the site to capture the vision I had in my mind but I finally got there. I wanted to create a site that I would want to go visit and I am very happy with the outcome. I hope you do get your site going and would be happy to stay in touch on that.

    Best,

    Michael
     
  4. Michael, great work as far as I looked - I admire your urge to create a community and the thoughtful detail you've applied. Will they come is the next question, which comes down to how you promote and who knows what else.
    Bill
     
  5. Bill,
    Thanks for taking a look and your thoughtful comments. You are exactly right. I have started some get togethers and will be doing a workshop with another photographer as a start. Perhaps you can join the community and we can stay in touch!
    Best,
    Michael
     
    1. Warning: The banner role is unnecessary for element header.
      From line 118, column 2; to line 118, column 57
      d site">↩ <header id="masthead" role="banner">↩ <hg
    2. Error: Element hgroup not allowed as child of element header in this context. (Suppressing further errors from this subtree.)
      From line 119, column 3; to line 119, column 10
      anner">↩ <hgroup>↩ <h
      Content model for element header:
      Flow content, but with no header, footer, or main element descendants.
    3. Error: The hgroup element is obsolete. To mark up subheadings, consider either just putting the subheading into a p element after the h1-h6 element containing the main heading, or else putting the subheading directly within the h1-h6 element containing the main heading, but separated from the main heading by punctuation and/or within, for example, a span element with differentiated styling. To group headings and subheadings, alternative titles, or taglines, consider using the header or div elements.
      From line 119, column 3; to line 119, column 10
      anner">↩ <hgroup>↩ <h
    4. Warning: Element nav does not need a role attribute.
      From line 126, column 1; to line 126, column 68
      /></a>↩ ↩<nav id="site-navigation" role="navigation">↩ <b
    5. Warning: Element nav does not need a role attribute.
      From line 381, column 6; to line 381, column 62
      ↩ ↩ <nav id="nav-below" role="navigation">↩ <h
    6. Error: An img element must have an alt attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
      From line 394, column 128; to line 394, column 211
      ="_blank"><img src="http://www.michaelmarksphoto.com/wp-content/uploads/2015/12/facebook.png"></a>&n
    7. Error: An img element must have an alt attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
      From line 395, column 78; to line 395, column 162
      ="_blank"><img src="http://www.michaelmarksphoto.com/wp-content/uploads/2015/12/instagram.png"></a>&n
    8. Error: An img element must have an alt attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
      From line 395, column 247; to line 395, column 331
      ="_blank"><img src="http://www.michaelmarksphoto.com/wp-content/uploads/2015/12/pinterest.png"></a></
    9. Warning: The contentinfo role is unnecessary for element footer.
      From line 551, column 2; to line 551, column 42
      pper -->↩ <footer id="colophon" role="contentinfo">↩ <di
    10. Warning: Consider using the h1 element as a top-level heading only (all h1 elements are treated as top-level headings by many screen readers and other tools).
      From line 211, column 7; to line 211, column 30
      ">↩↩ <h1 >↩ <
    11. Warning: Consider using the h1 element as a top-level heading only (all h1 elements are treated as top-level headings by many screen readers and other tools).
      From line 265, column 7; to line 265, column 30
      ">↩↩ <h1 >↩ <
    12. Warning: Consider using the h1 element as a top-level heading only (all h1 elements are treated as top-level headings by many screen readers and other tools).
      From line 296, column 7; to line 296, column 30
      ">↩↩ <h1 >↩ <
    13. Warning: Consider using the h1 element as a top-level heading only (all h1 elements are treated as top-level headings by many screen readers and other tools).
      From line 183, column 7; to line 183, column 30
      ">↩↩ <h1 >↩ <
    14. Warning: Consider using the h1 element as a top-level heading only (all h1 elements are treated as top-level headings by many screen readers and other tools).
      From line 155, column 7; to line 155, column 30
      ">↩↩ <h1 >↩ <
    15. Warning: Consider using the h1 element as a top-level heading only (all h1 elements are treated as top-level headings by many screen readers and other tools).
      From line 324, column 7; to line 324, column 30
      ">↩↩ <h1 >↩ <
    16. Warning: Consider using the h1 element as a top-level heading only (all h1 elements are treated as top-level headings by many screen readers and other tools).
      From line 354, column 7; to line 354, column 30
      ">↩↩ <h1 >↩ <
    17. Warning: Consider using the h1 element as a top-level heading only (all h1 elements are treated as top-level headings by many screen readers and other tools).
      From line 241, column 7; to line 241, column 30
      ">↩↩ <h1 >↩ <
     
  6. Thanks but I am not sure what all of this means.
    Best,

    Michael
     
  7. Thanks for looking and your nice comment. I have to admit I don't know much about the subject matter contained on your website. However what is important is to keep things as simple and straight forward as possible. Ease of navigation is critical. Keep the content interesting and informative for the target audience.

    Hope this helps.

    Best,

    Michael
     

Share This Page