Find and fix markdown pages that aren't rendering

[concur]

Find and fix markdown pages that aren't rendering

[henryyamamoto-concur]

@pilara This is something we can start next week, but you have the master list and I know you and Deborah have been going through the pages so you may already have this info to provide Howard.

[DDlugosch]

There were some Imaging operations files that didn’t make it into GitHub during the initial conversion process, so I add them in a couple of weeks ago. They don’t show up on the test site so they are probably among the ones you’re talking about.

These are the directory paths of the files in GitHub:

api-reference\image\image-url-resource\image-url-resource-get
api-reference\image\image-url-resource\report-image-URL-get
api-reference\image\image-url-resource\entry-image-URL-get
api-reference\image\image-url-resource\payment-request-image-URL-get

Those are the only ones I know about that aren’t showing up.

From: Howard Dierking [mailto:[email protected]]
Sent: Wednesday, March 11, 2015 2:48 PM
To: concur/developer.concur.com
Subject: [developer.concur.com] Find and fix markdown pages that aren't rendering (#23)

I don't have a list at the moment, but if I compare the pages that exist in the directory structure with the pages that are generated, there are gaps. We need to figure out which pages are not rendering and get them rendering.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/23.

---

This e-mail message is authorized for use by the intended recipient only and may contain information that is privileged and confidential. If you received this message in error, please call us immediately at [phone] and ask to speak to the message sender. Please do not copy, disseminate, or retain this message unless you are the intended recipient. In addition, to ensure the security of your data, please do not send any unencrypted credit card or personally identifiable information to this email address. Thank you.

[pilara]

Deborah and I will start a scrub next week.

On Mar 11, 2015, at 2:54 PM, HenryY <[email protected]mailto:[email protected]> wrote:

@pilarahttps://github.com/pilara This is something we can start next week, but you have the master list and I know you and Deborah have been going through the pages so you may already have this info to provide Howard.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/23#issuecomment-78380774.

---

This e-mail message is authorized for use by the intended recipient only and may contain information that is privileged and confidential. If you received this message in error, please call us immediately at [phone] and ask to speak to the message sender. Please do not copy, disseminate, or retain this message unless you are the intended recipient. In addition, to ensure the security of your data, please do not send any unencrypted credit card or personally identifiable information to this email address. Thank you.

[pilara]

We'll shoot for starting Friday. My day tomorrow is fully booked writing new docs for the User API and making new updates to the Ground Transportation API that came through this week.

[pilara]

I'll walk through the site and create a list of the topics that are not rendering.

[henryyamamoto-concur]

Need to do this AFTER the next refresh effort to avoid throwaway work.