diff --git a/.github/workflows/docker-build.yml b/.github/workflows/docker-build.yml index 3f777977..9678f0b2 100644 --- a/.github/workflows/docker-build.yml +++ b/.github/workflows/docker-build.yml @@ -1,28 +1,28 @@ -name: Docker CI build - -on: - push: - branches: ['main'] - pull_request: - branches: ['main'] - -jobs: - build: - runs-on: ubuntu-latest - steps: - - name: Checkout repository - uses: actions/checkout@v4 - - - name: Set up QEMU - uses: docker/setup-qemu-action@v3 - - - name: Set up Docker Buildx - uses: docker/setup-buildx-action@v3 - - - name: Build and push Docker image - id: build-and-push - uses: docker/build-push-action@v6 - with: - context: . - platforms: linux/amd64,linux/arm64 - push: false +name: Docker CI build + +on: + push: + branches: ['main'] + pull_request: + branches: ['main'] + +jobs: + build: + runs-on: ubuntu-latest + steps: + - name: Checkout repository + uses: actions/checkout@v4 + + - name: Set up QEMU + uses: docker/setup-qemu-action@v3 + + - name: Set up Docker Buildx + uses: docker/setup-buildx-action@v3 + + - name: Build and push Docker image + id: build-and-push + uses: docker/build-push-action@v6 + with: + context: . + platforms: linux/amd64,linux/arm64 + push: false diff --git a/.github/workflows/docker-publish.yml b/.github/workflows/docker-publish.yml index e6068d17..3a0b1329 100644 --- a/.github/workflows/docker-publish.yml +++ b/.github/workflows/docker-publish.yml @@ -1,50 +1,50 @@ -name: Docker build and publish - -on: - release: - types: - - published - -env: - REGISTRY: ghcr.io - IMAGE_NAME: ${{ github.repository }} - -jobs: - build: - runs-on: ubuntu-latest - permissions: - contents: read - packages: write - - steps: - - name: Checkout repository - uses: actions/checkout@v4 - - - name: Set up QEMU - uses: docker/setup-qemu-action@v3 - - - name: Set up Docker Buildx - uses: docker/setup-buildx-action@v3 - - - name: Log into registry ${{ env.REGISTRY }} - uses: docker/login-action@v3 - with: - registry: ${{ env.REGISTRY }} - username: ${{ github.actor }} - password: ${{ secrets.GITHUB_TOKEN }} - - - name: Extract metadata (tags, labels) for Docker - id: meta - uses: docker/metadata-action@v5 - with: - images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }} - - - name: Build and push Docker image - id: build-and-push - uses: docker/build-push-action@v6 - with: - context: . - platforms: linux/amd64,linux/arm64 - push: true - tags: ${{ steps.meta.outputs.tags }} - labels: ${{ steps.meta.outputs.labels }} +name: Docker build and publish + +on: + release: + types: + - published + +env: + REGISTRY: ghcr.io + IMAGE_NAME: ${{ github.repository }} + +jobs: + build: + runs-on: ubuntu-latest + permissions: + contents: read + packages: write + + steps: + - name: Checkout repository + uses: actions/checkout@v4 + + - name: Set up QEMU + uses: docker/setup-qemu-action@v3 + + - name: Set up Docker Buildx + uses: docker/setup-buildx-action@v3 + + - name: Log into registry ${{ env.REGISTRY }} + uses: docker/login-action@v3 + with: + registry: ${{ env.REGISTRY }} + username: ${{ github.actor }} + password: ${{ secrets.GITHUB_TOKEN }} + + - name: Extract metadata (tags, labels) for Docker + id: meta + uses: docker/metadata-action@v5 + with: + images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }} + + - name: Build and push Docker image + id: build-and-push + uses: docker/build-push-action@v6 + with: + context: . + platforms: linux/amd64,linux/arm64 + push: true + tags: ${{ steps.meta.outputs.tags }} + labels: ${{ steps.meta.outputs.labels }} diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index cb85e5ce..794f3c8f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,46 +1,46 @@ -# Contributing to PxWeb - -Thank you for your interest in contributing to PxWeb! We welcome contributions from the community to help improve our project. - -## Getting Started -To get started with contributing, please follow these steps: - -1. Fork the repository on GitHub. -2. Clone your forked repository to your local machine. -3. Create a new branch from the `main` branch. Name your branch descriptively, indicating the purpose of your changes. -4. Make your changes and ensure that the code follows the project's coding conventions. -5. Test your changes thoroughly to ensure they work as expected. -6. Commit your changes with a clear and descriptive commit message. -7. Push your changes to your forked repository. -8. Open a pull request against the `main` branch of the original repository. - -## 3rd Party Components - -While developing for this project, we aim to minimize the number of dependencies. This is to keep the project lightweight, maintainable, and to reduce potential security risks. - -Before adding a new 3rd party component or library, please consider the following: - -1. Is the component necessary? Can the functionality be achieved without it? -2. Is the component actively maintained? An unmaintained component can pose a security risk and may lack support. -3. Does the component have a large community? Larger communities often mean more resources for troubleshooting and learning. -4. Is the component's license compatible with our project? - -If you believe a 3rd party component is necessary, please provide a justification in your pull request. The project maintainers will review and discuss the addition. - -## Code Review - -All pull requests will be reviewed by the project maintainers. Please be patient and responsive during the review process. Feedback and suggestions may be provided to help improve the quality of your contribution. - -## Issue Tracking - -If you encounter any issues or have ideas for improvements, please check the project's issue tracker on GitHub. If the issue or idea has not been reported yet, feel free to open a new issue. - -## Code of Conduct - -This project and everyone participating in it is governed by the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. - -## License - -By contributing to this project, you agree that your contributions will be licensed under the [project's license](LICENSE). - -We appreciate your contributions and look forward to working with you! +# Contributing to PxWeb + +Thank you for your interest in contributing to PxWeb! We welcome contributions from the community to help improve our project. + +## Getting Started +To get started with contributing, please follow these steps: + +1. Fork the repository on GitHub. +2. Clone your forked repository to your local machine. +3. Create a new branch from the `main` branch. Name your branch descriptively, indicating the purpose of your changes. +4. Make your changes and ensure that the code follows the project's coding conventions. +5. Test your changes thoroughly to ensure they work as expected. +6. Commit your changes with a clear and descriptive commit message. +7. Push your changes to your forked repository. +8. Open a pull request against the `main` branch of the original repository. + +## 3rd Party Components + +While developing for this project, we aim to minimize the number of dependencies. This is to keep the project lightweight, maintainable, and to reduce potential security risks. + +Before adding a new 3rd party component or library, please consider the following: + +1. Is the component necessary? Can the functionality be achieved without it? +2. Is the component actively maintained? An unmaintained component can pose a security risk and may lack support. +3. Does the component have a large community? Larger communities often mean more resources for troubleshooting and learning. +4. Is the component's license compatible with our project? + +If you believe a 3rd party component is necessary, please provide a justification in your pull request. The project maintainers will review and discuss the addition. + +## Code Review + +All pull requests will be reviewed by the project maintainers. Please be patient and responsive during the review process. Feedback and suggestions may be provided to help improve the quality of your contribution. + +## Issue Tracking + +If you encounter any issues or have ideas for improvements, please check the project's issue tracker on GitHub. If the issue or idea has not been reported yet, feel free to open a new issue. + +## Code of Conduct + +This project and everyone participating in it is governed by the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. + +## License + +By contributing to this project, you agree that your contributions will be licensed under the [project's license](LICENSE). + +We appreciate your contributions and look forward to working with you! diff --git a/Dockerfile b/Dockerfile index 1a5664d9..8c3f046e 100644 --- a/Dockerfile +++ b/Dockerfile @@ -1,11 +1,11 @@ -FROM node:20.18.0-slim AS build -WORKDIR /app -COPY . ./ -RUN npm ci && npm run build - -# production environment -FROM nginxinc/nginx-unprivileged:1.27.3-alpine3.20 -COPY --from=build /app/packages/pxweb2/dist /usr/share/nginx/html -COPY nginx/conf.d/default.conf /etc/nginx/conf.d -EXPOSE 8080 -CMD ["nginx", "-g", "daemon off;"] +FROM node:20.18.0-slim AS build +WORKDIR /app +COPY . ./ +RUN npm ci && npm run build + +# production environment +FROM nginxinc/nginx-unprivileged:1.27.3-alpine3.20 +COPY --from=build /app/packages/pxweb2/dist /usr/share/nginx/html +COPY nginx/conf.d/default.conf /etc/nginx/conf.d +EXPOSE 8080 +CMD ["nginx", "-g", "daemon off;"] diff --git a/MAINTAINERS.md b/MAINTAINERS.md index 782743ad..88fceb69 100644 --- a/MAINTAINERS.md +++ b/MAINTAINERS.md @@ -1,109 +1,109 @@ -# Maintainers Guide - -This guide is intended for maintainers - those who are maintaining PxWeb by providing or reviewing pull requests. - -## Getting Started - -1. Familiarize yourself with the project structure and our [CONTRIBUTING.md](./CONTRIBUTING.md) guide as well as this guide. -2. Setup the project locally and make sure that you can run PxWeb. - -## Development Tools we use -We recommend the following tools for our development environment: - -- **Code Editor**: [Visual Studio Code (VS Code)](https://code.visualstudio.com/) is our preferred code editor. It provides a rich set of features, extensions, and integrations that enhance productivity and make development easier. - -- **Build System**: [NX](https://nx.dev/) is our build system of choice. It is a powerful tool that helps us manage monorepos, improve build performance, and enforce best practices in our development workflow. - -- **Development Environment**: [Vite](https://vitejs.dev/) is our preferred development environment. It is a fast and lightweight build tool that optimizes the development experience by providing instant server startup, hot module replacement, and efficient bundling. - -- **Accessibility**: [Axe](https://www.deque.com/axe/) is our preferred tool to help us comply with wcag - - -By using these tools, we ensure a streamlined and efficient development process, enabling us to deliver high-quality code. - - -## Git Branching Strategy - -We use a simple and effective Git branching strategy to keep our project organized and maintainable. - -1. **Main Branch**: The `main` branch is the primary branch where the source code of HEAD always reflects a "production-ready" state. - -2. **Feature Branches**: For new features and non-emergency bug fixes, we create a new branch off of `main`. Name your branch descriptively, indicating the purpose of your changes. Branch names should be lowercased and should be prefixed with `feature/`. - - Example: `feature/PXWEB2-1-new-login-screen` - -3. **Fix Branches**: For bug fixes, we create a new branch off of `main`. Name your branch descriptively, indicating the purpose of your changes. Branch names should be lowercased and prefixed with `fix/`. - - Example: `fix/PXWEB2-1-login-screen-bug` - -4. **Patch Branches**: For minor changes and patches, we create a new branch off of `main`. Name your branch descriptively, indicating the purpose of your changes. Branch names should be lowercased and prefixed with `patch/`. - - Example: `patch/PXWEB2-1-update-login-screen-docs` - -5. **Pull Requests**: After making your changes in these branches, merge them back into `main` via a pull request. The pull request should be reviewed and tested before it is merged. - ->Make sure that the JIRA id is included in the branch name and that this should be in capital letters. - ->We prefer hyphens instead of underscores for word separator in branch names. - -This strategy ensures that our `main` branch always has "production-ready" code that has been reviewed and tested. - -## Create Pull Requests -To get started with contributing code, please follow these steps: - -1. Clone the repository to your local machine. -2. Create a new branch from the `main` branch. Name your branch descriptively, indicating the purpose of your changes. -3. Make your changes and ensure that the code follows the project's coding conventions. -4. Test your changes thoroughly to ensure they work as expected. -5. Commit your changes with a clear and descriptive commit message. -6. Push your changes. -7. Open a pull request against the `main` branch and make sure that it has: - - A descriptive title. - - A clear and concise description of the changes, including the purpose and benefits of the change. - - A reference to the related issue(s) or ticket(s). - - Screenshots or gifs if the changes include UI/UX changes. - - New tests that cover the added features or bug fixes. - - Documentation updates if necessary. - - Passed all the continuous integration checks (like build, linting and tests). - -> Your PR will have automatic deploys to Cloudflare Pages that can be used by the reviewers - -8. Assign reviewers to your PR and once approved by at least one reviewer you can continue and merge the PR. - - -## Reviewing Pull Requests - -1. Ensure that the PR is related to a filed issue. -2. Check that the code follows the project's coding standards. -3. Test the code locally to ensure it works as expected. -4. Review the tests included with the PR to ensure they cover the new functionality or bug fix. - - -## Communicating - -1. Be respectful and kind to the contributors. -2. Provide clear, constructive feedback on PRs. -3. Promote a collaborative and learning environment. - -Remember, this project and everyone participating in it is governed by the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. - -## 3rd Party Components - -While developing for this project, we aim to minimize the number of dependencies. This is to keep the project lightweight, maintainable, and to reduce potential security risks. - -Before adding a new 3rd party component or library, please consider the following: - -1. Is the component necessary? Can the functionality be achieved without it? -2. Is the component actively maintained? An unmaintained component can pose a security risk and may lack support. -3. Does the component have a large community? Larger communities often mean more resources for troubleshooting and learning. -4. Is the component's license compatible with our project? -5. Consult with another maintainer if it is the right component for the job. -6. Consult [snyk Advisor](https://snyk.io/advisor/) to get a summary for the component. - -For existing third-party component dependencies, we will utilize Dependabot to help us stay up to date. Dependabot is an automated dependency management tool that regularly checks for updates to our dependencies and creates pull requests to update them. This helps us ensure that we are using the latest versions of our dependencies, which can include important bug fixes, security patches, and new features. - -We are committed to continuously updating our dependencies to ensure that we are using the latest versions. However, in some cases, we may encounter conflicts with NX plugins that prevent us from updating to the latest versions. In such situations, we carefully evaluate the impact and risks before deciding on the appropriate course of action. - -In the event of a security vulnerability being discovered in any of our dependencies, we will prioritize attending to it urgently. Our team will take immediate action to mitigate the risk and apply necessary patches or updates. - - +# Maintainers Guide + +This guide is intended for maintainers - those who are maintaining PxWeb by providing or reviewing pull requests. + +## Getting Started + +1. Familiarize yourself with the project structure and our [CONTRIBUTING.md](./CONTRIBUTING.md) guide as well as this guide. +2. Setup the project locally and make sure that you can run PxWeb. + +## Development Tools we use +We recommend the following tools for our development environment: + +- **Code Editor**: [Visual Studio Code (VS Code)](https://code.visualstudio.com/) is our preferred code editor. It provides a rich set of features, extensions, and integrations that enhance productivity and make development easier. + +- **Build System**: [NX](https://nx.dev/) is our build system of choice. It is a powerful tool that helps us manage monorepos, improve build performance, and enforce best practices in our development workflow. + +- **Development Environment**: [Vite](https://vitejs.dev/) is our preferred development environment. It is a fast and lightweight build tool that optimizes the development experience by providing instant server startup, hot module replacement, and efficient bundling. + +- **Accessibility**: [Axe](https://www.deque.com/axe/) is our preferred tool to help us comply with wcag + + +By using these tools, we ensure a streamlined and efficient development process, enabling us to deliver high-quality code. + + +## Git Branching Strategy + +We use a simple and effective Git branching strategy to keep our project organized and maintainable. + +1. **Main Branch**: The `main` branch is the primary branch where the source code of HEAD always reflects a "production-ready" state. + +2. **Feature Branches**: For new features and non-emergency bug fixes, we create a new branch off of `main`. Name your branch descriptively, indicating the purpose of your changes. Branch names should be lowercased and should be prefixed with `feature/`. + + Example: `feature/PXWEB2-1-new-login-screen` + +3. **Fix Branches**: For bug fixes, we create a new branch off of `main`. Name your branch descriptively, indicating the purpose of your changes. Branch names should be lowercased and prefixed with `fix/`. + + Example: `fix/PXWEB2-1-login-screen-bug` + +4. **Patch Branches**: For minor changes and patches, we create a new branch off of `main`. Name your branch descriptively, indicating the purpose of your changes. Branch names should be lowercased and prefixed with `patch/`. + + Example: `patch/PXWEB2-1-update-login-screen-docs` + +5. **Pull Requests**: After making your changes in these branches, merge them back into `main` via a pull request. The pull request should be reviewed and tested before it is merged. + +>Make sure that the JIRA id is included in the branch name and that this should be in capital letters. + +>We prefer hyphens instead of underscores for word separator in branch names. + +This strategy ensures that our `main` branch always has "production-ready" code that has been reviewed and tested. + +## Create Pull Requests +To get started with contributing code, please follow these steps: + +1. Clone the repository to your local machine. +2. Create a new branch from the `main` branch. Name your branch descriptively, indicating the purpose of your changes. +3. Make your changes and ensure that the code follows the project's coding conventions. +4. Test your changes thoroughly to ensure they work as expected. +5. Commit your changes with a clear and descriptive commit message. +6. Push your changes. +7. Open a pull request against the `main` branch and make sure that it has: + - A descriptive title. + - A clear and concise description of the changes, including the purpose and benefits of the change. + - A reference to the related issue(s) or ticket(s). + - Screenshots or gifs if the changes include UI/UX changes. + - New tests that cover the added features or bug fixes. + - Documentation updates if necessary. + - Passed all the continuous integration checks (like build, linting and tests). + +> Your PR will have automatic deploys to Cloudflare Pages that can be used by the reviewers + +8. Assign reviewers to your PR and once approved by at least one reviewer you can continue and merge the PR. + + +## Reviewing Pull Requests + +1. Ensure that the PR is related to a filed issue. +2. Check that the code follows the project's coding standards. +3. Test the code locally to ensure it works as expected. +4. Review the tests included with the PR to ensure they cover the new functionality or bug fix. + + +## Communicating + +1. Be respectful and kind to the contributors. +2. Provide clear, constructive feedback on PRs. +3. Promote a collaborative and learning environment. + +Remember, this project and everyone participating in it is governed by the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. + +## 3rd Party Components + +While developing for this project, we aim to minimize the number of dependencies. This is to keep the project lightweight, maintainable, and to reduce potential security risks. + +Before adding a new 3rd party component or library, please consider the following: + +1. Is the component necessary? Can the functionality be achieved without it? +2. Is the component actively maintained? An unmaintained component can pose a security risk and may lack support. +3. Does the component have a large community? Larger communities often mean more resources for troubleshooting and learning. +4. Is the component's license compatible with our project? +5. Consult with another maintainer if it is the right component for the job. +6. Consult [snyk Advisor](https://snyk.io/advisor/) to get a summary for the component. + +For existing third-party component dependencies, we will utilize Dependabot to help us stay up to date. Dependabot is an automated dependency management tool that regularly checks for updates to our dependencies and creates pull requests to update them. This helps us ensure that we are using the latest versions of our dependencies, which can include important bug fixes, security patches, and new features. + +We are committed to continuously updating our dependencies to ensure that we are using the latest versions. However, in some cases, we may encounter conflicts with NX plugins that prevent us from updating to the latest versions. In such situations, we carefully evaluate the impact and risks before deciding on the appropriate course of action. + +In the event of a security vulnerability being discovered in any of our dependencies, we will prioritize attending to it urgently. Our team will take immediate action to mitigate the risk and apply necessary patches or updates. + + diff --git a/docs/getting-started/configuration.md b/docs/getting-started/configuration.md index e55fc8dc..1a6deaf5 100644 --- a/docs/getting-started/configuration.md +++ b/docs/getting-started/configuration.md @@ -1,14 +1,14 @@ -# Configuration - -## Application configuration settings - -### API end point -In order for PxWeb to display your statistics, you need to configure the URL to the root of PxWebApi 2.0 - -### Language settings -Is that fetched from the API? - -### TODO other settings - - +# Configuration + +## Application configuration settings + +### API end point +In order for PxWeb to display your statistics, you need to configure the URL to the root of PxWebApi 2.0 + +### Language settings +Is that fetched from the API? + +### TODO other settings + + ## Application configuration settings \ No newline at end of file diff --git a/docs/getting-started/contribute/add-translations.md b/docs/getting-started/contribute/add-translations.md index 65d84d64..22cb3422 100644 --- a/docs/getting-started/contribute/add-translations.md +++ b/docs/getting-started/contribute/add-translations.md @@ -1,2 +1,2 @@ -# Add translations +# Add translations Help us out adding translations to PxWeb. \ No newline at end of file diff --git a/docs/getting-started/contribute/help-us-write-the-docs.md b/docs/getting-started/contribute/help-us-write-the-docs.md index 30c9bf7c..630e172a 100644 --- a/docs/getting-started/contribute/help-us-write-the-docs.md +++ b/docs/getting-started/contribute/help-us-write-the-docs.md @@ -1,2 +1,2 @@ -# Help us write the docs +# Help us write the docs With good documentation ... \ No newline at end of file diff --git a/docs/getting-started/contribute/report-a-bug.md b/docs/getting-started/contribute/report-a-bug.md index 23e469c3..0f09b769 100644 --- a/docs/getting-started/contribute/report-a-bug.md +++ b/docs/getting-started/contribute/report-a-bug.md @@ -1,4 +1,4 @@ -# Report a bug -TODO: Add link to GitHub issues. - +# Report a bug +TODO: Add link to GitHub issues. + TODO: Security issues should be reported with GitHub ... \ No newline at end of file diff --git a/docs/getting-started/installation.md b/docs/getting-started/installation.md index 3e936a6f..cb6e5f28 100644 --- a/docs/getting-started/installation.md +++ b/docs/getting-started/installation.md @@ -1,20 +1,20 @@ -# Getting started ->Looking for existing PxWeb, PxWeb 2023 v1? Then head away to the official repository at [https://github.com/statisticssweden/PxWeb](https://github.com/statisticssweden/PxWeb) - -## Installation -This version is still under development so there are no packaged version yet. -But you could always install it from source. - -### Install from source -Make usre that you have NodeJS installed. - -1. Clone the reposiory `git clone https://github.com/PxTools/PxWeb2.git` -2. Install dependencies `npm install` -3. Build the PxWeb with `npm run build` -4. Host the result of the builds on a web server of your choice - -### Install from binaries -_TODO: Describe how to download from GitHub Releases the latest version._ - -### Install docker image +# Getting started +>Looking for existing PxWeb, PxWeb 2023 v1? Then head away to the official repository at [https://github.com/statisticssweden/PxWeb](https://github.com/statisticssweden/PxWeb) + +## Installation +This version is still under development so there are no packaged version yet. +But you could always install it from source. + +### Install from source +Make usre that you have NodeJS installed. + +1. Clone the reposiory `git clone https://github.com/PxTools/PxWeb2.git` +2. Install dependencies `npm install` +3. Build the PxWeb with `npm run build` +4. Host the result of the builds on a web server of your choice + +### Install from binaries +_TODO: Describe how to download from GitHub Releases the latest version._ + +### Install docker image _TODO: Describe how to run the docker image._ \ No newline at end of file diff --git a/docs/overrides/home.html b/docs/overrides/home.html index 750b2233..e40fdd49 100644 --- a/docs/overrides/home.html +++ b/docs/overrides/home.html @@ -1,104 +1,104 @@ - - -{% extends "main.html" %} - - -{% block tabs %} - {{ super() }} - - - - - -
-
-
- - - - - -
-

