You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The URLs for serverless documentation will be significantly different than the URLs for the classic docs. Though we don't have all of the content created yet, writers can start filling in the new list for the pages that already exist.
Then when we generate the output specification files we just need the tools (or some manual method) to ensure that we can pull in the appropriate table.csv file.
Thanks @lcawl. That makes sense to have a separate file for serverless doc URLs (e.g. table_serverless.csv).
The next step for the client team will be to update the schema.json format to allow for both URLs to be imported there, and also update the various generation pipelines to take it into account.
🚀 Feature Proposal
In order to have documentation links that are appropriate for Serverless, I believe we need a second serverless-specific file like https://github.com/elastic/elasticsearch-specification/blob/main/specification/_doc_ids/table.csv
The URLs for serverless documentation will be significantly different than the URLs for the classic docs. Though we don't have all of the content created yet, writers can start filling in the new list for the pages that already exist.
Then when we generate the output specification files we just need the tools (or some manual method) to ensure that we can pull in the appropriate
table.csv
file.Related:
Motivation
We need our specifications to point to the appropriate set of documentation.
Example
For example, the page https://www.elastic.co/guide/en/elasticsearch/reference/master/search-aggregations.html in the classic docs is https://docs-staging.elastic.dev/serverless/elasticsearch/explore-your-data-aggregations in the serverless (WIP) docs.
The text was updated successfully, but these errors were encountered: