-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
docs: drop list.rst and code behind it #7436
Conversation
# Conflicts: # doc/list.rst # src/Documentation/ListDocumentGenerator.php
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general I agree, the simpler page (variant A) is enough for explaining what each rule does, and when anyone can look deeper, then can go the rule's page. I would only ask if it's possible to make some redirect from the B's URL to A's? If not then it's OK too 😉.
(not giving approval because auto-merge is enabled, and I leave an option for suggestion above)
redirection on repo files:
redirection on website:
yet... ref
meaning:
|
Yeah, I got that it's not linked anywhere, I was thinking only about places outside of the docs where it could be linked. It's not a big deal if it can't be linked. In Hugo pages can have aliases so some kind of "redirector" pages are generated alongside the actual ones, I was wondering if it's possible to apply similar approach with |
likely there is possibility to have it on whatever generating website nowadays (or added on top of it). |
We have 2 docs for rules:
doc B is not listed anywhere, it's big and clumsy, 2 files are same purpose - index of rules that one can find what they look for and go for fixer details page if needed.
I suggest we drop doc B