Official website for libp2p https://libp2p.io

This repository contains the source code for the libp2p website available at https://libp2p.io

This project builds out a static site to explain libp2p, ready for deployment on ipfs. It uses hugo to glue the html together. It provides an informative, public-facing website. The most important things are the words, concepts and links it presents.

Much of the site content is data-driven, take a look at the data dir where find the data behind the implementations information as json.

git clone https://github.com/libp2p/website

To deploy the site libp2p.io, run:

# Build out the optimised site to ./public, where you can check it locally.
make
# Add the site to your local ipfs, you can check it via /ipfs/<hash>
make deploy
# Save your dnsimple api token as auth.token
cat "<api token here>" > auth.token
# Update the dns record for libp2p to point to the new ipfs hash.
make publish-to-domain

The following commands are available:

Build the optimised site to the ./public dir

Preview the production ready site at https://localhost:1313 (requires hugo on your PATH)

Start a hot-reloading dev server on https://localhost:1313 (requires hugo on your PATH)

Optimise all the things!

Build the site in the public dir and add to ipfs (requires hugo & ipfs on your PATH)

See the Makefile for the full list or run make help in the project root. You can pass the env var DEBUG=true to increase the verbosity of your chosen command.

• Node.js and npm for build tools
• ipfs to deploy changes
• jq, curl and an auth.token file in the project root containing your dnsimple api token to update the dns.

All other dependencies are pulled from npm and the Makefile will run npm install for you because it's nice like that.

Please do! Check out the issues, or open a PR!

Check out our notes on contributing for more information on how we work, and about contributing in general. Please be aware that all interactions related to libp2p are subject to the IPFS Code of Conduct.

Small note: If editing the README, please conform to the standard-readme specification.