Contribution
Requests arrive through scattered messages or meetings.
Possible responseStructured submissions and a visible queue.
A visual conversation starter about how contributors, reviewers, FLEx and Payload could work together. This is a hypothesis, not an approved implementation plan.
Illustrative current workflow — confirm the actual handoffs with the team.
Observed direction: the team provides input and Aandeg handles FLEx updates. Exact review, export and publishing responsibilities still need verification.
Separate proposing changes from approving and publishing them.
Each problem requires a different intervention.
Requests arrive through scattered messages or meetings.
Possible responseStructured submissions and a visible queue.
Only one qualified person may be able to verify changes.
Possible responseReviewer roles, triage, and clear escalation rules.
Accepted changes may require repetitive manual editing.
Possible responseInvestigate safe batch workflows and synchronization.
Export and import may require developer involvement.
Possible responseValidated admin imports with preview and rollback.
These are options to evaluate, not decisions already made. Select a card for more detail.
Preserves existing lexical structure and practices.
Payload receives submissions and review activity; FLEx remains the canonical lexical record.
Direct web-based maintenance and publication.
Use these to guide a meeting, rather than to prescribe a solution.
Is FLEx intended to remain the permanent source of truth?
Who can submit, review, approve, integrate and publish changes?
Where do requests wait the longest today?
How are approved changes returned to FLEx and synchronized to the website?
What small improvement could be piloted without changing canonical data?
Suggested first experiment: a separate submission and review queue, with no direct writes to published dictionary entries until ownership and synchronization rules are agreed.
Help us understand how people contribute to and maintain the dictionary.
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.