nextcloud / nextcloud/server

Web settings design update & standardization

Open
#45,248 1 comment 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

design overview
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

General PRs:

General

  • add 40vh margin at the bottom of the page so that the content can be scrolled to the middle
  • fix dividing lines width
  • Equalize width of the content and wrap accordingly
  • Remove custom styles of headings
  • Standardize whitespace between sections
  • Security:

    • Move app password creation form to the top
    • Add a description
  • Notifications:

    • Align checkboxes with heading
    • Some whitespace between select and text
    • Not written in Vue so the select component is native
  • Sharing:

    • Federated cloud has different font-size heading
    • Add your website button is wider than the others
    • Transfer ownership too big
    • Move transfer ownership into a dialog
    • Maybe combine files and sharing sections
  • Appearance and accessibility:

    • Theme selector: come up with a layout that fits in the width limit
    • Background: Align left and see if the width can be maximised till the end of the columnn
    • Navigation bar settings: Add drag icon to the left of the items
  • Flows

    • Remove the line

Admin settings

  • Basic settings

    • Email form: left align everything and create new line for headings
    • Background jobs heading has custom styles
  • Groupware

    • Provisioning configurations: buttons side by side
    • Add configuration: if possible move to modal
    • Anti spam settings: only 1 heading and 1 explanatory paragraph, remove indentation
    • Too little whitespace between sections
    • Too little whitespace between paragraph and forms
  • Administration privileges

    • Select components too long? Try with half the width and see
  • Activity

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.