Format for resources as data: Extension for new site

[Mikael Brevik]

When doing the re-design, we should have all resources as data, to be able to se it in different ways. By having json data we can make filtering, sorting, grouping, APIs etc.

This issue is to discuss the format for this structure.

My thoughts:

[
  {
   "title": String,
   "link": String,
   "author": Array<String>,
   "level": String, // (beginner | intermediate | advanced)
   "description": Optional<String>,
   "type": String, // (video | article | blogpost | tutorial | book|)
   "topic": String, // (node | architecture | ... ) ?
   "keywords": Array<String>, // Might void topic?


   "hashtag": String, // Potential twitter hashtag to tweet under?
   "priority": int, // to have order? Or just alphabetically?
  }
]

[Kim Joar Bekkelund]

I like it.

There are potentially several authors per resource (Irish and Osmani on one today, at least). Maybe just authors and Array<String>?

Maybe level could just be beginner, intermediate and advanced? Simpler to classify, simpler to understand.

I like having a main topic (i.e. our classification) and then potentially having keywords in addition.

[Mikael Brevik]

Good thinking! I've updated the schema