Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-76548

Remove classic theme (and move it to the plugins directory)

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • 4.1
    • Themes
    • None
    • MOODLE_401_STABLE

      While running some discoverability user sessions we've realised a few are missing some of the main features added from Moodle 4.0 onwards (like the sticky Edit edition toggle or the course index) because they are still using the classic theme. That leads us to re-think if maintaining both themes (classic and boost) is something good or something that should be discussed:

      • Pros classic removal
        • Users won't miss new features added only to boost.
        • Easier to maintain (fewer code, fewer behat tests, fewer CI jobs...)
        • UX team will focus on improving the boost theme, to include the missing features from classic.
      • Cons classic removal
        • It helps to identify non-boost behat failures.
        • With classic, users feel they use fewer clicks to navigate.

       

      This issue is the first step to start the discussion to check what people think about the classic removal (it would be moved to the plugins directory). So, please, feel free to share your 5 cents here  

            Votes:
            5 Vote for this issue
            Watchers:
            19 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.