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
I think we should convert the Zelig online documentation generation to pkgdown. This has a number of advantages:
Easily enable close integration with the internal documentation, which is currently different from the online documentation in ways that are potentially confusing to users
Closer test integration as the online docs could be tested every time Zelig goes through a build check. This would enable more accurate documentation (e.g. docs that don't include errors) and provide another "test surface" for finding errors.
Simplify package development toolchain.
The text was updated successfully, but these errors were encountered:
I think we should convert the Zelig online documentation generation to pkgdown. This has a number of advantages:
Easily enable close integration with the internal documentation, which is currently different from the online documentation in ways that are potentially confusing to users
Closer test integration as the online docs could be tested every time Zelig goes through a build check. This would enable more accurate documentation (e.g. docs that don't include errors) and provide another "test surface" for finding errors.
Simplify package development toolchain.
The text was updated successfully, but these errors were encountered: