diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index 2e8ac23f5b9dc..dffd5748c8015 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -33,7 +33,6 @@ apps/site/redirects.json @nodejs/web-infra # Critical Documents LICENSE @nodejs/tsc -GOVERNANCE.md @nodejs/tsc CONTRIBUTING.md @nodejs/nodejs-website @nodejs/web-infra docs @nodejs/nodejs-website @nodejs/web-infra SECURITY.md @nodejs/security-wg diff --git a/GOVERNANCE.md b/GOVERNANCE.md deleted file mode 100644 index 555217dc82a23..0000000000000 --- a/GOVERNANCE.md +++ /dev/null @@ -1,90 +0,0 @@ -# Node.js Web Team Governance - -The Node.js Web Team (@nodejs/web) is a team in the Node.js Project that is composed by a set of subteams. Each containing specific responsibilities and goals. - -### TSC Oversight - -Any website change that expresses a position about a global event or group of people requires explicit -[TSC](https://github.com/nodejs/TSC/blob/main/TSC-Charter.md#section-4-responsibilities-of-the-tsc) -approval. This can be obtained by pinging `@nodejs/tsc` and receive no objections after seven days, -or by sending an email to `tsc@iojs.org` and receive at least one approval and no objections after seven days. - -### Node.js Website Team (`@nodejs/nodejs-website`) - -The Node.js Website Team is responsible for the day-to-day technical development of the Node.js Website. This is primarily the development of the website itself, adding new features, pages and components, but also fixing any security issues in the website code, handling operational maintenance, and so on. - -The maintainers on the Node.js Website Team are responsible for steering the technical direction of the Node.js Website, and reserve the right to make final decisions on any issues or pull requests, in line with the Contribution Guidelines, Collaborator Guidelines, the Code of Conduct and the overall Governance premises of the Node.js project. - -Members of this team are nominated through the guidelines provided in the [Contributing Guidelines](https://github.com/nodejs/nodejs.org/blob/main/CONTRIBUTING.md#becoming-a-collaborator) within this repository. After a passed nomination, members should submit a PR to add themselves to the list of current members, shown below. - -#### Current Members - -- [araujogui](https://github.com/araujogui) - **Guilherme Araújo** (he/him) - -- [AugustinMauroy](https://github.com/AugustinMauroy) - **Augustin Mauroy** (he/him) - -- [avivkeller](https://github.com/avivkeller) - **Aviv Keller** (he/him) - -- [aymen94](https://github.com/aymen94) - **Aymen Naghmouchi** - -- [benhalverson](https://github.com/benhalverson) - **Ben Halverson** (he/him) - -- [bjohansebas](https://github.com/bjohansebas) - **Sebastian Beltran** - -- [bmuenzenmeyer](https://github.com/bmuenzenmeyer) - **Brian Muenzenmeyer** (he/him) - -- [bnb](https://github.com/bnb) - **Tierney Cyren** (they/them) - -- [canerakdas](https://github.com/canerakdas) - **Caner Akdas** - -- [dario-piotrowicz](https://github.com/dario-piotrowicz) - **Dario Piotrowicz** - -- [Harkunwar](https://github.com/Harkunwar) - **Harkunwar Kochar** (he/him) - -- [HinataKah0](https://github.com/HinataKah0) - **HinataKah0** (he/him) - -- [manishprivet](https://github.com/manishprivet) - **Manish Kumar** (he/him) - -- [mikeesto](https://github.com/mikeesto) - **Michael Esteban** (he/him) - -- [ovflowd](https://github.com/ovflowd) - **Claudio Wunder** (they/them) - -- [SEWeiTung](https://github.com/SEWeiTung) - **Wei Tung** - -- [shanpriyan](https://github.com/shanpriyan) - **Shanmughapriyan S** - -### Node.js Web Infra Team (`@nodejs/web-infra`) - -The Node.js Web Infra Team is responsible for maintaining the Infrastructure relating to Node.js's Web Presence. The Node.js Web Infra team has the responsibilities of: - -- Maintaining CI/CD pipelines related to Web Infrastructure -- Maintaining our Infrastructure Providers\* -- Have technical ownership on best-standards and best-practices for our Web Infrastructure (such as Web Frameworks that we use) - -Web Infra Team members should have access to be able to maintain the services mentioned above. - -Members of this team are nominated either by the Node.js Technical Steering Committee (TSC) or the Node.js Build WG and follow the guidelines provided in the Collaborator Guidelines of the Node.js Build WG. Note that members of the Node.js Web Team might also recommend people for nomination. - -\* This team has access to infrastructure providers directly related to the Website only, such as Vercel. Other providers that are shared beyond the Website may be controlled by other teams (for example, the Node.js Build WG owns Cloudflare). - -### Node.js Web Standards Team (`@nodejs/web-standards`) - -The Node.js Web Standards Team is composed of Node.js Collaborators and External Collaborators that have extensive experience or expertisè on Web Standards, such as Ecma262. The Standards Team is responsible for guiding and serving as points of contact when either Node.js Collaborators, the Node.js Technical Steering Committee (TSC), or the Web Team, requires assistance or guidance regarding Web Standards. - -Members of this team are nominated by the Node.js Technical Steering Committee (TSC). Note that members of the Node.js Web Team might also recommend people for nomination. - -### Node.js UX & Design Team (`@nodejs/ux-and-design`) - -The Node.js UX & Design Team is composed of Node.js Collaborators and External Collaborators that have experience or expertisè with UX & Design. The UX & Design Team is responsible for guiding and serving as points of contact when members of the Node.js Web Team require assistance or guidance regarding UX & Design. - -Often members of this team will collaborate on providing best practices and guidelines for the Node.js Website, on matters of UX & Design. Members of this team are also responsible for providing feedback on the Node.js Website, and providing feedback on the Node.js Website's design. (For example, when a discussion arises regarding best practices on topics such as CSS, accessibility, UX flows and intent, or component design, the UX & Design Team has a say on the matter). - -Members of this team are nominated by the Node.js Technical Steering Committee (TSC). Note that members of the Node.js Web Team might also recommend people for nomination. - -## The Interoperability of the Node.js Web Team - -As seen above, the different teams under the Node.js Web Team umbrella are responsible for having the oversight on different aspects of Node.js's Web-related projects. However, it is important to note that the Node.js Web Team is not a set of siloed teams, but rather a set of teams that work together to achieve the same goal: Providing the best Web Experience for Node.js. - -Following this line of thought, the Web Infra Team is responsible for the technical aspects of the Node.js Website (Infrastructure, Framework, CI/CD, etc); The Website Team is responsible for the day-to-day development of the Node.js Website; The UX and Design Team advise on Design Matters and the Web Standards Team advise on best-practices for Web APIs and Web Technologies/Standards. - -But above all, the Web Team should work together to better the Web Experience for Node.js, aiming to provide the best experience for Node.js users. diff --git a/README.md b/README.md index aa076088a5427..da65bb0d0e836 100644 --- a/README.md +++ b/README.md @@ -94,6 +94,8 @@ These are maintained in different repositories and we urge users to open **issue [Collaborator Guide][] +[Governance Document][] + [Figma Design][] [Content vs Code][] @@ -121,5 +123,6 @@ These are maintained in different repositories and we urge users to open **issue [content vs code]: https://github.com/nodejs/nodejs.org/blob/main/docs/content-vs-code.md [dependency pinning]: https://github.com/nodejs/nodejs.org/blob/main/docs/dependency-pinning.md [collaborator guide]: https://github.com/nodejs/nodejs.org/blob/main/docs/collaborator-guide.md +[governance document]: https://github.com/nodejs/web-team/blob/main/GOVERNANCE.md [figma design]: https://www.figma.com/file/a10cjjw3MzvRQMPT9FP3xz [translation guidelines]: https://github.com/nodejs/nodejs.org/blob/main/docs/translation.md diff --git a/apps/site/components/Blog/BlogPostCard/index.module.css b/apps/site/components/Blog/BlogPostCard/index.module.css index 166f694e85505..53ec2686369f0 100644 --- a/apps/site/components/Blog/BlogPostCard/index.module.css +++ b/apps/site/components/Blog/BlogPostCard/index.module.css @@ -6,8 +6,8 @@ } .subtitle { - @apply mb-2 - mt-6 + @apply mt-6 + mb-2 inline-block text-xs font-semibold diff --git a/apps/site/components/Common/Turtle/index.module.css b/apps/site/components/Common/Turtle/index.module.css index 6bbeefdbd9bb2..82bacb8ee7d5e 100644 --- a/apps/site/components/Common/Turtle/index.module.css +++ b/apps/site/components/Common/Turtle/index.module.css @@ -8,20 +8,20 @@ translate-x-0 translate-y-0 after:absolute - after:-left-full after:top-[20%] + after:-left-full after:-z-10 after:block after:h-36 after:w-36 after:-rotate-90 - after:select-none after:bg-[url('/static/images/smoke.gif')] after:opacity-[0.15] after:content-[''] + after:select-none motion-reduce:animate-none - after:md:-left-1/2 - after:md:top-1/2; + after:md:top-1/2 + after:md:-left-1/2; } .image { diff --git a/apps/site/components/Downloads/Release/ReleaseCodeBox.tsx b/apps/site/components/Downloads/Release/ReleaseCodeBox.tsx index 63b9f57256d61..a3792cd7c0135 100644 --- a/apps/site/components/Downloads/Release/ReleaseCodeBox.tsx +++ b/apps/site/components/Downloads/Release/ReleaseCodeBox.tsx @@ -128,7 +128,7 @@ const ReleaseCodeBox: FC = () => { const isLoading = context.os === 'LOADING' || context.installMethod === ''; return ( -
+
{/* NoScript warning */}