We’re getting close to shipping guides. Here’s what we’ve accomplished so far:
- We have stubbed out all the most-googled topics related to math, programming, and tools like Git and SQL
- We have a great README.md thanks to @hkuz and other contributors
- Each article has a nice stub with a link directly to the file on GitHub where a contributor can edit it
- We’ve successfully on-boarded several contributors who are actively writing articles.
- @Bouncey has gotten Gatsby (1.0.0!) building successfully and deploying to Netlify. We have linting, continuous integration, and continuous deployment set up to make contribution as smooth as possible.
In short, we are geared up for launching our own wiki for new coders.
- making the sidenav more like DevDocs.io (https://github.com/freeCodeCamp/guides/issues/66)
- getting the search bar to show suggested results after a few keystrokes (https://github.com/Bouncey/react-freecodecamp-search/issues/30)
- Making it work with AMP (https://github.com/freeCodeCamp/guides/issues/65) Yes, I know. AMP is getting a lot of hate right now. But our goal here is not to generate ad revenue like most websites. Our goal is to create helpful articles read by as many people as possible, and AMP will help with that.
In the meantime, I encourage everyone to contribute as many articles as possible. Even if your articles are a bit superficial, this is better than just a stub.
The analogy I like to use is this: by writing articles, we’re putting rocks into a giant rock tumbler that is the community.
The rocks are rough when they go in. But the community will constantly update them. Before long, those rocks will become polished stones.
Shipping guides is a high priority for all of us - as is getting as many proverbial rocks into the tumbler as quickly as possible, so they have plenty of time to become polished stones.