How should we sort the resources?

[IonicaBizau]

A loooong list of links will look ugly in the future. How will we group them?

[wkerswell]

I imagine into things like.

Colour resources sliders textures/images. Anything else that seem relevant

[mikedidthis]

Maybe use Github pages to make the list easier / more visually appealing?

[MFFoX]

I think concerning that actual repository, we could use a folder structure separated first by language then by resource type. Then we can have .mds that contain the lists in the folders. Some things will be multi-language or language agnostic, in which case we could keep that on a parent level.

Something like:

/languages
    /css
        /tools
            readme.md
        /resources 
            readme.md   
        /tutorials
            readme.md
       /documentation
            readme.md
       /examples (this could link to the Examples repository)
    /html
        /...
    /javascript
        /...
/online-enviroments
    /playgrounds
        readme.md
    /compilers
        readme.md
/other-language-agnostic-stuff

Then the root level readme.md can mimic the folder structure (in a more readable format) and link to nested readmes that contain the lists. The downside of this is that some of these resources are ambiguous. We could either have them in multiple places or choose a place that it fits best.

We could us a github pages with this structure as well.

Technically, we could just do this in one readme and use anchors as the separators but I see that getting unmanageable quickly.

[MadaraUchiha]

Using GitHub pages to manage it all in one page seems like a better solution to me. See http://room-11.github.io/canonical.

On Thu, Apr 24, 2014 at 5:16 PM, Carrie Kendall notifications@github.comwrote:

I think concerning that actual repository, we could use a folder structure separated first by language then by resource type. Then we can have .mds that contain the lists in the folders. Some things will be multi-language or language agnostic, in which case we could keep that on a parent level.

Something like:

/languages /css /tools readme.md /resources readme.md /tutorials readme.md /documentation readme.md /examples (this could link to the Examples repository) /html /... /javascript /... /online-enviroments /playgrounds readme.md /compilers readme.md /other-language-agnostic-stuff

Then the root level readme.md can mimic the folder structure (in a more readable format) and link to nested readmes that contain the lists. The downside of this, is that some of these resources are ambiguous. We could either have them in multiple places or choose a place that it fits best.

We could us a github pages with this structure as well.

Technically, we could just do this in one readme and use anchors as the separators but I see that getting unmanageable quickly.

— Reply to this email directly or view it on GitHubhttps://github.com/HTML-CSS-DOM-chat/Resources/issues/4#issuecomment-41284922 .

[MFFoX]

so you'd rather keep it static on one page?

[IonicaBizau]

I also like the idea of a single static page. And yes, GitHub pages is a good solution, in my opinion.

[MFFoX]

I like the idea of using github pages, but I don't like the idea of storing the resources in javascript.

[IonicaBizau]

We can store them in JSON files (in this repository) and parse them with some JavaScript in a GitHub page.

[MFFoX]

Sounds good to me. I'm still in favor of categorizing the resources using a structure similar to https://github.com/HTML-CSS-DOM-chat/Resources/issues/4#issuecomment-41284922.

[MadaraUchiha]

Yeah, Static in JSON format on the same file (or on a different file) and parse it to full fledged DOM with JavaScript. See the source on the link I shared above, it does just that.

On Thu, Apr 24, 2014 at 6:47 PM, Ionică Bizău notifications@github.comwrote:

We can store them in JSON files (in this repository) and parse them with some JavaScript in a GitHub page.

— Reply to this email directly or view it on GitHubhttps://github.com/HTML-CSS-DOM-chat/Resources/issues/4#issuecomment-41296169 .

[IonicaBizau]

@MFFoX Sure, categorizing will be needed. We just need to think how a JSON document will look like.

{
    "url": "http://example.com"
  , "description": "Some interesting stuff"
  , "category": "languages.css.tools"
  , ???
}

[mikedidthis]

I am going to leave you guys to it, as I feel JSON is overkill for something we could do with HTML.

However if you need help with styling the page, ping me.

[MadaraUchiha]

Yeah, maybe with an image/screenshot.

@mikedidthis The reason JSON is the best, is because it's more structured and easily alterable. You don't need to know HTML to add/change items, also, it eliminates the possibility of dissimilarity with the HTML markup when adding new items. It's a bit more overhead to begin with, but it pays off in the future.

[IonicaBizau]

+1, Also, we will be able to export the resources in any format we want.

[ghost]

I'm in support of JSON, and the folder structure proposed.