Explain beta

[amyjko]

What's the problem?

When visitors reach the landing page, the only signal that the site is beta is the small label at the bottom. We need a much stronger set of expectation setting, so that people don't expect everything to work, and help report issues.

What's the idea?

Perhaps a special paragraph at the top that goes to the milestone page.

Who benefits?

Every visitor.

Design ideas

TBD

[amyjko]

@kelliannr, I see you added yourself to this. Did you want to work on this? I was just going to add some text to the landing page.

[amyjko]

Remember, if someone is already assigned an issue, you need to explicitly coordinate with them, otherwise they don't know that you're also working on it. Explicit communication is essential to avoiding conflicts and redundant work. For example, I was planning on working on this issue this morning, but now I don't know if I should, because maybe you're working on it too? Please communicate your plans.

[kelliannr]

Hello, sorry for the late reply! Me and Megan started working on this on Tuesday and were putting together a design to show you for approval. Here is what we have so far:

Not fully fleshed out yet, but thats what we have

[amyjko]

I like the visual design! A few notes:

• It should use the existing color palette defined in global.css, rather than using any new hard coded colors
• I think the message needs to be tweaked a bit, to include a link to where to report issues. (The current beta link in the footer goes there, but that will be less discoverable).
• What about just replacing function's speech bubble text with the beta text? That takes up less space, and is more prominent.
• This needs to be localized, so you'll need to coordinate with the Chinese and Spanish team for translations.

This must be built ASAP, since we release in 11 days. I can do it quickly, or you could find a developer who wants to take it on and is willing to do it quickly. Your choice (but at some point, given the urgency, I will be the fallback dev to build it).

[amyjko]

I think I'll work on building this this weekend, using your sketch as a guide, but leave in localization placeholders. Can you coordinate with localization to craft text for this, and I'll build and finalize English text?

[kelliannr]

Ok, sounds good. Should I ask them to localize the text present in the sketch or should I direct them to you for specific text?

[amyjko]

I'll merge the implementation today, with placeholders for the non-English locales, and so you can just alert them to the placeholders. You'll know it's done when this issue is closed.

[amyjko]

Okay, all built, thank you for designing! I've included placeholders for the localization team to translate. Thanks for nudging them.