Hi all,
I'm launching a series of threads related to the migration of individual services. The main web server was listed first.
-- Migration status --
The web server is already successfully migrated to the virtual machine on the tde-box. It was migrated almost unchanged. The changes concerned only:
1. Service alerts - instead of a manually maintained page, the real status of services is now displayed.
Additional work is required to ensure that the retrieval status of the services is properly distributed among the individual servers where the services are active (eg, the mail server for the status of the mailing list services).
2. API documentation - search is not active, instead of Qt3 documentation TQt documentation is now published, instead of old KDE documentation, TDE documentation is published (tdelibs and tdebase).
Further changes will be needed here. However, there will be a need to discuss how to maintain and generate documentation.
3. Supported RFEs - the page is now static and since we do not currently have a way to accept monetary donations, this page is suitable for removal and replacement in a new way sometime in the future.
4. List of active mirrors - now provides a better overview of the status of mirrors.
-- What needs to be done --
1. Webhook for automatic update when pushing commits to git.
2. New bot for recording history / interaction on IRC and Jabber rooms. Currently, IRC history is being retrieved from the old Tim's server.
3. There could be some small changes in style - for example, for better display on mobile devices.
4. The menu could be revised - there some links are almost duplicated - Documentation × API Docs, some fully duplicated Home/Contact × Support, Bugs × Support/Bugs, Wiki × Support/Wiki.
5. Some changes in the content.
-- More ideas and suggestions?
Does everything work fine with the web server? Do you have any other ideas and suggestions?
Cheers
On Tue, 15 Sep 2020 17:39:10 +0200 Slávek Banko via tde-users ml-migration-agent@trinitydesktop.org wrote:
- There could be some small changes in style - for example, for better
display on mobile devices.
- The menu could be revised - there some links are almost duplicated -
Documentation × API Docs, some fully duplicated Home/Contact × Support, Bugs × Support/Bugs, Wiki × Support/Wiki.
- Some changes in the content.
-- More ideas and suggestions?
Does everything work fine with the web server? Do you have any other ideas and suggestions?
Not suggestions, exactly, but a few notes on the site:
I designed the site in 2014. The style was rather retro even then. Most of it is hand-coded PHP+CSS. There is no content management system driving it, but since it isn't usually touched by non-programmers, this hasn't been an issue as far as I know.
Mobile browsing wasn't as ubiquitous in 2014 as it has since become. I still don't own a smartphone. Based on what I know of how the interfaces work, I would guess that the main usability problem with the current design is the lack of enough padding around the nav links for them to work well with a touch interface. This was discussed a bit at the time, but everyone agreed that we were targetting the website at desktops. Alas, this is no longer a safe assumption.
The best way of dealing with the menu crowding is probably to add some kind of slide-out functionality for Javascript-equipped browsers. Or we could take the opportunity to redesign from scratch, but if we're going to do that, I'd like to know before I get too much deeper into the guts of MediaWiki's revised skinning system.
The nav menu redundancies are due to the headers being links—for the sake of uniformity, they all had to point somewhere, even when the destination was a duplicate of another link. The ideal way to remove the redundancies would be to de-link all of the headers, but that means adding some small links. Or we could just remove the redundant "Bugs" and "Wiki" header links and leave the rest.
The one actual *suggestion* I'd like to make is that we expand the "CLAs" nav link into something like "License Agreements", because I had to blink at it for several moments before I was able to figure out what it was (especially since the top search result is "Conjugated Linoleic Acids" . . .)
E. Liddell
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Dne út 15. září 2020 E. Liddell via tde-users napsal(a):
On Tue, 15 Sep 2020 17:39:10 +0200
Slávek Banko via tde-users ml-migration-agent@trinitydesktop.org wrote:
- There could be some small changes in style - for example, for
better display on mobile devices.
- The menu could be revised - there some links are almost duplicated
- Documentation × API Docs, some fully duplicated Home/Contact ×
Support, Bugs × Support/Bugs, Wiki × Support/Wiki.
- Some changes in the content.
-- More ideas and suggestions?
Does everything work fine with the web server? Do you have any other ideas and suggestions?
Not suggestions, exactly, but a few notes on the site:
I designed the site in 2014. The style was rather retro even then. Most of it is hand-coded PHP+CSS. There is no content management system driving it, but since it isn't usually touched by non-programmers, this hasn't been an issue as far as I know.
Mobile browsing wasn't as ubiquitous in 2014 as it has since become. I still don't own a smartphone. Based on what I know of how the interfaces work, I would guess that the main usability problem with the current design is the lack of enough padding around the nav links for them to work well with a touch interface. This was discussed a bit at the time, but everyone agreed that we were targetting the website at desktops. Alas, this is no longer a safe assumption.
For me, I don't see a problem in the size of the space around the links, but in the fact that mobile devices are portrait by default, which means that there is little room for content next to the menu, which takes up a fixed space on the left.
For example, in the current basic wiki style, it's nice that when viewed on a mobile => on a narrow screen, the menu is at the bottom instead of on the left. Something like that would be enough for me. Maybe there will be some more ideas.
The best way of dealing with the menu crowding is probably to add some kind of slide-out functionality for Javascript-equipped browsers. Or we could take the opportunity to redesign from scratch, but if we're going to do that, I'd like to know before I get too much deeper into the guts of MediaWiki's revised skinning system.
The current style seems good to me - some parts of the user interface are in the same style - for example, the front page in Konqeuror.
The nav menu redundancies are due to the headers being links—for the sake of uniformity, they all had to point somewhere, even when the destination was a duplicate of another link. The ideal way to remove the redundancies would be to de-link all of the headers, but that means adding some small links. Or we could just remove the redundant "Bugs" and "Wiki" header links and leave the rest.
Removing the separate Bugs and Wiki entries from menu seems good to me.
The one actual *suggestion* I'd like to make is that we expand the "CLAs" nav link into something like "License Agreements", because I had to blink at it for several moments before I was able to figure out what it was (especially since the top search result is "Conjugated Linoleic Acids" . . .)
CLA will be a completely separate chapter for discussion - see Project status report - tasks. Maybe there could then be a Contributing item instead of CLAs, where there could be instructions on how to contribute code (TGW), how to contribute translations (TWTW) and so on. The license agreement could then be one of the related pieces of information.
E. Liddell
Thank you!
Cheers
I designed the site in 2014. The style was rather retro even then. Most of it is hand-coded PHP+CSS. There is no content management system driving it, but since it isn't usually touched by non-programmers, this hasn't been an issue as far as I know.
Mobile browsing wasn't as ubiquitous in 2014 as it has since become. I still don't own a smartphone. Based on what I know of how the interfaces work, I would guess that the main usability problem with the current design is the lack of enough padding around the nav links for them to work well with a touch interface. This was discussed a bit at the time, but everyone agreed that we were targetting the website at desktops. Alas, this is no longer a safe assumption.
For me, I don't see a problem in the size of the space around the links, but in the fact that mobile devices are portrait by default, which means that there is little room for content next to the menu, which takes up a fixed space on the left.
For example, in the current basic wiki style, it's nice that when viewed on a mobile => on a narrow screen, the menu is at the bottom instead of on the left. Something like that would be enough for me. Maybe there will be some more ideas.
The best way of dealing with the menu crowding is probably to add
some kind of slide-out functionality for Javascript-equipped browsers. Or we could take the opportunity to redesign from scratch, but if we're going to do that, I'd like to know before I get too much deeper into the guts of MediaWiki's revised skinning system.
The current style seems good to me - some parts of the user interface are in the same style - for example, the front page in Konqeuror.
I think having a more smartphone/tablet friendly website would be good, as E. said lot have changed since 2014. Maybe a different position for the menu is enough, maybe we need some bigger changes like a popup menu on smartphone linked to a button, which is a fairly common user experience on mobile.
The nav menu redundancies are due to the headers being links—for the sake of uniformity, they all had to point somewhere, even when the destination was a duplicate of another link. The ideal way to remove the redundancies would be to de-link all of the headers, but that means adding some small links. Or we could just remove the redundant "Bugs" and "Wiki" header links and leave the rest.
Removing the separate Bugs and Wiki entries from menu seems good to me.
I am not sure I understand the exact technical issues with links here, but double links are a bit of a waste. I found the main link like "wiki" "bugs" better than the small links under Support and I would support removing some of the links under Support.
The one actual *suggestion* I'd like to make is that we expand the "CLAs" nav link into something like "License Agreements", because I had to blink at it for several moments before I was able to figure out what it was (especially since the top search result is "Conjugated Linoleic Acids" . . .)
CLA will be a completely separate chapter for discussion - see Project status report - tasks. Maybe there could then be a Contributing item instead of CLAs, where there could be instructions on how to contribute code (TGW), how to contribute translations (TWTW) and so on. The license agreement could then be one of the related pieces of information.
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.
Overall I think a bit of restyling would be good. For example change the main screenshot, maybe add a second one too.
What do you think?
Cheers Michele
On Wed, 16 Sep 2020 23:24:49 +0900 Michele Calgaro via tde-users ml-migration-agent@trinitydesktop.org wrote:
The best way of dealing with the menu crowding is probably to add
some kind of slide-out functionality for Javascript-equipped browsers. Or we could take the opportunity to redesign from scratch, but if we're going to do that, I'd like to know before I get too much deeper into the guts of MediaWiki's revised skinning system.
The current style seems good to me - some parts of the user interface are in the same style - for example, the front page in Konqeuror.
I think having a more smartphone/tablet friendly website would be good, as E. said lot have changed since 2014. Maybe a different position for the menu is enough, maybe we need some bigger changes like a popup menu on smartphone linked to a button, which is a fairly common user experience on mobile.
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).
The nav menu redundancies are due to the headers being links—for the sake of uniformity, they all had to point somewhere, even when the destination was a duplicate of another link. The ideal way to remove the redundancies would be to de-link all of the headers, but that means adding some small links. Or we could just remove the redundant "Bugs" and "Wiki" header links and leave the rest.
Removing the separate Bugs and Wiki entries from menu seems good to me.
I am not sure I understand the exact technical issues with links here, but double links are a bit of a waste. I found the main link like "wiki" "bugs" better than the small links under Support and I would support removing some of the links under Support.
The problem with the big links is that they don't really work with the rest of the nav menu (and never have). I think they were inherited from Tim's original website design, and I didn't feel strongly enough about them at the time to protest their presence.
A quick, unscientific survey of the websites of other Linux desktop environments shows that they either have two unrelated sets of nav links (not the best idea, IMHO) or place their wikis and bug trackers at the level of our "small links". That means that most people should have no trouble locating them there.
The one actual *suggestion* I'd like to make is that we expand the "CLAs" nav link into something like "License Agreements", because I had to blink at it for several moments before I was able to figure out what it was (especially since the top search result is "Conjugated Linoleic Acids" . . .)
CLA will be a completely separate chapter for discussion - see Project status report - tasks. Maybe there could then be a Contributing item instead of CLAs, where there could be instructions on how to contribute code (TGW), how to contribute translations (TWTW) and so on. The license agreement could then be one of the related pieces of information.
I think other sections could be reworked too.
- GIT, commit history, Packaging GIT, secure GIT --> just need one entry to point to TGW.
- uLAB GIT: should not be displayed, since uLAB is an unrelated project from TDE
- nightly builds: either remove or point to PSB/PTB archives
- Related projects: they are part of the TDE repos, no need for a separate page on main menu
- RFEs: just remove that
- Donations (once we clarify the legal status of TDE): make link stand alone and more visible
- 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:
HOME: News, Features, About, Screenshots, Donations
GET TRINITY: Packages, LiveCDs
DOCUMENTATION: FAQ, Wiki, Installation, Applications
SUPPORT: Bugs, Mailing Lists, Service Alerts, Contact
DEVELOPMENT: GIT, API Docs, Library Projects, Get Involved
This structure has no "floating" headers without children, and the headers do not need to be links.
Overall I think a bit of restyling would be good. For example change the main screenshot, maybe add a second one too.
What do you think?
That's a relatively small change.
E. Liddell
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
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@trinitydesktop.org
wrote:
The best way of dealing with the menu crowding is probably to add
some kind of slide-out functionality for Javascript-equipped browsers. Or we could take the opportunity to redesign from scratch, but if we're going to do that, I'd like to know before I get too much deeper into the guts of MediaWiki's revised skinning system.
The current style seems good to me - some parts of the user interface are in the same style - for example, the front page in Konqeuror.
I think having a more smartphone/tablet friendly website would be good, as E. said lot have changed since 2014. Maybe a different position for the menu is enough, maybe we need some bigger changes like a popup menu on smartphone linked to a button, which is a fairly common user experience on mobile.
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.
The nav menu redundancies are due to the headers being links—for the sake of uniformity, they all had to point somewhere, even when the destination was a duplicate of another link. The ideal way to remove the redundancies would be to de-link all of the headers, but that means adding some small links. Or we could just remove the redundant "Bugs" and "Wiki" header links and leave the rest.
Removing the separate Bugs and Wiki entries from menu seems good to me.
I am not sure I understand the exact technical issues with links here, but double links are a bit of a waste. I found the main link like "wiki" "bugs" better than the small links under Support and I would support removing some of the links under Support.
The problem with the big links is that they don't really work with the rest of the nav menu (and never have). I think they were inherited from Tim's original website design, and I didn't feel strongly enough about them at the time to protest their presence.
A quick, unscientific survey of the websites of other Linux desktop environments shows that they either have two unrelated sets of nav links (not the best idea, IMHO) or place their wikis and bug trackers at the level of our "small links". That means that most people should have no trouble locating them there.
Yes, because both levels of our menu are still displayed, there should be no problem for users to find Bugs and Wiki on the second level. These links do not seem to be so special that they are like first-level items that have no children.
The one actual *suggestion* I'd like to make is that we expand the "CLAs" nav link into something like "License Agreements", because I had to blink at it for several moments before I was able to figure out what it was (especially since the top search result is "Conjugated Linoleic Acids" . . .)
CLA will be a completely separate chapter for discussion - see Project status report - tasks. Maybe there could then be a Contributing item instead of CLAs, where there could be instructions on how to contribute code (TGW), how to contribute translations (TWTW) and so on. The license agreement could then be one of the related pieces of information.
I think other sections could be reworked too.
- 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.
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.
Overall I think a bit of restyling would be good. For example change the main screenshot, maybe add a second one too.
What do you think?
That's a relatively small change.
E. Liddell
Cheers
On Thu, 17 Sep 2020 04:43:15 +0200 Slávek Banko via tde-users ml-migration-agent@trinitydesktop.org 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@trinitydesktop.org
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.
- 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.
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).
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.
"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
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
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.
All you have said here sounds good to me too.
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.
Fully agree with E. here. We could in fact have a single link to a "Development" page on the wiki, where we can more freely add contents and links to other sections. The "Development" pages in the current wiki also need a rework, IMO.
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
I really question the need to have a "Library project" page. All the libraries we used are in the source code already, what's so special about some of them to create a dedicated page?
Cheers Michele
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@trinitydesktop.org 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@trinitydesktop.org
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.
- 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
On Thursday 17 September 2020 09:09:37 am Slávek Banko via tde-users wrote:
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.
As a user all I ever use is Commit history. And I hate projects that say 'look at git.'
Impersonating an ‘average user,’ “What the fuck is git? Screw this I’ll find something else!”
And while I’m on the topic of git, please, never, ever, put user documentation in git. Utter fail. Users are the best source of keeping user docs up to date, force them to use git, or similar, and they take a walk from the entire project (unless they are forced to use it).
If someone has a friend who does UIX, please have them look at the final change proposal.
Best All, Michael
Apologies for not following the entire discussion, throwing my 2 cents in for what I skimmed, best, Michael
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).
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.
I’d also make the "Development" link go to a summary page of ALL the development type information. Do make sure to put a link-able TOC at the top of that page! Why? We users do click on these, but with just a link we have no idea what a ‘Gitea’ is and hence we’re not real likely to ever even try to help with it.
This structure has no "floating" headers without children, and the headers do not need to be links.
Disagree. Headers, and this is arguable in UIX land, should link to a summary page for each of the items in the menu.
"Get Trinity" has the same destination as "Releases".
"Get Trinity" is better UIX, drop "Releases" if you have too.
"Support" has the same destination as "Contact".
You want both links and while going to the same place is fine, "Support" really should go to a summary page that lists the email lists, where to file code bug reports, where to submit website bug reports, ...
Other
If it’s not already there, a TLM of “How you can help” linking to a summary page of all the ways anyone (dev or user) can help TDE is really desirable. There (should!) be too many items under this, so do not have any sub-menus.
Hmm, this like the "Development" link could go the a wiki page, so that it can be maintained easier. (Plus the wiki already has link-able TOCs)
Dne čt 17. září 2020 Michael via tde-users napsal(a):
Apologies for not following the entire discussion, throwing my 2 cents in for what I skimmed, best, Michael
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).
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.
I’d also make the "Development" link go to a summary page of ALL the development type information. Do make sure to put a link-able TOC at the top of that page! Why? We users do click on these, but with just a link we have no idea what a ‘Gitea’ is and hence we’re not real likely to ever even try to help with it.
This structure has no "floating" headers without children, and the headers do not need to be links.
Disagree. Headers, and this is arguable in UIX land, should link to a summary page for each of the items in the menu.
Great, Michael, thank you for your feedback. I also thought that there would be a good idea that the first level of the menu would continue to be as links, for exactly the same purpose as you state.
"Get Trinity" has the same destination as "Releases".
"Get Trinity" is better UIX, drop "Releases" if you have too.
"Support" has the same destination as "Contact".
You want both links and while going to the same place is fine, "Support" really should go to a summary page that lists the email lists, where to file code bug reports, where to submit website bug reports, ...
Other
If it’s not already there, a TLM of “How you can help” linking to a summary page of all the ways anyone (dev or user) can help TDE is really desirable. There (should!) be too many items under this, so do not have any sub-menus.
Hmm, this like the "Development" link could go the a wiki page, so that it can be maintained easier. (Plus the wiki already has link-able TOCs)
It is quite clear that the Get Involved link does not belong to Development! Get Involved should cover all topics - user and developer. It probably belongs in the Home section. Again - thank you Michael for your feedback.
Cheers
On Thu, 17 Sep 2020 16:54:53 +0200 Slávek Banko via tde-users ml-migration-agent@trinitydesktop.org wrote:
Dne čt 17. září 2020 Michael via tde-users napsal(a):
"Get Trinity" has the same destination as "Releases".
"Get Trinity" is better UIX, drop "Releases" if you have too.
"Support" has the same destination as "Contact".
You want both links and while going to the same place is fine, "Support" really should go to a summary page that lists the email lists, where to file code bug reports, where to submit website bug reports, ...
Other
If it’s not already there, a TLM of “How you can help” linking to a summary page of all the ways anyone (dev or user) can help TDE is really desirable. There (should!) be too many items under this, so do not have any sub-menus.
Hmm, this like the "Development" link could go the a wiki page, so that it can be maintained easier. (Plus the wiki already has link-able TOCs)
It is quite clear that the Get Involved link does not belong to Development! Get Involved should cover all topics - user and developer. It probably belongs in the Home section. Again - thank you Michael for your feedback.
Another possibility would be to divide the development links according to types of potential volunteers and give them each an overview page with resources and how-tos, for instance:
DEVELOPMENT: Coders, Packagers, Translators, Testers, [...]
Although I admit I can't recall seeing that anywhere else. That may mean that it's a bad idea.
E. Liddell
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
E. Liddell wrote:
Another possibility would be to divide the development links according to types of potential volunteers and give them each an overview page with resources and how-tos, for instance:
DEVELOPMENT: Coders, Packagers, Translators, Testers, [...]
Although I admit I can't recall seeing that anywhere else. That may mean that it's a bad idea.
I would suggest keep it simple and less is more, because everything needs to be maintained. I always try to reduce to the minimum necessary to communicate something.
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Thursday 17 September 2020 14:24:50 deloptes via tde-users wrote:
E. Liddell wrote:
Another possibility would be to divide the development links according to types of potential volunteers and give them each an overview page with resources and how-tos, for instance:
DEVELOPMENT: Coders, Packagers, Translators, Testers, [...]
Although I admit I can't recall seeing that anywhere else. That may mean that it's a bad idea.
I would suggest keep it simple and less is more, because everything needs to be maintained. I always try to reduce to the minimum necessary to communicate something.
As a user, I found the byzantine complexity of the site pretty frustrating in the beginning -- although now I am kind of used to it. But I recall finding a lot of seeming duplication; for example, when I looked for installation discs with TDE. Somehow I would end up finding different sets of pages, apparently because legacy items were allowed to remain, then new pages created for newer distros, and so on.
It doesn't really apply to my own situation now, as I decided to roll my own. However, it occurs to me that we might want to preserve an archived version of the old pages, at least for a while, until the new pages supersede them completely.
Bill
On Thursday 17 September 2020 05:14:23 pm William Morder via tde-users wrote:
However, it occurs to me that we might want to preserve an archived version of the old pages, at least for a while, until the new pages supersede them completely.
Usually you just foward the old URL to the new URL. Either through .htaccess, which Google likes best:
<IfModule mod_rewrite.c> RewriteEngine on RewriteBase / RewriteRule ^my-old-page.html$ new-page.html [R=301,L] </IfModule>
Or use an HTML header entry on the old page:
<HTML> <HEAD> <META HTTP-EQUIV="refresh" CONTENT="1; url=http://example.com/new-page.html"> <SCRIPT TYPE="text/javascript"> window.location.href = "http://example.com/new-page.html" </SCRIPT> </HEAD> <BODY> {snip}
Contact me directly whoever's doing the changes if you need/want help.
Best, Michael
On Thursday 17 of September 2020 23:12:21 E. Liddell via tde-users wrote:
On Thu, 17 Sep 2020 16:54:53 +0200
Slávek Banko via tde-users ml-migration-agent@trinitydesktop.org wrote:
Dne čt 17. září 2020 Michael via tde-users napsal(a):
"Get Trinity" has the same destination as "Releases".
"Get Trinity" is better UIX, drop "Releases" if you have too.
"Support" has the same destination as "Contact".
You want both links and while going to the same place is fine, "Support" really should go to a summary page that lists the email lists, where to file code bug reports, where to submit website bug reports, ...
Other
If it’s not already there, a TLM of “How you can help” linking to a summary page of all the ways anyone (dev or user) can help TDE is really desirable. There (should!) be too many items under this, so do not have any sub-menus.
Hmm, this like the "Development" link could go the a wiki page, so that it can be maintained easier. (Plus the wiki already has link-able TOCs)
It is quite clear that the Get Involved link does not belong to Development! Get Involved should cover all topics - user and developer. It probably belongs in the Home section. Again - thank you Michael for your feedback.
Another possibility would be to divide the development links according to types of potential volunteers and give them each an overview page with resources and how-tos, for instance:
DEVELOPMENT: Coders, Packagers, Translators, Testers, [...]
Although I admit I can't recall seeing that anywhere else. That may mean that it's a bad idea.
E. Liddell
Links divided by area of interest may make sense in the documentation (for example on a wiki), but they do not seem useful for menu on the main web. It seems to me a good option as mentioned before, just change the location of Get Involved to the Home menu:
HOME: News, About, Features, Screenshots, Get Involved, Donations
DOCUMENTATION: Wiki, Installation, Applications, FAQ
DEVELOPMENT: GIT, Translations, Commit History, Resources
What is your opinion?
Links divided by area of interest may make sense in the documentation (for example on a wiki), but they do not seem useful for menu on the main web. It seems to me a good option as mentioned before, just change the location of Get Involved to the Home menu:
Agree with Slavek here, makes perfect sense. Cheers Michele
Michele Calgaro via tde-users wrote:
Agree with Slavek here, makes perfect sense.
yes indeed
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Fri, 18 Sep 2020 03:05:42 +0200 Slávek Banko via tde-users ml-migration-agent@trinitydesktop.org wrote:
It seems to me a good option as mentioned before, just change the location of Get Involved to the Home menu:
HOME: News, About, Features, Screenshots, Get Involved, Donations
GET TRINITY: Packages, LiveCDs
DOCUMENTATION: Wiki, Installation, Applications, FAQ
SUPPORT: Bugs, Mailing Lists, Service Alerts, Contact
DEVELOPMENT: GIT, Translations, Commit History, Resources
So is this the final menu layout that we want?
E. Liddell
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Saturday 19 of September 2020 20:17:44 E. Liddell via tde-users wrote:
On Fri, 18 Sep 2020 03:05:42 +0200
Slávek Banko via tde-users ml-migration-agent@trinitydesktop.org wrote:
It seems to me a good option as mentioned before, just change the location of Get Involved to the Home menu:
HOME: News, About, Features, Screenshots, Get Involved, Donations
GET TRINITY: Packages, LiveCDs
DOCUMENTATION: Wiki, Installation, Applications, FAQ
SUPPORT: Bugs, Mailing Lists, Service Alerts, Contact
DEVELOPMENT: GIT, Translations, Commit History, Resources
So is this the final menu layout that we want?
E. Liddell
E., thank you for adding the items I forgot to mention. For me, the proposal to change the structure of the menu seems to be ready and good.
Anyone else have any suggestions or objections?
Thank you
On 2020/09/21 12:07 AM, Sl�vek Banko via tde-users wrote:
SUPPORT: Bugs, Mailing Lists, Service Alerts, Contact
We have both bugszilla and TGW issues to report bugs, with the second being preferred now. We either point to a wiki page and then split to the two destinations or add a second link there.
Cheers Michele
On Sunday 20 of September 2020 17:46:14 Michele Calgaro via tde-users wrote:
On 2020/09/21 12:07 AM, Sl�vek Banko via tde-users wrote:
SUPPORT: Bugs, Mailing Lists, Service Alerts, Contact
We have both bugszilla and TGW issues to report bugs, with the second being preferred now. We either point to a wiki page and then split to the two destinations or add a second link there.
Cheers Michele ____________________________________________________
We need to discuss the future of TDE Bugzilla ... see task 5 in Project status report - tasks.
For now, we probably agree on the proposal to change the menu layout here and we can start working in this direction. In the meantime, I'll open threads for the next of the tasks on the list to move quickly to task 5 and discuss Bugzilla.
Cheers
On Sun, 20 Sep 2020 17:07:28 +0200 Slávek Banko via tde-users ml-migration-agent@trinitydesktop.org wrote:
On Saturday 19 of September 2020 20:17:44 E. Liddell via tde-users wrote:
On Fri, 18 Sep 2020 03:05:42 +0200
Slávek Banko via tde-users ml-migration-agent@trinitydesktop.org wrote:
It seems to me a good option as mentioned before, just change the location of Get Involved to the Home menu:
HOME: News, About, Features, Screenshots, Get Involved, Donations
GET TRINITY: Packages, LiveCDs
DOCUMENTATION: Wiki, Installation, Applications, FAQ
SUPPORT: Bugs, Mailing Lists, Service Alerts, Contact
DEVELOPMENT: GIT, Translations, Commit History, Resources
So is this the final menu layout that we want?
E. Liddell
E., thank you for adding the items I forgot to mention. For me, the proposal to change the structure of the menu seems to be ready and good.
I've uploaded a preview of what the menu looks like with the changes to https://i.postimg.cc/R0mpJpSf/tdepage.png . (Ignore the old news item and screenshot, please—this is my private copy of the php code from several years ago, not the live site, and the menu is in a separate php file anyway.) This is not quite ready to deploy, since we have to decide what to do with some of the link targets first.
E. Liddell
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Saturday 26 of September 2020 23:20:49 E. Liddell via tde-users wrote:
On Sun, 20 Sep 2020 17:07:28 +0200
Slávek Banko via tde-users ml-migration-agent@trinitydesktop.org wrote:
On Saturday 19 of September 2020 20:17:44 E. Liddell via tde-users
wrote:
On Fri, 18 Sep 2020 03:05:42 +0200
Slávek Banko via tde-users ml-migration-agent@trinitydesktop.org
wrote:
It seems to me a good option as mentioned before, just change the location of Get Involved to the Home menu:
HOME: News, About, Features, Screenshots, Get Involved, Donations
GET TRINITY: Packages, LiveCDs
DOCUMENTATION: Wiki, Installation, Applications, FAQ
SUPPORT: Bugs, Mailing Lists, Service Alerts, Contact
DEVELOPMENT: GIT, Translations, Commit History, Resources
So is this the final menu layout that we want?
E. Liddell
E., thank you for adding the items I forgot to mention. For me, the proposal to change the structure of the menu seems to be ready and good.
I've uploaded a preview of what the menu looks like with the changes to https://i.postimg.cc/R0mpJpSf/tdepage.png . (Ignore the old news item and screenshot, please—this is my private copy of the php code from several years ago, not the live site, and the menu is in a separate php file anyway.) This is not quite ready to deploy, since we have to decide what to do with some of the link targets first.
E. Liddell
Great - it looks good!
To get the current code, you can clone the repository https://mirror.git.trinitydesktop.org/gitea/TDE/tdemainweb-core
I assume we can remove the vps branch, which is now in line with the master. And instead, we could create a branch called test, for example, that could be published to a test site. The changes that will be made could be gradually pushed into this branch. What do you think?
Cheers
I've uploaded a preview of what the menu looks like with the changes to https://i.postimg.cc/R0mpJpSf/tdepage.png . (Ignore the old news item and screenshot, please—this is my private copy of the php code from several years ago, not the live site, and the menu is in a separate php file anyway.) This is not quite ready to deploy, since we have to decide what to do with some of the link targets first.
E. Liddell
Great - it looks good!
To get the current code, you can clone the repository https://mirror.git.trinitydesktop.org/gitea/TDE/tdemainweb-core
I assume we can remove the vps branch, which is now in line with the master. And instead, we could create a branch called test, for example, that could be published to a test site. The changes that will be made could be gradually pushed into this branch. What do you think?
Looks great, thanks E.!
@Slavek: some months ago we already discussed about having a 'test' branch for previewing/testing changes on the website, so we should definitely do that :-)
Cheers Michele
On Thu, 17 Sep 2020, E. Liddell wrote:
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.
360px shows up a lot -- with varying heights. See: https://gs.statcounter.com/screen-resolution-stats
Clicking on [All Platforms] [Desktop] [Tablet] and [Mobile] yields some "interesting" numbers. A suggestion would be to collect those sort of figures for the Trinity entry (home) page.
The Palemoon browser will let you shrink the page width down to something like 80px -- useful to view and critique your "Mobile Friendly" design(s).
May the mask be with you, Jonesy
E. Liddell wrote:
-"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.
I see there is only 5 of us listed under "team". The team grew luckily in the past few years. Perhaps when you are reworking it link to Gitea TEAM https://mirror.git.trinitydesktop.org/gitea/org/TDE/members
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Saturday 19 of September 2020 20:30:38 deloptes via tde-users wrote:
E. Liddell wrote:
-"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.
I see there is only 5 of us listed under "team". The team grew luckily in the past few years. Perhaps when you are reworking it link to Gitea TEAM https://mirror.git.trinitydesktop.org/gitea/org/TDE/members
Hi Emanoil,
it is a good reminder that the team information needs to be updated. However, it will not be enough to make a reference to TGW. Not only is there no place to indicate what focus a member has, but access to team members requires the user to be logged in.
Cheers
On Saturday 19 September 2020 06:02:27 pm Slávek Banko via tde-users wrote:
On Saturday 19 of September 2020 20:30:38 deloptes via tde-users wrote:
E. Liddell wrote:
-"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.
I see there is only 5 of us listed under "team". The team grew luckily in the past few years. Perhaps when you are reworking it link to Gitea TEAM https://mirror.git.trinitydesktop.org/gitea/org/TDE/members
Hi Emanoil,
it is a good reminder that the team information needs to be updated. However, it will not be enough to make a reference to TGW. Not only is there no place to indicate what focus a member has, but access to team members requires the user to be logged in.
Can we open a discussion about moving all changeable information to the Wiki and only having purely static information on the website? We seem to be hitting this type of issue a lot, where the website would need to be updated fairly frequently...
It’s only tangentially related to the website menu layout, but should save E. (or whoever is doing maintenance) time in the long run.
Just a though, Michael
Michael via tde-users wrote:
Can we open a discussion about moving all changeable information to the Wiki and only having purely static information on the website? We seem to be hitting this type of issue a lot, where the website would need to be updated fairly frequently...
It’s only tangentially related to the website menu layout, but should save E. (or whoever is doing maintenance) time in the long run.
Yes indeed. I was/am think of minimizing the maintenance effort, but Slavek is right - you need a log on TGW to see the details. What was the standpoint on dynamically updating content? If TGW has some kind of API for example it could be used to retrieve some sort of information from there.
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Hi Emanoil,
it is a good reminder that the team information needs to be updated. However, it will not be enough to make a reference to TGW. Not only is there no place to indicate what focus a member has, but access to team members requires the user to be logged in.
Yes, team information needs to be updated, indeed. Probably good to have a page on wiki, since the team is constantly evolving. We could have Core, Contributors, Translators groups perhaps. Also we could let people place a picture of themselves near the name, if they wish. What do you think of that?
On 2020/09/20 12:57 PM, Michael via tde-users wrote:
Can we open a discussion about moving all changeable information to the Wiki and only having purely static information on the website? We seem to be hitting this type of issue a lot, where the website would need to be updated fairly frequently...
+1 for this, makes perfect sense to me.
Cheers Michele
On Thu, 17 Sep 2020 01:17:42 -0500 J Leslie Turriff via tde-users ml-migration-agent@trinitydesktop.org wrote:
On 2020-09-16 09:24:49 you wrote: :
- CLAs: as mentioned by Slavek, this will be a separate discussion
What is a CLA?
Contributor License Agreement. Basically, it's something that programmers working on a project are asked to agree to in order to avoid certain weird copyright situations cropping up around their code.
E. Liddell
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Hi all,
although it may appear that after discussions about the migration of services, nothing happens, we'll gradually move forward. It is true that we are busy, so things move slowly, but it's not frozen. Currently there was a move forward about IRC. See small summary below.
On Tuesday 15 of September 2020 17:39:10 Slávek Banko via tde-users wrote:
-- What needs to be done --
Webhook for automatic update when pushing commits to git.
New bot for recording history / interaction on IRC and Jabber rooms.
Currently, IRC history is being retrieved from the old Tim's server.
Here were several events. From the beginning of May, the original tbottu was offline, so history was not recorded on old Tim's server. May 20, IRC channel was moved from Freenode to Libera.Chat. The creation of a new bot therefore gained a higher priority.
Now the new bot provides all the necessary things and is already active on all channels. In addition to providing information about bugs from TDE Bugzilla, it is now mainly integrated to provide information from TGW. History records are again available on the web.
- There could be some small changes in style - for example, for better
display on mobile devices.
Thanks to the work of E.Liddell, the updated web style is published from April 12th.
- The menu could be revised - there some links are almost duplicated -
Documentation × API Docs, some fully duplicated Home/Contact × Support, Bugs × Support/Bugs, Wiki × Support/Wiki.
Completed along with web style update.
- Some changes in the content.
Many pages have been updated. Some still need to edit.
Cheers
-
deloptes -
E. Liddell
-
J Leslie Turriff -
Jonesy W3DHJ via trinity-users
-
Michael -
Michele Calgaro -
Slávek Banko -
William Morder