sillsdev / sillsdev/languageforge-lexbox

Develop communication with our users

Open
#610 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

📦 Lexbox documentation research task
Dominant language
C#
Stars
9
Forks
8
Avg merge
2d 13h
Merged PRs (30d)
49

Description

At our last retro we ALL brought up the point that we want to improve communication with our users.
Here are our favorite ideas:

Asynchronous: News channel
  • We'd like to let interested users know about the biggest changes we ship. A (quarterly?) email newsletter might be the right medium. Potentially we'd want to just contribute to LT News?
Synchronous: Open Zoom meeting
  • As an experiment, send a Zoom meeting invitation to (all?) LexBox users. It's an opportunity for them to ask questions and for us to gather feedback and insight from the field.
Groundwork

We don't want our Zoom meeting to be about teaching users the basic functionality of LexBox. So, there should be some basic documentation that users can reference before the Zoom meeting.

  • #689

Here were all of our ideas for the sake of completeness

Ideas:

  • email newsletter (quarterly - examples of newsletters: Paratext and LT News)
  • Email survey
  • in app feedback button
  • host a meeting with users (fireside chat)
  • LT webinar?
  • Cover the 4 or 5 mail worokflows with Scribe

image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the completed #689 groundwork first to understand which user documentation already exists. The issue still needs a decision about the newsletter, Zoom meeting, or another communication approach before work can start; define one selected experiment and its completion criteria.

Written by the indexing model from the issue text.

Assessment

Domain
content, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.