Sacha Greif

I'm going to start marking locales an "inactive" when their translations are too out of date. Inactive locales won't appear as selectable options when taking the surveys or browsing the...

Let's discuss ideas for improving the translation system. I think a good start could be having an auto-generated notification feed of any changes/additions to `locale-en-US`. Or maybe even automatically create...

When you land on the form with a source tag we store that somewhere and then use it in the next survey you take. We should probably have a time...

Currently, an alias defined in `locale-en-US` is only effective there. Change it so that it's effective for all locales, *except* if said locale has its own alias or string definition

No way to clear select inputs (or radio buttons) currently?

Radio buttons in Featurev3 questions are deselectable, but not the ones in standard radiogroup questions.

We could have a table of contents at the start of the entire survey that lets people uncheck sections they don't intend to answers or are not relevant to them,...

Add an option to prefill "about you" data from last filled out survey.

Currently: `document.tools.front_end_frameworks_pain_points` Migrate to: `document.front_end_frameworks_pain_points` - Note: ensure every question id is unique within a survey edition first.

Currently, `results` uses a lot of survey-specific code (components, configs, etc.) which is all imported using webpack alias. But that means it has to live in `monorepo` instead of `surveys`....