equinor/energyvision

Última actividad de origen registrada: 5 de octubre de 2026 a las 10:49

Catálogo de SkillsMP actualizado: 29 de octubre de 2026 a las 18:30

skills recopiladas: 8

Estrellas en GitHub: 6
Forks en GitHub: 2

Instalar con un asistente de IA

Copia este prompt en el asistente de IA que estés usando.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/equinor/energyvision.

README del repositorio

Archivo de origen del README: README.md

Leer el README original

Mostrar README completo

<p align="center"> <a href="https://www.equinor.com"> <img width="300" src=".github/Equinor_HORIZ_logo_RGB_RED.png"> </a> </p> # EnergyVision This is the main repository for the [equinor.com website](https://www.equinor.com). This version of the website is built using the [Sanity content platform](https://www.sanity.io/) as headless CMS and [Next.js](https://nextjs.org/) for the web frontend. The project is licensed under the [MIT license](https://github.com/equinor/energyvision/blob/main/LICENSE) following [the open source strategy of Equinor](https://opensource.equinor.com) and integrates elements from the [Equinor Design System](https://eds.equinor.com). ## Getting started This project uses [pnpm](https://pnpm.io) as main package manager. You can install pnpm using npm as shown below, or use one of the [alternative installation methods](https://pnpm.io/installation). Use Node.js 24.22.1 for development and builds. With nvm installed, run `nvm install` and `nvm use` to select the version in `.nvmrc`. Verify the actual runtime with `node --version` on each host and CI runner, and `docker run --rm <image> node --version` for each container image. The web and Studio deployment actions log both runner and built-image versions, and their containers log the runtime version at startup. ```bash # Install pnpm npm i -g pnpm # Install all project dependencies pnpm setup-project ``` For compatibility reasons, the Sanity Studio uses the Yarn package manager, and the search indexer uses npm. The `pnpm setup-project` script will automatically install the dependencies for the Studio as well as the workspace packages listed in `pnpm-workspace.yaml`. See the [section on package managers](#package-managers) for more information. This project requires several environment variables to run. These environment variables should be added in `studio/.env.development`, `web/.env.local`, and `search/.env` respectively. ## Project overview This monorepo is organized into several folder. Please refer to README files inside each folder for more information. - `studio` - [Sanity](https://www.sanity.io/) powered content platform. - `web` - Web application using [Next.js](https://nextjs.org/) and React components. - `search` - Azure functions for maintaining search indexes at [Algolia](https://www.algolia.com/apps/24ZMKUY18Z/dashboard). ## Package managers This project uses the pnpm package manager. All commands should be run from root. There are filter aliases in the root `package.json` file that can be used to run commands in specific directories. For example: ```bash # Install dependencies pnpm web install # Start the web in dev mode pnpm web dev # Add some package to the web folder pnpm web add <some-package> # Build Next.js pnpm web build ``` If you need to add arguments to scripts when using one of the aliases, such as `--force` or `--dev` to force a re-install of all dependencies, you must add `--` when running these commands from the project root. For example: ```bash # Add a dev-dependency pnpm web add chalk -- --save-dev ``` ### Studio ```bash # Start studio in dev mode pnpm studio dev ``` ### Search Due to compatibility issues, npm is used for the Search Indexers. The reason being that it was not possible (with pnpm v6 at least) to generate a package containing all dependencies from the search folder. So in order to work with dependencies for anything under `search`, use npm from within that folder. You can still use pnpm from the root folder to execute scripts however. ## Feature flags These feature flags are based on the currently active [Sanity dataset](https://www.sanity.io/docs/datasets). This allows us to have features that are based on dataset. For example some features related to analytics can be disabled in development dataset where it is not needed. Not all features in global dataset are used in other datasets. ## Contributing If you want to report a bug, please create an issue in GitHub unless it is a security issue. If it is a security issue, please follow our Security Reporting Policy in SECURITY.md file.

Cargando el README del repositorio…

Skills en este repositorio

Desarrolladores de software

1 categorías ocupacionales · 38% clasificado

skill

ocupación

descripción

actualizado

web

sin clasificar

Web application React/NextJS/TypeScript coding standards, state management patterns, and component guidelines. Use this when working on web code