update: .markdown-section max-width 800px to 80%

[jhoneybee]

Summary

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Docs
• Build-related changes
• Other, please describe:

If changing the UI of default theme, please provide the before/after screenshot:

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

You have tested in the following browsers: (Providing a detailed version will be better.)

• Chrome
• Firefox
• Safari
• Edge
• IE

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature
• Related documents have been updated
• Related tests have been updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.

Other information:

---

• DO NOT include files inside lib directory.

[anikethsaha]

@jhoneybee can you please describe the reason or any point for this change

[jhoneybee]

@anikethsaha

The reason to modify 800px to percentage is as follows

1. The document is not beautiful under the huge screen.

800px

80%

Testable by browser zoom

I found 80% is the most beautiful after trying . sorry, because English is not my native language, I answered late

[yzhang-gh]

I would suggest restoring max-width to 100% if the viewport width is less than 768px.

docsify/src/themes/basic/_layout.styl

Line 406 in bea19ed

@media screen and (max-width: 768px)

This PR breaks the layout on mobile devices 😥.

[anikethsaha]

can you create an issue

[yzhang-gh]

I created a PR (#1273) as it is so slight a problem.

[yzhang-gh]

@anikethsaha Could you spare a few minutes to take a look. Thanks.

[jhildenbiddle]

@anikethsaha --

I know this has already been merged, but setting text width to 80% of the screen resolution is a bad idea. Standard practice for readability is 45-75 characters per line. Here's more detail:

https://www.smashingmagazine.com/2014/09/balancing-line-length-font-size-responsive-web-design/

THE IDEAL MEASURE: 45 TO 75 CHARACTERS

We have multiple “rules” for facilitating a horizontal reading motion, one of which is to set text at a reasonable measure. As James Craig wrote in his book Designing With Type (originally published in 1971, now it its fifth edition):

Reading a long line of type causes fatigue: the reader must move his head at the end of each line and search for the beginning of the next line.… Too short a line breaks up words or phrases that are generally read as a unit.
If a casual reader gets tired of reading a long horizontal line, then they’re more likely to skim the left edge of the text. If an engaged reader gets tired of reading a long horizontal line, then they’re more likely to accidentally read the same line of text twice (a phenomenon known as “doubling”).

65 characters (2.5 times the Roman alphabet) is often referred to as the perfect measure. Derived from this number is the ideal range that all designers should strive for: 45 to 75 characters (including spaces and punctuation) per line for print. Many web designers (including me) apply that rule directly to the web. I’ve found, however, that we can reliably broaden the range to 45 to 85 characters (including spaces and punctuation) per line for web pages.

Filling more of the empty space may be visually preferable to some, but there's little argument to be made that this is better for everyone. My recommendation would be to revert this change and let those who prefer content to stretch for wide monitors to add their own custom CSS to a <style> block in their index.html page.

[anikethsaha]

@jhildenbiddle how about #1273 ?