elastic / elastic/docs-content

Produce guidance for writers for documenting subscription and feature tier requirements, which are not the same

Open
#5,357 0 comments 0 reactions 0 assignees View on GitHub
cross-team
Dominant language
No language data
Stars
47
Forks
261
Avg merge
3d 21h
Merged PRs (30d)
141

Description

In order to increase consistency in how we write about subscription level requirements or feature tier requirements (even in a non specific way such as "you must have the appropriate subscription or feature tier"), we should create clear guidance with examples.

More context about how subscription levels and feature tiers work in the parent issue.

This should be not only documented, but also clearly shared with the writing team.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.