OpenMRS’ mission is to improve healthcare delivery in resource-constrained environments by coordinating a global community that creates and sustains a robust, scalable open-source medical record platform.
The OpenMRS Community is currently undergoing a renaissance, with smaller groups of community members driving new and exciting projects forward in response to user needs. The opportunities to make meaningful contributions to our community have never been better. Our current getting started guide does not include the additional information newcomers need in order to begin working on any of these new projects. Our community is in need of a suite of Getting Started Guides that share a consistent format and style.
We are currently seeking an experienced Technical Writer to work hand in hand with our community developers, Documentation Team, and documentation fellows to:
- Create a documentation toolkit for writing smart Getting Started Guides, including a template and sample guide.
- Provide guidance and mentorship to documentation fellows on using the toolkit to create additional Getting Started Guides
This is a part-time position for 5 months, beginning in mid-May, and is eligible to receive a monthly stipend.
Potential, priority Getting Started Guides identified by the community include:
Getting Started with 3.0: How to Develop with Microfrontends and Carbon
Getting Started with OpenMRS Upgrades
Getting Started with Quality Assurance
Getting Started with FHIR
Getting Started with OCL for OpenMRS
This project will assist our community to sustainably develop and maintain documentation that supports an easy and friendly environment for those who join and are interested in contributing to this community as they get started contributing to the different areas of software development and quality assurance.
- Create documentation guidance and templates in the form of a “Getting Started Guide” Toolkit, including a sample guide.
- Research, write, edit and revise content that is both engaging and accessible to target audiences.
- Publish templates for written documentation produced by others (technical writers in training), ensuring a consistent “look and feel.”
- Collaborate with relevant community squads and teams, including those focused on specific development projects, quality assurance, and documentation.
- Test processes and guides for issues, provide insight to resolving problems and ensure documentation is accurate and consistent.
- Mentor up to two community documentation fellows on using the Getting Started Guide Toolkit to create new Getting Started Guides. This may be accomplished through paired working sessions, reviewing/editing draft getting started guides for consistency and continuously updating content with current information.
- Maintain a tracking and ticketing system to ensure deadlines are met and deliverables are received on time.
For specific project activities and timeline, please see the full project description on our WIki.
Bachelor’s degree or the equivalent in experience in English, Communication, Journalism, Software Engineering, Computer Science, Technical Writing, Teaching, Curriculum Development or Scientific Publication.
2-3 years experience in technical writing.
Strong communications skills, including written, verbal and presentation.
Excellent attention to detail and the ability to prioritize and work on multiple projects
Ability to communicate complex technical topics to non-technical stakeholders both internally and externally.
Prior experience working with open source communities
Experience mentoring aspiring technical writers preferred
Please submit a statement of interest, including links to your CV and technical writing samples, that addresses the responsibilities and skills outlined above. Share your availability for an informational interview using this Doodle poll.
Please send this information or your questions to email@example.com.
Applications are due on May 7, 2021. Priority will be given to candidates submitting their application by May 3, 2021.