[GitHub] sling pull request #233: SLING-6850 Launchpad Homepage update for Sling 9
Github user auniverseaway closed the pull request at: https://github.com/apache/sling/pull/233 ---
[GitHub] sling pull request #233: Launchpad Homepage update for Sling 9
GitHub user auniverseaway opened a pull request: https://github.com/apache/sling/pull/233 Launchpad Homepage update for Sling 9 This PR is to address [SLING-6850](https://issues.apache.org/jira/browse/SLING-6850) The new launchpad homepage is completely redesigned for better information architecture while retaining the spirit of the original. The new homepage is responsive, and leverages flexbox to vertically center the content when the viewport is beyond a certain size. To address front-end productivity, I have added a launchpad clientlib which uses SCSS to generate the minified CSS. To not be heavy handed with an FE build process, I have ***not*** added the [frontend-maven-plugin](https://github.com/eirslett/frontend-maven-plugin), so overall build time should not be affected. The idea is that the CSS is the CSS, and if you want to change it, you can run `npm install` and `gulp` manually. Let me know if you want any changes @rombert.  You can merge this pull request into a Git repository by running: $ git pull https://github.com/auniverseaway/sling SLING-6850_Launchpad_Homepage Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/233.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #233 commit c3742b5a2a7671475b76e881ac5a4fe731362f0e Author: Chris Millar Date: 2017-05-18T21:40:09Z Launchpad Homepage update for Sling 9 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request #214: SLING-2696 - Update Logo
GitHub user auniverseaway opened a pull request: https://github.com/apache/sling/pull/214 SLING-2696 - Update Logo This is to address [SLING-2696](https://issues.apache.org/jira/browse/SLING-2696). I did not modify any samples. Only the logo for launchpad/content and the webconsolebranding bundle. I removed the old PNGs and put the new ones in retaining the same height. You can merge this pull request into a Git repository by running: $ git pull https://github.com/auniverseaway/sling SLING-2696_Update_Logo Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/214.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #214 commit 8647b878182272a990403c981283eaefcf81d5d0 Author: Chris Millar Date: 2017-04-14T19:47:47Z SLING-2696 - Update Logo --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request #210: Sling 6740 HTL Blog sample
GitHub user auniverseaway opened a pull request: https://github.com/apache/sling/pull/210 Sling 6740 HTL Blog sample This is the HTL blog sample I mentioned in [SLING-6740](https://issues.apache.org/jira/browse/SLING-6740). It's basic by design. In some scenarios it's less DRY to allow for easier understanding for a beginner. The README will have all the details to get a beginner started. If there's any formatting or syntax constraints I missed, please let me know. If there's anything I should change to match the Sling project, let me know. Of course, any general tips are also appreciated. Thanks! Chris  You can merge this pull request into a Git repository by running: $ git pull https://github.com/auniverseaway/sling SLING-6740_HTLBlog_Sample Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/210.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #210 commit 446220f3c0249dccee5af7eecc2b79a354b5ef65 Author: Chris Millar Date: 2017-03-28T18:40:25Z Initial commit of HTL Blog Sample commit bda763d31d200968fd085706c596d3b069a7b3c0 Author: Chris Millar Date: 2017-03-29T15:29:24Z Working blog. Needs a bit of polish. commit 660cceec8707842b949813a93625dcaa110d19ff Author: Chris Millar Date: 2017-03-31T15:22:29Z Adding created time. More polish and clean up. commit d8ab3a2948ddc41d272d3769cdc4725d9bb7e2d1 Author: Chris Millar Date: 2017-04-01T17:19:52Z More polish. Added readme. commit 76a48b3490bd316709f355b244cf38b1aa4b9bba Author: Chris Millar Date: 2017-04-01T17:22:50Z Update readme.md commit 8d00937ea8a0d952df3ecf4732b349f26a514f85 Author: Chris Millar Date: 2017-04-01T17:33:56Z Adding comments to Edit model commit 314c851c0e82d4ce502d26fda36319d280078437 Author: Chris Millar Date: 2017-04-01T19:24:49Z More comments. commit 4809bb81ea88d2eca3857cf18681d19c8fb87db2 Author: Chris Millar Date: 2017-04-01T19:31:14Z More formatting cleanup in prep for PR commit 127ac6ebff1ef9bae3d1fbdd17e612c4f40676cb Author: Chris Millar Date: 2017-04-01T19:45:23Z Comments and a screenshot --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
