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
Status and Updates too wordy #12
Comments
Agree with Shadi on the first point here. If I see that there was a new 'last updated' date since I last visited, I would have no idea of what content was last updated. It would be nice to know if a specific country or state/province was updated, and would be more relevant to what information I am looking for. Maybe the paragraph could work better this way:
|
Agree to delete "This page was updated on 03 Feb 2017 and will be updated on a regular basis as new information is received." See also #7 |
You can make edits to the texts here: https://github.com/w3c/wai-policies-prototype/tree/gh-pages/_help |
@nitedog I’ll put your point number 2 into a separate issue so it is easier to follow. |
+1 for the shortest, most straightforward wording possible. The last updated date could be dynamically generated based on the last update to the document. No maintenance required. |
To clarify, this is about the Status and Updates section at the top of the page since update information will be throughout the page. Remove that section, and simply have a button/link to submit updates somewhere toward the top of the page. See tools page for info for ideas on where to put the button, and potentially have a way to request to update existing entries where the submission form is pre-loaded with today's info to update. |
Discussion in 10 Feb telecon |
The status and updates part has been edited to shorten it significantly. The headings are going to be collapsed into one heading with the pertinent information for the page which is being tracked with issue #13 and the addition of a working submission button is being tracked with issue #18. I'll copy over comments about potentially having a submit updates button on individual country parts to pre-fill the submission form into Issue #18 to keep these issues more distinct. |
The text was updated successfully, but these errors were encountered: