Init migrating blog post

This commit is contained in:
Jeremy Thomas
2018-04-11 18:58:11 +01:00
parent 24878c09bc
commit 1074ea834b
11 changed files with 1063 additions and 2554 deletions

View File

@@ -1,7 +1,8 @@
---
layout: post
title: "Blog launched, new responsive columns, new helpers"
introduction: "First blog post on the newly launched blog! It even has its own [RSS feed](/atom.xml) for those who still use that. This blog will be more frequently updated than the [newsletter](#newsletter), so you can subscribe to either or both, as they will be used for different purposes."
introduction: "Stay updated with everything that's coming up with Bulma"
long_introduction: "First blog post on the newly launched blog! It even has its own [RSS feed](/atom.xml) for those who still use that. This blog will be more frequently updated than the [newsletter](#newsletter), so you can subscribe to either or both, as they will be used for different purposes."
color: "danger"
name: "Launch!"
icon: "rocket"

View File

@@ -1,7 +1,8 @@
---
layout: post
title: "Metro UI CSS grid with Bulma tiles"
introduction: "Have you ever wanted to build a **Metro-UI-like grid in CSS**?<br>Thanks to Flexbox and the new [Bulma tiles](https://bulma.io/documentation/layout/tiles/), you now can! And it only requires 1 HTML element: the `tile` element."
introduction: "Build a **Metro-UI-like grid in CSS** with the new `tile` element"
long_introduction: "Have you ever wanted to build a **Metro-UI-like grid in CSS**?<br>Thanks to Flexbox and the new [Bulma tiles](https://bulma.io/documentation/layout/tiles/), you now can! And it only requires 1 HTML element: the `tile` element."
color: "info"
name: "Metro UI"
icon: "th-large"

View File

@@ -2,7 +2,8 @@
layout: post
title: "New field element (for better controls)"
published: true
introduction: "<p>The <code>.control</code> element has been a very versatile container for form controls. But it came at a cost: it was difficult to combine its <strong>block</strong> characteristics with its <strong>inline</strong> variations.</p>"
introduction: "A new versatile container for form controls"
long_introduction: "<p>The <code>.control</code> element has been a very versatile container for form controls. But it came at a cost: it was difficult to combine its <strong>block</strong> characteristics with its <strong>inline</strong> variations.</p>"
color: "success"
name: "Field element"
icon: "square"

View File

@@ -1,7 +1,8 @@
---
layout: post
title: "Access previous Bulma versions"
introduction: "It is now possible to **access previous versions** of Bulma. Just head towards: [http://versions.bulma.io/](http://versions.bulma.io/)"
introduction: "It is now possible to **access previous versions** of Bulma"
long_introduction: "It is now possible to **access previous versions** of Bulma. Just head towards: [http://versions.bulma.io/](http://versions.bulma.io/)"
color: "primary"
name: "Versions"
icon: "undo"

View File

@@ -1,7 +1,8 @@
---
layout: post
title: "Bulma / Bootstrap comparison"
introduction: "If you're unsure _how_ or _why_ you should try out Bulma if you're familiar to Bootstrap, the new page [\"Alternative to Bootstrap\"](https://bulma.io/alternative-to-bootstrap/) tries to help you answer questions you might have."
introduction: "New page \"Alternative to Bootstrap\""
long_introduction: "If you're unsure _how_ or _why_ you should try out Bulma if you're familiar to Bootstrap, the new page [\"Alternative to Bootstrap\"](https://bulma.io/alternative-to-bootstrap/) tries to help you answer questions you might have."
color: "bootstrap"
name: "Bulma over Bootstrap?"
icon: "heart"

View File

@@ -0,0 +1,99 @@
---
title: "Migrating to v0.7.0"
layout: post
introduction: "What has changed"
color: "success"
name: "Migrating to v0.7.0"
icon: "sync-alt"
---
## Updated default values
{% for item in site.data.blog.migratingv070.updated %}
<table class="table is-bordered">
<tbody>
<tr>
<th class="is-light" colspan="3">
File
<code>{{ item.file }}</code>
</th>
</tr>
<tr>
<th>Variable</th>
<th>From</th>
<th>To</th>
</tr>
{% for change in item.changes %}
<tr>
<td>
<code>{{ change.variable }}</code>
</td>
<td>
<code>{{ change.from }}</code>
</td>
<td>
<code>{{ change.to }}</code>
</td>
</tr>
{% endfor %}
</tbody>
</table>
{% endfor %}
## New variables
{% for item in site.data.blog.migratingv070.new %}
<table class="table is-bordered">
<tbody>
<tr>
<th class="is-light" colspan="2">
File
<code>{{ item.file }}</code>
</th>
</tr>
<tr>
<th>Name</th>
<th>Value</th>
</tr>
{% for newcomer in item.newcomers %}
<tr>
<td>
<code>{{ newcomer.name }}</code>
</td>
<td>
<code>{{ newcomer.value }}</code>
</td>
</tr>
{% endfor %}
</tbody>
</table>
{% endfor %}
## Removed variables
<table class="table is-bordered">
<thead>
<tr>
<th>File</th>
<th>Removed</th>
<th>Replaced with</th>
</tr>
</thead>
<tbody>
{% for item in site.data.blog.migratingv070.removed %}
<tr>
<td>
<code>{{ item.file }}</code>
</td>
<td>
<code>{{ item.before }}</code>
</td>
<td>
{% for newcomer in item.after %}
<code>{{ newcomer }}</code>
{% endfor %}
</td>
</tr>
{% endfor %}
</tbody>
</table>