Add documentation for Springshare admin tasks

[VickieKarasic]

Introduction

We need to create documentation separate from Springshare's support docs(need to be logged into PUL LibApps to access) and from our user-facing docs on Confluence to outline the PUL-specific admin tasks that we perform in LibApps regularly.

Acceptance criteria

• If there is no docs directory, create one.

• Update an existing markdown document or add a new one in the docs directory.

• It has introduction: Explains the goals and purpose of this documentation.

• It has a step by step guide: Provides the exact steps to guide the user on how to do a task.

Additional acceptance criteria

• It includes references: References any related resources that have assisted creating this documentation (links to other tickets, online articles etc.).

• It includes workflow: Defines the steps in different environments (production, staging)

Even more acceptance criteria (see full list of PUL Springshare admin tasks)

• LibApps

  • Creating accounts
  • Managing people's profile boxes

• LibCal

  • Creating / editing locations and spaces
  • Creating / editing equipment
  • Editing library hours
  • Adding Zoom / Outlook integrations and checking integration status
  • Managing event calendars

• LibGuides

  • Changing a Guide's owner
  • Update Look & Feel: guide templates, CSS/JS, headers/footers
  • Managing metadata and subjects/experts
  • Manage A-Z Databases List

• LibAnswers

  • Forwarding to/from a service account
  • Creating queues
  • Deleting queues

• LibWizard