concur/developer.concur.com

The Concur developer portal Web site

developer.concur.com's Issues

Clean up Travel left nav

landing page needed for /api-reference

need the index.html or index.markdown content for the complete api listing

Fix broken links for all items under Authentication in API home page

Links became broken when we changed "OAuth2.0" to "Authentication"

Find and fix markdown pages that aren't rendering

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.

Support markdown page not rendering hyperlinks correctly

Hyperlinks are not rendering as hyperlinks should (different color with underline):
http://concur.github.io/developer.concur.com/tools-support/support.html

They are rendering correctly on GitHub:
https://github.com/concur/developer.concur.com/blob/gh-pages/tools-support/support.markdown

combine conceptual, reference, operation, and resource layouts into a single layout

these are currently exact duplicates of one another

Fix weird behavior of ">" not expanding or collapsing sub nav menu

The ">" is clickable and changes state when you click on it, but to expose the nested items, you have to click on anywhere, but the ">". The fact that it changes state and is independently clickable causes a confusing UX.

So we should:

• Open and close the nested items when a user clicks on ">" OR
• Tie the state change of the ">" to be based on the open/close state of the nested items

Akamai Integration

• Setup CDN with Akamai
• Flush CDN as a part of build process for Akamai
• Terminate SSL at network edge
• Setup DNS (notify 7 days prior to launch)

visual cue for "active" item on top navigation menu

robots.txt file

Create the actual content for the why-concur.html page

Currently, content is still boilerplate images and filler text.

landing page needed for /docs/guides

How to handle redirects or old URLs to new portal URLs

What's the best way to handle redirects from a URL on the old portal to the new portal URL? This is for specific cases where a heavily used URL is propagated on various internal and external sites. Rather than hunt these down and opening multiple JIRA tickets against other teams, this may be an easier way to handle it.

This URL is from the old portal:
developer.concur.com/docs-and-resources/documentation
Needs to go to this URL on the new portal:
developer.concur.com/api-reference/

Update nav: Remove "Home", Shorten "APIs" and Add "Manage Apps"

We need to get "Manage Apps" back in to provide a home for: sandbox creation, go to market (remove from "Tools & Support") and link to App Store.

• REMOVE "Home" from top nav
• EDIT "API Reference" to "APIs"
• ADD "Manage Apps" + sub nav

See image below for how it should look and where new sub-nav items are located:

Directory structure for storing PDF documents

I was going to create a folder in the go-to-market folder for the PDFs they want to have partners download, but is there a better or preferred place these types of docs should be stored?

I was planning on go-to-market/PDF/

Add bootstrap banner for successful form posting

Change site name from Developer Portal to "Developer Center"

Two changes regarding the name of the site next to the Concur logo:

• Change name from Developer Portal to Developer Center
• Increase font point size 4-6 pts larger

create folder for QuickStart

move content around per content team's recommendation

nav should automatically adjust

Scale down home page banner by 1/3?

Is there a way we can scale the header image banner down by a third?

Need method to handle pop-up video playback and/or image zoom

We're going to have some YouTube videos on the site and in some case, we want them to pop up rather than imbed them inline with content. These cases would mostly be from banners on some pages.

Dustin found this, which is what the Unify template examples on portfolio pages seem to be using:
http://fancyapps.com/fancybox/

I don't want to muck anything up. I know how to use the href attributes, not not sure about where to put the script and stylesheet.

There may be a better free way to do this, so if you know of one we can use that instead.

Instrument the site for making data-driven UX decisions down the road

In order of priority

• general traffic info (e.g. which pages are viewed most)
• page flow info (page1 -> page2 -> exit)
• eye tracking

Delete Overview element in the Overivew subnav.

Overview left nav shows the parent Overview element as a child element

Hidden form field to thwart bots (aka Honeypot)

create folder for Expense recipe

PREVIEW BRANC: .markdown pages in some instances not rendering (404 error)

On the Preview branch, I've discovered the following not working:

App Cert page:
http://preview.developer.concur.com.s3-website-us-west-2.amazonaws.com/manage-apps/app-certification Fixed by adding .html

Terms of use in footer:
http://preview.developer.concur.com.s3-website-us-west-2.amazonaws.com/Terms-of-Use

These work on the gh-pages and may not be the only ones. These are just two I've found so far.

Broken link in top nav Docs ==> Reference

The link to the Reference page from the Docs top nav menu is broken. Can you help troubleshoot why that that is?

