{"action":"created","issue":{"url":"https://api.github.com/repos/kud1ing/awesome-rust/issues/190","repository_url":"https://api.github.com/repos/kud1ing/awesome-rust","labels_url":"https://api.github.com/repos/kud1ing/awesome-rust/issues/190/labels{/name}","comments_url":"https://api.github.com/repos/kud1ing/awesome-rust/issues/190/comments","events_url":"https://api.github.com/repos/kud1ing/awesome-rust/issues/190/events","html_url":"https://github.com/kud1ing/awesome-rust/issues/190","id":170816614,"number":190,"title":"Moving away from a single markdown file?","user":{"login":"kud1ing","id":391975,"avatar_url":"https://avatars.githubusercontent.com/u/391975?v=3","gravatar_id":"","url":"https://api.github.com/users/kud1ing","html_url":"https://github.com/kud1ing","followers_url":"https://api.github.com/users/kud1ing/followers","following_url":"https://api.github.com/users/kud1ing/following{/other_user}","gists_url":"https://api.github.com/users/kud1ing/gists{/gist_id}","starred_url":"https://api.github.com/users/kud1ing/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kud1ing/subscriptions","organizations_url":"https://api.github.com/users/kud1ing/orgs","repos_url":"https://api.github.com/users/kud1ing/repos","events_url":"https://api.github.com/users/kud1ing/events{/privacy}","received_events_url":"https://api.github.com/users/kud1ing/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":11,"created_at":"2016-08-12T07:47:39Z","updated_at":"2016-08-12T21:33:10Z","closed_at":null,"body":"Since the Markdown file has grown a bit, i am considering extracting the data to a file (maybe JSON) and generating HTML from it.\r\n\r\nDisadvantages:\r\n\r\n* there is an additonal generator step\r\n* contributors might expect a Markdown file\r\n\r\nAdvantages:\r\n\r\n* the data file could be reused easier by other projects\r\n* entries can show up in multiple sections without duplicating data\r\n* less boilerplate code for contributors, less possibilities for errors\r\n* the data can be checked and enriched easier. E.g. a script could check whether the links in the data file are correct or whether projects have (now) working Travis/Cargo URLs\r\n* no manual sorting necessary anymore\r\n* consistent output format across all entries\r\n* the output format can be adjusted easier in the generator"},"comment":{"url":"https://api.github.com/repos/kud1ing/awesome-rust/issues/comments/239565140","html_url":"https://github.com/kud1ing/awesome-rust/issues/190#issuecomment-239565140","issue_url":"https://api.github.com/repos/kud1ing/awesome-rust/issues/190","id":239565140,"user":{"login":"Qard","id":205482,"avatar_url":"https://avatars.githubusercontent.com/u/205482?v=3","gravatar_id":"","url":"https://api.github.com/users/Qard","html_url":"https://github.com/Qard","followers_url":"https://api.github.com/users/Qard/followers","following_url":"https://api.github.com/users/Qard/following{/other_user}","gists_url":"https://api.github.com/users/Qard/gists{/gist_id}","starred_url":"https://api.github.com/users/Qard/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Qard/subscriptions","organizations_url":"https://api.github.com/users/Qard/orgs","repos_url":"https://api.github.com/users/Qard/repos","events_url":"https://api.github.com/users/Qard/events{/privacy}","received_events_url":"https://api.github.com/users/Qard/received_events","type":"User","site_admin":false},"created_at":"2016-08-12T21:33:10Z","updated_at":"2016-08-12T21:33:10Z","body":"I think this bikeshed should be painted blue. :trollface: \r\n\r\nSeriously though, the storage format is irrelevant. The issue is not about which storage format is superior, it's about whether the content of this repo should be accessible as data and used to generate human-consumable pages.\r\n\r\nPersonally, I don't feel like there's a lot of value to content as data for this repo. Seems to me like the effort of building a generator and converting the existing content would far outweigh the small advantage of avoiding data duplication and sorting.\r\n\r\nAs a side note, there are already tools for validating links in markdown files, so you could just use those.\r\n\r\nPersonally, I'd rather just see the single markdown file split into multiple markdown files."}}
{"actor":{"display_login":"Qard"}}