Uploaded image for project: 'KS Enrollment'
  1. KS Enrollment
  2. KSENROLL-2988

Application Boilerplate - validate proposed page titling scheme by mocking M1-M5 page titles

    Details

    • Type: Task
    • Status: In Progress
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Core UX
    • Security Level: Public (Public: Anyone can view)
    • KS Theme:
      UI Design

      Description

      Need to compare suggested titles to the scheme developed by UX Core and make recommendations for revisions.

        Attachments

          Issue Links

            Activity

            Hide
            wwashington William Washington (Inactive) added a comment -

            For each screen in the current build (~M1-M5):

            • Capture a screenshot
            • Record URL
            • Document proposed header facets (I would suggest in a spreadsheet with "Functional Area/Object or Task/Context)
            • Document any anomalies with the screen's page titling or header (e.g. includes Term search, includes Joint Listed

            As a next step:

            • Mock proposed header in new iteration of screenshot (so we can compare the two).

            Specific issues to resolve:

            • What to do with multiple pages, and with "page-level" tab groups

            Overview of currently proposed titling scheme is described here:
            https://wiki.kuali.org/display/STUDENT/KS+ENR+DS+-+Application+Boilerplate#KSENRDS-ApplicationBoilerplate-1UnifiedHeaders

            Further in-depth exploration of page titling scheme is here:
            https://docs.google.com/a/kuali.org/document/d/1TAbk1XfVToxgg8KeqS2kZnohYcByLT7vzqZPzP1a2Jk/edit
            (I believe the yellow-highlighted examples were "successful" ones, but also note that multiple pages/tabs hadn't been fleshed out).

            Document any assumptions or questions in UIM Q&A doc:
            https://docs.google.com/a/kuali.org/document/d/1Rx9ue0D25XpDOVqTUytY871kbq8Iag2ppGdwLKnWDQ8/edit#heading=h.4h61caxrpoga

            [Kevin Makice 6:36 AM May 10]
            The previous thinking was:

            For titles, guidelines should be <verb> <object type>: <object ID> <object name>. Example: Edit Course Offering: ENGL293 - Introduction to English. Use for page, views, view titles (source: https://docs.google.com/a/kuali.org/document/d/13d8aiP0DwPsQdv7xZvd_yBd2rg33aR3Eh2CmyA0sdAc/edit)
            Show less

            Show
            wwashington William Washington (Inactive) added a comment - For each screen in the current build (~M1-M5): Capture a screenshot Record URL Document proposed header facets (I would suggest in a spreadsheet with "Functional Area/Object or Task/Context) Document any anomalies with the screen's page titling or header (e.g. includes Term search, includes Joint Listed As a next step: Mock proposed header in new iteration of screenshot (so we can compare the two). Specific issues to resolve: What to do with multiple pages, and with "page-level" tab groups Overview of currently proposed titling scheme is described here: https://wiki.kuali.org/display/STUDENT/KS+ENR+DS+-+Application+Boilerplate#KSENRDS-ApplicationBoilerplate-1UnifiedHeaders Further in-depth exploration of page titling scheme is here: https://docs.google.com/a/kuali.org/document/d/1TAbk1XfVToxgg8KeqS2kZnohYcByLT7vzqZPzP1a2Jk/edit (I believe the yellow-highlighted examples were "successful" ones, but also note that multiple pages/tabs hadn't been fleshed out). Document any assumptions or questions in UIM Q&A doc: https://docs.google.com/a/kuali.org/document/d/1Rx9ue0D25XpDOVqTUytY871kbq8Iag2ppGdwLKnWDQ8/edit#heading=h.4h61caxrpoga [Kevin Makice 6:36 AM May 10] The previous thinking was: For titles, guidelines should be <verb> <object type>: <object ID> <object name>. Example: Edit Course Offering: ENGL293 - Introduction to English. Use for page, views, view titles (source: https://docs.google.com/a/kuali.org/document/d/13d8aiP0DwPsQdv7xZvd_yBd2rg33aR3Eh2CmyA0sdAc/edit ) Show less
            Hide
            erikrath Erik Rath (Inactive) added a comment -

            The latest version of the headers spreadsheet can be downloaded here:

            http://ux.ks.kuali.org.s3.amazonaws.com/UIM/Headers/TitlesTracker v1.5.xlsx

            Show
            erikrath Erik Rath (Inactive) added a comment - The latest version of the headers spreadsheet can be downloaded here: http://ux.ks.kuali.org.s3.amazonaws.com/UIM/Headers/TitlesTracker v1.5.xlsx
            Hide
            erikrath Erik Rath (Inactive) added a comment -

            This task seems like it would best be taken over by Core UX, though, the specific work described in this JIRA is also fairly complete, so may just need to be closed.

            Show
            erikrath Erik Rath (Inactive) added a comment - This task seems like it would best be taken over by Core UX, though, the specific work described in this JIRA is also fairly complete, so may just need to be closed.
            Hide
            cbeekman Cassy Beekman (Inactive) added a comment -

            Please see KULRICE-8868 and the jiras relying on it!

            Show
            cbeekman Cassy Beekman (Inactive) added a comment - Please see KULRICE-8868 and the jiras relying on it!
            Hide
            cbeekman Cassy Beekman (Inactive) added a comment -

            Removing PDT - West Coast 1 component, since this is in Core UX now.

            Show
            cbeekman Cassy Beekman (Inactive) added a comment - Removing PDT - West Coast 1 component, since this is in Core UX now.

              People

              • Assignee:
                wwashington William Washington (Inactive)
                Reporter:
                wwashington William Washington (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2 days
                  2d
                  Remaining:
                  Remaining Estimate - 2 days
                  2d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified