[Issue 514] Remove NOFO content from static site milestone

[widal001]

Summary

Updates milestone docs to remove NOFO content and target release date attribute

Fixes #514

Time to review: 3 mins

Changes proposed

What was added, updated, or removed in this PR.

• Removes references to NOFO transformation workstream from milestone doc
• Removes "target release date" row from milestone doc metadata
• Updates template to include metadata that is consistent across milestone docs

Context for reviewers

Testing instructions, background context, more in-depth details of the implementation, and anything else you'd like to call out or ask reviewers. Explain how the changes were verified.

It may be easier to view the rendered versions of the docs to review

Additional information

Screenshots, GIF demos, code examples or output to help show the changes working as expected.

[andycochran]

Not asking for a change here but wanted to note a PROTIP:

To create an ordered list, add line items with numbers followed by periods. The numbers don’t have to be in numerical order, but the list should start with the number one.

So you can do this:

1. First item
1. Second item
1. Third item
1. Fourth item

…and it'll render like this:

1. First item
2. Second item
3. Third item
4. Fourth item

…then you don't have to worry about setting the right number.

Aside: This reminds me of an article I just read about "a single HTML tag (ordered lists) and end with the downfall of civilization."

[andycochran]

I suppose all 1s is less helpful when viewing a document as code (not rendered markdown).

[widal001]

@andycochran This is a good tip to limit unnecessary diffs!

Currently I use Markdown All in One as my VSCode extension for formatting Markdown, which automates the process of updating numbers in ordered lists, so (fortunately) I'm not manually reordering these myself. Still it is a pain to see the diffs on lines that didn't actually result in content changes.

I'll have to check if that VSCode extension supports configuring ordered lists to only use 1. like you mentioned. Do you use a different markdown extension for VSCode?

[widal001]

Also that article is a wild ride, but I love it!! I could feel the computational law recesses of my brain itching as I was reading it 😅

[andycochran]

Ooh! I'll check out the Markdown All in One extension. I'm new to VS Code, was an Atom (R.I.P.) user until this project.

[widal001]

Same!! Atom was so great, I'm still salty they sunsetted it. And Atom did have a great Markdown plugin that followed the 1. only style for ordered lists