Skip to content

docs: Start a compiler development guide outside the main table of contents - #17120

Open
djolertrk wants to merge 1 commit into
argotorg:developfrom
walnuthq:docs/compiler-guide
Open

djolertrk wants to merge 1 commit into
argotorg:developfrom
walnuthq:docs/compiler-guide

Conversation

@djolertrk

Copy link
Copy Markdown
Contributor

Adds docs/compiler-guide/ for pages aimed at compiler developers, with its own table of contents titled "Solidity Compiler Development Guide". The main table of contents does not link it.

ethdebug_internal_debug_info.rst moves there from docs/internals/ under a new "Implementation plans" category. Its index entries are removed: Sphinx builds a single index for the whole documentation, so they would show up next to the user-facing pages.

Split out of #16990 as suggested in the review. That PR adds a second category, "Feature guides", with the ethdebug implementation page.

@djolertrk

Copy link
Copy Markdown
Contributor Author

@cameel cc

@cameel

cameel commented Oct 15, 2026

Copy link
Copy Markdown
Collaborator

Also CC @clonker. This would be the place for our implementation docs.

Comment thread docs/compiler-guide/index.rst Outdated
They are not part of the main table of contents.

.. toctree::
:maxdepth: 2

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's reduce the depth here. The way it is now, the headings from inside the pages show up on the list. That would be fine for the sidebar where they fold, but will be too noisy when we add more pages here.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, reduced to 1

Comment thread docs/compiler-guide/index.rst Outdated
@@ -1,7 +1,3 @@
:orphan:

.. index:: ! ethdebug, ! debug info

@cameel cameel Oct 19, 2026 •

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Continuing from #16990 (comment):

I think that having index entries would be fine, it's just that they should not be the first thing the user finds. For example here it could be something like ethdebug;implementation. Or generally something more specific than just ethdebug or debug info.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, makes sense. I added ethdebug; internal debug info as a plain subentry, not a main one, so it doesn’t come up first.

@cameel cameel self-assigned this Oct 19, 2026
…ntents

Add a separate table of contents for pages aimed at compiler developers,
which the main one does not link, and move the specification of the
ethdebug internal debug info there under the implementation plans.
Sphinx has one index for the whole documentation, so the page is indexed
under a specific subentry, ethdebug; internal debug info, rather than
as a main entry for ethdebug and debug info.
@djolertrk
djolertrk force-pushed the docs/compiler-guide branch from f676e62 to 61c31d7 Compare October 19, 2026 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants