discussion

README.md

@@ -8,11 +8,19 @@
 
 ## Manuscript description
 
-<!-- usage note: edit this section. -->
-
 This is an updated manuscript for the BrAPI Project and Community. The [first BrAPI paper](https://academic.oup.com/bioinformatics/advance-article/doi/10.1093/bioinformatics/btz190/5418796)
 was focused on the technical aspects of BrAPI and its potential. This manuscript gives us an opportunity to report on the project success so far and show how that potential has become a reality.
 
+## How to contribute
+
+Everyone in the BrAPI Community is welcome and encouraged to contribute to this manuscript! You can contribute in any of the following ways:
+
+1. Checkout this repository, make edits directly, and submit a pull request.
+2. Create an [ISSUE](https://github.com/plantbreeding/BrAPI-Manuscript2/issues/new) with your edits.
+3. Send edits directly to @BrapiCoordinatorSelby via [email](mailto:[email protected]) or [Slack](https://plantbreedingapi.slack.com).
+
+If you would like to be recognized as a co-author, please add your details to the file [/content/metadata.yaml](https://github.com/plantbreeding/BrAPI-Manuscript2/blob/main/content/metadata.yaml). Again you can do this with a pull request, and issue, or by contacting @BrapiCoordinatorSelby directly. 
+
 ## Helpful Links
 
 + [Manuscript Content Folder](content)

content/04.discussion.md

@@ -5,11 +5,15 @@
 * Analytics
 * HDP
 * GraphQL?
-* Field mgmt - treatments etc
+* Field management - treatments etc
 * Drones, image processing, HTP
 * ChatGPT integration - BreedersGPT
 * Weather & soil - why it won’t be in BrAPI -->
 
 ### BrAPI for Breeders and Scientists
 
-The BrAPI technical specification document is meant to be read and used by software developers. However, the purpose of the specification, and the community around it, is to make things faster, easier, and cheaper for the breeders and scientists working to make the world a better place. BrAPI offers a convenient path to automation and data integration for software tools in the breeding domain. All of the example use cases described above can be achieved with manual effort, moving and editing data files by hand. When the basic structure anf flow of data becomes automated, breeders and scientists can spend more time focussing on the science and doing what they do best. For many, the ultimate goal is the development of a digital ecosystem: a collection of software tools and applications that can all work together seamlessly. In this digital ecosystem, data is collected digitally from the beginning, reducing as much human error as possible. The data is checked by quality control and stored automatically, then can be sent to any internal tool or external lab for further analysis with just the click of a button. 
+The BrAPI technical specification document is meant to be read and used by software developers. However, the purpose of the specification, and the community around it, is to make things faster, easier, and cheaper for the breeders and scientists working to make the world a better place. BrAPI offers a convenient path to automation and data integration for software tools in the breeding domain. All of the example use cases described above can be achieved with manual effort, moving and editing data files by hand. When the basic structure and flow of data becomes automated, breeders and scientists can spend more time focussing on the science and doing what they do best. For many, the ultimate goal is the development of a digital ecosystem: a collection of software tools and applications that can all work together seamlessly. In this digital ecosystem, data is collected digitally from the beginning, reducing as much human error as possible. The data is checked by quality control and stored automatically, then can be sent to any internal tool or external lab for further analysis with just the click of a button. This idea might sound too good to be true, but as more tools start sharing a universal data standard, automating data flow becomes easier, and the community gets closer to total interoperability. 
+
+### Looking Ahead
+
+The BrAPI specification will continue to grow, enabling more use cases and new types of data. 

content/metadata.yaml

@@ -1,10 +1,12 @@
 ---
-title: "BrAPI 2"
+title: "BrAPI Success Stories"
 date: null  # Defaults to date generated, but can specify like '2022-10-31'.
 keywords:
-  - markdown
-  - publishing
-  - manubot
+  - brapi
+  - breeding
+  - api
+  - standards
+  - community
 lang: en-US
 authors:
   - github: BrapiCoordinatorSelby