set up homepage template

.github/dependabot.yml

@@ -0,0 +1,8 @@
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "daily"
+    allow:
+      - dependency-name: "@acid-info/logos-docusaurus-preset"

.gitignore

@@ -0,0 +1,26 @@
+# Dependencies
+/node_modules
+
+# Production
+/build
+
+# Generated files
+.docusaurus
+.cache-loader
+
+# Misc
+.DS_Store
+.env
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+.yalc
+yalc.lock
+.idea
+
+static/search-index.json

.husky/commit-msg

@@ -0,0 +1,2 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"

.husky/pre-commit

@@ -0,0 +1,5 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+# yarn prettier:staged
+# yarn typecheck

.prettierignore

@@ -0,0 +1,2 @@
+*.mdx
+*.md

.prettierrc

@@ -0,0 +1,6 @@
+{
+  "tabWidth": 2,
+  "semi": false,
+  "singleQuote": true,
+  "trailingComma": "all"
+}

Jenkinsfile

@@ -0,0 +1,61 @@
+pipeline {
+  agent { label 'linux' }
+
+  options {
+    disableConcurrentBuilds()
+    /* manage how many builds we keep */
+    buildDiscarder(logRotator(
+      numToKeepStr: '20',
+      daysToKeepStr: '30',
+    ))
+  }
+
+  environment {
+    GIT_COMMITTER_NAME = 'status-im-auto'
+    GIT_COMMITTER_EMAIL = 'auto@status.im'
+    PROD_SITE = 'nomos.tech'
+    DEV_SITE  = 'dev.nomos.tech'
+    DEV_HOST  = 'jenkins@node-01.do-ams3.sites.misc.statusim.net'
+    SCP_OPTS  = 'StrictHostKeyChecking=no'
+  }
+
+  stages {
+    stage('Install') {
+      steps {
+        sh "yarn install"
+      }
+    }
+
+    stage('Build') {
+      steps {
+        sh 'yarn build'
+        sh "echo ${env.PROD_SITE} > build/CNAME"
+      }
+    }
+
+    stage('Publish Prod') {
+      when { expression { env.GIT_BRANCH ==~ /.*master/ } }
+      steps {
+        sshagent(credentials: ['status-im-auto-ssh']) {
+          sh "ghp-import -p build"
+        }
+      }
+    }
+
+    stage('Publish Devel') {
+      when { expression { !(env.GIT_BRANCH ==~ /.*master/) } }
+      steps {
+        sshagent(credentials: ['jenkins-ssh']) {
+          sh """
+            rsync -e 'ssh -o ${SCP_OPTS}' -r --delete build/. \
+              ${env.DEV_HOST}:/var/www/${env.DEV_SITE}/
+          """
+        }
+      }
+    }
+  }
+
+  post {
+    cleanup { cleanWs() }
+  }
+}

README.md

