Pet Circle discover pages improvements

Pet Circle notes

ui-main.css is in assets/.
Page partials are in views/.
Anything else not mentioned are extra files used to help local development.
SEO content (meta tags) are declared in a fake <seo> block at the top of each partial. These need to be extracted out into the <head> element in order to work properly (not sure how your build system works).
Change discover/preparing-for-a-puppy to discover/preparing-for-a-puppy-or-kitten or similar, in order to get extra hits (since it relates to more than just puppies).
Maybe look at JSON-LD for SEO (can be used to create Google smart cards).
For decorative images, add an alt="" attribute to designate it as such.
Add understandable alt text for images important to page content.
Ensure proper heading hierarchy (h1 > h2 > h3 > h4 > h5 > h6), descending by one step at a time. There should only be one h1 on each page.
Make sure to prioritise semantic HTML elements over their styling, so that they make sense to web crawlers and accessibility software. Styling should also be done based off element ID or class name (preferred), so that it is detached from the element's meaning and you can use it on any element as required. See https://developer.mozilla.org/en-US/docs/Glossary/Semantics#semantics_in_html for more information.

Run a Lighthouse performance test and other SEO feedback tools to see what aspects you can improve on.

Partials are put as-is inside the main tag.
Partials often fetch images and stuff from ./ which is rewritten to a Google storage bucket on build time, dumb server redirects aren't perfect but work good enough.

Name		Name	Last commit message	Last commit date
Latest commit History 33 Commits
assets		assets
built		built
templates		templates
views		views
.gitignore		.gitignore
.prettierrc		.prettierrc
README.md		README.md
index.js		index.js
package.json		package.json
yarn.lock		yarn.lock