To reduce manual StackEdit exports and associated limitation, and to avoid storing the HTML within this repository, this should be scrapped and turned into a CI/CD pipeline that renders the HTML and builds the static asset based on the markdown in this repository.
To do this, the code from within StackEdit that renders the HTML will have to be used and customised to run this via a GitHub pipeline. This ensures that new contributions will only require an edit to the markdown content, as opposed to a manual copy and export from within the StackEdit editor.
To reduce manual StackEdit exports and associated limitation, and to avoid storing the HTML within this repository, this should be scrapped and turned into a CI/CD pipeline that renders the HTML and builds the static asset based on the markdown in this repository.
To do this, the code from within StackEdit that renders the HTML will have to be used and customised to run this via a GitHub pipeline. This ensures that new contributions will only require an edit to the markdown content, as opposed to a manual copy and export from within the StackEdit editor.