@@ -0,0 +1,93 @@
+# Logos Homepage Template
+
+The template repository for homepage using [logos-docusaurus-plugins](https://github.com/acid-info/logos-docusaurus-plugins).
+
+
+## Use cases
+- [nomos.tech](https://nomos.tech/)
+- [waku.org](https://waku.org/)
+- [nomos.tech](https://nomos.tech/)
+- [codex.storage](https://codex.storage/)
+
+
+## How to Run Locally
+
+1. Clone this repository
+```bash
+$ git clone https://github.com/acid-info/logos-homepage-template.git
+```
+
+2. Install the dependencies:
+```bash
+$ yarn install
+```
+
+3. Start the website:
+```bash
+$ yarn start
+```
+
+4. Visit `http://localhost:3000` in your browser
+
+
+## Configuration
+Edit the `docusaurus.config.js` file in the repository's root directory, and update the value of the `businessUnit` field in presets section; below is a list of valid values:
+- Logos
+- Codex
+- Waku
+- Nimbus
+- Nomos
+- VacResearch
+- Acid.info
+
+Example:
+```js
+presets: [
+  [
+    '@acid-info/logos-docusaurus-preset',
+    {
+      businessUnit: 'Codex',
+    },
+  ],
+],
+```
+
+This is typically sufficient for most cases, as the Logos plugins will automatically populate other configurations related to the specified business unit. If you encounter any errors in the information provided by Logos Plugins, please visit the [Logos Docusaurus Plugins](https://github.com/acid-info/logos-docusaurus-plugins) repository and open an issue.
+
+
+## Landing page
+
+The code for a landing page is located in `src/pages/index.mdx`. This file employs the `mdx` format and utilizes React components from the [Logos Docusaurus Plugins](https://github.com/acid-info/logos-docusaurus-plugins/tree/main/packages/logos-docusaurus-theme/src/client/components/mdx) package.
+
+
+## Adding subpages
+
+To include subpages (e.g., https://nomos.tech/about/architect), create a `.md` or `mdx` file within the `about` directory. You can use [Frontmatter](https://docusaurus.io/docs/markdown-features#front-matter) to add metadata to your markdown file.
+
+The content in `about/index.md` will be utilized as the index page for the `/about` section.
+
+
+## Root pages
+
+Subpages that do not belong to the `About` page (e.g., [Terms of Use](https://nomos.tech/terms)) can be situated in the `root-pages` directory.
+
+
+## Customization
+
+You can find instructions for adding additional documentation sections, implementing localization, and managing versioning on the [Docusaurus](https://docusaurus.io/docs) website.
+
+> Please note that theme customization is somewhat restricted; for more detailed instructions on customizing your theme, visit the [Logos Docusaurus Theme](https://github.com/acid-info/logos-docusaurus-plugins/tree/main/packages/logos-docusaurus-theme/) repository.
+
+
+## CI/CD
+
+- The `master` branch is automatically deployed to the production server (e.g., logos.co) through [CI](https://ci.infra.status.im)
+- The `develop` branch is automatically deployed to the staging server (e.g., dev.logos.co) through [CI](https://ci.infra.status.im)
+
+
+## Change Process
+
+1. Create a new working branch from `develop`: `git checkout develop; git checkout -b my-changes`.
+2. Make your changes, push them to the `origin`, and open a Pull Request against the `develop` branch.
+3. After approval, merge the pull request, and verify the changes on the staging server (e.g., https://dev.vac.dev).
+4. When ready to promote changes to the live website, rebase the `master` branch on the staging changes: `git checkout master; git pull origin master; git rebase origin/develop; git push`.

about/architect.md

@@ -0,0 +1,92 @@
+---
+title: Description and architecture
+sidebar_position: 2
+---
+
+Nomos was designed to serve as the trustless agreements layer for emerging network states, providing a key piece of infrastructure to the Logos tech stack. We believe that such a network must maintain the following properties:
+
+- **Maximum decentralisation:** Nomos is designed to place minimum resource demands on validators, ensuring that those without access to powerful hardware can participate. With the network maximally accessible, greater numbers of users can join as full peers, strengthening Nomos from a security perspective.
+
+- **Multi-chain ecosystem:** Nomos' multi-chain architecture is designed to support multiple heterogeneous network states with their own rules, or even desires for independence. In addition to extending greater sovereignty to the network states on Nomos, this approach enables unlimited horizontal scaling.
+
+- **Isolated performance trade-offs:** Nomos will provide a means for customizable execution environments in which trade-offs can be made to achieve performance enhancements such as high transaction throughput.
+
+- **Privacy-centric:** We believe privacy is essential for the self-determination and sovereignty of aspiring network states. Consequently, Nomos has been designed to protect user privacy at the network level, and in such a way as to enable the integration of new privacy techniques as they become available.
+
+### Design space
+
+To achieve the above, Nomos is developing an underexplored area in the design space between Ethereum, Cosmos, Polkadot, and newer systems like Celestia and Anoma.
+
+Ethereum pioneered the concept of a blockchain network capable of smart contract execution, ushering in an ongoing era of monetary and organisational experimentation. Yet, it is vulnerable to various centralising forces. Furthermore, while its rollup-centric approach to scaling has the potential for decentralisation, most rollups today rely on centralised sequencers, and inter-rollup communication presents its own complications. While Nomos is inspired by Ethereum in many ways, these limitations make Ethereum ill-suited for our vision of a network of network states.
+
+App-chain ecosystems like Cosmos and Polkadot offer an alternative architecture but introduce their own challenges. Examples include bootstrapping sufficient participants to ensure the economic security of multiple independent chains, and addressing the asynchronous nature of cross-chain protocols. While Polkadot's shared security model offers something of a solution, the network fails to enable easy, permissionless participation and its parachains cannot be considered fully sovereign.
+
+Meanwhile, Anoma's fractal approach to scaling maintains decentralisation while providing flexibility and customizability closer to our vision for Nomos. However, the approach is still to be tested widely by real-world applications, which will surely produce its own challenges. Finally, Nomos implements insights from Celestia's architecture in its approach to communication, sovereignty, and scalability.
+
+<br />
+
+### Network architecture
+
+Nomos consists of three layers—the Base Layer, Coordination Layer, and Execution Zones. Each has a specific role that contributes to the system's functionality and performance.
+
+<br />
+
+**Base Layer**
+
+Nomos' Base Layer focuses exclusively on consensus, data availability, and decentralisation, with the goal of ensuring stability, security, and scalability for the rest of the network. No execution or validation is performed at the Base Layer, as functions requiring access to state cannot be as reliably decentralised as consensus and data availability.
+
+The Carnot consensus protocol is crucial to ensuring high performance as the network scales from a few validators to tens of thousands. A forthcoming paper covers Carnot in greater detail. 
+
+Alongside ensuring maximum decentralisation, the Base Layer also strives to make data availability scalable. It achieves this by:
+
+- Reducing the amount of computation validators need by minimising  or eliminating block execution or verification from the Base Layer.
+
+- Reducing the amount of data light clients need to download through Data Availability Sampling.
+
+- Reducing data redundancy in the network via sharding techniques that decouple data stored on the blockchain from the data that a single node needs to process and store.
+
+<br />
+
+**Coordination Layer**
+
+Above the Base Layer is the Coordination Layer. The Coordination Layer's aim is to support functions common across all Execution Zones. To ensure maximum decentralisation, these functions are kept to the bare minimum, since everything on the Coordination Layer must be downloaded and verified by all validators. 
+
+The Coordination Layer provides the following functions only:
+
+- **Verification of ZK proofs:** The Coordination Layer's ability to verify ZK proofs facilitates powerful bridging capabilities, including private deposits and withdrawals between the Coordination Layer and Execution Zones, inter-Execution Zone private transfers, and generalised use cases.
+
+- **Message passing between Execution Zones:** The Coordination Layer enables Execution Zones to communicate asynchronously with each other. Such messaging is a powerful feature but not entirely trustless—as detailed in the forthcoming Nomos whitepaper.
+
+- **Special operations, such as those relating to the creation of new Execution Zones:** Initially, these special operations are limited to initiating new Execution Zones and the creation of a new zone's genesis block.  
+
+- **Censorship resistance:** Censorship resistance is an emergent property of the above features, enabling any user to "exit" an execution zone by submitting transactions to the Coordination Layer directly. This is particularly powerful in the event that an Execution Zone attempts to censor a user's actions.
+
+<br />
+
+**Execution Zones**
+
+The Base and Coordination Layers support a third layer of Execution Zones. Execution Zones provide the following properties: 
+
+- Share liquidity with the entire Nomos network.
+
+- Configurable latency reduction.
+
+- Configurable throughput increases.
+
+- Adaptability to specific applications and use cases.
+
+Execution Zones are most easily thought of as virtual sidechains that share the same global data availability space. Transactions associated with an Execution Zone are only processed by that zone's validators. However, unlike traditional sidechains, all applications on Nomos share the same blockchain, and data availability is uniformly ensured by the global Nomos network.
+
+This architecture makes Execution Zones more powerful than traditional sidechains as they:
+
+- Use trust-minimised bridging for communication. 
+
+- Can access each other's transactions securely. 
+
+- Share liquidity across the network. 
+
+- Enable improved security via restaking. 
+
+Execution Zones exist to satisfy a wide range of application requirements that may demand far greater performance characteristics than what a highly decentralised, monolithic blockchain can achieve before hitting scaling limits. Such applications are often willing to make compromises in terms of security or decentralisation to achieve higher performance. By combining the elastic consensus algorithm Carnot with a restaking mechanism and flexible execution models, Nomos grants a high degree of Execution Zone adaptability.
+
+![architect.png](/subpages/architect.png)

about/index.md

@@ -0,0 +1,40 @@
+---
+title: About
+sidebar_position: 1
+---
+
+Nomos is an innovative blockchain platform designed to address the critical requirements of the network state. It aims to provide developers with secure, flexible, and scalable infrastructure for building a wide range of applications while respecting the privacy and sovereignty of its users.
+
+Nomos serves as the trustless agreement layer of the [Logos](https://logos.co/) tech stack. Alongside the communications layer, [Waku](https://waku.org/), and the storage layer, [Codex](https://codex.storage/), it is one of the Logos Collective's foundational projects.
+
+We believe that blockchain technology has the potential to lay the foundations of a fairer, less corruptible and, ultimately, freer society. However, its most successful implementations to date fall short of achieving this. 
+
+<br/>
+
+## Network-level privacy, network-level sovereignty
+
+Bitcoin and Ethereum emerged from the cypherpunk tradition. As Eric Hughes wrote in his seminal 1993 essay, "A Cypherpunk's Manifesto":
+
+> "Privacy is necessary for an open society in the electronic age."
+
+Yet, neither network protects the right to privacy by default. Without network-level privacy, these technologies are, in fact, the perfect tool for surveillance because every on-chain interaction is recorded publicly forever.
+
+We believe that such absolute transparency massively limits the scope of the technology's adoption, and therefore its revolutionary potential. We cannot expect individuals to voluntarily exit the current system into one in which their every interaction (both financial and social) is forever available for the entire world to see. When we buy a coffee, for example, there is no need for the seller to see our salary, other purchase history, or political leanings.
+
+### Consent of the governed
+
+Furthermore, we believe consent to be a critical element of any governance system. We find the nation-state's claims of governance via implied consent to be extremely contrived.  And we believe blockchain-based systems represent an improvement because every on-chain action is voluntary and requires an individual to digitally sign, therefore, providing explicit consent.
+
+While this is certainly a step in the right direction, it does not go far enough. If an individual no longer aligns with the on-chain institutions of which they were once a part, today's blockchains offer a means of exiting the system to recreate something new. However, the cost to do so successfully can be prohibitively expensive.
+
+There have been numerous occasions in history where an on-chain community has been divided on some issue, resulting in a hard fork that creates two independent chains. In such situations, both networks suffer in terms of their overall security, making them more vulnerable to external attacks.
+
+Nomos leverages a novel architecture to avoid this situation. We believe that a simple disagreement over a community's path forward should not threaten the existence of either party. The Nomos network enables the creation of numerous semi-autonomous execution zones that share the main network's security while retaining the freedom to follow their own rulesets, and eventually become fully independent if they so choose.
+
+<br/>
+
+### History
+
+Work on Nomos began among a small subgroup of Status core contributors in June, 2021. The network takes its name from the ancient Greek concept of law, while alluding to the protection of its users’ autonomy.
+
+Nomos was first announced as a core Logos project in June 2023.

about/roadmap.md

@@ -0,0 +1,9 @@
+---
+title: Development roadmap
+sidebar_position: 3
+---
+
+At this early stage of Nomos' development, the team is primarily focused on implementing the network's consensus protocol, Carnot. As the consensus protocol is so foundational to the rest of the project, it must precede other development areas. Alongside Carnot, Nomos' contributors are working on defining the network architecture, which will also influence future roadmap items.
+
+After defining the network architecture and implementing the consensus protocol, we can establish further milestones both above and below the consensus protocol. Above the consensus layer will be the network's data model and execution environments, which will enable advanced functionality. Below will be P2P networking and peer discovery, which must be built or integrated while maintaining privacy and performance.
+

about/team.md

@@ -0,0 +1,14 @@
+---
+title: Core contributors
+sidebar_position: 4
+---
+
+Building Nomos is a team of passionate and experienced blockchain developers and researchers. 
+
+Alongside Nomos' project lead is a team of researchers and developers with experience as software engineers both within and beyond the web3 ecosystem, and in academia.
+
+At this stage of development, the group of contributors working on Nomos is small, meaning it has a loose, fluid structure. As more contributors join to work on the network, we expect to revise the structure detailed here. 
+
+Nomos is keen to work with other contributors. If you share our passion for decentralisation, individual sovereignty and privacy, we'd love to hear from you. As an open-source project, we also welcome community contributions. Please check out our [Github repo here](https://github.com/logos-co).
+
+[Work with us](https://jobs.status.im/)

babel.config.js

@@ -0,0 +1,3 @@
+module.exports = {
+  presets: [require.resolve("@docusaurus/core/lib/babel/preset")],
+};

docusaurus.config.js

@@ -0,0 +1,116 @@
+// @ts-check
+// Note: type annotations allow type checking and IDEs autocompletion
+require('dotenv').config()
+
+/** @type {import('@docusaurus/types').Config} */
+const config = {
+  title: 'Nomos',
+  url: 'https://nomos.tech',
+  baseUrl: '/',
+
+  markdown: {
+    mermaid: true,
+  },
+
+  // Even if you don't use internalization, you can use this field to set useful
+  // metadata like html lang. For example, if your site is Chinese, you may want
+  // to replace "en" with "zh-Hans".
+  i18n: {
+    defaultLocale: 'en',
+    locales: ['en'],
+  },
+
+  presets: [
+    [
+      '@acid-info/logos-docusaurus-preset',
+      /** @type {import('@acid-info/logos-docusaurus-preset').PluginOptions} */
+      ({
+        businessUnit: 'Nomos',
+        theme: {
+          name: 'default',
+          options: {
+            customCss: [require.resolve('./src/css/custom.scss')],
+            docs: {
+              default: {
+                sidebar: {
+                  hide: true,
+                },
+              },
+            },
+          },
+        },
+        docs: {
+          routeBasePath: '/',
+          path: 'root-pages',
+        },
+        og: {},
+      }),
+    ],
+  ],
+
+  plugins: [
+    [
+      '@docusaurus/plugin-content-docs',
+      {
+        id: 'about',
+        routeBasePath: '/about',
+        path: 'about',
+      },
+    ],
+  ],
+
+  themeConfig:
+    /** @type {import('@acid-info/logos-docusaurus-preset').ThemeConfig} */
+    ({
+      navbar: {
+        items: [
+          {
+            type: 'search',
+          },
+          {
+            label: 'About',
+            to: '/about',
+          },
+          {
+            label: 'Features',
+            href: '/#features',
+          },
+          {
+            label: 'Github',
+            href: 'https://github.com/logos-co',
+          },
+        ],
+      },
+      footer: {
+        copyright: 'Nomos @2023<br/>All Rights Reserved.',
+        links: [
+          {
+            items: [
+              {
+                href: 'https://twitter.com/Nomos_tech',
+                label: 'Twitter',
+              },
+              {
+                href: 'https://discord.gg/NYDm83h46b',
+                label: 'Discord',
+              },
+            ],
+          },
+          {
+            items: [
+              {
+                href: 'https://jobs.status.im/',
+                label: 'Work with us',
+              },
+              {
+                href: '/terms',
+                label: 'Terms & conditions',
+              },
+            ],
+          },
+        ],
+      },
+    }),
+}
+
+module.exports = config

package.json

@@ -0,0 +1,53 @@
+{
+  "name": "logos-homepage-template",
+  "version": "0.0.0",
+  "private": true,
+  "scripts": {
+    "docusaurus": "docusaurus",
+    "start": "docusaurus start",
+    "build": "docusaurus build",
+    "swizzle": "docusaurus swizzle",
+    "deploy": "docusaurus deploy",
+    "clear": "docusaurus clear",
+    "serve": "docusaurus serve",
+    "write-translations": "docusaurus write-translations",
+    "write-heading-ids": "docusaurus write-heading-ids",
+    "typecheck": "tsc"
+  },
+  "dependencies": {
+    "@acid-info/logos-docusaurus-preset": "^1.0.0-alpha.97",
+    "@docusaurus/core": "2.4.1",
+    "@docusaurus/preset-classic": "2.4.1",
+    "@docusaurus/theme-mermaid": "^2.4.1",
+    "@emotion/react": "^11.11.0",
+    "@emotion/styled": "^11.11.0",
+    "@mdx-js/react": "^1.6.22",
+    "clsx": "^1.2.1",
+    "dotenv": "^16.0.3",
+    "prism-react-renderer": "^1.3.5",
+    "react": "^17.0.2",
+    "react-dom": "^17.0.2",
+    "sass": "^1.62.1",
+    "tsdx": "^0.14.1"
+  },
+  "devDependencies": {
+    "@docusaurus/module-type-aliases": "2.4.1",
+    "@tsconfig/docusaurus": "^1.0.5",
+    "typescript": "^4.7.4"
+  },
+  "browserslist": {
+    "production": [
+      ">0.5%",
+      "not dead",
+      "not op_mini all"
+    ],
+    "development": [
+      "last 1 chrome version",
+      "last 1 firefox version",
+      "last 1 safari version"
+    ]
+  },
+  "engines": {
+    "node": ">=16.14"
+  }
+}

root-pages/terms.md

@@ -0,0 +1,75 @@
+---
+displayed_sidebar: null
+sidebar_class_name: hidden
+---
+
+# Terms of Use
+
+These terms of use ('**Website Terms of Use**') are entered into by you and us, and they govern your access and use of the Website, including any content and functionality contained in the Website.
+
+It is your responsibility to read the Website Terms of Use carefully before your use of the Website and your use of the Website means you have agreed to be bound and comply with these Website Terms of Use.
+
+If you do not agree with these Website Terms of Use, you must not access or use the Website.
+
+### Content provided for informational purposes only
+
+Content available on the Website is for informational purposes only and is not intended to address the specific circumstances of any particular individual or entity. Such content may not always be entirely accurate, complete, or up to date, and may also include inaccuracies or typographical errors. You are solely responsible for verifying their adequacy, completeness, and accuracy, and any reliance you place on such content is at your own risk.
+
+None of the content on this Website should be considered by you as legal, tax, investment, financial, professional, or any other type of advice. You should always conduct your own research and seek independent professional advice if necessary. You are solely responsible for the decisions or actions you might take in this respect. We are not liable for any loss resulting from your action (or inaction) and decisions based on the content on this Website.
+
+Additionally, we are not responsible for any information, content, or services contained in any third-party content or on any third-party websites accessible or linked through this Website.
+
+### Intellectual property rights
+
+The Website and its contents are made available under free and open-source licences. This means that anyone can use, share, and modify such content, as long as they follow the terms of the applicable licence.
+
+### Third-party website links
+
+To the extent the Website provides any links to a third-party website, then its terms and conditions, including privacy policies, govern your use of those third-party websites. We have no control over such third-party websites and will not be liable for your use of or activities on any third-party websites accessed through the Website. If you access such third-party websites through the Website, it is at your own risk and you are solely responsible for your activities on such third-party websites.
+
+The Website may embed videos from Youtube, a service provided by Google LLC, using Youtube’s privacy-enhanced mode. When you interact with such videos, Youtube may place cookies on your personal device which do not directly identify individual users. Unless you are logged in to a Google account, Youtube will not store information to personalise your experience. We do not have any control over these cookies set by Youtube and it is recommended that you review YouTube’s embedding videos information page.
+
+### Disclaimer
+
+The Website is provided by us on an ‘as is’ basis, and you use the Website at your own sole discretion and risk.
+
+We disclaim all warranties of any kind, express or implied, including without limitation the warranties of merchantability, fitness for a particular purpose, and non-infringement of intellectual property or other violation of rights. We do not warrant or make any representations concerning the completeness, accuracy, legality, utility, reliability, suitability, or availability of the use of the Website, the content on this Website, or otherwise relating to the Website, such content, or on any sites linked to this site.
+
+We make no claims that the Website or any of its content is accessible, legally compliant or appropriate in your jurisdiction. Your access or use of the Website is at your own sole discretion and you are solely responsible for complying with any applicable local laws. These disclaimers will apply to the maximum extent permitted by applicable law.
+
+
+### Limitation of liability
+
+We will not be held liable to you under any contract, negligence, strict liability, or other legal or equitable theory for any lost profits, cost of procurement for substitute services, or any special, incidental, or consequential damages related to, arising from, or in any way connected with these Website Terms of Use, the Website, the content on the Website, or your use of the Website, even if we have been advised of the possibility of such damages. In any event, our aggregate liability for such claims is limited to EUR 100 (one hundred euros). This limitation of liability will apply to the maximum extent permitted by applicable law.
+
+### Indemnity
+
+You shall indemnify us and hold us harmless from and against any and all claims, damages, and expenses, including attorneys’ fees arising from or related to your use of the Website and the content on the Website, including without limitation your violation of these Website Terms of Use.
+
+### Modifications
+
+We may modify or replace any part of this Website Terms of Use at any time and without notice. You are responsible for checking the Website periodically for any changes. The new Website Terms of Use will be effective immediately upon its posting on the Website.
+
+### Governing law
+
+Swiss law governs these Website Terms of Use and any disputes between you and us, whether in court or arbitration, without regard to conflict of laws provisions.
+
+### Disputes
+
+In these terms, ‘dispute’ has the broadest meaning enforceable by law and includes any claim you make against or controversy you may have in relation to these Website Terms of Use, the Website, the content on the Website, or your use of the Website.
+
+We prefer arbitration over litigation as we believe it meets our principle of resolving disputes in the most effective and cost-effective manner. You are bound by the following arbitration clause, which waives your right to litigation and to be heard by a judge. Please note that court review of an arbitration award is limited. You also waive all your rights to a jury trial (if any) in any and all jurisdictions.
+
+If a (potential) dispute arises, you must first use your reasonable efforts to resolve it amicably with us. If these efforts do not result in a resolution of such dispute, you shall then send us a written notice of dispute setting out (i) the nature of the dispute and the claim you are making; and (ii) the remedy you are seeking.
+
+If we and you are unable to further resolve this dispute within sixty (60) calendar days of us receiving this notice of dispute, then any such dispute will be referred to and finally resolved by you and us through arbitration administered by the Swiss Chambers’ Arbitration Institution in accordance with the Swiss Rules of International Arbitration for the time being in force, the rules of which are deemed to be incorporated herein by reference. The arbitral decision may be enforced in any court. The arbitration will be held in Zug, Switzerland, and may be conducted via video conference virtual/online methods if possible. The tribunal will consist of one arbitrator, and all proceedings as well as communications between the parties will be kept confidential. The language of the arbitration will be in English. Payment of all relevant fees in respect of the arbitration, including filing, administration, and arbitrator fees, will be in accordance with the Swiss Rules of International Arbitration.
+
+Regardless of any applicable statute of limitations, you must bring any claims within one year after the claim arose or the time when you should have reasonably known about the claim. You also waive the right to participate in a class action lawsuit or a classwide arbitration against us.
+
+### About these Website Terms of Use
+
+These Website Terms of Use cover the entire agreement between you and us regarding the Website and supersede all prior and contemporaneous understandings, agreements, representations, and warranties, both written and oral, with respect to the Website.
+
+The captions and headings identifying sections and subsections of these Website Terms of Use are for reference only and do not define, modify, expand, limit, or affect the interpretation of any provisions of these Website Terms of Use.
+
+If any part of these Website Terms of Use is held invalid or unenforceable, that part will be severable from these Website Terms of Use, and the remaining portions will remain in full force and effect. If we fail to enforce any of these Website Terms of Use, that does not mean that we have waived our right to enforce them.

src/components/mdx/index.tsx

@@ -0,0 +1 @@
+export * from '@acid-info/logos-docusaurus-theme/lib/client/components/mdx'

src/css/custom.scss

@@ -0,0 +1,7 @@
+:root {
+}
+
+body,
+html {
+  overflow-x: hidden;
+}

src/pages/index.mdx

@@ -0,0 +1,149 @@
+---
+title: Private, Sovereign, and Modular Blockchains for Network States
+description: Nomos is a novel blockchain project that will address a network state's fundamental need for adaptable privacy and sovereignty.
+---
+
+import {
+  Hero,
+  HeroTitle,
+  HeroDescription,
+  HeroVideo,
+  HeroActions,
+  HeroAction,
+  CallToActionSection,
+  CallToActionButton,
+  FeatureList,
+  Showcase,
+  HeroInfo,
+  Roadmap,
+  Box,
+} from '../components/mdx'
+
+<Hero size="large">
+  <HeroInfo>
+    <HeroTitle>
+      {'Private, Sovereign, and Modular Blockchains for Network States'} 
+    </HeroTitle>
+    <HeroDescription>
+      {'Nomos is a novel blockchain project that will address a network state\'s fundamental need for adaptable privacy and sovereignty.'} 
+    </HeroDescription>
+    <HeroActions>
+      <HeroAction href="https://discord.gg/NYDm83h46b" target="_blank">
+        Get involved
+      </HeroAction>
+    </HeroActions>
+  </HeroInfo>
+
+  <HeroVideo
+    placeholderSrc="/hero/david04-1080x1080-placeholder.png"
+    desktop={{ scale: "1.917" }}
+    mobile={{ scale: "1.917", minHeight: "80vh", height: '100%'  }}
+  >
+    <source src="/hero/david04-2048x2048-24fps-1M.mov" type='video/mp4; codecs="hvc1"' />
+    <source src="/hero/david04-2048x2048-24fps-1M.webm" type="video/webm" />  
+  </HeroVideo>
+
+</Hero>
+
+<FeatureList
+  id="features"
+  alignment="top"
+  title="High-level project goals"
+  features={[
+    {
+      title: 'Privacy',
+      description:
+        'Nomos is prioritising privacy for both users and infrastructure providers. At the app level developers choose how much identifying and transaction information users may disclose, while validators and delegators are able to shield their participation in the network.',
+    },
+    {
+      title: 'Sovereignty',
+      description:
+        "Communities have the ability to adopt the initial network state, or fork it based on a new set of rules they wish to establish. Users may remain on the initial blockchain, migrate to the new one, or be in both.",
+    },
+    {
+      title: 'Modularity',
+      description:
+        'Nomos has an integrated modular architecture separating data availability, coordination, and execution. Modular design is essential for combining decentralisation with scalability through layer-specific resource pricing.',
+    },
+    {
+      title: 'Adaptability',
+      description:
+        "Privacy and sovereignty are fundamental to Nomos' mission. Because they exist on a spectrum, Nomos is building mechanisms that allow both to be adapted and expanded based on the needs and maturity of a network state.",
+    },
+  ]}
+>
+</FeatureList>
+
+<Box top={{ xs: 144, lg: 216 }}>
+  <CallToActionSection
+    title="Logos Network State"
+    columns={1}
+    description={
+      <>
+        Nomos is the blockchain layer of the Logos Network State. Logos is a grassroots movement to provide trust-minimised, corruption-resistant governing services and social institutions to peaceful people worldwide.
+        <br/>
+        <br/>
+        Learn more about our ambitious vision.  
+      </>
+    }
+    label="Explore Logos"
+    href="https://logos.co/"
+    target="_blank"
+  />
+</Box>
+
+<Box top={{ xs: 144, lg: 216 }}>
+  <Roadmap
+    title="Roadmap"
+    alignment="top"
+    timeline={[
+      {
+        period: '2024 Q1',
+        borderStyle: 'solid',
+        description: "Full specification of the base layer",
+      },
+      {
+        period: '2024 Q3',
+        borderStyle: 'solid',
+        description: 'Testnet base layer implementation',
+      },
+      {
+        period: '2024 Q4',
+        borderStyle: 'dashed',
+        description: 'Full specification of the coordination layer',
+      },
+      {
+        period: '2025 Q1',
+        borderStyle: 'solid',
+        description: 'Testnet coordination layer implementation',
+      },
+      {
+        period: '2025 Q3',
+        borderStyle: 'solid',
+        description: 'Mainnet base plus coordination layer launch',
+      },
+      {
+        period: '2025 Q4',
+        description: 'Specification and implementation of execution zones',
+      },
+    ]}
+  >
+    <CallToActionButton size="small" variant="outlined" href="/about/roadmap">
+      Read more
+    </CallToActionButton>
+  </Roadmap>
+</Box>
+
+<Box top={{ xs: 144, lg: 336 }}>
+  <CallToActionSection
+    title={
+      <>
+        Want to get involved with Nomos? <br/> 
+        Join the Discord community.
+      </>
+    }
+    label="Discord"
+    target="_blank"
+    href="https://discord.gg/NYDm83h46b"
+  />
+</Box>

static/showcase/railgun-mark-white.svg

@@ -0,0 +1,4 @@
+<svg width="58" height="58" viewBox="0 0 58 58" fill="none" xmlns="http://www.w3.org/2000/svg">
+<rect width="58" height="58" rx="29" fill="white"/>
+<path d="M23 39V19H29.737C31.2013 19 32.4164 19.2669 33.3823 19.8008C34.3544 20.3346 35.0804 21.0736 35.5603 22.0176C36.0402 22.9551 36.2802 24.0391 36.2802 25.2695C36.2802 26.4935 36.0371 27.571 35.5511 28.502C35.0712 29.4264 34.3452 30.1458 33.3731 30.6602C32.4072 31.1745 31.192 31.4316 29.7278 31.4316H24.6243V28.834H29.4693C30.3922 28.834 31.1428 28.694 31.7212 28.4141C32.3056 28.1341 32.7332 27.7272 33.004 27.1934C33.2747 26.6595 33.41 26.0182 33.41 25.2695C33.41 24.5143 33.2716 23.86 32.9947 23.3066C32.724 22.7533 32.2964 22.3301 31.7119 22.0371C31.1336 21.7376 30.3738 21.5879 29.4324 21.5879H25.8517V39H23ZM32.3303 29.9766L37 39H33.7515L29.174 29.9766H32.3303Z" fill="black"/>
+</svg>

static/showcase/status-mark-white.svg

@@ -0,0 +1,3 @@
+<svg width="58" height="58" viewBox="0 0 58 58" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path fill-rule="evenodd" clip-rule="evenodd" d="M33.6479 28.7455C30.3452 28.9358 28.2754 28.1665 24.9723 28.3573C24.1531 28.4033 23.3396 28.522 22.5412 28.7121C23.0288 22.6037 27.3519 17.2602 33.2306 16.9205C36.8381 16.7123 40.4439 18.9397 40.6394 22.5555C40.8319 26.1094 38.1221 28.487 33.6483 28.7451L33.6479 28.7455ZM24.779 41.24C21.323 41.4352 17.8692 39.3501 17.6817 35.9665C17.4972 32.6404 20.0937 30.4152 24.3794 30.1736C27.543 29.9953 29.5261 30.7157 32.6897 30.5369C33.4741 30.4939 34.2533 30.3828 35.0186 30.2048C34.5523 35.9214 30.411 40.9226 24.779 41.24ZM28.9999 1.4449C13.7812 1.44446 1.44434 13.7812 1.44434 29C1.44434 44.2189 13.7812 56.5556 28.9999 56.5556C44.2186 56.5556 56.5554 44.2184 56.5554 29C56.5554 13.7816 44.2186 1.44446 28.9999 1.44446" fill="white"/>
+</svg>

static/showcase/xmtp-mark-white.svg

@@ -0,0 +1,10 @@
+<svg width="57" height="58" viewBox="0 0 57 58" fill="none" xmlns="http://www.w3.org/2000/svg">
+<g clip-path="url(#clip0_603_7836)">
+<path d="M0 29C0 12.9837 12.8112 0 28.6147 0C44.4079 0 56.61 12.7424 56.9815 28.8744C56.9815 34.0217 55.2473 38.3527 50.9119 42.4328C47.2482 45.8808 41.0019 46.3874 36.4191 43.8139C33.1479 41.9015 30.627 37.8289 28.4908 34.8377L24.5268 40.9892H15.9796L24.0314 28.8739L16.2274 16.948H25.0223L28.5528 23.0996L32.0211 16.948H40.8782L32.8265 28.8744C32.8265 28.8744 36.6665 34.8377 38.7722 37.1602C40.8782 39.4828 44.7182 39.5455 47.1955 37.0346C49.9195 34.274 50.5292 32.0759 50.5403 28.8744C50.5828 16.4828 40.8709 6.52813 28.6147 6.52813C16.3687 6.52813 6.44139 16.5891 6.44139 29C6.44139 41.4108 16.3687 51.472 28.6147 51.472C30.3085 51.472 31.932 51.3277 33.5077 50.9696L34.8704 57.3096C32.6282 57.819 30.8169 58 28.6147 58C12.8112 58 0 45.0162 0 29Z" fill="white"/>
+</g>
+<defs>
+<clipPath id="clip0_603_7836">
+<rect width="57" height="58" fill="white"/>
+</clipPath>
+</defs>
+</svg>

tsconfig.json

@@ -0,0 +1,4 @@
+{
+  // This file is not used in compilation. It is here just for a nice editor experience.
+  "extends": "@tsconfig/docusaurus/tsconfig.json"
+}