Skip to content

Conversation

@AnsMelanie
Copy link
Collaborator

This page provides guidance for developers on how to generate DPF documentation locally and preview it. The generation steps still need to be updated, as they are currently based on my setup, which differs from the external development environment.

@PProfizi
Copy link
Contributor

@ansys-akarcher did you try it out locally?

$env:ANSYSLMD_LICENSE_FILE = "1055@lyolmserv1.win.ansys.com"
```

### 2. Install the DPF server
Copy link
Contributor

Choose a reason for hiding this comment

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

You also have to install ansys-dpf-core and jinja2

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Done

@@ -0,0 +1,188 @@
# DPF documentation: Generation and local preview

This section details how to:
Copy link
Contributor

Choose a reason for hiding this comment

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

Add when this guide is useful (custom install, custom plugins/operators, to preview doc for a dev version)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Done

@AnsMelanie
Copy link
Collaborator Author

@PProfizi
I updated the guidelines by installing everything from scratch on my machine. There are still a few points to complete together.

@AnsMelanie AnsMelanie requested a review from PProfizi September 29, 2025 12:57
Copy link
Contributor

@PProfizi PProfizi left a comment

Choose a reason for hiding this comment

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

Several small comments, but a big proposition to change the source and target of copied files.
The idea would be to update the DevRelDocs repository files instead of what is proposed now.
A notable advantage would be that the Edit this page link on every page would work and redirect to the right file on the DevRelDocs GH project.
This would also be better as in the future we will not need to clone PyDPF-Core, but we will still need to clone DevRelDocs.


This step prepares your computer with the necessary software and files.

#### Download the pydpf-core
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
#### Download the pydpf-core
#### Download the pydpf-core project

1. Navigate to `pydpf-core/doc/source/operators-doc/`
2. Copy all contents to your website's `docs` folder

### Step 4: Add complete DPF Framework documentation
Copy link
Contributor

Choose a reason for hiding this comment

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

You can move the whole operator doc generation after this step, this way it is the generation script which overrides the DPF framework documentation, no?

Copy link
Contributor

Choose a reason for hiding this comment

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

Also, it would be much better to copy-paste to the DevRelDocs repository as we then have the option to directly edit the page in GH:
image

Copy link
Contributor

Choose a reason for hiding this comment

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

This tries to send you directly to the file on GH, which is very nice!
But you need to be within the git repository of interest.

Copy link
Contributor

Choose a reason for hiding this comment

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

I tested copying the docfx.json file generated by docfx in MyDPFDocs into the DevRelDocs repository and generated the website. The documentation is properly generated and the Edit this page link works.

2. **Copy the documentation carefully:**
- **Important:** Do NOT copy the `operator-specifications` folder from the source, as this would overwrite your custom DPF operators documentation.
- Select all other files and folders from the source (excluding `operator-specifications`).
- Copy and paste them into your website's `docs` folder.
Copy link
Contributor

Choose a reason for hiding this comment

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

It asks whether to replace the toc.yml. Yes or No?

Copy link
Contributor

Choose a reason for hiding this comment

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

The operator-specifications/operator-specifications.md file must actually be copied.

AnsMelanie and others added 3 commits September 30, 2025 14:53
Co-authored-by: Paul Profizi <100710998+PProfizi@users.noreply.github.com>
Co-authored-by: Paul Profizi <100710998+PProfizi@users.noreply.github.com>
Co-authored-by: Paul Profizi <100710998+PProfizi@users.noreply.github.com>
Co-authored-by: Paul Profizi <100710998+PProfizi@users.noreply.github.com>
@AnsMelanie AnsMelanie merged commit a25a2c7 into main Oct 1, 2025
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.

4 participants