Create additional-resources page

[denar90]

Todo

• [x] Update awesome list with resources for main page
• [x] Parse topics from awesome list file using grunt
• [x] Automatically generate data files for topics: Tutorials and articles, Books, Videos,Examples and boilerplates, Libraries
• [x] Make data for Books topic the same structure as books.json
• [x] Make data for Videos topic the same structure as videos.json
• [x] Create examples.json using github API.
• [x] Cut some resources from main page
• [x] Add links to "Additional resources page" on menu and other places
• [x] Add tests

[jdaudier]

Would be great to allow flexibility to exclude or add to the parsed list from Awesome list.

[denar90]

I've also been thinking to write some tests for compilers using AVA. It really good works with promises. I've added some example for my compiler but soon we can cover all of them.

[denar90]

About videos file. After creating json from list we can send request and get youtube video data. But problem in format. Format for video described here can't be reached by format which youtube provide with:

{
 "kind": "youtube#videoListResponse",
 "etag": "\"zekp1FB4kTkkM-rWc1qIAAt-BWc/YEXgZysUsYLiaQP-TsJ06g5fKic\"",
 "pageInfo": {
  "totalResults": 1,
  "resultsPerPage": 1
 },
 "items": [
  {
   "kind": "youtube#video",
   "etag": "\"zekp1FB4kTkkM-rWc1qIAAt-BWc/2vl2mbQ52e_OMWORgKaIpNlfrbA\"",
   "id": "jbGm3mJXh_s",
   "snippet": {
    "publishedAt": "2014-12-17T17:11:38.000Z",
    "channelId": "UCQUPI1PxfE4-bqwuI26I2HA",
    "title": "Jason Laster - Backbone under the Magnifying Glass Tools for Exploring and Debugging Your Apps",
    "description": "",
    "thumbnails": {
     "default": {
      "url": "https://i.ytimg.com/vi/jbGm3mJXh_s/default.jpg",
      "width": 120,
      "height": 90
     },
     "medium": {
      "url": "https://i.ytimg.com/vi/jbGm3mJXh_s/mqdefault.jpg",
      "width": 320,
      "height": 180
     },
     "high": {
      "url": "https://i.ytimg.com/vi/jbGm3mJXh_s/hqdefault.jpg",
      "width": 480,
      "height": 360
     },
     "standard": {
      "url": "https://i.ytimg.com/vi/jbGm3mJXh_s/sddefault.jpg",
      "width": 640,
      "height": 480
     },
     "maxres": {
      "url": "https://i.ytimg.com/vi/jbGm3mJXh_s/maxresdefault.jpg",
      "width": 1280,
      "height": 720
     }
    },
    "channelTitle": "BocoupLLC",
    "tags": [
     "Open Web",
     "JavaScript",
     "Programming",
     "Open Source",
     "Bocoup"
    ],
    "categoryId": "28",
    "liveBroadcastContent": "none",
    "localized": {
     "title": "Jason Laster - Backbone under the Magnifying Glass Tools for Exploring and Debugging Your Apps",
     "description": ""
    }
   }
  }
 ]
}

Can I change format a bit due to youtube API ?

[peterblazejewicz]

@denar90 Yes, you can I think. The format (and data description/names) does not matter. What matters is to be sure that data from JSON is outputted to static html markup. We just use this information to enhance crawlers and screen readers (so Marionette has good generic traffic from the net)

[denar90]

@peterblazejewicz Can moving some sections (books, videos. example apps) from main page to additional resources page have bad effect on traffic?

[peterblazejewicz]

Can moving some sections (books, videos. example apps) from main page to additional resources page have bad effect on traffic?

No (if done while preserving markup and document outline/sections). Just go ahead and it could be later reviewed. btw: that's about library discoverability - not traffic :) Thanks!

[denar90]

What do you think about using our own awesome list? We can make fork of original one and prepare format what we need. Because in some places instead of line A Thorough Introduction To Backbone.Marionette by Joseph Zimmerman - [Part 1](some_link), [Part 2](some_link) and [Part 3](some_link) we should parse lines like

 [A Thorough Introduction To Backbone.Marionette by Joseph Zimmerman, Part 1](some_link)
 [A Thorough Introduction To Backbone.Marionette by Joseph Zimmerman, Part 2](some_link)
 [A Thorough Introduction To Backbone.Marionette by Joseph Zimmerman, Part 3](some_link)

Or in original repo we can try to change contributing instructions so format will support our needs (compiler needs).

[peterblazejewicz]

A Thorough Introduction To Backbone.Marionette by Joseph Zimmerman - Part 1, Part 2 and Part 3

Splitting or rewriting this could be an overkill - the Google or Bing are smart enough to crawl a real meaning/title of the link I believe - the link's target origin content heading/page is important (their relevance to the link source, uniqueness, etc)

[denar90]

Sorry, I've read contributing

Use the following format: List Name

Maybe list was made before awesome contributing file was changed, so task

Update awesome list with resources for main page

became more interesting)

[denar90]

merged #453