Registry docs incorrectly reference "Oracle Cloud Infrastructure"

.github/workflows/ci.yml

@@ -11,24 +11,35 @@ concurrency:
 
 jobs:
   main:
-    name: Nx Cloud - Main Job
-    uses: nrwl/ci/.github/workflows/nx-cloud-main.yml@v0.6
-    secrets: inherit
-    with:
-      number-of-agents: 3
-      parallel-commands: |
-        npx nx-cloud record -- npx nx workspace-lint
-        npx nx-cloud record -- npx nx format:check
-      parallel-commands-on-agents: |
-        npx nx affected --target=lint --parallel=3
-        npx nx affected --target=test --parallel=3 --ci --code-coverage
-      final-commands: |
-        npx nx affected --target=build --parallel=3
-        npx nx affected --target=e2e --parallel=3
-
-  agents:
-    name: Nx Cloud - Agents
-    uses: nrwl/ci/.github/workflows/nx-cloud-agents.yml@v0.6
-    secrets: inherit
-    with:
-      number-of-agents: 3
+    name: Main Job
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
+
+      - name: Set SHA
+        uses: nrwl/nx-set-shas@v2
+
+      - name: Install
+        run: yarn install --frozen-lockfile
+
+      - name: Lint
+        run: |
+          yarn nx workspace-lint
+          yarn nx format:check
+          yarn nx affected --target=lint --parallel=3
+
+      - name: Test
+        run: |
+          yarn nx affected --target=test --parallel=3 --ci --code-coverage
+
+      - name: Build
+        run: |
+          yarn nx affected --target=build --parallel=3
+
+      - name: E2E
+        run: |
+          yarn nx affected --target=e2e --parallel=3

.github/workflows/deploy-landing-page.yml

@@ -28,14 +28,13 @@ jobs:
       - name: Set SHA
         uses: nrwl/nx-set-shas@v2
 
-      - name: Install and Build
+      - name: Install
+        run: yarn install --frozen-lockfile
+
+      - name: Build
         run: |
-          yarn install --frozen-lockfile
           yarn nx affected --target=postexport --project=landing-page
-
-          if [ -d ./dist/apps/landing-page/exported ]; then
-            echo "is_new_build=true" >> $GITHUB_ENV
-          fi
+          [ -d ./dist/apps/landing-page/exported ] && echo "is_new_build=true" >> $GITHUB_ENV
 
       - name: Deploy to Branch
         uses: JamesIves/github-pages-deploy-action@v4

apps/landing-page/project.json

@@ -7,7 +7,7 @@
       "executor": "nx:run-commands",
       "dependsOn": ["^build"],
       "options": {
-        "command": "yarn docs"
+        "command": "bash ./scripts/docs.sh"
       }
     },
     "build": {

libs/docs/src/config/github-docs-url.ts

@@ -0,0 +1 @@
+export const githubDocsUrl = 'https://github.com/devfile/devfile-web/tree/main/libs/docs/src/docs';

libs/docs/src/config/index.ts

@@ -1,3 +1,2 @@
-export const githubDocsUrl = 'https://github.com/devfile/devfile-web/tree/main/libs/docs/src/docs';
-
+export * from './github-docs-url';
 export * from './version';

libs/docs/src/docs/no-version/understanding-a-devfile-registry.md

@@ -6,8 +6,8 @@ description: Understanding a devfile registry
 A devfile registry is a service that stores and provides devfile stacks
 to Kubernetes developer tools like `odo`, Eclipse Che, and the OpenShift
 Developer Console. Therefore, you can access devfiles through the
-devfile registry. Devfile registries are based on the Oracle Cloud
-Infrastructure (OCI) Specification, and devfile stacks are stored as OCI
+devfile registry. Devfile registries are based on the Open Container
+Initiative (OCI) Specification, and devfile stacks are stored as OCI
 artifacts in the registry.
 
 Each devfile stack corresponds to a specific runtime or framework, such

nx.json

@@ -18,7 +18,6 @@
       "runner": "@nrwl/nx-cloud",
       "options": {
         "cacheableOperations": [
-          "prebuild",
           "build",
           "export",
           "postexport",