search

dss-ialh / dss-blogs

Communication portal of Data Science Studio at the Institute of Aging and Lifelong Health
GNU General Public License v3.0
1 stars 0 forks source link

Post Preview Summary Length #11

Closed mrparker909 closed 5 years ago

mrparker909 commented 5 years ago

@andkov, @huttoncp, I am working on the blog post giving instructions for new posts, and it would be helpful to nail down exactly how long the preview text summary will be. I think we should discuss (and implement any change to) the length of text that displays. The default is 200 characters (so that is probably what we have right now). As soon as we nail it down I will add it to the instructional blog post so that future contributors have a reference.

I think that it would be good to increase this to 250 characters, but we could just as easily keep it at 200, or make it even shorter (demanding very short concise summaries has some merit). What are your opinions on this?

how to edit length

We can easily change this parameter in config.toml:

[params]
    summary_length = 250
huttoncp commented 5 years ago

I think 250 characters is reasonable.

On Tue., May 21, 2019, 4:17 p.m. Matthew Parker, notifications@github.com wrote:

@andkov https://github.com/andkov, @huttoncp https://github.com/huttoncp, I am working on the blog post giving instructions for new posts, and it would be helpful to nail down exactly how long the preview text summary will be. I think we should discuss (and implement any change to) the length of text that displays. The default is 200 characters (so that is probably what we have right now). As soon as we nail it down I will add it to the instructional blog post so that future contributors have a reference.

I think that it would be good to increase this to 250 characters, but we could just as easily keep it at 200, or make it even shorter (demanding very short concise summaries has some merit). What are your opinions on this?

how to edit length https://yihui.name/en/2017/08/hugo-post-summary/

We can easily change this parameter in config.toml:

[params] summary_length = 250

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dss-ialh/dss-blog/issues/11?email_source=notifications&email_token=ALBJZKBGYOHTCYCBEXQXDQTPWR7GZA5CNFSM4HOPNTT2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GVCT4KQ, or mute the thread https://github.com/notifications/unsubscribe-auth/ALBJZKBZTPVGGMTTGJD2G5DPWR7GZANCNFSM4HOPNTTQ .

mrparker909 commented 5 years ago

Comment from speaking with @andkov: 250 character limit is perfect for tweeting, as twitter has a 280 character limit (leaving 30 characters for a link back to the blog when we tweet the summary.

mrparker909 commented 5 years ago

I will make the change to 250 character limit and include the change in the future pull request along with the how-to-blog post.

mrparker909 commented 5 years ago

@andkov, @huttoncp I ran into a snag. The new hugo version uses word count instead of character count, the default for hugo-academic is 60 words now (instead of 200 characters). What is a good word limit? This gets in the way of easy twitter alignment regardless of what we decide.

I believe we now change it with the line: let summaryLength = 60; in the file: "./themes/hugo-academic/assets/js/academic-search.js"

But this assumption will need to be tested.

huttoncp commented 5 years ago

Twitter allows 280 characters , so if the average English word is around 5 characters and leaving around 75 characters or so for the link URL, let's go with 40 or so for a word limit plus whatever space is needed for the URL? Is that enough?

On Thu, May 23, 2019 at 3:22 PM Matthew Parker notifications@github.com wrote:

@andkov https://github.com/andkov, @huttoncp https://github.com/huttoncp I ran into a snag. The new hugo version uses word count instead of character count, the default for hugo-academic is 60 words now (instead of 200 characters). What is a good word limit? This gets in the way of easy twitter alignment regardless of what we decide.

I believe we now change it with the line: let summaryLength = 60; in the file: "./themes/hugo-academic/assets/js/academic-search.js"

But this assumption will need to be tested.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dss-ialh/dss-blog/issues/11?email_source=notifications&email_token=ALBJZKF6GK6NE7LA4CQ6GSLPW4KL7A5CNFSM4HOPNTT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWDUZLQ#issuecomment-495406254, or mute the thread https://github.com/notifications/unsubscribe-auth/ALBJZKHL2HEG5ZV6QJKYW63PW4KL7ANCNFSM4HOPNTTQ .

-- Craig Hutton, PhD Postdoctoral Fellow - Neuroscience Division of Medical Sciences University of Victoria craig.hutton@gmail.com craighutton@uvic.ca 250-472-4244 https://www.uvic.ca/research/labs/christie/home/contact/index.php#

mrparker909 commented 5 years ago

I think that's a good approach. The URL most likely only takes one word, so we could go as high as 50 or 60 for the word limit.

andkov commented 5 years ago

I like the math. I still think making the summary compatible with twitter limit is a good strategy

mrparker909 commented 5 years ago

Sounds good, in that case I will leave it at the default 60 words, and we can change it later if we find it's too much (or not enough)