Skip to content

Commit

Permalink
website: updates
Browse files Browse the repository at this point in the history
ilg-ul committed Dec 4, 2024
1 parent 3f5a7ca commit 4480e0d
Showing 30 changed files with 85 additions and 48 deletions.
2 changes: 2 additions & 0 deletions website/blog/2020-09-28-ninja-build-v1-10-0-1-released.mdx
Original file line number Diff line number Diff line change
@@ -28,6 +28,8 @@ import {PageMetadata} from '@docusaurus/theme-common';
import Image from '@theme/IdealImage';
import CodeBlock from '@theme/CodeBlock';

{/* ------------------------------------------------------------------------ */}

Version **1.10.0-1** is the first release of the **xPack Ninja Build** package.

<!-- truncate -->
2 changes: 2 additions & 0 deletions website/blog/2020-09-28-ninja-build-v1-10-1-1-released.mdx
Original file line number Diff line number Diff line change
@@ -28,6 +28,8 @@ import {PageMetadata} from '@docusaurus/theme-common';
import Image from '@theme/IdealImage';
import CodeBlock from '@theme/CodeBlock';

{/* ------------------------------------------------------------------------ */}

Version **1.10.1-1** is a new release of the **xPack Ninja Build** package.

<!-- truncate -->
2 changes: 2 additions & 0 deletions website/blog/2020-12-19-ninja-build-v1-10-2-1-released.mdx
Original file line number Diff line number Diff line change
@@ -28,6 +28,8 @@ import {PageMetadata} from '@docusaurus/theme-common';
import Image from '@theme/IdealImage';
import CodeBlock from '@theme/CodeBlock';

{/* ------------------------------------------------------------------------ */}

Version **1.10.2-1** is a new release of the **xPack Ninja Build** package.

<!-- truncate -->
2 changes: 2 additions & 0 deletions website/blog/2021-03-16-ninja-build-v1-10-2-2-released.mdx
Original file line number Diff line number Diff line change
@@ -28,6 +28,8 @@ import {PageMetadata} from '@docusaurus/theme-common';
import Image from '@theme/IdealImage';
import CodeBlock from '@theme/CodeBlock';

{/* ------------------------------------------------------------------------ */}

Version **1.10.2-2** is a maintenance release of the **xPack Ninja Build** package, fixing the spawning of cmd.exe scripts on Windows.

<!-- truncate -->
2 changes: 2 additions & 0 deletions website/blog/2021-04-28-ninja-build-v1-10-2-3-released.mdx
Original file line number Diff line number Diff line change
@@ -28,6 +28,8 @@ import {PageMetadata} from '@docusaurus/theme-common';
import Image from '@theme/IdealImage';
import CodeBlock from '@theme/CodeBlock';

{/* ------------------------------------------------------------------------ */}

Version **1.10.2-3** is a maintenance release of the **xPack Ninja Build** package, fixing the spawning of cmd.exe scripts on Windows.

<!-- truncate -->
2 changes: 2 additions & 0 deletions website/blog/2021-10-19-ninja-build-v1-10-2-4-released.mdx
Original file line number Diff line number Diff line change
@@ -28,6 +28,8 @@ import {PageMetadata} from '@docusaurus/theme-common';
import Image from '@theme/IdealImage';
import CodeBlock from '@theme/CodeBlock';

{/* ------------------------------------------------------------------------ */}

Version **1.10.2-4** is a maintenance release; it is a rebuild with the latest build environment.

<!-- truncate -->
2 changes: 2 additions & 0 deletions website/blog/2021-12-06-ninja-build-v1-10-2-5-released.mdx
Original file line number Diff line number Diff line change
@@ -28,6 +28,8 @@ import {PageMetadata} from '@docusaurus/theme-common';
import Image from '@theme/IdealImage';
import CodeBlock from '@theme/CodeBlock';

{/* ------------------------------------------------------------------------ */}

Version **1.10.2-5** is a maintenance release; it **adds support for Apple Silicon** and uses the latest build scripts.

<!-- truncate -->
2 changes: 2 additions & 0 deletions website/blog/2022-05-17-ninja-build-v1-11-0-1-released.mdx
Original file line number Diff line number Diff line change
@@ -30,6 +30,8 @@ import {PageMetadata} from '@docusaurus/theme-common';
import Image from '@theme/IdealImage';
import CodeBlock from '@theme/CodeBlock';

{/* ------------------------------------------------------------------------ */}

Version **1.11.0-1** is a new release; it follows the upstream release.

<!-- truncate -->
2 changes: 2 additions & 0 deletions website/blog/2022-08-31-ninja-build-v1-11-1-1-released.mdx
Original file line number Diff line number Diff line change
@@ -30,6 +30,8 @@ import {PageMetadata} from '@docusaurus/theme-common';
import Image from '@theme/IdealImage';
import CodeBlock from '@theme/CodeBlock';

{/* ------------------------------------------------------------------------ */}

Version **1.11.1-1** is a new release; it follows the upstream release.

<!-- truncate -->
2 changes: 2 additions & 0 deletions website/blog/2023-01-23-ninja-build-v1-11-1-2-released.mdx
Original file line number Diff line number Diff line change
@@ -30,6 +30,8 @@ import {PageMetadata} from '@docusaurus/theme-common';
import Image from '@theme/IdealImage';
import CodeBlock from '@theme/CodeBlock';

{/* ------------------------------------------------------------------------ */}

Version **1.11.1-2** is a maintenance release, built with the latest build scripts.

<!-- truncate -->
2 changes: 2 additions & 0 deletions website/blog/2023-09-05-ninja-build-v1-11-1-3-released.mdx
Original file line number Diff line number Diff line change
@@ -31,6 +31,8 @@ import {PageMetadata} from '@docusaurus/theme-common';
import Image from '@theme/IdealImage';
import CodeBlock from '@theme/CodeBlock';

{/* ------------------------------------------------------------------------ */}

Version **1.11.1-3** is a maintenance release, built with the lates tools.

<!-- truncate -->
4 changes: 2 additions & 2 deletions website/docs/about/_common/_history-xbb-v5.mdx
Original file line number Diff line number Diff line change
@@ -5,9 +5,9 @@

