Associate Markdown files and page ID's

[bhrutledge]

Related to #20.

To make it easier to update pages and change titles, I think it'd be helpful to save the relationship of a Markdown file and its page ID (preferably the whole URL) after creating it. I've seen this done with a separate config file, front matter, and comments. My preference would be to append a comment to the end of the file, e.g.:

# Page title

Page content

<!-- https://ORG.atlassian.net/wiki/spaces/~SPACE_ID/pages/PAGE_ID/Page+title -->

This could then be parsed for the host, space, and page ID.

[iamjackg]

Hey, just letting you know that I'm going through a move, so I won't have time for the next little while. I haven't forgotten about this.

[iamjackg]

This is published in the latest version :)

[bhrutledge]

@iamjackg Is it? I don't see it listed in the release notes, and I don't recall opening a PR for it.

[iamjackg]

Oh, no, it's not -- sorry, I completely crossed the streams here.

[PullDakar]

any updates?

[iamjackg]

Would you be okay with the comment starting with a unique string like md2cf:? I need a way to avoid clobbering any existing comments if a page gets updated, moved, renamed, etc.

Also, is that an actual URL format used by Atlassian-hosted instances, or just something you made up to encode that information in the comment?

[iamjackg]

@PullDakar, @bhrutledge if you're still interested in this feature, please let me know your thoughts.

[bhrutledge]

Thanks for the nudge!

Would you be okay with the comment starting with a unique string like md2cf:?

Yep!

Also, is that an actual URL format used by Atlassian-hosted instances, or just something you made up to encode that information in the comment?

That's the format that I've seen on our Atlassian-hosted instance.

[iamjackg]

Sorry, I missed your response -- I've been busy working on a huge rewrite and it's currently in alpha. If all goes well I'll try to sneak this in before the final version :)