mirror of https://github.com/bigchaindb/site.git
Reverting master to commit 014e45. (#307)
Signed-off-by: David Dashyan <mail@davie.li>
This commit is contained in:
David Dashyan
GitHub
parent
66453dedc8
commit
7c110417ae
|
|
@ -12,6 +12,8 @@ main:
|
|||
- title: Docs
|
||||
url: https://docs.bigchaindb.com/
|
||||
external: true
|
||||
- title: Services
|
||||
url: /services/
|
||||
|
||||
secondary:
|
||||
- title: About
|
||||
|
|
@ -24,6 +26,8 @@ secondary:
|
|||
url: "/contact/"
|
||||
|
||||
community:
|
||||
- title: Gitter
|
||||
url: https://gitter.im/bigchaindb/bigchaindb
|
||||
- title: GitHub
|
||||
url: https://github.com/bigchaindb
|
||||
- title: Twitter
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
<svg class="oceanprotocol__logo">
|
||||
<use xlink:href="/assets/img/sprite.svg#logo-oceanprotocol"></use>
|
||||
</svg>
|
||||
BigchainDB GmbH (the company) works on Ocean Protocol. IPDB Foundation (ipdb.io) oversees BigchainDB software and networks.</h1>
|
||||
Meet Ocean. A Decentralized Data Exchange Protocol</h1>
|
||||
</div>
|
||||
</a>
|
||||
|
||||
|
|
|
|||
|
|
@ -10,6 +10,39 @@
|
|||
</hgroup>
|
||||
</div>
|
||||
|
||||
<aside class="hero__community">
|
||||
<div class="row row--wide">
|
||||
<a class="btn btn-text btn-sm" id="release-link" href="{{ site.social.github.url }}/{{ site.social.github.repo }}/releases/latest" rel="external"><span class="hero__community__label">Latest release</span> <strong class="release" id="release"></strong></a>
|
||||
|
||||
<a class="social-link btn btn-text btn-sm js-social-link" href="{{ site.social.github.url }}/{{ site.social.github.repo }}" title="Star {{ site.social.github.org }}/{{ site.social.github.repo }} on GitHub">
|
||||
<svg class="icon icon--social icon--github" aria-labelledby="title">
|
||||
<title>GitHub</title>
|
||||
<use xlink:href="/assets/img/sprite.svg#github"></use>
|
||||
</svg> Star <span class="stars" id="stars"></span>
|
||||
</a>
|
||||
|
||||
<a class="social-link btn btn-text btn-sm js-social-link" href="{{ site.social.twitter.url }}" title="Follow on Twitter">
|
||||
<svg class="icon icon--social icon--twitter" aria-labelledby="title">
|
||||
<title>Twitter</title>
|
||||
<use xlink:href="/assets/img/sprite.svg#twitter"></use>
|
||||
</svg> Follow
|
||||
</a>
|
||||
|
||||
<a class="social-link btn btn-text btn-sm js-social-link" href="{{ site.social.gitter.url }}" title="Chat on Gitter">
|
||||
<svg class="icon icon--social icon--gitter" aria-labelledby="title">
|
||||
<title>Gitter</title>
|
||||
<use xlink:href="/assets/img/sprite.svg#gitter"></use>
|
||||
</svg> Chat
|
||||
</a>
|
||||
|
||||
<a class="social-link btn btn-text btn-sm js-social-link js-social-link--meetup" href="{{ site.social.meetup.url }}">
|
||||
<svg class="icon icon--social icon--meetup">
|
||||
<use xlink:href="/assets/img/sprite.svg#meetup"></use>
|
||||
</svg> <span class="meetup-title">BigchainDB Meetup</span>
|
||||
</a>
|
||||
</div>
|
||||
</aside>
|
||||
|
||||
<a class="hero__more btn btn-link btn-sm" href="#features" data-scroll>Learn More <svg class="icon icon--caret"><use xlink:href="/assets/img/sprite.svg#icon-caret"></use></svg></a>
|
||||
|
||||
</header>
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ partners:
|
|||
{% if page.partners.description %}
|
||||
{{ page.partners.description }}
|
||||
{% else %}
|
||||
Partnerships and collaborations have included
|
||||
We are proud to partner and collaborate with
|
||||
{% endif %}
|
||||
</p>
|
||||
</header>
|
||||
|
|
|
|||
|
|
@ -13,10 +13,10 @@
|
|||
</div>
|
||||
<![endif]-->
|
||||
|
||||
{% include banner.html %}
|
||||
|
||||
{{ content }}
|
||||
|
||||
{% include banner.html %}
|
||||
|
||||
{% include footer.html %}
|
||||
|
||||
{% include cookie-banner.html %}
|
||||
|
|
|
|||
|
|
@ -15,22 +15,16 @@ mediakit:
|
|||
link: /mediakit.zip
|
||||
|
||||
intro: >
|
||||
BigchainDB is a blockchain database offering decentralization, immutability and native assets. BigchainDB allows for the deployment of large-scale applications in a variety of use cases and industries from intellectual property and identity to supply chain, and Internet-of-Things.
|
||||
BigchainDB is a blockchain database offering decentralization, immutability and native assets. BigchainDB allows for the deployment of large-scale applications in a variety of use cases and industries from intellectual property and identity to supply chain, IoT and artificial intelligence. BigchainDB provides unique solutions for developers, start-ups and enterprises to successfully build their concepts, platforms and applications as big as they can dream.
|
||||
|
||||
---
|
||||
|
||||
## Our story
|
||||
|
||||
In summer 2013, we started working on a project that became [ascribe](www.ascribe.io). It started with problems in the art world: "how do you collect digital art?" and "how do digital artists get paid?". To address this, we wondered aloud: "what if you could own digital art the way you own Bitcoin?" We pulled on this thread further; the idea made sense. So we built early prototypes, raised money, hired a few early employees, and improved the product. We released in beta in 2014, and production in early 2015. We built on the Bitcoin blockchain. Alas, its scalability issues prevented us from serving larger customers.
|
||||
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 wouldn’t be able to handle the throughput we needed to serve larger enterprises.
|
||||
|
||||
We observed that MongoDB and other distributed databases (DBs) were powering webapps at internet scale. We asked: how do we “blockchain-ify” such a database? We saw that they'd need three new characteristics: decentralized, immutable, and the ability to "own" assets by holding the private key. So, we wrapped RethinkDB (and later MongoDB) with code to achieve the target characteristics. The result is BigchainDB software.
|
||||
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).
|
||||
|
||||
We started to build a prototype of BigchainDB in late summer 2015. It matured enough to open-source and announce BigchainDB in February 2016. What initially started as a “let’s solve our own problem” approach quickly turned into something much bigger than we expected. People and enterprises from across all industries reached out looking to build on the technology. It became clear that we were solving much more than our own problem.
|
||||
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 “let’s 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 blockchain database for the world.
|
||||
|
||||
We ran into another issue. Many people built prototypes on the technology, but there was no "live" network ready for them to use in production. Deploying their own became huge exercises and governance. So with others in the community, we initiated [IPDB Foundation](ipdb.io). Its mandate included running a live public BigchainDB network. We spent a lot of time designing governance.
|
||||
|
||||
By early 2017, we'd spent nearly four years thinking about IP and big data. We started to see problems at the intersection of these topics: how can you securely "own" data, and sell it while avoiding "data escapes"? Modern artificial intelligence (AI) was on the rise, and with it, the demand for way more data. We realized that blockchain technology could help, especially decentralized data marketplaces. With Toyota Research Institute, we [built](https://techcrunch.com/2017/05/22/toyota-pushes-into-blockchain-tech-to-enable-the-next-generation-of-cars) a prototype data marketplace that used BigchainDB.
|
||||
|
||||
This initial foray into decentralized data marketplaces grew into a much larger project: [Ocean Protocol](www.oceanprotocol.com). The team at BigchainDB GmbH (the company) is now focused on Ocean Protocol. [IPDB Foundation](ipdb.io) has [assumed governance](https://medium.com/ipdb-blog/ipdb-foundation-assumes-governance-of-bigchaindb-software-and-testnet-51235322e14c) of the BigchainDB software and networks.
|
||||
|
||||
"ascribe" is a registered trademark of BigchainDB.
|
||||
[ascribe](https://www.ascribe.io/) and [WhereOnTheNet](https://www.whereonthe.net/) are all registered trademarks of BigchainDB.
|
||||
|
|
|
|||
|
|
@ -1,14 +1,27 @@
|
|||
---
|
||||
layout: page
|
||||
|
||||
title: Contact BigchainDB GmbH
|
||||
title: Contact
|
||||
tagline: Get In Touch
|
||||
|
||||
js: page-contact.min.js
|
||||
---
|
||||
|
||||
<section class="section section-contactform">
|
||||
<div class="row row--wide">
|
||||
<div class="grid grid--full grid-medium--columns grid--gutters">
|
||||
<div class="grid__col grid__col--4">
|
||||
<p>Have a technical question? Head to
|
||||
<a href="{{ site.social.gitter.url }}">
|
||||
<svg class="icon icon--social icon--gitter">
|
||||
<use xlink:href="/assets/img/sprite.svg#gitter"></use>
|
||||
</svg> Gitter
|
||||
</a> to chat directly with our developers.
|
||||
</p>
|
||||
|
||||
{% include/form-contact.html %}
|
||||
</div>
|
||||
<div class="grid__col grid__col--2">
|
||||
<div class="h-card contactlist">
|
||||
<p><strong class="p-name p-org">{{ site.address.company }}</strong></p>
|
||||
|
||||
|
|
@ -20,6 +33,39 @@ js: page-contact.min.js
|
|||
|
||||
<p><a class="u-url" href="{{ site.url }}">{{ site.url | remove: 'https://' }}</a></p>
|
||||
<p><a class="u-email" href="mailto:{{ site.email.contact }}">{{ site.email.contact }}</a></p>
|
||||
</div>
|
||||
|
||||
|
||||
<div class="social">
|
||||
<p>
|
||||
<a href="https://github.com/{{ site.social.github.org }}">
|
||||
<svg class="icon icon--social icon--github" aria-labelledby="title">
|
||||
<title>GitHub</title>
|
||||
<use xlink:href="/assets/img/sprite.svg#github"></use>
|
||||
</svg>
|
||||
GitHub
|
||||
</a>
|
||||
</p>
|
||||
<p>
|
||||
<a href="{{ site.social.twitter.url }}">
|
||||
<svg class="icon icon--social icon--twitter" aria-labelledby="title">
|
||||
<title>Twitter</title>
|
||||
<use xlink:href="/assets/img/sprite.svg#twitter"></use>
|
||||
</svg>
|
||||
Twitter
|
||||
</a>
|
||||
</p>
|
||||
<p>
|
||||
<a href="{{ site.social.medium.url }}">
|
||||
<svg class="icon icon--social icon--blog" aria-labelledby="title">
|
||||
<title>Blog</title>
|
||||
<use xlink:href="/assets/img/sprite.svg#medium"></use>
|
||||
</svg>
|
||||
Blog
|
||||
</a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -20,9 +20,11 @@ features:
|
|||
- title: "Byzantine Fault Tolerant (BFT)"
|
||||
text: "Up to one third of the nodes in the network can be experiencing arbitrary faults and the rest of the network will still come to consensus on the next block."
|
||||
icon: "icon-network"
|
||||
new: true
|
||||
- title: "Low Latency"
|
||||
text: "A global network takes about a second to come to consensus on a new block. In other words, transaction finality happens fast."
|
||||
icon: "icon-hourglass"
|
||||
new: true
|
||||
- title: "Customizable"
|
||||
text: "Design your own private network with custom assets, transactions, permissions and transparency."
|
||||
icon: "icon-settings"
|
||||
|
|
@ -65,6 +67,10 @@ js: page-features.min.js
|
|||
{% endfor %}
|
||||
|
||||
</div>
|
||||
|
||||
<p class="text-center features-roadmap" >
|
||||
<a href="https://github.com/bigchaindb/org/blob/master/ROADMAP.md" class="btn btn-primary">Our Roadmap</a>
|
||||
</p>
|
||||
</div>
|
||||
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -65,3 +65,8 @@ intro:
|
|||
|
||||
{% include sections/section-partners.html %}
|
||||
|
||||
{% include sections/section-cta-services.html %}
|
||||
|
||||
{% include sections/section-blog.html %}
|
||||
|
||||
{% include sections/section-newsletter.html %}
|
||||
|
|
|
|||
|
|
@ -2,18 +2,80 @@
|
|||
layout: base
|
||||
|
||||
title: Services
|
||||
description: "Support for BigchainDB Software"
|
||||
description: "Hands-on consulting and production support by blockchain experts"
|
||||
|
||||
header: hero-services.jpg
|
||||
image: share-image-services.jpg
|
||||
js: page-services.min.js
|
||||
|
||||
hero:
|
||||
title: "Support for BigchainDB software"
|
||||
description: "To learn about service providers for BigchainDB software, please contact IPDB Foundation."
|
||||
title: "Hands-on consulting and production support"
|
||||
description: "From ideation to production, we have the team and technology to help you build enterprise-grade applications and platforms."
|
||||
cta:
|
||||
- name: IPDB Homepage
|
||||
link: "https://www.ipdb.io"
|
||||
- name: Get in touch
|
||||
link: "#contact"
|
||||
scroll: true
|
||||
|
||||
support:
|
||||
features:
|
||||
- title: "Ideation"
|
||||
description: "Have some ideas but don’t know where to start? We run a workshop to help you better understand blockchain technologies and let you drill-down into the right use cases that bring the biggest benefit."
|
||||
icon: icon-education
|
||||
- title: "Use case development"
|
||||
description: "You have a specific idea for a blockchain application? We help you build a detailed business and technical architecture that lets you move forward with confidence."
|
||||
icon: icon-blueprint
|
||||
- title: "Blockchain consulting"
|
||||
description: "The idea is clear. Now you need help to build a prototype. Our blockchain consultants can work to your needs, budget and timeline to get a demo into your hands that will impress."
|
||||
icon: icon-engineering
|
||||
|
||||
partners:
|
||||
title: "Trusted by leading global companies"
|
||||
description: "We work with partners who are deploying data-centric blockchain applications for automotive, energy, identity, IoT, intellectual property and supply chain use cases."
|
||||
|
||||
intro:
|
||||
title: "Designed for data-centric, high-transaction use cases."
|
||||
description: "Whether you’re a system architect, a developer or a database specialist, BigchainDB offers the performance and tooling to help you create the future."
|
||||
title2: "Decentralized, secure and immutable."
|
||||
text: "Traditional blockchains lack what most enterprises require. BigchainDB takes a different approach, one that starts with a big data distributed database and then adds blockchain characteristics. The result is high throughput and low latency, making data-centric and high volume use cases a breeze."
|
||||
text2: "Only BigchainDB combines the all-important advantages of queryability and performance of traditional databases with the distributed, secure and immutable nature of blockchain technology into one package."
|
||||
features:
|
||||
- title: "Easy to build with"
|
||||
description: "Build applications that speak directly to BigchainDB using our set of drivers and APIs. A powerfully simple and quick way to prototype."
|
||||
icon: icon-wrench
|
||||
- title: "Interoperability by design"
|
||||
description: "Interoperability with Ethereum, IPFS, Bitcoin and other protocols such as the Interledger Protocol (ILP), IPLD, COALA IP and COALA SC mean that enterprises can develop their applications knowing that their work is future-proofed."
|
||||
icon: icon-plug
|
||||
|
||||
contact:
|
||||
title: "Get in touch"
|
||||
description: "Ready to start building with BigchainDB? Enter your details below and we'll be in touch right away."
|
||||
|
||||
interests:
|
||||
- Training
|
||||
- Partnership
|
||||
- Proof-of-concept / prototype / pilot
|
||||
- Production support
|
||||
- Other
|
||||
|
||||
industries:
|
||||
- Analytics
|
||||
- Automotive
|
||||
- Consulting
|
||||
- Data Exchange
|
||||
- Energy
|
||||
- Finance
|
||||
- Government
|
||||
- Health Care
|
||||
- Identity
|
||||
- Insurance
|
||||
- Law
|
||||
- Manufacturing
|
||||
- Media
|
||||
- Security
|
||||
- Supply Chain
|
||||
- Technology
|
||||
- Other
|
||||
|
||||
---
|
||||
|
||||
<header class="hero hero--services" {% if page.header %}style="background-image:url('/assets/img/{{ page.header }}')"{% endif %}>
|
||||
|
|
@ -29,9 +91,98 @@ hero:
|
|||
<h2 class="hero__subtitle">{{ page.hero.description }}</h2>
|
||||
|
||||
{% for cta in page.hero.cta %}
|
||||
<a class="btn btn-blue-light hero__action" href="{{ cta.link }}">{{ cta.name }}</a>
|
||||
<a class="btn btn-blue-light hero__action" href="{{ cta.link }}" {% if cta.scroll %}data-scroll{% endif %}>{{ cta.name }}</a>
|
||||
{% endfor %}
|
||||
</hgroup>
|
||||
</div>
|
||||
|
||||
</header>
|
||||
|
||||
<section class="section section--servicesdetail background--blue--light">
|
||||
<div class="row row--wide">
|
||||
|
||||
<div class="grid grid--full grid-small--third grid--gutters">
|
||||
{% for feature in page.support.features %}
|
||||
<div class="grid__col">
|
||||
<div class="feature">
|
||||
<svg class="feature__icon icon">
|
||||
<use xlink:href="/assets/img/sprite.svg#{{ feature.icon }}"></use>
|
||||
</svg>
|
||||
<div class="feature__detail">
|
||||
<h1 class="feature__title">{{ feature.title }}</h1>
|
||||
<p class="feature__text">{{ feature.description }}</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
{% endfor %}
|
||||
</div>
|
||||
|
||||
<div class="actions">
|
||||
<a class="btn btn-blue" data-scroll href="#contact">Get in touch</a>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</section>
|
||||
|
||||
{% include sections/section-partners.html %}
|
||||
|
||||
<section class="section section--servicesintro background--darker">
|
||||
<div class="row">
|
||||
<header class="section-header text-left">
|
||||
<h1 class="section-title">{{ page.intro.title }}</h1>
|
||||
<p class="section-description">{{ page.intro.description }}</p>
|
||||
|
||||
<h2>{{ page.intro.title2 }}</h2>
|
||||
|
||||
<p>{{ page.intro.text }}</p>
|
||||
|
||||
<p>{{ page.intro.text2 }}</p>
|
||||
</header>
|
||||
|
||||
<div class="grid grid--full grid-small--half grid--gutters">
|
||||
{% for feature in page.intro.features %}
|
||||
<div class="grid__col">
|
||||
<div class="feature">
|
||||
<svg class="feature__icon icon">
|
||||
<use xlink:href="/assets/img/sprite.svg#{{ feature.icon }}"></use>
|
||||
</svg>
|
||||
<div class="feature__detail">
|
||||
<h1 class="feature__title">{{ feature.title }}</h1>
|
||||
<p class="feature__text">{{ feature.description }}</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
{% endfor %}
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<section class="section section--servicestestimonial">
|
||||
<div class="row">
|
||||
|
||||
<figure class="testimonial">
|
||||
<blockquote class="testimonial__quote">{{ site.data.testimonials.set4[0].quote }}</blockquote>
|
||||
|
||||
<figcaption class="testimonial__caption">
|
||||
<img class="testimonial__avatar" src="/assets/img/{{ site.data.testimonials.set4[0].image }}">
|
||||
<cite class="testimonial__cite">
|
||||
<span class="testimonial__name">{{ site.data.testimonials.set4[0].name }}</span>
|
||||
<span class="testimonial__org">{{ site.data.testimonials.set4[0].org }}</span>
|
||||
</cite>
|
||||
</figcaption>
|
||||
</figure>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<section class="section section--servicescontact background--blue" id="contact">
|
||||
<div class="row">
|
||||
<header class="section-header">
|
||||
<h1 class="section-title">{{ page.contact.title }}</h1>
|
||||
<p class="section-description">{{ page.contact.description }}</p>
|
||||
</header>
|
||||
|
||||
{% include form-services.html %}
|
||||
|
||||
</div>
|
||||
</section>
|
||||
|
|
|
|||
Loading…
Reference in New Issue