rsnext/examples/cms-makeswift
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
..
lib/makeswift Add a Makeswift example (#38018) 2022-06-29 13:25:51 -05:00
pages Update cms-makeswift example (#41005) 2022-09-28 11:33:08 -07:00
.env.local.example Update cms-makeswift example (#39834) 2022-08-22 16:02:19 -05: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 chore: remove swcMinify: true as it's the new default. (#41877) 2022-10-26 10:55:10 -07:00
package.json Update cms-makeswift example (#41005) 2022-09-28 11:33:08 -07:00
README.md Add a Makeswift example (#38018) 2022-06-29 13:25:51 -05:00
tsconfig.json Add a Makeswift example (#38018) 2022-06-29 13:25:51 -05:00

A statically generated landing page with Next.js and Makeswift

This example showcases how you can use Makeswift to visually build statically generated pages in Next.js.

Deploy your own

Deploy the example using Vercel:

Deploy with Vercel

Demo

https://nextjs-makeswift-example.vercel.app/

How to use

  1. Download the example:

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

    npx create-next-app --example cms-makeswift cms-makeswift-app
    # or
    yarn create next-app --example cms-makeswift cms-makeswift-app
    # or
    pnpm create next-app --example cms-makeswift cms-makeswift-app
    
  2. Install dependencies:

    yarn install
    # or
    npm install
    # or
    pnpm install
    
  3. Rename the .env.local.example file to .env.local and include your Makeswift site's API key:

    -- MAKESWIFT_API_HOST=
    -- MAKESWIFT_SITE_API_KEY=
    ++ MAKESWIFT_API_HOST=https://api.makeswift.com
    ++ MAKESWIFT_SITE_API_KEY=<YOUR_MAKESWIFT_SITE_API_KEY>
    
  4. Run the local dev script:

    yarn dev
    # or
    npm run dev
    

    Your host should be up and running on http://localhost:3000.

  5. Finally, go to your Makeswift site settings and add http://localhost:3000/makeswift as the host URL and you're all set!

Deploy it

When you're ready to go live, deploy it to the cloud with Vercel (Documentation). All you'll need to do is update your host inside of Makeswift to your Vercel deployment.

Next steps

With Makeswift, you can give your marketing team custom building blocks to create high quality Next.js pages.

To learn more about Makeswift, take a look at the following resources:

You can check out the Makeswift GitHub repository - your feedback and contributions are welcome!