Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: updated readme with personal token information #11

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Dapple is an attempt at providing a unified workflow for three DPL projects:
- [React components](https://github.com/danskernesdigitalebibliotek/dpl-react)
- [CMS](https://github.com/danskernesdigitalebibliotek/dpl-cms)

These projects recide in separate repositories but are used by one another to
These projects recide in separate repositories but are used by one another to
provide a complete application. While there is an established workflow for
implementing changes which span multiple repositories, some processes may
result in much back and forth between the individual parts. This can become
Expand All @@ -25,7 +25,7 @@ three projects with direct links between each of them.

- [Docker Compose](https://docs.docker.com/compose/install/)
- [Task](https://taskfile.dev/#/installation)
- Prerequisites required by the individual projects.
- Prerequisites required by the individual projects. (the design system requires a personal access token when running `task init`. The task will fail if not present)

## Installation

Expand Down Expand Up @@ -53,4 +53,4 @@ three projects with direct links between each of them.
7. Make a change in the local `react` project
8. See that the change triggers a build of the React components
9. See that the change causes the CMS cache to be cleared
10. Reload the browser to see the change reflected in the CMS
10. Reload the browser to see the change reflected in the CMS
Loading