accessibilitywars/zaw2

LARGE TASK: Remove armory-embeds

Open

#13 opened on Mar 14, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (5 forks)auto 404
enhancementhelp wantedroundtuit

Repository metrics

Stars
 (1 star)
PR merge metrics
 (PR metrics pending)

Description

Armory-embeds works well enough, but it doesn't truly fit the model of a static site.

If we were to build our own 'armory-alike' system that used static generation, AW2 could have offline capabilities and work cleanly as a cached progressive web app.

Additionally, this means that aw2 would continue to function if the API broke (or was deactivated). It also allows for the ability to supplement or modify the api data in cases where it is incorrect or incomplete.

This is a big job and should be broken down further.

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.