website: updates

Author: ilg-ul

website/docs/about/_common/_history-xbb-v5.mdx

@@ -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.

website/docs/about/_common/_website-docusaurus-template.mdx

@@ -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.

website/docs/getting-started/index.mdx

@@ -84,20 +84,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.
@@ -128,7 +128,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

website/src/pages/index.tsx

@@ -16,16 +16,20 @@ 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 HomepageTools from '@site/src/components/HomepageTools';
+
 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 Binary Development Tools!" />
       <div className="container">
         <h1 className="hero__title">{siteConfig.title}</h1>
         <p className="hero__subtitle">{siteConfig.tagline}</p>

website/tools.ts

@@ -10,7 +10,6 @@
  */
 
 const tools = {
-    /* When updated, don't forget to add sitemap to robots.txt! */
     mainTools: [
         {
             appName: 'GNU AArch64 Embedded GCC',