Change the discussion and home pages following the discontinuation …

…of `discuss` issues (#541)

Sundry updates to make the website friendlier

discussion.md

@@ -3,47 +3,52 @@ layout: default
 title: Discussion
 group: "navigation"
 ---
-
 # Discussion
 
-CF is carrying out a trial (beginning in March 2024) of using the CF [GitHub organization Discussions][github_discussions] for announcements relevant to CF, community discussion of comments and ideas for changing CF, and for questions and answers about how to use CF.
+CF discussions and decisions are mostly made on [GitHub][github]. No registration with CF is required to contribute; all that is needed is a freely available GitHub account.
 
-Announcements, discussions and Q&A that were initiated _before_ the trial of CF GitHub Discussions began are continuing as [GitHub issues][github_issues] in the [`discuss` repository][github_discuss]. (These might later be moved to GitHub Discussions if the trial is successful.)
-
-Proposals for changing CF are discussed as [GitHub issues][github_issues] in three repositories:
+### Questions, comments and announcements about CF
 
-*   [Vocabulary][github_vocabularies]
+In CF [GitHub organization Discussions][github_discussions] you can [ask a question](https://github.com/orgs/cf-convention/discussions/new?category=q-a-about-using-cf) about how to use CF, [comment](https://github.com/orgs/cf-convention/discussions/new?category=comments-and-ideas-for-changing-cf) on any aspect of CF or make a suggestion how CF could be changed or improved, contribute to any of the ongoing discussions, and read the previous ones. Announcements about CF are made there as well.
 
-    For proposing additions or amendments to standard names, their definitions, or other CF controlled vocabulary (area types and standardized regions).
+To keep up-to-date with announcements and discussions, go to the [`discuss` repository][github_discuss] and enable notifications from the <svg aria-hidden="true" height="16" version="1.1" width="16" data-view-component="true" class="octicon octicon-eye"><path d="M8 2c1.981 0 3.671.992 4.933 2.078 1.27 1.091 2.187 2.345 2.637 3.023a1.62 1.62 0 0 1 0 1.798c-.45.678-1.367 1.932-2.637 3.023C11.67 13.008 9.981 14 8 14c-1.981 0-3.671-.992-4.933-2.078C1.797 10.83.88 9.576.43 8.898a1.62 1.62 0 0 1 0-1.798c.45-.677 1.367-1.931 2.637-3.022C4.33 2.992 6.019 2 8 2ZM1.679 7.932a.12.12 0 0 0 0 .136c.411.622 1.241 1.75 2.366 2.717C5.176 11.758 6.527 12.5 8 12.5c1.473 0 2.825-.742 3.955-1.715 1.124-.967 1.954-2.096 2.366-2.717a.12.12 0 0 0 0-.136c-.412-.621-1.242-1.75-2.366-2.717C10.824 4.242 9.473 3.5 8 3.5c-1.473 0-2.825.742-3.955 1.715-1.124.967-1.954 2.096-2.366 2.717ZM8 10a2 2 0 1 1-.001-3.999A2 2 0 0 1 8 10Z"></path>
+</svg>&nbsp;<b>Watch</b> drop-down menu.
 
-    As well as in GitHub issues, the status of proposals about standard names is shown by the [CEDA vocabulary editor][vocab_editor]. To see a list of resolved proposals (accepted or rejected) for standard names from March 2011 onwards, click "Inactive" in the [CEDA vocabulary editor][vocab_editor]
-
-*   [Conventions][github_conventions]
+Discussions by category: &#x2753;&nbsp;[Questions and answers about using CF][github_qa]&nbsp;&nbsp;&#x1F4AC;&nbsp;[Comments and ideas for changing CF][github_comment]&nbsp;&nbsp;&#x1F4E3;&nbsp;[Announcements relevant to CF][github_announce]
 
-    For proposing enhancements and reporting defects in the CF conventions.
+### Proposals to change CF
+
+Proposals to change CF are made, debated and decided as [GitHub issues][github_issues] in three repositories:
 
-    Closed issues: [change agreed][github_conventions_change], [agreement not to change][github_conventions_nochange], [dormant][github_conventions_dormant] i.e. the discussion on a proposed change did not reach a conclusion. Dormant issues may be reopened if there is a new impetus or ideas that might help bring about an agreement.
+*   [Vocabulary issues][github_vocabularies], in the [vocabularies repository](https://github.com/cf-convention/vocabularies), for proposing additions or amendments to standard names, their definitions, or other CF controlled vocabulary (area types and standardized regions). [Open a new issue](https://github.com/cf-convention/vocabularies/issues/new/choose). See also [closed vocabulary issues][github_vocabularies_closed].
 
-*   [Website and governance][github_website]
+    As well as in GitHub issues, the status of proposals about standard names is shown by the [CEDA vocabulary editor][vocab_editor]. To see a list of resolved proposals (accepted or rejected) for standard names from March 2011 onwards, click "Inactive" in the [CEDA vocabulary editor][vocab_editor].
+
+*   [Conventions issues][github_conventions], in the [conventions repository](https://github.com/cf-convention/cf-conventions), for proposing enhancements and reporting defects in the CF conventions. [Open a new issue](https://github.com/cf-convention/cf-conventions/issues/new/choose). See also [closed conventions issues][github_conventions_closed], classified by reason for closure: [change agreed][github_conventions_change]&nbsp;&bull;&nbsp;[agreement not to change][github_conventions_nochange]&nbsp;&bull;&nbsp;[dormant][github_conventions_dormant]. "Dormant" means the discussion on a proposed change did not reach a conclusion. Dormant issues may be reopened if there is a new impetus or ideas that might help bring about an agreement.
 
-    For discussing, proposing changes and reporting defects in the [CF website][website] or CF governance.
+*   [Website and governance issues][github_website], in the [website repository](https://github.com/cf-convention/cf-convention.github.io), for proposing changes and reporting defects in the [CF website][website] or CF governance. [Open a new issue](https://github.com/cf-convention/cf-convention.github.io/issues/new/choose).
 
-No registration with CF is required to contribute; all that is needed is a freely available [GitHub account][github].
+You can enable notifications of updates to issues for each kind of issue separately using the <b>Watch</b> menu in its repository.
 
 ### Archive links
 
-Before the CF community migrated to GitHub, general and standard-name discussion took place on the [cf-metadata mailing list][archives], and enhancements to the conventions were proposed on the [CF Metadata Trac](Data/trac.html) site.
+Announcements, discussions and Q&A that were initiated before CF GitHub Discussions began are continuing as GitHub issues in the `discuss` repository. They will soon be converted to GitHub Discussions.
+
+Before the CF community migrated to GitHub:
+
+* until December 2019, general discussion took place and standard names were proposed on the [cf-metadata mailing list][archives] ([original at NCAR][NCAR_archives]).
+
+* until July 2018, changes to the conventions were proposed on the [CF Metadata Trac][about] site.
 
-* cf-metadata mailing list archive [copy on GitHub][archives] or [original at NCAR][NCAR_archives] (until December 2019)
-* [CF Metadata Trac](Data/trac.html) (until July 2018)
-* [About CF Metadata Trac][about]
 
 [github_conventions]: https://github.com/cf-convention/cf-conventions/issues
+[github_conventions_closed]: https://github.com/cf-convention/cf-conventions/issues?q=is:issue+is:closed
 [github_conventions_change]: https://github.com/cf-convention/cf-conventions/issues?q=is:issue+label:"change agreed"
 [github_conventions_nochange]: https://github.com/cf-convention/cf-conventions/issues?q=is:issue+label:"agreement not to change"
 [github_conventions_dormant]: https://github.com/cf-convention/cf-conventions/issues?q=is:issue+label:dormant
 [github_discuss]: https://github.com/cf-convention/discuss/issues
 [github_vocabularies]: https://github.com/cf-convention/vocabularies/issues
+[github_vocabularies_closed]: https://github.com/cf-convention/vocabularies/issues?q=is:issue+is:closed
 [github_website]: https://github.com/cf-convention/cf-convention.github.io/issues
 [github]: https://github.com
 [website]: https://cfconventions.org
@@ -55,4 +60,8 @@ Before the CF community migrated to GitHub, general and standard-name discussion
 [current]: https://cfeditor.ceda.ac.uk/proposals/1
 [vocab_editor]: https://cfeditor.ceda.ac.uk/proposals/1
 [github_issues]: https://guides.github.com/features/issues
+
 [github_discussions]: https://github.com/orgs/cf-convention/discussions
+[github_qa]: https://github.com/orgs/cf-convention/discussions/categories/q-a-about-using-cf
+[github_comment]: https://github.com/orgs/cf-convention/discussions/categories/comments-and-ideas-for-changing-cf
+[github_announce]: https://github.com/orgs/cf-convention/discussions/categories/announcements-relevant-to-cf

index.md

@@ -12,14 +12,13 @@ The CF convention includes a standard name table, which defines strings that ide
 
 ---
 
-**_Conventions_:** **Latest release** (1.11) [HTML][releasedhtml] [PDF][releasedpdf]
-<code>&nbsp;&bull;&nbsp;</code>
+[**_Ask a question_ about how to use CF**&nbsp;&nbsp;&#x2753;][github_askq]
+
+**_Read the conventions_:** **Latest release** (1.11) [HTML][releasedhtml] [PDF][releasedpdf]&nbsp;&bull;&nbsp;
 **Working draft** [HTML][workinghtml] [PDF][workingpdf]
 
-**_Vocabularies_:** [**Standard names**][currentnames]
-<code>&nbsp;&bull;&nbsp;</code>
-[**Area types**][areatypes]
-<code>&nbsp;&bull;&nbsp;</code>
+**_Check the latest vocabularies_:** [**Standard names**][currentnames]&nbsp;&bull;&nbsp;
+[**Area types**][areatypes]&nbsp;&bull;&nbsp;
 [**Standardized regions**][regions]
 
 ---
@@ -66,3 +65,4 @@ See also the links in the navigation bar at the top of this page.
 [github_website]: https://github.com/cf-convention/cf-convention.github.io/issues
 [cf_github]: https://github.com/cf-convention
 [github_discussions]: https://github.com/orgs/cf-convention/discussions
+[github_askq]: https://github.com/orgs/cf-convention/discussions/new?category=q-a-about-using-cf