Skip to content

EPIC: Structure playbook with spaces #220

Description

@jracenet

Description

Currently, all playbook entries (standards, commands, and skills) are stored and managed
at a global, flat organization level. This causes ownership and scaling issues.

This epic will introduce the concept of "spaces". Spaces are entities belonging to an
organization that contain their own playbook. They will allow teams to structure and
author their best practices in isolation.

Scope

⚠️ Warning: This epic will solely focus on playbook organization. It will not cover
things such as user rights regarding playbook authoring. ⚠️

This epic will cover the following capabilities:

  • Spaces can be added to / removed from an organization
  • Playbook entries can be managed within a space
  • Playbook entries can be moved from one space to another
  • Minimal space member management (invite / join…)
  • Set space visibility: public (a space can be discovered by any member of the
    organization) / private (a member needs to be invited)
  • New navbar enabling smooth navigation across multiple spaces

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions