docs: add "Build Your First Game" tutorial

[ayo-ola0710]

What was done

Added a comprehensive, step-by-step tutorial for new Rust developers onboarding to Cougr and Soroban. This tutorial addresses the Stage 3 onboarding gap identified in the UX strategy by building a complete, tested, and deployable 2D grid game (based on the spawn_and_move pattern).
It explicitly maps ECS primitives (Components, Systems) to Soroban's unique constraints, specifically highlighting instance storage differences, gas costs, and resource limits. It also introduces local testing using GameHarness and Scenario, ending with Stellar CLI deployment instructions.

Close #250
Close #249

[drips-wave]

@ayo-ola0710 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[ayo-ola0710]

"I have completed the cougr-site setup with the mdBook IA skeleton and the cross-repository sync script!

You can review the repository here: https://github.com/ayo-ola0710/cougr-site And see the live deployed site here: https://ayo-ola0710.github.io/cougr-site/

Let me know if you would like me to transfer ownership of this repository to the organization, or if you prefer to fork it from my account!"

[salazarsebas]

"I have completed the cougr-site setup with the mdBook IA skeleton and the cross-repository sync script!

You can review the repository here: https://github.com/ayo-ola0710/cougr-site And see the live deployed site here: https://ayo-ola0710.github.io/cougr-site/

Let me know if you would like me to transfer ownership of this repository to the organization, or if you prefer to fork it from my account!"

awesome

[salazarsebas]

Great tutorial content for #250 — clear steps, good callouts on storage/gas/resource limits, nice that it links out to PATTERNS.md and examples/ at the end.

However, this PR's description says it closes #249, and that part isn't delivered: #249 asks for a cougr-site repo scaffolded with mdBook (6-section IA, a sync mechanism from docs/*.md, placeholder pages). This PR only adds a single markdown file to this repo's docs/start/.

I see you already built that scaffold at https://github.com/ayo-ola0710/cougr-site (book.toml, src/, sync.py). Could you bring that code into a folder inside this monorepo (e.g. cougr-site/) and add it to this PR, so #249's deliverable actually lands here rather than living in a separate, disconnected repo? Once that's folded in, this PR would cover both #249 and #250.

[ayo-ola0710]

@salazarsebas pls review

[salazarsebas]

The tutorial content itself (docs/start/build-your-first-game.md) looks great and covers #250 well. Separate concern: this PR also commits the full built mdBook output (cougr-site/book/..., ~80 files of generated HTML/fonts/CSS) directly into this repo. Per #249, the docs site is meant to live in its own cougr-site repository that builds from docs/*.md here rather than duplicating/vendoring the built output into this repo. Could you rebase onto main, drop the committed book/ build artifacts from this PR, and split the docs-site scaffolding (#249) into a PR against a separate cougr-site repo? That'd let the tutorial content land cleanly on its own.

[ayo-ola0710]

@salazarsebas
Thank you for the clarification! I've rebased and dropped the site scaffolding from this PR so it only contains the tutorial content for #250.

For #249, I have the docs-site scaffold fully built in its own separate repository here: https://github.com/ayo-ola0710/cougr-site (it includes the GitHub Action sync mechanism and the mdBook setup). How would you like to proceed with merging that part? Should I transfer ownership of that repository to the organization, or if you want to create an empty salazarsebas/cougr-site repo for you to open a PR against.

[salazarsebas]

Great tutorial content for #250 — clear steps, good callouts on storage/gas/resource limits, nice that it links out to PATTERNS.md and examples/ at the end.

However, this PR's description says it closes #249, and that part isn't delivered: #249 asks for a cougr-site repo scaffolded with mdBook (6-section IA, a sync mechanism from docs/*.md, placeholder pages). This PR only adds a single markdown file to this repo's docs/start/.

I see you already built that scaffold at https://github.com/ayo-ola0710/cougr-site (book.toml, src/, sync.py). Could you bring that code into a folder inside this monorepo (e.g. cougr-site/) and add it to this PR, so #249's deliverable actually lands here rather than living in a separate, disconnected repo? Once that's folded in, this PR would cover both #249 and #250.

As I told you here, I would like you to solve issue 249 to make a folder here in this same repository and include everything here, please
@ayo-ola0710

[ayo-ola0710]

@salazarsebas
So, this PR ports the cougr-site documentation directly into the main Cougr repository to centralize our code and docs.

Here is a quick summary of how this was structured:

Created a new cougr-site/ directory at the root of the project to house the documentation.
Ported over the source files: I brought in the src/ directory (which contains all the markdown files), book.toml, sync.py, and .gitignore.
Excluded build artifacts: I intentionally excluded the generated book/ directory from being copied and committed. This ensures we are only tracking the source markdown and keeping the repository history clean from compiled static files.

Is these ok to close the two isses
or do you still want me to create them as two seperate PRs