1
0
mirror of https://github.com/bigchaindb/site.git synced 2024-12-24 02:16:10 +01:00

integrate brand assets & media kit download into about page

This commit is contained in:
Matthias Kretschmann 2017-08-22 12:58:59 +02:00
parent b5463b0d3f
commit a14222eb01
Signed by: m
GPG Key ID: 606EEEF3C479A91F
11 changed files with 179 additions and 45 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 32 KiB

File diff suppressed because one or more lines are too long

After

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 39 KiB

File diff suppressed because one or more lines are too long

After

Width:  |  Height:  |  Size: 11 KiB

File diff suppressed because one or more lines are too long

Before

Width:  |  Height:  |  Size: 4.2 KiB

After

Width:  |  Height:  |  Size: 11 KiB

View File

@ -1,3 +1,56 @@
.section--team {
padding-top: 0;
}
.section--about {
h2:first-of-type {
margin-top: 0;
}
}
.widget {
margin-top: $spacer * 4;
@media ($screen-sm) {
padding-left: $spacer * 2;
&:first-child {
margin-top: $spacer * 2.5;
}
}
}
.widget__title {
font-size: $font-size-h4;
margin-bottom: $spacer / 2;
margin-top: 0;
}
.brand {
margin-top: $spacer;
&:last-child {
margin-top: $spacer * 2;
}
}
.brand__logo {
padding: $spacer * 2;
border: 1px solid $gray-dark;
display: flex;
align-items: center;
justify-content: center;
.brand--dark & {
background: rgba($gray-light, .75);
}
}
.brand__logo__download {
text-align: center;
a {
font-size: $font-size-sm;
margin-left: $spacer;
}
}

View File

@ -140,6 +140,9 @@
&.grid__col--4 { flex: 0 0 75%; }
&.grid__col--5 { flex: 0 0 84%; }
&.grid__col--6 { flex: 0 0 100%; }
&.grid__col--2-3 { flex: 0 0 (100% / 1.5); }
&.grid__col--1-3 { flex: 0 0 (100% / 3); }
}
}

83
_src/_layouts/about.html Normal file
View File

@ -0,0 +1,83 @@
---
layout: base
---
<header role="banner" class="header" {% if page.image %}style="background-image:url('/assets/img/{{ page.image }}')"{% endif %}>
{% include menu-main.html %}
<div class="row">
<div class="header__content">
<h1 class="header__title">{{ page.title }}</h1>
</div>
</div>
</header>
<section role="main" class="content content--page">
<section class="section section--about">
<div class="row row--wide">
<div class="grid grid--full grid-medium--columns grid--gutters">
<div class="grid__col grid__col--2-3">
{{ content }}
</div>
<div class="grid__col grid__col--1-3">
<aside class="widget widget--logo">
<h2 class="widget__title">{{ page.brand.title }}</h2>
<p>{{ page.brand.description }}</p>
<div class="brand brand--dark">
<figure class="brand__logo">
<svg class="logo logo--sm logo--color" aria-labelledby="title">
<title>Logo BigchainDB</title>
<use xlink:href="/assets/img/sprite.svg#logo"></use>
</svg>
</figure>
<p class="brand__logo__download">
<a href="/assets/brand/logo-bigchaindb.svg" download>SVG</a>
<a href="/assets/brand/logo-bigchaindb.png" download>PNG</a>
</p>
</div>
<div class="brand brand--light">
<figure class="brand__logo">
<svg class="logo logo--sm logo--white--green" aria-labelledby="title">
<title>Logo BigchainDB</title>
<use xlink:href="/assets/img/sprite.svg#logo"></use>
</svg>
</figure>
<p class="brand__logo__download">
<a href="/assets/brand/logo-bigchaindb-white.svg" download>SVG</a>
<a href="/assets/brand/logo-bigchaindb-white.png" download>PNG</a>
</p>
</div>
</aside>
<aside class="widget widget--mediakit">
<h2 class="widget__title">{{ page.mediakit.title }}</h2>
<p>{{ page.mediakit.description }}</p>
<a href="{{ page.mediakit.link }}">{{ page.mediakit.download }}</a>
</aside>
</div>
</div>
</div>
</section>
<section class="section section--team">
<div class="row row--wide">
<h1 class="section-title">Team</h1>
{% include founders.html %}
{% include team.html %}
</div>
</section>
</section>

View File

@ -31,18 +31,6 @@ layout: base
</section>
{% if page.path contains "about" %}
<section class="section section--team section--founders">
<div class="row row--wide">
<h1 class="section-title">Team</h1>
{% include founders.html %}
{% include team.html %}
</div>
</section>
{% endif %}
{% if page.title == "Whitepaper" %}
<section class="section section-whitepaper-download background--photo">
<div class="row">

View File

@ -1,16 +1,28 @@
---
title: 'About BigchainDB'
layout: page
layout: about
js: page-about.min.js
ipdb: true
ipdb: true
brand:
title: Brand Assets
description: You don't have to use Google to get our logo.
mediakit:
title: Media Kit
description: Get our full media kit in one handy package.
download: Download media kit (zip)
link: /assets/brand/mediakit-bigchaindb.zip
---
## Our story
In the summer of 2013, we started working on a project that became ascribe, blockchain-based intellectual property (IP) attribution. We asked the question: how can creators of any digital IP get compensated? Why not own digital art the way you own Bitcoin? With a public store of attribution and provenance, blockchain technology could solve this. So we raised some money, hired a few early employees and kept working on the product until we were satisfied enough to release it, built on the Bitcoin blockchain. The product was basically in shape to serve larger-scale customers, with the glaring exception of the blockchain scalability. We found ourselves needing to turn down opportunities knowing that the Bitcoin blockchain wouldnt be able to handle the throughput we needed to serve larger enterprises.
With this as a starting point, we asked how do we “blockchain-ify” it? We drew on our experience in shipping blockchain products to define three specific characteristics: decentralized, immutable and the ability to register and transfer assets. With the definitions above as a starting point, we chose an enterprise-class distributed database and then built our own technology on top of that, adding those three key characteristics while improving base functionality, fault tolerance much more. See our roadmap <a href="https://github.com/bigchaindb/org/blob/master/ROADMAP.md">here</a>.
With this as a starting point, we asked how do we “blockchain-ify” it? We drew on our experience in shipping blockchain products to define three specific characteristics: decentralized, immutable and the ability to register and transfer assets. With the definitions above as a starting point, we chose an enterprise-class distributed database and then built our own technology on top of that, adding those three key characteristics while improving base functionality, fault tolerance much more. See our [roadmap](https://github.com/bigchaindb/org/blob/master/ROADMAP.md).
From the seed of the idea, to intense efforts starting late summer 2015, we made the announcement in February 2016. What initially started as a “lets solve our own problem” approach almost immediately turned into something much bigger than we expected. With people and enterprises from across all industries reaching out looking to partner, collaborate, license or build on the technology, it became clear that we were solving much more than our own problem. The result is BigchainDB, a scalable blockchain database for the world.
<a href="https://www.ascribe.io/">ascribe</a>, <a href="https://www.whereonthe.net/">WhereOnTheNet</a> and <a href="https://ipdb.foundation/">IPDB</a> are all registered trademarks of BigchainDB.
[ascribe](https://www.ascribe.io/), [WhereOnTheNet](https://www.whereonthe.net/) and [IPDB](https://ipdb.io/) are all registered trademarks of BigchainDB.

View File

@ -239,6 +239,13 @@ export const fonts = () => src(SRC + '_assets/fonts/**/*')
.pipe(dest(DIST + 'assets/fonts/'))
//
// Copy brand assets
//
export const brand = () => src(SRC + '_assets/brand/**/*')
.pipe(dest(DIST + 'assets/brand/'))
//
// Revision static assets
//
@ -335,7 +342,7 @@ const deployBanner = (done) => {
// `gulp build` is the development build
// `gulp build --production` is the production build
//
export const build = series(buildBanner, clean, jekyll, parallel(html, css, js, images, fonts, svg), rev, revReplace, criticalCss)
export const build = series(buildBanner, clean, jekyll, parallel(html, css, js, images, fonts, svg, brand), rev, revReplace, criticalCss)
//
// Build site, run server, and watch for file changes