Skip to content
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

Read Time may not be accurate #28

Closed
Kenshino opened this issue Mar 19, 2016 · 3 comments
Closed

Read Time may not be accurate #28

Kenshino opened this issue Mar 19, 2016 · 3 comments

Comments

@Kenshino
Copy link
Collaborator

@justingreerbbi

See http://helphub.wingz-media.com/2016/03/18/htaccess/ as example.

That article definitely looks like it will take longer than 4 mins.

Can we adjust the way read time is calculated?

Semi-related #27 #29

@justingreerbbi
Copy link
Contributor

Makes sense.. Right now we run on an average WPM (word per minute) base to calculate read time. The WPM value was taken from an average of people reading literature (novels, etc). Since the content is documentation we could decrease the WPM to increase read time an appropriate level.

To your point, people reading this documentation will read ever word without much skimming since they are instructions and or a guide. This still don't address the code blocks though. I will look deeper into this aspect.

@justingreerbbi
Copy link
Contributor

I also read the article skipping all the code blocks ran finished in about 3 minutes. The code blocks are going to play a bigger role than I initially thought.

@Kenshino
Copy link
Collaborator Author

Kenshino commented Apr 18, 2016

The new read time is a better estimate with PR #32

Closing this - may review afterwards with other articles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants