Skip to content

Organize and update writing templates and canned responses - #99

Draft
Premas wants to merge 4 commits into
mainfrom
experimental-snow-templates
Draft

Premas wants to merge 4 commits into
mainfrom
experimental-snow-templates

Conversation

@Premas

@Premas Premas commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Pull Request

Intent

Proposed Changes

Writing templates and canned responses already exist in the documentation. This issue is to:

  1. Review and organize the existing templates and canned responses.
  2. Update them to reflect recent changes.
  3. Add new templates and canned responses for additional/common use cases.
  4. Ensure the templates are clear, consistent, and easy to find and reuse.

Changes to Section Headers

Changes to Page URLs

Related or Fixed Issues

Accessibility Checklist

I have ensured all of the following for new or changed content:

  • all images have appropriate alt text. Guidelines
  • all images with text have sufficient contrast ratio. Checker
  • all image text is transcribed or described in body text.
  • all technical terms, jargon, and abbreviations are introduced before they are used.

Style Checklist

I have done all of the following:

  • searched for other relevant pages and crosslinked from my content to them.
  • searched for other relevant pages and crosslinked from them to my content.
  • added redirects in mkdocs.yml for any moved headers or pages.
  • defined new technical terms, jargon, and abbreviations in the glossary.
  • searched for existing technical terms, jargon, and abbreviations in the glossary and added crosslinks to them.
  • properly formatted and introduced key branding terms. List here.

Comment thread docs/tickets/account/cloud.rc/create.md Outdated

### Create a ServiceNow Task

1. Create a new [task](#creating-a-servicenow-task) on the ticket giving the BlazerID or XIAS name for the person requesting the account. Use `Request to create Cloud account` as the short description and `Create Cloud account for <blazerid_or_XIAS>` as the description. Omit any `@uab.edu` string for BlazerIDs, but keep the email host for XIAS accounts.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we provide a Cloud account for XIAS users?

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants