Description
The about page contains a large amount of blank space and is pretty empty from a content perspective. I think the intention of all the white space was to scroll from a whole page / card to a whole page / card / section. At least for me, this does only work if I use an apple trackpad. With a mouse wheel, i just have to scroll a lot...
Suggestion:
- remove all the whitespace
- replace
Explore / Erkunden button with Karte / Map
- Are the device and measurement counts actually computed or fixed? If they are fixed, they should be computed to match the ones on the map.
- make the page scroll normally without forcing some focus on the elements
- remove meaningless content (e.g. "Entdecke Geräte", "Vergleiche Geräte", "Keine Datenrückhaltung" in the feature list)
- use same design in
Partner section and update content (t.b.d.)
- replace
gehosted von openSenseLab (What happened to our logo, by the way? 😅 ) with something like "Made with love in Münster by openSenseLab" (use proper logo) and move to footer? Atm, it looks like openSenseLab is just a partner.
- replace twitter icon with X icon
- update year in copyright notice
Use case
I want to learn something about the openSenseMap on the about page.
Implementation ideas (optional)
No response
Additional information (optional)
No response
Description
The about page contains a large amount of blank space and is pretty empty from a content perspective. I think the intention of all the white space was to scroll from a whole page / card to a whole page / card / section. At least for me, this does only work if I use an apple trackpad. With a mouse wheel, i just have to scroll a lot...
Suggestion:
Explore/Erkundenbutton withKarte/MapPartnersection and update content (t.b.d.)gehosted von openSenseLab(What happened to our logo, by the way? 😅 ) with something like "Made with love in Münster by openSenseLab" (use proper logo) and move to footer? Atm, it looks like openSenseLab is just a partner.Use case
I want to learn something about the openSenseMap on the about page.
Implementation ideas (optional)
No response
Additional information (optional)
No response