rsnext/examples/cms-prismic
Karl Horky 3ad55721d1
Remove incorrect entries for pnpm debug log (#47241)
**Reasons for making this change:**

- it is contained within `node_modules/`, which is already ignored
- the previous versions, which were not in `node_modules/`, did not have
a period at the beginning of the filename

Links to documentation supporting these rule changes:

**Changelog with proof here:**


ba4b2db1f2/pnpm/CHANGELOG.md (L3330)

History:

- my PR to remove this from `github/gitignore` here:
https://github.com/github/gitignore/pull/4250
- First introduced in `github/gitignore` in
https://github.com/github/gitignore/pull/3732 by `@sakurayang` (merged
by `@martinwoodward`)

<!-- 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 or adding/fixing 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 #

-->

---------

Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-03-26 22:26:05 -07:00
..
.slicemachine chore(examples): refresh cms-prismic example (#40121) 2022-10-01 06:06:49 +02:00
components Run next/link codemod for Next.js 13 on examples (#41913) 2022-10-30 21:00:45 +01:00
customtypes chore(examples): refresh cms-prismic example (#40121) 2022-10-01 06:06:49 +02:00
documents chore(examples): refresh cms-prismic example (#40121) 2022-10-01 06:06:49 +02:00
lib chore(examples): refresh cms-prismic example (#40121) 2022-10-01 06:06:49 +02:00
pages fix(cms-examples): title warning (#46262) 2023-02-23 15:21:03 +00:00
public/favicon Add Prismic Example (#10897) 2020-04-10 12:41:09 +02:00
slices chore(examples): refresh cms-prismic example (#40121) 2022-10-01 06:06:49 +02:00
styles Add Prismic Example (#10897) 2020-04-10 12:41:09 +02:00
.gitignore Remove incorrect entries for pnpm debug log (#47241) 2023-03-26 22:26:05 -07:00
next-env.d.ts Remove incorrect entries for pnpm debug log (#47241) 2023-03-26 22:26:05 -07:00
next.config.js [Docs] Add config types to all examples (#40083) 2022-08-31 16:41:22 -05:00
package.json chore(examples): refresh cms-prismic example (#40121) 2022-10-01 06:06:49 +02:00
postcss.config.js Update dependencies of all CMS examples. (#27001) 2021-07-09 14:43:56 +02:00
prismicCodegen.config.ts chore(examples): refresh cms-prismic example (#40121) 2022-10-01 06:06:49 +02:00
README.md chore(examples): Add dotCMS example (#38214) 2022-10-01 15:26:13 +02:00
sm.json chore(examples): refresh cms-prismic example (#40121) 2022-10-01 06:06:49 +02:00
tailwind.config.js chore(examples): refresh cms-prismic example (#40121) 2022-10-01 06:06:49 +02:00
tsconfig.json chore(examples): refresh cms-prismic example (#40121) 2022-10-01 06:06:49 +02:00
types.generated.ts chore(examples): refresh cms-prismic example (#40121) 2022-10-01 06:06:49 +02:00

A statically generated blog example using Next.js and Prismic

This example showcases Next.js's Static Generation feature using Prismic as the data source.

Demo

https://next-blog-prismic.vercel.app/

Deploy your own

Once you have access to the environment variables you'll need, deploy the example using Vercel:

Deploy with Vercel

How to use

Execute create-next-app with npm, Yarn, or pnpm to bootstrap the example:

npx create-next-app --example cms-prismic cms-prismic-app
yarn create next-app --example cms-prismic cms-prismic-app
pnpm create next-app --example cms-prismic cms-prismic-app

Configuration

Step 1. Create an account and repository on Prismic

First, create a Prismic account and repository with the following command:

npx @slicemachine/init

This command will:

  1. Ask you to log in to Prismic or create an account.
  2. Create a new Prismic repository with premade Author and Post content models.
  3. Connect the Prismic repository to your app.

Optional: To see the premade content models, start the Slice Machine app.

npm run slicemachine

Slice Machine should be available on http://localhost:9999 once started.

Step 2. Populate Content

Go to the Prismic dashboard and select your Prismic repository.

Once in, click on Create new and select the Author type:

  • You just need 1 author document.
  • Use dummy data for the text.
  • For the image, you can download one from Unsplash.

Save and publish the document.

Next, go back to the documents list, click on Create new and select the Post type:

  • We recommend creating at least 2 Post documents.
  • Use dummy data for the text.
  • You can use the Text and Image Slices to create content.
  • For images, you can download them from Unsplash.
  • Pick the author you created earlier.

Important: For each document, you need to click Publish after saving. If not, the document will be in the draft state.

Step 3. Run Next.js in development mode

npm run dev

# or

yarn dev

Your blog should be up and running on http://localhost:3000! If it doesn't work, post on GitHub discussions.

Step 4. Try preview mode

On your repository page, go to Settings, click on Previews, and then Create a New Preview. Fill the form like so for development previews:

  • Site Name: may be anything, like "Development"
  • Domain of Your Application: http://localhost:3000
  • Link Resolver: /api/preview

Once saved, go to one of the posts you created and:

  • Update the title. For example, you can add [Draft] in front of the title.
  • Click Save, but DO NOT click Publish. By doing this, the post will be in draft state.
  • Right next to the Publish button, you should see the Preview button, displayed with an eye icon. Click on it!

You should now be able to see the updated title. To exit preview mode, click on the "x" icon in the purple Prismic toolbar in the bottom left corner of the page.

Step 5. Deploy on Vercel

You can deploy this app to the cloud with Vercel (Documentation).

Deploy Your Local Project

To deploy your local project to Vercel, push it to GitHub/GitLab/Bitbucket and import to Vercel.

Deploy from Our Template

Alternatively, you can deploy using our template by clicking on the Deploy button below.

Deploy with Vercel