Skip to content
This repository has been archived by the owner on Mar 26, 2022. It is now read-only.

Initial cut at rebranded site #7

Merged
merged 30 commits into from
Dec 10, 2019
Merged

Conversation

drluckyspin
Copy link
Contributor

First tranche of work to rebrand the micro site. Mostly focused on styling and content of home page.

Copy link
Member

@chrisguindon chrisguindon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is awesome! Thanks for contributing a PR to this project!

Here's a preview of this PR:
https://deploy-preview-7--eclipsefdn-edgenative.netlify.com/

Please note that I will need a +1 from our marketing team before I can pull this in. I need to make sure that this change does not interfere with any of their marketing effort that are planned for this week!

But for now, I can provide some feedback on the code since that's my department :)

General comments:

  1. Can we please shrink the size of +325 KB static/images/bg_hero01.png. The current image is 57 KB.
  2. Can we reduce our usage of the !important statement? Whenever possible, please override our variables: https://github.com/EclipseFdn/solstice-assets/blob/master/less/quicksilver/_variables.less
  3. I don't believe we are allowed to grayscale logo of our members.
  4. Please fix the git conflict with the data/testimonials.yml file.

@@ -37,7 +37,7 @@ container: "container-fluid"
<!-- start: Founding Members -->
<div id="members" class="row featured-section featured-section-members">
<div class="container">
<h2>Founding Members</h2>
<h2 class="section-title">Founding Members</h2>
Copy link
Member

@chrisguindon chrisguindon Dec 9, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit pick: Can we avoid introducing a new css class here?

If possible, I would prefer to keep our html simple so that we can easily re-use the featured-section component.

data/members.yml Show resolved Hide resolved
less/styles.less Outdated
}

