nextjs-non-profit-website
next-merge
| nextjs-non-profit-website | next-merge | |
|---|---|---|
| 1 | 1 | |
| 6 | 1 | |
| - | - | |
| 0.0 | 0.0 | |
| about 2 years ago | almost 2 years ago | |
| TypeScript | TypeScript | |
| - | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nextjs-non-profit-website
-
Build a Non-Profit App with Next.js and Cosmic
Install the App Template View the live demo Check out the code
next-merge
-
Show HN: Cosmic Merge Requests – Git-like workflows for CMS content
Hi HN,
I'm Tony, CEO and cofounder of Cosmic (W19). Since launching our headless CMS on HN during our YC batch (https://news.ycombinator.com/item?id=19330262), we've been working toward finding modern solutions to content management problems.
Something we've noticed is that traditional CMS systems have long relied on a draft / published model for content updates within a single database. And for many use cases this is fine. But what we’ve noticed with our users, is that they want to create multiple environments to stage updates for review, preview the changes, then push the changes to production. The problem with this, is that there wasn't an easy way to merge content changes between environments in review stages (such as Development, Staging, Production). This is especially true when you want to make large bulk edits to lots of content.
For this reason, we built Merge Requests (https://www.cosmicjs.com/blog/introducing-merge-requests).
Much like coding teams use git to work in isolated branches, make pull requests for updates, add reviewers with dedicated preview links to compare changes to code, with Cosmic Merge Requests you can work in isolated content environments, create a merge request, request reviewers, review dedicated preview links with bulk updates, and involve team approvals before merging content changes to production.
It works like this: Teams work in separate Bucket environments to add / update content, safely isolated from production content. When ready, a merge request is submitted to review content changes. Reviewers can be added to review and approve updated content. Preview links are available to preview bulk edits in the user-facing application or website. After approvals, a merge is performed. If needed, restoring to a previous version can be done in a few clicks.
To get started, sign up for a free Cosmic account (https://www.cosmicjs.com/). You can also install the Next Merge Starter (https://github.com/cosmicjs/next-merge) which includes merge request preview capabilities. Read the docs to get more information on how to implement the merge request preview for your applications currently available via the REST API and NPM module (https://docs.cosmicjs.com/rest-api/objects.html#get-objects-...).
The feature is free to anyone who signs up. If you want to see how it works without signing up, check out the videos on the blog announcement (https://www.cosmicjs.com/blog/introducing-merge-requests).
Cosmic Merge Requests is still a work in progress (currently in beta), and we would greatly appreciate any feedback that you may have in the comments below.
What are some alternatives?
faustjs - Faust.js™ - The Headless WordPress Framework
Stripe - PHP library for the Stripe API.
simple-nextjs-blog - A simple blog powered by Next.js and the Cosmic headless CMS