-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
New Block: Time to Read #42542
Comments
Let's do it! |
If this block is expected by many, can I try to develop? |
That'd be great, feel free to start a branch and submit a proposal! |
Thank you! |
I am working on developing a block and have hit a major problem. I think this block should be a dynamic block, so to match the numbers on this panel exactly, the same logic processing would need to be implemented in PHP. Does anyone have any good ideas on this point? |
@t-hamano It would be great if you could take on this new block. Maybe this helps to get started? |
Thanks for the advice! But, as was the concern with the ToC block, it cannot calculate dynamic time at render time. In other words, it would not work in the site editor (i.e., post templates such as single.html), but only in the post editor. If we can accept this disadvantage, I would like to restart development 🙂 |
I came here today checking to see if this had already been requested or not. Such a simple block, and very easy to implement I would imagine given the time to read component linked to above by @bph +1 for this block! |
@t-hamano thanks for your work! Hope this gets added soon! |
A Time to Read block would allow for site owners and theme builders to display the estimated time to read of the particular post or page to the frontend on single post templates or from within query loops in Archive templates.
Maybe the existing information form the table of contents panel can be stored into post meta key/value on save/publish action.
And then the Time To Read block displays the value, similar to the Post date or the post author.
The text was updated successfully, but these errors were encountered: