Move content into files and use nicer blocks

Signed-off-by: Marek Kubica <marek@tarides.com>

doc/tutorials/dune-package-management/setup.md

@@ -12,36 +12,34 @@ management for the very first time.
 The best way to work with the package management is to declare your
 dependencies in the `dune-project` file, like so:
 
-```dune
-(lang dune 3.17)
-(name test)
+::::{dropdown} `dune-project`
+:icon: file-code
 
-(package
-  (name test)
-  (depends
-    (ocaml (>= 4.14))))
-```
+:::{literalinclude} setup/dune-project
+:language: dune
+:::
 
 This setup will be very familiar to people who use Dune to generate their OPAM
 files as this is also exactly the information that is used to generate the
 files using the `generate_opam_files` stanza.
 
 The code we want to execute goes into our `test.ml`:
 
-```ocaml
-let langs = ["OCaml"; "Rust"]
+::::{dropdown} `test.ml`
+:icon: file-code
 
-let () =
-  let s = String.concat ", " langs in
-  Format.printf "Hello, %s!\n" s
-```
+:::{literalinclude} setup/test.ml
+:language: ocaml
+:::
 
 And finally we need to declare this module an executable using a `dune` file:
 
-```dune
-(executable
-  (public_name test))
-```
+::::{dropdown} `dune`
+:icon: file-code
+
+:::{literalinclude} setup/dune
+:language: dune
+:::
 
 ## Locking dependencies
 

doc/tutorials/dune-package-management/setup/dune

@@ -0,0 +1,2 @@
+(executable
+ (public_name test))

doc/tutorials/dune-package-management/setup/dune-project

@@ -0,0 +1,7 @@
+(lang dune 3.17)
+(name test)
+
+(package
+ (name test)
+ (depends
+  (ocaml (>= 4.14))))

doc/tutorials/dune-package-management/setup/test.ml

@@ -0,0 +1,5 @@
+let langs = ["OCaml"; "Rust"]
+
+let () =
+  let s = String.concat ", " langs in
+  Format.printf "Hello, %s!\n" s

doc/tutorials/index.md

@@ -7,4 +7,5 @@ These tutorials are hands-on lessons to learn about Dune.
 :maxdepth: 1
 
 developing-with-dune/index
+dune-package-management/index
 :::