Interactive IDG framework

[Greenheart]

Quick UI/UX exploration.

Mobile first is very important, but it should also work on larger screens.

In the future, consider that this might be embedded on other pages

[Greenheart]

Mobile support is ready for testing on https://idg.tools/framework :)

Next up is making it use the screen space in a good way on larger screens too

[Greenheart]

The initial version is now closer to ready.

Remaining tasks:

• Improve the UI and UX on larger screens: 1) make the dimension names visible by default. 2) Maybe use two column layout when possible to use horizontal space in a better way. For example show the skills to the side, and the reflection question together with the skill description.
• Add the skill symbols as soon as they become available (though publish only just before the IDG summit)
• Add the translated languages that are visible in the GitHub graph of forks, but haven't been merged into the main repo yet. Try opening pull requests for each branch that is found. Then ping the creators and thank them for their contributions.
• Add a simple way for people to help improving the translations and local versions of the framework. Basically a call to action on the framework page. Create an improved guide for how people can contribute with translation and localisation work.
• Also clarify how to add a new language that doesn't yet exist in the CMS. We also potentially need to update the locale switcher (CSS overrides for example) to allow switching to all locales (that now are almost outside of the screen).
• Add translations based on the PDF framework documents that are already available
• Improve the guide for how to contribute with translations. We need to more clearly describe how to submit a PR so the changes can easily be visible for review, feedback, improvements and merging.

Future

• Add reflection questions for each skill (should it be part of the skill and dimensions, so people translate the questions together with the framework? Or should we create a separate CMS concept for it?) To improve the UX for translators it's probably best to store the question within each skill. Then we make it easier to contribute. The extra data for each skill is no problem, and can safely be ignored in other places where it isn't needed. We should add an array of strings, starting with the three questions for each skill.