link more stuff in between

Author: ricardo-devis-agullo

website/docs/components/publishing-to-a-registry.md

@@ -17,12 +17,13 @@ Publishing is the process of uploading your packaged component to a registry whe
 
 ## Prerequisites
 
-Before publishing components, ensure you have:
+Publishing assumes:
 
-- An OpenComponents registry set up and accessible
-- A properly structured component with valid `package.json`
-- Registry credentials (if authentication is required)
-- Compatible CLI and Node.js versions
+1. A reachable registry (see [Registry Configuration](../registry/registry-configuration))
+2. A component folder that passes `oc dev` validation
+3. OC CLI installed (see [CLI install](cli.md#install-the-cli))
+
+That's all you need—no extra global setup.
 
 ## Basic Publishing Workflow
 
@@ -174,79 +175,7 @@ This validates your component and simulates the publish process without actually
 
 ## Troubleshooting
 
-### Common Errors
-
-**Unauthorized (401)**
-
-```
-Error: Unauthorized
-```
-
-**Solution**: Provide valid credentials using `--username` and `--password` options, or ensure your authentication is properly configured.
-
-**Component Already Exists**
-
-```
-Error: Component already exists: [email protected]
-```
-
-**Solution**: Update the version in your `package.json` file before publishing.
-
-**CLI Version Mismatch**
-
-```
-Error: OC CLI version needs upgrade
-```
-
-**Solution**: Update your CLI to the required version:
-
-```sh
-npm install -g oc@latest
-```
-
-**Node Version Incompatibility**
-
-```
-Error: Node CLI version needs upgrade
-```
-
-**Solution**: Update Node.js to a compatible version as specified in the error message.
-
-**Invalid Component Name**
-
-```
-Error: Component name not valid
-```
-
-**Solution**: Ensure your component name follows naming conventions (lowercase, no spaces, valid npm package name format).
-
-**Invalid Component Version**
-
-```
-Error: Component version not valid
-```
-
-**Solution**: Use semantic versioning (e.g., "1.0.0", "2.1.3") in your `package.json`.
-
-**Package Validation Failed**
-
-```
-Error: Package is not valid
-```
-
-**Solution**: Check that your component has:
-
-- Valid `package.json` with required `oc` configuration
-- All required files (template, server.js if needed)
-- Proper component structure
-
-**Template Version Incompatibility**
-
-```
-Error: Your template requires a version of OC higher than X.X.X
-```
-
-**Solution**: Either upgrade your registry or downgrade your template requirements.
+For error messages and advanced diagnostics, refer to the [CLI Troubleshooting Guide](cli.md#installation-troubleshooting). It covers authentication, versioning, validation failures, and more.
 
 ### Debugging Tips
 

website/docs/intro.md

@@ -203,58 +203,14 @@ See the dedicated [CLI guide](components/cli#install-the-cli) for installation,
 
 # Setup a library
 
-At the moment the only supported libraries are Amazon S3 & Google Storage.
+See detailed guides for:
 
-- S3 - Create an account and for S3 get the API credentials; you will need them while setting up the registry.
-- Google Storage - Create an account and setup your [gcloud](https://cloud.google.com/sdk/docs/#install_the_latest_cloud_tools_version_cloudsdk_current_version) cli.
+- [S3 library adapter](registry/registry-configuration#s3)
+- [Google Cloud Storage adapter](registry/registry-using-google-storage)
 
 # Setup a registry
 
-The registry is a node.js express app that serves the components. You can have multiple registries connected to a library, but you can't have multiple libraries connected to a registry.
-First, create a dir and install oc:
-
-```sh
-mkdir oc-registry && cd oc-registry
-npm init
-npm install oc --save
-```
-
-For Google Storage registry configuration's documentation, [look at this page](/docs/registry/registry-using-google-storage).
-
-Then on the entry point, what you need on an `index.js` file is:
-
-```js
-var oc = require("oc");
-
-var configuration = {
-  verbosity: 0,
-  baseUrl: "https://my-components-registry.mydomain.com/",
-  port: 3000,
-  tempDir: "./temp/",
-  refreshInterval: 600,
-  pollingInterval: 5,
-  s3: {
-    key: "your-s3-key",
-    secret: "your-s3-secret",
-    bucket: "your-s3-bucket",
-    region: "your-s3-region",
-    path: "//s3.amazonaws.com/your-s3-bucket/",
-    componentsDir: "components",
-  },
-  env: { name: "production" },
-};
-
-var registry = oc.Registry(configuration);
-
-registry.start(function (err, app) {
-  if (err) {
-    console.log("Registry not started: ", err);
-    process.exit(1);
-  }
-});
-```
-
-For the registry configuration's documentation, [look at this page](/docs/registry/registry-configuration).
+A full configuration reference and production-ready examples live in [Registry Configuration](registry/registry-configuration). Start there when you need to spin up your first registry.
 
 ## What Should I Read Next?