From 9c4abc7d8332fb5e682efdbcce0870a0cdabc580 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Thu, 5 Nov 2026 06:04:18 -0600 Subject: [PATCH] Feature Chris Tran and align Training with Loptr Lab typography and reading settings --- docs/accessibility/cognitive-learning.html | 3 +- docs/accessibility/index.html | 3 +- docs/accessibility/input-motor.html | 3 +- docs/accessibility/magnification.html | 3 +- docs/accessibility/screen-reader.html | 3 +- docs/accessibility/visual.html | 3 +- docs/case-study/01-vocational-goal.html | 3 +- docs/case-study/02-work-tasks.html | 3 +- .../03-accessibility-requirements.html | 3 +- docs/case-study/04-technology-assessment.html | 3 +- docs/case-study/05-funding-research.html | 3 +- docs/case-study/06-approval-packet.html | 3 +- docs/case-study/07-lessons-learned.html | 3 +- docs/case-study/README.html | 3 +- docs/funding/README.html | 3 +- .../united-states/federal/README.html | 3 +- .../united-states/state/minnesota/README.html | 3 +- docs/funding/program-research-template.html | 3 +- docs/index.html | 13 ++- docs/pixie-contributors.html | 3 +- docs/prompts/README.html | 3 +- docs/prompts/adapt-jurisdiction.html | 3 +- docs/prompts/audit-information.html | 3 +- docs/prompts/build-request.html | 3 +- docs/prompts/compare-costs.html | 3 +- docs/prompts/find-programs.html | 3 +- docs/prompts/research-technology.html | 3 +- docs/prompts/safe-research.html | 3 +- docs/prompts/verify-eligibility.html | 3 +- .../development-environment.html | 3 +- docs/technology-planning/index.html | 3 +- .../xbox-workstation-example.html | 3 +- docs/templates/README.html | 3 +- docs/templates/approval-packet.html | 3 +- docs/templates/decision-maker-questions.html | 3 +- docs/templates/equipment-justification.html | 3 +- docs/templates/needs-statement.html | 3 +- docs/templates/quote-comparison.html | 3 +- .../templates/source-verification-record.html | 3 +- docs/templates/technology-plan.html | 3 +- docs/templates/training-plan.html | 3 +- docs/tracks/audio.html | 3 +- docs/tracks/design.html | 3 +- docs/tracks/duet-development-provenance.html | 3 +- docs/tracks/game-development.html | 3 +- docs/tracks/hybrid-creative-technology.html | 3 +- docs/tracks/index.html | 3 +- docs/tracks/maker-game-systems.html | 3 +- docs/tracks/software-development.html | 3 +- docs/tracks/video.html | 3 +- docs/training-display.js | 36 +++++++ docs/training.css | 101 +++++++----------- 52 files changed, 187 insertions(+), 110 deletions(-) create mode 100644 docs/training-display.js diff --git a/docs/accessibility/cognitive-learning.html b/docs/accessibility/cognitive-learning.html index 2bd393c..9abdac4 100644 --- a/docs/accessibility/cognitive-learning.html +++ b/docs/accessibility/cognitive-learning.html @@ -1,2 +1,3 @@ -Cognitive and learning access — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

Guide home

Cognitive and learning access

Cognitive and learning access

+Cognitive and learning access — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

Guide home

Cognitive and learning access

Cognitive and learning access

Reduce avoidable memory, sequencing, naming, interruption, and context-switching burdens. Useful capabilities may include clear steps, persistent state, meaningful defaults, templates, checklists, searchable history, undo, reminders, transcription, plain-language explanations, and resumable workflows. The system should support autonomy rather than make decisions or disclose information on the participant's behalf.

Verify current evidence and requirements. Protect private records.
\ No newline at end of file diff --git a/docs/accessibility/index.html b/docs/accessibility/index.html index f43860b..5089b63 100644 --- a/docs/accessibility/index.html +++ b/docs/accessibility/index.html @@ -1,4 +1,5 @@ -Accessibility — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

← Guide home

Accessibility

Describe barriers without oversharing

Describe the barrier in relation to a task, then identify a capability or accommodation. Share only what is necessary; a diagnosis is not required to explain that text must enlarge without clipping or that an input method causes fatigue.

+Accessibility — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

← Guide home

Accessibility

Describe barriers without oversharing

Describe the barrier in relation to a task, then identify a capability or accommodation. Share only what is necessary; a diagnosis is not required to explain that text must enlarge without clipping or that an input method causes fatigue.

diff --git a/docs/accessibility/input-motor.html b/docs/accessibility/input-motor.html index 091c559..ab73577 100644 --- a/docs/accessibility/input-motor.html +++ b/docs/accessibility/input-motor.html @@ -1,2 +1,3 @@ -Input and motor access — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

Guide home

Input and motor access

Input and motor access

+Input and motor access — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

Guide home

Input and motor access

Input and motor access

Identify precision, reach, repetition, pressure, timing, posture, and fatigue barriers. Consider keyboard-only use, remapping, switch access, voice input, pointing alternatives, adjustable timing, automation, ergonomic positioning, and recovery from accidental activation. Evaluate sustained real tasks, not a brief demonstration.

Verify current evidence and requirements. Protect private records.
\ No newline at end of file diff --git a/docs/accessibility/magnification.html b/docs/accessibility/magnification.html index f908404..93e5dc0 100644 --- a/docs/accessibility/magnification.html +++ b/docs/accessibility/magnification.html @@ -1,2 +1,3 @@ -Magnification — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

Guide home

Magnification

Magnification

+Magnification — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

Guide home

Magnification

Magnification

Test operating-system and application zoom at the participant's working scale. Check reflow, pointer tracking, focus visibility, context retention, dialogs, timelines, canvases, and multi-pane layouts. A larger display may help some workflows, but it is not a substitute for software that remains operable when magnified.

Verify current evidence and requirements. Protect private records.
\ No newline at end of file diff --git a/docs/accessibility/screen-reader.html b/docs/accessibility/screen-reader.html index a435057..d5144f7 100644 --- a/docs/accessibility/screen-reader.html +++ b/docs/accessibility/screen-reader.html @@ -1,2 +1,3 @@ -Screen-reader access — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

Guide home

Screen-reader access

Screen-reader access

+Screen-reader access — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

Guide home

Screen-reader access

Screen-reader access

Verify meaningful names, roles, states, reading and focus order, keyboard operation, error announcements, document structure, and accessible output. Test installation, authentication, editor panes, dialogs, collaboration tools, and export—not only the primary screen. Record blockers and available workarounds without assuming that theoretical standards compliance equals usable work.

Verify current evidence and requirements. Protect private records.
\ No newline at end of file diff --git a/docs/accessibility/visual.html b/docs/accessibility/visual.html index 26682dc..8354c95 100644 --- a/docs/accessibility/visual.html +++ b/docs/accessibility/visual.html @@ -1,2 +1,3 @@ -Visual access — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

Guide home

Visual access

Visual access

+Visual access — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

Guide home

Visual access

Visual access

