Settings transitions seem to be a bottleneck when working with the tools. The null is essentially the best-of with no candidates. Also, most of the blocks have only 1 state. Therefore:

• by default, with no transition, use the next transition mode;
• for blocks with multiple states, convert all explicit null transitions into best-of transitions with 0 candidates.

• ButtonDelete with confirmation & color highlight.
• ToggleGroup with ability to set off completely.
• StateTransitionEditor with empty, next & best-of options.
• StateDisplayEditor with glossing & entity coloring.

• Enable overwritten tags reading.
• Enable overwritten tags editing in Phonology editor.

Some people mostly use converter functionality. Develop new UI layout where the phonetical table doesn't stand in their way.

Add the ability to specify and highlight multiple graphical representations of the same phoneme in a single lect. For example, in Kaitag for phoneme /e/ there are 2 graphemes: ⟨э⟩, ⟨е⟩.

🔉 Phonology

• Consider reorganizing ids to use properties instead of keys.
• Populate phonetic IPA database.
• Convert phonetic IPA database into object-array instead of key-value pairs.

🔃 Converter

• Implement Dropdown component for mapping selection.
• Implement Toggle component for bool toggling.
• Fix defaults sample handling.

🏠 Home

• Implement a new lect card with a new catalog structure.
• Add map markers for selected lects.
• Add lects search.

🛠 Editors

• Phonology editor.
• Converter editor.
• Editors navigation.

Add CSS tooltips for icon-only buttons.

Based on Nord palette

• Add support in PhraseBlock.
• Add support in PhrasebookEditor.

Add option to display phonemes grouped by their phonemic features.

Replace hard coded CSS color hexes with Nord palette references.

• Update color styling.
• Create separate color palettes for dark & light modes with css variables.
• Only give necessary info.

Implement modular and queriable phonetical table

In order to fascilitate state management (and for sake of learnin a new technology) explore how VueX can benefit the project.

Implement proper routing, history and ability to refer to specific view & language by passing url arguments into the address bar.

Migrate existing JS codebase into TS

• Group phrases by categories.
• Search phrases.

• Display & color text, ipa & glossing segments.
• Computed property for copying.
• Unify 3 strings into one data structure.

Rewrite current vanilla-js implementation with Vue.js in order to set a solid foundation for the future progress.

Implement script converter section for a language:

• real-time textfield conversion
• copy result to clipboard
• choose from multiple mappings
• upload .txt file
• display mapping table

Add "Work In Progress" label at some home language cards to indicate their content status.

• Header navigation.
• File serialization & deserealization (keep separate record for each editor).
• File actions (load least, load json, etc.).

Restore URL functionality after updating Lects architecture:

• Home (selected lects, zoom, position);
• Phonology (phoneme, lects filter);
• Converter (lect, source mapping, destination mapping);
• Phrasebook (phrase, section).

Try to utilize MapBox GL JS API directly, without leaflet package mediator.

• Context source.
• Context translation.
• Conditions.

Configure the hosting server accordingly.

Develop a prototype dictionary module, allowing to directly map words between our languages based on their English translation. It is not perfect, but it should be good enough.

Create db branch in the repository to hold all language data that is currently stored in public/lects. This should make it easier to contribute and allows for a cleaner project structure. Definitely would need the ability to still utilize local data for rapid development.

Although lects/phrasebook.json does not have "it" tagged as second. It receives the second tag in the interactive phrasebook screen.

• Show default text if glossing fields are empty.
• Allow glossing preview in phrasebook editor.

Create wiki pages about, remove all panel captions from, and add the corresponding links for:

• Phonology
• Converter
• Phrasebook

As the cost of maintaining custom CSS elements raises, migrate the project onto using scss preprocessor.

Find a way to play .m4a files without use of 3rd party libraries.

Steps to reproduce:

1. Create two entities for a phrase, for example Plurality and Proximity.
2. In the editor, when modifying a phrase, both will show the same tags as whichever is created first.
3. Save the JSON, making sure to double check that the tag values are not overwritten. I noticed that once or twice when playing around with this issue, the actual tag values were being overwritten in the phrasebook.json file.
4. Compare behavior in the normal interactive editor screen, where this tag overwritting does not occur.

Compare interactive mode:

Versus editor mode:

Example below:

{
    "id": "55fe6d97-c8ec-4637-9749-b8c4c85e5d7d",
    "name": "Test Section",
    "phrases": [
      {
        "id": "92a1654f-db81-4377-87a4-bd8ab2eb31fd",
        "preview": "Testing",
        "context": [
          {
            "entity": "plurality",
            "tags": "singular plural"
          },
          {
            "entity": "proximity",
            "tags": "near far"
          }
        ],
        "blocks": [
          {
            "states": [
              {
                "display": [
                  {
                    "text": "This"
                  }
                ],
                "transition": "next",
                "conditions": [
                  {
                    "entity": "plurality",
                    "tag": "singular"
                  },
                  {
                    "entity": "proximity",
                    "tag": "near"
                  }
                ]
              },
              {
                "display": [
                  {
                    "text": "That"
                  }
                ],
                "transition": "next",
                "conditions": [
                  {
                    "entity": "plurality",
                    "tag": "singular"
                  },
                  {
                    "entity": "proximity",
                    "tag": "far"
                  }
                ]
              },
              {
                "display": [
                  {
                    "text": "These"
                  }
                ],
                "transition": "next",
                "conditions": [
                  {
                    "entity": "plurality",
                    "tag": "plural"
                  },
                  {
                    "entity": "proximity",
                    "tag": "near"
                  }
                ]
              },
              {
                "display": [
                  {
                    "text": "Those"
                  }
                ],
                "transition": "next",
                "conditions": [
                  {
                    "entity": "proximity",
                    "tag": "far"
                  },
                  {
                    "entity": "plurality",
                    "tag": "plural"
                  }
                ]
              }
            ]
          },
          {
            "states": [
              {
                "display": [
                  {
                    "text": "is"
                  }
                ],
                "transition": "next",
                "conditions": [
                  {
                    "entity": "plurality",
                    "tag": "singular"
                  }
                ]
              },
              {
                "display": [
                  {
                    "text": "are"
                  }
                ],
                "transition": "next",
                "conditions": [
                  {
                    "entity": "plurality",
                    "tag": "plural"
                  }
                ]
              }
            ]
          },
          {
            "states": [
              {
                "display": [
                  {
                    "text": "a"
                  }
                ],
                "conditions": [
                  {
                    "entity": "plurality",
                    "tag": "singular"
                  }
                ]
              }
            ],
            "requirements": [
              {
                "entity": "plurality",
                "tag": "singular"
              }
            ]
          },
          {
            "states": [
              {
                "display": [
                  {
                    "text": "test"
                  }
                ],
                "transition": "next",
                "conditions": [
                  {
                    "entity": "plurality",
                    "tag": "singular"
                  }
                ]
              },
              {
                "display": [
                  {
                    "text": "tests"
                  }
                ],
                "transition": "next",
                "conditions": [
                  {
                    "entity": "plurality",
                    "tag": "plural"
                  }
                ]
              }
            ]
          }
        ]
      }
    ]
  }

Using phoneme-grapheme pairs, try to approximate text from one language into another by utilizing phoneme approximation similar to how it work during language acquisition.

Utilize vector tiles in Leaflet instead of raster tiles to increase loading speed & performance.