The project received a significant update by transitioning the build
scripts from the cumbersome monolithic XBB Docker images to the more
flexible and modular xPacks. XBB version
flexible and modular **xpm** packages. XBB version
[5.0.0](https://xpack.github.io/blog/2023/02/07/xbb-v5.0.0-released/)
marked a major milestone for the xPack project, as it was the first
self-sustained release. This version enabled the creation of new
binary xPacks using existing binary xPacks, eliminating the need for
binary packages using existing binary packages, eliminating the need for
custom Docker images or other compiled tools.
Original file line number Diff line number Diff line change
@@ -3,7 +3,7 @@

{/* ------------------------------------------------------------------------ */}

In **{props.date}** the website content was added in the `website` folder,
In **{props.date || 'DATE'}** the website content was added in the `website` folder,
as an instance of the Docusaurus template. Additionally a GitHub Action
was added to automatically publish the site upon any pushes to the
`website` Git branch.
Original file line number Diff line number Diff line change
@@ -45,7 +45,7 @@ or, for more verbosity, run the similar development build:

{developmentDurations[ props.platform ]}, the output of the build script is a compressed
archive and its SHA signature, created in
the <code>buils-assets/build/{props.platform}/deploy</code> folder:
the <code>build-assets/build/{props.platform}/deploy</code> folder:

* <code>xpack-ninja-build-{customField('xpackVersion')}-{props.platform}.tar.gz</code>
* <code>xpack-ninja-build-{customField('xpackVersion')}-{props.platform}.tar.gz.sha</code>
Original file line number Diff line number Diff line change
@@ -42,7 +42,7 @@ or, for more verbosity, run the similar development build:

{developmentDurations[ props.platform ]}, the output of the build script is a compressed
archive and its SHA signature, created in
the <code>buils-assets/build/{props.platform}/deploy</code> folder:
the <code>build-assets/build/{props.platform}/deploy</code> folder:

* <code>xpack-ninja-build-{customField('xpackVersion')}-{props.platform}.tar.gz</code>
* <code>xpack-ninja-build-{customField('xpackVersion')}-{props.platform}.tar.gz.sha</code>
18 changes: 9 additions & 9 deletions website/docs/developer/index.mdx
Original file line number Diff line number Diff line change
@@ -33,17 +33,17 @@ import More from './_more.mdx'

[![license](https://img.shields.io/github/license/xpack-dev-tools/ninja-build-xpack)](https://github.com/xpack-dev-tools/ninja-build-xpack/blob/xpack/LICENSE)

This page is intended for those who want to build the
This page is designed for developers of the
**xPack Ninja Build**
binaries themselves.
project and provides documentation on how to build and test the package.

<details>
<summary>The xPack Build Box</summary>

The build scripts in this project use the **xPack Build Box** (**XBB**)
tools, which require the usual native development tools
(packed as a Docker image for GNU/Linux builds), complemented with
several binary xPacks, installed with `xpm` as development dependencies.
several binary packages, installed with `xpm` as development dependencies.

For those interested in understanding how things work, a good starting point
would be to read the [XBB](https://xpack.github.io/xbb/) page.
@@ -144,17 +144,17 @@ xpm run build --config darwin-x64
</details>

<details>
<summary>xPack actions</summary>
<summary>xpm/xPack actions</summary>

The xPack actions are extensions of npm scripts, i.e. named sequences
The xpm actions are extensions of npm scripts, i.e. named sequences
of commands that are invoked via `xpm run <name>` to perform specific
operations.
together in a sub-shell .

The commands are invoked in a sub-shell with an adjusted PATH,
having the `xpacks/.bin`
folder prepended. This ensures the locally installed tools are
prefered to the system tools.
preferred to the system tools.

Actions can be defined for the entire project or for a specific build
configuration.
@@ -177,10 +177,10 @@ commands.
<details>
<summary>Visual Studio Code integration</summary>

xPack actions and build configurations are supported in Visual Studio via the
xpm/xPack actions and build configurations are supported in Visual Studio via the
[xPack C/C++ Managed Build Tools](https://marketplace.visualstudio.com/items?itemName=ilg-vscode.xpack) extension.

With this extension installed, xPack actions can be very conveniently
With this extension installed, xpm/xPack actions can be very conveniently
invoked via a single mouse click, for example:

![xPack actions](https://github.com/xpack/vscode-xpack-extension-ts/raw/master/assets/docs-images/xpack-actions.png)
@@ -328,7 +328,7 @@ In some cases it is necessary to run a debug session with the binaries.

For these cases, the build script accepts the `--debug` options.

There are also xPack actions that use this option (`build-development-debug`
There are also xpm actions that use this option (`build-development-debug`
and `docker-build-development-debug`).

### Use a local cache
12 changes: 6 additions & 6 deletions website/docs/getting-started/index.mdx
Original file line number Diff line number Diff line change
@@ -95,20 +95,20 @@ same repositories as **npm**, whether public or private.
The packages (usually regular archives, but also git repositories),
are extracted into separate folders within the project.

Based on the content, there are two types of packets:
Based on the content, there are two types of packages:

- **source xPacks** (that install source files, usually libraries) and
- **binary xPacks** (that install executables/binary files, usually tools).
- **source packages** (that install source files, usually libraries) and
- **binary packages** (that install executables/binary files, usually tools).

The binary xPacks include references to archives with the platform specific
Binary packages include references to archives with the platform specific
binaries (such as `.tar.gz` for Unix or `.zip` for Windows).

These archives are also expanded along the package metadata. Since they
include executables, links/forwarders to
these executables are created in a `.bin` folder,
eliminating the need to add multiple folders to the `PATH`.

Given that some binary xPacks, such as toolchains, can have very large
Given that some binary packages, such as toolchains, can have very large
archives, the packages are extracted only once into a user global location to
conserve space. In projects, instead of duplicating the content of these
archives, symbolic links are created.
@@ -139,7 +139,7 @@ feasible.
</details>

Similarly to [flatpacks](https://flatpak.org) or [snap](https://snapcraft.io),
but significantly simpler, xPacks include all dependent shared libraries
but significantly simpler, xpm packages include all dependent shared libraries
within the distributed archives, making the binaries independent of
any similar libraries installed on the system. This ensures they
can run on any system without needing specific libraries to be
7 changes: 4 additions & 3 deletions website/docs/install/index.mdx
Original file line number Diff line number Diff line change
@@ -69,7 +69,8 @@ They use **the same format as npm packages**,
which is a collection of files/folders
and a `package.json` file with the package metadata.

Binary xPacks also include references to regular archives with the platform
**xpm** can install source and binary packages.
Binary xPacks include references to regular archives with the platform
specific binaries (such as `.tar.gz` for Unix or `.zip` for Windows).
These archives are unpacked and links/forwarders to
the executables are created in a `.bin` folder.
@@ -155,8 +156,8 @@ Similarly, **xpm** adds links/forwarders into
a separate `<project>/xpacks/.bin` folder.

With this setup, the project needs to prepend only this `.bin` folder
to the `PATH`, and all the required tools are accesible
and prefered to possible system tools.
to the `PATH`, and all the required tools are accessible
and preferred to possible system tools.

</details>

4 changes: 2 additions & 2 deletions website/docs/maintainer/_common/_platform-docker-build.mdx
Original file line number Diff line number Diff line change
@@ -18,7 +18,7 @@ xpm run check-space -C ~/Work/xpack-dev-tools/ninja-build-xpack.git/build-assets
To free the space used by all previous builds of all `xpack-dev-tools` packages:

```sh
xpm run clear-all-project-builds -C ~/Work/xpack-dev-tools/ninja-build-xpack.git/build-assets
xpm run clear-all-projects-builds -C ~/Work/xpack-dev-tools/ninja-build-xpack.git/build-assets
```

To update the build scripts and build the development binaries:
@@ -39,7 +39,7 @@ xpm run docker-build-development --config ${props.platform} -C ~/Work/xpack-dev-

{developmentDurations[ props.platform ]}, the output of the build script is a compressed
archive and its SHA signature, created in
the <code>buils-assets/build/{props.platform}/deploy</code> folder:
the <code>build-assets/build/{props.platform}/deploy</code> folder:

* <code>xpack-ninja-build-{customField('xpackVersion')}-{props.platform}.{props.platform === 'win32-x64' ? 'zip' : 'tar.gz'}</code>
* <code>xpack-ninja-build-{customField('xpackVersion')}-{props.platform}.{props.platform === 'win32-x64' ? 'zip' : 'tar.gz'}.sha</code>
4 changes: 2 additions & 2 deletions website/docs/maintainer/_common/_platform-native-build.mdx
Original file line number Diff line number Diff line change
@@ -18,7 +18,7 @@ xpm run check-space -C ~/Work/xpack-dev-tools/ninja-build-xpack.git/build-assets
To free the space used by all previous builds of all `xpack-dev-tools` packages:

```sh
xpm run clear-all-project-builds -C ~/Work/xpack-dev-tools/ninja-build-xpack.git/build-assets
xpm run clear-all-projects-builds -C ~/Work/xpack-dev-tools/ninja-build-xpack.git/build-assets
```

To update the build scripts and build the development binaries:
@@ -38,7 +38,7 @@ xpm run build-development --config ${props.platform} -C ~/Work/xpack-dev-tools/n

{developmentDurations[ props.platform ]}, the output of the build script is a compressed
archive and its SHA signature, created in
the <code>buils-assets/build/{props.platform}/deploy</code> folder:
the <code>build-assets/build/{props.platform}/deploy</code> folder:

* <code>xpack-ninja-build-{customField('xpackVersion')}-{props.platform}.tar.gz</code>
* <code>xpack-ninja-build-{customField('xpackVersion')}-{props.platform}.tar.gz.sha</code>
27 changes: 16 additions & 11 deletions website/docs/maintainer/index.mdx
Original file line number Diff line number Diff line change
@@ -48,9 +48,9 @@ import PlatformDockerBuild from './_common/_platform-docker-build.mdx'
[![GitHub issues](https://img.shields.io/github/issues/xpack-dev-tools/ninja-build-xpack.svg)](https://github.com/xpack-dev-tools/ninja-build-xpack/issues/)
[![GitHub pulls](https://img.shields.io/github/issues-pr/xpack-dev-tools/ninja-build-xpack.svg)](https://github.com/xpack-dev-tools/ninja-build-xpack/pulls)

This page is intended for those who maintain the
This page is designed for maintainers of the
**xPack Ninja Build**
project and documents how to make new releases.
project and provides documentation on how to create new releases.

## Prerequisites

@@ -141,6 +141,7 @@ In the `xpack-dev-tools/ninja-build-xpack` Git repo:

- switch to the `xpack-development` branch
- pull new changes
- if necessary, merge the `xpack` branch
- if necessary, merge the `website` branch

:::caution
@@ -179,7 +180,7 @@ or run the following in a terminal:
```

Navigate to the **Maintainer Info** page,
the **Update the version specific code** section.
the **Increase the version and update VERSION** section.

### Increase the version and update VERSION

@@ -205,7 +206,8 @@ If the project uses `customFields` in `build-assets/package.json`

Check GitHub issues and pull requests:

- https://github.com/xpack-dev-tools/ninja-build-xpack/issues/
- https://github.com/xpack-dev-tools/ninja-build-xpack/issues
- https://github.com/xpack-dev-tools/ninja-build-xpack/pulls

and fix them; assign them to a milestone (like <code>{customField('xpackVersion')}</code>).

@@ -270,7 +272,7 @@ Before the real build, run test/development builds on all platforms.

### Visual Studio Code extension

All actions are defined as **xPack actions** and can be conveniently
All actions are defined as **xpm/xPack actions** and can be conveniently
triggered via the VS Code graphical interface, using the
[xPack C/C++ Managed Build Tools extension](https://marketplace.visualstudio.com/items?itemName=ilg-vscode.xpack).

@@ -441,7 +443,7 @@ In some cases it is necessary to run a debug session with the binaries.

For these cases, the build script accepts the `--debug` options.

There are also xPack actions that use this option (`build-development-debug`
There are also xpm actions that use this option (`build-development-debug`
and `docker-build-development-debug`).

### Files cache
@@ -560,7 +562,7 @@ df -BG -H /
To free the space used by all previous builds of all `xpack-dev-tools` packages:

```sh
xpm run clear-all-project-builds -C ~/Work/xpack-dev-tools/ninja-build-xpack.git/build-assets
xpm run clear-all-projects-builds -C ~/Work/xpack-dev-tools/ninja-build-xpack.git/build-assets
```

This is equivalent to running a wide `rm` to remove the `build` folders:
@@ -587,7 +589,7 @@ xpm run generate-workflows -C ~/Work/xpack-dev-tools/ninja-build-xpack.git/build

### Manually trigger the build GitHub Actions

To trigger the GitHub Actions builds, use the xPack actions:
To trigger the GitHub Actions builds, use the xpm actions:

- **trigger-workflow-build-darwin-x64**
- **trigger-workflow-build-darwin-arm64**
@@ -606,7 +608,7 @@ xpm run trigger-workflow-build-linux-arm64 -C ~/Work/xpack-dev-tools/ninja-build
xpm run trigger-workflow-build-linux-arm -C ~/Work/xpack-dev-tools/ninja-build-xpack.git/build-assets
```

The scripts behind these actions require the `GITHUB_API_DISPATCH_TOKEN`
The scripts behind these actions require the `XPACK_DEV_TOOLS_FG_DISPATCH_TOKEN`
variable to be present
in the environment, and the organization `PUBLISH_TOKEN` to be visible in the
SettingsAction
@@ -634,7 +636,7 @@ The resulting binaries are available for testing from

The automation is provided by GitHub Actions.

To trigger the GitHub Actions tests, run the xPack actions:
To trigger the GitHub Actions tests, run the xpm actions:

<ul>
<li><b>trigger-workflow-test-prime</b></li>
@@ -648,7 +650,7 @@ xpm run trigger-workflow-test-docker-linux-x64 -C ~/Work/xpack-dev-tools/ninja-b
xpm run trigger-workflow-test-docker-linux-arm -C ~/Work/xpack-dev-tools/ninja-build-xpack.git/build-assets
```

The scripts behind these accesible require the `GITHUB_API_DISPATCH_TOKEN` variable to be present
The scripts behind these accessible require the `XPACK_DEV_TOOLS_FG_DISPATCH_TOKEN` variable to be present
in the environment.

These actions use the `xpack-development` branch of this repo and the
@@ -870,6 +872,9 @@ version in `package.json` is not changed.

### Update the `xpack` branch

In this Git repo:

- select the `xpack` branch
- merge `xpack-development` into `xpack`
- push the `xpack` branch to GitHub

2 changes: 1 addition & 1 deletion website/docs/user/_common/_arm-toolchain-versioning.mdx
Original file line number Diff line number Diff line change
@@ -18,7 +18,7 @@ import versionMinor from '@site/src/libs/versionMinor';
The version string used by the
upstream **Arm GNU Toolchain** project is a bit unusual and unstable in time,
(like <code>{versionMajor()}.{versionMinor()}.Rel1</code>)
therefore the upstream GCC version is prefered, which
therefore the upstream GCC version is preferred, which
is a three number string
like <code>{customField('xpackVersion')}</code>;
to this string the xPack distribution adds a fourth number that represents
2 changes: 1 addition & 1 deletion website/docs/user/_common/_libraries-and-rpath.mdx
Original file line number Diff line number Diff line change
@@ -5,7 +5,7 @@

## Shared libraries

On all platforms the binary xPack packages are **standalone**,
On all platforms the binary xpm packages are **standalone**,
and expect only the standard runtime to be present on the host.

All dependencies that are built as shared libraries are copied locally
8 changes: 2 additions & 6 deletions website/docusaurus.config.ts
Original file line number Diff line number Diff line change
@@ -15,8 +15,6 @@ import {fileURLToPath} from 'node:url';
import path from 'node:path';
import fs from 'node:fs';



// ----------------------------------------------------------------------------

function getCustomFields() {
@@ -85,8 +83,6 @@ function getCustomFields() {
const customFields = getCustomFields();
logger.info(customFields);



// ----------------------------------------------------------------------------

const config: Config = {
@@ -139,7 +135,7 @@ const config: Config = {
// Please change this to your repo.
// Remove this to remove the "edit this page" links.
editUrl:
'https://github.com/facebook/docusaurus/tree/main/packages/create-docusaurus/templates/shared/',
'https://github.com/xpack-dev-tools/ninja-build-xpack/edit/xpack/website/',
showLastUpdateTime: true,
blogSidebarCount: 8,
authorsMapPath: '../authors.yml',
@@ -295,7 +291,7 @@ const config: Config = {
metadata: [
{
name: 'keywords',
content: 'xpack, binary, development, tools, ninja-build'
content: 'xpack, binary, development, tools, reproducibility, ninja-build'
}
],
navbar: {
2 changes: 2 additions & 0 deletions website/sidebars.ts
Original file line number Diff line number Diff line change
@@ -3,6 +3,8 @@

import type {SidebarsConfig} from '@docusaurus/plugin-content-docs';



/**
* Creating a sidebar enables you to:
- create an ordered group of docs
6 changes: 5 additions & 1 deletion website/src/components/HomepageFeatures/styles.module.css
Original file line number Diff line number Diff line change
@@ -6,7 +6,7 @@
.features {
display: flex;
align-items: center;
padding: 2rem 0 0.5rem 0;
padding: 2rem 0 0.5rem 0; /* 2rem 0; */
width: 100%;
}

@@ -15,6 +15,10 @@
width: 100px;
}

/* ------------------------------------------------------------------------- */

svg.featureSvg path {
stroke: var(--docusaurus-svg-color);
}

/* ------------------------------------------------------------------------- */
4 changes: 4 additions & 0 deletions website/src/css/custom.css
Original file line number Diff line number Diff line change
@@ -34,6 +34,8 @@
--docusaurus-svg-color: #CDCDCD;
}

/* ------------------------------------------------------------------------- */

/* For the home page xpm install field */
p.hero__code code {
color: var(--ifm-font-color-base)
@@ -115,3 +117,5 @@ img.mac-stadium-img {
float: right;
width: 200px;
}

/* ------------------------------------------------------------------------- */
2 changes: 1 addition & 1 deletion website/src/pages/index.module.css
Original file line number Diff line number Diff line change
@@ -6,7 +6,7 @@
* and scoped locally.
*/

.heroBanner {
.heroBanner {
padding: 2rem 0; /* 4rem 0; */
text-align: center;
position: relative;
3 changes: 3 additions & 0 deletions website/src/pages/index.tsx
Original file line number Diff line number Diff line change
@@ -16,15 +16,18 @@ import React from 'react';
import clsx from 'clsx';
import useDocusaurusContext from '@docusaurus/useDocusaurusContext';
import Layout from '@theme/Layout';
import HeadTitle from '@site/src/components/HeadTitle';

import styles from './index.module.css';
import HomepageFeatures from '@site/src/components/HomepageFeatures';

import InstallWithCopy from '@site/src/components/InstallWithCopy';

function HomepageHeader() {
const {siteConfig} = useDocusaurusContext();
return (
<header className={clsx('hero hero--primary', styles.heroBanner)}>
<HeadTitle title="Welcome to the xPack Ninja Build!" />
<div className="container">
<h1 className="hero__title">{siteConfig.title}</h1>
<p className="hero__subtitle">{siteConfig.tagline}</p>
Binary file modified website/static/img/favicon.ico
Binary file not shown.

0 comments on commit 4480e0d

Please sign in to comment.