ritredteam / ritredteam.github.io Goto Github PK

Reopening this comment from @mav8557 because I think it has some merit. It might need some more work but I also think the structure could be played around with more.

A details.md file for each tool, that describes how it works with some of the relevant resources could be helpful, especially if it is doing anything especially esoteric. That would be optional but encouraged, so that people in the future can hit the ground running both with how to use a tool and what it is actually doing in reasonably comprehensive detail.

I'm about 50/50 on the layout. It works but I think it could get hard to maintain and follow this way. Seeing cross-platform tools under Linux, Windows, etc would be nice. Duplication is not a good idea - some way to search or have tags for tools would be ideal.

I think a good compromise would be to just have a directory for every tool, and then link to those tool pages from the OS group page.

Something like this:

index.md
tools/
      vishnu/
          index.md
          details.md
      father/
          index.md
          details.md
      nosferatu/
          index.md
          details.md
windows/
      index.md
linux/
      index.md
...

This way what changes often is easier to find and edit, you get a centralized place to see every red team tool, and it's easy to add tools to OS group pages.

Most pages sites use Jekyll and it's helpful to be able to build the entire site locally, to see how things look before pushing to production.

Ideally this should be a docker-compose file to easily create the container and serve it locally. I had some issues getting this to build locally myself so I figured I'd open this up so we can get it going before we have folks start contributing more frequently.