content: update the board count and homepage text

Signed-off-by: deadprogram <[email protected]>

Author: deadprogram

content/_index.md

@@ -20,7 +20,7 @@ title: "TinyGo Home"
 {{% blocks/lead color="secondary" %}}
 TinyGo brings the [Go programming language](https://golang.org) to embedded systems and to the modern web by creating a new compiler based on [LLVM](https://llvm.org/).
 
-You can compile and run TinyGo programs on over 94 different microcontroller boards such as the [BBC micro:bit](https://www.microbit.co.uk/) and the [Arduino Uno](https://store.arduino.cc/usa/arduino-uno-rev3/). [Click here for the complete list](/docs/reference/microcontrollers)
+You can compile and run TinyGo programs on over 100 different microcontroller boards from maker boards such as the [BBC micro:bit](https://www.microbit.co.uk/) and the [Arduino Uno](https://store.arduino.cc/usa/arduino-uno-rev3/), to industrial processors from [Nordic Semiconductor](https://www.nordicsemi.com/) and [ST Microelectronics](https://www.st.com/). [Click here for the complete list](/docs/reference/microcontrollers)
 
 TinyGo can also produce [WebAssembly (WASM)](https://webassembly.org/) code which is very compact in size. You can compile programs for web browsers, as well as for server and edge computing environments that support the [WebAssembly System Interface (WASI)](https://github.com/WebAssembly/WASI) family of interfaces.
 

content/docs/guides/contributing/boards.md

@@ -0,0 +1,39 @@
+---
+title: "Adding runtime support for new processors"
+weight: 1
+description: >
+  How to add runtime support to a new processor.
+---
+
+In order for a processor to support `time.Sleep()` and other things you normally expect, there are some functions that need to be implemented in the runtime for that processor.
+
+## runtime timers/sleep
+
+Functions that need to be implemented:
+
+```go
+// timeUnit defines the type of the unit of time used for that processor per tick.
+// can be measured in nanoseconds, microseconds, or milliseconds.
+// the important part is that it be consistent for any particular processor.
+type timeUnit int64
+
+// ticksToNanoseconds converts ticks to nanoseconds
+func ticksToNanoseconds(ticks timeUnit) int64
+
+// nanosecondsToTicks converts nanoseconds  to ticks
+func nanosecondsToTicks(ns int64) timeUnit
+
+// sleepTicks should sleep for d number of ticks.
+func sleepTicks(d timeUnit)
+
+// ticks returns the elapsed time since reset as a number of timeUnit ticks
+func ticks() timeUnit
+```
+
+Defining the `timeUnit` is crucial, since the unit of time for most processors is usually dependant on the system clock settings.
+
+Based on that initial information, the functions `ticksToNanoseconds()` and `nanosecondsToTicks()` can be implemented in a fairly straightforward fashion.
+
+It is with the function `sleepTicks()` that implementation details become very important. This function needs to be able to yield the processor to perform other tasks while it is waiting, in order for it to work the way that you expect with Go routines.
+
+Lastly the `ticks()` function is needed, in order for many `time` package functions to work.

content/docs/reference/microcontrollers/_index.md

@@ -8,7 +8,7 @@ description: |
 
 TinyGo lets you run Go directly on microcontrollers.
 
-TinyGo has support for 85 different boards and devices such as the Arduino Nano33 IoT, Adafruit Circuit Playground Express, BBC micro:bit and more. Click on a board name below to see the what features are supported for the given hardware.
+TinyGo has support for over 100 different boards and devices such as the Arduino Nano33 IoT, Adafruit Circuit Playground Express, BBC micro:bit and more. Click on a board name below to see the what features are supported for the given hardware.
 
 Support for some boards and processor types are more complete than others.
 As of early 2023, boards using the following microcontrollers are