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

Tracking issue for 2i2c using MyST to generate a report #1002

Closed
9 of 17 tasks
choldgraf opened this issue Mar 18, 2024 · 1 comment
Closed
9 of 17 tasks

Tracking issue for 2i2c using MyST to generate a report #1002

choldgraf opened this issue Mar 18, 2024 · 1 comment

Comments

@choldgraf
Copy link
Collaborator

choldgraf commented Mar 18, 2024

We decided to use the new MyST build engine to create a three-year CZI report and retrospective, hosted at the following link:

https://2i2c.org/report-czi-2021

This is a tracking issue for the things that came up during that effort. I'm putting it into this style of an issue in order to track a pattern we hope to follow more times, which is to:

  1. Work with a community to convert their Jupyter Book content into MyST
  2. Identify the confusion points, missing functionality, etc and track them as issues for development
  3. Resolve the issues and then re-deploy to the new book

Issues uncovered

Documentation

Myst website issues

@agoose77
Copy link
Contributor

agoose77 commented May 7, 2024

As per a discussion with Chris, we're closing this in favour of new initiatives!

@agoose77 agoose77 closed this as completed May 7, 2024
@agoose77 agoose77 reopened this May 7, 2024
@agoose77 agoose77 closed this as not planned Won't fix, can't repro, duplicate, stale May 7, 2024
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