Details

    • Type: Task
    • Status: Merged (View workflow)
    • Priority: unspecified
    • Resolution: Ready for Release
    • Affects Version/s: None
    • Fix Version/s: platform-4.0.0
    • Component/s: None
    • Labels:
      None
    • Tested Version/s:
      None
    • Sprint:
      16.17, 16.18, 16.19, 16.20, 16.21, 16.22, 16.23
    • Story Points:
      3

      Description

      At the moment, frontend path uses /a, and alpha editor uses /app, as part of this change:

      Scope changes

      • Changed new glossary path from /glossary/{id} to /glossary?locale={localeid}
        • There is no glossary id since we only have a global glossary
        • Discussed 1/Sep/16 by damason, sflanigan
      • Added Requirements section.
        • In yesterday's meeting, we discussed several requirements, but they were not written down.
        • Checked with aeng about what we discussed for redirects.

      Requirements

      • "Try the new alpha editor" button in old editor still opens the new editor.
      • Opening a bookmark to the previous location of the alpha editor should show a 404 page.
        • There was discussion of a link from the 404 page to the new alpha editor path, but no one wrote it down. No one will remember by the time it is being tested, so I guess I should just add this if I feel like it.
      • Profile and glossary pages are not deployed yet so no redirect is needed.

      New paths to implement

      Profile:

      /profile/view/{username}
      
      • currently
        /a/#/profile/{username}

      Glossary:

      /glossary?locale={localeid}
      
      • currently
        /a/#/glossary?locale={localeid}

      Editor:

      /project/{project}/v/{version}/translate/{document}?lang={locale}
      
      • currently
        /app/#/{project}/{version}/translate/{document}/{locale}
      • document should be standard url encoded, but / characters can be included literally. Spaces, percentage sign, comma, quotes, apostrophe, semicolon, question mark, etc. will still need to be encoded, similar to github. e.g.
        /project/my-project/v/1.5/translate/path1/path2/my%20files/file.name?lang=en_us
        

      Technical notes

      This will require some server-side rules, similar to the ones we use on the project pages (which use crossroads.js for client-side routing):

                      .addRule(Join.path("/project/view/{slug}").to("/project/project.xhtml"))
                      .addRule(Join.path("/project/view/{slug}/{section}").to("/project/project.xhtml"))
                      .where("section").matches(".*")
      

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                damason David Mason
                Reporter:
                aeng Alex Eng
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: