Marc Roig 01a203b446
feat: move rw to plugin (#19937)
* chore: initiate moving CM to own package

* chore: refactor to handle routes

* chore: init review-workflows-package

* chore: fix build

* chore: refactor review-workflows fe

* chore: fix unit suite

* feat: move rw to plugin

* fix: build

* fix: start up

* chore: clean things up

* fix: peer dependencies

* chore(wip): refactor rw fe

* chore: re-add admin ui

* chore: fix tests & linter

* chore: re-implement drag layer

* fix: type

* feat: review-workflow middlewares

* chore: send params to CM endpoints

* fix: use layout options as well, let that have the final say, just incase

* feat: use doc id and locale for entity assignee and stage

* fix: api tests

* fix: cm updates when we update fields

* chore: cleanup edit-view e2e tests

* fix: build

* fix: useDocumentLayout for RW options

* test: fix fe tests

* fix: ts

* test(e2e): add review-workflow e2e tests

* chore: fix bad import for cli tests

* chore: delete old e2e data

* chore: import EVERYTHING for DTS

* chore: update dataset

* fix: e2e script

* fix: stage permissions

* chore: remove duplicate settings menu link

* fix: workflow middleware

* chore: change permission

* test(e2e): fix RW tests

* chore: ignore dynamic attributes in DTS

Co-Authored-By: Jean-Sébastien Herbaux <25851739+Convly@users.noreply.github.com>

* chore: make settings rw e2e run on EE only

* test(e2e): fix them all pls

* fix: admin stage transition uid name

* chore: fix firefox e2e ce tests

---------

Co-authored-by: Josh <37798644+joshuaellis@users.noreply.github.com>
Co-authored-by: Jean-Sébastien Herbaux <25851739+Convly@users.noreply.github.com>
2024-04-12 10:58:38 +02:00
..
2024-04-12 10:58:38 +02:00
2022-07-06 21:04:48 +02:00
2022-08-26 18:41:48 +02:00
2024-04-02 10:11:20 +01:00

Strapi contributor documentation

If you are looking for the official Strapi documentation, it is available here

This documentation is a contributor documentation made for anyone that wants to contribute to the project.

To run the documentation website, follow the instructions below.

Installation

$ yarn

Local Development

$ yarn start

This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.

Build

$ yarn build

This command generates static content into the build directory and can be served using any static contents hosting service.