You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the documentation generated by zig build docs for the zBench project lacks guides. These guides are essential for users to understand the library beyond the auto-generated API references. They provide context, examples, and deeper explanations of the library's use and capabilities.
Detailed Description
The autogenerated API section is helpful for users already familiar with zBench, but for new users or those looking to understand advanced usage patterns, guides are indispensable. The absence of these guides represents a significant gap in our documentation.
Proposed Solution
We need to create and integrate handwritten guides into our zig-autodoc output. This can be done by specifying markdown files to include in the top-level doc comment of our root file (zbench.zig). Here's an example of how to reference these guides:
Currently, the documentation generated by
zig build docs
for the zBench project lacks guides. These guides are essential for users to understand the library beyond the auto-generated API references. They provide context, examples, and deeper explanations of the library's use and capabilities.Detailed Description
The autogenerated API section is helpful for users already familiar with zBench, but for new users or those looking to understand advanced usage patterns, guides are indispensable. The absence of these guides represents a significant gap in our documentation.
Proposed Solution
We need to create and integrate handwritten guides into our zig-autodoc output. This can be done by specifying markdown files to include in the top-level doc comment of our root file (zbench.zig). Here's an example of how to reference these guides:
Action Items
docs/
folder at the root of the project).zbench.zig
as shown above.The text was updated successfully, but these errors were encountered: