Wikijunior:Raspberry Pi/Contributing

The goal of this book is provide a useful free guide to the Raspberry Pi adapted from tutorials made by Cotswold Jam and others. The tutorials themselves are available at http://cotswoldjam.org/downloads. I have also archived these files on my GitHub and on the Wayback Machine.

To-do edit

  • Organise assets for Button Invaders
  • Suggestion for a Charlieplexed 7-LED "H"-shaped dice tutorial.
  • Suggestion for a game inspired by the Haynes electronics advent calendar such as Simon Says.
  • Raspberry Pi Zero cake tutorial with the printout
  • Introduction to Python tutorial
  • A No Pi! No Problem logo and wikibox which is similar to the current information and warning (uses prohibited symbol 🚫)?
  • All the images for the Cotswold Jam tutorials
  • Ensure all the source code files use h3 headings and line numbers
  • Introduction to the Raspberry Pi - the ports

Types of tutorials edit

There are 4 types of tutorial that Cotswold Jam taught:

  • Electronics tutorials use electronic components such as breadboards, resistors, LEDs, switches and jumper wires.
  • Minecraft: Pi Edition
  • w:Scratch tutorials teach the visual Scratch language which can be attempted on just about any platform (Windows, macOS, GNU/Linux, etc.).
  • w:Raspberry Pi OS is the new name for Raspbian, these tutorials are almost engtirely software based.

Of course, we can add others providing they are compatible with a Raspberry Pi and suitable for an 8-12 year old audience.

Tasks edit

Additional content edit

  • Add tutorials – They can be obtained from: http://cotswoldjam.org/downloads. We also accept 3rd party tutorials as long as they are available under a compatible licence (public domain or CC-BY-SA). Such as: https://seattleraspberryjam.weebly.com/projects.html
  • No Pi, No Problem! – Add instructions where possible for the Raspberry Pi OS and Scratch tutorials for setting up these to work on a standard computer running Windows, macOS or a GNU/Linux distro such as Ubuntu. We need documentation for:
  • Forward compatibility testing – Test that all of these tutorials work on the latest Rasberry Pi models! The latest model is the Raspberry Pi 4, as of November 2022. Also that any Python 2 tutorials have been modified to work with Python 3.
  • Introductions for each section

Wording edit

  • Improve wording in the chapters – the guides should be adjusted to read like a book and less like standalone leaflets. The depth and quality of guides should be consistent across chapters.
  • Conform to our Manual of Style – the guides should be run through spell-checking software such as Grammarly and usage of symbols such as en dashes (–) and em dashes (—) should be consistent. I've started marking components and GPIO pins in bold to make them easy to see.
  • Rename chapters – some chapters have names which make sense for standalone leaflets, but are not useful book chapter names.

Images edit

Add screenshots and diagrams to the tutorials edit

Upload them to the specially-made c:Category:Raspberry Pi tutorials on Wikicommons.

Create SVG diagramss edit

Ideally, all images that are not photographs nor screenshots should be c:SVG as per the Wikicommons guidelines – because they take up less file space and are infinitely re-scalable. Also w:Fritzing (see below) apparently exports to SVG.

Recreate some low-resolution diagrams/screenshots edit

Some images are low-resolution and may be unclear.

Fritzing diagrams for every electronics tutorial edit

Every electronics tutorial should have at least one Fritzing diagram. Preferably, multiple diagrams to help illustrate each step. Fritzing charges a minimum of €8 EUR (~$10 USD or ~£7 GBP) for binaries from their website, as of November 2022: https://fritzing.org/

New screenshots for Scratch 3 edit

Scratch 3 was released in January 2019 and has a different user interface. Make sure that the Scratch cat mascot is not included as it's a registered trademark! See: c:Commons:Deletion requests/Files containing Scratch trademarks

Scratch has its own markup language called Scratchblocks which can be used to rapidly create SVG block diagrams. Ideally all diagrams should be recreated this way: https://scratchblocks.github.io/