You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imagine I want to build a hacking documentation with a tree like that (for, let's say, my OSCP exam preparation):
- Admin # Machines from the Admin network, containing a write-up for each machine
- Machine 1 # tags: [eop,windows]
- Machine 2 # tags: [network,linux]
- ...
- Cheat sheets # for various topics
- Elevation of Privilege # tags: [eop]
- Metasploit # tags: [exploit]
- MS SQL Server # tags: [mssql,windows]
- Network # tags: [network]
- PWK/OSCP Specific
- Pivoting # tags: [pivoting,network]
- ...
- Connectivity
- Machines
- PWK Lab
- Remote desktop
- ssh-hostkey # tags: [ssh]
- Dev # Machines from the Dev network, containing a write-up for each machine
- Machine 1
- Machine 2
- ...
- Exam
- Exam specific
- ...
- IT # Machines from the IT network, containing a write-up for each machine
- Machine 1
- Machine 2
- ...
- Public # Machines from the Public network, containing a write-up for each machine
- Machine 1
- Machine 2
- ...
- Tools
- Nmap # tags: [network,scanner]
- John the ripper # tags: [cracking,password,hash]
- gcc # tags: [compilation,exploit]
- dnsrecon # tags: [osint,dns]
- dnsenum # tags: [osint,dns]
- cmsmap # tags: [cms,web]
- ncat # tags: [backdoor,network,scanner]
- recon-ng tags: [osint]
- snmpwalk # tags: [snmp,network]
- snmpbrute # tags: [snmp,network]
- onesixtyone # tags: [snmp,network]
- ...
So I want to be able to search for a keyword (tag) like snmp and see all machines write-up where I attacked snmp, all cheat sheets explaining snmp stuff, all tools I can use to exploit snmp, etc.
Without tag support this is impossible.
One could say: "But there is already the search feature parsing the content of pages" yeah but this is automatic and introduce a lot of false positive (content containing a keywork but not really about it) and false negative (content not containing the keywork but actually talking about it) when the tag feature will be manual so there will be only exact matches.
I could also provide argumentation Why this shouldn't be theme dependent or plugin based. Some big companies like Docker, Joomla, or the Mozilla foundation are using documentation with tags.
Proposed Solution
Adding tags (keywords) in front-matter (see #2142) (meta-data) will generate a page referencing all pages containing this page.
Then on the page of the documentation where there is such a tags front-matter, the page will contain some tag link #dev and #python respectively referencing the previously mentioned endpoints.
Example on my blog using Hexo:
Notes
No response
The text was updated successfully, but these errors were encountered:
Problem
Imagine I want to build a hacking documentation with a tree like that (for, let's say, my OSCP exam preparation):
So I want to be able to search for a keyword (tag) like snmp and see all machines write-up where I attacked snmp, all cheat sheets explaining snmp stuff, all tools I can use to exploit snmp, etc.
Without tag support this is impossible.
One could say: "But there is already the search feature parsing the content of pages" yeah but this is automatic and introduce a lot of false positive (content containing a keywork but not really about it) and false negative (content not containing the keywork but actually talking about it) when the tag feature will be manual so there will be only exact matches.
I could also provide argumentation Why this shouldn't be theme dependent or plugin based. Some big companies like Docker, Joomla, or the Mozilla foundation are using documentation with tags.
Proposed Solution
Adding tags (keywords) in front-matter (see #2142) (meta-data) will generate a page referencing all pages containing this page.
Example:
In front-matter you add (in YAML for example):
So it will create an endpoint http://example.org/tags/dev and http://example.org/tags/python referencing, respectively, all pages containing the dev tag and the python tag.
Then on the page of the documentation where there is such a tags front-matter, the page will contain some tag link #dev and #python respectively referencing the previously mentioned endpoints.
Example on my blog using Hexo:
Notes
No response
The text was updated successfully, but these errors were encountered: