Reference 'next steps' in intro as well.

Makefile

@@ -1,11 +1,13 @@
 archive.pdf: intro.pdf requirements.pdf design-doc.pdf \
     binary/techreview-ryan.pdf techreview-daniel.pdf binary/techreview-matt.pdf \
     binary/blog-ryan.pdf blog-daniel.pdf binary/blog-matt.pdf \
+    binary/poster.pdf \
     readme.pdf resources.pdf reflection.pdf listings.pdf images.pdf review.pdf todo.pdf
 	ruby toc.rb
 	pdfjam --no-tidy --outfile archive.pdf -- intro.pdf requirements.pdf design-doc.pdf \
 	    binary/techreview-ryan.pdf techreview-daniel.pdf binary/techreview-matt.pdf \
 	    binary/blog-ryan.pdf blog-daniel.pdf binary/blog-matt.pdf \
+	    binary/poster.pdf \
 	    readme.pdf resources.pdf reflection.pdf listings.pdf images.pdf review.pdf todo.pdf
 
 todo.pdf: todo.tex

intro.tex

@@ -162,6 +162,9 @@ became more difficult. While previously, hardware components were distributed am
 did meaningfully affect the project deliverables, as the team was able to set up a system for remotely
 modifying the physical components' firmware.
 
+For information on how to pick up the project, see the \emph{Next Steps} section of the \emph{Foreword}, and
+Appendix 4.
+
 \subsection*{A Note on Tables of Contents}
 A large portion of this document is generated from existing files relating to this project, such as the design document,
 the various tech reviews, and the weekly blog posts. Many of these have their own tables of contents. These

toc.rb

@@ -20,7 +20,8 @@ pdf_structure = [
   all_pages("Ryan Alder's Blog Posts", "binary/blog-ryan.pdf"),
   all_pages("Danila Fedorin's Blog Posts", "blog-daniel.pdf"),
   all_pages("Matthew Sessions' Blog Posts", "binary/blog-matt.pdf"),
-  all_pages("Project Documentation and READMEs", "readme.pdf"),
+  all_pages("Expo Poster", "binary/poster.pdf"),
+  all_pages("Project Documentation", "readme.pdf"),
   all_pages("Learning Resources", "resources.pdf"),
   all_pages("Conclusions and Reflections", "reflection.pdf"),
   all_pages("Appendix 1: Essential Code Listings", "listings.pdf"),