-
Notifications
You must be signed in to change notification settings - Fork 5
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
Feature request or wish list #12
Comments
Hi Mitjakac, In regards to linking different sections, right now it's implemented on the url level for example following url maps to a certain section: https://www.docsie.io/documentation/?version=0.0.1&language=EN&article=versions#section-header-two-crhkd Can you elaborate a bit more on this? |
Hello Philippe, Regarding linking, not sure I understood you (or you me ) :-( My current setup for testing:
I would like to have separate help links on every page that links specific article / section. Thank you and best regards |
Yes this makes sense. There is a feature in works to allow that. It should be coming in two more sprints, so most likely in February. This feature would allow you to specify render of specific article in the script. I will update the story to allow it to optionally pass section so it could render the correct article/section in the scope of a div. |
Hello,
I'm playing with Docsie and very satisfied. Thank you for your effort.
Few questions or wish list:
Is there possibility to link to specific section of documentation? So I would have different link on different sections of my application. Something like
src="https://lib.docsie.io/1.1.0/service.js" data-docsie="test_pk_xxx, section:my section name
Do you have plans to allow Export to PDF? For using offline.
Also, is it possible to export documentation and include locally for application behind firewall?
So, it would be src="http:/localhost/service.js" with all data inside this or separate .js file
The text was updated successfully, but these errors were encountered: