How do I set anchors for the postman documentation?
I make the documentation for api, how to make a cross reference (named anchor) with markdown in postman?
Is there such a similar option?
Take me to <a href="#api"> rest api </a> ... <a name="api"> this is rest api </a>
postman
add a comment |
I make the documentation for api, how to make a cross reference (named anchor) with markdown in postman?
Is there such a similar option?
Take me to <a href="#api"> rest api </a> ... <a name="api"> this is rest api </a>
postman
add a comment |
I make the documentation for api, how to make a cross reference (named anchor) with markdown in postman?
Is there such a similar option?
Take me to <a href="#api"> rest api </a> ... <a name="api"> this is rest api </a>
postman
I make the documentation for api, how to make a cross reference (named anchor) with markdown in postman?
Is there such a similar option?
Take me to <a href="#api"> rest api </a> ... <a name="api"> this is rest api </a>
postman
postman
edited Jul 15 '18 at 9:49


Pearly Spencer
12.1k173968
12.1k173968
asked Jul 13 '18 at 9:18


NiraxNirax
64
64
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You could create an element with an id "api" in a collection/folder/request description, and then link it in another place like [rest api](#api)
If you want to link a folder or request, you should get the ID (from the documentation itself) and then using the same Markdown as before with the respective ID.
Note: Take into account that Postman Documentation doesn't provide (at this moment) a way to specify a custom ID for a folder or request, so in case you're trying to do that, the best you can do is create an element with an id at the top of the description and then linking to that new element. It will scroll to a point under the title, which may result in a poorer user experience.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f51321753%2fhow-do-i-set-anchors-for-the-postman-documentation%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You could create an element with an id "api" in a collection/folder/request description, and then link it in another place like [rest api](#api)
If you want to link a folder or request, you should get the ID (from the documentation itself) and then using the same Markdown as before with the respective ID.
Note: Take into account that Postman Documentation doesn't provide (at this moment) a way to specify a custom ID for a folder or request, so in case you're trying to do that, the best you can do is create an element with an id at the top of the description and then linking to that new element. It will scroll to a point under the title, which may result in a poorer user experience.
add a comment |
You could create an element with an id "api" in a collection/folder/request description, and then link it in another place like [rest api](#api)
If you want to link a folder or request, you should get the ID (from the documentation itself) and then using the same Markdown as before with the respective ID.
Note: Take into account that Postman Documentation doesn't provide (at this moment) a way to specify a custom ID for a folder or request, so in case you're trying to do that, the best you can do is create an element with an id at the top of the description and then linking to that new element. It will scroll to a point under the title, which may result in a poorer user experience.
add a comment |
You could create an element with an id "api" in a collection/folder/request description, and then link it in another place like [rest api](#api)
If you want to link a folder or request, you should get the ID (from the documentation itself) and then using the same Markdown as before with the respective ID.
Note: Take into account that Postman Documentation doesn't provide (at this moment) a way to specify a custom ID for a folder or request, so in case you're trying to do that, the best you can do is create an element with an id at the top of the description and then linking to that new element. It will scroll to a point under the title, which may result in a poorer user experience.
You could create an element with an id "api" in a collection/folder/request description, and then link it in another place like [rest api](#api)
If you want to link a folder or request, you should get the ID (from the documentation itself) and then using the same Markdown as before with the respective ID.
Note: Take into account that Postman Documentation doesn't provide (at this moment) a way to specify a custom ID for a folder or request, so in case you're trying to do that, the best you can do is create an element with an id at the top of the description and then linking to that new element. It will scroll to a point under the title, which may result in a poorer user experience.
answered Jan 2 at 15:06


Nicolas OrchowNicolas Orchow
12
12
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f51321753%2fhow-do-i-set-anchors-for-the-postman-documentation%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown