There have been various posts here in the last days describing how difficult it is for new people to start using Lemmy. In fact they are absolutely correct, it is much easier to get started on Reddit. But what many forget is that Lemmy is not a corporation employing dozens of full-time designers, running A/B-tests and so on. Lemmy is an open source project run by volunteers, with only @dessalines and me working on it full-time. Neither of us is a particularly good designer, and our time is mainly spent working on the backend (database, federation, api), and preparing the upcoming 1.0 release.
If you see anything on join-lemmy.org or in the Lemmy UI itself that could be improved, the best option is to make that improvement yourself. Both of them use standard web technologies (nodejs, tailwindcss, inferno etc). The userbase here is quite technical so there are many of you able to contribute. We rarely reject any pull requests as long as they make a real improvement. Though it usually requires a little back and forth to review the changes and then address the review comments.
You can find the source code for join-lemmy.org here and follow development instructions in the readme. Regarding the default Lemmy UI go here and read the documentation with development instructions. If you are not a developer you can still help, for example by improving the documentation. Additionally you can make changes to the texts for joinlemmy and lemmy-ui.
All this said, there have also been some suggestions to make onboarding easier by directing new users to a hardcoded default instance. This may sound like a good idea at first but won’t work well in practice. Running such an instance would take significant time for administration and moderation, but we maintainers are already too busy. Besides it would be impossible to reach an agreement who this default instance should federate with or how exactly it should be moderated. So if you want to get nontechnical users to Lemmy, the solution is to link them directly to a specific instance based on their interests.
There’d probably arise a need of a default instance with only guest access for a test drive before they pick their own instance, with some pop ups pointing at the fact that the name [email protected] means he is a part of some meta-subreddit lemmy.ml, that doesn’t mean shit for he just helped [email protected] with a link to the source. Their likes are collected but never shown. When they’d want to stop lurking and finally press a login button, it shall instead invite them to see instances of people they liked before first, others next, with tips what lead some rank so high in their list. After the signup is confirmed, their likes may or may not be transported, but their temporal profile is deleted.
I see the natural flow would be something akin to that: we start with a showcase of general content from different nearly-default instances and then get them recs about persons they did enjoy reading.