vikram-dagger

Marked as draft since these are stubs atm.

> It might be worth to have a better architecture other than copy-pasting ? I have several guides on-the-way that are worth being ported to python / go You can...

I investigated the following options: - https://www.npmjs.com/package/docusaurus-graphql-plugin - https://www.npmjs.com/package/@edno/docusaurus2-graphql-doc-generator - https://www.npmjs.com/package/spectaql All 3 tools had difficulty generating API docs from our GQL schema files, due to numerous linter errors (see...

First cut of auto-generated docs included in https://github.com/dagger/dagger/pull/3160

I'm not very sure how to correct this since the output is based on the schema obtained from introspection - for auto-generated docs, we would probably need to find a...

I think we should leave it open as this may come up again for the GraphQL launch

My suggestion would be: - remove the detail about future architecture plans - move the information about the engine into an FAQ rather than have it on the SDK page...

@shykes @gerhard updated PR as per my previous suggestion and now awaiting review.

@shykes OK to add this to the docs? Asking because the engine might change, so would you prefer to wait, or add this now and update it later when/if the...

@shykes @mircubed I believe this topic is already covered in: - https://docs.dagger.io/sdk/go/959738/get-started/#step-4-create-a-single-build-pipeline - https://docs.dagger.io/544174/multistage-build Please let me know if OK to close?