migrate to starlight #8

This commit is contained in:
tree🌴 2024-03-17 03:25:35 +01:00
parent 7b3104c884
commit 7356331159
104 changed files with 4083 additions and 20396 deletions

View file

@ -1,43 +0,0 @@
name: Deploy to GitHub Pages
on:
push:
branches:
- main
# Review gh actions docs if you want to further define triggers, paths, etc
# https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#on
permissions:
contents: write
jobs:
deploy:
name: Deploy to GitHub Pages
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
with:
node-version: 18
cache: yarn
- name: Install dependencies
run: yarn install --frozen-lockfile
- name: Build website
run: yarn build
# Popular action to deploy to GitHub Pages:
# Docs: https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-docusaurus
- name: Deploy to GitHub Pages
uses: peaceiris/actions-gh-pages@v3
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
# Build output to publish to the `gh-pages` branch:
publish_dir: ./build
# The following lines assign commit authorship to the official
# GH-Actions bot for deploys to `gh-pages` branch:
# https://github.com/actions/checkout/issues/13#issuecomment-724415212
# The GH actions bot is used by default if you didn't specify the two fields.
# You can swap them out with your own user credentials.
user_name: github-actions[bot]
user_email: 41898282+github-actions[bot]@users.noreply.github.com

31
.gitignore vendored
View file

@ -1,20 +1,21 @@
# Dependencies # build output
/node_modules dist/
# generated types
.astro/
# Production # dependencies
/build node_modules/
# Generated files
.docusaurus
.cache-loader
# Misc
.DS_Store
.env.local
.env.development.local
.env.test.local
.env.production.local
# logs
npm-debug.log* npm-debug.log*
yarn-debug.log* yarn-debug.log*
yarn-error.log* yarn-error.log*
pnpm-debug.log*
# environment variables
.env
.env.production
# macOS-specific files
.DS_Store

4
.vscode/extensions.json vendored Normal file
View file

@ -0,0 +1,4 @@
{
"recommendations": ["astro-build.astro-vscode"],
"unwantedRecommendations": []
}

11
.vscode/launch.json vendored Normal file
View file

@ -0,0 +1,11 @@
{
"version": "0.2.0",
"configurations": [
{
"command": "./node_modules/.bin/astro dev",
"name": "Development server",
"request": "launch",
"type": "node-terminal"
}
]
}

121
LICENSE
View file

