Footer design

[Zifare]

Here it is, the new footer. Reminder: The only thing left to do is add a few links to the buttons when the pages are ready. I hope you like it.

[achamely]

Pulled to staging for review/feedback

[achamely]

@oktype @Zifare what are your're thoughts on lightening up the blue footer a bit or lightening up the text color in the footer to make it easier to read (#A5B8CA; maybe for the text)

[achamely]

@oktype those little stick figure dudes creep me out (always watching with that "we're gonna get you" stare :P ) thoughts on something a little more subtle (http://vector-magz.com/people/young-people-silhouettes-vector-item-10/)

[Zifare]

About the color, I like darker text on a lighter background better (so maybe we can change the background color). Maybe something a tad bluer than the color you mentioned (like #749EC6), @oktype what's your opinion on that?

Note: I'm using the image in the original footer issue as a reference (the colors should be the same) because I can't enter the staging. Tomas told me you have to add my ip address to grant me access, but I'm not at my house right now so I think we leave that for later.

[achamely]

Yea lighter background keeps in line with the existing design structures. maybe even more to the grey-blue side #B3BDC7 or #CFD6DD ? @oktype @Zifare

[oktype]

No Silhouettes. @achamely
I was happy achieving some minor herd hinting, but when the little stick figure dudes gives you the look, is when they need to go. Will figure something out.

As for the bottom part color , Actually I like the way it is right now. the color stripe gives some finale tone to the end of the page, and using color similar to Onmi/Mastercoin just enveloping and gathers things up (like Omni), and also gives more vibrant feel. Light pale colors makes this really anemic in an old man pajamas style way.

The exclamation mark draws enough attention (?) to the necessary parts on first look, but on second look that line of text/buttons should not draw endless attention.
Take a look below: on roll overs the text is very readable

This is why I've choose for example to only use white text on the email, which should be more static.

With #A5B8CA for the text, guess this is OK, but the dark text gives more of that BOLD feel

While I keep this opinion, I still suggest we should use legal advise in those manners to make sure we make enough efforts to notify the user on thing he needs to be notified on,

If you haven't convinced yet I suggest we make this modification talk live.

[oktype]

Ok, was using the old man pajamas too soon :) lemmi try something

[oktype]

Yep.
When there is a problem with a background > remove the background :)

[oktype]

Some notes about the footer:
Images are blinking, should be loaded in advance. maybe use a sprite?

Is there a way to keep the "open to max" on rollover but also add the ability to scroll there? e.g when the page ends, start unfolding the footer

Inner pages should have minimum height so the footer will be below the screen even on short pages

Should farther work on the behavior of the elements for small screens (elements themselves are build good but maybe can remove dividers/ lower line height/ collide all to one list when screen is really small)

Really quality work 💯 @Zifare. thank you

[Zifare]

@oktype I'm not having the blinking issue, but I'll look into that.

Maybe the initial state of the footer could be expanded, so you can scroll down there and it starts to react to the roll over after the first time you roll off it? Of course for this to work the footer should be below the screen on short pages as you said, otherwise it would be covering the page's information as it'd be expanded when you load the page.

It does look weird on small screens, I'll try to fix that.

