Skip to content

Content pages editor #161

@josepjaume

Description

@josepjaume

🎩 User Story

Organization admins should be able to edit a pre-defined, set of pages like terms and conditions, FAQ, etc, and potentially define new ones.

There's a set of pages that should appear as created and editable but not removable, as there's gonna be static references to them throughout the page (footer, registration, etc).

  • FAQ
  • Terms and Conditions
  • Accessibility

At a technical level, those pages could be created during the seeds or simply by providing a fallback (content pending definition) and actually creating the page when the user "edits" it.

A page has the following fields:

  • Slug (not I18n)
  • Title (I18n)
  • Content (I18n, limited WYSIWYG)

Remember that we'll need to remove the current terms and conditions page and allow editing it from the system.

📋 Related documentation

🎯 Acceptance criteria

Organization admins can manage static pages. Any user can see those pages via a link provided in the admin panel.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions