docs: refactor documentation website

[ctrlc03]

Description

Organize in folders various entries to provide better readability.

## Related Issue(s)

fix #1342

Confirmation

• I have read and understand MACI's contributor guidelines and code of conduct.
• I have read and understand MACI's GitHub processes.
• I have read and understand MACI's testing guide.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
maci-website	✅ Ready (Inspect)	Visit Preview	May 17, 2024 7:11am

[kittybest]

do you think we could also add _category_.json to solidity doc and type doc?
else we might put some simple description to the index page, they look so empty now 🤔
.
another question, would you think the quick start and guides part should be put together? since for me, as a new user who just wanna try to run it first, would see the installation page first then the deployment page.

[0xmad]

@ctrlc03 thanks!

[ctrlc03]

do you think we could also add _category_.json to solidity doc and type doc?

Yes that's very needed, was thinking to do that in another PR if that's ok

another question, would you think the quick start and guides part should be put together?

I see, yea that makes sense. And maybe move the integration doc to the developer specific resources?

[kittybest]

do you think we could also add _category_.json to solidity doc and type doc?

Yes that's very needed, was thinking to do that in another PR if that's ok

Yes!

another question, would you think the quick start and guides part should be put together?

I see, yea that makes sense. And maybe move the integration doc to the developer specific resources?

I think the current structure is good!
But where are the solidity-docs and typedoc?

[ctrlc03]

do you think we could also add _category_.json to solidity doc and type doc?

Yes that's very needed, was thinking to do that in another PR if that's ok

Yes!

another question, would you think the quick start and guides part should be put together?

I see, yea that makes sense. And maybe move the integration doc to the developer specific resources?

I think the current structure is good! But where are the solidity-docs and typedoc?

they are inside developers-resources/ inside typescript there's the typedoc + cli docs and inside smart-contracts there's solidity docs