Statecharts are an accepted and compelling standard for modeling application logic and behavior in a deterministic manner. State machines and statecharts increase productivity while reducing bugs. In this workshop you'll learn about state machines and statecharts, and practical applications of them with React.
We will cover topics such as visualizing application logic, locating problematic edge cases, constructing features, and auto-generating tests.
The crux of this site is are the lessons. Provided are two examples. Each lesson needs a frontmattter path, order, and title. Generally you should make the path and the file name match for ease of finding it.
path- needs a leading slash. This will be slug of the lessontitle- will be the title displayed on the Table of Contents and on the page itselforder- the order of which the item should appear in the table of contents. The first item should be of order0. The second should be1, etc. Must be numbered sequentially, i.e. don't skip numbers.
Inside of gatsby-config.js be sure to fill out the siteMetadata fields, including title, subtitle, description, and keywords.
If you do want to deploy to GitHub pages, make sure you add the name of the repo to the pathPrefix property in gatsby-config.js so that it will correctly make all the links.
This site is ready to deployed to GitHub Pages out of the box with GitHub Actions. If you do not want to deploy this to GitHub Pages, delete the .github directory.
If you do want to deploy this to GitHub Pages with GitHub Actions, you need to do a few things.
- Create a personal access token with rights to read and write to repos.
- Put that token in your repos secrets. Click the Settings tab and paste your access token in the Secrets tab with the key
ACCESS_TOKEN. - Now once you commit your code, it should automatically deploy your GitHub Pages site should deploy automatically!
- This repo itself
- Complete Intro to Containers
- Complete Intro to React v5
- Complete Intro to Web Dev v2
- Four Semesters of Computer Science in Five Hours Part II
The code is this repo is licensed under the Apache 2.0 license.
I include the CC-BY-NC-4.0 license for the content; this is what I recommend you license your content under: anyone can use and share the content but they cannot sell it; only you can.