{"action":"created","issue":{"url":"https://api.github.com/repos/brunch/brunch-guide/issues/3","labels_url":"https://api.github.com/repos/brunch/brunch-guide/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/brunch/brunch-guide/issues/3/comments","events_url":"https://api.github.com/repos/brunch/brunch-guide/issues/3/events","html_url":"https://github.com/brunch/brunch-guide/issues/3","id":66262165,"number":3,"title":"My review","user":{"login":"paulmillr","id":574696,"avatar_url":"https://avatars.githubusercontent.com/u/574696?v=3","gravatar_id":"","url":"https://api.github.com/users/paulmillr","html_url":"https://github.com/paulmillr","followers_url":"https://api.github.com/users/paulmillr/followers","following_url":"https://api.github.com/users/paulmillr/following{/other_user}","gists_url":"https://api.github.com/users/paulmillr/gists{/gist_id}","starred_url":"https://api.github.com/users/paulmillr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/paulmillr/subscriptions","organizations_url":"https://api.github.com/users/paulmillr/orgs","repos_url":"https://api.github.com/users/paulmillr/repos","events_url":"https://api.github.com/users/paulmillr/events{/privacy}","received_events_url":"https://api.github.com/users/paulmillr/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-04-04T01:53:04Z","updated_at":"2015-04-04T17:31:11Z","closed_at":null,"body":"I think the live reloading itself is worth a small chapter.\r\n\r\n## Chapter 1\r\n\r\n1. Is there any point in mentioning glou at all? It was downloaded just 222 times within one month. No one knows about it.\r\n\r\n## Chapter 2\r\n\r\n1. Maybe add a link to Node + NPM itself for those who didn't heard about it (there may be someone)\r\n2. Should we promote default names for skeletons? @es128 i've started adding those in recent init-skeleton update. E.g. `brunch new angular` instead of gh repo.\r\n\r\n## Chapter 3\r\n\r\n1. Any value in adding link to brunch docs chapter for each convention?\r\n    > Customizing: source paths can be changed through an array of names/paths in the paths.watched setting. The target folder is set by paths.public. Special-treatment folders are defined through conventions.assets and conventions.vendor (which can be regexes or functions). Ignored files (not processed standalone, that is) are specified in conventions.ignored.\r\n2. [ ] Let's review the statement once 1.8 is released\r\n   > Do note that watching is not always 100% reliable, though, usually on Windows, more rarely on Linux or OSX (this is true as of 1.7.20; the next release should have improved things in this regard). A couple settings can help reduce what rare faux-pas you could see, we’ll explore these later.\r\n3. \"By the way, you can also get notified\" — how? We should probably add the install command.\r\n4. For webserver, we should probably just treat `brunch-server.coffee` as default server file that would be auto-consumed. \r\n\r\n## Chapter 5\r\n\r\n1. `bower install --save jquery#1.*` — a bit too cryptic maybe\r\n2. `/^bower_components/` — this won't include auto-reload which may confuse future user, maybe just `/^(?!app)/`\r\n\r\n## Chapter 9\r\n\r\n>So yeah, for JS and CSS builds, we went “overboard” to an average 200ms, but that’s mostly because we embed heavy JS libs (jQuery 1.11, etc.) and heavy CSS (all of Bootstrap 3), so even with an incremental build, we write “fat” files:\r\n\r\nJS libs are not the reason of \"200ms slowness\". Rather, it's jade compiler. We may say that we are doing some work in this direction to speed-up all compilers to work best  with brunch. (`fcache`)\r\n\r\n## Plugins\r\n\r\nIt's worth noting that **plugin order matters** (in package.json). For plugins that do stuff to same files.\r\n\r\nThe chapter feels too long when compared to others — worth splitting it into two?"},"comment":{"url":"https://api.github.com/repos/brunch/brunch-guide/issues/comments/89622787","html_url":"https://github.com/brunch/brunch-guide/issues/3#issuecomment-89622787","issue_url":"https://api.github.com/repos/brunch/brunch-guide/issues/3","id":89622787,"user":{"login":"es128","id":1740641,"avatar_url":"https://avatars.githubusercontent.com/u/1740641?v=3","gravatar_id":"","url":"https://api.github.com/users/es128","html_url":"https://github.com/es128","followers_url":"https://api.github.com/users/es128/followers","following_url":"https://api.github.com/users/es128/following{/other_user}","gists_url":"https://api.github.com/users/es128/gists{/gist_id}","starred_url":"https://api.github.com/users/es128/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/es128/subscriptions","organizations_url":"https://api.github.com/users/es128/orgs","repos_url":"https://api.github.com/users/es128/repos","events_url":"https://api.github.com/users/es128/events{/privacy}","received_events_url":"https://api.github.com/users/es128/received_events","type":"User","site_admin":false},"created_at":"2015-04-04T17:31:11Z","updated_at":"2015-04-04T17:31:11Z","body":"Uh yeah, I can't double check atm, but I think this concern about the plugin includes was already resolved - and that the regex joinTo would have actually worked fine. "}}