feat: add engineering section

[zivkovicmilos]

Description

This PR populates the engineering section for gno.land

[zivkovicmilos]

@ajnavarro
Not sure why the CI is failing

EDIT: Seems to be checking that the benchmark website is down for some reason, not an issue

[ajnavarro]

EDIT: Seems to be checking that the benchmark website is down for some reason, not an issue

It is down because the custom action runner is not deployed yet, so the benchmark workflow is not being executed.

[moul]

Hey team, I just added a new file and asked Guilhem to review the changes on this working branch.

PR Link: Link

I recommend merging this PR once it's in good shape, so we can iterate and refine the details as needed.

Feel free to keep PR concise instead of going into too much detail. Let's keep the momentum going!

[ajnavarro]

Maybe we should comment benchmarks link until it is rendering results to avoid the CI error on future PRs. Apart from that, LGTM.

[zivkovicmilos]

Maybe we should comment benchmarks link until it is rendering results to avoid the CI error on future PRs. Apart from that, LGTM.

I temporarily removed the link:
cd6ad99

Will open up an issue for it so we don't forget

[zivkovicmilos]

@moul

Do you want us to merge this out, or do you want us to wait for @gfanton to give a look?

I want to get Alexis' eyes on this so he can help tighten the color palette / design of the docs before we go live

[gfanton]

@zivkovicmilos This guide looks really cool and comprehensive. However, one point I find a little confusing is when I reached the meeting section. I was confused to see that in gno.land; I may be wrong, but I would personally prefer to have this in a separate section along with Team.

[zivkovicmilos]

@zivkovicmilos This guide looks really cool and comprehensive. However, one point I find a little confusing is when I reached the meeting section. I was confused to see that in gno.land; I may be wrong, but I would personally prefer to have this in a separate section along with Team.

@gfanton
I love the idea, and have moved the Meetings section to be under Team:
320f5e0

[moul]

@zivkovicmilos: Do you want us to merge this out, or do you want us to wait for @gfanton to give a look?

Since the repo is new, I propose focusing on either structure-oriented PRs or content-oriented PRs. Structure takes precedence, and we can allocate more time for content discussions.

As long as we avoid merging anything significantly flawed, I recommend merging once the improvements are in place and reviewed.|

[moul]

For meetings, maybe we can just link to https://github.com/gnolang/meetings for a single source of truth.

[zivkovicmilos]

@moul

I've updated the doc to point to our meetings repository. I'll open up a PR on that repo to spruce up the README a bit
04fda52

[zivkovicmilos]

@moul

Merging this out now as all comments seem resolved.
We need this PR merged out to proceed with fine tuning the guide