Good question
Internally, docgen relies on Robot Framework’s
LibraryDocumentationAPI (same source Libdoc uses), so it can only extract whatever metadata Robot Framework itself exposes for a library.That means:
- If a library (including Browser) exposes its keywords through RF’s normal mechanisms, they will show up automatically.
- If a plugin mechanism defines keywords in a way that Libdoc can see, they’ll work here as well.
- If keywords live purely outside RF’s introspection layer (e.g. dynamically on the JS side without metadata exposed to RF), then they won’t be discoverable — same limitation as Libdoc.
So the tool doesn’t try to re-implement or guess plugin internals; it intentionally stays aligned with what Robot Framework exposes.
Appreciate the kind words on the design — glad you liked the demo!
And dont forget to check the latest release New Release: robotframework-libdocgen - Professional Documentation Generator for RF Libraries