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

Pop-up notification to the user if contents have been updated #1180

Closed
amimas opened this issue Jan 4, 2019 · 1 comment
Closed

Pop-up notification to the user if contents have been updated #1180

amimas opened this issue Jan 4, 2019 · 1 comment

Comments

@amimas
Copy link

amimas commented Jan 4, 2019

🚀 Feature

As an end user, if I am on the site and in the meantime the contents have been updated, it'd be really useful if a pop-up notification would appear (without being intrusive; maybe in the bottom left/right corner). The user can click on the "refresh/reload" button on that pop-up to view the updated contents. This is similar to how Google Inbox behaves when the app is updated if I'm visiting a cached version.

Have you read the Contributing Guidelines on issues?

Yes

Motivation

I came across Docusaurus and VuePress while looking into migrating my company's existing docs to a new tool. I'm very impressed with Docusaurus so far as it comes with versioning and translation management out of the box. VuePress is also another decent tool that caught my attention and I noticed it has this feature that I believe is really useful. Here's a doc on this feature from VuePress.

https://v0.vuepress.vuejs.org/default-theme-config/#service-worker

Pitch

Static site generating tools are becoming more than just a simple site with html. Other tools (i.e. VuePress) now generates SPA and I believe so does the Docusaurus. To the end user, it is less obvious if it's static site or not. Having this feature will improve user experience greatly and provide a modern app to the audience that is already mobile friendly.

@amimas
Copy link
Author

amimas commented Feb 11, 2019

I was just going through some of the old issues and realized that this request is duplicate of #458 where it already raised the same request. Closing this item in favor of keeping track of the original request.

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