Skip to content

Restructure API page#718

Open
carme-hp wants to merge 8 commits intomasterfrom
update-api-overview
Open

Restructure API page#718
carme-hp wants to merge 8 commits intomasterfrom
update-api-overview

Conversation

@carme-hp
Copy link
Member

Fixes #715

@carme-hp carme-hp requested a review from MakisH February 17, 2026 17:23
@carme-hp
Copy link
Member Author

I have restructured the pages using bullet points + bold letters
image

The design does not look particularly appealing to me. I also tested alternatives:

  • bullet points (not bold)
image
  • blockquote
image
  • table
image
  • table (not bold)
image

Let me know which of the options above you prefer. Feel free to suggest another option.

Copy link
Member

@MakisH MakisH left a comment

Choose a reason for hiding this comment

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

Thanks for the updates! Looks good overall.

I don't mind the boldface, but without would also be fine.

I would not use a blockquote (semantically different). I would also not use a table with one column, as shown in the alternatives.

I guess a table with a title column is not supported in Markdown / this Markdown flavor. But the current style is fine (for me) anyway.

## C++ Bindings

## Bindings
Extensive documentation on the C++ API is available on [the preCICE API doxygen pages for the latest release](https://precice.org/doxygen/main/classprecice_1_1Participant.html), or [see more options](dev-docs-sourcedocs.html).
Copy link
Member

Choose a reason for hiding this comment

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

From what I understood from the discussion, we now want to remove the dev-docs-sourcedocs.html (and redirect from that to this page). This sentence can then include the rest of the options as well.

Ideally, I would make this another bullet point.

Copy link
Member Author

Choose a reason for hiding this comment

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

Not sure what to do here. Here's my suggestion:
image

Copy link
Member

Choose a reason for hiding this comment

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

I would add an additional bullet point for the develop, and I would list both the API and rest, as currently:

Image

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.

Structure of the API overview page, relation to source documentation

2 participants

Comments