Skip to content

docs: Move BuildElement's "Built-in functionality" to a new page#2122

Open
juergbi wants to merge 1 commit intomasterfrom
jbilleter/doc-buildelement
Open

docs: Move BuildElement's "Built-in functionality" to a new page#2122
juergbi wants to merge 1 commit intomasterfrom
jbilleter/doc-buildelement

Conversation

@juergbi
Copy link
Copy Markdown
Contributor

@juergbi juergbi commented May 8, 2026

The documentation of how to use the common features provided by the BuildElement base class is currently part of the API reference even though it's more relevant to project authors than plugin developers.

This moves that section to a new page in the "Reference" section, next to other plugin-specific documentation.

The main content of the new page is unchanged but I've tweaked the initial paragraphs to make sense with the structure change.

This is a replacement for #2103 with proper links and TOC entry (a bit quirky with Sphinx but I think it looks and works reasonably well now).

The documentation of how to use the common features provided by the
`BuildElement` base class is currently part of the API reference even
though it's more relevant to project authors than plugin developers.

This moves that section to a new page in the "Reference" section, next
to other plugin-specific documentation.

Co-authored-by: Dom Rodriguez <dom.rodriguez@codethink.co.uk>
@juergbi
Copy link
Copy Markdown
Contributor Author

juergbi commented May 8, 2026

From #2103 (review) (@tmewett):

My 2c: the main issue I have is that BuildElement is an API name, and if we're trying to document this for users it might make sense to frame this in a different way.

I've linked the new page as "Build Elements" in the TOC and tried to make the intro paragraph a bit more understandable for project authors. If you have any suggestions how to further improve that, please let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant