Improve introduction of modules and imports

Thanks @RyanBrewer317!

2 files changed, 25 insertions, 0 deletions

diff --git a/src/content/chapter0_basics/lesson03_unqualified_imports/code.gleam b/src/content/chapter0_basics/lesson03_unqualified_imports/code.gleam
new file mode 100644
index 0000000..2708f25
--- /dev/null
+++ b/src/content/chapter0_basics/lesson03_unqualified_imports/code.gleam
@@ -0,0 +1,10 @@
+// Import the module and one of its functions
+import gleam/io.{println}
+
+pub fn main() {
+  // Use the function in a qualified fashion
+  io.println("This is qualified")
+
+  // Or an unqualified fashion
+  println("This is unqualified")
+}
diff --git a/src/content/chapter0_basics/lesson03_unqualified_imports/en.html b/src/content/chapter0_basics/lesson03_unqualified_imports/en.html
new file mode 100644
index 0000000..ca83f2f
--- /dev/null
+++ b/src/content/chapter0_basics/lesson03_unqualified_imports/en.html
@@ -0,0 +1,15 @@
+<p>
+  Normally functions from other modules are used in a
+  <em>qualified</em> fashion, meaning the name used to refer the module goes
+  before function name with a dot between them. For example,
+  <code>io.println("Hello!")</code>.
+</p>
+<p>
+  It is also possible to specify a list of functions to import from a module in
+  an <em>unqualified</em> fashion, meaning the function name can be used without
+  the module <em>qualifier</em> (the name and the dot) before it.
+</p>
+<p>
+  Generally it is best to use qualified imports, as this makes it clear where
+  the function is defined, making the code easier to read.
+</p>