clean up unused assets from repository

There are quite a few assets (images, etc.) that will be left over from the template after we have the site all built out. Figure out what these are and remove them.

landing page needed for /docs/reference

e.g. need an index.markdown page

APIs by Category header needs to move to top of sub nav

Need to move "APIs by Category" to top of sub nav

Punch List - Priority to get done by Monday

I've created this punch list in priority order of things I'd like to have done by Fusion on Monday so we can preview to the partners who will be there.

1. Nav Update: Adding "Manage Apps" back in with noted nested items. Issue #26
2. Go-To-Market Support Form: https://jira.concur.com/jira/browse/WS-7093
3. Markdown Rendering Issues: @pilara and @howarddierking to work to resolve

I'll create an overall punch list of what work remains for us to be able to shut down the old Drupal site, but this is the minimum to allow us to preview at Fusion. The Go-to-Market form completes that page 100% and that's the audience that will be the majority at Fusion.

Sub Nav in API Reference collapses after selecting an item

The sub nav under API Reference collapses after you click on a sub-nav item. This results in having to reopen the nested items each time you click on an item. This should remain open until the user specifically clicks on the parent to collapse.

The expected behavior above is what the template sample site does in handling sub nav.

Bad links on api-reference/travel/itinerary/index.html page

http://concur.github.io/developer.concur.com/api-reference/travel/itinerary/index.html

• Itinerary Web Service FAQs. - page doesn't exist
• See Also section at bottom of page is missing links

Better definition of Tools & Support sub-menu

It currently consists of the following sub-items

• Help and FAQs
• Developer forum
• Contact Support
• Community
• Dev Blog
• Events
• Newsletter

How many of these are we keeping, and where should they point? Also, need to determine where we need to create content as I don't think that there's currently any content for many of these.

Latest Posts (Blog Title + Date) in Footer

Per our meeting today on Fusion status, I'm creating this issue to bring in the title and date of the blog posts from the concur.com site (https://www.concur.com/blog/c/product)

For now we'll pull the product posts until we get agreement from marketing to have a 'developer' category.

Add module for code high-lighting

Code blocks do not render with the proper highlighting. Please add a code high-lighting module so that XML and JSON code blocks render correctly.

Direct Connects left nav menu item does not expand and collapse

1. On the top nav, click API in the top nav
2. On the lef nav, click Direct Connects

Current Behavior
Direct Connects menu item does not expand/collapse

Expected Behavior
Direct Connects menu item should expand/collapse

Port content for existing site

• bring over content from existing developer.concur.com site in HTML form
• preserve the same structure initially to ensure that URLs can be preserved
• convert to markdown

change design template

based on the new selected template from PM

Add top nav to top of forum.developer.concur.com?

To help users navigate back to the dev portal easily, can we add the top nav on top of the Discourse site? Or add a little blue button with white text that says, "Back to Concur Developer Center"

Example:

Left nav menu entries should be capitalized consistently: Initial caps for first word in title

All left nav menu entries should be capitalized consistently. The pattern we will use is to capitalize only the first word in the title of each menu item regardless of level. For example:

Authentication
Access token
App center flow
Auto-connect flow
Concur OAuth 2.0 implementation
Choosing an authorization flow
Getting access tokens
Native flow
Revoking access tokens
Refreshing access tokens
Web flow

Add placeholder text for form fields (sandbox) to guide users

Update Getting Started with revised Quick Start content.

Add ZenHub to Dev Center and API Gateway for trial/test run

https://www.zenhub.io/

I'd do it but if something goes wrong, I'd rather have @howarddierking available.

create CI environment from dev branch so that content team can easily preview work

probably just have the CI server drop the top level directly into an s3 bucket

site navigation

need the strategy that includes

• top level navigation (e.g. menu)
• intra-page navigation
• site map page(s)

Table columns are too close together

We need the ability to adjust table column widths. This is a known issue for Markdown (markedjs/marked#266 ). Can we customize our CSS to accommodate this? Here are some resources I found:

https://www.dokuwiki.org/wiki:syntax#tables
http://jsfiddle.net/iegik/3D2Fb/

Clean up Expense left nav

sitemap.xml file

Links go to Drupal site expense/attendee/attendee-list-resource.html page

http://concur.github.io/developer.concur.com/api-reference/expense/attendee/attendee-list-resource.html

• All links on this page go to Drupal site