.founder-logo {
filter: grayscale(1) contrast(0)
Copy link
Member

@chrisguindon chrisguindon Dec 9, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't believe we are allowed to alter logos from our members. I would recommend that we remove this line.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really? This has become pretty standard fair on modern websites. Here's an example of (black this time) treatment on logos at Hashicorp's site:

https://www.hashicorp.com/

We can remove if it's a blocker, but certain is aesthetically more pleasing within the design ;)

Copy link
Member

@chrisguindon chrisguindon Dec 10, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree this is way nicer but it's a blocker.

Altering a company logo is not something that someone should do without proper permission.

Most brand usage guideline will require you to use their grayscale version of their logo.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should ask our members to supply a grayscale version of their logo if we need it on the website!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@chrisguindon
Copy link
Member

chrisguindon commented Dec 10, 2019

A few other comments:

  1. I think we should stick with our current tagline: Open Edge Native Platforms Now. I don’t think we need to put a negative spin on specs on this website. I quickly discussed with the tagline with Thabang and we may want try something like “Your Production Edge Platform. Now.”

  2. Can we improve the contrast in the jumbotron. I find the text a bit hard to read now with this new background image.

  3. Since we are changing the colors, can you supply a new favicon and new social media image:

https://github.com/EclipseFdn/edgenative.eclipse.org/blob/master/static/images/edgenative/favicon/favicon.ico

https://github.com/EclipseFdn/edgenative.eclipse.org/blob/master/static/images/edgenative/edge-logo-social.png

@chrisguindon
Copy link
Member

chrisguindon commented Dec 10, 2019

I have a +1 from Thabang to move forward with this new look and feel if the critical feedback is addressed:

  1. Remove grayscale on member logos
  2. Revert tagline or replace with “Your Production Edge Platform. Now.”
  3. Contribute new favicon and social media image.
  4. Improve contrast in jumbotron so that the non-bolded text is easier to read
  5. Reduce the size of the jumbotron background image. 325 KB is quite big.
  6. Fix git conflict (rebase) since we can't merge this PR as is.

Nit picks, i.e classname, are things that we can address/refactor at a later time.

@netlify
Copy link

netlify bot commented Dec 10, 2019

Deploy preview for eclipsefdn-edgenative ready!

Built with commit f064e20

https://deploy-preview-7--eclipsefdn-edgenative.netlify.com

@drluckyspin
Copy link
Contributor Author

Comments:

1: See above about Grayscale. Easy to remove/replace.
2. The old tagline was VERY confusing. We'll definitely put something more aspirational though.
3. Will update the images/icons needed.
4. We'll try and play with contrast.. but not sure which bit is troubling for you right now.
5. Can reduce the image size.
6. Will fix the merge.

@chrisguindon
Copy link
Member

chrisguindon commented Dec 10, 2019

Comments:

1: See above about Grayscale. Easy to remove/replace.

+1 to remove for now and let's ask our members to send us their approved grayscale logo.

  1. The old tagline was VERY confusing. We'll definitely put something more aspirational though.

Thabang gave me his approval to move forward if the tagline is reverted or updated to Your Production Edge Platform. Now.”

I probably won't be able to talk to him again tonight so hopefully we can keep this simple for today since we can always change it again tomorrow.

  1. Will update the images/icons needed.
    thanks!
  2. We'll try and play with contrast.. but not sure which bit is troubling for you right now.

Bolded text in the jumbotron is ok but the tagline is hard to read "Delivering code, not specs". The quick fix might be to bold the tagline.

Tomorrow, we will ask our designer @ChristieWittEclipse, for her recommendation in regards to accessibility/contrast!

  1. Can reduce the image size.
  2. Will fix the merge.

Thanks

@drluckyspin
Copy link
Contributor Author

Re: tagline: How about "Deploying Open Source Edge Platforms. Now."?

What browser are you using to view the tagline? It seems very clear on the ones we're testing with. We can always make the text heavier.

@chrisguindon
Copy link
Member

Re: tagline: How about "Deploying Open Source Edge Platforms. Now."?

This sounds good to me but it's not my call.

I sent a message to Thabang for approval but I think we should play it safe for now and use "Open Edge Native Platforms Now" until we get his approval for the new tagline.

@chrisguindon
Copy link
Member

chrisguindon commented Dec 10, 2019

What browser are you using to view the tagline? It seems very clear on the ones we're testing with. We can always make the text heavier.

Chrome. I think we are good if we add a bit font-weight to the tagline.

Screen Shot 2019-12-09 at 9 38 13 PM

Screen Shot 2019-12-09 at 9 45 53 PM

@chrisguindon
Copy link
Member

Are you experiencing issues with the rebase?

May I suggest that we squash these 21 commits into 1.

I would prefer we do that so that I can quickly revert to the old site by reverting 1 commit if a problem is uncovered.

@ThabangMash
Copy link

Re: tagline: How about "Deploying Open Source Edge Platforms. Now."?

This sounds good to me but it's not my call.

I sent a message to Thabang for approval but I think we should play it safe for now and use "Open Edge Native Platforms Now" until we get his approval for the new tagline.

Deploying feels off the mark. How about Delivering?
"Delivering Open Source Edge Platforms. Now."

@drluckyspin
Copy link
Contributor Author

Delivering it is!

@chrisguindon
Copy link
Member

@drluckyspin It's starting to be late here, do you have an ETA for when I should expect everything to be ready to be merged?

@Pixcell
Copy link
Contributor

Pixcell commented Dec 10, 2019

Hi @chrisguindon ,

thank you for your patience ! We are almost done ! Last bit is to check that the News and event are ok. But we cannot seem to populate them
image

Any tips ?

@drluckyspin
Copy link
Contributor Author

Last remaining thing is the favicon and social graphic. Being worked on right now.

@chrisguindon
Copy link
Member

chrisguindon commented Dec 10, 2019

hi @Pixcell,

The event is showing here: https://deploy-preview-7--eclipsefdn-edgenative.netlify.com/

This preview is built with hugo 0.54.0: https://github.com/EclipseFdn/edgenative.eclipse.org/blob/master/netlify.toml

A different version of hugo might cause the page to render differently. The clock on your computer might also affect what content is ready to be published on the website.

You should be able to see a news item by adding a news item in content/news/example.md

For example:
https://github.com/EclipseFdn/hugo-solstice-theme/tree/master/exampleSite/content/news

@Pixcell
Copy link
Contributor

Pixcell commented Dec 10, 2019

Thanks @chrisguindon ,

Looks good to me, just waiting on @drluckyspin favicons and we should be good to go.

Side note, I built the docker image (to use Hugo 0.54 instead of 0.60 that I have locally installed) and it didn't pick up our style changes. Any idea why ?

@drluckyspin
Copy link
Contributor Author

Fav icons are in.. rest of images coming now. That's the last bit I think

@chrisguindon
Copy link
Member

chrisguindon commented Dec 10, 2019

Side note, I built the docker image (to use Hugo 0.54 instead of 0.60 that I have locally installed) and it didn't pick up our style changes. Any idea why ?

Did you build the image more than once? If so, you might need build with the 'no-cache' option to make sure that build runs

RUN npm --unsafe-perm ci \

@chrisguindon
Copy link
Member

@drluckyspin @Pixcell will you squash all the commits into one or do you prefer I do it via github?

@drluckyspin
Copy link
Contributor Author

@chrisguindon Everything is in and done! Thanks for your patience.

@Pixcell
Copy link
Contributor

Pixcell commented Dec 10, 2019

@drluckyspin @Pixcell will you squash all the commits into one or do you prefer I do it via github?

Feel free do it via github

@chrisguindon
Copy link
Member

Thanks to you both for all of this work! I really think that it's awesome that you guys stepped up and contributed this code to improve the website!

Give me a few minutes to do a final review and I will merge the change if all is well!

@chrisguindon chrisguindon merged commit 743fed2 into EclipseFdn:master Dec 10, 2019
@chrisguindon
Copy link
Member

The changes were committed! It should take about 15 minutes to see them on production!

@Pixcell
Copy link
Contributor

Pixcell commented Dec 10, 2019

@chrisguindon Thanks for your patience and advices !

@drluckyspin
Copy link
Contributor Author

@chrisguindon Thanks dude! The site is looking really good!

Next up.. taking a look at the FAQ page ;) But that's for another day..

@chrisguindon
Copy link
Member

Keep these PR coming! I am 100% supportive for helping out folks in our community who wishes to collaborate on our websites!

Again, thank you so much for pushing this forward and I am looking forward to working with you guys in the future!

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

Successfully merging this pull request may close these issues.

4 participants