broken website

[thefasquelle]

Description
For months I have not been able to find information under https://rubberduckvba.com/Features/Summary
All feature boxes show an error message and links don't work

https://rubberduckvba.com/Features/Summary?name=UnitTesting

https://rubberduckvba.com/Features/Summary?name=CodeInspections

Is the issue on my side or is the website broken ? If yes, is there an alternative way to find this info, apart from the blog that is sometimes outdated ? (I am mostly interested in code inspections and unit test documentation)

Tested on my computer and my phone, on two different networks and using chrome and firefox with all extensions disabled

[retailcoder]

Hi! Indeed the site is all kinds of broken at the moment, which... sucks. I'm in the middle of pretty intense home renovations right now, but still making good under-the-radar progress on rebuilding the whole website.

The main issue is that acquiring the database connection is taking longer than the site/client is waiting for - basically everything times out just connecting, which is ridiculous.

In the meantime the inspections page sometimes manages to load content, at least partially - and the filtering, pagination, and "retry" buttons kinda work:
https://rubberduckvba.com/Features/Summary?name=Inspections

And then individual inspections' pages still work but you need the actual inspection names (which happen to be the headings of each inspection box before the formatted content is loaded):

https://rubberduckvba.com/FeatureDetails?name=AssignedByValParameter

These specific pages are used for linking to inspection details in Rubberduck's inspection results toolwindow.

[thefasquelle]

Thank you for your response. Quick and helpful as always.
I have a way to access all docs, that will do.

If someone else has trouble navigating the website, note that for some pages you need to put the feature name after
https://rubberduckvba.com/FeatureDetails?name= and for other pages you need to put it after https://rubberduckvba.com/Features/Summary?name=
e.g. https://rubberduckvba.com/Features/Summary?name=FakesApi
The name to put at the end of URL is the title of the box with the error

[retailcoder]

The features model is hierarchical, and route through /Features/Summary?name=. This content is basically markdown documents stored in the backend database.

The "feature items" are something else entirely, they're extracted from xmldoc comments directly from the .xml assets tied to a release/tag - that's the individual inspections, quick-fixes, and annotations pages; these route through FeatureDetails?name=.

Side note / good news, the rewritten site is going to be deployed as a Docker container on Azure, with all its data in a small SQLite database - and it's all instantaneous!