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
This would be a great opportunity to minimize the effort for people to contribute to the documentation.
However it's not that simple do this kind of thing on our side now, because the URLs in usermanual and github repo do not match: the URLs are flat on AT.com
(honestly I don't like this discrepancy, I don't have a preference, but it should be consistent)
However if we don't want to change the structure, in order to implement the feature, we could embed the "github classpath" in each MD file (via JS variable maybe and then make a script which will read it and put a DOM element with a link, or make it build-time, whatever is easier to do).
The text was updated successfully, but these errors were encountered:
I added the link "open an issue on github" in efdbbb5 in the bottom of documentation entries, but I still think "edit this on github" would be even better :)
On Karma, and many other projects, there's a direct link to edit the documentation page you're looking at right now, directly on Github (top right):
http://karma-runner.github.io/0.10/config/browsers.html
This would be a great opportunity to minimize the effort for people to contribute to the documentation.
However it's not that simple do this kind of thing on our side now, because the URLs in usermanual and github repo do not match: the URLs are flat on AT.com
//ariatemplates.com/usermanual/latest/ working_in_an_asynchronous_world
while they're structured in the repo:
//github.com/ariatemplates/usermanual/blob/master/src/latest/ core/concepts/working_in_an_asynchronous_world .md
(honestly I don't like this discrepancy, I don't have a preference, but it should be consistent)
However if we don't want to change the structure, in order to implement the feature, we could embed the "github classpath" in each MD file (via JS variable maybe and then make a script which will read it and put a DOM element with a link, or make it build-time, whatever is easier to do).
The text was updated successfully, but these errors were encountered: