{"id":51,"date":"2026-05-15T13:57:12","date_gmt":"2026-05-15T13:57:12","guid":{"rendered":"https:\/\/halfyolanda.com\/blog\/?p=51"},"modified":"2026-05-15T14:17:38","modified_gmt":"2026-05-15T14:17:38","slug":"sbw-revisited","status":"publish","type":"post","link":"https:\/\/halfyolanda.com\/blog\/index.php\/2026\/05\/15\/sbw-revisited\/","title":{"rendered":"SBW Revisited"},"content":{"rendered":"\n

Initial Version<\/strong><\/p>\n\n\n\n

The initial version of the website was heavily reliant on the visual design and on meeting the project criteria. Overall, it achieved my goal of a functional website, but, as usual, there were areas for improvement. The code was heavily reliant on IDs, misuse of semantics, inconsistent alt-text, non-inclusive, and weak SEO. So I started to slowly dissect the website starting off with the feedback from my professor, David Watson. <\/p>\n\n\n\n

Revision<\/strong><\/p>\n\n\n\n

For the website, I began the revision by addressing my professor David Watson’s feedback. \u00a0There were several points that he made that I needed to address.<\/p>\n\n\n\n

    \n
  1. Hard-coded uppercase<\/strong>\n
      \n
    • There were several places in my code where I’d written text in uppercase directly in the HTML, mainly on the home page. I switched these out and used text-transform: uppercase<\/code> in CSS instead \u2014 this way the styling stays in the stylesheet where it belongs and is much easier to change in the future.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
    • Markup semantics<\/strong>\n
        \n
      • David flagged that I wasn’t always using <section><\/code> correctly and suggested using <figure><\/code> when pairing an image with text. I went through my code and found the main issue on the “What’s in Store” page. The products grid had images and captions sitting inside a <div><\/code> with plain <p><\/code> tags. I replaced these with <figure><\/code> and <figcaption><\/code>, which is the proper semantic choice for image caption pairings.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
      • Alt text consistency<\/strong>\n
          \n
        • Some of my alt text was describing the image visually, and some was explaining its purpose, which wasn’t consistent. I went back through all the images across the site and tried to keep the approach uniform throughout.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
        • Navigation hover state<\/strong>\n
            \n
          • The hover effect on the navbar was causing nearby elements to shift around, which David flagged as a major distraction. I revised the styles so the hover effect stays contained to the element being hovered over without nudging anything else.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
          • Footer colour<\/strong>\n
              \n
            • David suggested swapping the mustard yellow footer for the green used elsewhere on the site. I did try it, but I wasn’t convinced by it either. I ended up going with a neutral beige instead, which I think sits better with the overall palette. Below you can see the mustard yellow, which was the initial design. With the new design, I was able to have a stronger play on colors as well. <\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
              \"\"<\/figure>\n\n\n\n
              \"\"<\/figure>\n\n\n\n

              After reviewing David’s feedback, it was time to begin revising the website based on what we learned over the past few months. The first task I started with was the 404 page, which I initially didn’t have.<\/p>\n\n\n\n

              404 Page<\/strong><\/p>\n\n\n\n

              This was done through the .htaccess file. I designed a friendlier page that aligned with the site’s branding. It also returns the user to the main page and enhances their overall experience. Connecting the 404 page to my site was a struggle, but I got there eventually with help from my classmates Sarah & Season. \u00a0<\/p>\n\n\n\n

              \"\"<\/figure>\n\n\n\n

              SEO<\/strong><\/p>\n\n\n\n

                \n
              • Meta descriptions and titles<\/strong> \u2014 each page had a unique, descriptive <title> and <meta name=”description”> tag written with relevant keywords for a local bike shop in Horsham.<\/li>\n<\/ul>\n\n\n\n
                  \n
                • Geo meta tags<\/strong> \u2014 I added geolocation SEO tags to every page with Horsham’s coordinates and region (shoutout to Season’s blog for the guidance on this one!).<\/li>\n<\/ul>\n\n\n\n
                  \"\"<\/figure>\n\n\n\n
                    \n
                  • sitemap.xml<\/strong> \u2014 created a sitemap listing all your pages with lastmod, changefreq, and priority values. I wasn’t initially planning to add this, but after going through Season’s journal, I decided it was worth doing properly.<\/li>\n<\/ul>\n\n\n\n
                    \"\"<\/figure>\n\n\n\n
                      \n
                    • robots.txt<\/strong> \u2014 I added a robots file to guide search engine crawlers on what to index, and pointed it to the sitemap.<\/li>\n<\/ul>\n\n\n\n
                      \"\"<\/figure>\n\n\n\n
                        \n
                      • Google Search Console<\/strong> \u2014 I set up Search Console for the site and submitted the sitemap directly so Google can start crawling and indexing the pages.<\/li>\n<\/ul>\n\n\n\n
                        \"\"<\/figure>\n\n\n\n

                        Accessibility<\/strong><\/p>\n\n\n\n

                        The next thing I tackled was accessibility. I started by running the site through several tools we’d used in the module, including the WAVE tool and PageSpeed Insights. This gave me a stronger idea of where the website stood before making any changes.<\/p>\n\n\n\n

                        \n
                        \n
                        <\/div>\n<\/div>\n<\/div><\/div>\n\n\n\n
                          \n
                        1. ARIA Labels – the website initially had none, so I needed to add them to the <nav>, <main>, <footer>, and any other links that were on the site.<\/li>\n\n\n\n
                        2. Accessibility Statement – This page was added and can be found in the footer. It outlines the page’s dedication to an inclusive website and guides users to contact us about any issues.<\/li>\n<\/ol>\n\n\n\n
                          \"\"<\/figure>\n\n\n\n

                          3. Skip link- I added a skip to main content link for keyboard users and screen readers.<\/p>\n\n\n\n

                          4. It was also suggested that I reduce some of my image sizes. However, after reviewing them, I felt that further compression would compromise image quality. Given that they were already well-optimized and my PageInsights score was at 83, it didn’t feel necessary.<\/p>\n\n\n\n

                          5. One suggestion was to improve the contrast of white text on a green background. After reviewing it, I felt the contrast was sufficient and didn’t negatively impact readability, so I chose not to make changes here.<\/p>\n\n\n\n

                          JavaScript<\/strong><\/p>\n\n\n\n

                          For the JavaScript element, I decided to add a dynamic opening hours banner at the top of the page. Since the site is mobile-first, I felt this was the most practical spot for it. The banner automatically updates based on the current time and day, changing both the text and color to reflect whether the shop is open or closed.<\/p>\n\n\n\n

                          \"\"<\/figure>\n\n\n\n
                          \"\"<\/figure>\n\n\n\n

                          PHP<\/strong><\/p>\n\n\n\n

                          The last task I tackled was the PHP server-side. For this, I moved the header, navigation bar, and footer into shared include files and converted all my HTML files to PHP. I kept the header and nav together in one file and the footer in another. This made the codebase much easier to manage and maintain, so any future changes to the header or footer only need to be made in one place.<\/p>\n","protected":false},"excerpt":{"rendered":"

                          Initial Version The initial version of the website was heavily reliant on the visual design and on meeting the project criteria. Overall, it achieved my goal of a functional website, but, as usual, there were areas for improvement. The code was heavily reliant on IDs, misuse of semantics, inconsistent alt-text, non-inclusive, and weak SEO. So […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-51","post","type-post","status-publish","format-standard","hentry","category-content-management"],"_links":{"self":[{"href":"https:\/\/halfyolanda.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/51","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/halfyolanda.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/halfyolanda.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/halfyolanda.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/halfyolanda.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=51"}],"version-history":[{"count":3,"href":"https:\/\/halfyolanda.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/51\/revisions"}],"predecessor-version":[{"id":67,"href":"https:\/\/halfyolanda.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/51\/revisions\/67"}],"wp:attachment":[{"href":"https:\/\/halfyolanda.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=51"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/halfyolanda.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=51"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/halfyolanda.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=51"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}