You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add inquirer to get some prompts
* Create some questions
Refs #16
* Add tomljs to read config for choices
* Kebab-case the input file name
* Fix listing errors
* Lint all relevant js files
* Add new incident npm script
* Set as default so out of the box this just works
* refactor out args that are used everywhere
* Add inquirer validation
* Handle inquirer answers
* Create toml from answers
* Fix linting
* Treat title and file name separately
This allows for Hugo new to work and enhances the gulp task but breaks
TranslationBaseName e.g.: `post` for `post.es.md` (if `Multilingual` is
enabled.) which I’m not sure is enabled by default.
* add comment to replace
* update new issue creation
* fix spelling
Copy file name to clipboardExpand all lines: README.md
+2-3Lines changed: 2 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -41,11 +41,10 @@ Incidents are plain markdown files inside the `site/content/incidents` directory
41
41
### Creating new incidents
42
42
43
43
Adding incidents to your status page is as simple as adding a new document to the incidents collection.
44
-
Create a new incident using Hugo with a command like this as of Hugo v0.24:
44
+
Create a new incident using npm:
45
45
46
46
```
47
-
cd site
48
-
hugo new incidents/oh-no-something-went-wrong.md
47
+
npm run new-incident
49
48
```
50
49
51
50
Hugo will create a new Markdown file for you with title and date based on the file name and a few predefined settings in the header. To learn more about the different severities and report, you can see more detailed examples in `site/archetypes/incidents.md`.
0 commit comments