Because we are an open-source project AND using docusaurus, Algolia should be free. Let's apply for it again, they didn't get back to us last time.

answer the following questions well

• How do I get access to Estuary?
• How to put data on Estuary?
• What are some gotchas? Things you have to work around
• How do I get data on Estuary?
• Key issues, explaining the difficulty of things, but showing how much faster we are than existing services
• Supported Platforms
• Explain how you can use any language, any library, any interface, etc

• pull homepage,
• #46
• fix merge conflict
• #44
• refresh API docs

our docs should have a proper home page instead of just an intro.

Right now the client library documentation is fairly naked. Let's add in:

• An explanation overall of what the client libraries are and do, that they are automatically generated and are kept in this repo https://github.com/application-research/estuary-clients and are generated using this docker image https://hub.docker.com/r/swaggerapi/swagger-codegen-cli which is a package of code in this repo: https://github.com/swagger-api/swagger-codegen
• For each of the language, build an onboarding set of instructions about how to use the code, install the client and build apps with it

brave browser supports ipfs pinning!

write a tutorial for

1. pinning data using brave
2. importing that data into estuary
3. may require "passing the origins too" https://filecoinproject.slack.com/archives/C016APFREQK/p1674762380721029?thread_ts=1674758909.757499&cid=C016APFREQK via @alvin-reyes 's suggestion on slack

• Get an API key
• Uploading your first file
• Listing your files

given slowness of getting confirmation on free algolia, let's set up paid to get the ball moving

the displayed curl code is correct, but when it runs it receives the error "details": "no multipart boundary param in Content-Type"

on further investigation this seems to be a common issue with using fetch - https://stackoverflow.com/questions/39280438/fetch-missing-boundary-in-multipart-form-data-post

may require a modification to the internal api library

https://docs.estuary.tech/Reference/API%20Clients/typescript-fetch/wiki/ContentApi#contentaddpost

We can integrate the page at https://docs.estuary.tech/swagger-ui-page into the docusuarus app easily at the same URL /swagger-ui-page

The new docusaurus page uses a slightly different api documentation that includes support for multiple langauges: https://whimsical-marzipan-4409a2.netlify.app/api/introduction/ and uses the postman library to generate code snippets for each API endpoint, so it's a cool light weight way to get code for a specific endpoint that does not integrate the swagger client apis.

Some open questions to me about how to do this:

1. Do we want to replace the new one for the old and update links / create a redirect?
2. Do we not like the new one and do we only want to use the old one?
3. Do we want find a place for both https://docs.estuary.tech/swagger-ui-page and https://whimsical-marzipan-4409a2.netlify.app/api/introduction/ ? - they're both fairly redundant but maybe both have a place

for example this link : https://whimsical-marzipan-4409a2.netlify.app/clients/java/docs/CollectionsApi#collectionsColuuidCommitPost

when you click the header the href isn't lined to the document section, and this is true across alll of the client languages

https://docusaurus.io/docs/search

has support for algolia free full text hosted search. i've made a request to join their program, waiting to get approval for the api key

Improve the introduction this page that explains how to use this resource and what it is:

link to the api documentation here: https://whimsical-marzipan-4409a2.netlify.app/api/introduction/

note the nearly blank introduction compared to a page like this: https://whimsical-marzipan-4409a2.netlify.app/api/create-a-new-collection

See this page on the old documentation for inspiration / text to include in the new repo https://docs.estuary.tech/swagger-intro

Following pages are within the "docs" section which generally are .md markup files, but because they require hitting an API they need to be JS react files. There doesn't seem to be a clear way to integrate react/js files into docs, but there must be some way to make it all work:

• give-feedback
• get an invite
• storage provider application
• chinese version of storage provider application