New releasepost look + Release post 9.0
Merge request reports
Activity
@marcia please take a look when you have time
@dimitrieh it looks great! No normal process beyond merging if it is an improvement to what is already there and this definitely is. Are there any new things writers need to take into consideration when writing release posts using this new style?
/cc @markpundsack
mentioned in merge request !4522 (merged)
Looks awesome @dimitrieh . Reminds me of http://www.apple.com/macos/sierra/
Awesome @dimitrieh!
The use of div's in markdown is always really weird, but this looks pretty clean, all things considered.
@JobV does the release posts.
Personally, I think I'd like to see the CE and EE labels appear to the right of the feature title rather than the left.
The spacing of the single column text vs image feels weird (they're no the same width). I know there are good reasons to keep the text width smaller than max, but it feels arbitrary in the screenshot. especially the image then looks to be a different arbitrary size.
Two-column text with image looks great.
This looks really nice!!
I agree, the EE label would be nice to the right so that the new feature is the "star."
On the labels topic, should we consider only having an EE label OR adding a .com label? My concern is that having CE and EE labels makes me instantly wonder about GitLab.com. I know that .com runs EE but new users reading this post may not know that right away.
@markpundsack @amara i think bringing the labels to the right could be the way to go! will try it out (really simple css change anyway :) )
@markpundsack the idea there was to give images the head light and make use of otherwise unused white space ;) (for wide enough viewports of course!)
@amara I was wondering about that as well.. also with future subscriptions in mind, we may need more labels then just ce/ee... i think for now it would be best to just state either ce or ee... stating the minimum required for it to be in your gitlab licence
@marcia @JobV perhaps we can hold this off/work slowly and work on this for the 9.0 release? (to give it a bigger splash!)
Edited by Dimitrie HoekstraThanks @dimitrieh! It's awesome!
perhaps we can hold this off/work slowly and work on this for the 9.0 release? (to give it a bigger splash!)
I think it's a good idea, yeah :)
Also, as you mentioned, I think we need to consider how we're gonna label EE-only features considering we'll have different versions of EE and .com.
And, I'd replace
<div>
with<section>
, for semantic SEO reasons. :)added blog label
cc/ @regisF I'd milestone it to 9.0 :)
Edited by username-removed-236961This is targeted for 9.0 right? Is the code for this MR just an example?
Will we have a similar WIP for 9.0 in the new format? Could we get that ready soon so we can start putting in at least placeholders? We already know a good number of features that will are targeting for 9.0.
We can use this WIP for 9.0, or we close that one and start a new one. https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/4780
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
added 1 commit
- 6b7fb2d8 - various css and structure changes, including improved mvp part
added 1 commit
- dbcf96a2 - fixed ce-ee badges placement and titles for smaller screens
On the labels topic, should we consider only having an EE label OR adding a .com label? My concern is that having CE and EE labels makes me instantly wonder about GitLab.com. I know that .com runs EE but new users reading this post may not know that right away.
@JobV what do you think about this?
added 1 commit
- 1d2d1e21 - fixed non centered titles on small screen sizes
added 1 commit
- 30642c81 - added link functionality to mvp's profile page
added 1 commit
- 804e3216 - added flexbox to normal sections, including a way to reverse them for smaller vi…
last major thing to do is fixing the linting errors
Edited by Dimitrie Hoekstraadded 2 commits
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by username-removed-236961
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
added 1 commit
- c83ee88b - fix description and hide by default.. as its only for SEO
- Resolved by Dimitrie Hoekstra
assigned to @marcia
Thanks @dimitrieh, overall, looking gooooood! \o/ I'll review it thoroughly, and at this point, I'm only concerned about making it easy to reproduce every month, considering the number of hands contributing to them ;) I'll prob gonna have to add some guidance in the template, and/or perhaps in the blog handbook.
@iamphill would you please review the frontend part? ;) thank you!
changed milestone to %9.0
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
@marcia this can probably considered a different issue, but perhaps its nice to rethink the order in which we layout the information in this particular kind of blogposts. To consider them more as a sort of extended releasenotes.
See for more info: https://uxdesign.cc/design-better-release-notes-3e8c8c785231#.st7d95llz
perhaps to clearly instruct we order items by:
*** NEW *** *** IMPROVEMENTS *** *** FIXED ***
@dimitrieh will you address Phill's review?
I want to target the branch
release-9-0
from https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/4780 with the content of this MR@marcia I hoped you would touch some code in this as well (so that's why i left those to you, as you would have to familiarise yourself to the code anyway) :) Otherwise can look at it later tonight perhaps!
Edited by Dimitrie Hoekstra@dimitrieh I'd love too, but there's too much on my plate already :)
I'm tweaking it @dimitrieh :) Committing/pushing shortly.
Will need your help with the intro block.
Edited by username-removed-236961- Resolved by Dimitrie Hoekstra
- Resolved by Dimitrie Hoekstra
assigned to @dimitrieh
added 2 commits
assigned to @iamphill
@iamphill could you assign it to @marcia if no further changes are needed? :D she will do the merge in to https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/4780
assigned to @marcia
added 1 commit
- e309a1fa - documented way to add video webcast recording to blogpost if needed/done afterwards
added 2 commits
added 1 commit
- 7de43ae0 - remove example post (screenshot here: https://gitlab.com/gitlab-com/www-gitlab-c…
Final screenshot here: https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/source/images/new-release-post-example.jpg
Merging into release post 9.0 NOW! \o/
Thank you all for the awesome work! #teamwork
Thanks @dimitrieh for making this happen!!
mentioned in commit 5def7473
@marcia @dimitrieh why this MR has so many changes?
mentioned in issue #998 (closed)
mentioned in merge request !4780 (merged)
mentioned in issue #1216 (closed)