mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
Page Views Count #440
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Sep 20, 2017).
For Feature Requests
Desired Feature: Tracking page views count, displayed on the details div.
@ssddanbrown commented on GitHub (Sep 28, 2017):
Hi @dsaundersWizmo, Thanks for your suggestion.
I've thought about this before, BookStack does store view information so it wouldn't be hard to add but I've often wondered what value it would offer on a documentation platform.
I could see the value if it was part of an 'Analytics' area of BookStack where stats could be viewed/exported regarding top viewed, least viewed, most active users, most active times etc.. This area could then be permission controlled.
@Ethanb00 commented on GitHub (Sep 28, 2017):
I'd favor an analytics page. Readers of the page don't care how often the page has been looked at. The main use would be the author. So that content would be best offered in a separate location.
@Shackelford-Arden commented on GitHub (Sep 28, 2017):
@ssddanbrown Potentially something I had in my mind when I was thinking about this #440
@Chris-ZA commented on GitHub (Sep 29, 2017):
An analytics page would be awesome!
It would be a useful tool to figure out what books, chapters and pages aren't being read, how popular they are etc.
I've often wondered if the stuff I document is ever read. :/
@ghost commented on GitHub (Sep 30, 2017):
Yes—There are a couple of valuable aspects:
From: Chris [mailto:notifications@github.com]
Sent: Friday, September 29, 2017 1:40 PM
To: BookStackApp/BookStack BookStack@noreply.github.com
Cc: Dustin Saunders dsaunders@wizmo.com; Mention mention@noreply.github.com
Subject: Re: [BookStackApp/BookStack] Page Views Count (#518)
An analytics page would be awesome!
It would be a useful tool to figure out what books, chapters and pages aren't being read, how popular they are etc.
I've often wondered if the stuff I document is ever read. :/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/BookStackApp/BookStack/issues/518#issuecomment-333205740, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVwzOjqcZZMYkYgiQDDr7AcweA8G_2Kvks5snTlwgaJpZM4PdDKF.
@marcusforsberg commented on GitHub (Jan 27, 2018):
Would love to see a feature like this, especially the ability to track user activity to see the top contributors.
@moretolearn01 commented on GitHub (Dec 3, 2018):
Analytics dashboard would be great to help identify content regularly being used, as well as those that may not be visited and therefore should be updated or removed.
Another item on the analytics dashboard/page that would provide insight is the search terms being used (ranked by number of occurrences) and the click through to pages, e.g. if they clicked through it may be counted as successful.
@s1mpleman commented on GitHub (Dec 21, 2018):
Ditto on this, or at least an easy way to use google analytics. Trying to find a decent place to put it in the code but can't find it at the minute.
Edit: Found the custom code settings :)
@fanyigle commented on GitHub (Mar 20, 2019):
@s1mpleman sorry,Could you kindly point out where the code resides.
@n0nag0n commented on GitHub (Aug 2, 2022):
I echo a few of what others have suggested here regarding page views. I noticed recently that searching seems to be a little more accurate, I can only assume that you're roping in the page views into the sorting algorithm? It's still not perfect, but seems like the more common articles are up top.
I would like a page view count of some kind to find the popular pages and just make sure their content is up to par and if any updates need to happen with it. It'd be nice to have a report of some kind to show aging articles (by book, etc) so they can be updated if possible. Of course if none of this is possible, I can just hack my way into the db (or through the api) and manually create a page that would show this info.
@mso-l commented on GitHub (Oct 10, 2022):
I agree, statistics are missing on BookStack :
document statistics in order to :
search statistics to list frequent searches that have no associated relevant document, in order to create those missing documents
@ssddanbrown commented on GitHub (Nov 8, 2022):
I'm going to go ahead and close this off since the OP no longer exists, and the goals/values desired seem to be mixed.
Feel free to open a new specific issue to detail the user value/end-goal you desire, but note I'll probably only leave it open for consideration if the value can't already be gained by simply incorporating an external analytics option.