Dne čt 17. září 2020 E. Liddell via tde-users napsal(a):
> On Thu, 17 Sep 2020 04:43:15 +0200
>
> Slávek Banko via tde-users <ml-migration-agent@xxxxxxxxxxxxxxxxxx> wrote:
> > On Thursday 17 of September 2020 03:46:45 E. Liddell via tde-users
wrote:
> > > On Wed, 16 Sep 2020 23:24:49 +0900
> > > Michele Calgaro via tde-users
> > > <ml-migration-agent@xxxxxxxxxxxxxxxxxx>
> >
> > wrote:
> > > Now that I've taken the time to look around more, I think I know
> > > what kind of thing Slávek means. It involves a specialized CSS rule
> > > that moves the menu to the bottom of the page when the width of the
> > > viewport is less than 900px or so (since testing for portrait
> > > orientation is apparently not reliable). I'll see what I can do (if
> > > possible, I'd like the rearrange the menu horizontally when it's
> > > moved).
> >
> > Yes, that's exactly what I had in mind - a solution in CSS. This could
> > preserve the simplicity and no need for javascripts.
> >
> > Remember that if moving a menu is a response to a "narrow display",
> > then there probably won't be much space for the menu to be arranged
> > horizontally. That's my guess.
>
> I'm going to have to check up on the average resolution of modern phone
> displays. 500 or 600px should be enough. 300px is probably too little.
>
> > > > I think other sections could be reworked too.
> > > > 1) GIT, commit history, Packaging GIT, secure GIT --> just need
> > > > one entry to point to TGW. 2) uLAB GIT: should not be displayed,
> > > > since uLAB is an unrelated project from TDE 3) nightly builds:
> > > > either remove or point to PSB/PTB archives 4) Related projects:
> > > > they are part of the TDE repos, no need for a separate page on
> > > > main menu 5) RFEs: just remove that
> > > > 6) Donations (once we clarify the legal status of TDE): make link
> > > > stand alone and more visible 7) CLAs: as mentioned by Slavek, this
> > > > will be a separate discussion
> > > >
> > > > We could even simply consider to have a simple "Development" link
> > > > to point to the relevant section on Wiki in fact.
> > >
> > > There are definitely too many links in that section.
> > >
> > > -The GIT links should all be combined into one which points at the
> > > current repository, agreed.
> > >
> > > -Nightly builds are limited to specific distros and should be filed
> > > with the installation information for those distros.
> > >
> > > -There's already a link to the CLA on the "get involved" page—no
> > > reason to have it (or whatever replaces it) at the top level.
> > >
> > > -"TDE Team" has more to do with "Home > About" than "Development".
> > > We might want to punt the "Donations" link up to the first section
> > > as well, to make it more likely it will come to the attention of
> > > non-developers.
> > >
> > > -RFEs should be removed until their status is clarified.
> > >
> > > -"Related Projects" needs a different name and a content refresh to
> > > add libart-lgpl and TQT at minimum, since it seems to be mostly
> > > about libraries.
> > >
> > >
> > > Weeding thus reduces the menu structure to something like this:
> >
> > The proposed rearrangement looks good. I suggest only small changes to
> > the
> >
> > order at the second level:
> > > HOME: News, Features, About, Screenshots, Donations
> >
> > HOME: News, About, Features, Screenshots, Donations
> >
> > > GET TRINITY: Packages, LiveCDs
> > >
> > > DOCUMENTATION: FAQ, Wiki, Installation, Applications
> >
> > DOCUMENTATION: Wiki, Installation, Applications, FAQ
> >
> > > SUPPORT: Bugs, Mailing Lists, Service Alerts, Contact
> > >
> > > DEVELOPMENT: GIT, API Docs, Library Projects, Get Involved
> >
> > A little note here: We have three useful interfaces - CGit, Gitea and
> > Weblate. I believe that all three should be mentioned here.
> >
> > In addition, Commit history provides an excellent overview of what's
> > going on in git across all the individual GIT modules - it seems like
> > a good idea to keep it in the menu as well.
>
> The majority of the people visiting the site are users, not developers.
> Even for prospective developers, the nav menu "Developers" section
> is too complex right now. We should reduce the number of links to
> no more than 6 (5 or less would be better). Currently, people not
> familiar with the site are probably experiencing choice paralysis when
> they see the options.
>
> The "GIT" link should point at the most-used interface to the currently
> active source control repository (or at a subsidiary page explaining why
> there's more than one). Anyone who knows how to use a source control
> system will be able to get to the commit history from there. People who
> don't understand source control won't understand what a "Commit History"
> link means. It's something for developers to bookmark, not something
> that needs to be presented to everyone.
>
Regarding Commit history, I dare to disagree. GIT (CGit and Gitea) are a
clear choice for developpers. But Commit history, on the other hand, I
consider a very good simplification for ordinary users. I observe this on
my colleague, who never looks into GIT, but uses Commit history to quickly
and easiely look at current activity in the source code. That's why I find
Commit history a useful thing.
> Breaking Weblate out is legitimate, on the other hand, since it's aimed
> at translators rather than coders. So add a "Translations" link or
> similar.
>
> So we now have:
>
> DEVELOPMENT: Get Involved, GIT, API Docs, Library Projects,
> Translations, Resources
>
> That's more than sufficient links, IMHO. ("Resources" is explained
> below.) I promoted "Get Involved" to the top because it's really the
> first thing we want new visitors to see in this section. The text on
> the "Help Wanted" page should possibly be re-written to take current
> infrastructure into account (list things people can do without having to
> explicitly make contact with the dev team, and where to go to do it).
>
Yes, moving Get Involved to first place is a good idea. On the other hand,
Library Projects seems an uninteresting link that could be moved to
Resources. Likewise, the API Docs could be moved to Resources.
So it could be:
DEVELOPMENT: Get Involved, GIT, Translations, Commit History, Resources
> > > This structure has no "floating" headers without children, and the
> > > headers do not need to be links.
> >
> > Remember that Home and News, for example, are different pages. If the
> > items at the first level were not as a link, there would not be a
> > reasonable location for a backlink to the home page.
>
> The logo on the upper left has the same link destination as "Home"
> (which is a convention that's been around for more than twenty years and
> that I would expect most visitors to be aware of). Another unscientific
> survey of some of the sites I happen to have open tabs for shows that
> half of them use their logo as the only homepage link.
>
Yes, of course, you're right - I focused on the menu items and forgot about
the logo dominating the menu :)
> "Get Trinity" has the same destination as "Releases".
>
> "Documentation" leads to (mostly) older API documentation that
> probably doesn't need to be in the main menu.
>
> "Support" has the same destination as "Contact".
>
> The target of "Development" should probably be transferred to a
> lower-level link "Resources", which can then serve as a catch-all portal
> for the development tools.
>
> E. Liddell
>
Cheers
--
Slávek
Attachment:
signature.asc
Description: This is a digitally signed message part.
____________________________________________________ tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
