getodk / getodk/web-forms

Accept and use style/theming configuration

Open
#43 2 comments 0 reactions 0 assignees View on GitHub
enhancement front-end
Dominant language
TypeScript
Stars
38
Forks
22
PR merge metrics
No merged PRs in 30d

Description

## User Story
As a ODK project manager
I want to specify simple style customizations
So that my forms can match my branding

(Decide whether in scope/a separate issue)
As the developer of an application that uses ODK Web Forms
I want to specify a completely custom style
So that my forms can match the host application

## Questions
* Do we want to make it easy for people to opt out of Material/specify their own design language?
* What colors? Do we generate palette?
* Is passing in something like a logo image a theming concern?
* Do we allow for a preamble and suffix? Or is that a responsibility of the host app?
* Are we comfortable deferring the scope to whatever component framework we pick?
* If we defer to the component framework, should we still subset what we expose?
* Maybe styling is expressed as a CSS blob

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue does not name any files, tests, or entry points. First resolve the open scope questions around Material, custom designs, colors, logos, preambles, and CSS blobs, then identify the component framework and theming entry points. Done should mean a defined, implementable theming configuration with agreed boundaries and acceptance criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.