@ -1,121 +0,0 @@
Creative Commons Legal Code
CC0 1.0 Universal
CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
HEREUNDER.
Statement of Purpose
The laws of most jurisdictions throughout the world automatically confer
exclusive Copyright and Related Rights (defined below) upon the creator
and subsequent owner(s) (each and all, an "owner") of an original work of
authorship and/or a database (each, a "Work").
Certain owners wish to permanently relinquish those rights to a Work for
the purpose of contributing to a commons of creative, cultural and
scientific works ("Commons") that the public can reliably and without fear
of later claims of infringement build upon, modify, incorporate in other
works, reuse and redistribute as freely as possible in any form whatsoever
and for any purposes, including without limitation commercial purposes.
These owners may contribute to the Commons to promote the ideal of a free
culture and the further production of creative, cultural and scientific
works, or to gain reputation or greater distribution for their Work in
part through the use and efforts of others.
For these and/or other purposes and motivations, and without any
expectation of additional consideration or compensation, the person
associating CC0 with a Work (the "Affirmer"), to the extent that he or she
is an owner of Copyright and Related Rights in the Work, voluntarily
elects to apply CC0 to the Work and publicly distribute the Work under its
terms, with knowledge of his or her Copyright and Related Rights in the
Work and the meaning and intended legal effect of CC0 on those rights.
1. Copyright and Related Rights. A Work made available under CC0 may be
protected by copyright and related or neighboring rights ("Copyright and
Related Rights"). Copyright and Related Rights include, but are not
limited to, the following:
i. the right to reproduce, adapt, distribute, perform, display,
communicate, and translate a Work;
ii. moral rights retained by the original author(s) and/or performer(s);
iii. publicity and privacy rights pertaining to a person's image or
likeness depicted in a Work;
iv. rights protecting against unfair competition in regards to a Work,
subject to the limitations in paragraph 4(a), below;
v. rights protecting the extraction, dissemination, use and reuse of data
in a Work;
vi. database rights (such as those arising under Directive 96/9/EC of the
European Parliament and of the Council of 11 March 1996 on the legal
protection of databases, and under any national implementation
thereof, including any amended or successor version of such
directive); and
vii. other similar, equivalent or corresponding rights throughout the
world based on applicable law or treaty, and any national
implementations thereof.
2. Waiver. To the greatest extent permitted by, but not in contravention
of, applicable law, Affirmer hereby overtly, fully, permanently,
irrevocably and unconditionally waives, abandons, and surrenders all of
Affirmer's Copyright and Related Rights and associated claims and causes
of action, whether now known or unknown (including existing as well as
future claims and causes of action), in the Work (i) in all territories
worldwide, (ii) for the maximum duration provided by applicable law or
treaty (including future time extensions), (iii) in any current or future
medium and for any number of copies, and (iv) for any purpose whatsoever,
including without limitation commercial, advertising or promotional
purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
member of the public at large and to the detriment of Affirmer's heirs and
successors, fully intending that such Waiver shall not be subject to
revocation, rescission, cancellation, termination, or any other legal or
equitable action to disrupt the quiet enjoyment of the Work by the public
as contemplated by Affirmer's express Statement of Purpose.
3. Public License Fallback. Should any part of the Waiver for any reason
be judged legally invalid or ineffective under applicable law, then the
Waiver shall be preserved to the maximum extent permitted taking into
account Affirmer's express Statement of Purpose. In addition, to the
extent the Waiver is so judged Affirmer hereby grants to each affected
person a royalty-free, non transferable, non sublicensable, non exclusive,
irrevocable and unconditional license to exercise Affirmer's Copyright and
Related Rights in the Work (i) in all territories worldwide, (ii) for the
maximum duration provided by applicable law or treaty (including future
time extensions), (iii) in any current or future medium and for any number
of copies, and (iv) for any purpose whatsoever, including without
limitation commercial, advertising or promotional purposes (the
"License"). The License shall be deemed effective as of the date CC0 was
applied by Affirmer to the Work. Should any part of the License for any
reason be judged legally invalid or ineffective under applicable law, such
partial invalidity or ineffectiveness shall not invalidate the remainder
of the License, and in such case Affirmer hereby affirms that he or she
will not (i) exercise any of his or her remaining Copyright and Related
Rights in the Work or (ii) assert any associated claims and causes of
action with respect to the Work, in either case contrary to Affirmer's
express Statement of Purpose.
4. Limitations and Disclaimers.
a. No trademark or patent rights held by Affirmer are waived, abandoned,
surrendered, licensed or otherwise affected by this document.
b. Affirmer offers the Work as-is and makes no representations or
warranties of any kind concerning the Work, express, implied,
statutory or otherwise, including without limitation warranties of
title, merchantability, fitness for a particular purpose, non
infringement, or the absence of latent or other defects, accuracy, or
the present or absence of errors, whether or not discoverable, all to
the greatest extent permissible under applicable law.
c. Affirmer disclaims responsibility for clearing rights of other persons
that may apply to the Work or any use thereof, including without
limitation any person's Copyright and Related Rights in the Work.
Further, Affirmer disclaims responsibility for obtaining any necessary
consents, permissions or other rights required for any use of the
Work.
d. Affirmer understands and acknowledges that Creative Commons is not a
party to this document and has no duty or obligation with respect to
this CC0 or use of the Work.

View file

@ -1,15 +1,54 @@
# Web3Privacy Now Documentation # Starlight Starter Kit: Basics
[![Deploy to GitHub Pages](https://github.com/web3privacy/docs/actions/workflows/deploy.yml/badge.svg)](https://github.com/web3privacy/docs/actions/workflows/deploy.yml) [![Built with Starlight](https://astro.badg.es/v2/built-with-starlight/tiny.svg)](https://starlight.astro.build)
![Vercel Deploy](https://therealsujitk-vercel-badge.vercel.app/?app=w3pn-docs)
<a href="https://docs.web3privacy.info"><img width="75%" alt="Web3Privacy Now Documentation" src="https://github.com/web3privacy/docs/assets/67269/5e5df873-fbb9-4815-8b16-eb7975f09862" /></a><br/> ```
npm create astro@latest -- --template starlight
```
The documentation is based on the [Docusaurus 3](https://docusaurus.io/docs). [![Open in StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/github/withastro/starlight/tree/main/examples/basics)
[![Open with CodeSandbox](https://assets.codesandbox.io/github/button-edit-lime.svg)](https://codesandbox.io/p/sandbox/github/withastro/starlight/tree/main/examples/basics)
[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2Fwithastro%2Fstarlight%2Ftree%2Fmain%2Fexamples%2Fbasics&project-name=my-starlight-docs&repository-name=my-starlight-docs)
The production version can be found here: > 🧑‍🚀 **Seasoned astronaut?** Delete this file. Have fun!
* https://docs.web3privacy.info/
## License ## 🚀 Project Structure
CC0 1.0 Universal Inside of your Astro + Starlight project, you'll see the following folders and files:
```
.
├── public/
├── src/
│ ├── assets/
│ ├── content/
│ │ ├── docs/
│ │ └── config.ts
│ └── env.d.ts
├── astro.config.mjs
├── package.json
└── tsconfig.json
```
Starlight looks for `.md` or `.mdx` files in the `src/content/docs/` directory. Each file is exposed as a route based on its file name.
Images can be added to `src/assets/` and embedded in Markdown with a relative link.
Static assets, like favicons, can be placed in the `public/` directory.
## 🧞 Commands
All commands are run from the root of the project, from a terminal:
| Command | Action |
| :------------------------ | :----------------------------------------------- |
| `npm install` | Installs dependencies |
| `npm run dev` | Starts local dev server at `localhost:4321` |
| `npm run build` | Build your production site to `./dist/` |
| `npm run preview` | Preview your build locally, before deploying |
| `npm run astro ...` | Run CLI commands like `astro add`, `astro check` |
| `npm run astro -- --help` | Get help using the Astro CLI |
## 👀 Want to learn more?
Check out [Starlights docs](https://starlight.astro.build/), read [the Astro documentation](https://docs.astro.build), or jump into the [Astro Discord server](https://astro.build/chat).

82
astro.config.mjs Normal file
View file

@ -0,0 +1,82 @@
import { defineConfig } from 'astro/config';
import starlight from '@astrojs/starlight';
// https://astro.build/config
export default defineConfig({
integrations: [
starlight({
title: 'Web3Privacy Now Docs',
social: {
github: 'https://github.com/web3privacy',
twitter: 'https://twitter.com/web3privacy',
},
logo: {
src: './public/logo.png',
replacesTitle: true
},
sidebar: [
{ label: 'Introduction', link: '/' },
{
label: 'About Web3Privacy Now',
items: [
// Each item here is one entry in the navigation menu.
{ label: 'Manifesto', link: '/manifesto' },
{ label: 'Roadmap', link: '/roadmap' },
{ label: 'History', link: '/history' },
{ label: 'Brand', link: '/brand' },
{ label: 'Contact us', link: '/contacts' },
],
},
{
label: 'Projects',
items: [
// Each item here is one entry in the navigation menu.
{ label: 'Research', link: '/research' },
{ label: 'Privacy Explorer', link: '/projects/privacy-explorer' },
],
},
{
label: 'Future concepts',
items: [
{ label: 'Privacy Tech Awards', link: '/projects/privacy-tech-awards' }
]
},
{
label: 'Tools',
items: [
{ label: 'Git repositories', link: '/git' },
{ label: 'Communication tools', link: '/communication' },
{ label: 'Workgroups', link: '/workgroups' }
]
},
{
label: 'Community',
items: [
{ label: 'Follow us', link: '/follow-us' },
{ label: 'Get involved', link: '/get-involved' },
{ label: 'Contributors guide', link: '/contributors' },
{
label: 'Membership',
link: '/membership',
items: [
{ label: 'Personal benefits', link: '/membership/personal-benefits' }
]
},
{ label: 'Donate', link: '/donate' },
{ label: 'Code of conduct', link: '/code-of-conduct' },
]
},
{
label: 'Governance',
items: [
{ label: 'Governance overview', link: '/governance' },
{ label: 'Congress', link: '/congress' },
{ label: 'Core Team', link: '/core-team' },
{ label: 'Association', link: '/association' },
{ label: 'Contributors Guild', link: '/guild' },
]
}
],
}),
],
});

View file

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

1
docs Symbolic link
View file

@ -0,0 +1 @@
src/content/docs

View file

@ -1,176 +0,0 @@
// @ts-check
// `@type` JSDoc annotations allow editor autocompletion and type checking
// (when paired with `@ts-check`).
// There are various equivalent ways to declare your Docusaurus config.
// See: https://docusaurus.io/docs/api/docusaurus-config
import {themes as prismThemes} from 'prism-react-renderer';
/** @type {import('@docusaurus/types').Config} */
const config = {
title: 'Web3Privacy Now Documentation',
tagline: '',
favicon: 'img/favicon.ico',
// Set the production url of your site here
url: 'https://docs.web3privacy.info',
// Set the /<baseUrl>/ pathname under which your site is served
// For GitHub pages deployment, it is often '/<projectName>/'
baseUrl: '/',
// GitHub pages deployment config.
// If you aren't using GitHub pages, you don't need these.
organizationName: 'web3privacy', // Usually your GitHub org/user name.
projectName: 'w3pn-docs', // Usually your repo name.
onBrokenLinks: 'throw',
onBrokenMarkdownLinks: 'warn',
// Even if you don't use internationalization, 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'],
},
themes: [
[
require.resolve("@easyops-cn/docusaurus-search-local"),
{
// ... Your options.
// `hashed` is recommended as long-term-cache of index file is possible.
hashed: true,
// For Docs using Chinese, The `language` is recommended to set to:
// ```
// language: ["en", "zh"],
// ```
language: [ "en" ],
docsRouteBasePath: '/',
},
]
],
plugins: [
[
'@docusaurus/plugin-client-redirects',
{
redirects: [
{ from: '/research/Ethereum Privacy Ecosystem', to: '/research/ethereum-privacy-ecosystem' },
{ from: '/governance/multisig', to: '/core-team/multisig' },
],
}
]
],
presets: [
[
'@docusaurus/preset-classic',
/** @type {import('@docusaurus/preset-classic').Options} */
({
docs: {
routeBasePath: '/',
sidebarPath: './sidebars.js',
// Please change this to your repo.
// Remove this to remove the "edit this page" links.
editUrl:
'https://github.com/web3privacy/w3pn-docs/tree/main/',
showLastUpdateAuthor: true,
showLastUpdateTime: true
},
blog: false,
theme: {
customCss: './src/css/custom.css',
},
}),
],
],
themeConfig:
/** @type {import('@docusaurus/preset-classic').ThemeConfig} */
({
colorMode: {
defaultMode: "dark",
disableSwitch: false,
respectPrefersColorScheme: false,
},
// Replace with your project's social card
image: 'img/docusaurus-social-card.jpg',
navbar: {
//title: 'Documentation',
logo: {
alt: 'Web3Privacy Now',
src: 'img/logo.png',
},
items: [
{
type: 'docSidebar',
sidebarId: 'tutorialSidebar',
position: 'left',
label: 'Documentation',
},
{
href: 'https://web3privacy.info/',
label: 'Website',
position: 'right',
},
{
href: 'https://github.com/web3privacy',
label: 'GitHub',
position: 'right',
},
],
},
/*footer: {
style: 'dark',
links: [
{
title: 'Docs',
items: [
{
label: 'Documentation',
to: '/docs/intro',
},
],
},
{
title: 'Community',
items: [
{
label: 'Stack Overflow',
href: 'https://stackoverflow.com/questions/tagged/docusaurus',
},
{
label: 'Discord',
href: 'https://discordapp.com/invite/docusaurus',
},
{
label: 'Twitter',
href: 'https://twitter.com/docusaurus',
},
],
},
{
title: 'More',
items: [
{
label: 'Blog',
to: '/blog',
},
{
label: 'GitHub',
href: 'https://github.com/facebook/docusaurus',
},
],
},
],
copyright: `Copyright © ${new Date().getFullYear()} My Project, Inc. Built with Docusaurus.`,
},*/
prism: {
//theme: prismThemes.github,
darkTheme: prismThemes.dracula,
},
}),
};
export default config;

14796
package-lock.json generated

File diff suppressed because it is too large Load diff

View file

@ -1,46 +1,17 @@
{ {
"name": "w-3-pm-docs", "name": "intergalactic-iron",
"version": "0.0.0", "type": "module",
"private": true, "version": "0.0.1",
"scripts": { "scripts": {
"docusaurus": "docusaurus", "dev": "astro dev",
"start": "docusaurus start", "start": "astro dev",
"build": "docusaurus build", "build": "astro build",
"swizzle": "docusaurus swizzle", "preview": "astro preview",
"deploy": "docusaurus deploy", "astro": "astro"
"clear": "docusaurus clear",
"serve": "docusaurus serve",
"write-translations": "docusaurus write-translations",
"write-heading-ids": "docusaurus write-heading-ids"
}, },
"dependencies": { "dependencies": {
"@docusaurus/core": "^3.1.1", "@astrojs/starlight": "^0.21.1",
"@docusaurus/plugin-client-redirects": "^3.1.1", "astro": "^4.3.5",
"@docusaurus/preset-classic": "^3.1.1", "sharp": "^0.32.5"
"@easyops-cn/docusaurus-search-local": "^0.40.1",
"@mdx-js/react": "^3.0.0",
"clsx": "^2.0.0",
"prism-react-renderer": "^2.1.0",
"react": "^18.0.0",
"react-dom": "^18.0.0"
},
"devDependencies": {
"@docusaurus/module-type-aliases": "^3.1.1",
"@docusaurus/types": "^3.1.1"
},
"browserslist": {
"production": [
">0.5%",
"not dead",
"not op_mini all"
],
"development": [
"last 3 chrome version",
"last 3 firefox version",
"last 5 safari version"
]
},
"engines": {
"node": ">=18.0"
} }
} }

View file

@ -0,0 +1,11 @@
---
title: Example Guide
description: A guide in my new Starlight docs site.
---
Guides lead a user through a specific task they want to accomplish, often with a sequence of steps.
Writing a good guide requires thinking about what your users are trying to do.
## Further reading
- Read [about how-to guides](https://diataxis.fr/how-to-guides/) in the Diátaxis framework

36
public/docs-old/index.mdx Normal file
View file

@ -0,0 +1,36 @@
---
title: Welcome to Starlight
description: Get started building your docs site with Starlight.
template: splash
hero:
tagline: Congrats on setting up a new Starlight project!
image:
file: ../../assets/houston.webp
actions:
- text: Example Guide
link: /guides/example/
icon: right-arrow
variant: primary
- text: Read the Starlight docs
link: https://starlight.astro.build
icon: external
---
import { Card, CardGrid } from '@astrojs/starlight/components';
## Next steps
<CardGrid stagger>
<Card title="Update content" icon="pencil">
Edit `src/content/docs/index.mdx` to see this page change.
</Card>
<Card title="Add new content" icon="add-document">
Add Markdown or MDX files to `src/content/docs` to create new pages.
</Card>
<Card title="Configure your site" icon="setting">
Edit your `sidebar` and other config in `astro.config.mjs`.
</Card>
<Card title="Read the docs" icon="open-book">
Learn more in [the Starlight Docs](https://starlight.astro.build/).
</Card>
</CardGrid>

View file

@ -0,0 +1,11 @@
---
title: Example Reference
description: A reference page in my new Starlight docs site.
---
Reference pages are ideal for outlining how things work in terse and clear terms.
Less concerned with telling a story or addressing a specific use case, they should give a comprehensive outline of what you're documenting.
## Further reading
- Read [about reference](https://diataxis.fr/reference/) in the Diátaxis framework

1
public/favicon.svg Normal file
View file

@ -0,0 +1 @@
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 128 128"><path fill-rule="evenodd" d="M81 36 64 0 47 36l-1 2-9-10a6 6 0 0 0-9 9l10 10h-2L0 64l36 17h2L28 91a6 6 0 1 0 9 9l9-10 1 2 17 36 17-36v-2l9 10a6 6 0 1 0 9-9l-9-9 2-1 36-17-36-17-2-1 9-9a6 6 0 1 0-9-9l-9 10v-2Zm-17 2-2 5c-4 8-11 15-19 19l-5 2 5 2c8 4 15 11 19 19l2 5 2-5c4-8 11-15 19-19l5-2-5-2c-8-4-15-11-19-19l-2-5Z" clip-rule="evenodd"/><path d="M118 19a6 6 0 0 0-9-9l-3 3a6 6 0 1 0 9 9l3-3Zm-96 4c-2 2-6 2-9 0l-3-3a6 6 0 1 1 9-9l3 3c3 2 3 6 0 9Zm0 82c-2-2-6-2-9 0l-3 3a6 6 0 1 0 9 9l3-3c3-2 3-6 0-9Zm96 4a6 6 0 0 1-9 9l-3-3a6 6 0 1 1 9-9l3 3Z"/><style>path{fill:#000}@media (prefers-color-scheme:dark){path{fill:#fff}}</style></svg>

After

Width:  |  Height:  |  Size: 696 B

View file

Before

Width:  |  Height:  |  Size: 62 KiB

After

Width:  |  Height:  |  Size: 62 KiB

View file

@ -1,162 +0,0 @@
/**
* Creating a sidebar enables you to:
- create an ordered group of docs
- render a sidebar for each doc of that group
- provide next/previous navigation
The sidebars can be generated from the filesystem, or explicitly defined here.
Create as many sidebars as you want.
*/
// @ts-check
/** @type {import('@docusaurus/plugin-content-docs').SidebarsConfig} */
const sidebars = {
// By default, Docusaurus generates a sidebar from the docs folder structure
//tutorialSidebar: [{type: 'autogenerated', dirName: '.'}],
// But you can create a sidebar manually
tutorialSidebar: [
'index',
{
type: "html",
value: '<span class="sidebar-divider" />',
},
{
type: "html",
className: "sidebar-title",
value: "About Web3Privacy Now",
defaultStyle: true,
},
'manifesto',
'roadmap',
'history',
'brand',
{
type: "html",
value: '<span class="sidebar-divider" />',
},
{
type: "html",
className: "sidebar-title",
value: "Projects",
defaultStyle: true,
},
{
type: "category",
label: "Research",
link: { type: 'doc', id: 'research/index'},
items: [{type: 'autogenerated', dirName: 'research'}],
},
{
type: "category",
label: "Events",
link: {type: 'doc', id: 'events/index'},
items: [{type: 'autogenerated', dirName: 'events'}],
},
'projects/privacy-explorer',
/*{
type: "category",
label: "Privacy News",
link: {type: 'doc', id: 'news/week-in-the-privacy'},
items: [{type: 'autogenerated', dirName: 'news'}],
},*/
'news/week-in-the-privacy',
{
type: "category",
label: "Future concepts",
items: [
'projects/privacy-tech-awards',
],
},
{
type: "html",
value: '<span class="sidebar-divider" />',
},
{
type: "html",
className: "sidebar-title",
value: "Tools",
defaultStyle: true,
},
'git',
'communication',
'workgroups',
{
type: "html",
value: '<span class="sidebar-divider" />',
},
{
type: "html",
className: "sidebar-title",
value: "Community",
defaultStyle: true,
},
'follow-us',
'get-involved',
{
type: "category",
label: "Contributors Guide",
link: {type: 'doc', id: 'contributors/index'},
items: [
],
},
{
type: "category",
label: "Membership",
link: {type: 'doc', id: 'membership/index'},
items: [
'membership/personal-benefits',
'membership/org-benefits',
'membership/survival-kit',
],
},
'donate',
'code-of-conduct',
{
type: "html",
value: '<span class="sidebar-divider" />',
},
{
type: "html",
className: "sidebar-title",
value: "Organization",
defaultStyle: true,
},
{
type: "category",
label: "Governance",
link: {type: 'doc', id: 'governance'},
items: [
'congress',
{
type: "category",
label: "Core Team",
link: {type: 'doc', id: 'core-team/index'},
items: [
'core-team/multisig'
],
},
'association/index',
'guild',
],
},
'contacts',
/*{
type: "html",
value: '<span class="sidebar-divider" />',
},
{
type: "html",
className: "sidebar-title",
value: "Others",
defaultStyle: true,
},
'funding-requests',*/
],
};
export default sidebars;

View file

@ -1,64 +0,0 @@
import clsx from 'clsx';
import Heading from '@theme/Heading';
import styles from './styles.module.css';
const FeatureList = [
{
title: 'Easy to Use',
Svg: require('@site/static/img/undraw_docusaurus_mountain.svg').default,
description: (
<>
Docusaurus was designed from the ground up to be easily installed and
used to get your website up and running quickly.
</>
),
},
{
title: 'Focus on What Matters',
Svg: require('@site/static/img/undraw_docusaurus_tree.svg').default,
description: (
<>
Docusaurus lets you focus on your docs, and we&apos;ll do the chores. Go
ahead and move your docs into the <code>docs</code> directory.
</>
),
},
{
title: 'Powered by React',
Svg: require('@site/static/img/undraw_docusaurus_react.svg').default,
description: (
<>
Extend or customize your website layout by reusing React. Docusaurus can
be extended while reusing the same header and footer.
</>
),
},
];
function Feature({Svg, title, description}) {
return (
<div className={clsx('col col--4')}>
<div className="text--center">
<Svg className={styles.featureSvg} role="img" />
</div>
<div className="text--center padding-horiz--md">
<Heading as="h3">{title}</Heading>
<p>{description}</p>
</div>
</div>
);
}
export default function HomepageFeatures() {
return (
<section className={styles.features}>
<div className="container">
<div className="row">
{FeatureList.map((props, idx) => (
<Feature key={idx} {...props} />
))}
</div>
</div>
</section>
);
}

View file

@ -1,11 +0,0 @@
.features {
display: flex;
align-items: center;
padding: 2rem 0;
width: 100%;
}
.featureSvg {
height: 200px;
width: 200px;
}

6
src/content/config.ts Normal file
View file

@ -0,0 +1,6 @@
import { defineCollection } from 'astro:content';
import { docsSchema } from '@astrojs/starlight/schema';
export const collections = {
docs: defineCollection({ schema: docsSchema() }),
};

View file

Before

Width:  |  Height:  |  Size: 53 KiB

After

Width:  |  Height:  |  Size: 53 KiB

View file

Before

Width:  |  Height:  |  Size: 174 KiB

After

Width:  |  Height:  |  Size: 174 KiB

View file

Before

Width:  |  Height:  |  Size: 268 KiB

After

Width:  |  Height:  |  Size: 268 KiB

View file

Before

Width:  |  Height:  |  Size: 1.2 MiB

After

Width:  |  Height:  |  Size: 1.2 MiB

View file

Before

Width:  |  Height:  |  Size: 543 KiB

After

Width:  |  Height:  |  Size: 543 KiB

View file

Before

Width:  |  Height:  |  Size: 543 KiB

After

Width:  |  Height:  |  Size: 543 KiB

View file

Before

Width:  |  Height:  |  Size: 1.3 MiB

After

Width:  |  Height:  |  Size: 1.3 MiB

View file

Before

Width:  |  Height:  |  Size: 7.1 KiB

After

Width:  |  Height:  |  Size: 7.1 KiB

View file

Before

Width:  |  Height:  |  Size: 12 KiB

After

Width:  |  Height:  |  Size: 12 KiB

View file

Before

Width:  |  Height:  |  Size: 47 KiB

After

Width:  |  Height:  |  Size: 47 KiB

View file

Before

Width:  |  Height:  |  Size: 174 KiB

After

Width:  |  Height:  |  Size: 174 KiB

View file

Before

Width:  |  Height:  |  Size: 14 KiB

After

Width:  |  Height:  |  Size: 14 KiB

View file

Before

Width:  |  Height:  |  Size: 4.8 KiB

After

Width:  |  Height:  |  Size: 4.8 KiB

View file

Before

Width:  |  Height:  |  Size: 20 KiB

After

Width:  |  Height:  |  Size: 20 KiB

View file

Before

Width:  |  Height:  |  Size: 59 KiB

After

Width:  |  Height:  |  Size: 59 KiB

View file

Before

Width:  |  Height:  |  Size: 28 KiB

After

Width:  |  Height:  |  Size: 28 KiB

View file

Before

Width:  |  Height:  |  Size: 293 KiB

After

Width:  |  Height:  |  Size: 293 KiB

View file

Before

Width:  |  Height:  |  Size: 44 KiB

After

Width:  |  Height:  |  Size: 44 KiB

View file

Before

Width:  |  Height:  |  Size: 170 KiB

After

Width:  |  Height:  |  Size: 170 KiB

View file

Before

Width:  |  Height:  |  Size: 162 KiB

After

Width:  |  Height:  |  Size: 162 KiB

View file

Before

Width:  |  Height:  |  Size: 167 KiB

After

Width:  |  Height:  |  Size: 167 KiB

View file

@ -1,4 +1,6 @@
# Association ---
title: Association
---
:::note :::note

View file

@ -1,4 +1,6 @@
# Brand assets ---
title: Brand assets
---
:::note :::note

View file

@ -1,4 +1,6 @@
# Code of Conduct ---
title: Code of Conduct
---
We are a collective and we want to bring people in the community together to exchange ideas, make new friends, and build things as an inclusive, welcoming, and safe community. We are a collective and we want to bring people in the community together to exchange ideas, make new friends, and build things as an inclusive, welcoming, and safe community.

View file

@ -1,4 +1,6 @@
# Communication tools ---
title: Communication tools
---
We use different platforms for communication: We use different platforms for communication:

View file

@ -1,4 +1,6 @@
# Congress ---
title: Congress
---
The main governance body of the whole organisation, which decides on the most important issues by voting. The main governance body of the whole organisation, which decides on the most important issues by voting.

View file

@ -1,4 +1,7 @@
# Contact us ---
title: Contact us
---
For any questions or requests, please feel free to contact us at: For any questions or requests, please feel free to contact us at:
- 𝕏/Twitter: [@web3privacy](https://twitter.com/web3privacy) - 𝕏/Twitter: [@web3privacy](https://twitter.com/web3privacy)

View file

@ -1,4 +1,6 @@
# Contributors Guide ---
title: Contributors Guide
---
## Who is a contributor? ## Who is a contributor?

View file

@ -1,4 +1,6 @@
# Core Team ---
title: Core Team
---
The Core Team is the team of people who manage this initiative. The Core Team is the team of people who manage this initiative.

View file

@ -1,4 +1,6 @@
# Multisig wallet ---
title: Multisig wallet
---
## Deployments ## Deployments

View file

@ -1,4 +1,6 @@
# Donate ---
title: Donate
---
We persist in advocating for a development model reliant on voluntary contributions and donations. We persist in advocating for a development model reliant on voluntary contributions and donations.

View file

@ -1,9 +1,7 @@
--- ---
sidebar_position: 8 title: Follow us
--- ---
# Follow us
You can follow us on many different platforms: You can follow us on many different platforms:
## 🗨️ Social networks ## 🗨️ Social networks

View file

@ -1,9 +1,7 @@
--- ---
sidebar_position: 7 title: Get involved
--- ---
# Get involved
## _So you wish to be part of W3PN Ecosystem?? Lets make sure we are on the same page about what our work is all about._ ## _So you wish to be part of W3PN Ecosystem?? Lets make sure we are on the same page about what our work is all about._
Despite the foundational role that privacy is meant to play in shaping Web3, genuinely impactful initiatives remain scarce. Many projects leverage the concept of privacy as a buzzword or for public relations advantage, rather than addressing tangible issues or enacting substantial changes at the infrastructural and transactional level. Despite the foundational role that privacy is meant to play in shaping Web3, genuinely impactful initiatives remain scarce. Many projects leverage the concept of privacy as a buzzword or for public relations advantage, rather than addressing tangible issues or enacting substantial changes at the infrastructural and transactional level.

View file

@ -1,4 +1,6 @@
# Git repositories ---
title: Git repositories
---
All our projects are open-source and distributed across many Git repositories. Production repositories are hosted on [GitHub](https://github.com), under our [`@web3privacy`](https://github.com/web3privacy) organization. All our projects are open-source and distributed across many Git repositories. Production repositories are hosted on [GitHub](https://github.com), under our [`@web3privacy`](https://github.com/web3privacy) organization.

View file

@ -1,4 +1,6 @@
# Governance ---
title: Governance overview
---
In this section you will find a detailed description of how *Web3Privacy Now* governance works. In this section you will find a detailed description of how *Web3Privacy Now* governance works.

View file

@ -1,4 +1,6 @@
# Contributors Guild ---
title: Contributors Guild
---
A collective of *Web3Privacy Now* contributors receiving personal incentives. A collective of *Web3Privacy Now* contributors receiving personal incentives.

View file

@ -1,4 +1,6 @@
# History ---
title: History
---
Historical track record of *Web3Privacy Now*. Historical track record of *Web3Privacy Now*.

View file

@ -1,10 +1,8 @@
--- ---
sidebar_position: 1
slug: / slug: /
title: Introduction
--- ---
# Introduction
![Welcome to Web3Privacy Now Documentation](./assets/intro-cover.jpeg) ![Welcome to Web3Privacy Now Documentation](./assets/intro-cover.jpeg)
This documentation aims to provide a comprehensive overview of our motivations, activities, and the various ways in which you can contribute. This documentation aims to provide a comprehensive overview of our motivations, activities, and the various ways in which you can contribute.

View file

@ -1,9 +1,7 @@
--- ---
sidebar_position: 2 title: Manifesto
--- ---
# Manifesto
## Our Mission: Pioneering Privacy in the Web3 Era ## Our Mission: Pioneering Privacy in the Web3 Era
**Web3privacy Now** is a think-and-do-tank to foster knowledge and collaboration, produce insightful research and market reports, train builders, explore potential use-cases, and develop innovative privacy concepts and tools. **Web3privacy Now** is a think-and-do-tank to foster knowledge and collaboration, produce insightful research and market reports, train builders, explore potential use-cases, and develop innovative privacy concepts and tools.

View file

@ -1,4 +1,6 @@
# Membership ---
title: Membership
---
For all privacy enthusiasts, as well as projects and companies, we offer a simple and straightforward way for you to support us financially and become an integral part of our community with many benefits. For all privacy enthusiasts, as well as projects and companies, we offer a simple and straightforward way for you to support us financially and become an integral part of our community with many benefits.

View file

@ -1,4 +1,6 @@
# Benefits for Organizations ---
title: Benefits for Organizations
---
Here you will find a detailed description of the benefits of [membership for organisations](/membership#membership-for-organizations). Here you will find a detailed description of the benefits of [membership for organisations](/membership#membership-for-organizations).

View file

@ -1,4 +1,6 @@
# Personal benefits ---
title: Personal benefits
---
## Benefits: ## Benefits:

View file

@ -1,4 +1,6 @@
# Privacy Survival Kit ---
title: Privacy Survival Kit
---
A package of items for our [members](/membership) that they receive for free each year as a gift for their contribution. A package of items for our [members](/membership) that they receive for free each year as a gift for their contribution.

View file

@ -1,4 +1,6 @@
# Privacy Explorer ---
title: Privacy Explorer
---
**3in1**: a ranking system, database & comprehensive profiling to empower the general public in discerning the privacy levels, security, and reliability of Web3 projects. **3in1**: a ranking system, database & comprehensive profiling to empower the general public in discerning the privacy levels, security, and reliability of Web3 projects.

View file

@ -1,4 +1,6 @@
# Privacy Tech Awards ---
title: Privacy Tech Awards
---
:::note :::note

View file

@ -1,4 +1,6 @@
# Web3Privacy Now News ---
title: Web3Privacy Now News
---
News within the market is highly scattered. It's hard to keep track of the latest discussions, Twitter spaces, product releases & major updates. W3PN wants to facilitate privacy x web3-related newsletter build by the community. News within the market is highly scattered. It's hard to keep track of the latest discussions, Twitter spaces, product releases & major updates. W3PN wants to facilitate privacy x web3-related newsletter build by the community.

View file

@ -1,10 +1,7 @@
--- ---
sidebar_label: Research Introduction title: Research
sidebar_position: 0
--- ---
# Research
W3PN research branch fills the gap within the market knowledge + makes data free & public forever (not locked within web3 analytical services). W3PN research branch fills the gap within the market knowledge + makes data free & public forever (not locked within web3 analytical services).
**Areas of interest** **Areas of interest**

View file

@ -1,4 +1,6 @@
# Roadmap ---
title: Roadmap
---
Here you can find a high-level overview of what we are planning for the future. Here you can find a high-level overview of what we are planning for the future.

View file

@ -1,4 +1,6 @@
# Workgroups ---
title: Workgroups
---
All our activities are divided into many *working groups*. Internal working groups take care of the basic needs of the whole organization and serve as a key support for the teams of individual specific projects. All our activities are divided into many *working groups*. Internal working groups take care of the basic needs of the whole organization and serve as a key support for the teams of individual specific projects.

View file

@ -1,61 +0,0 @@
/**
* Any CSS included here will be global. The classic template
* bundles Infima by default. Infima is a CSS framework designed to
* work well for content-centric websites.
*/
/* You can override the default Infima variables here. */
:root {
--ifm-color-primary: black;
--ifm-color-primary-dark: #29784c;
--ifm-color-primary-darker: #277148;
--ifm-color-primary-darkest: #205d3b;
--ifm-color-primary-light: #33925d;
--ifm-color-primary-lighter: #359962;
--ifm-color-primary-lightest: #3cad6e;
--ifm-code-font-size: 95%;
--docusaurus-highlighted-code-line-bg: rgba(0, 0, 0, 0.1);
}
/* For readability concerns, you should choose a lighter palette in dark mode. */
[data-theme='dark'] {
--ifm-color-primary: #ffffff;
--ifm-color-primary-dark: #e6e6e6;
--ifm-color-primary-darker: #d9d9d9;
--ifm-color-primary-darkest: #b3b3b3;
--ifm-color-primary-light: #ffffff;
--ifm-color-primary-lighter: #ffffff;
--ifm-color-primary-lightest: #ffffff;
--search-local-highlight-color: #000000;
}
.sidebar-divider {
border-top: 1px solid var(--ifm-color-gray-200);
display: block;
margin: 0.5rem 0 0.25rem 1rem;
}
html[data-theme='dark'] .sidebar-divider {
border-top: 1px solid var(--ifm-color-gray-800);
}
.theme-doc-markdown.markdown a {
text-decoration: underline;
}
.theme-doc-markdown.markdown a:hover {
text-decoration: none;
}
.sidebar-title {
font-size: 0.8rem;
letter-spacing: 0.05rem;
text-transform: uppercase;
font-weight: 600;
color: var(--ifm-color-gray-600);
}
html[data-theme='dark'] .sidebar-divider {
color: var(--ifm-color-gray-200);
}

2
src/env.d.ts vendored Normal file
View file

@ -0,0 +1,2 @@
/// <reference path="../.astro/types.d.ts" />
/// <reference types="astro/client" />

View file

@ -1,23 +0,0 @@
/**
* CSS files with the .module.css suffix will be treated as CSS modules
* and scoped locally.
*/
.heroBanner {
padding: 4rem 0;
text-align: center;
position: relative;
overflow: hidden;
}
@media screen and (max-width: 996px) {
.heroBanner {
padding: 2rem;
}
}
.buttons {
display: flex;
align-items: center;
justify-content: center;
}

View file

@ -1,7 +0,0 @@
---
title: Markdown page example
---
# Markdown page example
You don't need React to write simple standalone pages.

View file

View file

@ -1 +0,0 @@
docs.web3privacy.info

Some files were not shown because too many files have changed in this diff Show more