-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vertical rhythm for headers #9397
Vertical rhythm for headers #9397
Conversation
@karland I'm away until tomorrow but from your description this sounds fantastic! I'll take a look properly tomorrow but thank you. A great first step into doing similar with everything hopefully. |
@brettsmason Any progress? Questions? |
@karland sorry I haven't had as much time as I wanted but I will make sure I fully review it tomorrow. I did quickly pull it down to try yesterday and from my brief tests it seems to work great. Will get back to you properly tomorrow. 6.3 release has been delayed a week because of thanksgiving so we have plenty of time. |
Hi @karland so had another look (will look more throughout the day). A few things so far:
I love the map conversion you have done, really brilliant idea! I'll continue testing, as well as reading through the docs with any other points I might find. |
|
@karland sorry just to clear the points up:
Does that make sense? |
Inheriting the default values is actually more tricky than I thought. I am working on something. I'll PR later. |
Basically cut out else branches and re-introduce default values for margin-top and margin-bottom. Update of docs.
I think, this was not tricky at all. |
@karland thanks for looking at this some more. However I think I might of misled you with what I meant by mobile first on this occasion - apologies. I think the ideal output would be something like this (just an example):
So what I mean is the fallback values are only used on the small breakpoint, and not output again if the user hasn't entered a value. The above was generated by making a simple change to your original PR, so the final code would be:
The key point being the
as they aren't needed. Does that make sense and look clearer/cleaner output? Really sorry if I caused any confusion! Also feel free to disagree with me... |
@brettsmason No worries. I think our solutions are very similar. Basically, we both do not make use of the |
@andycochran If you get a minute could you take a quick look at this? It now looks OK to me. I'll then get this branch together and sort out a PR into develop. |
Just a short question, as I can't find anything about it. This change will break existing old configuration? If that's the case I think the new configuration should have another name and there should be a mapping from old to new, to ensure backward compatibility for a certain time. As this change is an extension to the old functionality it shouldn't be that hard to create a mapping that works with old configuration. |
@DaSchTour This PR should not break your old settings as described in the accompanying docs. "Warning. The So, the |
Oh, okay. Somehow I haven't seen it at first sight. Thanks for clarification and great work. 👍 |
@karland going to merge this in so I can put together the main PR into develop. Thanks so much for your work on this, its excellent! 👍 |
@brettsmason Thanks to you. It has been fun working with you. I think one of my next PRs will be to improve on other elements to get proper vertical rhythm. |
Here is the second attempt of a PR to the vertical-ryhthm branch:
npm run test: visual
and you will find a filevertical-rhythm/vertical-rhythm.htm