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

Restructuring the website #32

Merged
merged 8 commits into from
Aug 18, 2023
Merged

Restructuring the website #32

merged 8 commits into from
Aug 18, 2023

Conversation

NoraLoose
Copy link
Contributor

@NoraLoose NoraLoose commented Aug 18, 2023

Closes #15.

To reiterate, this PR mainly

  • breaks the website into several pages
  • includes the demo notebooks

EDIT:
Next steps:

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@NoraLoose if fig_1.png is now in website/ maybe we can delete it from the repo root? (IIUC the copy there now is a duplicate?)

Copy link
Contributor Author

@NoraLoose NoraLoose Aug 18, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should include website/fig_1.png in the .gitignore.

As of now, both the README and fig_1.png are copied to website/ by GitHub actions before the website is built. That is because you can't include files in the website that live outside the website/ directory. Copying only README over would lead to conflicting paths for where to find the figure (for showing the README vs. building the website).

Maybe a cleaner solution would be to have separate markdown files in website/ (which break up the README into sections).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copying only README over would lead to conflicting paths for where to find the figure (for showing the README vs. building the website)

haha 🤯 yikes yeah I see your point there

@NoraLoose
Copy link
Contributor Author

NoraLoose commented Aug 18, 2023

I have set the execution of notebooks is set to 'off', see website/_config.yml:

execute:
  execute_notebooks         : off  # Whether to execute notebooks at build time. Must be one of ("auto", "force", "cache", "off")

If we want to execute the notebooks at build time, we have to include a lot more packages in website/environment.yml. Also, the notebooks would probably take a long time to run, right? @cisaacstern @jerrylin96

@cisaacstern
Copy link
Contributor

cisaacstern commented Aug 18, 2023

I have set the execution of notebooks is set to 'off',

I think this is the right call for now. Eventually, it would be great to run the notebooks automatically to ensure reproducibility, but that's too heavy a lift for now IMO. I'll open a separate issue to track that. Edit: tracking this in #33

@cisaacstern cisaacstern mentioned this pull request Aug 18, 2023
2 tasks
@jerrylin96 jerrylin96 merged commit eae253f into leap-stc:main Aug 18, 2023
1 check passed
@NoraLoose NoraLoose mentioned this pull request Aug 18, 2023
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

Successfully merging this pull request may close these issues.

Restructure website
3 participants