diff --git a/gatsby-config.js b/gatsby-config.js index efb436743..d4c9aa74c 100644 --- a/gatsby-config.js +++ b/gatsby-config.js @@ -15,6 +15,9 @@ module.exports = { DEV_SSR: false }, siteMetadata: { + githubIssue: { + removeLogIssue: true, + }, docs: { title: 'Get credentials', path: 'https://acrobatservices.adobe.com/dc-integration-creation-app-cdn/main.html' diff --git a/package.json b/package.json index 7818b502d..92031d8bd 100644 --- a/package.json +++ b/package.json @@ -12,7 +12,7 @@ "url": "https://github.com/icaraps" }, "dependencies": { - "@adobe/gatsby-theme-aio": "4.9.12", + "@adobe/gatsby-theme-aio": "4.11.0", "gatsby": "4.22.0", "react": "^17.0.2", "react-dom": "^17.0.2" diff --git a/src/@adobe/gatsby-theme-aio/components/Layout/index.js b/src/@adobe/gatsby-theme-aio/components/Layout/index.js index 4bcc66a55..a60e7e1b3 100644 --- a/src/@adobe/gatsby-theme-aio/components/Layout/index.js +++ b/src/@adobe/gatsby-theme-aio/components/Layout/index.js @@ -215,6 +215,9 @@ export default ({ children, pageContext, location }) => { title path } + githubIssue{ + removeLogIssue + } versions { title path diff --git a/src/pages/apis/index.md b/src/pages/apis/index.md index 1e5df79d7..95ff59311 100644 --- a/src/pages/apis/index.md +++ b/src/pages/apis/index.md @@ -1,5 +1,5 @@ --- title: Adobe PDF Services Open API spec description: The OpenAPI spec for Adobe PDF Services API endpoints, parameters, and responses. -openAPISpec: https://raw.githubusercontent.com/AdobeDocs/pdfservices-api-documentation/main/src/pages/resources/openapi.json +openAPISpec: https://raw.githubusercontent.com/AdobeDocs/pdfservices-api-documentation/webhook_support2/src/pages/resources/openapi.json --- diff --git a/src/pages/overview/document-generation-api/docgenTemplateDocumentation.docx b/src/pages/overview/document-generation-api/docgenTemplateDocumentation.docx index c6bee1df1..09a7fb642 100644 Binary files a/src/pages/overview/document-generation-api/docgenTemplateDocumentation.docx and b/src/pages/overview/document-generation-api/docgenTemplateDocumentation.docx differ diff --git a/src/pages/overview/document-generation-api/templatetags.md b/src/pages/overview/document-generation-api/templatetags.md index af3fa7cd9..696844468 100644 --- a/src/pages/overview/document-generation-api/templatetags.md +++ b/src/pages/overview/document-generation-api/templatetags.md @@ -409,8 +409,29 @@ Here is the list of [supported aggregation functions](https://docs.jsonata.org/a aggregate numerical calculation can only be applied to a list of numbers. -## Adobe Sign +## Autogen Marker +Autogen Marker represents a category of tags whose values are automatically generated by MS Office and are not derived from the input data. + +### Table-of-Contents + +Represents a type of Autogen Marker which creates a Table of Contents section in the document. It can be inserted anywhere in the document. + +#### Usage +![Table of Contents tag replaced by Table of Content Section](../images/table_of_contents.png) + +#### Depth +Depth property can be specified with Table of Contents tag. It represents the levels of subheadings or subsections included in the Table of Contents and can accept an Integer value between 1 and 9. The default value is 3. + +![Table of Contents tag with depth](../images/table_of_contents_depth.png) + + +- Table of Contents tag should be placed in a separate paragraph in the document template. +- The paragraph containing Table of Contents tag should be a part of main body of the document, not nested within other elements or sections. +- Table of Contents section if already present, in the document template, won't be automatically updated in final output document. + + +## Adobe Sign Adobe Sign text tags can be placed anywhere within the contents of the document template. These tags are converted into Adobe Sign form fields when the final document is sent for a signature using Adobe Sign. diff --git a/src/pages/overview/images/table_of_contents.png b/src/pages/overview/images/table_of_contents.png new file mode 100644 index 000000000..a484bc1bf Binary files /dev/null and b/src/pages/overview/images/table_of_contents.png differ diff --git a/src/pages/overview/images/table_of_contents_depth.png b/src/pages/overview/images/table_of_contents_depth.png new file mode 100644 index 000000000..4b4b97295 Binary files /dev/null and b/src/pages/overview/images/table_of_contents_depth.png differ diff --git a/src/pages/overview/pdf-embed-api/releasenotes.md b/src/pages/overview/pdf-embed-api/releasenotes.md index 9d7061b98..c91db0a1a 100644 --- a/src/pages/overview/pdf-embed-api/releasenotes.md +++ b/src/pages/overview/pdf-embed-api/releasenotes.md @@ -11,8 +11,8 @@ the changes below for each release. ### January, 2024 | Change | Description | | ------ | ---------------------------------------------------------------------- | -| Changed | Essential library upgrades | -| Bug fix | Addressed issues with the error dialog that appears when an invalid Client ID is provided to the PDF Embed API. | +| Changed | New UI experience | +| Bug fix | Fixed wrong/missing client ID error dialog. | ### December, 2023 | Change | Description | diff --git a/src/pages/overview/security.md b/src/pages/overview/security.md index f7c7b4e00..6cca4859e 100644 --- a/src/pages/overview/security.md +++ b/src/pages/overview/security.md @@ -15,3 +15,33 @@ The Adobe Privacy Policy describes the privacy practices of Adobe's Services and ## Compliance Our [open, flexible framework](https://www.adobe.com/trust/compliance/adobe-ccf.html) adapts to constantly changing standards and regulations to help provide ongoing compliance across all our products and services. To learn more, please visit this [link](https://www.adobe.com/trust/compliance/compliance-list.html). + + +### Adobe PDF Embed API +Adobe PDF Embed API allows you to embed a PDF viewer in your web applications with only a few lines of code. With options for controlling how a PDF appears and functions, your applications can deliver the rich and compelling digital document experiences to your customers expect and need. + +### Adobe Commitment to Accessibility +[Adobe Accessibility Principles](https://blog.adobe.com/en/publish/2023/09/26/announcing-adobes-new-accessibility-principles) align with our core values and form the foundation for what we believe — everyone should be able to create, interact, and engage with digital experiences. These principles will serve as our guideposts as we build thoughtful and inclusive technology that makes a difference in people’s lives. + +The Adobe Accessibility Board has been created to set the strategy, review progress and oversee our commitment to supporting people with disabilities. + + +#### Conformance Statement +##### Adobe PDF Embed API +Adobe PDF Embed API is partially conformant with the Web Content Accessibility Guide (WCAG) 2.1 level AA. Adobe internally assessed the accessibility of Adobe Embed PDF using: +* Automated testing using 3rd party accessibility tools. +* Manual testing covering keyboard interactions and color contrast. + +##### PDF Viewer +Adobe PDF Viewer is partially conformant with WCAG 2.1 level AA. It is notable that accessible PDF documents are fully supported for viewing with assistive technologies in the Adobe PDF Viewer. + +The Adobe PDF Viewer was fully evaluated against: +* [Web Content Accessibility Guidelines 2.1](https://www.w3.org/TR/WCAG21/) +* [Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018](https://www.access-board.gov/ict/) +* [EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe](https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.01.01_60/en_301549v030101p.pdf), - V3.2.1 (2021-03) + +An annual audit was conducted on Acrobat Web, which includes the PDF Viewer, using a 3rd party vendor. This audit also included testing with native assistive technology users. The resulting Accessibility Conformance Report for Acrobat Web can be found on the [Adobe Accessibility Compliance page](https://www.adobe.com/accessibility/compliance.html). + +Additional testing for Acrobat Web included: +* Testing integrated into development using automated testing. +* Manual testing conducted on feature work. Some areas of focus include keyboard, color contrast, and testing with assistive technologies.