<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=271629) </details> <!--IssueSummary end--> <!-- * Use this issue template for suggesting new docs or updates to existing docs. Note: Doc work as part of feature development is covered in the Feature Request template. * For issues related to features of the docs.gitlab.com site, see https://gitlab.com/gitlab-org/gitlab-docs/issues/ * For information about documentation content and process, see https://docs.gitlab.com/ee/development/documentation/ --> ### Problem to solve Can any of the manual checks the technical writers perform on release post items be automated? The current list is available at https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/.gitlab/merge_request_templates/Release-Post-Item.md Examples: - Length of title field - Single quotes around link field - Double quotes around the title field - _(others?)_ The release post items are YAML files, which would imply using `yamllint`, but based on @aqualls' reading of the yamllint rules (https://yamllint.readthedocs.io/en/stable/rules.html) it looks like quotation marks may be all-or-nothing in a way that causes more disruption than help. Consider if there are other ways some of the items could be automated to help eliminate manual checks and increase self-service for PMs. cc @cnorris <!-- Include the following detail as necessary: * What product or feature(s) affected? * What docs or doc section affected? Include links or paths. * Is there a problem with a specific document, or a feature/process that's not addressed sufficiently in docs? * Any other ideas or requests? --> ### Further details <!-- * Any concepts, procedures, reference info we could add to make it easier to successfully use GitLab? * Include use cases, benefits, and/or goals for this work. * If adding content: What audience is it intended for? (What roles and scenarios?) For ideas, see personas at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ or the persona labels at https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A --> ### Proposal <!-- Further specifics for how can we solve the problem. --> ### Who can address the issue <!-- What if any special expertise is required to resolve this issue? --> ### Other links/references <!-- E.g. related GitLab issues/MRs -->