-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
buble theme: strong font-weight increased to 600 #913
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
Conversation
Is there any specific issue or link which might support this change? I can see you checked Thanks |
@anikethsaha The bug is, that the bold font is not recognizable from the normal fint in the buble theme. I do not know what kind of link should I provide. Should I make one more bug issue about that? |
@xmedeko actually the optimal flow is to have an issue and then discussing there we can decide whether its a bug or not and PR is required or not. Leave it for this one. No need to create an issue. We can discuss this here just for this PR. Also, can you provide some screenshots comparing PS
|
src/themes/buble.styl
Outdated
.markdown-section h1, .markdown-section h2, .markdown-section h3, .markdown-section h4, .markdown-section strong | ||
color #333 | ||
font-weight 400 | ||
font-weight 600 |
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.
The default of these is bold
in the browser. I am pretty sure this is an intended code.
If you make markdown bold It's possible the fix is not well for this theme. It should affect headings also, but the buble theme has just a few lines bellow: .markdown-section a
...
font-weight 400 And it overwrites the fix I think the theme has a few more troubles, but I like it. I am not so strong in CSS. Since the docsify has been kind of unmaintained with lot of open issues, I have decided to post this hot fix PR instead of opening one more issue. If you can make a better fix of buble theme, then go ahead (also not wrong spelling of "buble"). |
Actually thats where we are struggling a bit. The former maintainers I guess are not active and not maintaining so we are struggling to get the indentions of these few codes. Like this one. I am not sure why at first place these where I think we will go with this PR and if required we will revert this if it is suggested. I am down to |
Since the doplhin and vue are using 600, I vote for 600. I thing the reason is to be kind of lighter feeling. Also, because both these styles have same value for |
Ok let's go with |
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.
Thanks for PR and detailed explanation
👍
Hold on, I've been playing with that a bit and seems to me the 400 suites the headings and links better in this theme. Maybe separate strong style could be better. |
separate the strong from this group 👍 |
Ok, will do it tomorrow. |
ohh shoot!! |
@anikethsaha I've separated strong and set it to 600. I've removed the (Links has blue color in the buble theme, so they do not need the slight font-weight increase. I also do not know how to keep font-weight and do not override headings, because headings are links to. I aware of CSS I've rebased to master. You should set the default branch to master from develop. |
We are discussing that. Actually |
Ok, closing this PR and have made #952 |
Summary
What kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
fix #xxx[,#xxx]
, where "xxx" is the issue number)You have tested in the following browsers: (Providing a detailed version will be better.)