{"action":"created","issue":{"url":"https://api.github.com/repos/jhipster/generator-jhipster/issues/1881","labels_url":"https://api.github.com/repos/jhipster/generator-jhipster/issues/1881/labels{/name}","comments_url":"https://api.github.com/repos/jhipster/generator-jhipster/issues/1881/comments","events_url":"https://api.github.com/repos/jhipster/generator-jhipster/issues/1881/events","html_url":"https://github.com/jhipster/generator-jhipster/issues/1881","id":101548054,"number":1881,"title":"Reorganizing the JHipster documentation","user":{"login":"michaelisvy","id":1440137,"avatar_url":"https://avatars.githubusercontent.com/u/1440137?v=3","gravatar_id":"","url":"https://api.github.com/users/michaelisvy","html_url":"https://github.com/michaelisvy","followers_url":"https://api.github.com/users/michaelisvy/followers","following_url":"https://api.github.com/users/michaelisvy/following{/other_user}","gists_url":"https://api.github.com/users/michaelisvy/gists{/gist_id}","starred_url":"https://api.github.com/users/michaelisvy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/michaelisvy/subscriptions","organizations_url":"https://api.github.com/users/michaelisvy/orgs","repos_url":"https://api.github.com/users/michaelisvy/repos","events_url":"https://api.github.com/users/michaelisvy/events{/privacy}","received_events_url":"https://api.github.com/users/michaelisvy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-08-18T01:51:27Z","updated_at":"2015-08-18T20:13:15Z","closed_at":null,"body":"Hi,\r\nI think the JHipster documentation is getting big and it would be nice to reorganize it so users can find information faster. \r\n\r\nMain goals: \r\n- avoid to use words such as \"introduction\", \"setup\", \"presentation\" etc and try to be more specfic\r\n- some pages should be broken into several pages  (such as \"Using in development\")\r\n- Separate out \"environment setup\" from \"core JHipster tasks\" such as creating an entity\r\n\r\n\r\nWhat would you think of the below structure?\r\n\r\n1) JHipster in 5 minutes (currently called \"introduction\")\r\n* Technical stack\r\n* Official JHipster slides (currently called \"presentation\")\r\n* JHipster in 5 screenshots\r\n* Video tutorial\r\n\r\n2) Setting up your environnement\r\n* Install JHispter\r\n* Install a new language\r\n* Configure JHipster in Eclipse\r\n* Configure JHispter in IntelliJ IDEA\r\n* Contributors: installing a development environment\r\n\r\n3) Core JHipster tasks\r\n* Creating a JHipster application\r\n* Creating an entity\r\n* Creating a service\r\n* Managing relationships\r\n* Creating DTOs\r\n\r\n4) Understanding and customizing generated code\r\n* AngularJS generation (currently called \"Development/Using AngularJS\")\r\n* Customizing CSS (currently called \"Customizing Bootstrap\")\r\n* Automated tests (currently inside \"Test/running tests\")\r\n\r\n\r\n5) Running JHipster \r\n(currently inside \"Using in development\" page that should be split into several pages)\r\n\r\n6) Third party integrations\r\n* Elastic Search \r\n* Cassandra\r\n* MongoDB\r\n* Oracle\r\n\r\n7) JHipster profiles: development, test, production\r\n* Introduction to profiles (currently inside \"Managing profiles\" page)\r\nimprovement: we should add a matrix to explain differences between various profiles\r\n\r\n8) JHipster in production\r\n* Best practices when using JHipster in production (currently \"Production/Using in production\")\r\n* Deploying to Cloud Foundry\r\n* Deploying to Heroku\r\n* Deploying to OpenShift\r\n* Deploying to AWS\r\n\r\n9) JHipster-UML\r\n\r\n10) Miscellaneous\r\n* Setting up continuous integration for your JHipster project (currently inside \"Test/Continuous integration\")\r\n* Tips 'n tricks from JHipster users\r\n \r\n11) Help and Bugs\r\n\r\n12) About"},"comment":{"url":"https://api.github.com/repos/jhipster/generator-jhipster/issues/comments/132336319","html_url":"https://github.com/jhipster/generator-jhipster/issues/1881#issuecomment-132336319","issue_url":"https://api.github.com/repos/jhipster/generator-jhipster/issues/1881","id":132336319,"user":{"login":"jdubois","id":316835,"avatar_url":"https://avatars.githubusercontent.com/u/316835?v=3","gravatar_id":"","url":"https://api.github.com/users/jdubois","html_url":"https://github.com/jdubois","followers_url":"https://api.github.com/users/jdubois/followers","following_url":"https://api.github.com/users/jdubois/following{/other_user}","gists_url":"https://api.github.com/users/jdubois/gists{/gist_id}","starred_url":"https://api.github.com/users/jdubois/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jdubois/subscriptions","organizations_url":"https://api.github.com/users/jdubois/orgs","repos_url":"https://api.github.com/users/jdubois/repos","events_url":"https://api.github.com/users/jdubois/events{/privacy}","received_events_url":"https://api.github.com/users/jdubois/received_events","type":"User","site_admin":false},"created_at":"2015-08-18T20:13:15Z","updated_at":"2015-08-18T20:13:15Z","body":"I would also like to:\r\n\r\n- rename all the pages with underscores to use a dash instead (\"create_a_new_app\" -> \"create-a-new-app\") as it's better for SEO. What's bad is that we will have tons of 404 errors (I tried to do a redirect rule with Jekyll but that failed!)\r\n- migrate everything from HTML to MarkDown (only reason we have HTML is that I didn't know we could use MarkDown in the first place!)\r\n- host everything to our own domain name (I still need to decide which one... BTW the jhipster.com domain is owned by our friend Matt Raible, and redirects to our github page). The main issue is that Github pages can't handle SSL on a custom domain, and that should be bad for SEO -> that means I should have a look at hosting this myself, but I'm so happy with the way Github pages work that this really annoys me."}}