Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P Plasma Workspace
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 18
    • Issues 18
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 96
    • Merge requests 96
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Plasma
  • Plasma Workspace
  • Issues
  • #31

Closed
Open
Created Dec 01, 2021 by Artem Grinev@agrinevDeveloper

Layouts KCM

Previous discussion

IMO previous decision doesn't cover all use cases of separate KCM for Layouts, for example layouts that exist without theme at all (similar how Splash screens now work).

They also don't overlap with each other as having more granular control for global theme in all aspects and maybe even show for user what components global theme sets also sounds reasonable.

So considering these points I'd like to propose and implement a separate KCM for layout.

cc @teams/vdg @teams/usability

Edited Dec 01, 2021 by Artem Grinev
Assignee
Assign to
Time tracking