Make this project's content appear in Google searches and otherwise be SEO-friendly

[JordanMartinez]

The issue here is that this repo's content won't appear in a Google search.

From a conversation on FP Slack:

yep. I'll make a point of searching your repo before undertaking more extreme measures 😄 It's a shame google doesn't seem to index github code. A google search for "purescript-quickcheck-laws" and related terms didn't return any results with example implementations

Yeah.... Perhaps one goal could be to migrate that repo from GH into an actual website with SEO?

I also understand that means work for you (unless you can figure out a way to share the work with others). Thanks for putting together the valuable resource that you've already created. If I can help, let me know. I'm still learning, but I would like to contribute to the community
Have you considered putting some content in GitHub wiki pages? I know Google indexes those, and it might be easier to do that than move everything to a new site. I'd be happy to help.

I would like to do the same with the docs repo somehow

[kurtmilam]

As I mentioned in the conversation, Google does index GitHub wiki pages. It also indexes (at least some) markdown pages:

While an entirely separate website might be nice, putting more content in the wiki and/or in well-named markdown pages might be a good first/interim step.

[JordanMartinez]

Slightly related to this but JordanMartinez/learn-halogen#18 relates here as pandoc can be used to produce an HTML page. One could convert this repo into HTML and then load that into some other repo that gets rendered by GH via GH pages or something...

[JordanMartinez]

Another way this could be improved is to convert this entire repository into a web application like Read the Docs but have everything served via a Haskell backend and a PureScript frontend.

[JordanMartinez]

The PureScript by Example book repo, thanks to milesfrain, recently decided to use mdbook to render the entire book as nice HTML page with search and anchors. I think I'd like to do the same here, and that might fix this issue in a very straightforward and easy way.

If that is done, then I'm not sure I would pursue #453

[JordanMartinez]

I believe #511 fixed this, but I'll leave this open until I can confirm that.