{"action":"created","issue":{"url":"https://api.github.com/repos/aurelia-ui-toolkits/global-issues/issues/4","repository_url":"https://api.github.com/repos/aurelia-ui-toolkits/global-issues","labels_url":"https://api.github.com/repos/aurelia-ui-toolkits/global-issues/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/aurelia-ui-toolkits/global-issues/issues/4/comments","events_url":"https://api.github.com/repos/aurelia-ui-toolkits/global-issues/issues/4/events","html_url":"https://github.com/aurelia-ui-toolkits/global-issues/issues/4","id":191754467,"number":4,"title":"Expanding the concept of the \"aurelia plugins catalog\" application","user":{"login":"adriatic","id":2712405,"avatar_url":"https://avatars.githubusercontent.com/u/2712405?v=3","gravatar_id":"","url":"https://api.github.com/users/adriatic","html_url":"https://github.com/adriatic","followers_url":"https://api.github.com/users/adriatic/followers","following_url":"https://api.github.com/users/adriatic/following{/other_user}","gists_url":"https://api.github.com/users/adriatic/gists{/gist_id}","starred_url":"https://api.github.com/users/adriatic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adriatic/subscriptions","organizations_url":"https://api.github.com/users/adriatic/orgs","repos_url":"https://api.github.com/users/adriatic/repos","events_url":"https://api.github.com/users/adriatic/events{/privacy}","received_events_url":"https://api.github.com/users/adriatic/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-11-25T19:02:59Z","updated_at":"2016-11-28T06:32:56Z","closed_at":null,"body":"### Introduction\r\nThis is a long standing issue, which got a significant boost today, by an almost casual remark by Rob:\r\n\r\n> At some point in the future, I would like to explore how we can potentially integrate the catalog you built into our official docs. \r\n\r\nSeveral months ago (before Monterey's time) this would be less inspiring to me at least, as in all previous discussions we had, the subject was the use of **`aurelia docs api`** so far used in **[`aurelia HUB`](http://aurelia.io/hub.html#/doc/persona/developer)** as the building block of Aurelia-UI-Toolkits bridge catalog applications (**[kendoUI](http://aurelia-ui-toolkits.github.io/demo-kendo/#/about/about)**, **[materialize](http://aurelia-ui-toolkits.github.io/demo-materialize/)** and **[Syncfusion](http://aurelia-ui-toolkits.github.io/demo-syncfusion/)**).\r\n\r\nIt is the planned support for the package importer module for **[aurelia-cli](https://github.com/aurelia/cli)** tool that allows us to create a more ambitious plan: a **`catalog`** of all aurelia plugins which will allow the aurelia community a uniform, guided access to all existing plugins.\r\n\r\n***\r\n\r\n### Properties of Aurelia-UI-Toolkits bridge catalog applications\r\n\r\nThis is a brief summary of the catalog application architecture, needed to initiate the discussion and the design if the next generation of the catalog app mentioned in the Introduction section above\r\n\r\nThe **`catalog`** is a very lightweight ___container___, hosting just the basic application's skeleton, where all of the frequently changing components are external. This allows `catalog` maintenance without the rebuilding the app in most of the cases. The screen shot below indicates the `catalog` sections that reside outside the `catalog` app.\r\n\r\n![ice_screenshot_20161125-171336](https://cloud.githubusercontent.com/assets/2712405/20636476/6d940110-b333-11e6-9d2c-3d14e9d382d6.png)\r\n\r\nEqually important, all of the `catalog`'s main content (list of all Aurelia components, with examples how to use them) is also not a part of the application itself. All this information is organized in the form of GitHub **[Gists](https://gist.github.com/)** - click **[here](https://gist.run/?id=c76e763d64c2d3244e222d32f0de062f)** to run see the gist that renders the `catalog`s **[basic listview component](http://aurelia-ui-toolkits.github.io/demo-kendo/#/samples/listview-basic-use)**:\r\n\r\n![ice_screenshot_20161125-173017](https://cloud.githubusercontent.com/assets/2712405/20636590/03fc8eb4-b335-11e6-8ae3-a7e7a75ba635.png)\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/aurelia-ui-toolkits/global-issues/issues/comments/263193641","html_url":"https://github.com/aurelia-ui-toolkits/global-issues/issues/4#issuecomment-263193641","issue_url":"https://api.github.com/repos/aurelia-ui-toolkits/global-issues/issues/4","id":263193641,"user":{"login":"JeroenVinke","id":2189477,"avatar_url":"https://avatars.githubusercontent.com/u/2189477?v=3","gravatar_id":"","url":"https://api.github.com/users/JeroenVinke","html_url":"https://github.com/JeroenVinke","followers_url":"https://api.github.com/users/JeroenVinke/followers","following_url":"https://api.github.com/users/JeroenVinke/following{/other_user}","gists_url":"https://api.github.com/users/JeroenVinke/gists{/gist_id}","starred_url":"https://api.github.com/users/JeroenVinke/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JeroenVinke/subscriptions","organizations_url":"https://api.github.com/users/JeroenVinke/orgs","repos_url":"https://api.github.com/users/JeroenVinke/repos","events_url":"https://api.github.com/users/JeroenVinke/events{/privacy}","received_events_url":"https://api.github.com/users/JeroenVinke/received_events","type":"User","site_admin":false},"created_at":"2016-11-28T06:32:56Z","updated_at":"2016-11-28T06:32:56Z","body":"We use `<compose view-model=\"jeroenvinke.nl/gist/<gist id>/app\">` to run gists in the catalog. So the app.html, app.js (and any resources in app.html etc) but **not** index.html of the gist, are pulled in just like \"normal\" files. Since the css of gists are loaded in index.html, and we do not load this index.html in the catalog, the compose tag renders without any style. Because of the compose tag, they also run in the context of the app (it is not an iframe or anything), so the css of the catalog is applied to the gists. And this css is switched via the theme switcher\r\n\r\n\r\n\r\n\r\n"}}
{"actor":{"display_login":"JeroenVinke"}}