{"action":"created","issue":{"url":"https://api.github.com/repos/jaws-stack/JAWS/issues/41","labels_url":"https://api.github.com/repos/jaws-stack/JAWS/issues/41/labels{/name}","comments_url":"https://api.github.com/repos/jaws-stack/JAWS/issues/41/comments","events_url":"https://api.github.com/repos/jaws-stack/JAWS/issues/41/events","html_url":"https://github.com/jaws-stack/JAWS/issues/41","id":100130559,"number":41,"title":"JAWS React Front-End Module: Design Specs & Help Wanted","user":{"login":"ac360","id":2752551,"avatar_url":"https://avatars.githubusercontent.com/u/2752551?v=3","gravatar_id":"","url":"https://api.github.com/users/ac360","html_url":"https://github.com/ac360","followers_url":"https://api.github.com/users/ac360/followers","following_url":"https://api.github.com/users/ac360/following{/other_user}","gists_url":"https://api.github.com/users/ac360/gists{/gist_id}","starred_url":"https://api.github.com/users/ac360/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ac360/subscriptions","organizations_url":"https://api.github.com/users/ac360/orgs","repos_url":"https://api.github.com/users/ac360/repos","events_url":"https://api.github.com/users/ac360/events{/privacy}","received_events_url":"https://api.github.com/users/ac360/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/jaws-stack/JAWS/labels/enhancement","name":"enhancement","color":"84b6eb"},{"url":"https://api.github.com/repos/jaws-stack/JAWS/labels/help%20wanted","name":"help wanted","color":"159818"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-08-10T17:58:10Z","updated_at":"2015-08-11T02:57:40Z","closed_at":null,"body":"**This thread is for discussing the `JAWS-site-react` module's design and finding developers who want to help build it**\r\n\r\nOverall, JAWS should support all front-end frameworks.  There has been a lot of demand for JAWS + React support.  So, let's start with React!\r\n\r\nJAWS already comes with a `site` module.  But you should be able to swap this out with another `site` module that is focused on a specific front-end framework.  So, I'm proposing a new `JAWS-site-react` module/repo, which will contain JAWS + React boilerplate.  Here are some design considerations:\r\n\r\n* **Keep It Simple:**  There should be little bloat in this module.  This module is for convenience, not strong opinions and obscure React patterns.  Make it the best possible starting point for a React project, that is all.\r\n  \r\n* **Make It Extendable**  While this module is meant for convenience, there should be some mechanism for plugging in other JAWS + React modules.  There have been lots of requests to do AWS stuff without API Gateway, since many tasks can be accomplished by using the AWS JS SDK in the browser to interact directly with AWS services.  For example, a `JAWS-site-react-s3-upload` module would be incredibly useful and fast since it would upload from the browser, directly to S3.  This module needs to also contain config files for the AWS Browser JS SDK and make them accessible to other JAWS + React modules.\r\n\r\n* **Integrate With JAWS REST API**  JAWS will have Swagger integration finished soon.  There should be some service that allows you easily interact with your JAWS REST API.  Keeping this simple again is key.  Perhaps we can get the `JAWS-cli` to automatically scaffold this for you based on your Swagger JSON.\r\n\r\nThese are just my opinions.  Please contribute your thoughts/ideas/advice.  Also, I'm not a great React developer, so I'm looking for some better people to take the lead on this.  If you'd like to do that, please say so here :)"},"comment":{"url":"https://api.github.com/repos/jaws-stack/JAWS/issues/comments/129686705","html_url":"https://github.com/jaws-stack/JAWS/issues/41#issuecomment-129686705","issue_url":"https://api.github.com/repos/jaws-stack/JAWS/issues/41","id":129686705,"user":{"login":"SOSANA","id":2634185,"avatar_url":"https://avatars.githubusercontent.com/u/2634185?v=3","gravatar_id":"","url":"https://api.github.com/users/SOSANA","html_url":"https://github.com/SOSANA","followers_url":"https://api.github.com/users/SOSANA/followers","following_url":"https://api.github.com/users/SOSANA/following{/other_user}","gists_url":"https://api.github.com/users/SOSANA/gists{/gist_id}","starred_url":"https://api.github.com/users/SOSANA/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SOSANA/subscriptions","organizations_url":"https://api.github.com/users/SOSANA/orgs","repos_url":"https://api.github.com/users/SOSANA/repos","events_url":"https://api.github.com/users/SOSANA/events{/privacy}","received_events_url":"https://api.github.com/users/SOSANA/received_events","type":"User","site_admin":false},"created_at":"2015-08-11T02:57:40Z","updated_at":"2015-08-11T02:57:40Z","body":"opening pandora's box with flux implementation @mbreton lol this is where the real debate starts, \r\n@ac360 made a great comment about \"Currently, I think JAWS should support multiple front-end frameworks, and each should have their own repo within the JAWS organization\"\r\n\r\nutilizing modules is the way to go under the jaws organization. I think for demo purposes simple hello with basic routes implemented, but if other maintiners want to add addional modules with implementation I think that is under consideration :), that way we have the freedom to implement any bleeding edge technologies modules with various implementations, add that my vote +1\r\n"}}