Skip to content

Commit 4320ee0

Browse files
committed
Remove CMS on readme
1 parent 871c92c commit 4320ee0

1 file changed

Lines changed: 5 additions & 13 deletions

File tree

README.md

Lines changed: 5 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -36,29 +36,21 @@ Netlify can run in any frontend web environment, but the quickest way
3636
to try it out is by running it on a pre-configured starter site with
3737
Netlify.
3838

39-
[![Deploy to Netlify](https://www.netlify.com/img/deploy/button.svg)](https://app.netlify.com/start/deploy?repository=https://github.com/faeldon/faeldon-website&stack=cms)
39+
[![Deploy to Netlify](https://www.netlify.com/img/deploy/button.svg)](https://app.netlify.com/start/deploy?repository=https://github.com/faeldon/faeldon-website)
4040

4141
After clicking the link, you’ll authenticate with GitHub and choose a
4242
repository name. Netlify will then automatically create a repository
4343
in your GitHub account with a copy of the files from the template.
44-
Next, it will build and deploy the new site on Netlify, bringing you
45-
to the site dashboard when the build is complete. Next, you’ll need to
46-
set up Netlify’s Identity service to authorize users to log in to the
47-
CMS.
44+
45+
Finally, it will build and deploy the new site on Netlify, bringing you
46+
to the site dashboard when the build is complete.
4847

4948

5049
### Access Locally
5150
```
5251
$ git clone https://github.com/[GITHUB_USERNAME]/[REPO_NAME].git
5352
$ cd [REPO_NAME]
54-
$ yarn
55-
$ npm run start
56-
```
57-
58-
To test the CMS locally, you'll need run a production build of the site:
59-
```
60-
$ npm run build
61-
$ npm run serve
53+
$ npm run develop
6254
```
6355

6456
# CONTRIBUTING

0 commit comments

Comments
 (0)