-
-
Notifications
You must be signed in to change notification settings - Fork 12
Conversation
There was a problem hiding this 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:
- Can we please shrink the size of +325 KB static/images/bg_hero01.png. The current image is 57 KB.
- 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
- I don't believe we are allowed to grayscale logo of our members.
- Please fix the git conflict with the data/testimonials.yml file.
content/_index.md
Outdated
@@ -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> |
There was a problem hiding this comment.
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.
less/styles.less
Outdated
} | ||
|
||
.founder-logo { | ||
filter: grayscale(1) contrast(0) |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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:
We can remove if it's a blocker, but certain is aesthetically more pleasing within the design ;)
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
A few other comments:
|
I have a +1 from Thabang to move forward with this new look and feel if the critical feedback is addressed:
Nit picks, i.e classname, are things that we can address/refactor at a later time. |
Deploy preview for eclipsefdn-edgenative ready! Built with commit f064e20 |
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.
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.
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!
Thanks |
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. |
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. |
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. |
Deploying feels off the mark. How about Delivering? |
Delivering it is! |
@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? |
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 Any tips ? |
Last remaining thing is the favicon and social graphic. Being worked on right now. |
Tweaks the mission statement and keywords Initial cut of new style variables
Updated all svg logos to correct color palette.
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: |
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 ? |
Fav icons are in.. rest of images coming now. That's the last bit I think |
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 edgenative.eclipse.org/Dockerfile Line 32 in cb96061
|
@drluckyspin @Pixcell will you squash all the commits into one or do you prefer I do it via github? |
@chrisguindon Everything is in and done! Thanks for your patience. |
Feel free do it via github |
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! |
The changes were committed! It should take about 15 minutes to see them on production! |
@chrisguindon Thanks for your patience and advices ! |
@chrisguindon Thanks dude! The site is looking really good! Next up.. taking a look at the FAQ page ;) But that's for another day.. |
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! |
First tranche of work to rebrand the micro site. Mostly focused on styling and content of home page.