Skip to content

Conversation

@Pietfried
Copy link
Contributor

Describe your changes

This PR introduces documentation sources and build tooling for the new EVerest documentation, which applies the diataxis format. Every part of the documentation is sorted into one of these categories:

  • Tutorials
  • How-To-Guides
  • Explanations
  • References

We started with the documentation skeleton in the branch-protected featrue/docs-migration branch a few weeks ago and reviewed and merged single documentation bits seperately into this branch, which now contains the composition of the changes.

Many parts of the existing documentation of https://everest.github.io/nightly/ has been reused and/or revised. A lot of additional documentation has been added:

  • Quickstart Guides for getting started with SW and HW
  • External API including generated reference documentation
  • BringUp & Qualification
  • Dedicated Linux / Yocto sections /
  • Cross-compilation
  • Subsystems of EVerest

and much more.

A preview of the documentation is available on https://everest.github.io/everest-core .

Issue ticket number and link

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • I read the contribution documentation and made sure that my changes meet its requirements

@Pietfried Pietfried added the documentation Improvements or additions to documentation label Nov 28, 2025
krealyt and others added 27 commits December 8, 2025 16:04
…tory. (#1380)

It is the foundation for the integration of more documentation bits from https://github.com/EVerest/EVerest
into this structure.

Changes include:
* Docs build process and Sphinx configuration
* Diataxis skeleton dividing every part of the documentation into: Explaination, How-to-guide, Tutorial, Reference
* Added instructions how to build the documentation to everest-core README
* Generation of reference documentation

Signed-off-by: Krealyt <[email protected]>
Signed-off-by: Andreas Heinrich <[email protected]>
Signed-off-by: Piet Gömpel <[email protected]>
Co-authored-by: Piet Gömpel <[email protected]>
* doc(explanation): Add community channels to docs

Signed-off-by: Piet Gömpel <[email protected]>
---------

Signed-off-by: Piet Gömpel <[email protected]>
Co-authored-by: Piet Gömpel <[email protected]>
…inx (#1477)

* Refactor _find_sphinx_build macro to allow system installation of sphinx

Signed-off-by: Andreas Heinrich <[email protected]>

* Fix setting of _SPHINX_BUILD_EXECUTABLE

It needs to be a list, otherwise cmake will escape all whitespace which would then lead to a failure executing the command

Signed-off-by: Kai-Uwe Hermann <[email protected]>

---------

Signed-off-by: Andreas Heinrich <[email protected]>
Signed-off-by: Kai-Uwe Hermann <[email protected]>
Co-authored-by: Kai-Uwe Hermann <[email protected]>
* doc(tutorial): Added Plug&Charge tutorial to docs
---------

Signed-off-by: Piet Gömpel <[email protected]>
* doc(how-to): Add Configure Plug&Charge in EVerest
---------

Signed-off-by: Piet Gömpel <[email protected]>
* doc(tutorial): Add OCPP1.6 tutorial

---------

Signed-off-by: Piet Gömpel <[email protected]>
Signed-off-by: Piet Gömpel <[email protected]>
Signed-off-by: Piet Gömpel <[email protected]>
Signed-off-by: Piet Gömpel <[email protected]>
* doc(how-to): Add debug ISO15118 documentation
---------

Signed-off-by: Piet Gömpel <[email protected]>
* doc(tutorial): Add develop new modules
---------

Signed-off-by: Piet Gömpel <[email protected]>
* doc(linux/yocto): Added several documentation parts for Linux/Yocto integration
---------

Signed-off-by: Piet Gömpel <[email protected]>
Signed-off-by: Piet Gömpel <[email protected]>
…ging Regulations to documentation (#1494)

Signed-off-by: Piet Gömpel <[email protected]>
* doc(how-to): Add Renesas MPU docs

---------

Signed-off-by: Piet Gömpel <[email protected]>
… as part of EVerest doc (#1564)

* docs(api): Move asyncapi spec and provide HTMLs as part of EVerest doc
---------

Signed-off-by: Christoph Burandt <[email protected]>
* doc(how-to): Add BringUp documentation for basic, ac, dc and powermeter bringup
---------

Signed-off-by: Piet Gömpel <[email protected]>
* doc(explanation): Add adapt EVerest documentation
---------

Signed-off-by: Piet Gömpel <[email protected]>
* doc(getting-started): Added Getting Started guides for SW and HW
---------

Signed-off-by: Piet Gömpel <[email protected]>
Signed-off-by: Christoph Burandt <[email protected]>
@Pietfried Pietfried force-pushed the feature/docs-migration branch from 8d0bce3 to 78eeca2 Compare December 8, 2025 15:07
Pietfried and others added 6 commits December 8, 2025 16:08
Copy link
Contributor

@cburandt cburandt left a comment

Choose a reason for hiding this comment

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

Missing: The module configuration from originally #1432 which was closed in favour of #1492 which became #1577 after the security incident but never had the module configuration chapter.


get-started-sw
get-started-hw
/explanation/adapt-everest/index
Copy link
Contributor

Choose a reason for hiding this comment

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

This makes adapt-everest appear in the index for the second time (once below explanation and now also under explanation/getting-started)

Copy link
Contributor

Choose a reason for hiding this comment

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

Some modules link to yaml files (like this one to manifest <../manifest.yaml>_.) - this does not work in the generated docs.

Comment on lines 34 to 40
.. grid-item-card:: 🔌 EVerest APIs
:link: /explanation/adapt-everest/index
:link-type: doc

Learn about the APIs provided by EVerest that help you integrating
EVerest into your system and adapting it to your needs.

Copy link
Contributor

Choose a reason for hiding this comment

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

This links to both, EVerest APIs and Sub-Systems - change link name&explanation or remove the link (since it's linked on a higer level in the toc anyways)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I would like the APIs to be highlighted in the GettingStarted section. Removed it from the toctree

Copy link
Contributor

Choose a reason for hiding this comment

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

Remove index.rst for all BU modules or create them for each one?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Created it for all BU modules

Copy link
Contributor

Choose a reason for hiding this comment

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

Linked on the top-level index.rst, but not part of the TOC?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

added it

Select PWM off / X1, switch EV simulator to state A.
This should output constant +12 V on the CP line.

- ☐ Select AC coupling on the scope and verify the ripple noise. There
Copy link
Contributor

Choose a reason for hiding this comment

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

These boxes look awkward (here and in some other rst files). I think, dynamic checkboxes are not possible in the resulting html.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Agreed, just using simple bullets now

We provide several entry points for a fast start with EVerest.
Whether you want to do a software-based simulation or start
working with existing hardware, you will find your way here.

Copy link
Contributor

Choose a reason for hiding this comment

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

This is the only subpage with grid-itme-cards - on purpose?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It would probably be nice to have it for subpages explanation, how-to-guides, and tutorials as well.

Copy link
Contributor

Choose a reason for hiding this comment

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

I can do this.

.. tip::

You can download an SDK for the phyVERSO board here:
[SDK BaseCamp/phyVERSO](http://pionix-update.de/phyverso/1.0.0/phytec-ampliphy-rauc-glibc-x86_64-phyverso-basecamp-image-aarch64-toolchain-BSP-Yocto-Ampliphy-AM62x-PD23.2.1-phyVERSO-EVCS.sh).
Copy link
Contributor

Choose a reason for hiding this comment

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

since it's a link, it got to be what it is, but still a bit unfortunate that it uses "basecamp"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It was still a markdown link, fixed it.

##############################################

To get more information on EVerest and Renesas hardware, see here:
https://www.renesas.com/en/products/microcontrollers-microprocessors/rz-mpus/rz-partner-solutions/pionix-basecamp
Copy link
Contributor

Choose a reason for hiding this comment

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

a bit unfortunate that it uses "basecamp" in the link

Pietfried and others added 7 commits December 12, 2025 09:41
Signed-off-by: Piet Gömpel <[email protected]>
Signed-off-by: Piet Gömpel <[email protected]>
Signed-off-by: Piet Gömpel <[email protected]>
Signed-off-by: Christoph Burandt <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants