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
For the popup design and implementation, driver.js can be used. Its API is well-documented and provides most of the features we need (https://driverjs.com/docs/api). Ideally, a full stack engineer can implement driverjs in the Onboarding app.
Currently since we don't have a Chrome extension, the configuration of the elements can be retrieved from the server itself. Check https://driverjs.com/docs/static-tour as an example where the steps can be taken from a configuration file generated in the Onboarding server.
Later, when the Chrome extension is implemented, this configuration can be generated on the extension and then sent to the server, where it will be served to the driverjs endpoint.
Each driverjs instance should be initiated with an API key generated on the Onboarding server.
For the popup design and implementation, driver.js can be used. Its API is well-documented and provides most of the features we need (https://driverjs.com/docs/api). Ideally, a full stack engineer can implement driverjs in the Onboarding app.
Currently since we don't have a Chrome extension, the configuration of the elements can be retrieved from the server itself. Check https://driverjs.com/docs/static-tour as an example where the steps can be taken from a configuration file generated in the Onboarding server.
Later, when the Chrome extension is implemented, this configuration can be generated on the extension and then sent to the server, where it will be served to the driverjs endpoint.
Each driverjs instance should be initiated with an API key generated on the Onboarding server.
The text was updated successfully, but these errors were encountered: