🐞 Bug Bash wk 2🐞 Add: second lesson and images

.gitignore

@@ -7,6 +7,12 @@ tmp/
 __pycache__
 *notes-from-review.md
 *.idea*
+<<<<<<< HEAD
 
 .vale.ini
 styles/*
+=======
+# grammar / syntax checkers
+.vale.ini
+styles/
+>>>>>>> 7e6685f (Rename diagram)

index.md

@@ -71,7 +71,8 @@ by the community now! Join our community review process or watch development of
 :::{card} ✿ Tutorials ✿
 :class-card: left-aligned
 
-[What is a Python package?](/tutorials/intro)
+* [What is a Python package?](/tutorials/intro)
+* [Make your code installable](/tutorials/1-installable-code)
 
 :::
 ::::
@@ -188,14 +189,14 @@ If you have questions about our peer review process or packaging in general, you
 
 This is a living guide that is updated as tools and best practices evolve in the Python packaging ecosystem. We will be adding new content over the next year.
 
+
 ```{toctree}
 :hidden:
-:caption: Testing
-
+:caption: Tutorials
 Tutorials  <tutorials/intro>
-
 ```
 
+
 ```{toctree}
 :hidden:
 :caption: Documentation

package-structure-code/python-package-distribution-files-sdist-wheel.md

@@ -6,6 +6,7 @@
 You need to build your Python package in order to publish it to PyPI (or Conda). The build process organizes your code and metadata into a distribution format that can be uploaded to PyPI and subsequently downloaded and installed by users. NOTE: you need to publish a sdist to PyPI in order for conda-forge to properly build your package automatically.
 :::
 
+(building-package)=
 ## What is building a Python package?
 
 To [publish your Python package](build_workflow) and make it easy for anyone to install, you first need to build it.