Compare commits

...

1 Commits
0.4.1 ... main

Author SHA1 Message Date
Adnan ELARAJI
92b387d910 Fix typo in README.md file (#19)
Fixed a couple of  typos.

Co-authored-by: Adnan ELARAJI <7360655+aelaraji@users.noreply.github.com>
Reviewed-on: https://git.mills.io/prologic/zs/pulls/19
Reviewed-by: James Mills <james@mills.io>
Co-authored-by: Adnan ELARAJI <aelaraji@noreply@mills.io>
Co-committed-by: Adnan ELARAJI <aelaraji@noreply@mills.io>
2024-05-10 10:13:34 +00:00

View File

@ -51,7 +51,7 @@ EOF
zs serve
```
For a starter template see the [zs-starter-template](https://git.mills.io/prologic/zs-stater-template) which can also be found running live at [zs.mills.io](https://zs.mills.io).
For a starter template see the [zs-starter-template](https://git.mills.io/prologic/zs-starter-template) which can also be found running live at [zs.mills.io](https://zs.mills.io).
## Features
@ -99,7 +99,7 @@ Markdown text goes after a header *separator*
```
Use placeholders for variables and plugins in your markdown or html
files, e.g. `{{ title }}` or `{{ command arg1 arg2 }}.
files, e.g. `{{ title }}` or `{{ command arg1 arg2 }}`.
Write extensions in any language you like and put them into the `.zs`
sub-directory.
@ -159,7 +159,7 @@ For a full-list of default extensions enabled, see `zs --help` and the `-e/--ext
Plugins are just executables in any language that output content. They can be system executables like `data` or custom scripts or programs that you place in `.zs/`. To use a plugins simply reference it in your content like so:
```markdown
Site last updated at {{{ date }}
Site last updated at {{ date }}
```
or: