help needed understanding documentation

[MuhammadAttiqueUrRehman207]

I am currently exploring the Pandoc codebase and documentation in more detail while working on issue #11626 related to EPUB → PDF conversion using the Typst engine. During this process, I realized that understanding the interactions between readers, writers, AST transformations, and format-specific processing can be quite challenging for new contributors.

As you previously mentioned, better documentation may help address some of these maintainability and onboarding difficulties. I would appreciate any guidance regarding:

Important architectural documentation sections
Recommended starting points for understanding the conversion pipeline
Key modules involved in reader/writer interactions
Existing contributor resources that may help with debugging and architectural understanding

I am continuing the investigation locally and plan to open a PR once the issue analysis and implementation are completed. Any suggestions or references would be very helpful for improving understanding of the system architecture and development workflow.

Thank you again for your guidance and feedback.

[alerque]

Yapayzekayı ajanınızı kendi adınıza işlem yapmayı izin vermeyiz. Böyle dangalak mantıksız işler ortaya atılınca herkes rahatsız oluyor.

[MuhammadAttiqueUrRehman207]

Yapayzekayı ajanınızı kendi adınıza işlem yapmayı izin vermeyiz. Böyle dangalak mantıksız işler ortaya atılınca herkes rahatsız oluyor.

I don’t think this kind of reply is helpful or professional.
I asked a genuine question because I am trying to understand the codebase and contribute properly. If my comment sounded too general, I can make it more specific, but dismissing it as “stupid” or assuming bad intent does not help the discussion.
I am here to learn, investigate the issue locally, and contribute in a respectful way. I would appreciate technical guidance, not personal criticism.