I created a PanelPOMP website that is automatically generated using GitHub Actions. Specifically, the action found in the file: .github/workflows/render-website.
One of the goals that I had in the development of this website is that it should be automatically synced with the package in the GitHub repository: any changes to the package that are pushed the cbreto/panelPomp should automatically be incorporated into the website without the need to run any additional code.
The code to generate the website is largely based on code Aaron King uses to generate the website for the pomp website. The primary differences being:
The proposed panelPomp website uses a tool called Quarto to generate the website rather than jekyll. This allows for some easy theming options that make the panelPomp website look somewhat modern.
The panelPomp website is created entirely using GitHub actions, instead of using makefiles like the pomp package. These two approaches serve similar purposes, but relying on GitHub actions exclusively means that the website is entirely self contained and does not require rendering the website locally.
I created a PanelPOMP website that is automatically generated using GitHub Actions. Specifically, the action found in the file:
.github/workflows/render-website
.One of the goals that I had in the development of this website is that it should be automatically synced with the package in the GitHub repository: any changes to the package that are pushed the
cbreto/panelPomp
should automatically be incorporated into the website without the need to run any additional code.The code to generate the website is largely based on code Aaron King uses to generate the website for the
pomp
website. The primary differences being:panelPomp
website uses a tool calledQuarto
to generate the website rather thanjekyll
. This allows for some easy theming options that make thepanelPomp
website look somewhat modern.panelPomp
website is created entirely using GitHub actions, instead of using makefiles like thepomp
package. These two approaches serve similar purposes, but relying on GitHub actions exclusively means that the website is entirely self contained and does not require rendering the website locally.