Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a "Getting started" page #99

Open
erlend-sh opened this issue Aug 29, 2018 · 2 comments
Open

Add a "Getting started" page #99

erlend-sh opened this issue Aug 29, 2018 · 2 comments

Comments

@erlend-sh
Copy link
Member

I suggest adding a new top-level page titled "Getting started". Its purpose would be to provide a quick and safe answer to the many budding Rust game developers who are wondering "where should I start?"

@kvark already made one such write-up:

https://gist.github.com/kvark/840c8cadf755b0d822b331222b0c3095

I would prefer something a tad more fleshed out, but the essence of it is spot-on. It's also encouraging to see that a year later it is still good advice, which speaks to the growing stability of the ecosystem.

How to write the article as democratically as possible is of course an issue. A more elaborate process could be considered for the future, but for now I would suggest the following:

  • Start a new issue: "RFC: Getting started 09-2018", provide a skeleton similar to kvark's and solicit feedback from the Rust community. Invite engine creators and game developers to make their case.
  • Once the discussion has gone on for two weeks or so (which might not be much discussion at all at this early stage) the AWGY team makes an executive decision and publishes the final draft to the website.
  • The "Getting started" page will link back to the draft discussion for transparency.
@doppioslash
Copy link
Collaborator

@erlend-sh Agreed on adding a Getting Started article.
Though isn't that whole procedure a tad overcomplicated for one simple article?
I'd rather just draft one, and then people can send pull requests to tweak it, or entirely change it or whatever.

@erlend-sh
Copy link
Member Author

Yeah I agree, I was getting a bit ahead of myself. Best to just start it off as a living document like you're suggesting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants