Answers.Body: <p>The <a href="https://kindlegen.s3.amazonaws.com/AmazonKindlePublishingGuidelines.pdf" rel="nofollow noreferrer">Amazon Publishing Guidelines</a> has sample code for making a nested html TOC.</p>
  
  <p>It's on page 16</p>
  
  <pre><code>&lt;div&gt;Section 1&lt;/div&gt; 
  &lt;div style="margin-left:2%;"&gt;Chapter 1&lt;/div&gt; 
  &lt;div style="margin-left:2%;"&gt;Chapter 2&lt;/div&gt; 
  &lt;div style="margin-left:2%;"&gt;Chapter 3&lt;/div&gt; 
  &lt;div style="margin-left:4%;"&gt;Subchapter 1&lt;/div&gt; 
  &lt;div style="margin-left:4%;"&gt;Subchapter 2&lt;/div&gt; 
  &lt;div style="margin-left:2%;"&gt;Chapter 4&lt;/div&gt; 
  &lt;div style="margin-left:4%;"&gt;Subchapter 1&lt;/div&gt; 
  &lt;div&gt;Section 2&lt;/div&gt; 
   ... 
  </code></pre>
  
  <p>Now here's an alternate way to do the same thing: </p>
  
  <pre><code>&lt;style&gt; div.chapter { margin-left: 1em} 
   div.subchapter { margin-left: 2em} &lt;/style&gt; 
  &lt;div&gt;Section 1&lt;/div&gt; 
  &lt;div class="chapter"&gt;Chapter 1&lt;/div&gt; 
  &lt;div class="chapter"&gt;Chapter 2&lt;/div&gt; 
  &lt;div class="chapter"&gt;Chapter 3&lt;/div&gt; 
  &lt;div class="subchapter"&gt;Subchapter 1&lt;/div&gt; 
  &lt;div class="subchapter"&gt;Subchapter 2&lt;/div&gt; 
  &lt;div class="chapter"&gt;Chapter 4&lt;/div&gt; 
  &lt;div class="subchapter"&gt;Subchapter 1&lt;/div&gt; 
  &lt;div&gt;Section 2&lt;/div&gt; ...
  </code></pre>
  
  <p>I've never tried it, but I assume it will work. </p>
  
  <p>Also, I found another working example for nested TOC in the book <strong>EPUB3 Best Practices</strong> by Matt Garrish and Markus Gylling. The code they used depending on very sophisticated CSS for the NAV element. I'm guessing that this is only an EPUB solution and wouldn't work for the Kindle. </p>
  
  <p>FURTHER THOUGHTS: It's not mentioned in the Amazon Publishing Guidelines, but I assume that all of this html is inside the <code>&lt;nav epub:type="toc"&gt;</code> element (leading me to wonder why the elements here are all DIVs instead of LIs). </p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-24T02:14:55.750Z
Answers.Text: NCX files are deprecated after epub3 ( http://www.idpf.org/epub/301/spec/epub-publications.html#ncx-superseded ) , and if my memory serves me correctly, Kindle doesn't pay attention to them anymore. The NAV element is very important because it provides both the logical TOC and the inline TOC. That said, I'm not sure that using margin-left accomplishes the goal of indenting subchapters in the logical TOC.
Answers.UserDisplayName: idiotprogrammer
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-24T02:16:50.780Z
Answers.Text: The section on NCX  might be out of date. That said, there is  an easy way to verify way to verify that Kindle ignores the NCX/NAV. Hand edit one chapter title there so it's different from what's in the NAV file. (I'll report back to confirm)
Answers.UserDisplayName: idiotprogrammer
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-16T15:43:28.850Z
Answers.LastActivityDate: 2018-10-16T16:02:12.940Z
Answers.LastEditDate: 2018-10-16T16:02:12.940Z
Answers.UserDisplayName: idiotprogrammer
Body: <p>I've created an epub that works great.  It has daily meditations, for a total of 366.  In my epub, the TOC is nested, so if I want to go to October 15, I click on October, the dates expand out 1 - 31, then I click on 15.  When I converted it to Mobi, however, on my Kindle the TOC is like:</p>
  
  <pre><code>January
  1    
  2
  3
  4
  .
  .
  .
  February
  1
  2
  3
  4
  .
  .
  .
  and so on to Dec 31.  
  </code></pre>
  
  <p>How do I fix my menu to be nested like the epub?</p>
  
  <p>So far everything else is looking fine on the mobi.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-16T15:28:30.753Z
Comments.Text: how are you creating your mobi file?  How are you creating Nested menus in epub?
Comments.UserDisplayName: idiotprogrammer
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-21T00:33:09.667Z
Comments.Text: Welcome to SE ebooks. Your question seems fine, but I have no answer. However I added two relevant tags, which may attract more users.
Comments.UserDisplayName: babou
Tags: <kindle><epub><conversion><mobi><table-of-contents>
Title: Nested menus in Mobi
UserDisplayName: Cody S
ThreadText: # Nested menus in Mobi
  
  (Asked by: username_0 on 2018-10-15)
  
  I've created an epub that works great.  It has daily meditations, for a total of 366.  In my epub, the TOC is nested, so if I want to go to October 15, I click on October, the dates expand out 1 - 31, then I click on 15.  When I converted it to Mobi, however, on my Kindle the TOC is like:
  January
  1    
  2
  3
  4
  .
  .
  .
  February
  1
  2
  3
  4
  .
  .
  .
  and so on to Dec 31.  
  
  How do I fix my menu to be nested like the epub?
  So far everything else is looking fine on the mobi.
  
  **Tags:** kindle, epub, conversion, mobi, table-of-contents
  
  > **Comments:**
  > **username_1**: how are you creating your mobi file?  How are you creating Nested menus in epub?  
  > **username_2**: Welcome to SE ebooks. Your question seems fine, but I have no answer. However I added two relevant tags, which may attract more users.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-10-16. Score: 1
  
  The Amazon Publishing Guidelines has sample code for making a nested html TOC.
  It's on page 16
  Section 1 
  Chapter 1 
  Chapter 2 
  Chapter 3 
  Subchapter 1 
  Subchapter 2 
  Chapter 4 
  Subchapter 1 
  Section 2 
   ... 
  
  Now here's an alternate way to do the same thing: 
   
  Section 1 
  Chapter 1 
  Chapter 2 
  Chapter 3 
  Subchapter 1 
  Subchapter 2 
  Chapter 4 
  Subchapter 1 
  Section 2 ...
  
  I've never tried it, but I assume it will work. 
  Also, I found another working example for nested TOC in the book EPUB3 Best Practices by Matt Garrish and Markus Gylling. The code they used depending on very sophisticated CSS for the NAV element. I'm guessing that this is only an EPUB solution and wouldn't work for the Kindle. 
  FURTHER THOUGHTS: It's not mentioned in the Amazon Publishing Guidelines, but I assume that all of this html is inside the  element (leading me to wonder why the elements here are all DIVs instead of LIs).
  
  > **Comments:**
  > **username_1**: NCX files are deprecated after epub3 ( http://www.idpf.org/epub/301/spec/epub-publications.html#ncx-superseded ) , and if my memory serves me correctly, Kindle doesn't pay attention to them anymore. The NAV element is very important because it provides both the logical TOC and the inline TOC. That said, I'm not sure that using margin-left accomplishes the goal of indenting subchapters in the logical TOC.  
  > **username_1**: The section on NCX  might be out of date. That said, there is  an easy way to verify way to verify that Kindle ignores the NCX/NAV. Hand edit one chapter title there so it's different from what's in the NAV file. (I'll report back to confirm)  
  
  ---
  
  