Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-29008 Feature requests needing merging/consideration for Sakai 11
  3. SAK-29400

Feature Request: Rename "Site Info" to "Info & Settings"



    • Type: Sub-task
    • Status: OPEN
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 11.0, 19.6, 20.2, 21.0 [Tentative], 22.0 [Tentative]
    • Fix Version/s: None
    • Component/s: Site Info, Translation
    • Labels:


      For years, there has been interest in the Sakai community in renaming the "Site Info" tool to something that better describes its function. For Sakai 11, I propose renaming the tool from "Site Info" to "Site Settings."

      "Site Info" is not clear and does not communicate the tool's utility, especially to instructors or site managers. Users often say that the label "Info" does not convey that they can change anything related to the site, just view information about it. By changing its tool name, the goal is to clear up this confusion and empower professors to manage their sites. At the same time, "Site Info" isn't limited only to instructors, teaching assistants, or "maintain" users. Students or "access" users also can use the tool. For example, group functionality is part of the Site Info tool. So, student users need access to the tool and a label that doesn't make the tool seem to be only for professors.

      I propose "Site Settings" since this communicates a place where someone can check the settings. Settings could apply to any user. Labels like "Site Setup," "Site Editor," "Site Manager," "Control Panel," etc. may suggest that non-instructor/maintain users shouldn't try the tool. The label "Settings" is also used by popular online services like Google to allow users to adjust a tool's settings, so this seems in alignment with software in general, too.

      I am completely open to other naming conventions. I'd just love an improvement to the name of this important tool! Thank you for your consideration.

        Gliffy Diagrams



              Issue Links



                  maintenanceteam Core Team
                  alanregan Alan Regan
                  16 Vote for this issue
                  20 Start watching this issue



                      Git Integration