Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

Guys, we used to have link here to `<https://docs.airbyte.io/>`. Does anybody remember why did we get rid of it? Should revert changes? Or we do not need that logic anymore? Currently it is commented out.

my opinion is that we should add again. also created <https://github.com/airbytehq/airbyte/issues/3543|an issue> :p

yeah. i think we may have just gotten rid of it by accident.

Is there a way to map connectorId to url in docs?

```{"sourceDefinitionId":"2af123bf-0aaf-4e0d-9784-cb497f23741a","name":"Appstore","dockerRepository":"airbyte/source-appstore-singer","dockerImageTag":"0.2.1","latestDockerImageTag":"0.2.2","documentationUrl":"<https://hub.docker.com/r/airbyte/source-appstore-singer>","icon":""}```

This is how the definition looks like. Is it safe to assume that all sources will be under

`docsUrl/source or destination/conector.name.toLowerCase()` ?

it should be the documentationUrl that is provided in the spec: airbyte-integrations/connectors/source-appstore-singer/source_appstore_singer/spec.json

we shouldn't use the one in  source definition, we should use the one in spec.

i think we'd prefer to use the actual value in the spec, otherwise if we ever change the naming convention or the structure of the docs (which happens a lot) this is going to be a gotcha.

but then we will be able to display link only after we receive response from backend after we select connector in dropdown. Is it possible that we may have some useful info in docs while source is still loading or it is fine to display it after actual schema is loading?

I was just updating some stuff in exact same place so decided to fix it too :slightly_smiling_face:

oh. that's true. let's try just using the string in the spec for now. i think accidentally providing a bad link will be worse than the link showing up a little later.