(Why/How/When) Does Building a CMS "fit in" to the Product Roadmap?

[nelsonic]

Short answer: Yes!
Long(er) answer: Stay tuned!

[nelsonic]

Supporting data/screens for long-form answer/post I am writing. Please ignore!
if you don't like "criticism" STOP Reading Now and instead enjoy some "pink fluffy unicorns" ...

---

Preface / Context

As the "technical lead" of @dwyl the "buck stops here".
I take ownership and responsibility for anything where technical choices, implementation and quality control is concerned. Which means if something is "sub optimal" in any way, it's "on me".

Good Thinking

Site

https://www.good-thinking.uk

## Case Study

https://dwyl.com/case-studies/nhs-england/good-thinking.html

Objective Technical Analysis

Write-up to follow in a blog post ... just uploading the screenshots for now.

Page Speed

https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fwww.good-thinking.uk

Light House

https://googlechrome.github.io/lighthouse/viewer/

Web Hint

https://webhint.io/scanner/56cafff5-aab4-41b9-a7c0-f1c4d339c46d

CSS Stats

https://cssstats.com

Wagtail...?

It should be "safe to assume" that https://wagtail.io is made using the Wagtail CMS:
it's unclear from: https://builtwith.com/?https%3a%2f%2fwagtail.io ...
what is clear is that they are using a "Kitchen Sink" approach:
https://builtwith.com/detailed/wagtail.io

The https://webhint.io stats for the https://wagtail.io website: 148 errors:

Lighthouse Score: 62% for accessibility and 67% for performance.

https://cssstats.com/stats?url=https%3A%2F%2Fwagtail.io

If the CMS does not optimise for accessibility or performance "out-of-the-box"
we will spend all our time building with the CMS only for our end-user's time to be wasted
with slow page-loads and inaccessible content.

"Throwing Stones"...?

To be clear the dwyl.com website should not be used as a "benchmark" for all these metrics.
We know we are "behind"! see: dwyl/dwyl-site#447 and dwyl/dwyl-site#450

Light House Score: pretty freakin' good. (we aren't focussed on having a PWA right now...)

WebHint not so great ... we have an issue open for it! dwyl/dwyl-site#450
https://webhint.io/scanner/d873de22-23e1-445d-afe4-0fd59818a920

However what we do want to highlight is that while dwyl.com certainly requires some "TLC",
the website is not an "Advert" for a CMS which is supposed to be the "answer to all your problems" ...
According to the "testimonial" on their homepage, @pelliportraits want's to "Marry" the software: 🙄

https://twitter.com/pelliportraits 27 tweets. of which the Wagtail quote is nowhere to be found.

Anyway, given my experience of using Wagtail, I want a divorce.
I don't feel that the time we (the @dwyl team) invested in building a CMS-based website
had a good "return on investment".
The Travis-CI build log: https://travis-ci.org/wagtail/wagtail/builds is insightful:

At the time of writing/capturing this, the master branch of the project has failed build.
And it's not an "isolated" event.
What this should tell you is that Wagtail's core developers treat code quality as a "low priority"
and using the CMS is at best "hit and miss".

[nelsonic]

Closing as not "core".