1 How the notebook is laid out

The Mental Map follows the website exactly. Its six numbered sections are the six fields, each section has six subsections (the topics), and each subsection has six subsubsections (the destinations). Numbers match the site, so 1.2.2 is Science & Engineering, Physics, Quantum Mechanics, and the hexagon for every page links to its own heading.

Science & Engineering is section 1:

A destination that has no notes yet contains a single line, Open for notes. Replacing that line is how a destination gets filled.

2 Before you start

• Work in the pandas_projects folder. The file to edit is mental_map.tex at its root.

• Every outline heading has a comment line above it and a label after it, for example:

  % atlas: Science-and-Engineering/Physics/Optics
\subsubsection{Optics}\label{sec:optics}

  Search for the comment to jump to a destination. Never edit, move or delete these two lines: the website uses them to link each hexagon to its section, and the build stops if one is missing.

• Keep the Gemini export itself out of the repository if it contains anything private. Copy only the parts you rewrite into the notebook.

3 From the chat log to a destination

1. Export the conversation. Copy the useful Gemini responses into a scratch file, keeping your own questions next to them for context.

2. Sort by destination. Split the scratch file by topic and give each piece the number of the subsubsection where it belongs, using the table above or the dropdowns in the Request a change form on the Mental Map page. When a piece fits two places, put it in one and add a cross-reference in the other.

3. Check before you keep. A chat answer can be confidently wrong. Verify each claim, equation and number against a textbook, lecture notes or a primary source, and note the source. Mark anything you could not check with Unverified: in italics rather than presenting it as fact.

4. Rewrite in your own words. Short paragraphs, one idea per subheading. Keep equations in LaTeX, numbered displays in an equation or align environment, and inline maths between single dollar signs.

5. Paste under the destination. Replace the Open for notes line with your notes. For subheadings below a destination use \subsubsubsection{...}, and one level further \subparagraph{...}. Do not add \section, \subsection or \subsubsection headings: those levels are the website’s outline and change only in site_content/atlas.py.

6. Label what you will refer to. Give equations labels with a topic prefix, such as \label{eq:optics-snell}, and refer to them with \eqref. Refer to another destination with its label, for example Section~\ref{sec:thermodynamics}. Every label must be unique in the file.

7. Add figures carefully. Save PNG or JPEG images in tex_images/mental_map/, in a folder named after the topic, and include them with that root-relative path. Remote, absolute and PDF figures are refused; export a PNG instead. Only use images you made or are allowed to reuse, and credit them in the caption.

4 Build and check

1. Rebuild both copies of the site:
   python -B -m site_content.build --also-local

2. Run the tests, which check that every outline marker, label and image is in place:
   python -B -m unittest discover -s site_content/tests

3. Preview the local site and open the Mental Map. Look for a box titled LaTeX conversion notes at the top of the document: it lists unresolved references, duplicate labels and unsupported commands. Fix every note, then check that your equations are numbered and your figures appear.

5 Publish

1. Commit mental_map.tex and any new images in pandas_projects. Stage files by name; never stage private folders such as the résumé sources or the original work-term report.

2. Commit and push the site repository, liammspandasprojects. Only that repository is served at liammspandasprojects.org; pushing pandas_projects alone does not change the live site.

3. Add a line to the Change Log under Website Changes saying which destinations were filled.

6 Checklist

• Notes sit under the right destination, below its outline heading.

• The % atlas: comment and its label are unchanged.

• Every claim has been checked, or is marked as unverified.

• Equations, labels and figures follow the conventions above.

• The build shows no conversion notes and all tests pass.

• Both repositories are committed, and the site repository is pushed.

Download original LaTeX source