Workflows

Overview

This page describes different types of workflows for development processes implemented from 2024 and onward. The various workflows are composed of information that can inform administrators and developers of the capabilities of the site.

User Workflows

User Workflows are what users can do on the site. The different processes that will be described are:

• Foundations of the Website:

  • This section includes information about the foundations of DAILP’s website like the menu items.

• Navigating CWKW:

  • This section includes steps on how users can find and use different features of DAILP’s Reading Environment such as:
    • Navigating from the DAILP Website to CWKW
    • CWKW Reference Section
    • Teaching Modules

• Accessing A Collection:

  • This section includes the steps on how to access a collection in the site.

• Viewing A Document:

  • This section includes information on the tabs within each document and how to adjust display settings.

• Viewing A Word:

  • This section includes a description about the Wordpane on each Document page

Development Workflows

This Development Workflows page describes the process of how developers maintain the code driving the website. This consists of a contribution guide and onboarding documentation. Developers can learn how to set up their computers to get started writing code.

• Contribution Guide:

  • This consists of what DAILP expects in code.

• Onboarding Documentation:

  • This consists of what developers need to get started on coding such as Development Environment Setup, Git, Front-end, and Rust Back-end.

Administrative Workflows

This page describes what DAILP, as a project, does to organize and support tribal translation teams (e.g. Eastern Band of Cherokee Indians, Anishinaabemowin, and United Keetoowah Band of Cherokee Indians). The translation teams develop and administer processes to create their own digital edited collections. Translation teams develop content and technical documentation for their workflows and the digital edited collections they create.

• DAILP Project Team:

  • This section describes what the DAILP teams are, what those teams do, and the specifics of how they operate.

• DAILP Project Operations:

  • This section includes information about DAILP’s:
    • Publication Pipeline (Documents/Stories): Provides links to some of our other pages for more details.
    • RI: Reading Interface: Includes insight into DAILP’s Reading Environment.
    • TI: Translation Interface: Includes insight into DAILP’s Translation Environment.
    • RI & TI: Describes how both environments work together and provides a link another page that has more information about the RI and TI structures as well as their workflows.
    • CARE Principles: The CARE Principles page under Community-Based Design provides information about DAILP’s community-based CARE Principles. This page describes how these principles affect teams and workflows.

• Maintaining The DAILP Project:

  • This section describes how DAILP maintains DAILP as a project and details documentation workflows and team-training materials.

    • Documentation Workflows: Gives details about the different documentation workflows within DAILP and the process of these workflows. These documentation workflows include:
      • Public Materials
      • Technical Standards and Requirements
      • Wiki
      • Developer Documentation
      • Internal Documentation

    • Team-Training Materials:

      • This section describes what DAILP’s team-training materials are with providing links to other pages.

    • Grants Administration:

      • As DAILP grows, grants are an important aspect of how we support the DAILP project, workflows, and teams.
      • DAILP plans grants with community-based teams and supports them in the application process.