tfgrid/archive_www_docs_threefold_io
8
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
ThreeFold Docs Website - Moved here: https://github.com/threefoldfoundation/www_docs_threefold_io
138 Commits 2 Branches 0 Tags 30 MiB
TypeScript 54.4%
CSS 25.1%
Shell 20%
JavaScript 0.5%
main
Go to file
mik-tf 37ee4aea44 update description for website
2024-11-28 10:49:46 -05:00
docs_beta ... 2024-11-24 08:35:52 +03:00
docs_website update description for website 2024-11-28 10:49:46 -05:00
build_osx.sh Your commit message 2024-11-23 06:59:03 +03:00
build_ubuntu.sh Your commit message 2024-11-23 06:59:03 +03:00
build.sh set kristof, timur, mik and ourworld webserver in authorized keys, removed comments in index 2024-10-01 18:09:29 +00:00
develop_osx.sh ... 2024-11-24 08:35:52 +03:00
install_osx.sh Your commit message 2024-11-23 06:59:03 +03:00
install_ubuntu.sh Your commit message 2024-11-23 06:59:03 +03:00
install.sh add yarn installation to install script 2024-09-25 07:09:13 +00:00
LICENSE added LICENSE mit for threefold 2024 2024-08-25 15:25:27 -04:00
README.md Update README.md 2024-11-15 16:15:29 +00:00
run_osx.sh Your commit message 2024-11-23 06:59:03 +03:00

README.md

ThreeFold Docs Website

Table of Contents

Introduction

This repository contains the code to the ThreeFold Docs website.

URL

The website is hosted at docs.threefold.io.

Branches

  • development
    • code version of website
  • development_<suffix>
    • See Contribute section for details

Ops Scripts

To install the prerequisites to build the website, you can use the install.sh script.

To build the website, you can use the build.sh script.

Deploy and Test Locally

To deploy and test locally, refer to this documentation.

Contribute

To optimize updates to this repository, we propose a uniform way to collaborate.

Branches and Forks

To contribute to this repository, make a pull request of your changes. There are two main methods.

  1. Fork the repository and make a pull request with your changes
  2. If you have access, create a new branch in this repo and make a pull request with your changes

Overview

  • The production-ready content is published on the development branch
  • Any changes to development must go through a pull request (PR) and its associated review from a different branch with the prefix development_.
    • The name of the branch should indicate the work being done, e.g. working on the readme, development_readme_work

References

This website is written with Docusaurus.