-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update guides #1035
base: main
Are you sure you want to change the base?
Update guides #1035
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -49,3 +49,23 @@ Developers have two options when using the ``InAppGuide`` widget: | |
A decent amount of ``InAppGuide(identifier=<identifier>)`` instances have been placed strategically throughout the app. | ||
Developers may suggest additional core guide sections via GitHub pull requests. | ||
For plugin developers, additional instances of either flavor are recommended to be added in any component of the plugin in conjunction with dedicated plugin-specific guides. | ||
|
||
Plugin guides | ||
------------- | ||
|
||
Plugin developers may introduce additional guides to the app. To do so, add the following key/value entry in your plugin's ``__init__.py`` file: | ||
|
||
.. code:: python | ||
|
||
my_plugin = { | ||
... | ||
"guides": <path-to-guide>, | ||
} | ||
|
||
where ``path-to-guide`` is the path (``Path`` object or absolute string path) to the directory containing the guide HTML files. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "Here, path_to_guide should be either a Path object or an absolute string path pointing to the directory that contains the guide HTML files." |
||
On app start, the guide manager will scan the plugin entry points for the ``guides`` key and load the guides accordingly. | ||
|
||
Guide order | ||
----------- | ||
|
||
When naming your guide HTML documents, prefix the file name with ``#_``. The number ``#`` will determine the order in which the guides are displayed in the list. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "To control the display order of your guide HTML documents, prefix each file name with #_, where # is a number. This number will dictate the order in which the guides appear in the list." |
This file was deleted.
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about , "Plugin developers can enhance the user experience while using the app by introducing custom guides"