Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C Compose
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Alloy Magnetic
  • Compose
  • Issues
  • #9

Closed
Open
Created Aug 02, 2018 by Matt Moen@mattOwner

Take over node edit form with compose interface

For a content type that has opted in to the compose interface, the node add/edit form for that type is replaced with the compose interface.

  • No sidebar
  • Four tabs: Compose, Fields, Settings, Revisions
  • Any field marked to use compose in the form display settings for the type will appear on the compose.
  • All other fields appear on the fields tab
  • All "Advanced" (sidebar) stuff appears in settings
  • If there are no items in the compose or fields tabs, those tabs should not be available.
  • Tabs should use existing UI patterns for display purposes, but should load without a refresh.
  • Load revisions via ajax callback
Edited Aug 02, 2018 by Matt Moen
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking