SAP Concur Developer Center (Source)

This repo contains the documentation and support content for the Concur API developer audience. This includes both internal and external developers.

Changes merged to the preview repository (https://github.com/SAP-docs/preview.developer.concur.com) can be found here: https://preview.developer.concur.com/

Changes merged to the live repository (https://github.com/SAP-docs/developer.concur.com) can be found here: https://developer.concur.com/

Sitemap

The Concur Developer Website found within the /src folder is organized into these areas:

_data            Sidebars for navigation and various other YML files for the site.
_includes        Base HTML for the site combined with Markdown at build time.
_layouts         Specific HTML for the various types of resources, referenced with Jekyll front matter, combined with Markdown at build time.
_plugins         Various Jekyll plugins used at build time.
_sass            CSS styling for the site.
api-explorer     OpenAPI documentation (aka 'Swagger') for some of the API endpoints.
api-guides       Partner enablement resources showing how to combine various APIs for end-to-end solutions.
api-reference    Specific API endpoint documentation.
assets           Various site wide images.
manage-apps      SAP Concur App Center partner marketing materials.
swagger-ui       Supporting files for /api-explorer
tools-support    Support resources for developers including release notes.

Availability

View Availability

Support

If you are an existing Concur partner and require support assistance, please open a partner support case here.

Site Build

Within CircleCI:

1. Environment is created.
2. Source code for the site is cloned from GitHub.
3. Installs the packages needed to build the site, primarily the Jekyll package -- see https://github.com/jekyll/jekyll.
4. Builds the entire site according to _config.yml. This is mostly converting Markdown to HTML using Jekyll.
5. Archives the site.

Site Deploy

If the site build is successful, within CircleCI:

1. Environment is created.
2. Generated static content is updated in gh-pages branch
3. gh-pages branch is automatically re-published using GitHub Pages

Code of Conduct

Please refer to our Code of Conduct when contributing

Licensing

Copyright 2021 SAP SE or an SAP affiliate company and SAP Concur API documentation contributors.

Please see our LICENSE for copyright and license information.

Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool (https://api.reuse.software/info/github.com/SAP-docs/preview.developer.concur.com)