├── .github └── ISSUE_TEMPLATE │ └── bug_report.md ├── .gitignore ├── .nvmrc ├── .travis.yml ├── CHANGELOG.md ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE ├── README.md ├── docs └── nuxt-netlify.svg ├── generate-test.js ├── meta.js ├── netlify.toml ├── package-lock.json ├── package.json └── template ├── .editorconfig ├── .eslintrc.js ├── .gitignore ├── .travis-example.yml ├── README.md ├── app.html ├── assets └── README.md ├── components ├── AppLogo.vue └── README.md ├── content ├── blog │ └── posts │ │ └── 2018-02-13-hello-world.md └── pages │ ├── page-1.md │ └── page-2.md ├── layouts ├── README.md └── default.vue ├── middleware └── README.md ├── netlify-example.toml ├── nuxt.config.js ├── nuxtdown.config.js ├── package.json ├── pages ├── README.md ├── index.vue └── page │ └── _page.vue ├── plugins └── README.md ├── static ├── README.md ├── admin │ ├── config.yml │ └── index.html └── favicon.ico └── store └── README.md /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | title: '' 5 | labels: 'type: bug' 6 | assignees: renestalder 7 | 8 | --- 9 | 10 | **Describe the bug** 11 | A clear and concise description of what the bug is. 12 | 13 | **To Reproduce** 14 | Steps to reproduce the behavior: 15 | 1. Go to '...' 16 | 2. Click on '....' 17 | 3. Scroll down to '....' 18 | 4. See error 19 | 20 | **Expected behavior** 21 | A clear and concise description of what you expected to happen. 22 | 23 | **Screenshots** 24 | If applicable, add screenshots to help explain your problem. 25 | 26 | **Additional context** 27 | Add any other context about the problem here. 28 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | node_modules/ 2 | test/ 3 | generate-test.debug.txt 4 | 5 | # Common 6 | 7 | 8 | # Created by https://www.gitignore.io/api/linux,macos,windows,visualstudiocode 9 | # Edit at https://www.gitignore.io/?templates=linux,macos,windows,visualstudiocode 10 | 11 | ### Linux ### 12 | *~ 13 | 14 | # temporary files which can be created if a process still has a handle open of a deleted file 15 | .fuse_hidden* 16 | 17 | # KDE directory preferences 18 | .directory 19 | 20 | # Linux trash folder which might appear on any partition or disk 21 | .Trash-* 22 | 23 | # .nfs files are created when an open file is removed but is still being accessed 24 | .nfs* 25 | 26 | ### macOS ### 27 | # General 28 | .DS_Store 29 | .AppleDouble 30 | .LSOverride 31 | 32 | # Icon must end with two \r 33 | Icon 34 | 35 | # Thumbnails 36 | ._* 37 | 38 | # Files that might appear in the root of a volume 39 | .DocumentRevisions-V100 40 | .fseventsd 41 | .Spotlight-V100 42 | .TemporaryItems 43 | .Trashes 44 | .VolumeIcon.icns 45 | .com.apple.timemachine.donotpresent 46 | 47 | # Directories potentially created on remote AFP share 48 | .AppleDB 49 | .AppleDesktop 50 | Network Trash Folder 51 | Temporary Items 52 | .apdisk 53 | 54 | ### VisualStudioCode ### 55 | .vscode/* 56 | !.vscode/settings.json 57 | !.vscode/tasks.json 58 | !.vscode/launch.json 59 | !.vscode/extensions.json 60 | 61 | ### VisualStudioCode Patch ### 62 | # Ignore all local history of files 63 | .history 64 | 65 | ### Windows ### 66 | # Windows thumbnail cache files 67 | Thumbs.db 68 | ehthumbs.db 69 | ehthumbs_vista.db 70 | 71 | # Dump file 72 | *.stackdump 73 | 74 | # Folder config file 75 | [Dd]esktop.ini 76 | 77 | # Recycle Bin used on file shares 78 | $RECYCLE.BIN/ 79 | 80 | # Windows Installer files 81 | *.cab 82 | *.msi 83 | *.msix 84 | *.msm 85 | *.msp 86 | 87 | # Windows shortcuts 88 | *.lnk 89 | 90 | # End of https://www.gitignore.io/api/linux,macos,windows,visualstudiocode 91 | -------------------------------------------------------------------------------- /.nvmrc: -------------------------------------------------------------------------------- 1 | 10.15.0 -------------------------------------------------------------------------------- /.travis.yml: -------------------------------------------------------------------------------- 1 | language: node_js 2 | cache: npm 3 | 4 | script: 5 | - npm run ci:test # Generate test project -------------------------------------------------------------------------------- /CHANGELOG.md: -------------------------------------------------------------------------------- 1 | # Changelog 2 | All notable changes to this project will be documented in this file. 3 | 4 | This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). 5 | 6 | ## 2.0.0 - 2019-01-11 7 | 8 | ### Features 9 | 10 | * **Nuxt v2.2.x**: The template was updated to use Nuxt v2.0.0. 11 | * **Netlify Config Example**: Added a Netlify config example that enables the `npm run generate` to work on all kinds of deployments e.g. Branch, Preview and Production deployment without the need of additional configuration. 12 | 13 | In addition, the README was updated with more clear instructions how to use it in different environments, not only with Netlify deploy. 14 | 15 | ### Breaking changes 16 | 17 | If you want to apply the template changes to your current project using the template, be aware of the following required changes to make your project work. 18 | 19 | * Nuxt v2.x replaces `isClient` with `process.client`. See [required](https://github.com/renestalder/nuxt-netlify-cms-starter-template/commit/ca752c53adb221bde3070a8c4197ea140ccd4a5a#diff-ab6b79105e8be7d546b7510a53d2dd71) changes to the `nuxt.config.js`. 20 | 21 | ## 1.0.0 - 2019-01-06 22 | 23 | Initial stable release with frontmatter support. 24 | 25 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as 6 | contributors and maintainers pledge to making participation in our project and 7 | our community a harassment-free experience for everyone, regardless of age, body 8 | size, disability, ethnicity, sex characteristics, gender identity and expression, 9 | level of experience, education, socio-economic status, nationality, personal 10 | appearance, race, religion, or sexual identity and orientation. 11 | 12 | ## Our Standards 13 | 14 | Examples of behavior that contributes to creating a positive environment 15 | include: 16 | 17 | * Using welcoming and inclusive language 18 | * Being respectful of differing viewpoints and experiences 19 | * Gracefully accepting constructive criticism 20 | * Focusing on what is best for the community 21 | * Showing empathy towards other community members 22 | 23 | Examples of unacceptable behavior by participants include: 24 | 25 | * The use of sexualized language or imagery and unwelcome sexual attention or 26 | advances 27 | * Trolling, insulting/derogatory comments, and personal or political attacks 28 | * Public or private harassment 29 | * Publishing others' private information, such as a physical or electronic 30 | address, without explicit permission 31 | * Other conduct which could reasonably be considered inappropriate in a 32 | professional setting 33 | 34 | ## Our Responsibilities 35 | 36 | Project maintainers are responsible for clarifying the standards of acceptable 37 | behavior and are expected to take appropriate and fair corrective action in 38 | response to any instances of unacceptable behavior. 39 | 40 | Project maintainers have the right and responsibility to remove, edit, or 41 | reject comments, commits, code, wiki edits, issues, and other contributions 42 | that are not aligned to this Code of Conduct, or to ban temporarily or 43 | permanently any contributor for other behaviors that they deem inappropriate, 44 | threatening, offensive, or harmful. 45 | 46 | ## Scope 47 | 48 | This Code of Conduct applies both within project spaces and in public spaces 49 | when an individual is representing the project or its community. Examples of 50 | representing a project or community include using an official project e-mail 51 | address, posting via an official social media account, or acting as an appointed 52 | representative at an online or offline event. Representation of a project may be 53 | further defined and clarified by project maintainers. 54 | 55 | ## Enforcement 56 | 57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 58 | reported by contacting the project team at renestalder@protonmail.com. All 59 | complaints will be reviewed and investigated and will result in a response that 60 | is deemed necessary and appropriate to the circumstances. The project team is 61 | obligated to maintain confidentiality with regard to the reporter of an incident. 62 | Further details of specific enforcement policies may be posted separately. 63 | 64 | Project maintainers who do not follow or enforce the Code of Conduct in good 65 | faith may face temporary or permanent repercussions as determined by other 66 | members of the project's leadership. 67 | 68 | ## Attribution 69 | 70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, 71 | available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html 72 | 73 | [homepage]: https://www.contributor-covenant.org 74 | 75 | For answers to common questions about this code of conduct, see 76 | https://www.contributor-covenant.org/faq 77 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contribution 2 | 3 | Contributions are more than welcome. 4 | 5 | ## Development 6 | 7 | This section describes steps for direct contribution to this template. 8 | 9 | 1. Checkout git repository. 10 | 2. Install dependencies. 11 | ```sh 12 | $ npm ci # or npm i 13 | ``` 14 | 3. Automatically install and build the template to a test folder. 15 | ```sh 16 | $ npm run ci:test 17 | ``` 18 | 19 | Now, whenever you make changes to the source files in `template/`, you can directly test the installation 20 | and the build. It isn't possible to directly build the project inside `template/` due to variables 21 | that get replaced during the vue init steps. 22 | 23 | ## Commit Message Guidelines 24 | 25 | ### Commit Message Format 26 | Each commit message consists of a **header**, a **body** and a **footer**. The header has a special 27 | format that includes a **type**, a **scope** and a **subject**: 28 | 29 | ``` 30 | (): 31 | 32 | 33 | 34 |