Conform with distill.pub build process
Closed this issue · 5 comments
In b8d8a15 I have committed all of our source code and build system.
We now need to make some smaller changes to our build process. Distill.pub requires a public/ folder that contains the bundled version of our article. We have a similar folder already (docs/), which we need for hosting the article on Github Pages (we used this link to share the article as a pre-print).
It should be sufficient to do this as the last step of the process when we transfer the ownership to distill.pub as well.
I'd love to complete this step and move the repository to Distill, but I'm really not sure—it now looks as though there are two copies of build results checked in, and I can't identify the source—so I'm likely wrong about one of them being a build result! :D
Which folder currently contains your ground-truth source document?
(We need to add certain values such as meta tags in our won build process so we can extract the same data for additional indexing purposes such as crossref citations.)
The following file is the original source: dist/index.html.
The docs/ folder is populated by running npm run deploy. The reason for this duplications was that Github Pages only works from either the master branch or the docs/ folder.
My strategy would be to rename dist/ to public/ in accordance with the distill.pub build process and delete docs/ folder, including the npm run deploy script. I can make a quick PR for this.
Oh and by the way, I have transferred the ownership of this repository to the distillpub Github organization.
@grtlr Your proposed strategy sounds perfect. I'd appreciate the PR!