solid
Create sitemap.xml
Re: https://github.com/solid/solidproject.org/issues/842
@csarven I created this using a online sitemap generator. Is this what you are looking for?
Thanks. I used the word sitemap generally: https://en.wikipedia.org/wiki/Site_map :
There are three primary kinds of sitemap:
- Sitemaps used during the planning of a website by its designers
- Human-visible listings, typically hierarchical, of the pages on a site
- Structured listings intended for web crawlers such as search engines
For our purpose, I had the first two points in mind. It is so that we have an inventory of the site's assets originating from the repositories (and possibly elsewhere) published under solidproject.org.
There is certainly overlap with what a crawler can get to (as with the XML Sitemap). Our internal sitemap (along the lines of tabular data below) however gives a broader view of what we have, track, and intend to do with them. It helps us to observe and ensure a URI Template that can be followed.
Here is a snippet below of what I had in mind.
- url: URLs of the tracked resources
- status: intended status code in response to
HTTP GET - design: information about the design (including architectural, presentational, behavioural) of the resource
- note: supplementary notes
| url | status | design | notes |
|---|---|---|---|
| https://solidproject.org/ | 200 | foo | bar |
| https://solidproject.org/TR | 200 | Should be 404 TR/ is canonical |
TODO: issue |
| https://solidproject.org/TR/ | 200 | Uses W3C specification design patterns | - |
I've created https://github.com/solid/solidproject.org/pull/856 (using the loc from the sitemap you've provided as initial input and some other manual entries that I've made) to track this by adding a section in existing website-strategy.md (for now). If this information should be tracked somewhere, that's fine. Can we continue in that PR? Or merge that PR and update as we go. That will tell us what pages are designed for or how a particular design should be reused across different pages.
Aside: That's just top-level input. We'll look at individual components on these pages (towards IA/UX) next.
FYI @KyraAssaad Jekyll has a sitemap plugin.
This is how you generate the sitemap intended for crawlers similar to the one you created: https://github.com/solid/solidproject.org/commit/d096c26d5300f8f7ae4cd896d1d279d49c3b5e04.
