Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Beta" word should always be present with steemit logo on top bar #1939

Closed
ghost opened this issue Nov 7, 2017 · 4 comments
Closed

"Beta" word should always be present with steemit logo on top bar #1939

ghost opened this issue Nov 7, 2017 · 4 comments

Comments

@ghost
Copy link

ghost commented Nov 7, 2017

There seems to be 4 adaptive top bar styles which depend on screen width:

.1. Wide has everything
steemit_wide
.2. Medium size drops the beta under steemit logo
steemit_medium
.3. Short size drops trending, new, hot, promoted
steemit_short
.4. Very short size (mobile) goes into mobile mode
steemit_mobile

New new website is great for the adaptive sizing and styling. But you should always have the word "beta" present here when in beta, it should not be an optional bit of information. Really it should be incorporated into the logo itself and switched out with an updated logo when out of beta.

I bring this up in part because some people have been talking and think it's out of beta, probably because they have small screens or use mobile. It's misleading.

@steevc
Copy link

steevc commented Nov 7, 2017

On mobile we just have the logo. Should that have 'beta' too?

@ghost
Copy link
Author

ghost commented Nov 8, 2017

Yes I definitely think so. Making the screen size smaller does not promote the web app out of beta, that's the logic I'm following. It's important information.

@relativityboy
Copy link
Contributor

We've been progressively moving away from 'beta' branding. Condenser (like most software these days) is an evolving thing, with new features and new challenges popping up on a somewhat frequent basis.

Expect the remaining beta tags to disappear in the coming months.

@ghost
Copy link
Author

ghost commented Nov 12, 2017

I know it's not high priority, but you're not using good reasoning. Have it consistently or don't have it at all, that's simply the point. Just because it will at some point not be in beta is no excuse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants