Salta al contenuto
0
  • Categorie
  • Recenti
  • Tag
  • Popolare
  • Mondo
  • Utenti
  • Gruppi
  • Categorie
  • Recenti
  • Tag
  • Popolare
  • Mondo
  • Utenti
  • Gruppi
Collassa

Forum Federato

Di Piero Bosio
  1. Home
  2. Categorie
  3. Feature Requests
  4. Why the NodeBB composer holds users back

Why the NodeBB composer holds users back

Pianificato Fissato Bloccato Spostato Feature Requests
4 Post 3 Autori 0 Visualizzazioni
  • Da Vecchi a Nuovi
  • Da Nuovi a Vecchi
  • Più Voti
Rispondi
  • Topic risposta
Effettua l'accesso per rispondere
Questa discussione è stata eliminata. Solo gli utenti con diritti di gestione possono vederla.
  • dave1904undefined Questo utente è esterno a questo forum
    dave1904undefined Questo utente è esterno a questo forum
    dave1904
    scritto su ultima modifica di
    #1

    Hi all,

    from discussions in another, competing forum running a different software it has become clear that the composer editor is a real barrier: users there explicitly say they will not switch to our NodeBB forum because even simple actions like inserting a link feel too complicated in the current composer, especially on mobile devices.

    There is also a steep learning curve for new users, as many people (especially older users) are not familiar with Markdown and struggle with basic tasks such as formatting text. Even simple actions can be frustrating. For example, having to scroll horizontally to find certain buttons or functions that are hidden for the time being. Any evaluation of the composer should include its accessibility challenges.

    I genuinely hope this will be addressed in the future, as improving the composer would remove one of the biggest obstacles preventing more users from adopting NodeBB.

    Thank you and best regards
    David

    Kichaeundefined 1 Risposta Ultima Risposta
    • dave1904undefined dave1904

      Hi all,

      from discussions in another, competing forum running a different software it has become clear that the composer editor is a real barrier: users there explicitly say they will not switch to our NodeBB forum because even simple actions like inserting a link feel too complicated in the current composer, especially on mobile devices.

      There is also a steep learning curve for new users, as many people (especially older users) are not familiar with Markdown and struggle with basic tasks such as formatting text. Even simple actions can be frustrating. For example, having to scroll horizontally to find certain buttons or functions that are hidden for the time being. Any evaluation of the composer should include its accessibility challenges.

      I genuinely hope this will be addressed in the future, as improving the composer would remove one of the biggest obstacles preventing more users from adopting NodeBB.

      Thank you and best regards
      David

      Kichaeundefined Questo utente è esterno a questo forum
      Kichaeundefined Questo utente è esterno a questo forum
      Kichae
      scritto su ultima modifica di
      #2

      dave1904 There is a WYSIWYG composer. You just need to install/enable it as a plugin. It doesn't play nicely with Lemmy, though (nor Mastodon, IIRC), so it's not a great option if you're interested in federation.

      dave1904undefined 1 Risposta Ultima Risposta
      • Kichaeundefined Kichae

        dave1904 There is a WYSIWYG composer. You just need to install/enable it as a plugin. It doesn't play nicely with Lemmy, though (nor Mastodon, IIRC), so it's not a great option if you're interested in federation.

        dave1904undefined Questo utente è esterno a questo forum
        dave1904undefined Questo utente è esterno a questo forum
        dave1904
        scritto su ultima modifica di
        #3

        Kichae Changing to the WYSIWYG composer breaks all the posts created with the original composer afaik, which are ~50k in my forum.

        That aside, I think the editor out of the box shouldn’t only be usable for technically experienced people, but should be immediately understandable for everyone. One small example: when clicking link, the composer currently produces

        [link text](https://community.nodebb.org/link%20url)
        

        On mobile devices in particular, this is so cumbersome that some users find it nearly unusable. An alternative could be a simple dialog with separate fields for link text and URL. This is just one illustration. There are certainly other small changes of this kind that could make the composer significantly more approachable for casual users.

        The fewer barriers there are, the more people will actually use it and the editor is a key element of any forum software.

        julianundefined 1 Risposta Ultima Risposta
        • dave1904undefined dave1904

          Kichae Changing to the WYSIWYG composer breaks all the posts created with the original composer afaik, which are ~50k in my forum.

          That aside, I think the editor out of the box shouldn’t only be usable for technically experienced people, but should be immediately understandable for everyone. One small example: when clicking link, the composer currently produces

          [link text](https://community.nodebb.org/link%20url)
          

          On mobile devices in particular, this is so cumbersome that some users find it nearly unusable. An alternative could be a simple dialog with separate fields for link text and URL. This is just one illustration. There are certainly other small changes of this kind that could make the composer significantly more approachable for casual users.

          The fewer barriers there are, the more people will actually use it and the editor is a key element of any forum software.

          julianundefined Questo utente è esterno a questo forum
          julianundefined Questo utente è esterno a questo forum
          julian
          scritto su ultima modifica di
          #4

          dave1904 said in Why the NodeBB composer holds users back:
          > On mobile devices in particular, this is so cumbersome that some users find it nearly unusable. An alternative could be a simple dialog with separate fields for link text and URL.

          That's actually quite a good workaround. It would probably be a good idea for us to implement this in the default composer.

          1 Risposta Ultima Risposta
          Rispondi
          • Topic risposta
          Effettua l'accesso per rispondere
          • Da Vecchi a Nuovi
          • Da Nuovi a Vecchi
          • Più Voti


          • Accedi

          • Accedi o registrati per effettuare la ricerca.
          • Primo post
            Ultimo post