Go to file
ksr cb51856b5a format fix
Signed-off-by: ksr <kaiserd@users.noreply.github.com>
2023-09-01 17:27:31 +02:00
.github remove vercel actions 2023-03-17 12:22:59 +01:00
.husky Migrate to Docusaurus (#108) 2023-06-07 22:12:28 +01:00
docs docs: update terms 2023-08-31 20:28:04 +09:00
rlog format fix 2023-09-01 17:27:31 +02:00
src new URL structure for root pages and research posts, refs #115 2023-06-14 22:49:18 +03:30
static/img Migrate to Docusaurus (#108) 2023-06-07 22:12:28 +01:00
.gitignore Migrate to Docusaurus (#108) 2023-06-07 22:12:28 +01:00
.prettierignore Migrate to Docusaurus (#108) 2023-06-07 22:12:28 +01:00
.prettierrc Migrate to Docusaurus (#108) 2023-06-07 22:12:28 +01:00
Jenkinsfile Migrate to Docusaurus (#108) 2023-06-07 22:12:28 +01:00
README.md add deployment process back to README 2023-07-10 18:31:08 +02:00
babel.config.js Migrate to Docusaurus (#108) 2023-06-07 22:12:28 +01:00
docusaurus.config.js fix: redirect /research to /rlog 2023-07-18 09:43:47 +03:30
package.json docs: update terms and preset version 2023-08-03 22:47:24 +09:00
tsconfig.json Migrate to Docusaurus (#108) 2023-06-07 22:12:28 +01:00
yarn.lock docs: update terms and preset version 2023-08-03 22:47:24 +09:00

README.md

Description

This repository contains the content of your documentation website.

How to Run Locally

  1. Clone this repository.
  2. Install the dependencies:
$ yarn
  1. Start and open the website in your browser:
$ yarn start

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

Example:

presets: [
  [
    '@acid-info/logos-docusaurus-preset',
    {
      businessUnit: 'Codex',
    },
  ],
],

This is probably enough in most cases, as the Logos plugins will fill in other configurations related to the specified business unit. If you find any error in the information coming from Logos Plugins, please head over to Logos Docusaurus Plugins and create an issue.

Customization

You can find the instructions on adding more documentation sections, localization, and versioning on the Docusaurus website.

Note that theme customization is limited; for further instructions on customizing your theme, head over to Logos Docusaurus Theme.

Continuous Deloyment

Change Process

  1. Create a new working branch from develop: git checkout develop; git checkout -b my-changes;
  2. Proceed with changes, push to origin and open a Pull Request against develop;
  3. Once approved, merge pull request, check changes on dev.vac.dev;
  4. Once ready to promote to live website, rebase master on staging: git checkout master; git pull master; git rebase origin/develop; git push.