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

refactor: content and organization for RADIUSS 2024 #38

Merged
merged 1 commit into from
Jul 5, 2024

Conversation

vsoch
Copy link
Member

@vsoch vsoch commented Jul 5, 2024

I am starting preliminary changes for RADIUSS 2024. So far:

  • the launcher is fixed to load the tutorials via buttons
  • I am moving "core" flux tutorial content separate from what we can consider external or plugins, like dyad. The reason is because these are experimental and change from year to year, and having it alongside core content makes a promise about consistency that I am not sure we can keep. I have not done this yet, but I am going to separate the files (images and notebooks) cleanly as well.
  • top level: everything is there for the tutorial user when the notebook opens, no need to navigate into many sub- directories.
  • terminal button: instead of "click this long list of annoying paths to open a terminal" I figured out how to make a button in the notebook directly.
  • marginal content changes: I am starting to tweak / update content, this will be a multi-step process.

I made a new branch only to compare the upstream here with what I have locally - I don't need approval to merge this (and will merge into the previous WIP branch for radiuss 2024 AWS to continue working, and will add these notes). I think there will be merge conflicts I will need to address, and I want to do those sooner than later.

I am starting preliminary changes for RADIUSS 2024. So far:
- the launcher is fixed to load the tutorials via buttons
- I am moving "core" flux tutorial content separate from
  what we can consider external or plugins, like dyad. The
  reason is because these are experimental and change from
  year to year, and having it alongside core content makes
  a promise about consistency that I am not sure we can
  keep. I have not done this yet, but I am going to separate
  the files (images and notebooks) cleanly as well.
- top level: everything is there for the tutorial user when
  the notebook opens, no need to navigate into many sub-
  directories.
- terminal button: instead of "click this long list of
  annoying paths to open a terminal" I figured out how to
  make a button in the notebook directly.
- marginal content changes: I am starting to tweak / update
  content, this will be a multi-step process.

Signed-off-by: vsoch <vsoch@users.noreply.github.com>
@vsoch vsoch merged commit 0953704 into 2024-radiuss-aws Jul 5, 2024
0 of 6 checks passed
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.

1 participant