mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-21 03:09:38 +03:00
Favourites vs Starred vs Bookmarks vs Pinned vs Something Else #1678
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 @ssddanbrown on GitHub (Apr 25, 2020).
Just looking to get some feedback on the naming for some kind of user-level "favourite" system of BookStack entities (Shelves, Pages, Books, Chapters). This feature is a prerequisite for working towards a notification system in BookStack (For example, receiving notifications for starred items).
What terminology do you think would suit best?
Intended Functionality of this system (Initially)
Options
Thoughts so far
Related to #505 & #1376
@hercules808 commented on GitHub (Apr 26, 2020):
Well, a word like "reservation" might fit with the book/library theme, although that has the same limitation around specificity (i.e. you might expect it to mostly apply to just a book), and it does feel like it might be stretching the metaphor a little too far! I wonder whether "Favourite" (English spelling preferred) might be the best choice even it it does tend to get over-used...
@MatthieuParis commented on GitHub (Apr 26, 2020):
+1 for "favourite shelves/books/chapters/pages".
The place where one could find all the favourites could be called ones's desk or nightstand.
@angelos-alexiou commented on GitHub (Apr 27, 2020):
Favourites = Could produce confusion! Eg. a "favourite" page full of warnings' descriptions, might not be as favourite as is sounds, but a shortcut to that page!
Starred = THE BEST 👍
Bookmarks = Agree to your thought
Pinned = Suitable for forums, not in bookstack (hey, my opinion)
Something Else = Shortcuts (??)
@dannyhanes commented on GitHub (Apr 29, 2020):
I would go with favorite and maybe have the icon look a little like a bookmark. If you use "starred" then it would have to look like a star lol.
In the future when we can get notifications, are you thinking if we "favorite" a book, then anytime a new page is created / updated in the book, we could send out notifications? Because that would be amazing.
@Venkinovec commented on GitHub (May 2, 2020):
From your options I would go for Starred.
Something Else = what about simply Watch shelves/books/chapters/pages
then u can have a place called Observatory ?
Just my opinion.
@c0shea commented on GitHub (May 28, 2020):
What about Checked Out Items? Although similar to the bookmark term, you don't check out a page.
@Honvid commented on GitHub (Jul 7, 2020):
comment for the content's words. it's looks like bellow:
this can be links to the page's comment, some other link address.
@b-zurg commented on GitHub (Jul 10, 2020):
In terms of language and usability I think sticking to a commonly used term, like the ones originally put forth, is important instead of making something new.
The clarity of its usage is more a matter of UX than a matter of wording imo. As for the wording I'm tending toward starred but I think that's because of my affinity for GitHub 😆
@gustavo-godoy commented on GitHub (Aug 23, 2020):
What about calling them simply "Markers"? That way it still fits the booking theme while sounding differently than browser "bookmarkers". Just don't call it "dog ears" or something like that 🤣
Locale and language may also play a role in that choice. For example, in portuguese browser bookmarks are usually called favoritos ("favourited")instead, so calling the feature "favourited" would cause confusion in at least one language other than english.
@alexmannuk commented on GitHub (Aug 25, 2020):
I would suggest either Watch or Subscribe would be best. Bookmark would seem to be more like marking the last viewed page in a book, and may also be confused with Browser bookmarks, as may Favourites. Starred would commit you to using a star to mark, and intuitively seems like it would just be marking your most used pages/books. Watch and Subscribe both make it clear that you're looking for changes.
@C493 commented on GitHub (Oct 21, 2020):
I think @alexmannuk has hit the nail on the head with Watch or Subscribe. It fits with Shelves, Books, Chapters & Pages as well as being very descriptive. I would lean towards Watch/Watched myself but I find either suitable.
@dhorroxhlm commented on GitHub (Jan 5, 2021):
I think it makes sense to name the section "Watchlist". "Starred" is a strong second in my opinion, as it's a common term used throughout software packages and the web at large. Either term seems straightforward to me.
@dannyhanes commented on GitHub (Jan 5, 2021):
@VonCountHLM Starred if I am simply saving it for later. Watchlist if I am going to be emailed about changes to the page (or sub pages) +1 for watchlist if we can get that feature.
I have a "Chapter" books and would LOVE to be able to send out emails to "watcher" whenever a new page (or chapter) is added to the book.
@bridgeyuwa commented on GitHub (Mar 6, 2021):
Many Apps I have come across use starred, so I am more conversant with Star/Unstar
I vote in favor of Starred 👍
@ssddanbrown commented on GitHub (May 23, 2021):
Thanks everyone for your feedback.
In the end, when counting the comments and the various reactions on each, stars and favourites were kind of close, with 11 votes for "Favourites" to 12 votes for Stars.
In the end I've chosen "Favourites" as the wording, since I think that's the most clear wording for the feature, especially for those that may be non-technical. I feel the "Stars" option may have had a slight bias advantage since this was asked on GitHub to technical folks. A star will be used as the icon that'll sit alongside the action.
I don't want any "Watch", "Subscribe" or similar wording for this since any kind of notification/alert would be a potential secondary idea of this feature, The core function is to have a personal refined list of content within the system.
A "Favourites" system implementation has now been merged into master (Details on PR #2748) ready for the next feature release.