Create General Tags in order to classify Docs / And create Special security tag for Classification of the Docs : public, intern, sensitive information, do not share, secret etc..

Open
#2,267 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Domain
content

Research direction

No files, tests, or entry points are named. First clarify the scope and security-tag rules with maintainers, then trace the existing document metadata and tag interfaces; done should include agreed general and single-choice security tags, with the requested visibility on document pages.

Written by the indexing model from the issue text.

Description

backend drive feature frontend

Feature Request

Is your feature request related to a problem or unsupported use case? Please describe.
It could be great to be able to create some tags for the docs.
So user can classify them.
Users could create a tag in order to explain what is the nature of the tags (for exemple "UX, Human resssrouces, marketig, communication team etc..)

Image

Describe the solution you'd like

Describe alternatives you've considered
one special need for the administrations, is also to be able to tag a docs bteween 3 ou 4 types of "status security tags" of the nature of the document.
The user wold be able to only choose one of them: public, intern, sensitive information, don't share, secret etc..

Image

These "security tags" could be addition to the general tags created by the user.

These Genral tags, or at least the "secrity tags" should be also visible on the front page of the document:

Image
Dominant language
Python
Stars
16.8k
Forks
638
Avg merge
1d 15h
Merged PRs (30d)
40

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from suitenumerique/docs

All issues in suitenumerique/docs

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.