Added new sections

Author: sleipnir

docs/sdks.md

@@ -16,8 +16,12 @@ Spawn currently has or develops SDK for the following languages:
 | Rust            | 🚧      | https://github.com/eigr/spawn-rust-sdk                      |
 | Spring Boot     | ✅      | https://github.com/eigr/spawn-springboot-sdk                |
 
+Full documentation for each language can be found in each of their repositories, but [here](sdks/index.md) we provide a quick introduction to each.
+
 [Back to Index](index.md)
 
+[Jump to language support index](sdks/index.md)
+
 [Next: Custom Resources](crds.md)
 
 [Previous: Getting Started](getting_started.md)

docs/sdks/go/actor_invocation.md

@@ -0,0 +1,7 @@
+# Actor Invocation
+
+TODO
+
+[Next: Workflows](workflows.md)
+
+[Previous: Actors](actors.md)

docs/sdks/go/actors.md

@@ -0,0 +1,40 @@
+# Go Actors
+
+Spawn defines the following types of Actors:
+
+* **Named Actors**: Named actors are actors whose name is defined at compile time. They also behave slightly differently 
+Then unnamed actors and pooled actors. Named actors when they are defined with the stateful parameter equal to True are 
+immediately instantiated when they are registered at the beginning of the program, they can also only be referenced by 
+the name given to them in their definition.
+
+* **Unnamed Actors**: Unlike named actors, unnamed actors are only created when they are named at runtime, that is, 
+during program execution. Otherwise, they behave like named actors.
+
+* **Pooled Actors**: Pooled Actors, as the name suggests, are a collection of actors that are grouped under the same name 
+assigned to them at compile time. Pooled actors are generally used when higher performance is needed and are also 
+recommended for handling serverless loads.
+
+## Stateless Actors
+
+TODO
+
+## Stateful Actors
+
+TODO
+
+
+## Considerations about Spawn actors
+
+Another important feature of Spawn Actors is that the lifecycle of each Actor is managed by the platform itself. 
+This means that an Actor will exist when it is invoked and that it will be deactivated after an idle time in its execution. 
+This pattern is known as [Virtual Actors](#virtual-actors) but Spawn's implementation differs from some other known 
+frameworks like [Orleans](https://www.microsoft.com/en-us/research/project/orleans-virtual-actors/) or 
+[Dapr](https://docs.dapr.io/developing-applications/building-blocks/actors/actors-overview/) 
+by defining a specific behavior depending on the type of Actor (named, unnamed, pooled, and etc...).
+
+For example, named actors are instantiated the first time as soon as the host application registers them with the Spawn proxy. 
+Whereas unnamed and pooled actors are instantiated the first time only when they receive their first invocation call.
+
+[Next: Actor Invocation](actor_invocation.md)
+
+[Previous: Getting Started](getting_started.md)

docs/sdks/go/getting_started.md

@@ -0,0 +1,7 @@
+# Go Getting Started
+
+TODO
+
+[Next: Actors](actors.md)
+
+[Previous: SDKs](../../sdks.md)

docs/sdks/go/projections.md

@@ -0,0 +1,7 @@
+# Go Projections
+
+TODO
+
+[Next: SDKS](../../sdks.md)
+
+[Previous: Workflows](workflows.md)

docs/sdks/go/workflows.md

@@ -0,0 +1,25 @@
+# Go Workflows
+
+Spawn has several mechanisms to facilitate integration between your actors or your application with the outside world. Below are some types of integration that Spawn provides:
+
+## Broadcast
+
+TODO
+
+## Side Effects
+
+TODO
+
+## Forward
+
+TODO
+
+## Pipe
+
+TODO
+
+Forwards and pipes do not have an upper thread limit other than the request timeout.
+
+[Next: Projections](projections.md)
+
+[Previous: Actor Invocation](actor_invocation.md)

docs/sdks/index.md

@@ -0,0 +1,39 @@
+# Spawn Language Support
+
+# Table of Contents
+
+01. [Dart](dart/getting_started.md)
+    - 1.2. [Actors](dart/actors.md) 
+    - 1.3. [Actors Invocations](dart/actor_invocation.md)
+    - 1.4. [Workflows](dart/workflows.md)
+    - 1.5. [Projections](dart/projections.md)
+02. [Elixir](elixir/getting_started.md)
+    - 2.2. [Actors](elixir/actors.md) 
+    - 2.3. [Actors Invocations](elixir/actor_invocation.md)
+    - 2.4. [Workflows](elixir/workflows.md)
+    - 2.5. [Projections](elixir/projections.md)
+03. [Go](go/getting_started.md)
+    - 3.2. [Actors](go/actors.md) 
+    - 3.3. [Actors Invocations](go/actor_invocation.md)
+    - 3.4. [Workflows](go/workflows.md)
+    - 3.5. [Projections](go/projections.md)
+04. [Java](java/getting_started.md)
+    - 4.2. [Actors](java/actors.md) 
+    - 4.3. [Actors Invocations](java/actor_invocation.md)
+    - 4.4. [Workflows](java/workflows.md)
+    - 4.5. [Projections](java/projections.md)
+05. [Node](node/getting_started.md)
+    - 5.2. [Actors](node/actors.md) 
+    - 5.3. [Actors Invocations](node/actor_invocation.md)
+    - 5.4. [Workflows](node/workflows.md)
+    - 5.5. [Projections](node/projections.md)
+06. [Python](python/getting_started.md)
+    - 6.2. [Actors](python/actors.md) 
+    - 6.3. [Actors Invocations](python/actor_invocation.md)
+    - 6.4. [Workflows](python/workflows.md)
+    - 6.5. [Projections](python/projections.md)
+07. [Rust](rust/getting_started.md)
+    - 7.2. [Actors](rust/actors.md) 
+    - 7.3. [Actors Invocations](rust/actor_invocation.md)
+    - 7.4. [Workflows](rust/workflows.md)
+    - 7.5. [Projections](rust/projections.md)