Skip to content

[JAMES-3187] fixes most documentation generation#2925

Merged
Arsnael merged 1 commit intoapache:masterfrom
jeantil:doc/fixes
Jan 28, 2026
Merged

[JAMES-3187] fixes most documentation generation#2925
Arsnael merged 1 commit intoapache:masterfrom
jeantil:doc/fixes

Conversation

@jeantil
Copy link
Contributor

@jeantil jeantil commented Jan 28, 2026

Generating the documentation raised lots of warnings and errors with dead links and missing attributes.

I did not fix the customization section ( 3 errors ) as I am unsure how to fix these links. The corresponding documentation lies in server specific directories.

I also changed some code blocks to have syntax highlighting and a more consistent syntax at least within a file.

Generating the documentation raised lots of warnings and errors with dead links and missing attributes.

I did not fix the customization section ( 3 errors ) as I am unsure how to fix these links. The corresponding documentation lies in server specific directories.

I also changed some code blocks to have syntax highlighting and a more consistent syntax at least within a file.
Copy link
Contributor

@chibenwa chibenwa left a comment

Choose a reason for hiding this comment

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

Looks neat.

I bet now is about time to work on the overall content now that the form looks nicer...

@Arsnael Arsnael merged commit 188f8f5 into apache:master Jan 28, 2026
1 check passed
@jeantil
Copy link
Contributor Author

jeantil commented Jan 28, 2026

I bet now is about time to work on the overall content now that the form looks nicer...

The content is not so bad. I started building the documentation because I intended to find a place to write down what I learned about the BlobStore recently :d

From my pov, what's missing ( or the location is unclear or duplicated ) is

  • reference documentation on the configuration files.
  • how-tos

I'm a bit torn about the choice of using includes in the server's documentation. It makes it easier for users looking for a specific server's configuraton setup but it mostly duplicates content and makes linking to a specific configuration use case from other sections difficult (see customization for instance)

I noticed that the index of the configuration section for the basic server contained a lot of comments I haven't read it all yet, maybe that's where the reference configuration is supposed to live

@chibenwa
Copy link
Contributor

I'm a bit torn about the choice of using includes in the server's documentation.

The idea was to avoid duplication and thus ensure easier maintenance and that the documentation stays relevant.

It allows to build a configuration tailor made per application addresses a major weakness of historical maven site that mixes everything and did never know if what he reads apply to him.

@jeantil
Copy link
Contributor Author

jeantil commented Jan 28, 2026

I understand the idea of building tailored configuration per assembly, should we replicate this for the customization section then ?

@chibenwa
Copy link
Contributor

Some extension mechanisms like mailbox listeners do not make sense for eg smtp only servers so I would say yes.

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