Add articles associated with module development youtube

This commit is contained in:
Mark Bools 2024-08-24 18:52:24 +01:00
parent 88af3553b4
commit d1b01fb422
2 changed files with 43 additions and 0 deletions

View File

@ -0,0 +1,18 @@
+++
title = "Github Repository Setup"
date = 2024-08-22T09:00:00Z
draft = false
summary="Learning Foundry VTT Module Development from the very start"
categories = ['Technical', 'FoundryVTT', 'Foundry VTT for Module Developers']
prev = ['/post/lets-build-a-module/']
+++
In the [previous post]({{< ref "/post/lets-build-a-module/" >}}) I proposed we build a couple of Foundry modules. This post starts that process, looking at Github to hold our module code.
{{< youtube nXZ-fwcygYk >}}
Although not a detailed lesson on Github, this session covers:
* Setting up your account to use SSH keys.
* Creating a repository to hold our module.
* Cloning that repository to our local development machine so we can work on the module.

View File

@ -0,0 +1,25 @@
+++
title = "Local Project Setup"
date = 2024-08-23T09:00:00Z
draft = false
summary="Learning Foundry VTT Module Development from the very start. In this session: setting up the local project."
categories = ['Technical', 'FoundryVTT', 'Foundry VTT for Module Developers']
prev = ['/post/fvtt-mod-dev-github-repository-setup/']
+++
Having cloned our Github repository to our local development machine we now set up some basic tooling that will help later as we develop our module.
{{< youtube 8Qm0XJSWqYU >}}
In this session we set up:
* [`npm`](https://www.npmjs.com/), initialising our project.
* [`husky`](https://typicode.github.io/husky/) to marshal our `git` hook scripts.
* [`commitizen`](https://github.com/commitizen/cz-cli) to enforce standard `git` log messages.
These tools provide some 'guardrails' on our project that, although they may seem onerous now, will pay dividends later by facilitating:
* The production of consistent a changlog for our release notes (poviding users and other developers with timely and accurate details of what changes occur to our module).
* Management of our release versioning.
A few minutes of setup now will save hours over the life of our module.