All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: dev@dpdk.org
Subject: UX Bug in Sphinx HTML Layout for Programming Guide (and maybe other guides?)
Date: Wed, 13 Jan 2016 12:26:29 -0500	[thread overview]
Message-ID: <20160113172629.GA9710@mhcomputing.net> (raw)

When you go to this link:

http://dpdk.org/doc/guides/prog_guide/perf_opt_guidelines.html

There is a bug in the Sphinx layout, where the subchapters of a chapter are
invisible even after the chapter is clicked.

It is a pain when you are trying to figure out the different sections in a 
widely variable chapter like the performance chapter, to know which section to 
read without having to click one-by-one to find the right part.

I am not sure about what it would take to show the subchapters in the outline 
view to make this easier for someone to figure out. Or maybe a TOC for a 
chapter at the beginning of the chapter?

This would really help a lot.

Sincerely,
Matthew.

             reply	other threads:[~2016-01-13 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 17:26 Matthew Hall [this message]
2016-01-14 12:12 ` UX Bug in Sphinx HTML Layout for Programming Guide (and maybe other guides?) Mcnamara, John
2016-01-15 16:23 ` Mcnamara, John
2016-01-16  8:19   ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160113172629.GA9710@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.