Add a resource section

[ctmbl]

This is an old idea for the iscsc blog/website: a place where to store interesting resources we may find or give to new users interested into various subject we do! Non exhaustive list:

• cybersecurity resources
• network
• docker/containerization/virtualization
• various programming language
• useful tools for Linux/Windows system (IDE, DM, editors, shells...)
• other low level subjects: Linux/Windows insides, assembly,...

[Turtyo]

Who would be able to add resources ? It might also be interesting to have a way to sort the resources by difficulty levels.

[ctmbl]

@Turtyo Basically everyone, on the same model as blog posts, see https://iscsc.fr/posts/publish-your-own-post/ And yes sure, we could use tags or special tags to sort them by difficulty

[Turtyo]

Yes I see there is already a tagging system with the blog posts. How would the resource section be different from the normal posts if everyone can contribute to it ? This feels like a blog post with extra steps for now

[ctmbl]

@Turtyo Nop I imagine it more lightweight and organised differently. but sure it would be a good thing to debate about the aspect organisation and use-cases!

We could also adopt an iterative approach. With this in mind, I suggest the following:

• two views/endpoints:
  • /resources: a single page with every resource ordered in lists and sublists such as:

    /resources
    |_ OSes
    |_ Linux
    |_ Windows
    |_ Cybersecurity
    |_

    of course such a hierarchy would be arbitrary, and probably not very handy. Some resources might go in multiple cases, hence a second endpoint, that I hope complementary to this first one:

  • /resources/tags (or /rtags or /resources_tags... the name doesn't matter) that would fill the same purpose that the tag system for articles: we'd have the possibility of registering multiple tags for each resource allowing an easy finding!
• a single file storing unsorted resources entries: this file would just be a database of resources entries, for example a json, toml or yml file:

  resources:
  - my_res:
  - url:
  - title:
  - tags:

All of this is just my ideas at the moment but I'd be happy to here others!

[Turtyo]

I think we could just have the tagging system as a singular entry point, and list everything under it, updating the list that is shown as the user adds tags (and thus reducing the possibilities). This would be less confusing than a dual endpoint imo. I am not sure what the purpose of a json file listing all resources would be, if tag endpoint already does that, could you explain ?

[ctmbl]

I think we could just have the tagging system as a singular entry point, and list everything under it, updating the list that is shown as the user adds tags (and thus reducing the possibilities).

great idea! I'll keep it for sure

I am not sure what the purpose of a json file listing all resources would be, if tag endpoint already does that, could you explain ?

You still need somewhere to store your resources, something that isn't shown directly to the user but parsed by the website (like a View is different from a Model in the Model-View-Controller framework) This file can be a big list of entries, yml, json, toml, ...

[Turtyo]

Oh I see, this wouldn't be visible to the user, i understand