archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update README.md (#60595)

Browse source 
### Improving Documentation

necessary update for agilitycms readme file to enhance clarity

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->
This commit is contained in:
Elyees T 2024-01-17 03:23:05 +03:00 committed by GitHub
parent 16d1c26985
commit 5e29dfc881
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 10 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
examples/cms-agilitycms/README.md
View file

@ -74,18 +74,19 @@ First, [create an account on Agility CMS](https://agilitycms.com).
After creating an account you'll be asked to create a new project. Use any name of your liking as the **Project Name** and select the **Blank (advanced users)** template to create a blank Agility CMS instance.
### Step 2. Create an `Author` Content Definition
### Step 2: Create an Author Content Definition
From within the Agility CMS Content Manager, navigate to **Settings** > **Content Definitions** and click **New** to create a new **Content Definition**.
To create an Author Content Definition in the Agility CMS Content Manager, follow these steps:
- The **Title** should be `Author`. This will also pre-populate **Reference Name** for you.
1. Navigate to **Settings** > **Content Definitions**.
2. Click on the "New" button to create a new Content Definition.
3. In the Title field, enter "Author". The Reference Name will be automatically populated for you.
4. Use the Form Builder tab to add the following fields:
- `Name`: Set the Field Label to "Name" and the Field Type to "Text".
- `Picture`: Set the Field Label to "Picture" and the Field Type to "Image".
5. Once you have added these fields, click on "Save & Close" to save your Author content definition.
Next, add these fields via the **Form Builder** tab (you don't have to modify any other settings):
- `Name` - Set **Field Label** to `Name` and **Field Type** to `Text`
- `Picture` - Set **Field Label** to `Picture` and **Field Type** to `Image`
When you are done, click **Save & Close** to save your `Author` content definition.
By following these steps, you will be able to define an Author Content Definition in the Agility CMS Content Manager.
### Step 3. Create a `List` based on your `Author` Content Definition