purescript / purescript/pursuit
Sitemap
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 174
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
Presumably this would help a lot with search engine results.
We could have one sitemap index at /sitemap.xml (see http://www.sitemaps.org/protocol.html#index), and then have one sitemap per package per version, at eg /packages/purescript-prelude/0.1.0/sitemap.xml.
We'd have to regenerate the sitemap index every time a new package was uploaded, but the individual package version sitemaps would only need to be created once (unless someone re-submitted a particular package version).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the sitemap protocol linked in the issue and the site's /sitemap.xml entry point. Define how the index and per-package-version sitemaps should be generated when packages are uploaded or resubmitted. Done means search engines can retrieve the index and each package version's sitemap at the proposed paths.
Written by the indexing model from the issue text.
Assessment
- Domain
- search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100