Unfortunately, good code won't speak for itself. Even the most elegantly designed and well-written codebase that solves the most pressing problem in the world won't just get adopted on its own. You, the open source creator, need to speak for your code and breathe life into your creation. That's where technical writing and documentation come in. A project's documentation gets the most amount of traffic, by far. It's the place where people decide whether to continue learning about your project or move on. Thus, spending time and energy on documentation and technical writing, focusing on the most important section, "Getting Started," will do wonders for your project's traction.
technical information
See the following -
Catalonia releases RFI on technology elements to build an open platform using openEHR ~ ECHAlliance
Press Release |
European Connected Health Alliance (ECHAlliance) |
July 15, 2021
The region of Catalonia has launched today a Request for Information (RFI) with the purpose to obtain technical information on the possibilities of supplying the elements of a technological platform for the development of the Electronic Health Record of Catalonia. Given the technical complexity of the technological platform for the development of the Electronic Health Record and the need to finish defining its design and the components of the platform to be tendered, as well as to inform the economic operators active in the market of the need that has arisen...
- Login to post comments
How To Write Effective Documentation For Your Open Source Project
By Kevin Xu | March 12, 2020