Merge pull request #129 from IABTechLab/sas-UID2-3917-sample-site-tex…

…t-links

Updates to secure signals example pages

.github/workflows/publish-secure-signal-examples.yml

@@ -1,5 +1,5 @@
 name: Release Secure Signal Examples Docker Image
-run-name: ${{ github.action_ref == 'refs/head/main' && 'Release' || 'Publish Pre-release' }} Secure Signal Examples Docker Image by @${{ github.actor }}  
+run-name: ${{ github.action_ref == 'refs/head/main' && 'Release' || 'Publish Pre-release' }} Secure Signal Examples Docker Image by @${{ github.actor }}
 
 on:
   workflow_dispatch:
@@ -8,7 +8,7 @@ env:
   REGISTRY: ghcr.io
 
 jobs:
-  build-server-only:
+  build-server-side:
     runs-on: ubuntu-latest
     permissions:
       contents: read
@@ -29,10 +29,10 @@ jobs:
           tags: |
             type=sha,format=short
             type=raw,value=latest
-      - name: Build and push Docker server_only image
+      - name: Build and push Docker server_side image
         uses: docker/build-push-action@v5
         with:
-          context: examples/google-secure-signals-integration/server_only
+          context: examples/google-secure-signals-integration/server_side
           push: true
           tags: ${{ steps.meta.outputs.tags }}
           labels: ${{ steps.meta.outputs.labels }}

.github/workflows/release-secure-signal-examples-docker-image-server-only.yaml

@@ -1,35 +1,35 @@
 name: Release Secure Signal Examples Docker Image for Server Only
-run-name: ${{ inputs.release_type == 'Snapshot' && 'Publish Pre-release' || format('Release {0}', inputs.release_type)}} Secure Signal Examples Docker Image for Server Only by @${{ github.actor }}  
+run-name: ${{ inputs.release_type == 'Snapshot' && 'Publish Pre-release' || format('Release {0}', inputs.release_type)}} Secure Signal Examples Docker Image for Server Only by @${{ github.actor }}
 on:
   workflow_dispatch:
     inputs:
       release_type:
         type: choice
         description: The type of release
         options:
-        - Major
-        - Minor
-        - Patch
-        - Snapshot
+          - Major
+          - Minor
+          - Patch
+          - Snapshot
         required: true
 
 jobs:
   incrementVersionNumber:
     uses: IABTechLab/uid2-shared-actions/.github/workflows/shared-increase-version-number.yaml@v2
     with:
       release_type: ${{ inputs.release_type }}
-      working_dir: examples/google-secure-signals-integration/server_only
+      working_dir: examples/google-secure-signals-integration/server_side
     secrets: inherit
 
   publishForSecureSignalsExampleSrvOnly:
     uses: IABTechLab/uid2-shared-actions/.github/workflows/shared-publish-to-docker-versioned.yaml@v3
     needs: incrementVersionNumber
-    with: 
+    with:
       new_version: ${{ needs.incrementVersionNumber.outputs.new_version }}
       image_tag: ${{ needs.incrementVersionNumber.outputs.image_tag }}
       release_type: ${{ inputs.release_type }}
-      docker_file: examples/google-secure-signals-integration/server_only/Dockerfile
-      docker_context: examples/google-secure-signals-integration/server_only
+      docker_file: examples/google-secure-signals-integration/server_side/Dockerfile
+      docker_context: examples/google-secure-signals-integration/server_side
       docker_image_name: iabtechlab/uid2-secure-signals-example-srvonly
       docker_registry: ghcr.io
     secrets: inherit

examples/google-secure-signals-integration/server_only/README.md → examples/google-secure-signals-integration/server_side/README.md

@@ -1,6 +1,6 @@
-# Server-Only UID2 Secure Signals Integration Example
+# Server-Side UID2 Secure Signals Integration Example
 
-This example demonstrates how a content publisher who is working with [Google Interactive Media Ads(IMA) SDKs](https://developers.google.com/interactive-media-ads/docs/sdks/html5/client-side) can use [Google Secure Signal](https://support.google.com/admanager/answer/10488752) to share UID2 directly with bidders, in a server-only implementation of UID2.
+This example demonstrates how a content publisher who is working with [Google Interactive Media Ads(IMA) SDKs](https://developers.google.com/interactive-media-ads/docs/sdks/html5/client-side) can use [Google Secure Signal](https://support.google.com/admanager/answer/10488752) to share UID2 directly with bidders, in a server-side implementation of UID2.
 
 For an example application using the [UID2 SDK for JavaScript](https://unifiedid.com/docs/sdks/sdk-ref-javascript), see [Server-Side Integration Example, UID2 JavaScript SDK](../with_sdk_v3/README.md).
 

examples/google-secure-signals-integration/server_only/views/header.html → examples/google-secure-signals-integration/server_side/views/header.html

@@ -2,7 +2,7 @@
 <html>
   <head>
     <meta charset="UTF-8" />
-    <title>UID2 Publisher Server-Side Integration Example</title>
+    <title>Server-Side UID2 Integration Example with Google Secure Signals</title>
     <link rel="stylesheet" type="text/css" href="/stylesheets/app.css" />
     <link rel="shortcut icon" href="/images/favicon.png" />
     <script src="https://code.jquery.com/jquery-3.6.0.min.js"></script>
@@ -26,15 +26,20 @@
     </script>
   </head>
   <body>
-    <h1>Server-Side UID2 Integration Example</h1>
+    <h1>Server-Side UID2 Integration Example with Google Secure Signals</h1>
     <p class="intro">
       This example demonstrates how a content publisher can use the UID2 services to implement the
       <a href="https://unifiedid.com/docs/guides/integration-google-ss#server-side-integration"
-        >Server-Side Integration</a
+        >Server-Side Integration.</a
       >. [<a
-        href="https://github.com/IABTechLab/uid2-web-integrations/tree/main/examples/google-secure-signals-integration/server_only"
+        href="https://github.com/IABTechLab/uid2-web-integrations/tree/main/examples/google-secure-signals-integration/server_side"
         >Source Code</a
       >]
+      <br />
+      <br />
+      This assumes that the publisher has implemented
+      <a href="https://unifiedid.com/docs/guides/integration-google-ss">Server-Side integration</a>
+      on the backend and able to pass the resulting UID2 identity response to the front end.
     </p>
   </body>
 </html>