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

CLEANER PR for #856 the new homepage implementation #952

Merged
merged 4 commits into from
May 28, 2015

Conversation

mmmavis
Copy link
Member

@mmmavis mmmavis commented May 28, 2015

My original PR is getting messier and messier and it's very painful for people to understand(sorry 😬 ).

This PR contains minimal changes needed for the new homepage implementation and hopefully it will be a lot easier to understand.

…nly contains miminal changes needed for the new homepage
@mmmavis
Copy link
Member Author

mmmavis commented May 28, 2015

@toolness LET'S GET THIS PUSHEDDDDD! :shipit: (well, after I get a R+ of course)

@@ -22,6 +22,8 @@ to [Semantic Versioning](http://semver.org/).
accessible.

### Changed
- The homepage has been refreshed to better inform
the site vistors what they can do on the site.
Copy link
Contributor

Choose a reason for hiding this comment

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

Aw yeah, right up at the top! 😋

Er can you make the second line indented so it is flush with the first letter of the previous line? Like all the other bullet points below are? Also mention that it shows the latest BLOG POSTS!!!!!!!!!!!

Copy link
Member Author

Choose a reason for hiding this comment

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

oh yea, meant to have indentation, I was just careless.

@toolness
Copy link
Contributor

Woot this is looking good and super clean, I will manually test it to make sure everything looks good.

@toolness
Copy link
Contributor

This looks A ⭐ W ⭐ S ⭐ M, great work @mmmavis! Feel free to merge once Travis is happy.

@mmmavis
Copy link
Member Author

mmmavis commented May 28, 2015

HUGE SORRY AND THANKS @toolness
this has been kinda painful for both of us haha but glad it finally worked out hoorayyy 🎉

After this PR is merged, what will be the next step to get the new homepage pushed? Are we going to stick with hardcoded data for now or we should include #950 as well?

@toolness
Copy link
Contributor

Haha no worries, I actually thought it was kinda fun :) Yay teamwork!

Good question about pushing the homepage... I guess I recommend including #950 before we formally push to production, but that said, if the teach team REALLY wants their new homepage ASAP, it's probably OK for now to actually just push without #950, since our "fake feed" actually contains all the latest posts. We could even manualy "update" the fake feed to keep up with the blog, lol. I guess that is an unintentional side benefit of our approach that we hadn't considered.

@hannahkane
Copy link

Would be rad to push sooner rather than later. :)

@mmmavis
Copy link
Member Author

mmmavis commented May 28, 2015

@toolness yea I personally would prefer to just push it live without #950 for now . Selfishly speaking my brain would love a break today to get away from the homepage stuff (๑•́ ₃ •̀๑) and I'm hoping to not violate our "don't push to PROD on Fridays" rule.

@toolness
Copy link
Contributor

Ah yea sounds good to me! I will bust out a new release in a bit.

@mmmavis
Copy link
Member Author

mmmavis commented May 28, 2015

Thanksssss. I will get to #950 tomorrow! 👯 👯 👯 👯 👯

mmmavis added a commit that referenced this pull request May 28, 2015
CLEANER PR for #856 the new homepage implementation
@mmmavis mmmavis merged commit daf9310 into mozilla:develop May 28, 2015
@mmmavis
Copy link
Member Author

mmmavis commented May 28, 2015

M-E-R-G-E-D

@@ -22,6 +22,9 @@ to [Semantic Versioning](http://semver.org/).
accessible.

### Changed
- Homepage has been refreshed to better inform
Copy link
Contributor

Choose a reason for hiding this comment

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

Ack lol I didn't actually look to make sure your new bullet points were being added to the "Unreleased" section--you added them to the release notes for our last release :) Fixed this in e3ac628

Copy link
Member Author

Choose a reason for hiding this comment

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

oops, sorry should've been more careful. thanks Atul

Copy link
Contributor

Choose a reason for hiding this comment

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

is ok, it was your first time editing the changelog 🍔

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.

3 participants