You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 15, 2020. It is now read-only.
I've been slowly making my way through the new visual guide and related assets. At West Virginia University we have a similar project though not nearly as robust as the current visual guide. The frontend guide is really interesting. It almost reads as a spec but not quite. Are there plans to follow the RFC 2119 wording to make the document a little clearer? If you've considered it but decided against using it could you share the reasoning?
Thanks much for the inspiration.
The text was updated successfully, but these errors were encountered:
Hi @dmolsen, thanks so much for you're interest. When most of this content was written, it was a little unclear in how it would evolve, so we picked language that we were most comfortable with. RFC 2119 does look interesting and seems like it could potentially improve clarity. That being said, we have an internal content team here that reviews any web content we publish to ensure it maintains a consistent and accessible tone. We generally follow their guidance on how to write our content. I think I'll pass on your recommendation to them to see what they think.
I've been slowly making my way through the new visual guide and related assets. At West Virginia University we have a similar project though not nearly as robust as the current visual guide. The frontend guide is really interesting. It almost reads as a spec but not quite. Are there plans to follow the RFC 2119 wording to make the document a little clearer? If you've considered it but decided against using it could you share the reasoning?
Thanks much for the inspiration.
The text was updated successfully, but these errors were encountered: