deny /tips from being gated

Author: shtukas

dotcom-rendering/README.md

@@ -6,27 +6,44 @@ Frontend rendering framework for theguardian.com. It uses [React](https://reactj
 
 This guide will help you get the `dotcom-rendering` application running on your development machine.
 
+To download the repository
+
+```
+$ git clone [email protected]:guardian/dotcom-rendering.git
+$ cd dotcom-rendering
+```
+
 ### Install Node.js
 
-The only thing you need to make sure you have installed before you get going is [Node.js](https://nodejs.org).
+Make sure you have [Node.js](https://nodejs.org) installed.
 
-We recommend using [fnm](https://github.com/Schniz/fnm) to help manage multiple versions of Node.js on on machine.
+We recommend using [fnm](https://github.com/Schniz/fnm) to help manage multiple versions of Node.js on one machine.
 
 Once Node is installed, make sure you're using the correct package manager by [enabling corepack](https://github.com/nodejs/corepack?tab=readme-ov-file#utility-commands):
 
 ```sh
 $ corepack enable
 ```
 
-> [!NOTE]
->
-> If you're using `asdf`, you'll need to run `asdf reshim nodejs` after running `corepack enable`.
+If you're using `asdf`, you'll need to run `asdf reshim nodejs` after running `corepack enable`.
+
+### Install Dependencies
 
-### Running instructions
+run
+
+```
+$ make install
+```
+
+If it complains that you do not have the right version of node, then run (or replace with the correct version manager or the correct version):
+
+```
+$ fnm install 22.14.0
+```
+
+### Running on local
 
 ```sh
-$ git clone [email protected]:guardian/dotcom-rendering.git
-$ cd dotcom-rendering
 $ make dev
 ```
 
@@ -44,7 +61,7 @@ http://localhost:3030/ArticleJson?url=https://www.theguardian.com/sport/2019/jul
 
 If you're new to TypeScript projects, if you're trying to integrate with other applications or if you prefer to take things slow, we also have a more [detailed setup guide](docs/contributing/detailed-setup-guide.md).
 
-### Technologies
+## Technologies
 
 | Technology                                                                                                                 | Description                                                                                                                                                                                                                                                                                                                                       |
 | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

dotcom-rendering/docs/contributing/detailed-setup-guide.md

@@ -8,25 +8,44 @@ This high level diagram shows the difference between the data flow when DCR is u
 
 ## Developing
 
-### Setup
+## Getting started
 
-The only thing you need to make sure you have installed before you get going is Node.
+To download the repository
 
-#### Node.js
+```
+$ git clone [email protected]:guardian/dotcom-rendering.git
+$ cd dotcom-rendering
+```
+
+### Node.js
+
+Make sure you have [Node.js](https://nodejs.org) installed.
 
 We recommend using [fnm](https://github.com/Schniz/fnm) to help manage multiple versions of Node.js on on machine.
 
-### Start
+### Install Dependencies
+
+run
+
+```
+$ make install
+```
+
+If it complains that you do not have the right version of node, then run (or replace with the correct version manager or the correct version):
+
+```
+$ fnm install 22.14.0
+```
 
-Start the development server:
+### Running on local
 
 ```sh
-make dev
+$ make dev
 ```
 
 This will start the development server on port 3030: [http://localhost:3030](http://localhost:3030).
 
-> Note: To run the development server with support for legacy browsers, use `make dev-legacy`
+Note: To run the development server with support for legacy browsers, use `make dev-legacy`
 
 ### Previewing article on local
 

dotcom-rendering/src/components/SignInGateSelector.importable.tsx

@@ -370,14 +370,43 @@ const SignInGateSelectorDefault = ({
 // Auxia Integration Experiment //
 // -------------------------------
 
+/*
+	Date: 29th April 2025
+
+	We have a request to prevent sign-in gate for a specific URL. This feels like an
+	adhoc request and not a new general feature to implement.
+
+	We have a check in SDC: https://github.com/guardian/support-dotcom-components/pull/1345 ,
+	to prevent the Auxia gate from showing, but we also need to prevent the legacy gate from
+	showing. For a cleaner implementation. we are simply going to prevent any of the two
+	gates components from rendering.
+
+	To keep things simple, we are going to add a check in SignInGateSelector, which seems
+	like a good place.
+*/
+
+export const pageIdIsAllowedForGating = (pageId: string): boolean => {
+	// This function was introduced to handle the specific request of not showing a gate for
+	// this url: https://www.theguardian.com/tips
+
+	// pageId is the path without the starting slash
+	// example:
+	// - full url: https://www.theguardian.com/world/2025/apr/29/canada-election-result-liberal-win-mark-carney-anti-trump
+	// - pageId: world/2025/apr/29/canada-election-result-liberal-win-mark-carney-anti-trump
+
+	const denyPaths = ['tips'];
+
+	return !denyPaths.some((denyPath) => pageId.startsWith(denyPath));
+};
+
 export const SignInGateSelector = ({
 	contentType,
 	sectionId = '',
 	tags,
 	isPaidContent,
 	isPreview,
 	host = 'https://theguardian.com/',
-	pageId,
+	pageId, // pageId is the path without starting slash
 	idUrl = 'https://profile.theguardian.com',
 	switches,
 	contributionsServiceUrl,
@@ -389,6 +418,10 @@ export const SignInGateSelector = ({
 		'auxia-signin-gate',
 	);
 
+	if (!pageIdIsAllowedForGating(pageId)) {
+		return <></>;
+	}
+
 	if (!userIsInAuxiaExperiment) {
 		return (
 			<SignInGateSelectorDefault
@@ -529,6 +562,7 @@ const fetchProxyGetTreatments = async (
 ): Promise<AuxiaProxyGetTreatmentsResponse> => {
 	// pageId example: 'money/2017/mar/10/ministers-to-criminalise-use-of-ticket-tout-harvesting-software'
 	const articleIdentifier = `www.theguardian.com/${pageId}`;
+	// articleIdentifier example: 'www.theguardian.com/money/2017/mar/10/ministers-to-criminalise-use-of-ticket-tout-harvesting-software'
 	const url = `${contributionsServiceUrl}/auxia/get-treatments`;
 	const headers = {
 		'Content-Type': 'application/json',