PxWeb 2.0 New user interface -

-

Statistics Sweden and Statistics Norway have a project together to build a new and more user-friendly interface for PxWeb.

- - About the project - -
-
-
- -
-

-
-
-{% endblock %} - - -{% block content %}{% endblock %} - - -{% block footer %}{% endblock %} + + +{% extends "main.html" %} + + +{% block tabs %} + {{ super() }} + + + + + +
+
+
+ + + + + +
+

PxWeb 2.0 New user interface +

+

Statistics Sweden and Statistics Norway have a project together to build a new and more user-friendly interface for PxWeb.

+ + About the project + +
+
+
+ +
+

+
+
+{% endblock %} + + +{% block content %}{% endblock %} + + +{% block footer %}{% endblock %} diff --git a/docs/stylesheets/extra.css b/docs/stylesheets/extra.css index 0dd0d9e6..2e9fccce 100644 --- a/docs/stylesheets/extra.css +++ b/docs/stylesheets/extra.css @@ -1,77 +1,77 @@ -.mdx-container { - background: url("data:image/svg+xml;utf8,") - no-repeat bottom, - linear-gradient( - to bottom, - var(--md-primary-fg-color), - #a63fd9 99%, - var(--md-default-bg-color) 99% - ); - padding-top: 1rem; - } - [data-md-color-scheme="slate"] .mdx-container { - background: url("data:image/svg+xml;utf8,") - no-repeat bottom, - linear-gradient( - to bottom, - var(--md-primary-fg-color), - #363949 99%, - var(--md-default-bg-color) 99% - ); - } - .mdx-hero { - color: var(--md-primary-bg-color); - margin: 0 0.8rem; - } - .mdx-hero h1 { - color: currentcolor; - font-weight: 700; - margin-bottom: 1rem; - } - @media screen and (max-width: 29.984375em) { - .mdx-hero h1 { - font-size: 1.4rem; - } - } - .mdx-hero__content { - padding-bottom: 6rem; - } - @media screen and (min-width: 60em) { - .mdx-hero { - align-items: stretch; - display: flex; - } - .mdx-hero__content { - margin-top: 3.5rem; - max-width: 19rem; - padding-bottom: 14vw; - } - .mdx-hero__image { - order: 1; - transform: translateX(4rem); - width: 38rem; - } - } - @media screen and (min-width: 76.25em) { - .mdx-hero__image { - transform: translateX(8rem); - } - } - .mdx-hero .md-button { - color: var(--md-primary-bg-color); - margin-right: 0.5rem; - margin-top: 0.5rem; - } - .mdx-hero .md-button:focus, - .mdx-hero .md-button:hover { - background-color: var(--md-accent-fg-color); - border-color: var(--md-accent-fg-color); - color: var(--md-accent-bg-color); - } - .mdx-hero .md-button--primary { - background-color: var(--md-primary-bg-color); - border-color: var(--md-primary-bg-color); - color: #894da8; - } - - +.mdx-container { + background: url("data:image/svg+xml;utf8,") + no-repeat bottom, + linear-gradient( + to bottom, + var(--md-primary-fg-color), + #a63fd9 99%, + var(--md-default-bg-color) 99% + ); + padding-top: 1rem; + } + [data-md-color-scheme="slate"] .mdx-container { + background: url("data:image/svg+xml;utf8,") + no-repeat bottom, + linear-gradient( + to bottom, + var(--md-primary-fg-color), + #363949 99%, + var(--md-default-bg-color) 99% + ); + } + .mdx-hero { + color: var(--md-primary-bg-color); + margin: 0 0.8rem; + } + .mdx-hero h1 { + color: currentcolor; + font-weight: 700; + margin-bottom: 1rem; + } + @media screen and (max-width: 29.984375em) { + .mdx-hero h1 { + font-size: 1.4rem; + } + } + .mdx-hero__content { + padding-bottom: 6rem; + } + @media screen and (min-width: 60em) { + .mdx-hero { + align-items: stretch; + display: flex; + } + .mdx-hero__content { + margin-top: 3.5rem; + max-width: 19rem; + padding-bottom: 14vw; + } + .mdx-hero__image { + order: 1; + transform: translateX(4rem); + width: 38rem; + } + } + @media screen and (min-width: 76.25em) { + .mdx-hero__image { + transform: translateX(8rem); + } + } + .mdx-hero .md-button { + color: var(--md-primary-bg-color); + margin-right: 0.5rem; + margin-top: 0.5rem; + } + .mdx-hero .md-button:focus, + .mdx-hero .md-button:hover { + background-color: var(--md-accent-fg-color); + border-color: var(--md-accent-fg-color); + color: var(--md-accent-bg-color); + } + .mdx-hero .md-button--primary { + background-color: var(--md-primary-bg-color); + border-color: var(--md-primary-bg-color); + color: #894da8; + } + +