Skip to content

rustwasm bookshelf #41

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

Merged
merged 6 commits into from
Mar 6, 2019
Merged

rustwasm bookshelf #41

merged 6 commits into from
Mar 6, 2019

Conversation

DebugSteven
Copy link
Contributor

This PR fleshes out the docs.md file to provide some
context about what the Rust and WebAssembly resources are
and what the reader might want to know before jumping into
these books. This PR is a continuation of @alexcrichton's PR
to merge the documentation for Rust and WebAssembly to one
location
.

The docs.md format is inspired by "The Rust Bookshelf".
Once this bookshelf is merged, it might be nice to send the
docs team a PR to add a link to the Rust and WebAssembly
Bookshelf under the Specialize Rust section so that more
people can find this information in the general docs too!
I'd be happy to send that PR if that's something that would
be useful. I'd would appreciate feedback on what the
Rust and WebAssembly section should say. The Embedded
Working Group is under the Specialize Rust section
currently, if you'd like to look at an example.

Tentatively, I think this would work well as a description
to link to the Rust and WebAssembly Working Group and
the bookshelf:

## WebAssembly

To use Rust in your web browser or to interop with JavaScript, check out the resources maintained by
the [WebAssembly Working Group].

[WebAssembly Working Group]: https://github.com/rustwasm

### The Rust and WebAssembly Bookshelf

[The Rust and WebAssembly Bookshelf] contains resources for those just getting started with Rust and WebAssembly to those that would like a deeper dive into the various tools and crates in the rustwasm project.

[The Rust and WebAssembly Bookshelf]: https://rustwasm.github.io/docs.html

alexcrichton and others added 3 commits January 17, 2019 11:53
This PR is aimed at making the this repository, and the
`rustwasm.github.io` domain, the one stop shop for all documentation for
Rust and WebAssembly. Currently we have a number of sources of documentation:

* https://rustwasm.github.io/book - a tutorial and guide to Rust and WebAssembly
* https://rustwasm.github.io/wasm-bindgen - a tutorial and guide
  specific to `wasm-bindgen`
* https://rustwasm.github.io/wasm-pack - a tutorial and guide
  specific to `wasm-pack`
* https://rustwasm.github.io/ - the Rust and WebAssembly blog

This commit reorganizes all of these properties to instead be deployed
in this repository in one location, hopefully making it easier to
discover more of them and also cross-link between them. The setup here
is somewhat similar to the Rust documentation itself, comprising of a
number of books.

When this site is built it will clone the book, wasm-bindgen, and
wasm-pack repositories. The latter two will be reset to their most
recent tag, matching the most recently published version on crates.io.
All books are then compiled with `mdbook` and placed into the output here.

The current set is then laid out as follows:

* https://rustwasm.github.io/ - landing page, button to install
  wasm-pack, links everywhere else
* https://rustwasm.github.io/blog.html - new home for the blog
* https://rustwasm.github.io/docs.html - dispatch point for documentation

I'm hoping that we can centralize here by using
https://rustwasm.github.io if anyone wants an entry point or an
easy-click installer and using `/docs.html` as the main location for
documentation.

Once this lands I'd like to update the deployments of the book,
wasm-bindgen, and wasm-pack. All those books will gain a banner saying
they're a "nightly preview" with links to the officially published
versions. This means that visiting https://rustwasm.github.io/book will
have a banner saying you should go to
https://rustwasm.github.io/docs/book instead basically. The landing page
at https://rustwasm.github.io/wasm-pack will probably stay for now (and
the installer page will definitely stay), but we likely won't link to it
much any more.

Finally for a deployment strategy I hope to turn this into a daily cron
job for this repository. That means we'll redeploy everything at least
once a day, picking up any changes naturally. If we want to manually
trigger a redeploy, however, we can simply reexecute the previous build
on Travis.
@alexcrichton alexcrichton requested a review from fitzgen March 5, 2019 15:24
Copy link
Member

@fitzgen fitzgen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is so so so great -- thank you @DebugSteven!!

Apologies for the late review, I guess it slipped through my inbox :-|

@fitzgen
Copy link
Member

fitzgen commented Mar 5, 2019

Will merge as soon as the inline suggestions are addressed :)

@fitzgen
Copy link
Member

fitzgen commented Mar 5, 2019

I'd be happy to send that PR if that's something that would
be useful.

+1000

I'd would appreciate feedback on what the
Rust and WebAssembly section should say.

What you've written in the original comment sounds great to me. The only nitpick I have is that I'd use the full "interoperate" instead of "interop" :-p

fitzgen and others added 3 commits March 5, 2019 20:19
Co-Authored-By: DebugSteven <[email protected]>
Co-Authored-By: DebugSteven <[email protected]>
Co-Authored-By: DebugSteven <[email protected]>
@DebugSteven
Copy link
Contributor Author

Thank you for the review on this!
Also it's only Tuesday, I'd say that's pretty fast turn around for review. :)

@alexcrichton
Copy link
Contributor

As a follow up I've sent a number of PRs to indicate that the gh-pages documentation we're primarily using today is for unpublished versions and the official versions are now in this repository's published documentation:

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

Successfully merging this pull request may close these issues.

3 participants