{"action":"created","issue":{"url":"https://api.github.com/repos/almasaeed2010/AdminLTE/issues/710","labels_url":"https://api.github.com/repos/almasaeed2010/AdminLTE/issues/710/labels{/name}","comments_url":"https://api.github.com/repos/almasaeed2010/AdminLTE/issues/710/comments","events_url":"https://api.github.com/repos/almasaeed2010/AdminLTE/issues/710/events","html_url":"https://github.com/almasaeed2010/AdminLTE/issues/710","id":108551724,"number":710,"title":"AdminLTE 3.0 Plans","user":{"login":"almasaeed2010","id":1512664,"avatar_url":"https://avatars.githubusercontent.com/u/1512664?v=3","gravatar_id":"","url":"https://api.github.com/users/almasaeed2010","html_url":"https://github.com/almasaeed2010","followers_url":"https://api.github.com/users/almasaeed2010/followers","following_url":"https://api.github.com/users/almasaeed2010/following{/other_user}","gists_url":"https://api.github.com/users/almasaeed2010/gists{/gist_id}","starred_url":"https://api.github.com/users/almasaeed2010/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/almasaeed2010/subscriptions","organizations_url":"https://api.github.com/users/almasaeed2010/orgs","repos_url":"https://api.github.com/users/almasaeed2010/repos","events_url":"https://api.github.com/users/almasaeed2010/events{/privacy}","received_events_url":"https://api.github.com/users/almasaeed2010/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/almasaeed2010/AdminLTE/labels/News","name":"News","color":"009800"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":33,"created_at":"2015-09-27T18:16:35Z","updated_at":"2015-10-17T08:47:52Z","closed_at":null,"body":"Hello everyone,\r\n\r\nAs you may already know, Bootstrap v4 is coming soon. Thus, a major update for AdminLTE is due with the release of BS4. For the time being, we will only take suggestions for AdminLTE 3. In other words, v2 will get bug fixes and patches but won't get new features.\r\n\r\n**Quick glance at our plans for AdminLTE 3:**\r\n- Full utilization of Bower for package management\r\n- SASS instead of LESS\r\n- Customized Bootstrap via variables to significantly decrease the number of (override) lines of code in AdminLTE.css\r\n-  Front-end template using the easily customizable color-scheme of AdminLTE to create a sense of consistency and broaden AdminLTE's domain\r\n- Color variables of AdminLTE will be removed and Bootstrap 4 color vars will replace them\r\n  * That is to say, instead of @light-blue for example, we will use $brand-primary\r\n- The box component will be replaced with the new BS4 cards\r\n- The main header will use a custom navbar to avoid current issues with responsiveness\r\n- The treeview in the sidebar will be rewritten to provide advanced features and options such as treeview search and expand only when a specific element gets clicked.\r\n- App.js will be removed and ECMA6 will be used for each plugin to produce AdminLTE.js\r\n  * Treeview.js for example will be its own plugin and app.js will only supply a demo use case\r\n  * This gives developers the ability to create their own custom app.js and use only the relevant plugins\r\n- I still prefer Grunt over Gulp so I will keep using it (this is debatable)\r\n- The layout may make use of the new flexbox functionality that BS4 provides. Thus, reducing the number of calls to ```$(window).resize(...)```\r\n\r\nThe product of these changes should make AdminLTE highly customizable and convert it into a framework level tool rather than just a template. Suggestions and contributions are highly recommended as always. If you know of new plugins, tools or ideas, please feel free to post them here."},"comment":{"url":"https://api.github.com/repos/almasaeed2010/AdminLTE/issues/comments/148896246","html_url":"https://github.com/almasaeed2010/AdminLTE/issues/710#issuecomment-148896246","issue_url":"https://api.github.com/repos/almasaeed2010/AdminLTE/issues/710","id":148896246,"user":{"login":"YasserHassan","id":9349772,"avatar_url":"https://avatars.githubusercontent.com/u/9349772?v=3","gravatar_id":"","url":"https://api.github.com/users/YasserHassan","html_url":"https://github.com/YasserHassan","followers_url":"https://api.github.com/users/YasserHassan/followers","following_url":"https://api.github.com/users/YasserHassan/following{/other_user}","gists_url":"https://api.github.com/users/YasserHassan/gists{/gist_id}","starred_url":"https://api.github.com/users/YasserHassan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/YasserHassan/subscriptions","organizations_url":"https://api.github.com/users/YasserHassan/orgs","repos_url":"https://api.github.com/users/YasserHassan/repos","events_url":"https://api.github.com/users/YasserHassan/events{/privacy}","received_events_url":"https://api.github.com/users/YasserHassan/received_events","type":"User","site_admin":false},"created_at":"2015-10-17T08:47:52Z","updated_at":"2015-10-17T08:47:52Z","body":"@ManuelRauber the sidebar state server-side part is required for the initial page load. For example, if you collapse the sidebar after page load, it will show expanded first then animate to collapse with every page load. You need to set the state (class) to the correct status before sending the page to the server to show right initially. The client-side function should be capturing user's expand/collapse action and setting cookie only. Refer to #315 for this.\r\n\r\nConsidering the above, in my opinion, local storage is not the right way to do it unless you need to do extra work to sent its value with each request to the server (in turn could be stored in a session), something a cookie would do directly and implicitly."}}