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

Preferred Way to Add Supplementary Information to Proceedings #909

Open
hp2500 opened this issue May 29, 2024 · 3 comments
Open

Preferred Way to Add Supplementary Information to Proceedings #909

hp2500 opened this issue May 29, 2024 · 3 comments

Comments

@hp2500
Copy link
Contributor

hp2500 commented May 29, 2024

Hi there,

I am wondering what would be the preferred way to add supplementary information to the proceedings. Should we upload them to a separate repo and just provide the link, or should we add them as a section to the proceedings template?
Your guidance would be much appreciated.

All the best,
Heinrich

@rowanc1
Copy link
Contributor

rowanc1 commented May 29, 2024

Thanks @hp2500, excited about your submission!

What is the form of your supplementary materials (e.g. notebook, latex doc, code, data?), I think that the answer will depend a bit on what that looks like!

@hp2500
Copy link
Contributor Author

hp2500 commented May 29, 2024

Thanks for the quick response @rowanc1 ! It's 4 larger images of GUIs with some explanations and a collection of links taking readers to documentation and tutorial notebooks. Not more than a few pages overall.

@rowanc1
Copy link
Contributor

rowanc1 commented May 29, 2024

I am getting some consensus from the other proceeding chairs on what we are aiming to support this year. The mystmd client does support supporting documents very easily (just add a new markdown page and it will be added under the document outline), and it sounds like that would fit your needs.

We will get back to you very soon with an official direction!

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

2 participants