Renaming UI elements

[AdrianDAlessandro]

Description

This PR is for renaming a bunch of UI elements and urls for consistency. There are essentially no functional changes except that some old URLs will be dead now, but they are all internally consistent. The only new change is that there is a new framework overview page.

TODO:

• @anenadic to fill detail in the framework overview page.

Fixes #684 - opening in draft until the overview page is populated

Type of change

• Documentation (non-breaking change that adds or improves the documentation)
• New feature (non-breaking change which adds functionality)
• Optimization (non-breaking, back-end change that speeds up the code)
• Technical work (non-breaking, change which is work as part of a new feature)
• Bug fix (non-breaking change which fixes an issue)
• Breaking change (whatever its nature)

Key checklist

• All tests pass (eg. python -m pytest)
• The documentation builds and looks OK (eg. mkdocs serve)
• Pre-commit hooks run successfully (eg. pre-commit run --all-files)

Further checks

• Code is commented, particularly in hard-to-understand areas
• Tests added or an issue has been opened to tackle that in the future. (Indicate issue here: # (issue))

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[anenadic]

Looks great - thank you @AdrianDAlessandro.

I'll add an issue / PR to tidy up css for the mermaid SVG element.