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
blog: home page should only show previews instead of full posts #33476
Comments
Can you be a bit more specific about exactly is the bad user experience you are having? @gopherbot please add WaitingForInfo |
WaitingForInfo check out this url https://blog.golang.org/ |
Do you mean that the list page of each entry on Go Blog should omit the content, and add a "read more" link to go to the permalink? |
The fact that the https://blog.golang.org homepage is a huge page where the latest n blog entries are included in full without being clear where one ends and the following one begins is also something that has always bugged me. I'm guessing this is what the OP is reporting. |
Two different suggestions for a possible solution:
|
Another possible solution: There should be pagination and sidebar with categories |
The https://blog.golang.org/ is unnecessarily long and can bore the users. Pagination can be applied |
Let’s start with only showing previews (with a “read more”) instead of full posts. |
I am a UI/UX Developer... I can help revamping the blog page @agnivade |
Feel free to go ahead. And just a small note that mentioning hashtags does not have any effect here. |
my preference is to leave it alone the titles are but can't certain gophers use a feed reader e.g., add Atom feed under Blog index in the sidebar categories complicate feeds |
The read more on the homepage of the goLang website leads to a tunnel which has bad User Experience
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: