# nuxt-content-git
Additional module for @nuxt/content that replaces or adds createdAt and updatedAt dates based on the git history.
## Install
```bash
# npm
$ npx nuxi module add nuxt-content-git
# Yarn
$ yarn nuxi module add nuxt-content-git
```
## Usage
Add the module to your `nuxt.config.js`:
```js
export default {
modules: [
'@nuxt/content',
'nuxt-content-git',
},
}
```
This will set `doc.createdAt` and `doc.updatedAt` with the dates from the Git log.
Now you need to define those fields in your collection schema, otherwise @nuxt/content won't add them to the database.
```js
// content.config.js
import { defineContentConfig, defineCollection, z } from '@nuxt/content';
export default defineContentConfig({
collections: {
content: defineCollection({
source: '**',
type: 'page',
schema: z.object({
createdAt: z.date(),
updatedAt: z.date(),
}),
}),
},
});
```
You can override the values via front matter like so:
```md
// content/home.md
---
createdAt: 2020-04-04
updatedAt: 2020-06-06
---
```
It is also possible to adjust the field names like this:
```js
export default {
modules: [
'@nuxt/content',
['nuxt-content-git', {
createdAtName: 'gitCreatedAt',
updatedAtName: 'gitUpdatedAt',
}],
],
}
```
Update the schema accordingly. Then you can access them via `doc.gitCreatedAt` and `doc.gitUpdatedAt`.
## Deployment
The module uses the Git history to calculate the dates. That is why the history also needs to be checked out when deploying the project to live. During local development the repository is usually deeply cloned. But CI systems like GitHub Actions often only do a shallow clone for performance reasons, which will result in wrong dates.
To do a deep clone in a GitHub Actions workflow, configure the checkout step the following way:
```yaml
- uses: actions/checkout
with:
fetch-depth: 0
```
Keep in mind that when deploying to static site hosters like GitHub Pages, you also need to do a deep clone on the system where you are generating the site. So do a local regular clone when generating locally, or use the config above for GitHub actions.
## Contribute
Are you missing something or want to contribute? Feel free to file an [issue](https://github.com/dword-design/nuxt-content-git/issues) or a [pull request](https://github.com/dword-design/nuxt-content-git/pulls)! ⚙️
## Support
Hey, I am Sebastian Landwehr, a freelance web developer, and I love developing web apps and open source packages. If you want to support me so that I can keep packages up to date and build more helpful tools, you can donate here:
If you want to send me a one time donation. The coffee is pretty good 😊.
Also for one time donations if you like PayPal.
Here you can support me regularly, which is great so I can steadily work on projects.
Thanks a lot for your support! ❤️
## See also
* [nuxt-content-body-html](https://github.com/dword-design/nuxt-content-body-html): Embed a Mermaid diagram in a Nuxt.js app by providing its diagram string.
* [nuxt-mail](https://github.com/dword-design/nuxt-mail): Adds email sending capability to a Nuxt.js app. Adds a server route, an injected variable, and uses nodemailer to send emails.
* [nuxt-route-meta](https://github.com/dword-design/nuxt-route-meta): Adds Nuxt page data to route meta at build time.
* [nuxt-modernizr](https://github.com/dword-design/nuxt-modernizr): Adds a Modernizr build to your Nuxt.js app.
* [nuxt-mermaid-string](https://github.com/dword-design/nuxt-mermaid-string): Embed a Mermaid diagram in a Nuxt.js app by providing its diagram string.
## License
[MIT License](https://opensource.org/license/mit/) © [Sebastian Landwehr](https://sebastianlandwehr.com)