Update what-is-payload.mdx
This commit is contained in:
@@ -22,10 +22,16 @@ keywords: documentation, getting started, guide, Content Management System, cms,
|
||||
- Live preview - see your frontend render content changes in realtime as you update
|
||||
- Lots more
|
||||
|
||||
### Instant backend superpowers
|
||||
|
||||
No matter what you're building, Payload will give you backend superpowers. It can be installed in one line into any existing Next.js app, and is designed to catapult your development process. Payload takes the most complex and time-consuming parts of any modern web app and makes them simple.
|
||||
|
||||
### Open source - deploy anywhere, including Vercel
|
||||
|
||||
It's fully open source with an MIT license and you can self-host anywhere that you can run a Node app. You can also deploy serverless to hosts like Vercel, right inside your existing Next.js app folder.
|
||||
|
||||
### Fully extensible
|
||||
|
||||
Even in spite of how much you get out of the box, you still have full control over every aspect of your app - be it database, admin UI, or anything else. Every part of Payload has been designed to be extensible and customizable with modern TypeScript / React. And you'll fully understand the code that you write.
|
||||
|
||||
In Payload, there are no "click ops" - as in clicking around in an admin panel to define your schema. In Payload, everything is done the right way—code-first and version controlled like a proper backend. But once developers define how Payload should work, non-technical users can independently make use of its admin panel to manage whatever they need to without having to know code whatsoever.
|
||||
@@ -36,7 +42,7 @@ Payload started as a headless Content Management System (CMS), but since, we've
|
||||
|
||||
Large enterprises use Payload to power significant internal tools, retailers power their entire storefronts without the need for headless Shopify, and massive amounts of digital assets are stored + managed within Payload. Of course, websites large and small still use Payload for content management as well.
|
||||
|
||||
#### As a CMS
|
||||
### As a CMS
|
||||
|
||||
The biggest barrier in large web projects cited by marketers is engineering. On the flip side, engineers say the opposite. This is a big problem that has yet to be solved even though we have countless CMS options.
|
||||
|
||||
@@ -54,7 +60,7 @@ Get started with Payload as a CMS using our official Website template:
|
||||
npx create-payload-app@latest -t website
|
||||
```
|
||||
|
||||
#### For enterprise tools
|
||||
### For enterprise tools
|
||||
|
||||
When a large organization starts up a new software initiative, there's a lot of plumbing to take care of.
|
||||
|
||||
@@ -77,7 +83,7 @@ Generally, the best place to start for a new enterprise tool is with a blank can
|
||||
npx create-payload-app@latest -t blank
|
||||
```
|
||||
|
||||
#### Headless commerce
|
||||
### Headless commerce
|
||||
|
||||
Companies who prioritize UX generally run into frontend constraints with traditional commerce vendors. These companies will then opt for frontend frameworks like Next.js which allow them to fine-tune their user experience as much as possible—promoting conversions, personalizing experiences, and optimizing for SEO.
|
||||
|
||||
@@ -93,7 +99,7 @@ Payload's official Ecommerce template gives you everything you need for a storef
|
||||
npx create-payload-app@latest -t ecommerce
|
||||
```
|
||||
|
||||
#### Digital asset management
|
||||
### Digital asset management
|
||||
|
||||
Payload's API-first tagging, sorting, and querying engine lends itself perfectly to all types of content that a CMS might ordinarily store, but these strong fundamentals also make it a formidable Digital Asset Management (DAM) tool as well.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user