Document the task and observable barrier: text size, contrast, glare, focus visibility, dense layout, color dependence, detail inspection, or eye fatigue. Required capabilities may include scalable text, reflow, high contrast, adjustable brightness, non-color cues, zoom that preserves context, and display positioning. Test the actual application; a hardware specification alone does not prove access.

Verify current evidence and requirements. Protect private records.
\ No newline at end of file diff --git a/docs/case-study/01-vocational-goal.html b/docs/case-study/01-vocational-goal.html index 0b329fb..0936354 100644 --- a/docs/case-study/01-vocational-goal.html +++ b/docs/case-study/01-vocational-goal.html @@ -1,4 +1,5 @@ -1. Vocational goal — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
Guide home

1. Vocational goal

1. Vocational goal

+1. Vocational goal — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
Guide home

1. Vocational goal

1. Vocational goal

The participant wants to pursue accessible creative-technology work that combines software, interactive media, documentation, and production support. The goal is stated as work to be performed—not as ownership of a particular device, company formation, guaranteed employment, or a claim that a program must fund the plan.

diff --git a/docs/case-study/02-work-tasks.html b/docs/case-study/02-work-tasks.html index 4b02b21..69f4198 100644 --- a/docs/case-study/02-work-tasks.html +++ b/docs/case-study/02-work-tasks.html @@ -1,4 +1,5 @@ -2. Work tasks — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
Guide home

2. Work tasks

2. Work tasks

+2. Work tasks — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
Guide home

2. Work tasks

2. Work tasks

Representative tasks include editing and testing code, organizing project files, producing and reviewing media, documenting decisions and provenance, collaborating through repositories, conducting source-based research, and preparing accessible demonstrations.

diff --git a/docs/case-study/03-accessibility-requirements.html b/docs/case-study/03-accessibility-requirements.html index 4ca4f2e..f1c779f 100644 --- a/docs/case-study/03-accessibility-requirements.html +++ b/docs/case-study/03-accessibility-requirements.html @@ -1,4 +1,5 @@ -3. Accessibility requirements — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
Guide home

3. Accessibility requirements

3. Accessibility requirements

+3. Accessibility requirements — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
Guide home

3. Accessibility requirements

3. Accessibility requirements

The participant describes functional needs without publishing diagnoses or private records. The plan includes readable scaling and contrast, reduced visual strain, resumable task state, low-memory-burden file handling, clear sequencing, alternate input where needed, and reliable ways to recover after interruption.

diff --git a/docs/case-study/04-technology-assessment.html b/docs/case-study/04-technology-assessment.html index 60f5c34..dc61229 100644 --- a/docs/case-study/04-technology-assessment.html +++ b/docs/case-study/04-technology-assessment.html @@ -1,4 +1,5 @@ -4. Technology assessment — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
Guide home

4. Technology assessment

4. Technology assessment

+4. Technology assessment — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
Guide home

4. Technology assessment

4. Technology assessment

The assessment converts tasks and barriers into capabilities: accessible display and input, sufficient compute for representative development and media workloads, dependable storage and backup, portable project state, and compatible collaboration tools.

diff --git a/docs/case-study/05-funding-research.html b/docs/case-study/05-funding-research.html index 2c9ae5f..bbdcec8 100644 --- a/docs/case-study/05-funding-research.html +++ b/docs/case-study/05-funding-research.html @@ -1,4 +1,5 @@ -5. Funding research — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
Guide home

5. Funding research

5. Funding research

+5. Funding research — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
Guide home

5. Funding research

5. Funding research

The participant identifies the relevant jurisdiction and researches programs through current official sources. General program descriptions are separated from an individual eligibility or authorization decision. Conflicts and missing facts are labeled unverified, and questions are prepared for the responsible counselor or agency.

diff --git a/docs/case-study/06-approval-packet.html b/docs/case-study/06-approval-packet.html index 1236109..424d80e 100644 --- a/docs/case-study/06-approval-packet.html +++ b/docs/case-study/06-approval-packet.html @@ -1,4 +1,5 @@ -6. Approval packet — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
Guide home

6. Approval packet

6. Approval packet

+6. Approval packet — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
Guide home

6. Approval packet

6. Approval packet

The packet contains the vocational goal, work tasks, functional barriers, essential capabilities, minimum and preferred configurations, alternatives, a training plan where relevant, dated quotes, source-verification records, and a concise list of decisions required from the responsible human.

diff --git a/docs/case-study/07-lessons-learned.html b/docs/case-study/07-lessons-learned.html index 5e0ed20..f49266e 100644 --- a/docs/case-study/07-lessons-learned.html +++ b/docs/case-study/07-lessons-learned.html @@ -1,4 +1,5 @@ -7. Lessons learned — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
Guide home

7. Lessons learned

7. Lessons learned

+7. Lessons learned — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
Guide home

7. Lessons learned

7. Lessons learned

• Beginning with work tasks produces a defensible plan; beginning with a desired product produces assumptions.

• Accessibility is a system requirement throughout the workflow, not a final checklist.

diff --git a/docs/case-study/README.html b/docs/case-study/README.html index 8070b59..a5b16bb 100644 --- a/docs/case-study/README.html +++ b/docs/case-study/README.html @@ -1,4 +1,5 @@ -Worked example — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

← Guide home

Worked example

See planning in practice

This anonymized real-world example demonstrates a process, not a guarantee of eligibility, authorization, funding, employment, or benefits treatment. Identifying details are removed. Inspect the work one stage at a time:

+Worked example — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

← Guide home

Worked example

See planning in practice

