Testing and jotting some notes on my Boox Tablet this morning
Fix Leaderboards data pipelines and do a UI audit too
Bug: While editing a very long page, I kept getting "error page not saved" api errors, which interrupted my writing and moved me to the top of the screen, it shouldn't reset my scroll, and perhaps it could be a toast error in the bottom right instead of our full-page error which interrupts? ideally also the root cause of that error would be fixed too, since it seems like page save operations were only occuring on that very long page, but page save operations worked just fine elsewhere
Down arrows from selection of the bottom line to select through various UI elements, kinda interpreting cursor as focus state, not to collide with the down key page scroll behavior when things are not focused
In e-ink mode should we make primary buttons and secondary buttons look more similar? like perhaps primary buttons shouldn't have black fill (too contrasty) but perhaps they could have thicker strokes? audit this on design systme page when e-ink mode is enabled
Given whichever page set a page lives in (sets come from page list component) we can have previous / next buttons to go to prev / next page in the set, pages can live in many different sets
In "more by username" page stat card, we can have a "all by username" button that goes to the user's pages tab
E-ink usage? Theme usage? Dark vs light vs system? Devices? Do we know if devices are e-ink?
In product kpis let's add a "pages supported" stat for number of pages supported, i.e. if one supporter is supporting 3 pages, that'll be 3. we can also have a "total supporters" stat for all unique supporters. So that one supporter supporting 3 pages would be a value of 1, since it's one unique supporter
Make date and location less prominent
Double check supporters graph to see if it’s working properly
Do a UX pass at all the version flows
Recent edits counter doesn’t increase immediately after new version is saved
How are page views calculated? Is it truthful?
Fix mobile settings headers now that we’ve made the global mobile header persistent, our settings and admin settings headers should therefore be scooted down a little bit