Also, if you hadn't thought of something yet, I have an idea for a replacement of the "dudes" (yeah I did it on ms paint :'( here is a draft:

Those are monitors, btw. The colors could be different. On the right is the roll over image, with the omni icon colored and the monitor's screen in the same light blue as before (which as you know is also in the text rollover). There could be a little omni icon in the top-left part of the present. Maybe it's a bad idea, but I think it's better to share a bad one than to keep a potentially good one.

[oktype]

Thanks for those thoughts, please keep 'em coming :) @Zifare

I can imagine how to make this ms paint can be transformed into a nice simplified scheme, thou might be too illustrative. Bringing Omni to many screens is our goal, the user just need to want to share his Omni experience (in this case). I'm trying to find something more friendly and uncommitted.

how about this direction:

I might remove the surrounding circle, and add more shapes in all sizes to simulate some kind of hinted explosion

About the footer, why can't it be below the screen in a closed state, opening while scrolling (opens to max on roll over)?

[achamely]

@Zifare make sure to grab the latest upstream changes and merge them into your branch (there is an update to the theme.css file that will cause a conflict otherwise.

@oktype i like the potential present much more than the dudes/silhouettes.

[Zifare]

@oktype I liked your idea, it's more subtle.
About the opening while scrolling, I'm not sure how it will react if the mouse isn't on the footer as you'd be ordering it to expand because of the scrolling, but to hide because your mouse isn't over it.
But I'm sure it can be done somehow, let me think how.

[marv-engine]

The scroll bar is at the bottom of the page, but the footer covers up some content. See

[marv-engine]

I think the footer should expand only when the pointer lingers on the expandable part for at least some small fraction of a second. It should contract when the pointer isn't in the expandable section.

[oktype]

The footer should not cover content or get covered. top of the footer should be static relatively to the page and below the content or minimum highet (below visible screen in inner pages)
The only time when the footer can cover content is when the page is not fully scrolled, and the user points on the footer, then it maxed. bottom part is also part of the footer. on roll out footer should get to it's position based on the scroll. (if scroll until the end of the page, no need to minimize)

making short suspension is a good idea so we can avoid the roll out "bug" when the user is try to reach below the browser. but should be really frictional, so the content of the footer won't "run away" making the user to press the wrong link.

I guess we can make the footer static (at least for now) if this is too costly.

[Zifare]

Shall I make it to wait a fraction of a sec before hidding when the mouse is not over the footer anymore? or only when it has to expand?
I found why it's covering content: the body has a 60px bottom margin, as that was the old footer's height. I changed it so it doesn't cover any content now.
Also I made it to be below the screen when you first enter it, and you have to scroll down to see it. I'm still not sure on how to make it to react according to the scrolling.

[Zifare]

alright, @achamely this is ready for staging and review.
Some notes:
-The "titles" are in bold, let me know if you want that removed.

-Missing links (please tell me if there are pages that already exists so I can add them):
"Trouble Logging In?"
"Terms of Use" (in two places)
"Tell your friends..."
"Ask a question on our forums" /added /about/contact/
"info@omniwallet.org" /removed as a link/
"Google+"
"Disclaimer"
"Open Source Project"

-Show the version number to be done. (also, is this supposed to be a link or not?)

[achamely]

@Zifare
Bold titles seem fine,
We have an entire contact us page, See https://staging.omniwallet.org/about/contact for the details.
@warrenyen I thought there was some talk about slimming down the options/content of the footer and making it more dynamic, it feels too big in its current form and slightly out of place.

[achamely]

@Zifare make sure we are using https for these

[Zifare]

Ok. added the s to http. Also added /about/contact to "ask a question on our forums". The email is not a link anymore.

[warrenyen]

Omniwallet Concepts Round 4

[dexX7]

Wow. Just wow. This is jaw-dropping, I really like it!

Regarding the UI:

• Imho there should not be a red alert-indicating warning right from the start when creating a new wallet

Some information about the protocol, which are not directly related to the concept:

• There are three ways to create a property: creation with a fixed number of tokens, as managed property or via a crowdsale
• Properties have two category fields and altogether there are the following meta data fields: name, category, subcategory, url and description - providing a name is required, the rest can be blank.
• It could be fine to provide only one category field and hide the other one. I have no strong opinion on this and for the sake of simplicity I tend to favor a one-category-only approach.
• Managed properties are properties where an issuer can emit new units of the property or revoke/remove units that are in the issuer's possession

Edit:

• There is a rather strict seperation between a "main ecosystem" and "test ecosystem" and basically no actions or interaction between both is allowed, like trading of main-ecosystem-properties for test-ecosystem-properties for example. This is relevant in the context of creating new properties and imho there should be a visual hint to indicate to which ecosystem a property belongs.

[warrenyen]

Logo Concept Artwork

[Zifare]

@warrenyen nice designs Warren. But this is supposed to be a talk about the footer only. You can open a new issue with the green button in the upper right.

[Nevtep]

@Zifare This PR needs to be closed and recreated, merging to the rebrand branch

[Zifare]

Closing this, opening it in another PR and merging it with the rebrand branch