This project ‘kirbytag-codepen’ is now hosted over on GitHub: https://github.com/plfstr/kirbytag-codepen
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<?php $thumb = thumb($cover, array('width' => 300)) ?> | |
<img src="<?php echo $thumb->url() ?>" width="<?php echo $thumb->width() ?>" width="<?php echo $thumb->height() ?>" alt=""> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// Reference: http://www.blackdogfoundry.com/blog/moving-repository-from-bitbucket-to-github/ | |
// See also: http://www.paulund.co.uk/change-url-of-git-repository | |
$ cd $HOME/Code/repo-directory | |
$ git remote rename origin bitbucket | |
$ git remote add origin https://github.com/mandiwise/awesome-new-repo.git | |
$ git push origin master | |
$ git remote rm bitbucket |
This is the follow up to a post I wrote recently called From Require.js to Webpack - Party 1 (the why) which was published in my personal blog.
In that post I talked about 3 main reasons for moving from require.js to webpack:
- Common JS support
- NPM support
- a healthy loader/plugin ecosystem.
Here I'll instead talk about some of the technical challenges that we faced during the migration. Despite the clear benefits in developer experience (DX) the setup was fairly difficult and I'd like to cover some of the challanges we faced to make the transition a bit easier.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<section class="section">This is a Test!</section> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[{"key":"320 x 480","name":"iPhone 3/4/S","width":320,"height":480}, | |
{"key":"320 x 568","name":"iPhone 5/C","width":320,"height":568}, | |
{"key":"375 x 667","name":"iPhone 6/S","width":375,"height":667}, | |
{"key":"414 x 736","name":"iPhone 6/S Plus","width":414,"height":736}, | |
{"key":"768 x 1024","name":"iPad1/2/3/4/Air","width":768,"height":1024}, | |
{"key":"1024 x 1366","name":"iPad Pro","width":1024,"height":1366}, | |
{"key":"320 x 533","name":"Samsung S/S2/S3mini","width":320,"height":533}, | |
{"key":"360 x 640","name":"Samsung S3/S4/S5/Note2/3/4","width":360,"height":640}, | |
{"key":"400 x 640","name":"Samsung Note","width":400,"height":640}, | |
{"key":"800 x 1280","name":"Samsung Galaxy Tab 8.9/10","width":800,"height":1280}, |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@mixin font-size($fs-map) { | |
@each $val in $fs-map { | |
$fs-breakpoint: nth($val, 1); | |
$fs-font-size: nth($val, 2); | |
$fs-font-color: nth($val, 3); | |
@if $fs-breakpoint == null { | |
font-size: $fs-font-size; | |
@include font-color($fs-font-color); | |
} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
$body-fontsize: ( | |
(null, 16px, #000000), | |
(800px, null, #81CFE0), | |
(1000px, 26px, #F9690E) | |
); | |
body { | |
@include font-size($body-fontsize); | |
} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<div class="foo"> | |
Lorem ipsum dolor sit amet <br /> | |
Lorem ipsum dolor sit amet | |
</div> | |
<div class="bar"> | |
Lorem ipsum dolor sit amet <br /> | |
Lorem ipsum dolor sit amet | |
</div> |
OlderNewer