WORKFLOW EXPLORATION • discussion draft
Dictionary contribution & publication

Remove bottlenecks.
Preserve linguistic authority.

A visual conversation starter about how contributors, reviewers, FLEx and Payload could work together. This is a hypothesis, not an approved implementation plan.

Independent HTML + CSSNo live dataNo project dependencies
01

Where work may be concentrated

Illustrative current workflow — confirm the actual handoffs with the team.

01 · InputTeam & contributorsIdeas, corrections, audio, examples
→
02 · CoordinationCentral maintainerCollects and interprets requestsPossible queue bottleneck
→
03 · Lexical dataFLEx updatesStructured dictionary editingPossible specialist bottleneck
→
04 · DeliveryExport → websiteImport, validate and publish

Observed direction: the team provides input and Aandeg handles FLEx updates. Exact review, export and publishing responsibilities still need verification.

02

A possible distributed workflow

Separate proposing changes from approving and publishing them.

01 · ContributeSubmission formNew entries, corrections, recordings
→
02 · OrganizeShared review queueOwnership, status, history
→
03 · DecideLinguistic reviewQualified reviewers retain authority
→
04 · IntegrateAuthoritative recordValidated change, provenance
→
05 · PublishPublic dictionaryOnly approved, synchronized data
Approval ≠ publication. An accepted proposal should enter a deliberate integration process. The team must decide which system owns the canonical lexical record.
03

Four different bottlenecks

Each problem requires a different intervention.

INTAKE

Contribution

Requests arrive through scattered messages or meetings.

Possible response

Structured submissions and a visible queue.

EXPERTISE

Linguistic review

Only one qualified person may be able to verify changes.

Possible response

Reviewer roles, triage, and clear escalation rules.

TOOLING

FLEx entry

Accepted changes may require repetitive manual editing.

Possible response

Investigate safe batch workflows and synchronization.

RELEASE

Publication

Export and import may require developer involvement.

Possible response

Validated admin imports with preview and rollback.

04

Three architectural choices

These are options to evaluate, not decisions already made. Select a card for more detail.

A

FLEx authoritative

Preserves existing lexical structure and practices.

Tradeoff: manual handoffs may remain.
C

Payload authoritative

Direct web-based maintenance and publication.

Tradeoff: migration, linguistic structure and divergence risks.
05

Questions before implementation

Use these to guide a meeting, rather than to prescribe a solution.

01

Is FLEx intended to remain the permanent source of truth?

02

Who can submit, review, approve, integrate and publish changes?

03

Where do requests wait the longest today?

04

How are approved changes returned to FLEx and synchronized to the website?

05

What small improvement could be piloted without changing canonical data?

Start with visibility.
Then automate the right handoff.

Suggested first experiment: a separate submission and review queue, with no direct writes to published dictionary entries until ownership and synchronization rules are agreed.

06

Share your experience

Help us understand how people contribute to and maintain the dictionary.

A short team questionnaire · approximately 5–8 minutes

You don't need technical knowledge to participate. We're interested in what you actually do, what works, and what could be easier. There are no right or wrong answers. Skip anything that doesn't apply to you.

Responses will inform recommendations and user stories; technical and project decisions remain with the appropriate team members. Please avoid including confidential dictionary content or personal information about others.

01 / 05

Your involvement

1. What is your involvement with the dictionary? Select all that apply.
2. How familiar are you with the process for updating dictionary entries?
02 / 05

How work happens today

3. How do you currently submit, receive, or work on dictionary changes? Select all that apply.
03 / 05

Difficulties and delays

5. Which parts of updating the dictionary are difficult or time-consuming? Select all that apply.
6. Where do changes tend to spend the most time waiting?
04 / 05

What would help?

8. Which improvements would make your work easier? Choose up to three.
05 / 05

Care and responsibilities

11. When someone proposes a change, how clear is it who should review and approve it?
Ready to share?

Answers are optional. Responses are stored for the project discussion; please submit only once.

How it works

    Advantages

      Tradeoffs and risks

        Possible first experiment

        Question for the team