• Textlint (github)

This webpage mentions a few different readability score algorithms. It would be interesting to either find or build textlint plugins for them:

• The Flesch Reading Ease formula
• The Flesch-Kincaid Grade Level
• The Fog Scale (Gunning FOG Formula)
• The SMOG Index
• The Coleman-Liau Index
• Automated Readability Index (ARI)
• Linsear Write Formula

Other links:

• https://datayze.com/readability-analyzer.php

• http://www.hemingwayapp.com/

https://help.github.com/en/articles/creating-a-custom-404-page-for-your-github-pages-site

https://github.com/whitecolor/yalc

https://speckyboy.com/on-page-seo/

Check out https://github.com/thinkmill/manypkg

Looking for a website checklist I found this great resource:

https://www.beewits.com/the-ultimate-web-design-checklist-things-to-do-when-launching-a-website/

https://cssnano.co/

Axe seems useful. I could use the axe-ci tool to test accessibility in a CI environment.

https://utteranc.es/

I came across moveable which allows you to build Draggable, Resizable, Scalable, Rotatable, and Warpable components. This might be usefull for RavenDesk Pagebuilder

tufte-css seems like an interesting starting point for building a blog.

This comment mentions how you can use devMiddleware.waitUntilValid(() => { /* do something here */ }); to wait for the build. This would be great for larger webpages / slow computers.

Could I setup so that it shows a Setting up / building page while it builds and then automatically refreshes when its up? This could perhaps be combined with webpack-hot-middleware.

Similarly too create-react-app RavenDesk should check if the port it want to use is in use ,and offer up an alternative instead.

https://www.staticgen.com/

• https://en.wikipedia.org/wiki/Sitemaps
• https://yoast.com/what-is-an-xml-sitemap-and-why-should-you-have-one/

SaaS Pages shows some great examples and guidelines for creating a landing page for a SaaS-company. Maybe I could use this as an example for what one can create using RavenDesk Pagebuilder?

The ravendesk dev command currently doesn't handle errors that well (where source code it tries to build might be mallformed). I need to add some try catches around and some kind of retry logic to make this more consistent for people to work with.

When having a multicompiler setup where the Webpack config is an array of two or more configs I sometimes get the following error:

Error: Cannot read outputFileSystem of a MultiCompiler

The problem comes from this part of the code where it tries to access the outputFileSystem when it's a multicompiler build.

The solution seems to be to follow what this comment says. In other words using something like the following code:

var isMemoryFs = compiler.outputFileSystem instanceof MemoryFileSystem;
if(isMemoryFs) {
   fs = compiler.outputFileSystem;
} else {
   fs = compiler.outputFileSystem = new MemoryFileSystem();
}

TODO

• Try to use such a solution to fix the problem
• Write a unit-/integration- test for it

http://ogp.me/

Could we do UI diffing in PR's similarly to this?