Post by @fasnix

The status entry area is just a box and post button
The status entry area is just a box and post button
Upon clicking into the status box the options become available
Upon clicking into the status box the options become available

Hey @stefano following up from my earlier comment with some quick edits from the DOM inspector. These are some UI/UX suggestions and why I'm making the suggestion. I hope this isn't over stepping and happy to take guidance on what kind of feedback you'd prefer instead.

Changes shown and why:

  • The default width increased from 720 to 800 to prevent overflow of Catch-up into separate line and 800 is a reasonable expectation for width for contemporary viewports.
  • Both of the screenshots show #littleFedi interface with timeline-nav moved above composer.
    • When a new user comes to the home timeline they don't see all the awesome post options, wonderful as they are, they are numerous and intimidating.
    • However, when they click into updating the status the options are revealed to them. This follows existing paradigm of clicking Poll / Content Warning / Schedule / Self Destruct which reveal relevant options when clicked.

In writing this up I also discovered a quirk with the Visual Editor, there's no mechanism to make a nested bulleted list. I switched to markdown to indent the list level and it works fine when doing that, it also handles traversing up the bullet hierarchy via backspacing as expected from other editors.

Happy to expand on anything I explained poorly! Also, you/team have been putting in some Herculean efforts with the updates, I hope there are scheduled naps đź’›

Cheers!

Replying to @shom

@shom
Love the suggestions, as the compose field gets much smaller, if not used.

@stefano

Replying to @fasnix
Sneek peek of the new composer
Sneek peek of the new composer

@fasnix @shom definitely!

Replying to @stefano
fasnix
@fasnix
Local unlisted en

@stefano
When I see Italian in the composer:
I wonder if the complete surface of littlefedi ever will get translated into several other languages, like e.g. German, French, Spanish, Esperanto or Interlingua. hihi

(Interlingua being understandable by speakers of Italian, French, Spanish, Portuguese ad hoc, without even having learned it, estimated 800 million to 1 billion speakers of that language worldwide, so a huge potential!)

https://interlingua.com

Sorry for "derailing" the topic ...

@shom

Replying to @fasnix

@fasnix @shom Some of them are already supported. Maybe Esperanto or Interlingua could be eventually added.

Replying to @stefano
fasnix
@fasnix
Local unlisted en

@stefano
That would be really cool!
No pressure, though <3

@shom

Replying to @stefano
Upper menu and compose field.
Upper menu and compose field.

@stefano
Interesting: when I tile the browser window in two separate areas (resolution: 1920x1080), the upper menu still flows in two rows.

The compose field now is sooo much calmer, thanks!

@shom

Replying to @stefano

@stefano wow, that looks so nice and sleek and it expands to give options without losing visual context. Nice work team and thanks for being so collaborative in seeking design input.
@fasnix

Replying to @shom

@stefano I would have the same suggestion for the compose box in threads as well where clicking into it exposes the options.
@fasnix

Replying to @shom

@shom @fasnix thanks. It makes sense!