Skip to content

Split up Admin page into groups #712

Closed

Description

@blizzz

We want to have the huge admin page split up in groups.

Goals:

  • avoid to have a single huge, long page
  • group different settings reasonable (e.g. everything related to sharing & federation)
  • make sure specific settings have full pages (like Log, LDAP etc)
  • avoid very small setting pages by another group "Additional settings"

Long term considerations:

  • integrate personal settings

Solution:

  • anything that has an admin settings page will register a Controller. A group¹ parameter is required.
  • legacy support: group apps that do not register a controller into "Additional Settings"
  • downside: we need to adjust as many apps as possible and provide developer documentation quickly

¹also requires a way to register groups. Probably another controller to register new groups and have "core" groups pre-defined (sharing, logging, background jobs, …)

@jancborchardt @nickvergessen

Activity

  1. added this to the Nextcloud 11.0 milestone on Aug 3, 2016
  2. self-assigned this
    on Aug 3, 2016
  3. jancborchardt commented on Aug 3, 2016

    @jancborchardt
    Member

    Good summary. I only adjusted details (added federation, Logs and LDAP as specific examples).

    And just for reference, the original oC issue is at owncloud/core#24188

  4. MariusBluem commented on Aug 9, 2016

    @MariusBluem
    Member

    Maybe we could also integrate @icewind1991's logreader (https://github.com/icewind1991/logreader) as the default one into its own page. Now we would have space for it 😉 What do you think?

  5. blizzz commented on Aug 9, 2016

    @blizzz
    MemberAuthor

    @Mar1u5 this crossed my mind when I looked into the Logging section today. I would find it useful, however this would be out of scope of this issue (and the PR #796 is already huge).

  6. icewind1991 commented on Aug 10, 2016

    @icewind1991
    Member

    Once #796 is done I'll adjust the logreader to register itself in the admin page, we can then look into shipping it on default

  7. MorrisJobke commented on Aug 17, 2016

    @MorrisJobke
    Member

    This is merged and backported to stable10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions