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

Outbound Checklists: Convert from PDF to Markdown #147

Closed
4 tasks done
natalialuzuriaga opened this issue Sep 5, 2024 · 8 comments
Closed
4 tasks done

Outbound Checklists: Convert from PDF to Markdown #147

natalialuzuriaga opened this issue Sep 5, 2024 · 8 comments
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request summer2024 Tickets for Coding It Forward Summer 2024 Interns

Comments

@natalialuzuriaga
Copy link
Collaborator

MENTOR

  • @natalialuzuriaga
  • SWE Fellow, USDigitalCorps
  • dm on slack, #wg-government on CHAOSS.community slack,

BRIEF DESCRIPTION

Currently, all our outbound checklists are in a pdf format. We would like to have a markdown file of it on the repository for easy access and to be able to reference to specific sections

SCOPING

  • 1 week

SKILLS NEEDED

Markdown, Git/GitHub

REQUIRED DELIVERABLES

DESIRED DELIVERY WINDOW

  • Before Sept 16

NOTES/INSPO

Any feedback and ideas on this issue are welcome!

ACKNOWLEDGEMENTS

  • - Yes, I agree to spend file a project proposal ticket
  • - Yes, I agree this project falls within a 2 week or less (ideally less) scope of time
  • - Yes, I agree to spend an hour per week of office hours and 1x1 mentoring
  • - Yes, I agree to spend an hour at the end of the sprint for filling out a Retro Template
@natalialuzuriaga natalialuzuriaga added documentation Improvements or additions to documentation enhancement New feature or request summer2024 Tickets for Coding It Forward Summer 2024 Interns labels Sep 5, 2024
@natalialuzuriaga
Copy link
Collaborator Author

09/16:
Hack Sesh complete ✅

Next steps:

Hey @g5t3, let's start off with focusing on the Tier 1 checklist.
First, let's create the markdown file for the Tier 1 checklist. In the tier1 folder/directory, create a new file called checklist.md
In checklist.md you can start writing the markdown code in there.

Let me know if you have any questions as you work on this!

It is probably best to start off with the "Code Review" section (page 4). Some pages are more complex than others so if you get stuck and I'm taking too long to help/respond to you, feel free to jump around and do other sections.

Important links:
Ticket on the project board: #147
Tier 1 PDF on repo: https://github.com/DSACMS/repo-scaffolder/blob/main/tier1/checklist.pdf
Tier 1 Checklist Google Doc: https://docs.google.com/document/d/1EwjLpAOChNLLHSAnXdHQCtzcrcsdqsf1WcS_ZjNDClQ/edit#heading=h.slv8bucc4nti

@IsaacMilarky
Copy link
Collaborator

9/30:

@IsaacMilarky
Copy link
Collaborator

10/4:

  • Some feedback from @IsaacMilarky and @natalialuzuriaga
  • Will work on and hopefully fix soon
  • Should not have too much trouble for tiers 2 and 4
  • Will have tier 3 done by today
  • Some minor link issues and grammar stuff

@natalialuzuriaga
Copy link
Collaborator Author

10/07:

  • Keni has completed the Tier 3 checklist conversion
  • Working on Tier 2 and Tier 4

@IsaacMilarky
Copy link
Collaborator

10/11:

  • Tier 2 should be in by EoD today will send a PR
  • Busy week this week

@IsaacMilarky
Copy link
Collaborator

10/15:

  • Markdown checklist for tier 2 is up in PR: Tier 2 checklist markdown #178
  • Needs some minor changes due to 2 broken links (one for code.gov and one for cms.github.gov)
  • Overall great work !

@decause-gov
Copy link
Contributor

10/21:

@decause-gov
Copy link
Contributor

10/25:

  • All PRs have been Merged!!!
  • Congrats @NoobNoob06 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request summer2024 Tickets for Coding It Forward Summer 2024 Interns
Development

No branches or pull requests

5 participants