-
Notifications
You must be signed in to change notification settings - Fork 0
Description
In addition to the more internal processes, we should document how to do things related to WCRS. Some of this may need to be little more than a link to other resources. Other cases should have extra details about how it is to be used more specifically for WCRS. The same main storage options (and more) as in #1 are available for this as well. While some information will be slanted to WCRS, especially getting started, most of it should be useful for the general WCRS target audience.
For this, I lean more towards a new github repository specifically for documentation. The line between the information to be put here, and that belongs with the processes information is a bit vague. Make suggestions about what you think belongs in either place, with a bit of the reasons why.
- markdown
- editing content
- viewing content without posting to github
- using git and github for storing and displaying markdown content
- documents, issue postings, wiki pages
- formatting content using markdown
- advanced formatting: mixing html with markdown
- git
- Arudino, Raspberry Pi, other resources for robot intelligence
- programming languages for robotics (at wcrs)
- Arduino¦C/C++/Wiring, Python, node.js, Scratch, Lego
- tools for programming
- Arduino IDE
- Arduino Create online
- Adrublocky
- Scratch
- Lego
- firmata
- node.js, Johnny-Five
- «programmers» text editor
- atom
- sublime text
- emacs
- nano
- electronics
- Fritzing
- Circuit Simulation
- hardware modelling
- Fusion 360
The markdown and git section of the above is intended, especially initially, to be focused on getting WCRS contributors the basic capabilities to add content. I stuck it here, because although it is anticipated to include 'process', it is also targeted to be quite general, and useful for other members to get started with their own projects that would benefit from recording some history and learnings. Suggestions for places to put this? More stuff to add to the list?