Details

    • Type: Task
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Component/s: download.moodle.org
    • Labels:
      None

      Description

      From Martin's notes:

      Re-make Download site as a simple web page and update it with new theme.

      http://download.moodle.org/

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            poltawski Dan Poltawski added a comment -

            Hi Eloy,

            We discussed your thoughts for the download site some time ago, but i've completely forgotten it.

            I think you want the CI server to automate a lot of the building etc, but perhaps in the meantime I could create the front page for the download site with the appropriate hooks for automation to come later?

            Show
            poltawski Dan Poltawski added a comment - Hi Eloy, We discussed your thoughts for the download site some time ago, but i've completely forgotten it. I think you want the CI server to automate a lot of the building etc, but perhaps in the meantime I could create the front page for the download site with the appropriate hooks for automation to come later?
            Hide
            stronk7 Eloy Lafuente (stronk7) added a comment -

            Note that MDLSITE-2045 has been created about the improved (git-based) packaging process happening @ download.moodle.org. Note it's 100% done by download.moodle.org but it should be easier to move the "trigger" to Jenkins once everything is working ok (MDLSITE-2047 for more details).

            This is only about packaging, not about releasing (aka, branching, editing version.php...). For that mdlrelease continues being our guide.

            Show
            stronk7 Eloy Lafuente (stronk7) added a comment - Note that MDLSITE-2045 has been created about the improved (git-based) packaging process happening @ download.moodle.org. Note it's 100% done by download.moodle.org but it should be easier to move the "trigger" to Jenkins once everything is working ok ( MDLSITE-2047 for more details). This is only about packaging, not about releasing (aka, branching, editing version.php...). For that mdlrelease continues being our guide.
            Hide
            dougiamas Martin Dougiamas added a comment -

            Assigning this to Barbara to come up with a better design in HTML/CSS for this page.

            It should be a simple matter then to wire that to the scripts for the data.

            Show
            dougiamas Martin Dougiamas added a comment - Assigning this to Barbara to come up with a better design in HTML/CSS for this page. It should be a simple matter then to wire that to the scripts for the data.
            Hide
            tsala Helen Foster added a comment -

            Increasing priority as this issue needs to be completed at the same time as moodle.org. The downloads site will no longer appear to be part of moodle.org; instead it will be a site with top menu items:

            Packages | Plugins | Language packs

            We will also need to figure out how to separate plugins navigation from moodle.org navigation.

            Show
            tsala Helen Foster added a comment - Increasing priority as this issue needs to be completed at the same time as moodle.org. The downloads site will no longer appear to be part of moodle.org; instead it will be a site with top menu items: Packages | Plugins | Language packs We will also need to figure out how to separate plugins navigation from moodle.org navigation.
            Hide
            poltawski Dan Poltawski added a comment -

            I'm taking this task as most of the work has already been done in the theme, its just a case of me applying the current pages to the theme.

            Show
            poltawski Dan Poltawski added a comment - I'm taking this task as most of the work has already been done in the theme, its just a case of me applying the current pages to the theme.
            Hide
            poltawski Dan Poltawski added a comment -

            Just noting the progress I've been making on this:

            1. I've made the downloads theme front page use lang strings (just working out MDLSITE-3187)
            2. I've created a class in local_downloadmoodleorg which the theme will use if the plugin is installed to populate the front-page download buttons/lang packs links etc.

            The class is using eloys existing infrastructure which is auto-generated by the packager so that the right downloads will be promoted on the front page as soon as release happens as you would expect.

            Having just remembered about the windows download page etc I think I probably need to do a bit more work tidying up this code and adding tests to support the numerous different cases as there is a fair amount of important logic contained within it.

            Show
            poltawski Dan Poltawski added a comment - Just noting the progress I've been making on this: I've made the downloads theme front page use lang strings (just working out MDLSITE-3187 ) I've created a class in local_downloadmoodleorg which the theme will use if the plugin is installed to populate the front-page download buttons/lang packs links etc. The class is using eloys existing infrastructure which is auto-generated by the packager so that the right downloads will be promoted on the front page as soon as release happens as you would expect. Having just remembered about the windows download page etc I think I probably need to do a bit more work tidying up this code and adding tests to support the numerous different cases as there is a fair amount of important logic contained within it.
            Hide
            poltawski Dan Poltawski added a comment - - edited

            To Helen et al,

            I've read one of the other issues and it seems that we are decided on having the index page without any downloads from there, is that correct?

            I've implemented that on:
            http://next.download.moodle.org

            Then the 'big links' on that page link to, say:
            http://next.download.moodle.org/builds/#v2.6.3

            And the mac builds link to:
            http://next.download.moodle.org/macosx/

            Is that how we want the pages to be organised, or do we want everything on one page?

            Show
            poltawski Dan Poltawski added a comment - - edited To Helen et al, I've read one of the other issues and it seems that we are decided on having the index page without any downloads from there, is that correct? I've implemented that on: http://next.download.moodle.org Then the 'big links' on that page link to, say: http://next.download.moodle.org/builds/#v2.6.3 And the mac builds link to: http://next.download.moodle.org/macosx/ Is that how we want the pages to be organised, or do we want everything on one page?
            Hide
            stronk7 Eloy Lafuente (stronk7) added a comment -

            Personal opinion:

            1) I don't oppose to just have the "main" downloads in the frontpage. But I'd say that "+" versions, when available, should be the preferred "mains". At least that has been the way always in the current page. In other words, bigger version wins always.

            2) I probably would expect some little text, color or hover explaining the differences between security only and supported. Or, alternatively would only put fully supported versions in the main page. (perhaps something to configure from config.php).

            3) I'd transform the 3 texts under the downloads (all builds, windows, macosx) into some buttons more prominent. Clearly separated from the "main" downloads (perhaps bottom-right...) but buttons too. I'd consider also to offer a "development" version button there, observing config.php.

            Note, when I say "config.php", it's a main file that roots what's available for download and which configuration is used to define every aspect of the current downloads page (Dan knows).

            Just my thoughts, other that that... yay... lovely page!

            Ciao

            Show
            stronk7 Eloy Lafuente (stronk7) added a comment - Personal opinion: 1) I don't oppose to just have the "main" downloads in the frontpage. But I'd say that "+" versions, when available, should be the preferred "mains". At least that has been the way always in the current page. In other words, bigger version wins always. 2) I probably would expect some little text, color or hover explaining the differences between security only and supported. Or, alternatively would only put fully supported versions in the main page. (perhaps something to configure from config.php). 3) I'd transform the 3 texts under the downloads (all builds, windows, macosx) into some buttons more prominent. Clearly separated from the "main" downloads (perhaps bottom-right...) but buttons too. I'd consider also to offer a "development" version button there, observing config.php. Note, when I say "config.php", it's a main file that roots what's available for download and which configuration is used to define every aspect of the current downloads page (Dan knows). Just my thoughts, other that that... yay... lovely page! Ciao
            Hide
            dougiamas Martin Dougiamas added a comment -

            1) Agreed.
            2) Yes, only put supported versions on the main links. The rest can be in "View all builds"
            3) Agreed about those links, but also the main download buttons might also be a little more prominent. Perhaps reduce the wordy text above them and put "Latest Moodle releases:"

            Getting close I think!

            Show
            dougiamas Martin Dougiamas added a comment - 1) Agreed. 2) Yes, only put supported versions on the main links. The rest can be in "View all builds" 3) Agreed about those links, but also the main download buttons might also be a little more prominent. Perhaps reduce the wordy text above them and put "Latest Moodle releases:" Getting close I think!
            Hide
            poltawski Dan Poltawski added a comment -

            1) That was just my own bias for non-weeklies, will switch
            2) Cool, prefer that too. And I remove those branches from the langpacks box too?
            3) I assume we want the main 'current' download' to also be a bigger 'lure you into clicking' button too, like http://www.drupal.org/download

            Are we happy with the general long table layout of the builds page like before? (Note we've not really done any styling/reorganisation other than putting it in them theme)

            Show
            poltawski Dan Poltawski added a comment - 1) That was just my own bias for non-weeklies, will switch 2) Cool, prefer that too. And I remove those branches from the langpacks box too? 3) I assume we want the main 'current' download' to also be a bigger 'lure you into clicking' button too, like http://www.drupal.org/download Are we happy with the general long table layout of the builds page like before? (Note we've not really done any styling/reorganisation other than putting it in them theme)
            Hide
            dougiamas Martin Dougiamas added a comment -

            The long layout page is not awesome but I don't have any clear better ideas at the moment. There's a lot of data but we do need it all IMO. I think we could just add some sort of "back to main downloads page" link at the top and bottom so that it looks less disconnected and it would be OK for now.

            And yes, very latest major release should be prominent of all.

            Show
            dougiamas Martin Dougiamas added a comment - The long layout page is not awesome but I don't have any clear better ideas at the moment. There's a lot of data but we do need it all IMO. I think we could just add some sort of "back to main downloads page" link at the top and bottom so that it looks less disconnected and it would be OK for now. And yes, very latest major release should be prominent of all.
            Hide
            tsala Helen Foster added a comment -

            Dan, thanks a lot for your work on this issue.

            You wrote "... it seems that we are decided on having the index page without any downloads from there, is that correct?" Reading the comments in MDLSITE-2814, I think I missed or misunderstood the decision to have latest supported versions as links to the builds page. I thought download links (.tgz and .zip) would be included on the downloads index page? Anchor links to a different page (download.moodle.org/builds/#v2.6.3 etc.) doesn't seem a nice solution to me at all. Perhaps I'm the only one to think like this though?

            Show
            tsala Helen Foster added a comment - Dan, thanks a lot for your work on this issue. You wrote "... it seems that we are decided on having the index page without any downloads from there, is that correct?" Reading the comments in MDLSITE-2814 , I think I missed or misunderstood the decision to have latest supported versions as links to the builds page. I thought download links (.tgz and .zip) would be included on the downloads index page? Anchor links to a different page (download.moodle.org/builds/#v2.6.3 etc.) doesn't seem a nice solution to me at all. Perhaps I'm the only one to think like this though?
            Hide
            dougiamas Martin Dougiamas added a comment -

            Moodle is Free software with an open-source GPL license.

            Latest recommended packages, built weekly:
            X X X

            Or use Git to make your upgrades easier in future:
            X

            Show
            dougiamas Martin Dougiamas added a comment - Moodle is Free software with an open-source GPL license. Latest recommended packages, built weekly: X X X Or use Git to make your upgrades easier in future: X
            Hide
            poltawski Dan Poltawski added a comment -

            Barbara and I had a bit of discussion today and I wanted to sort of frame the goals for the pages the way I think it should work (and hopefully you'll all agree )

            1. The 'landing page' is just that. A pretty landing page when you arrive there from the sites bar with links to the relevant info. You won't actually do any downloading from this page (and so we don't need disclaimers/more info etc). It'll be relevant to most people.
            2. The hero banner will have the purpose of being pretty and promoting the main stable version only (i.e. 2.7.1). This is useful information to people aren't necessarily downloading Moodle (e.g. teacher who wants to check if their hosting provider is using it) and its similar to other projects: https://wordpress.org https://www.drupal.org/download. It'll link to /builds/
            3. The actual downloads will be done from /builds/ - much like the current front page this page will be for syadmins/people actually downloading Moodle and will have a lot of the details
            Show
            poltawski Dan Poltawski added a comment - Barbara and I had a bit of discussion today and I wanted to sort of frame the goals for the pages the way I think it should work (and hopefully you'll all agree ) The 'landing page' is just that. A pretty landing page when you arrive there from the sites bar with links to the relevant info. You won't actually do any downloading from this page (and so we don't need disclaimers/more info etc). It'll be relevant to most people. The hero banner will have the purpose of being pretty and promoting the main stable version only (i.e. 2.7.1). This is useful information to people aren't necessarily downloading Moodle (e.g. teacher who wants to check if their hosting provider is using it) and its similar to other projects: https://wordpress.org https://www.drupal.org/download . It'll link to /builds/ The actual downloads will be done from /builds/ - much like the current front page this page will be for syadmins/people actually downloading Moodle and will have a lot of the details
            Hide
            dougiamas Martin Dougiamas added a comment -

            Congrats on getting this live. It looks a heap better than the old one.

            Small niggle, can we not say "Check out our latest release:" ... it's a bit slangy and we need to think international.

            Can someone also please estimate how many hours total went into this project so far? I'm trying to get a handle on our internal costs.

            Show
            dougiamas Martin Dougiamas added a comment - Congrats on getting this live. It looks a heap better than the old one. Small niggle, can we not say "Check out our latest release:" ... it's a bit slangy and we need to think international. Can someone also please estimate how many hours total went into this project so far? I'm trying to get a handle on our internal costs.
            Hide
            dougiamas Martin Dougiamas added a comment - - edited

            A screenshot of the app would not go astray here: https://download.moodle.org/mobile/

            Also the iOS button has a non-working graphic, for me.

            Show
            dougiamas Martin Dougiamas added a comment - - edited A screenshot of the app would not go astray here: https://download.moodle.org/mobile/ Also the iOS button has a non-working graphic, for me.
            Hide
            tsala Helen Foster added a comment -

            Thanks Martin for your feedback.

            The wording "Check out our latest release" was chosen rather than "Download our latest release" so people didn't think that clicking the button resulted in an immediate download. Is "Get..." better, or should we just use "Download"?

            Re. your comments about the mobile page, I've made a note of them in MDLSITE-3346.

            Show
            tsala Helen Foster added a comment - Thanks Martin for your feedback. The wording "Check out our latest release" was chosen rather than "Download our latest release" so people didn't think that clicking the button resulted in an immediate download. Is "Get..." better, or should we just use "Download"? Re. your comments about the mobile page, I've made a note of them in MDLSITE-3346 .
            Hide
            matteo Matteo Scaramuccia added a comment -

            @Dan: what about your proposal with named anchors?
            Refs: your comment and MDLSITE-2675.

            BTW, great work!

            Show
            matteo Matteo Scaramuccia added a comment - @Dan: what about your proposal with named anchors? Refs: your comment and MDLSITE-2675 . BTW, great work!
            Hide
            poltawski Dan Poltawski added a comment -

            Can someone also please estimate how many hours total went into this project so far? I'm trying to get a handle on our internal costs.

            Way more hours than you'd expect (and me)- accounting for just my recent time on it, I've been full time on it for the last 12 days in SITES - at 75% of time effective time (meetings etc) thats at least 72 hours. And even now, there are a lot of things we've descoped to get this live (MDLSITE-3344).

            I'm sure we'll have a debrief meeting but two major factors:

            1) The downloads site isn't just a simple webpage - there is the interaction with all the other moving parts (updates api, amos langpack publishing, main packages, mac packages). It took some time to understand and fully get a grasp on things to switch over to the new site and avoid breaking anything. (Legacy).

            2) Every wording issue is a minefield which we can and do come full circle on (see your niggle above, MDLSITE-3310 etc).

            Show
            poltawski Dan Poltawski added a comment - Can someone also please estimate how many hours total went into this project so far? I'm trying to get a handle on our internal costs. Way more hours than you'd expect (and me)- accounting for just my recent time on it, I've been full time on it for the last 12 days in SITES - at 75% of time effective time (meetings etc) thats at least 72 hours. And even now, there are a lot of things we've descoped to get this live ( MDLSITE-3344 ). I'm sure we'll have a debrief meeting but two major factors: 1) The downloads site isn't just a simple webpage - there is the interaction with all the other moving parts (updates api, amos langpack publishing, main packages, mac packages). It took some time to understand and fully get a grasp on things to switch over to the new site and avoid breaking anything. (Legacy). 2) Every wording issue is a minefield which we can and do come full circle on (see your niggle above, MDLSITE-3310 etc).
            Hide
            poltawski Dan Poltawski added a comment -

            Matteo Scaramuccia commented on that issue

            Show
            poltawski Dan Poltawski added a comment - Matteo Scaramuccia commented on that issue

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Due:
                  Created:
                  Updated:
                  Resolved:

                  Development