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

build html and pdf for repo/official releases #27

Open
2 tasks done
soerenthomsen opened this issue Nov 3, 2021 · 7 comments
Open
2 tasks done

build html and pdf for repo/official releases #27

soerenthomsen opened this issue Nov 3, 2021 · 7 comments
Assignees

Comments

@soerenthomsen
Copy link
Member

soerenthomsen commented Nov 3, 2021

I suggest we try to do this before Julius is back mid November.

If I understand correctly we can deploy locally via GitHub actions as

  • html
  • pdf

The later would be nice as so far we miss this in the oxygen SOP. At the moment the user can only create a pdf of the single sections on the jupyter book deployment.

@soerenthomsen
Copy link
Member Author

This worked on @isgiddy local machine. We still aim to produce a html and pdf file into the repo!

@soerenthomsen soerenthomsen changed the title Deploy Jupyter book locally build html and pdf for repo/official releases Nov 4, 2021
@soerenthomsen
Copy link
Member Author

@isgiddy do you want to set this also up for the GitHub repo? Would be nice to also have a full pdf build in the repo.

@soerenthomsen
Copy link
Member Author

As discussed yesterday with Julius we will wait with this pdf generation until the community review is done to avoid multiple versions circulating. Only if community members explicitly ask for a full pdf we will create it. @isgiddy i also suggest to remove the outdated pdf from the repo again.

Like this we will ensure that the most recent version is commented on. And people can generate their chapters on the jupiter book.

When we close the community review we will generate pdf etc together with releases and doi's.

So we could include a pdf builder into the action just to test it but disable for now.

@jbusecke
Copy link
Member

I dont anticipate a lot of friction to build this (famous last words haha), so I would opt to integrate this closer to the end of the review process. Could you remind me about the proposed date?

@soerenthomsen
Copy link
Member Author

The official community review process will end February 2022 for this SOP but already end of January 2022 for the oxygen SOP. I suggest we start with the Oxygen SOP and do this mid January.

@jbusecke
Copy link
Member

Sounds great. If you could ping me here a week earlier, Id be happy to get back on this.

@soerenthomsen
Copy link
Member Author

As we solved this for the oxygen SOP and just need to redo it.

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