rsnext/examples/cms-cosmic
Freddy Montes 15cc88909c
chore(examples): Add dotCMS example (#38214)
<!--
Thanks for opening a PR! Your contribution is much appreciated.
In order 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 that you're making:
-->

This adds a new example under cms-dotcms/. Is a general-purpose example
that should allow developers to undestand how to use next.js with dotCMS
apis.

## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have helpful link attached, see `contributing.md`

## Feature

- [ ] Implements an existing feature request or RFC. Make sure the
feature request has been accepted for implementation before opening a
PR.
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [x] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.
- [ ] Errors have helpful link attached, see `contributing.md`

## Documentation / Examples

- [x] Make sure the linting passes by running `pnpm lint`
- [x] The examples guidelines are followed from [our contributing
doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)

Co-authored-by: Daniel Esteves <estevesd8@gmail.com>
Co-authored-by: Will Ezell <will@dotcms.com>
Co-authored-by: Arcadio Quintero A <oidacra@gmail.com>
Co-authored-by: Rafael <rjvelazco21@gmail.com>
2022-10-01 15:26:13 +02:00
..
components chore(examples): Cosmic cms updates (#41080) 2022-10-01 06:46:25 +02:00
interfaces chore(examples): Cosmic cms updates (#41080) 2022-10-01 06:46:25 +02:00
lib chore(examples): Cosmic cms updates (#41080) 2022-10-01 06:46:25 +02:00
pages chore(examples): fix lint 2022-10-01 06:59:44 +02:00
public/favicon CMS Cosmic Example (#13499) 2020-06-04 15:18:11 -05:00
styles CMS Cosmic Example (#13499) 2020-06-04 15:18:11 -05:00
.env.local.example Add new import flow to CMS examples (#14053) 2020-06-11 23:44:23 +00:00
.gitignore Update default gitignore templates (#39051) 2022-07-26 20:08:40 -05:00
jsconfig.json CMS Cosmic Example (#13499) 2020-06-04 15:18:11 -05:00
next-env.d.ts chore(examples): Cosmic cms updates (#41080) 2022-10-01 06:46:25 +02:00
next.config.js [Docs] Add config types to all examples (#40083) 2022-08-31 16:41:22 -05:00
package.json chore(examples): Cosmic cms updates (#41080) 2022-10-01 06:46:25 +02:00
postcss.config.js Update dependencies of all CMS examples. (#27001) 2021-07-09 14:43:56 +02:00
README.md chore(examples): Add dotCMS example (#38214) 2022-10-01 15:26:13 +02:00
tailwind.config.js [Docs] Add config types to all examples (#40083) 2022-08-31 16:41:22 -05:00
tsconfig.json chore(examples): Cosmic cms updates (#41080) 2022-10-01 06:46:25 +02:00

A statically generated blog example using Next.js and Cosmic

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

Demo

https://cosmic-next-blog.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-cosmic cms-cosmic-app
yarn create next-app --example cms-cosmic cms-cosmic-app
pnpm create next-app --example cms-cosmic cms-cosmic-app

Configuration

Step 1. Create an account and a project on Cosmic

First, create an account on Cosmic.

Step 2. Install the Next.js Static Blog app

After creating an account, install the Next.js Static Blog app from the Cosmic App Marketplace.

Step 3. Set up environment variables

Go to the Settings menu at the sidebar and click Basic Settings.

Next, copy the .env.local.example file in this directory to .env.local (which will be ignored by Git):

cp .env.local.example .env.local

Then set each variable on .env.local:

  • COSMIC_BUCKET_SLUG should be the Bucket slug key under API Access.
  • COSMIC_READ_KEY should be the Read Key under API Access.
  • COSMIC_PREVIEW_SECRET can be any random string (but avoid spaces) - this is used for Preview Mode.

Your .env.local file should look like this:

COSMIC_BUCKET_SLUG=...
COSMIC_READ_KEY=...
COSMIC_PREVIEW_SECRET=...

Step 4. Run Next.js in development mode

npm install
npm run dev

# or

yarn install
yarn dev

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

Step 5. Try preview mode

To add the ability to preview content from your Cosmic dashboard go to Posts > Edit Settings and scroll down to the "Preview Link" section. (Screenshot below)

Image

Add your live URL or localhost development URL which includes your chosen preview secret and [object_slug] shortcode. It should look like the following:

http://localhost:3000/api/preview?secret=<secret>&slug=[object_slug]
  • <secret> is the string you entered for COSMIC_PREVIEW_SECRET.
  • [object_slug] shortcode will automatically be converted to the post's slug attribute.

On Cosmic, go to one of the posts you've created and:

  • Update the title. For example, you can add [Draft] in front of the title.
  • Click Save Draft, but DO NOT click Publish. By doing this, the post will be in the draft state.

Now, if you go to the post page directly on localhost, you won't see the updated title. However, if you use the Preview Mode, you'll be able to see the change (Documentation).

Next, click the Preview Link button on the Post to see the updated title. (Screenshot below)

To exit preview mode, you can click on Click here to exit preview mode at the top.

Step 6. 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.

Important: When you import your project on Vercel, make sure to click on Environment Variables and set them to match your .env.local file.

Deploy from Our Template

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

Deploy with Vercel