Adding a line returns to list items and making events conditional on homepage

[jeremyzilar]

What was improved

• Unordered lists were not rendering on two page because there was not a space between the line of text above it and the start of the un-ordered list. This fix makes those unordered lists render properly.

  • About page Preview: https://federalist-proxy.app.cloud.gov/preview/gsa/digitalgov.gov/release-2.1.1/about/
  • User Experience Community of Practice Preview: https://federalist-proxy.app.cloud.gov/preview/gsa/digitalgov.gov/release-2.1.1/communities/user-experience/

• Made the events listing on the Homepage not appear if there are no events(Make the events listing on the Homepage conditional #169)

• Removed the contact page and all references to it and redirected it to the About page

• Added a Contact Us section to the About Page https://federalist-proxy.app.cloud.gov/preview/gsa/digitalgov.gov/release-2.1.1/about/

• making it clear that part of the event is online https://federalist-proxy.app.cloud.gov/preview/gsa/digitalgov.gov/release-2.1.1/event/workshop-making-government-websites-with-github-federalist-us-web-design-standards/

• removed the event-type prefix from event titles https://federalist-proxy.app.cloud.gov/preview/gsa/digitalgov.gov/release-2.1.1/events/

[thisisdano]

So, I don't want this to be a big deal, but I'd consider some of these kinds of changes more like a sprint release or a content release change. The way I see it:

patch release *.*.# — fixes errors: typos, missing or incorrect content or formatting
content release *.#.0 — new content and content design: new posts, articles, and resources; non-error changes to content design
sprint release #.0.0 — new or fixed site functionality: new components, new formatting, non-error fixes, improvements

How does that strike you? There's no need to hold off on these changes over a versioning discussion, but going forward it might make sense to be more strict. If only to keep us from hotfixing all the time, and limiting that to only when it's really necessary. It's annoying and sometimes painful from holding back on improvements, but it might help our workflow and sanity?

• I don't have the time at this moment to check the conditional events, but it looks like it should work!
• Dunno the reasoning behind removing the event type from the title, maybe just spell the reason out in the notes, or point to an issue?
• Was there an issue behind removing the contact page? I'm sure it's fine to do it, but, as above, it could be helpful to have an issue as a documentation of reasoning

It may feel like I'm being a bit of a process stickler here, and I guess I am a bit. But the process is the product to some degree here.

[dailybreade03]

• [@]()

[dailybreade03]

• -