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

Page Tags Improvements #121

Di2g10 opened this Issue Jun 2, 2016 · 2 comments


3 participants

Di2g10 commented Jun 2, 2016

Some comments on ways to improve tag implementation

  • Can the suggestion list populated with all previously used Tags before any text is entered so i don't have to remember what the tag values where. (apply to tag values as well)
  • Tag Value Suggestions are limited to values used previously only for the related tag.(Rather than any tag value used anywhere)
  • The ability to apply tags at the book and chapter level. Potentially these would then auto tag pages underneath them.
  • Ideally i would have liked more controls on available tags and tag values i.e. forcing tag use or linking some tags to only be available based on other tags. However this may affect easy of use.

This comment has been minimized.

bridgeyuwa commented Jun 3, 2016

Very nice suggestion

ssddanbrown added a commit that referenced this issue Jun 4, 2016

ssddanbrown added a commit that referenced this issue Jun 4, 2016

Added tag autosuggestion when no input provided
Shows the most popular tag names/values.
As requested on #121

@ssddanbrown ssddanbrown added this to the BookStack Beta v0.21.0 milestone Mar 27, 2018


This comment has been minimized.


ssddanbrown commented Mar 27, 2018

Added to milestone for next release.
Done a couple of the original points already.

For next release the focus will be just to finish off the implementation of the base tags implementation by adding to Books and Chapters. Once this is done I will close off this issue. For further changes or to re-request remaining features feel free to open new, specific issues.

To be honest, I think the remaining features are a little too specific at this stage for the implementation/maintenance effort. Good ideas though.

@ssddanbrown ssddanbrown self-assigned this Mar 27, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment