Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy built DOCX to Github pages #471

Open
habi opened this issue Jul 7, 2022 · 4 comments
Open

Deploy built DOCX to Github pages #471

habi opened this issue Jul 7, 2022 · 4 comments

Comments

@habi
Copy link

habi commented Jul 7, 2022

I've started a new manuscript and think I need an easily accessible DOCX file for the co-authors.
The DOCX file is built correctly, but not accessible at https://habi.github.io/EAWAG-manuscript/manuscript.docx as I would expect.
How can I deploy/copy the DOCX file to GitHub pages to make it easily accessible for my co-authors?

@agitter
Copy link
Member

agitter commented Jul 7, 2022

That has to do with the deploy script. The current behavior is to commit the files written in the output directory to the output branch, which includes the docx file, and to commit the files written to the webpage directory to the gh-pages branch, which does not include the docx file.

You could probably modify deploy.sh to copy the docx output file into the webpage directory before this command makes the commit to the gh-pages branch:

ghp-import \
  --no-jekyll \
  --follow-links \
  --push \
  --branch=gh-pages \
  --message="$MESSAGE" \
  webpage

If you want to try doing that, I can give more detail. It should even be possible to track the versions of the docx file in the versioned GitHub pages URLs.

@dhimmel
Copy link
Member

dhimmel commented Jul 8, 2022

Noting that the DOCX is getting saved to the output branch, so if you are okay with a URL like https://github.com/habi/EAWAG-manuscript/raw/output/manuscript.docx that might be all you need.

@agitter
Copy link
Member

agitter commented Jul 8, 2022

Maybe adding a link from the manuscript front matter to that output branch URL would be a quick solution? It's much easier than modifying the deploy script.

@habi
Copy link
Author

habi commented Jul 9, 2022

I'll try to fiddle with the deploy script, but having a link to the output branch is a quick and easy solution, yeah!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants