Thoughts on integration & integration docs

[mantrachain-support]

Referencing: https://github.com/skip-mev/connect/blob/main/docs/developers/integration.mdx

I'd like to make a suggestion that I think will make connect much easier to integrate.

Currently, in the docs we have:

• app wiring (occurs in app.go)
• ABCI extensions (should occur in a file named app/abci_extensions.go)
• Oracle client (should occur in app/oracle_client.go)
• setup markets (should occur in app/setup_markets.go)

providing these files in their complete form, for use as pasta, is likely the best way to present the integration step of the process.

After that, there could be another document:

Referencing: https://github.com/skip-mev/connect/blob/main/docs/developers/customization.mdx

and in the customization document, we could guide developers through any possible tweaks.

[Eric-Warehime]

We can look into this--for now the Skip team takes a large role in most of the integrations so we're pretty comfortable with weaving these components into the existing app structure. The other consideration is that each app is in general structured differently and can potentially be constructed differently w/r/t depinject, etc. so it's likely that 1 size fits all wouldn't track very well in practice here.

[ethsdev]

Hello @zrbecker, sorry for leaving a comment here without respecting the team rules. As a blockchain developer, I think my tech stack is fit for the team project. So I want to prove my skills by solving some team issues and join the team as a full-time developer. Could you give me a test task?