This anonymized real-world example demonstrates a process, not a guarantee of eligibility, authorization, funding, employment, or benefits treatment. Identifying details are removed. Inspect the work one stage at a time:

  1. Vocational goal
  2. Work tasks
    3. diff --git a/docs/funding/README.html b/docs/funding/README.html index 6272d4d..3829391 100644 --- a/docs/funding/README.html +++ b/docs/funding/README.html @@ -1,4 +1,5 @@ -Funding research — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    ← Guide home

    Funding research

    Check rules before requesting support

    Funding is jurisdiction- and program-specific. Start with the jurisdiction tree, verify the responsible agency, and record the source and verification date. Listing a program never guarantees eligibility, authorization, or payment.

    +Funding research — Loptr Lab +
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    ← Guide home

    Funding research

    Check rules before requesting support

    Funding is jurisdiction- and program-specific. Start with the jurisdiction tree, verify the responsible agency, and record the source and verification date. Listing a program never guarantees eligibility, authorization, or payment.

    • United States federal context
    • Minnesota—first state implementation
      • diff --git a/docs/funding/jurisdictions/united-states/federal/README.html b/docs/funding/jurisdictions/united-states/federal/README.html index bf07d48..7825587 100644 --- a/docs/funding/jurisdictions/united-states/federal/README.html +++ b/docs/funding/jurisdictions/united-states/federal/README.html @@ -1,4 +1,5 @@ -United States federal context — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
      Guide home

      United States federal context

      United States federal context

      +United States federal context — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
      Guide home

      United States federal context

      United States federal context

      Federal law and national programs may shape state or local services, but the responsible state, tribal, territorial, local, educational, workforce, or benefits authority may make the individual decision. Research the current official federal source, then identify the office that can answer the participant's specific question.

      diff --git a/docs/funding/jurisdictions/united-states/state/minnesota/README.html b/docs/funding/jurisdictions/united-states/state/minnesota/README.html index ddaa14d..b513948 100644 --- a/docs/funding/jurisdictions/united-states/state/minnesota/README.html +++ b/docs/funding/jurisdictions/united-states/state/minnesota/README.html @@ -1,4 +1,5 @@ -Minnesota funding research — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
      Guide home

      Minnesota funding research

      Minnesota funding research

      +Minnesota funding research — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
      Guide home

      Minnesota funding research

      Minnesota funding research

      Minnesota is the first worked jurisdiction, not the default architecture. Begin with current official Minnesota sources and confirm the responsible program and decision-maker before relying on any rule.

      diff --git a/docs/funding/program-research-template.html b/docs/funding/program-research-template.html index 35d0e3b..655575a 100644 --- a/docs/funding/program-research-template.html +++ b/docs/funding/program-research-template.html @@ -1,4 +1,5 @@ -Program research record — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
      Guide home

      Program research record

      Program research record

      +Program research record — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
      Guide home

      Program research record

      Program research record

      • Jurisdiction and responsible authority:

      • Program and official source:

      diff --git a/docs/index.html b/docs/index.html index c3f284d..d363336 100644 --- a/docs/index.html +++ b/docs/index.html @@ -6,7 +6,8 @@ Start with your work — Loptr Lab - + + @@ -36,6 +37,16 @@

      Start with your work,
      not a computer.

      +
      +

      Featured resource · Gaming careers

      +

      Chris Tran: make your work easier to see.

      +

      Chris Tran’s free GG: Work and Play newsletter covers portfolios, interviews and professional networking. Explore his advice, then use a real contribution to build evidence of your own work.

      +
      + Explore Chris Tran’s resources + Build your portfolio evidence +
      +

      Independent resource. Chris also offers optional paid coaching; free training remains available separately.

      +
      YOUR ROUTE

      Six steps from goal to request

      diff --git a/docs/pixie-contributors.html b/docs/pixie-contributors.html index 609e97b..48e81b6 100644 --- a/docs/pixie-contributors.html +++ b/docs/pixie-contributors.html @@ -1,4 +1,5 @@ -PIXIE: join, contribute and resume — Loptr Lab
      LOPTR LAB / CONTRIBUTOR COORDINATION

      PIXIE stays with the work.

      Join a project, keep a shared checkpoint in GitHub, and resume without reconstructing the briefing.

      Why we are testing PIXIE

      Loptr Lab’s ecosystem is the testing ground for an open-source multimedia training studio. PIXIE is its contributor companion, helping people join, learn, coordinate work and return with context intact. Contributor testing is the immediate goal; a finished commercial app is not required before testing begins. Pilot evidence should inform a concrete project pitch and a sustainable revenue model consistent with the existing mission, open participation and project licenses.

      Read the owner-confirmed studio direction. Record concrete contributions, learning outcomes, handoffs, repeated explanations and defects. Build the pitch from these findings; studio viability, public plugin distribution and commercial readiness remain separate questions.

      Your contributor journey

      1. Start. Open the existing PIXIE companion, choose a project and read its repository’s contribution instructions. Training is the default starting point.
      2. Choose a task. Use “How can I help?” for a bounded suggestion. Then choose “Join & coordinate” and describe the proposed task, progress, blocker and next action.
      3. Review and submit. Review the checkpoint draft and its public visibility. “Review & submit on GitHub” opens a prefilled issue in that project. You submit it using GitHub; PIXIE does not post automatically or enroll you.
      4. Agree scope. Record maintainer agreement, time, credit and exit arrangements in the issue. A suggestion or issue does not itself assign a task or grant access.
      5. Keep coordinated. Add progress comments with evidence, blockers and the next action. Keep the issue URL. GitHub holds the shared history.
      6. Resume. In a later session, choose the same project, select “Resume my checkpoint” and paste the issue URL. PIXIE reads the current public issue and latest comment page. Open the full GitHub discussion for older comments.

      From work to portfolio evidence

      +PIXIE: join, contribute and resume — Loptr Lab +
      LOPTR LAB / CONTRIBUTOR COORDINATION

      PIXIE stays with the work.

      Join a project, keep a shared checkpoint in GitHub, and resume without reconstructing the briefing.

      Why we are testing PIXIE

      Loptr Lab’s ecosystem is the testing ground for an open-source multimedia training studio. PIXIE is its contributor companion, helping people join, learn, coordinate work and return with context intact. Contributor testing is the immediate goal; a finished commercial app is not required before testing begins. Pilot evidence should inform a concrete project pitch and a sustainable revenue model consistent with the existing mission, open participation and project licenses.

      Read the owner-confirmed studio direction. Record concrete contributions, learning outcomes, handoffs, repeated explanations and defects. Build the pitch from these findings; studio viability, public plugin distribution and commercial readiness remain separate questions.

      Your contributor journey

      1. Start. Open the existing PIXIE companion, choose a project and read its repository’s contribution instructions. Training is the default starting point.
      2. Choose a task. Use “How can I help?” for a bounded suggestion. Then choose “Join & coordinate” and describe the proposed task, progress, blocker and next action.
      3. Review and submit. Review the checkpoint draft and its public visibility. “Review & submit on GitHub” opens a prefilled issue in that project. You submit it using GitHub; PIXIE does not post automatically or enroll you.
      4. Agree scope. Record maintainer agreement, time, credit and exit arrangements in the issue. A suggestion or issue does not itself assign a task or grant access.
      5. Keep coordinated. Add progress comments with evidence, blockers and the next action. Keep the issue URL. GitHub holds the shared history.
      6. Resume. In a later session, choose the same project, select “Resume my checkpoint” and paste the issue URL. PIXIE reads the current public issue and latest comment page. Open the full GitHub discussion for older comments.

      From work to portfolio evidence

      Chris Tran’s career advice and optional coaching can help gaming professionals explain their work and prepare relevant professional conversations. The Made-Sick card holds the source, attribution and free/commercial distinctions.

      • Starting without project experience? Browse the current Training issues, read how to contribute, and choose one bounded task suited to your skills and interests. Labels and available work can change. Check existing assignments and agree scope with the maintainer; a listing is not acceptance.
      • Returning to current work? Keep the same project and issue. Use “Resume my checkpoint” as described above, or open that issue directly. Add evidence and your next action there; do not create a second tracker.
        • diff --git a/docs/prompts/README.html b/docs/prompts/README.html index cee71ce..33c30b6 100644 --- a/docs/prompts/README.html +++ b/docs/prompts/README.html @@ -1,4 +1,5 @@ -AI research prompts — Loptr Lab
        LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

        ← Guide home

        AI research prompts

        Use AI research with human oversight

        These prompts are designed to make AI research more reliable, not to replace the agency or person who makes the decision. Each prompt requires current authoritative sources, direct links, verification dates, separation of confirmed facts from uncertainty, and the word unverified instead of a guess.

        +AI research prompts — Loptr Lab +
        LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

        ← Guide home

        AI research prompts

        Use AI research with human oversight

        These prompts are designed to make AI research more reliable, not to replace the agency or person who makes the decision. Each prompt requires current authoritative sources, direct links, verification dates, separation of confirmed facts from uncertainty, and the word unverified instead of a guess.

        • Safe research practices
        • Find programs
          • diff --git a/docs/prompts/adapt-jurisdiction.html b/docs/prompts/adapt-jurisdiction.html index 718de41..3370960 100644 --- a/docs/prompts/adapt-jurisdiction.html +++ b/docs/prompts/adapt-jurisdiction.html @@ -1,4 +1,5 @@ -Prompt: adapt research to another jurisdiction — Loptr Lab
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          Guide home

          Prompt: adapt research to another jurisdiction

          Prompt: adapt research to another jurisdiction

          +Prompt: adapt research to another jurisdiction — Loptr Lab +
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          Guide home

          Prompt: adapt research to another jurisdiction

          Prompt: adapt research to another jurisdiction

          Adapt this research method—not its conclusions—from [current jurisdiction] to [new jurisdiction] for [question]. Identify the correct levels of authority and current official sources in the new jurisdiction. Provide links and verification dates, distinguish confirmed facts from uncertainty, and mark unsupported mappings unverified. Do not assume that program names, eligibility, funding, deadlines, appeals, or decision-makers transfer between jurisdictions.
          Educational guidance only. Protect private records and verify current sources.
          \ No newline at end of file diff --git a/docs/prompts/audit-information.html b/docs/prompts/audit-information.html index 6816f5e..4367591 100644 --- a/docs/prompts/audit-information.html +++ b/docs/prompts/audit-information.html @@ -1,4 +1,5 @@ -Prompt: audit existing information — Loptr Lab
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          Guide home

          Prompt: audit existing information

          Prompt: audit existing information

          +Prompt: audit existing information — Loptr Lab +
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          Guide home

          Prompt: audit existing information

          Prompt: audit existing information

          Audit the following material for outdated facts, unsupported assumptions, duplicated guidance, privacy risk, and claims that only a human authority can make: [material]. Check current authoritative sources and link them with verification dates. Classify each claim as confirmed, contradicted, uncertain, or unverified. Identify volatile facts that should move into dated research notes. Preserve substantive content unless you can state why it is superseded or intentionally retired.
          Educational guidance only. Protect private records and verify current sources.
          \ No newline at end of file diff --git a/docs/prompts/build-request.html b/docs/prompts/build-request.html index 3d06770..77fda22 100644 --- a/docs/prompts/build-request.html +++ b/docs/prompts/build-request.html @@ -1,4 +1,5 @@ -Prompt: build a request — Loptr Lab
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          Guide home

          Prompt: build a request

          Prompt: build a request

          +Prompt: build a request — Loptr Lab +
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          Guide home

          Prompt: build a request

          Prompt: build a request

          Draft a preparation document for [human decision-maker] using only these confirmed inputs: [goal, tasks, barriers, capabilities, verified sources]. Organize it as goal, work tasks, functional barriers, essential capabilities, minimum configuration, preferred configuration, alternatives considered, current quotes, uncertainties, and questions requiring a decision. Do not invent facts, diagnoses, eligibility, authorization, or approval. Mark absent evidence unverified and flag every statement that needs human confirmation.
          Educational guidance only. Protect private records and verify current sources.
          \ No newline at end of file diff --git a/docs/prompts/compare-costs.html b/docs/prompts/compare-costs.html index 9ec7f4c..1cb29a2 100644 --- a/docs/prompts/compare-costs.html +++ b/docs/prompts/compare-costs.html @@ -1,4 +1,5 @@ -Prompt: compare costs and alternatives — Loptr Lab
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          Guide home

          Prompt: compare costs and alternatives

          Prompt: compare costs and alternatives

          +Prompt: compare costs and alternatives — Loptr Lab +
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          Guide home

          Prompt: compare costs and alternatives

          Prompt: compare costs and alternatives

          Compare current ways to meet these documented capabilities: [capabilities] in [location/jurisdiction]. Include purchase, refurbishment, borrowing, public or maker-space access, training-lab access, cloud or remote services, and phased acquisition where relevant. Use current source links and verification dates. Separate one-time and recurring costs, note prerequisites and accessibility tradeoffs, and mark missing or changing information unverified. Do not treat the cheapest option as equivalent unless it performs the required tasks accessibly.
          Educational guidance only. Protect private records and verify current sources.
          \ No newline at end of file diff --git a/docs/prompts/find-programs.html b/docs/prompts/find-programs.html index 065533d..2a944fd 100644 --- a/docs/prompts/find-programs.html +++ b/docs/prompts/find-programs.html @@ -1,4 +1,5 @@ -Prompt: find programs — Loptr Lab
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          Guide home

          Prompt: find programs

          Prompt: find programs

          +Prompt: find programs — Loptr Lab +
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          Guide home

          Prompt: find programs

          Prompt: find programs

          Find programs in [jurisdiction] that may relate to [vocational goal or documented need]. Start with current official government, educational, or program-owner sources. For each candidate, provide its exact name, responsible authority, official link, source verification date, stated purpose, and how a person applies or asks a question. Separate confirmed facts from possible relevance. Mark unconfirmed fit or availability as unverified. Do not predict eligibility or approval; identify the human decision-maker.
          Educational guidance only. Protect private records and verify current sources.
          \ No newline at end of file diff --git a/docs/prompts/research-technology.html b/docs/prompts/research-technology.html index a5c4953..2cf6464 100644 --- a/docs/prompts/research-technology.html +++ b/docs/prompts/research-technology.html @@ -1,4 +1,5 @@ -Prompt: research technology — Loptr Lab
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          Guide home

          Prompt: research technology

          Prompt: research technology

          +Prompt: research technology — Loptr Lab +
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          Guide home

          Prompt: research technology

          Prompt: research technology

          Research technology capabilities for these work tasks: [tasks] and these functional barriers: [barriers]. Begin with required capabilities, then identify minimum, preferred, and alternative configurations. Use current manufacturer documentation and independent primary technical sources where available; include links and verification dates. Treat prices, availability, models, and specifications as dated facts. Separate verified specifications from assumptions and mark gaps unverified. Do not choose a product solely by brand, popularity, or price.
          Educational guidance only. Protect private records and verify current sources.
          \ No newline at end of file diff --git a/docs/prompts/safe-research.html b/docs/prompts/safe-research.html index 20ba625..b5578d2 100644 --- a/docs/prompts/safe-research.html +++ b/docs/prompts/safe-research.html @@ -1,4 +1,5 @@ -Prompt: safe research practices — Loptr Lab
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          Guide home

          Prompt: safe research practices

          Prompt: safe research practices

          +Prompt: safe research practices — Loptr Lab +
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          Guide home

          Prompt: safe research practices

          Prompt: safe research practices

          Help me research the following question without requesting or exposing private identifiers: [question]. Use current authoritative sources and link directly to each source. Record the date each source was checked. Separate confirmed facts, reasonable inferences, and unresolved questions. Mark anything not supported by a current authoritative source as unverified. Identify the human or agency that has authority to decide this question and give me questions to ask them. Do not claim that AI research establishes eligibility, approval, legal status, or funding.
          Educational guidance only. Protect private records and verify current sources.
          \ No newline at end of file diff --git a/docs/prompts/verify-eligibility.html b/docs/prompts/verify-eligibility.html index 5f080a4..f770b97 100644 --- a/docs/prompts/verify-eligibility.html +++ b/docs/prompts/verify-eligibility.html @@ -1,4 +1,5 @@ -Prompt: verify eligibility information — Loptr Lab
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          Guide home

          Prompt: verify eligibility information

          Prompt: verify eligibility information

          +Prompt: verify eligibility information — Loptr Lab +
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          Guide home

          Prompt: verify eligibility information

          Prompt: verify eligibility information

          Audit the claim [claim] for [program and jurisdiction]. Use current authoritative sources, link to the controlling or most direct source, and state the date verified. Quote only the minimum language needed. Distinguish general eligibility rules from an individual decision, identify exceptions or missing facts, and mark unsupported claims as unverified. State who has authority to decide and prepare concise questions for that person. Do not request personal identifiers or confidential records.
          Educational guidance only. Protect private records and verify current sources.
          \ No newline at end of file diff --git a/docs/technology-planning/development-environment.html b/docs/technology-planning/development-environment.html index b784733..f4f4984 100644 --- a/docs/technology-planning/development-environment.html +++ b/docs/technology-planning/development-environment.html @@ -1,4 +1,5 @@ -Development environment & equipment — Loptr Lab
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          ← Guide home

          Development environment & equipment

          Plan the work first. Then choose the hardware, software and access tools.

          +Development environment & equipment — Loptr Lab +
          LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

          ← Guide home

          Development environment & equipment

          Plan the work first. Then choose the hardware, software and access tools.

          1. Choose your development path

          Match equipment to the real tasks you must perform, not a brand or a presumed diagnosis. You can start with an iPad or other accessible device and still document why a separate workstation is required for certain development work.

AreaPlanning questions
Visual accessCan content be perceived through contrast, scale, spacing, and non-color cues?
diff --git a/docs/technology-planning/index.html b/docs/technology-planning/index.html index 10bc115..a3eec46 100644 --- a/docs/technology-planning/index.html +++ b/docs/technology-planning/index.html @@ -1,4 +1,5 @@ -Technology planning — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

← Guide home

Technology planning

Turn tasks into requirements

Explore development environment & equipment →

Use this chain for every recommendation:

+Technology planning — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

← Guide home

Technology planning

Turn tasks into requirements

Explore development environment & equipment →

Use this chain for every recommendation:

  1. Vocational goal — the work outcome.
  2. Work tasks — observable activities required by that goal.
    3. diff --git a/docs/technology-planning/xbox-workstation-example.html b/docs/technology-planning/xbox-workstation-example.html index b9c0e6b..0ba27b4 100644 --- a/docs/technology-planning/xbox-workstation-example.html +++ b/docs/technology-planning/xbox-workstation-example.html @@ -1,4 +1,5 @@ -Xbox development workstation: dated purchasing example — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    Guide home

    Xbox development workstation: dated purchasing example

    Xbox development workstation: dated purchasing example

    +Xbox development workstation: dated purchasing example — Loptr Lab +
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    Guide home

    Xbox development workstation: dated purchasing example

    Xbox development workstation: dated purchasing example

    Checked September 26, 2026 (US market). These are planning ranges, not quotes or guaranteed prices. Recheck stock, seller, configuration, taxes, shipping, and return terms before any purchase or funding request. Use the game development track to establish requirements first, and record actual offers in the quote comparison.

    Fair planning range

    | Item | Indicative US price | Basis and purchase channel |

    diff --git a/docs/templates/README.html b/docs/templates/README.html index 6f1b14f..eb54a37 100644 --- a/docs/templates/README.html +++ b/docs/templates/README.html @@ -1,4 +1,5 @@ -Preparation templates — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    ← Guide home

    Preparation templates

    Collect only the evidence you need

    Use only the templates needed for your request. Keep private records outside public repositories.

    +Preparation templates — Loptr Lab +
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    ← Guide home

    Preparation templates

    Collect only the evidence you need

    Use only the templates needed for your request. Keep private records outside public repositories.

    • Needs statement
    • Technology plan
      • diff --git a/docs/templates/approval-packet.html b/docs/templates/approval-packet.html index 43be6ea..f275576 100644 --- a/docs/templates/approval-packet.html +++ b/docs/templates/approval-packet.html @@ -1,4 +1,5 @@ -Approval packet checklist — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
      Guide home

      Approval packet checklist

      Approval packet checklist

      +Approval packet checklist — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
      Guide home

      Approval packet checklist

      Approval packet checklist

      • [ ] Vocational goal and work tasks

      • [ ] Functional barriers and essential capabilities

      diff --git a/docs/templates/decision-maker-questions.html b/docs/templates/decision-maker-questions.html index dd51515..55c1e0d 100644 --- a/docs/templates/decision-maker-questions.html +++ b/docs/templates/decision-maker-questions.html @@ -1,4 +1,5 @@ -Questions for a counselor or decision-maker — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
      Guide home

      Questions for a counselor or decision-maker

      Questions for a counselor or decision-maker

      +Questions for a counselor or decision-maker — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
      Guide home

      Questions for a counselor or decision-maker

      Questions for a counselor or decision-maker

      • Which office or person has authority to decide this request?

      • What current rule, policy, or plan governs the decision?

      diff --git a/docs/templates/equipment-justification.html b/docs/templates/equipment-justification.html index e372a60..7148d06 100644 --- a/docs/templates/equipment-justification.html +++ b/docs/templates/equipment-justification.html @@ -1,4 +1,5 @@ -Equipment justification — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Equipment justification

      Equipment justification

      +Equipment justification — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Equipment justification

      Equipment justification

      • Item or configuration:

      • Work tasks it enables:

      diff --git a/docs/templates/needs-statement.html b/docs/templates/needs-statement.html index 317294f..f5e9f7e 100644 --- a/docs/templates/needs-statement.html +++ b/docs/templates/needs-statement.html @@ -1,4 +1,5 @@ -Needs statement — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Needs statement

      Needs statement

      +Needs statement — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Needs statement

      Needs statement

      • Vocational goal:

      • Work tasks affected:

      diff --git a/docs/templates/quote-comparison.html b/docs/templates/quote-comparison.html index c71934d..a932eca 100644 --- a/docs/templates/quote-comparison.html +++ b/docs/templates/quote-comparison.html @@ -1,4 +1,5 @@ -Quote comparison — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
      Guide home

      Quote comparison

      Quote comparison

      +Quote comparison — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
      Guide home

      Quote comparison

      Quote comparison

      | Date checked | Vendor/source | Configuration | Required capabilities met | One-time cost | Recurring cost | Availability | Accessibility notes |

      | --- | --- | --- | --- | --- | --- | --- | --- |

      diff --git a/docs/templates/source-verification-record.html b/docs/templates/source-verification-record.html index 72efe10..a5c6ed4 100644 --- a/docs/templates/source-verification-record.html +++ b/docs/templates/source-verification-record.html @@ -1,4 +1,5 @@ -Source-verification record — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
      Guide home

      Source-verification record

      Source-verification record

      +Source-verification record — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
      Guide home

      Source-verification record

      Source-verification record

      • Claim or question:

      • Responsible jurisdiction and authority:

      diff --git a/docs/templates/technology-plan.html b/docs/templates/technology-plan.html index 65db51f..931ffa2 100644 --- a/docs/templates/technology-plan.html +++ b/docs/templates/technology-plan.html @@ -1,4 +1,5 @@ -Technology plan — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Technology plan

      Technology plan

      +Technology plan — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Technology plan

      Technology plan

      | Work task | Barrier | Required capability | Minimum | Preferred | Alternatives | Evidence needed |

      | --- | --- | --- | --- | --- | --- | --- |

      diff --git a/docs/templates/training-plan.html b/docs/templates/training-plan.html index ad4b420..9650272 100644 --- a/docs/templates/training-plan.html +++ b/docs/templates/training-plan.html @@ -1,4 +1,5 @@ -Training plan — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Training plan

      Training plan

      +Training plan — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Training plan

      Training plan

      • Vocational outcome:

      • Entry skills and evidence:

      diff --git a/docs/tracks/audio.html b/docs/tracks/audio.html index c41e132..16e9fc0 100644 --- a/docs/tracks/audio.html +++ b/docs/tracks/audio.html @@ -1,4 +1,5 @@ -Audio track — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Audio track

      Audio track

      +Audio track — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Audio track

      Audio track

      Work tasks

      Record, edit, arrange, mix, monitor, collaborate, export, document rights and versions, and archive sessions.

      Required capabilities

      diff --git a/docs/tracks/design.html b/docs/tracks/design.html index 0d2f4cd..8120768 100644 --- a/docs/tracks/design.html +++ b/docs/tracks/design.html @@ -1,4 +1,5 @@ -Design track — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Design track

      Design track

      +Design track — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Design track

      Design track

      Work tasks

      Research, sketch, compose, prototype, review, revise, export, and prepare assets for production or handoff.

      Required capabilities

      diff --git a/docs/tracks/duet-development-provenance.html b/docs/tracks/duet-development-provenance.html index dec56b8..ebb57b3 100644 --- a/docs/tracks/duet-development-provenance.html +++ b/docs/tracks/duet-development-provenance.html @@ -1,4 +1,5 @@ -Veiled Dominion / Duet development provenance — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Veiled Dominion / Duet development provenance

      Veiled Dominion / Duet development provenance

      +Veiled Dominion / Duet development provenance — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Veiled Dominion / Duet development provenance

      Veiled Dominion / Duet development provenance

      This is the development-training reference for the current Duet architecture. It teaches the actual lineage from the original Pulsr work through the current production/playtest build, the architecture laboratory, and the permanent Loptr Lab engine.

      The source-of-truth flow

      ```text

      diff --git a/docs/tracks/game-development.html b/docs/tracks/game-development.html index 5622020..eac02c6 100644 --- a/docs/tracks/game-development.html +++ b/docs/tracks/game-development.html @@ -1,4 +1,5 @@ -Game development track — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Game development track

      Game development track

      +Game development track — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Game development track

      Game development track

      Work tasks

      Implement and test game systems, use an engine and source control, create or integrate assets, profile performance, run playtests, and document production handoffs.

      Required capabilities

      diff --git a/docs/tracks/hybrid-creative-technology.html b/docs/tracks/hybrid-creative-technology.html index cff29cf..8c43257 100644 --- a/docs/tracks/hybrid-creative-technology.html +++ b/docs/tracks/hybrid-creative-technology.html @@ -1,4 +1,5 @@ -Hybrid creative-technology track — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Hybrid creative-technology track

      Hybrid creative-technology track

      +Hybrid creative-technology track — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Hybrid creative-technology track

      Hybrid creative-technology track

      Work tasks

      Combine code, interactive media, audio, video, design, automation, documentation, and production coordination into an integrated workflow.

      Required capabilities

      diff --git a/docs/tracks/index.html b/docs/tracks/index.html index 17b5e41..2173c66 100644 --- a/docs/tracks/index.html +++ b/docs/tracks/index.html @@ -1,4 +1,5 @@ -Career tracks — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      ← Guide home

      Career tracks

      Choose the work before the equipment

      See development equipment requirements →

      Choose the work you want to do before comparing equipment. For every track, document: work tasks, software and workflow requirements, compute requirements, accessibility considerations, minimum and preferred capabilities, and questions requiring individual assessment.

      +Career tracks — Loptr Lab +
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      ← Guide home

      Career tracks

      Choose the work before the equipment

      See development equipment requirements →

      Choose the work you want to do before comparing equipment. For every track, document: work tasks, software and workflow requirements, compute requirements, accessibility considerations, minimum and preferred capabilities, and questions requiring individual assessment.

PathWhat you need to demonstrateEquipment approach
Learning and web codingEdit code, use source control, preview accessible pages and run basic testsBrowser-based editor or accessible local editor, dependable internet access, keyboard or alternate input, backup and authentication
diff --git a/docs/tracks/maker-game-systems.html b/docs/tracks/maker-game-systems.html index d5181ec..336f6d1 100644 --- a/docs/tracks/maker-game-systems.html +++ b/docs/tracks/maker-game-systems.html @@ -1,4 +1,5 @@ -Optional maker pathway: game rules and physical interaction — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

Guide home

Optional maker pathway: game rules and physical interaction

Optional maker pathway: game rules and physical interaction

+Optional maker pathway: game rules and physical interaction — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

Guide home

Optional maker pathway: game rules and physical interaction

Optional maker pathway: game rules and physical interaction

Status: proposed, source-based learning pathway. The case studies are at different stages; neither is a verified hardware build or a demonstrated learner outcome.

Study two directions of translation: a pinball machine simulated in software, and turn-based Duet software considered for a physical LED chessboard. They differ in feedback tempo and access needs. Pinball demands real-time motor input and immediate state feedback; chess allows deliberate turns but must replace browser screen-reader feedback when moved to a standalone board.

TrackBegin with these tasks
Software developmentEdit code, run tests, manage versions, collaborate.
diff --git a/docs/tracks/software-development.html b/docs/tracks/software-development.html index ff1904f..c77624b 100644 --- a/docs/tracks/software-development.html +++ b/docs/tracks/software-development.html @@ -1,4 +1,5 @@ -Software development track — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

Guide home

Software development track

Software development track

+Software development track — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

Guide home

Software development track

Software development track

Work tasks

Read and edit code, navigate repositories, run builds and tests, debug, review changes, manage versions, communicate decisions, and use documentation.

Required capabilities

diff --git a/docs/tracks/video.html b/docs/tracks/video.html index 439a5cb..924585a 100644 --- a/docs/tracks/video.html +++ b/docs/tracks/video.html @@ -1,4 +1,5 @@ -Video track — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

Guide home

Video track

Video track

+Video track — Loptr Lab +
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

Guide home

Video track

Video track

Work tasks

Plan and capture footage, ingest media, edit picture and sound, review detail, create captions, render, deliver, and archive projects.

Required capabilities

diff --git a/docs/training-display.js b/docs/training-display.js new file mode 100644 index 0000000..75afadb --- /dev/null +++ b/docs/training-display.js @@ -0,0 +1,36 @@ +/* Optional device-local reading preferences. No requests or participant data. */ +(() => { + 'use strict'; + const root = document.documentElement; + const key = 'loptr-training-display'; + let preferences = { theme: 'dark', size: 'standard' }; + try { + const saved = JSON.parse(localStorage.getItem(key)); + if (saved && ['dark', 'light', 'system'].includes(saved.theme)) preferences.theme = saved.theme; + if (saved && ['standard', 'large', 'largest'].includes(saved.size)) preferences.size = saved.size; + } catch (_) { /* Reading remains available when storage is blocked. */ } + const system = window.matchMedia('(prefers-color-scheme: dark)'); + function apply() { + root.dataset.theme = preferences.theme === 'system' ? (system.matches ? 'dark' : 'light') : preferences.theme; + root.dataset.textSize = preferences.size; + } + apply(); + system.addEventListener('change', apply); + document.addEventListener('DOMContentLoaded', () => { + const header = document.querySelector('.masthead'); + if (!header) return; + const settings = document.createElement('details'); + settings.className = 'display-settings'; + settings.innerHTML = 'Reading settings
'; + header.prepend(settings); + const theme = settings.querySelector('[name=training-theme]'); + const size = settings.querySelector('[name=training-text-size]'); + theme.value = preferences.theme; + size.value = preferences.size; + settings.addEventListener('change', () => { + preferences = { theme: theme.value, size: size.value }; + apply(); + try { localStorage.setItem(key, JSON.stringify(preferences)); } catch (_) { /* Session-only fallback. */ } + }); + }); +})(); diff --git a/docs/training.css b/docs/training.css index 115af69..aad06c5 100644 --- a/docs/training.css +++ b/docs/training.css @@ -1,61 +1,42 @@ -:root{--paper:#eee9dc;--ink:#151515;--blue:#173d62;--orange:#d66b20;--line:#1b2731} +/* Loptr Lab Training: one shared stylesheet. Palette/type: veiled-dominion-engine/docs/design/DESIGN_BIBLE.md. +Gold marks links/labels, never fills. Muted text is raised for readable contrast. */ +:root{color-scheme:dark;--void:#050505;--surface:#141414;--text-primary:#e0e0e0;--text-muted:#b5b5b5;--the-light:#d4a853;--line:#777;--font-main:'Helvetica Neue',Helvetica,Arial,sans-serif;--reading-size:1.125rem;--gutter:clamp(1rem,4vw,3rem)} +:root[data-theme=light]{color-scheme:light;--void:#d9d9d6;--surface:#e6e6e3;--text-primary:#171717;--text-muted:#454545;--the-light:#72521b;--line:#777} +:root[data-text-size=large]{--reading-size:1.3125rem} +:root[data-text-size=largest]{--reading-size:1.5rem} *{box-sizing:border-box} -html{font-family:Arial,Helvetica,sans-serif;background:var(--paper);color:var(--ink)} -body{margin:0;min-height:100vh;background:linear-gradient(rgba(0,0,0,.025) 1px,transparent 1px),var(--paper);background-size:100% 4px} -.scanlines{position:fixed;inset:0;pointer-events:none;opacity:.08;background:repeating-linear-gradient(0deg,transparent 0,transparent 2px,#111 3px);z-index:5} -.masthead,main,footer{max-width:1100px;margin:auto} -.masthead{padding:2rem 1.25rem 1rem;border-left:8px solid var(--blue);border-right:8px solid var(--blue)} -.serial,.eyebrow,.panel-head,.statusbar,footer{font:700 .72rem/1.4 "Courier New",monospace;letter-spacing:.08em} -.serial{color:var(--blue)} -h1{font:900 clamp(2.5rem,8vw,6rem)/.9 Impact,"Arial Narrow",sans-serif;letter-spacing:.03em;margin:.5rem 0 0} -.subtitle{font:800 clamp(1rem,3vw,1.7rem)/1 "Arial Narrow",Arial,sans-serif;letter-spacing:.18em;margin:.5rem 0 1.25rem} -.statusbar{display:flex;gap:1rem;flex-wrap:wrap;border-block:2px solid var(--ink);padding:.65rem 0} -.statusbar span:first-child{color:var(--orange)} -main{padding:1rem 1.25rem 3rem} -.brief{border:3px solid var(--ink);padding:1.5rem;background:#f5f0e4;box-shadow:8px 8px 0 var(--blue)} -h2{font:900 clamp(1.8rem,5vw,3.5rem)/1 Impact,"Arial Narrow",sans-serif;margin:.25rem 0 .75rem} -.lead{font-size:1.2rem;max-width:760px} -.path{display:flex;flex-wrap:wrap;gap:.45rem;align-items:center;margin-top:1.25rem;font:800 .85rem "Courier New",monospace} -.path span{border:2px solid var(--ink);padding:.45rem .55rem;background:#fff} -.path b{color:var(--orange)} -.grid{display:grid;grid-template-columns:repeat(2,1fr);gap:1rem;margin-top:2rem} -.panel{border:2px solid var(--line);padding:1.2rem;background:rgba(255,255,255,.35);min-height:240px} -.panel-head{color:var(--blue);border-bottom:1px solid var(--line);padding-bottom:.5rem} -h3{font:900 1.5rem "Arial Narrow",Arial,sans-serif;letter-spacing:.05em} -dl{font:700 .75rem "Courier New",monospace;display:grid;grid-template-columns:110px 1fr;gap:.4rem;margin:1rem 0} -dt{color:var(--orange)}dd{margin:0} -.button{display:inline-block;border:2px solid var(--ink);padding:.65rem .8rem;color:var(--ink);text-decoration:none;font:800 .72rem "Courier New",monospace;background:#fff} -.button:hover,.button:focus{background:var(--blue);color:#fff} -.violet{margin-top:2rem;background:var(--blue);color:#fff;padding:1.5rem;border:3px solid var(--ink)} -.violet .eyebrow{color:#f3b36c}.directive{font:900 1.2rem/1.4 "Courier New",monospace;color:#f3b36c} -footer{padding:1.5rem 1.25rem;border-top:3px solid var(--ink);display:flex;justify-content:space-between;gap:1rem;flex-wrap:wrap} -@media(max-width:700px){.grid{grid-template-columns:1fr}.masthead{border-width:4px}.path b{display:none}.path{display:grid;grid-template-columns:1fr 1fr}.path span{width:max-content}} -@media(prefers-reduced-motion:reduce){*{scroll-behavior:auto!important;transition:none!important}.scanlines{display:none}} -@media(prefers-contrast:more){.panel,.brief,.violet,.button{border-width:3px}} -.skip-link{position:absolute;left:1rem;top:-5rem;z-index:10;padding:.75rem 1rem;background:#fff;color:#111}.skip-link:focus{top:1rem} -.actions{display:flex;flex-wrap:wrap;gap:.75rem;margin-top:1.5rem} -.journey{display:grid;gap:.8rem;padding-left:1.5rem} -.checks{display:grid;grid-template-columns:repeat(auto-fit,minmax(14rem,1fr));gap:.5rem 1.5rem} -.table-wrap{overflow-x:auto}table{width:100%;border-collapse:collapse}th,td{padding:.8rem;border:1px solid currentColor;text-align:left;vertical-align:top} -a:focus-visible,button:focus-visible{outline:3px solid var(--orange);outline-offset:3px} - -/* Readable, consistent guide pages */ -.guide{max-width:900px;margin:0 auto;font-size:1.075rem;line-height:1.65;overflow-wrap:anywhere} -.guide h2{font-size:clamp(1.65rem,4vw,2.5rem);margin:2rem 0 .75rem;line-height:1.15} -.guide p{max-width:75ch} -.guide li{margin-bottom:.65rem;padding-left:.2rem} -.guide ul,.guide ol{padding-left:1.6rem} -.guide a{color:var(--blue);text-underline-offset:.17em;text-decoration-thickness:2px} -.guide a:hover{color:#954213} -.guide table{background:#fff;line-height:1.5} -.guide tr:first-child{font-weight:700;background:#e4eaf0} -.guide td{min-width:10rem} -.guide a:focus-visible{outline-offset:4px} -@media(max-width:700px){ - .masthead h1{font-size:clamp(2.4rem,11vw,4rem);line-height:1;overflow-wrap:break-word} - .subtitle{font-size:clamp(1.05rem,4.5vw,1.4rem);line-height:1.35;letter-spacing:.035em} - .actions{display:grid;grid-template-columns:1fr} - .button{display:block;max-width:100%;font-size:.95rem;line-height:1.35;padding:.85rem 1rem;overflow-wrap:anywhere} - .guide{font-size:1rem;padding:1.1rem;box-shadow:4px 4px 0 var(--blue)} - .guide td{min-width:8.5rem} -} \ No newline at end of file +html{background:var(--void);color:var(--text-primary);font-family:var(--font-main);scroll-padding-top:1rem} +body{margin:0;font-size:var(--reading-size);line-height:1.65;background:var(--void);overflow-wrap:anywhere} +.masthead,main,footer{width:min(calc(100% - 2 * var(--gutter)),72rem);margin-inline:auto;min-width:0} +.masthead{padding-block:2rem 1.5rem;border-bottom:1px solid var(--line)} +.serial,.eyebrow,.panel-head{color:var(--the-light);font:600 .9em/1.5 var(--font-main);letter-spacing:.025em} +h1,h2,h3{font-family:var(--font-main);font-weight:500;letter-spacing:normal;line-height:1.25;margin:0 0 1rem;text-wrap:pretty;overflow-wrap:break-word} +h1{font-size:clamp(2.1em,4.5vw,3.5em);margin-top:1rem;max-width:22ch} +h2{font-size:clamp(1.6em,3vw,2.25em)}h3{font-size:1.3em} +.subtitle,.lead{font-size:1.15em;line-height:1.6;max-width:65ch;color:var(--text-muted);letter-spacing:normal;font-weight:400} +p,ul,ol,dl{margin:0 0 1.25rem}p{max-width:72ch}ul,ol{padding-left:1.5em}li+li{margin-top:.6em} +a{color:var(--the-light);text-underline-offset:.2em}a:hover{text-decoration-thickness:.15em} +button,input,select,textarea{font:inherit}button,select{min-height:3rem;background:var(--surface);color:var(--text-primary);border:1px solid var(--line);border-radius:.5rem;padding:.5rem .75rem} +:focus-visible{outline:3px solid var(--the-light);outline-offset:4px} +main{padding-block:1.5rem 3rem}main>section+section{margin-top:2rem} +.brief,.panel{border:1px solid var(--line);padding:clamp(1rem,3vw,2rem);background:var(--surface);border-radius:.75rem;box-shadow:none;min-width:0} +.panel-head{margin-bottom:1rem}.featured-resource{border-inline-start:3px solid var(--the-light)} +.featured-resource .eyebrow{margin-bottom:.75rem}.featured-resource p{max-width:70ch}.featured-resource .notice{margin-top:1.25rem} +.notice,footer{color:var(--text-muted)}.notice{font-size:.9em} +.actions{display:flex;flex-wrap:wrap;align-items:center;gap:.75rem 1rem;margin-top:1.25rem} +.button{display:inline-flex;align-items:center;justify-content:center;min-height:3rem;padding:.65rem 1rem;border:1px solid var(--line);border-radius:.5rem;background:transparent;color:var(--the-light);font:600 1em/1.45 var(--font-main);text-align:left;text-decoration:none;max-width:100%} +.button:hover{border-color:var(--the-light);text-decoration:underline} +.grid{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:1.5rem;margin-top:2rem}.grid>*{min-width:0} +.journey{display:grid;gap:.5rem}.checks{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,16rem),1fr));gap:.5rem 1.5rem} +.table-wrap{overflow-x:auto;max-width:100%}table{width:100%;border-collapse:collapse}th,td{padding:.8rem;border:1px solid var(--line);text-align:left;vertical-align:top}th{font-weight:650} +.guide{max-width:72rem;line-height:1.65}.guide h2{margin-top:2rem}.guide>h2:first-child{margin-top:0}.guide table{background:var(--surface)} +dl{display:grid;grid-template-columns:minmax(0,1fr) minmax(0,3fr);gap:.5rem 1rem}dt{font-weight:650;color:var(--the-light)}dd{margin:0} +footer{padding-block:2rem;border-top:1px solid var(--line);font-size:1em;display:block}footer p{max-width:75ch} +.display-settings{margin-bottom:1.5rem}.display-settings summary{cursor:pointer;color:var(--the-light);min-height:3rem;padding-block:.5rem;width:fit-content} +.display-controls{display:flex;flex-wrap:wrap;gap:1rem 2rem;margin-block:.5rem 1rem}.display-controls label{display:flex;flex-direction:column;gap:.4rem;font-size:1em;min-width:min(100%,12rem)} +.skip-link{position:absolute;top:0;left:var(--gutter);transform:translateY(-150%);z-index:100;background:var(--surface);color:var(--the-light);padding:1rem}.skip-link:focus{transform:translateY(0)} +.scanlines{display:none}.statusbar,.path{display:flex;flex-wrap:wrap;gap:1rem}.violet{margin-top:2rem;padding:1.5rem;border:1px solid var(--line);background:var(--surface)}.directive{color:var(--the-light)} +img,svg,video,iframe{max-width:100%}img{height:auto}code{overflow-wrap:anywhere} +@media(max-width:44rem){.grid{grid-template-columns:1fr}.actions{align-items:stretch}.actions .button{flex:1 1 100%;justify-content:flex-start}h1{font-size:2.1em}.masthead h1 br{display:none}.display-controls{flex-direction:column}dl{grid-template-columns:1fr}} +@media(prefers-reduced-motion:reduce){*{scroll-behavior:auto!important;animation:none!important;transition:none!important}} +@media(forced-colors:active){.brief,.panel,.button,select{border:1px solid CanvasText}:focus-visible{outline-color:Highlight}}