{'fraction_non_alphanumeric': 0.015544041450777202, 'fraction_numerical': 0.0, 'mean_word_length': 5.699421965317919, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Making Content Decisions between Open Source and Enterprise Versions of a Software Product

This case study shares how a cloud software development startup maintains both enterprise and open source content for its products by presenting its product and content strategy as a rubric to guide documentation decisions. The rubric is situated within the context of the company’s business objectives as well as within the concerns of the field, such as content strategy, usability, accessibility, and discoverability. The rubric is divided into three parts: decisions about the content itself, content operations for lifecycle maintenance, and content access. Practitioners can use the rubric to inform their content strategy across enterprise and open source documentation. Academics might find the rubric helpful as a teaching tool for content strategy courses. Together, practitioners and academics can collaborate on further research to understand how content strategy decisions between enterprise and open source technologies impact the community’s ability to use and innovate on the technology, while aligning with an organization’s broader strategic goals.