--- language: "en" --- # Spiegelei ## Spiegelei ## Welcome The Campaign Service Provider (CSP) API is a REST-based interface that allows applications to interact with The Campaign Registry (TCR) platform. The content in this site represents essential information about the CSP API and includes requests and responses. Additional content will be added over time. For a PDF version of this content (and more), please see [Introduction to the CSP API](https://www.campaignregistry.com/Assets/Introduction%20to%20the%20CSP%20API.pdf). Information in this document pertains to the creation and management of 10DLC campaigns. While TCR supports RCS campaign creation and management in its CSP and DCA portals, this functionality is not yet available in the APIs. ### Useful Links * **OpenAPI Specification:** An interactive OpenAPI specification document for the Staging environment can be found at: . * **API Version and Changelogs:** The CSP API version number can be retrieved via the `GET /version` endpoint. For information on updates and changes, view the [++changelog++](https://release.campaignregistry.com/en/changelog). For questions, contact [++TCR Support++](mailto:support@campaignregistry.com). * **TCR System Events Reference:** A guide to all the public system events sent by TCR in its [webhooks](https://www.campaignregistry.com/Assets/TCR%20System%20Events%20Reference.pdf). [Problem and Solution Guide](https://goodsoftware.k15t.dev/spiegelei/problem-and-solution-guide.md) ### Recommended Articles * #### [Link testing](https://goodsoftware.k15t.dev/spiegelei/link-testing.md) This is a link which I have inserted after 'Copy link to heading' from another confluence page. Page added by Rovo \| Additional Dummy Paragraphs A link: INLINE... * #### [This is a new set scroll page title](https://goodsoftware.k15t.dev/spiegelei/this-is-a-new-set-scroll-page-title.md) page.title Hello variant name rest of the title I will publish the page first, so this page will get updated to my existing site. After the page is published t... * #### [Latex math](https://goodsoftware.k15t.dev/spiegelei/latex-math.md) Site Updated the page 2026-03-02 and follow macros added: Screen Recording 2025-10-13 at 15.26.37.mov Latex math block Existed before: This macro says, Latex m... ### Documentation * #### [Support](https://goodsoftware.k15t.dev/spiegelei/support.md) * [KS-42236](https://goodsoftware.k15t.dev/spiegelei/ks-42236.md) * [KS-42502](https://goodsoftware.k15t.dev/spiegelei/ks-42502.md) * [KS-43718](https://goodsoftware.k15t.dev/spiegelei/ks-43718.md) * [KS-41878](https://goodsoftware.k15t.dev/spiegelei/ks-41878.md) * [KS-41669](https://goodsoftware.k15t.dev/spiegelei/ks-41669.md) * [2 more pages](https://goodsoftware.k15t.dev/spiegelei/support.md) * #### [Numbered lists](https://goodsoftware.k15t.dev/spiegelei/numbered-lists.md) * [Inline URL Links](https://goodsoftware.k15t.dev/spiegelei/inline-url-links.md) * #### [Add speciäl charäckter to the page nöme!-\&!@#$%\^\&\*()_+\~?](https://goodsoftware.k15t.dev/spiegelei/updated-article-path.md) * [Add speciäl charäckter to the page nöme!-\&!@#$%\^\&\*()_+\~?@](https://goodsoftware.k15t.dev/spiegelei/add-special-charackter-to-the-page-nome-_.md) * #### [Child page Macro and child items](https://goodsoftware.k15t.dev/spiegelei/child-page-macro-custom.md) * [Problem and Solution Guide](https://goodsoftware.k15t.dev/spiegelei/problem-and-solution-guide.md) * [juhuuu, let's get more pans](https://goodsoftware.k15t.dev/spiegelei/juhuuu-let-s-get-more-pans.md) * [Testing new page](https://goodsoftware.k15t.dev/spiegelei/testing-new-page.md) * #### [Link testing](https://goodsoftware.k15t.dev/spiegelei/link-testing.md) * [Second page to test headline links](https://goodsoftware.k15t.dev/spiegelei/second-page-to-test-headline-links.md) * #### [Mirrow Docs, Nvidia testing](https://goodsoftware.k15t.dev/spiegelei/mirrow-docs.md) * [First Egg](https://goodsoftware.k15t.dev/spiegelei/first-egg-customized.md) * [Second egg](https://goodsoftware.k15t.dev/spiegelei/second-egg.md) * [Preparation](https://goodsoftware.k15t.dev/spiegelei/preparation.md) * [My new page](https://goodsoftware.k15t.dev/spiegelei/my-new-page.md) * [Include Page macro can show content from page that does not belong to the current variant](https://goodsoftware.k15t.dev/spiegelei/include-page-macro-can-show-content-from-page-that.md) * [2 more pages](https://goodsoftware.k15t.dev/spiegelei/mirrow-docs.md) * #### [Versions of Mirrow Docs](https://goodsoftware.k15t.dev/spiegelei/versions-of-mirrow-docs.md) * [(release 2-de) Mirrow Docs](https://goodsoftware.k15t.dev/spiegelei/release-2-mirrow-docs-2.md) * [(release 4-en) Mirrow Docs](https://goodsoftware.k15t.dev/spiegelei/mirrow-docs-2.md) * [(release 5-en) Mirrow Docs](https://goodsoftware.k15t.dev/spiegelei/mirrow-docs-3.md) * [(release 6-en) Mirrow Docs](https://goodsoftware.k15t.dev/spiegelei/mirrow-docs-4.md) * #### [New testing Doc](https://goodsoftware.k15t.dev/spiegelei/new-testing-doc.md) * [Second page](https://goodsoftware.k15t.dev/spiegelei/second-page.md) * #### [Upgrading to Scroll Sites: A Guide to Transition from Scroll Viewport](https://goodsoftware.k15t.dev/spiegelei/upgrading-to-scroll-sites-a-guide-to-transition-fr.md) * [Automatically Upgrade a Scroll Viewport site as a Scroll site](https://goodsoftware.k15t.dev/spiegelei/automatically-upgrade-a-scroll-viewport-site-as-a-.md) * [Steps to Delete a Site in Scroll Sites and Viewport](https://goodsoftware.k15t.dev/spiegelei/steps-to-delete-a-site-in-scroll-sites-and-viewpor.md) * #### [Release Notes](https://goodsoftware.k15t.dev/spiegelei/release-notes.md) * [Release notes, Styles](https://goodsoftware.k15t.dev/spiegelei/release-notes-styles.md) * [#2 Release notes, Styles](https://goodsoftware.k15t.dev/spiegelei/2-release-notes-styles.md) * [#3 Release notes, Styles](https://goodsoftware.k15t.dev/spiegelei/3-release-notes-styles.md) * [#4 Release notes, Styles](https://goodsoftware.k15t.dev/spiegelei/4-release-notes-styles.md) * [#5 Release notes, Styles](https://goodsoftware.k15t.dev/spiegelei/5-release-notes-styles.md) * [1 more pages](https://goodsoftware.k15t.dev/spiegelei/release-notes.md) * #### [Exporters Extensions](https://goodsoftware.k15t.dev/spiegelei/exporters-extensions.md) * [Scroll title](https://goodsoftware.k15t.dev/spiegelei/scroll-title.md) * [Scroll Ignore](https://goodsoftware.k15t.dev/spiegelei/scroll-ignore.md) * [Scroll Inline Ignore](https://goodsoftware.k15t.dev/spiegelei/scroll-inline-ignore.md) * [Scroll Only Inline](https://goodsoftware.k15t.dev/spiegelei/scroll-only-inline.md) * #### [Tab Macro Testing](https://goodsoftware.k15t.dev/spiegelei/tab-macro-testing.md) * [Tab, #1](https://goodsoftware.k15t.dev/spiegelei/tab-1.md) * [Tabs #2](https://goodsoftware.k15t.dev/spiegelei/tabs-2.md) --- language: "en" --- # #2 Release notes, Styles Scroll Sites 2026-07-21 improves automatic site updates for Page Properties content, improves the automatic upgrade process, adds support for root-level redirects, and includes several improvements and bug fixes. ## ✨ More Content Changes Now Trigger Automatic Site Updates Pages containing a **Content Properties Report** (Page Properties Report) macro now automatically trigger a site update in Scroll Sites when any of the Page Properties macros they depend on are changed, added, or deleted --- even if the report page itself wasn't edited in Confluence. Previously, these indirect changes required a manual full-site update to appear in the live site. With this improvement, your Content Properties Report (Page Properties Report) pages stay in sync automatically whenever the underlying data changes, without any extra steps. ## ✨ Root-Level Redirects You can now create a redirect from the root of your site (`/`) to any page or external URL. This lets you redirect your site's home page to a specific article, a custom landing page, or a different domain. Set up root-level redirects under **Site Settings** \> **Redirects**, the same way as any other simple redirect. Learn more: *** ** * ** *** Please refer to the Jira items below for more details on the individual improvements and bug fixes included in this release. ### Improvements * [STS-192: Trigger an automatic site update if a page with a page property report macro gets updated in Confluence because a corresponding page property macro has been changed, added or deleted](https://k15t.jira.com/browse/STS-192) * [STS-219: Support creating a redirect on the root level](https://k15t.jira.com/browse/STS-219) * [STS-233: Improve the Size of Emojis Published in Scroll Sites](https://k15t.jira.com/browse/STS-233) ### Bug Fixes * [STS-223: Content property report macro does not reflect 'Columns to show' and has formatting issues](https://k15t.jira.com/browse/STS-223) * [STS-226: Content properties report overflowing article content](https://k15t.jira.com/browse/STS-226) * [STS-17: Mermaid diagrams don't render due to timeout if there are too many on a single page](https://k15t.jira.com/browse/STS-17) * [STS-195: Upgrade from Scroll Viewport to Scroll Sites fails when document content sources are missing from Confluence search index](https://k15t.jira.com/browse/STS-195) * [STS-204: Content source live site links missing in Scroll Sites app settings](https://k15t.jira.com/browse/STS-204) --- language: "en" --- # #3 Release notes, Styles Scroll Sites 2026-07-21 improves automatic site updates for Page Properties content, improves the automatic upgrade process, adds support for root-level redirects, and includes several improvements and bug fixes. ## ✨ More Content Changes Now Trigger Automatic Site Updates Pages containing a **Content Properties Report** (Page Properties Report) macro now automatically trigger a site update in Scroll Sites when any of the Page Properties macros they depend on are changed, added, or deleted --- even if the report page itself wasn't edited in Confluence. Previously, these indirect changes required a manual full-site update to appear in the live site. With this improvement, your Content Properties Report (Page Properties Report) pages stay in sync automatically whenever the underlying data changes, without any extra steps. ## ✨ Root-Level Redirects You can now create a redirect from the root of your site (`/`) to any page or external URL. This lets you redirect your site's home page to a specific article, a custom landing page, or a different domain. Set up root-level redirects under **Site Settings** \> **Redirects**, the same way as any other simple redirect. Learn more: *** ** * ** *** Please refer to the Jira items below for more details on the individual improvements and bug fixes included in this release. ### :improvement: Improvements * [STS-192: Trigger an automatic site update if a page with a page property report macro gets updated in Confluence because a corresponding page property macro has been changed, added or deleted](https://k15t.jira.com/browse/STS-192) * [STS-219: Support creating a redirect on the root level](https://k15t.jira.com/browse/STS-219) * [STS-233: Improve the Size of Emojis Published in Scroll Sites](https://k15t.jira.com/browse/STS-233) ### :bug: Bug Fixes * [STS-223: Content property report macro does not reflect 'Columns to show' and has formatting issues](https://k15t.jira.com/browse/STS-223) * [STS-226: Content properties report overflowing article content](https://k15t.jira.com/browse/STS-226) * [STS-17: Mermaid diagrams don't render due to timeout if there are too many on a single page](https://k15t.jira.com/browse/STS-17) * [STS-195: Upgrade from Scroll Viewport to Scroll Sites fails when document content sources are missing from Confluence search index](https://k15t.jira.com/browse/STS-195) * [STS-204: Content source live site links missing in Scroll Sites app settings](https://k15t.jira.com/browse/STS-204) --- language: "en" --- # #4 Release notes, Styles Scroll Sites 2026-07-21 improves automatic site updates for Page Properties content, improves the automatic upgrade process, adds support for root-level redirects, and includes several improvements and bug fixes. ## More Content Changes Now Trigger Automatic Site Updates Pages containing a **Content Properties Report** (Page Properties Report) macro now automatically trigger a site update in Scroll Sites when any of the Page Properties macros they depend on are changed, added, or deleted --- even if the report page itself wasn't edited in Confluence. Previously, these indirect changes required a manual full-site update to appear in the live site. With this improvement, your Content Properties Report (Page Properties Report) pages stay in sync automatically whenever the underlying data changes, without any extra steps. ## Root-Level Redirects You can now create a redirect from the root of your site (`/`) to any page or external URL. This lets you redirect your site's home page to a specific article, a custom landing page, or a different domain. Set up root-level redirects under **Site Settings** \> **Redirects**, the same way as any other simple redirect. Learn more: *** ** * ** *** Please refer to the Jira items below for more details on the individual improvements and bug fixes included in this release. ### Improvements * [STS-192: Trigger an automatic site update if a page with a page property report macro gets updated in Confluence because a corresponding page property macro has been changed, added or deleted](https://k15t.jira.com/browse/STS-192) * [STS-219: Support creating a redirect on the root level](https://k15t.jira.com/browse/STS-219) * [STS-233: Improve the Size of Emojis Published in Scroll Sites](https://k15t.jira.com/browse/STS-233) ### Bug Fixes * [STS-223: Content property report macro does not reflect 'Columns to show' and has formatting issues](https://k15t.jira.com/browse/STS-223) * [STS-226: Content properties report overflowing article content](https://k15t.jira.com/browse/STS-226) * [STS-17: Mermaid diagrams don't render due to timeout if there are too many on a single page](https://k15t.jira.com/browse/STS-17) * [STS-195: Upgrade from Scroll Viewport to Scroll Sites fails when document content sources are missing from Confluence search index](https://k15t.jira.com/browse/STS-195) * [STS-204: Content source live site links missing in Scroll Sites app settings](https://k15t.jira.com/browse/STS-204) --- language: "en" --- # #5 Release notes, Styles Scroll Sites 2026-07-21 improves automatic site updates for Page Properties content, improves the automatic upgrade process, adds support for root-level redirects, and includes several improvements and bug fixes. ## More Content Changes Now Trigger Automatic Site Updates Pages containing a **Content Properties Report** (Page Properties Report) macro now automatically trigger a site update in Scroll Sites when any of the Page Properties macros they depend on are changed, added, or deleted --- even if the report page itself wasn't edited in Confluence. Previously, these indirect changes required a manual full-site update to appear in the live site. With this improvement, your Content Properties Report (Page Properties Report) pages stay in sync automatically whenever the underlying data changes, without any extra steps. ## Root-Level Redirects You can now create a redirect from the root of your site (`/`) to any page or external URL. This lets you redirect your site's home page to a specific article, a custom landing page, or a different domain. Set up root-level redirects under **Site Settings** \> **Redirects**, the same way as any other simple redirect. Learn more: *** ** * ** *** Please refer to the Jira items below for more details on the individual improvements and bug fixes included in this release. ### Improvements * [STS-192: Trigger an automatic site update if a page with a page property report macro gets updated in Confluence because a corresponding page property macro has been changed, added or deleted](https://k15t.jira.com/browse/STS-192) * [STS-219: Support creating a redirect on the root level](https://k15t.jira.com/browse/STS-219) * [STS-233: Improve the Size of Emojis Published in Scroll Sites](https://k15t.jira.com/browse/STS-233) ### Bug Fixes * [STS-223: Content property report macro does not reflect 'Columns to show' and has formatting issues](https://k15t.jira.com/browse/STS-223) * [STS-226: Content properties report overflowing article content](https://k15t.jira.com/browse/STS-226) * [STS-17: Mermaid diagrams don't render due to timeout if there are too many on a single page](https://k15t.jira.com/browse/STS-17) * [STS-195: Upgrade from Scroll Viewport to Scroll Sites fails when document content sources are missing from Confluence search index](https://k15t.jira.com/browse/STS-195) * [STS-204: Content source live site links missing in Scroll Sites app settings](https://k15t.jira.com/browse/STS-204) --- language: "en" --- # #6 Release notes, Styles Scroll Sites 2026-07-21 improves automatic site updates for Page Properties content, improves the automatic upgrade process, adds support for root-level redirects, and includes several improvements and bug fixes. ## More Content Changes Now Trigger Automatic Site Updates Pages containing a **Content Properties Report** (Page Properties Report) macro now automatically trigger a site update in Scroll Sites when any of the Page Properties macros they depend on are changed, added, or deleted --- even if the report page itself wasn't edited in Confluence. Previously, these indirect changes required a manual full-site update to appear in the live site. With this improvement, your Content Properties Report (Page Properties Report) pages stay in sync automatically whenever the underlying data changes, without any extra steps. ## Root-Level Redirects You can now create a redirect from the root of your site (`/`) to any page or external URL. This lets you redirect your site's home page to a specific article, a custom landing page, or a different domain. Set up root-level redirects under **Site Settings** \> **Redirects**, the same way as any other simple redirect. Learn more: *** ** * ** *** Please refer to the Jira items below for more details on the individual improvements and bug fixes included in this release. ### Improvements * [STS-192: Trigger an automatic site update if a page with a page property report macro gets updated in Confluence because a corresponding page property macro has been changed, added or deleted](https://k15t.jira.com/browse/STS-192) * [STS-219: Support creating a redirect on the root level](https://k15t.jira.com/browse/STS-219) * [STS-233: Improve the Size of Emojis Published in Scroll Sites](https://k15t.jira.com/browse/STS-233) ### Bug Fixes * [STS-223: Content property report macro does not reflect 'Columns to show' and has formatting issues](https://k15t.jira.com/browse/STS-223) * [STS-226: Content properties report overflowing article content](https://k15t.jira.com/browse/STS-226) * [STS-17: Mermaid diagrams don't render due to timeout if there are too many on a single page](https://k15t.jira.com/browse/STS-17) * [STS-195: Upgrade from Scroll Viewport to Scroll Sites fails when document content sources are missing from Confluence search index](https://k15t.jira.com/browse/STS-195) * [STS-204: Content source live site links missing in Scroll Sites app settings](https://k15t.jira.com/browse/STS-204) --- language: "en" --- # Add a custom SVG to the headline Use a standard emoji in text 😃 Add a custom emoji to the text :f:, this is added through the emoji macro ## Add a custom emoji to a headline :f: --- language: "en" --- # Add speciäl charäckter to the page nöme!-&!@#$%^&\*()\_+\~?@ --- language: "en" --- # And a child egg ## **Introduction to the Mirror Egg** A mirror egg, often known as a sunny-side-up egg, is a simple yet classic way to prepare eggs. Its defining feature is the bright, glossy yolk sitting like a "mirror" on a firm, white base. This dish is a breakfast staple around the world, appreciated for its beauty, simplicity, and versatility. Unlike scrambled or poached eggs, the mirror egg is not flipped during cooking. Instead, gentle heat allows the whites to set completely while the yolk remains liquid and shiny. The result is a visually appealing and texturally balanced meal that can be enjoyed alone or paired with toast, rice, vegetables, or meats. This documentation explains the ingredients, tools, steps, variations, and nutritional aspects of the mirror egg so you can recreate it perfectly every time. --- language: "en" --- # (release 4-en) And a child egg ## **Introduction to the Mirror Egg** A mirror egg, often known as a sunny-side-up egg, is a simple yet classic way to prepare eggs. Its defining feature is the bright, glossy yolk sitting like a "mirror" on a firm, white base. This dish is a breakfast staple around the world, appreciated for its beauty, simplicity, and versatility. Unlike scrambled or poached eggs, the mirror egg is not flipped during cooking. Instead, gentle heat allows the whites to set completely while the yolk remains liquid and shiny. The result is a visually appealing and texturally balanced meal that can be enjoyed alone or paired with toast, rice, vegetables, or meats. This documentation explains the ingredients, tools, steps, variations, and nutritional aspects of the mirror egg so you can recreate it perfectly every time. --- language: "en" --- # (release 5-en) And a child egg ## **Introduction to the Mirror Egg** A mirror egg, often known as a sunny-side-up egg, is a simple yet classic way to prepare eggs. Its defining feature is the bright, glossy yolk sitting like a "mirror" on a firm, white base. This dish is a breakfast staple around the world, appreciated for its beauty, simplicity, and versatility. Unlike scrambled or poached eggs, the mirror egg is not flipped during cooking. Instead, gentle heat allows the whites to set completely while the yolk remains liquid and shiny. The result is a visually appealing and texturally balanced meal that can be enjoyed alone or paired with toast, rice, vegetables, or meats. This documentation explains the ingredients, tools, steps, variations, and nutritional aspects of the mirror egg so you can recreate it perfectly every time. --- language: "en" --- # Caro new title | **page.title** | a change in the new title variant name variant two some more content | |----------------|----------------------------------------------------------------------| ## **Introduction to the Mirror Egg** A mirror egg, often known as a sunny-side-up egg, is a simple yet classic way to prepare eggs. Its defining feature is the bright, glossy yolk sitting like a "mirror" on a firm, white base. This dish is a breakfast staple around the world, appreciated for its beauty, simplicity, and versatility. Unlike scrambled or poached eggs, the mirror egg is not flipped during cooking. Instead, gentle heat allows the whites to set completely while the yolk remains liquid and shiny. The result is a visually appealing and texturally balanced meal that can be enjoyed alone or paired with toast, rice, vegetables, or meats. This documentation explains the ingredients, tools, steps, variations, and nutritional aspects of the mirror egg so you can recreate it perfectly every time. --- language: "en" --- # And another one --- language: "en" --- # Another page to discover ## 📘 Instructions 1. 2. 3. Highlight important information in a panel like this one. To edit this panel's color or style, select one of the options in the menu. ## 📋 Related articles * [Another page to discover](https://goodsoftware.k15t.dev/spiegelei/another-page-to-discover.md) --- language: "en" --- # Another page to test headline links ## Spiegelei (Fried Egg) Recipe ### Introduction A Spiegelei, or fried egg, is a classic and simple dish enjoyed in many households. Whether served for breakfast, lunch, or as a topping for other meals, a perfectly cooked Spiegelei is both delicious and versatile. Follow these easy steps to prepare a traditional Spiegelei. ### Ingredients * 1 fresh egg * 1 tablespoon butter or oil * Salt and pepper to taste ### Instructions 1. **Heat the Pan** Place a non-stick frying pan over medium heat and add the butter or oil. Allow it to melt and heat up, but do not let it brown. 2. **Crack the Egg** Carefully crack the egg into a small bowl to avoid shell fragments, then gently slide the egg into the pan. 3. **Cook the Egg** Let the egg cook undisturbed until the white is set but the yolk remains runny, about 2--3 minutes. For a firmer yolk, cover the pan with a lid for an additional minute. 4. **Season and Serve** Sprinkle the egg with salt and pepper to taste. Serve immediately, either on its own or as a topping for bread, salads, or other dishes. ### Tips * For a crispier edge, increase the heat slightly during cooking. * Add herbs or spices for extra flavor. --- language: "en" --- # I am changing my page title, PDF attachment ## By drag- and drop [How to create a robust product analytics framework_ _ by Zipy _ Medium.pdf](https://goodsoftware.k15t.dev/__attachments/a_2e468d54065ad3ef9aede6d643d3ba113c379a4a15bd1f6bb8f4ba49f82eacf8/How%2520to%2520create%2520a%2520robust%2520product%2520analytics%2520framework_%2520_%2520by%2520Zipy%2520_%2520Medium.pdf.md) Insert \> PDF ADDDDD ![](https://api.media.atlassian.com/file/1ec6745a-a698-41f7-994b-3f477db779f1/image?token=eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiIxNTMwZTE0Zi1kNzZkLTRmYWItYWQ5MS0yZjEwMWM1ZmEyODciLCJhY2Nlc3MiOnsidXJuOmZpbGVzdG9yZTpmaWxlOjFlYzY3NDVhLWE2OTgtNDFmNy05OTRiLTNmNDc3ZGI3NzlmMSI6WyJyZWFkIl19LCJleHAiOjE3ODY2MTI4NDMsIm5iZiI6MTc4NjYwOTg0MywiYWFJZCI6IjcxMjAyMDoyYjIwNGJhNC0zNjQ1LTQwMjUtOWU3Yi00NTRhMzQ4NTViN2IiLCJodHRwczovL2lkLmF0bGFzc2lhbi5jb20vYXBwQWNjcmVkaXRlZCI6ZmFsc2V9.y90AUBpYLqurUZfAIJ-PRIvQfIE-EGHOhmpRR_UoTHE&client=1530e14f-d76d-4fab-ad91-2f101c5fa287&name=How%20to%20create%20a%20robust%20product%20analytics%20framework_%20_%20by%20Zipy%20_%20Medium.pdf) ### By uploading thought the attachment | File | Modified | |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------| | [How to create a robust product analytics framework_ _ by Zipy _ Medium.pdf](https://goodsoftware.k15t.dev/__attachments/a_2e468d54065ad3ef9aede6d643d3ba113c379a4a15bd1f6bb8f4ba49f82eacf8/How%2520to%2520create%2520a%2520robust%2520product%2520analytics%2520framework_%2520_%2520by%2520Zipy%2520_%2520Medium.pdf.md) | Oct 13, 2025 | --- language: "en" --- # Attach some PDF Cards extension hello hello [How to create a robust product analytics framework_ _ by Zipy _ Medium.pdf](https://goodsoftware.k15t.dev/__attachments/a_2dabbb24fa7f28b7406591988488a6e210baf39192118a7eb54a896c5429e7cb/How%2520to%2520create%2520a%2520robust%2520product%2520analytics%2520framework_%2520_%2520by%2520Zipy%2520_%2520Medium.pdf.md) --- language: "en" --- # Automatically Upgrade a Scroll Viewport site as a Scroll site This page will outline the process to start and complete an automated replication of the site in Scroll Sites. ## Start the Upgrade (Creates an Unpublished Copy of Your Site) From the purple box in the*My sites* screen: 1. In the list, look for the site you want to replicate and hover over it. 2. Click **Upgrade site**. 3. In the confirmation dialog, click **Upgrade site** again. Scroll Sites will now fetch all the files from your Viewport site and start building the site. Once the site is available, it will show in the *My sites* list in Scroll Sites. 4. Find and click into your site from the *My sites* list or click **Review site** from the toast message that appears at the bottom of the screen. You will land in the *Site settings* screen for the site (which is still in unpublished state). On top of the *Site settings* screen, you'll see a purple *Upgrade summary* box. This box lists all the settings that couldn't be copied over automatically. Before you can publish your site, you will need to adjust all the listed settings manually. ## Use the *Upgrade Summary* To Adjust Remaining Settings Manually Go through the items in the *Upgrade summary* box in the same order that they are listed in the box: 5. Click the first item in the list. You will be scrolled down to the respective site settings. 6. Open the setting and adjust it to reflect your Viewport site. Use the table below to help you make the adjustments. 7. Scroll back to the *Upgrade summary* box and use the tickbox to check off the item you've adjusted. 8. Repeat for all items in the list. ### References on how to adjust individual site settings Use the table below to help you make the manual adjustments required to complete the replication of your site in Scroll Sites. #### **Look and Feel** Some files couldn't be collected from Scroll Viewport. Review your theme configuration and upload missing files. To add missing files, navigate in Scroll Sites to **Site settings** \>**Look and feel** \>**Customize theme** *.* Click through all of the tabs in the left hand side and identify any *Upload file* fields that are empty and upload the respective files. #### **Redirects** To quickly migrate all your existing redirects from Viewport, navigate in Scroll Sites to **Site settings** \>**Redirects** \>**Advanced Redirects** and copy paste all your redirects from Viewport into the editor. #### **Custom CSS** Review your injected CSS code and possibly adjust some of the tokens, HTML attributes, components etc. #### **Custom JS** Review your injected Javascript code and possibly adjust some of it. To identify which parts of your custom code need to be re-written, please refer to #### **AI search** Add your AI integration credentials to enable AI Search. To add your OpenAI API key, go to and copy paste the same key you used in your Viewport site into the *OpenAI API key* field under **Site settings** \> **AI**. Make sure to complete all other site settings (except for site access) before you set up the right domain for your site. #### **Site URL** Switch your domain from the temporary one to the (custom) domain you used in Viewport. Does your Viewport site use a ***scrollhelp.site*** **domain?** Simply navigate in Scroll Sites to **Site settings** \>**Site URL** and under *Use provided domain* , in the *Site domain* field enter your used subdomain. From the dropdown, make sure to select **.** `scrollhelp.site` as the provided domain. We will automatically disconnect your existing Viewport site from the entered domain. Does your Viewport site use a **Custom** **domain?** To connect your new site to the same customdomain that your Viewport site is using, follow the steps on . #### **Site access** Review and apply your existing access settings to protect your site the way you want. Make sure to set up your custom domain before you set up protected site access. To set up a login protection with tokens or single sign-on, follow the steps on . ## Complete the Upgrade (Go Live With Your New Site) Once you have checked off all the items in the *Upgrade summary* box, you can save and bring all changes to the live site. We recommend to review your unpublished site one more time, then go live: 15. In the *Upgrade summary* box, click **Complete upgrade**. This will remove the box and resolve all 'review' statuses in your site settings. 16. From the top of the Site settings screen, click **Save changes**. 17. From the left sidebar, click **Site updates**. 18. In the top right of the *Site updates* screen, click **Publish updates.**This will bring all settings adjustments you made to your unpublished site. 19. From the sidebar, click **View site**. This will open your unpublished site in a new tab. 20. Thoroughly navigate through your site to make sure that your site looks and behaves exactly as your existing Viewport site. For example, you might want to test out some redirects or any enabled integrations, if your site uses them, or check that the styling and branding looks as expected, Please note that the help center theme in Scroll Sites is **not** identical to the one in Scroll Viewport. ### Differences between Scroll Viewport's and Scroll Sites' Help Center theme * 🎨 **Visual changes** . There are some small visual differences between the Help Center theme in Scroll Sites and the one in Scroll Viewport that are *expected*. Visual tweaks include font sizes, size of components, images etc. * 📏 **Banner images are centered**. The banner image in Scroll Sites' help center theme is centered (both vertically and horizontally) while the one in Scroll Viewport is aligned to the top. We recommend you review and adjust your banner image file as needed. * 🗑️ **Removed icons from the portal and content source pages**. The small material icons were removed from Scroll Sites' help center theme due to technical reasons. An improved solution will be coming. * 📑 **TOC now considers H2 to H6.** The table of contents in Scroll Viewport's help center theme only showed heading levels 2 to 4. Scroll Sites' help center theme will include headings up to level 6. * ❌ **No support for legacy pages.** While Scroll Viewport never officially supported pages created with the legacy editor, some of its content still rendered in acceptable ways. Since Confluence is deprecating the legacy editor soon, Scroll Sites is no longer rendering its content correctly. We recommend to auto-convert all your pages to the new editor. Read more on [Convert pages to the cloud editor](https://support.atlassian.com/confluence-cloud/docs/convert-pages-to-the-new-editor/). 11. Close the site and go back to the Scroll Sites app. 12. From the sidebar, click **Go live**. By default, your replicated Scroll site's [update strategy](https://k15t.jira.com/wiki/spaces/STS/pages/14722629677) will be set to *Manual updates* to mirror the behavior of your Viewport site as closely as possible (content changes are published on demand through the click of a button). In Scroll Sites you now have the additional option to opt for [*Live updates*](https://help.k15t.com/scroll-sites/update-a-site#Live-updates) instead. If you'd like your content changes to reflect almost instantly in your site (requiring no additional action on your part), we recommend to check out this new option from**Site settings** \> **Update strategy**. *** ** * ** *** **Done with your upgrade?** It's now time to proceed and [delete the original Viewport site.](https://k15t.jira.com/wiki/spaces/VPRTDOC/pages/15560474629) --- language: "en" --- # Cards Name Updated Cards extension This is my new edit here to test You can find those cards here. This is my page edit --- language: "en" --- # Caro Release Testing Title This is my page, where I have a Scroll Page Title enabled. Juhuuu---This is my extra content for turtle --- language: "en" --- # Carousel Carousel extension --- language: "en" --- # Cde blocks inside lists * This is a list * Another list item * Code Example 2nd * Java import org.junit.jupiter.api.*; import static org.junit.jupiter.api.Assertions.*; class CalculatorTest { private Calculator calculator; @BeforeEach void setUp() { calculator = new Calculator(); } * Another list item * @Nested @DisplayName("Edge case tests") class EdgeCases { @Test void testAdditionWithMaxInt() { assertThrows(ArithmeticException.class, () -> calculator.add(Integer.MAX_VALUE, 1)); } @Test void testNegativeMultiplication() { assertEquals(6, calculator.multiply(-2, -3)); assertEquals(-6, calculator.multiply(2, -3)); } } --- language: "en" --- # Child page Macro and child items * [Problem and Solution Guide](https://goodsoftware.k15t.dev/spiegelei/problem-and-solution-guide.md) * [juhuuu, let's get more pans](https://goodsoftware.k15t.dev/spiegelei/juhuuu-let-s-get-more-pans.md) [Testing new page](https://goodsoftware.k15t.dev/spiegelei/testing-new-page.md) * [Problem and Solution Guide](https://goodsoftware.k15t.dev/spiegelei/problem-and-solution-guide.md) * [juhuuu, let's get more pans](https://goodsoftware.k15t.dev/spiegelei/juhuuu-let-s-get-more-pans.md) * [Testing new page](https://goodsoftware.k15t.dev/spiegelei/testing-new-page.md) --- language: "en" --- # Content Properties | Status | hello | | **Emoji** | 😃 ![check mark](https://goodsoftware.k15t.dev/__attachments/a_c396eb54b43b957a542558eb3397b54fa4f82b5a6d3da751ff7e221a4164c685/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | **Description** | This is a description also using **bold** and *italic* test | | **Date** | 2026-07-01 | | **Image** | ![sweating.gif](https://goodsoftware.k15t.dev/__attachments/a_e07fc0aa33e1a5105ea0af4b6e82c6e93e4b0f93f755f10e8c6dab51536ac1f6/sweating.gif?cb=7a20ddcc3657f1307bc4a3341bb5a7ec) | |-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| --- language: "en" --- # Content properties report | Title | Date | Description | Emoji | Image | Status | |----------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|--------| | [Copy of Copy of Content Properties](https://goodsoftware.k15t.dev/spiegelei/copy-of-copy-of-content-properties.md) | 2026-06-29 | This is a description also using **bold** and *italic* test | ![check mark](https://goodsoftware.k15t.dev/__attachments/a_c396eb54b43b957a542558eb3397b54fa4f82b5a6d3da751ff7e221a4164c685/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![sweating.gif](https://goodsoftware.k15t.dev/__attachments/a_a916f7d551d3242cd5010697b1301f61cba0ad2271590af7b93071c1915896e9/sweating.gif?cb=7a20ddcc3657f1307bc4a3341bb5a7ec) | hello | | [Copy of Content Properties](https://goodsoftware.k15t.dev/spiegelei/copy-of-content-properties.md) | 2026-06-29 | This is a description also using **bold** and *italic* test | ![check mark](https://goodsoftware.k15t.dev/__attachments/a_c396eb54b43b957a542558eb3397b54fa4f82b5a6d3da751ff7e221a4164c685/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![sweating.gif](https://goodsoftware.k15t.dev/__attachments/a_9a7955d1e485694d7b6505863ca3dff9c8026ea50edbfe32ec369acc41b6d682/sweating.gif?cb=7a20ddcc3657f1307bc4a3341bb5a7ec) | hello | --- language: "en" --- # Copy of Content Properties | Status | hello | | **Emoji** | ![check mark](https://goodsoftware.k15t.dev/__attachments/a_c396eb54b43b957a542558eb3397b54fa4f82b5a6d3da751ff7e221a4164c685/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | **Description** | This is a description also using **bold** and *italic* test | | **Date** | 2026-06-29 | | **Image** | ![sweating.gif](https://goodsoftware.k15t.dev/__attachments/a_9a7955d1e485694d7b6505863ca3dff9c8026ea50edbfe32ec369acc41b6d682/sweating.gif?cb=7a20ddcc3657f1307bc4a3341bb5a7ec) | |-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| --- language: "en" --- # Copy of Copy of Content Properties | Status | hello | | **Emoji** | ![check mark](https://goodsoftware.k15t.dev/__attachments/a_c396eb54b43b957a542558eb3397b54fa4f82b5a6d3da751ff7e221a4164c685/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | **Description** | This is a description also using **bold** and *italic* test | | **Date** | 2026-06-29 | | **Image** | ![sweating.gif](https://goodsoftware.k15t.dev/__attachments/a_a916f7d551d3242cd5010697b1301f61cba0ad2271590af7b93071c1915896e9/sweating.gif?cb=7a20ddcc3657f1307bc4a3341bb5a7ec) | |-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| --- language: "en" --- # Page added by Rovo This page demonstrates heading levels H1--H6, varied content blocks, and sample text for layout testing. It also showcases Confluence elements like panels, lists, tables, code blocks, and task lists. ## H1 --- Page Introduction Well Well Well piscing elit. Curabitur facilisis, nibh at lacinia pulvinar, nulla dui congue purus, vitae viverra mauris lectus et massa. Integer commodo, sapien sed eleifend facilisis, urna justo porttitor elit, a consequat risus augue non mi. ### H2 --- Context and Goals Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate. Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate.Proin nec nibh non lectus finibus mollis. Sed non sapien eget turpis varius fermentum. Integer eget urna id erat bibendum tincidunt. Pellentesque a ligula vitae libero volutpat malesuada. Cras fermentum justo id pellentesque vulputate. Use this section to verify styling, spacing, and semantic structure across headings and mixed content blocks. #### H3 --- Key Highlights * Consistent heading hierarchy for accessibility and scanability. * Representative paragraphs with varied sentence lengths to test wrapping and spacing. * Inclusion of lists, tables, code blocks, panels, and tasks to simulate real documentation. ##### H4 --- Example Table (Mixed Content) The table below contains formatted text, statuses, and future dates for layout validation. | Item | Status | Target Date | |-------------------------|-------------|-------------| | Typography review | In Progress | 2026-04-15 | | Content density check | Review | 2026-05-10 | | Cross-browser rendering | Complete | 2026-03-20 | ###### H5 --- Code and Technical Blocks Use code blocks to validate monospace rendering and line wrapping: Bash # Example build script echo "Starting build" mkdir -p dist && cp -r src/* dist/ echo "Build complete" Inline code examples can be included to test emphasis, e.g., `npm run build` and `yarn start` for local development. ###### H6 --- Tasks and Follow-ups * [ ] Scan heading hierarchy for consistency and spacing * [ ] Validate list, table, and panel styling across themes * [ ] Confirm code block readability and contrast All core layout elements are present. You can duplicate this page as a template for documentation styling tests. ### Additional Dummy Paragraphs Suspendisse potenti. Fusce porttitor, tortor ac viverra volutpat, nibh lorem tempus erat, at laoreet nisi ipsum at magna. In hac habitasse platea dictumst. Etiam dictum, arcu in efficitur dictum, lorem risus varius dui, ac iaculis nunc augue sit amet enim. Mauris at risus at nisl vehicula volutpat. Pellentesque accumsan eu sapien non fermentum. Nullam id bibendum tortor. Phasellus et nunc non mauris aliquam dictum. Nam pretium augue id nibh vehicula, vitae facilisis nunc vulputate. Cras vehicula gravida arcu, a tempus dolor condimentum a. Remember to replace placeholder text with real content before publishing. Keep headings meaningful and concise. #### References and Links Explore authoring best practices: * * * --- language: "en" --- # Excerpt testing Hi Hi, I am the **spiegelei** excerpt and this page is using `scroll-ignor `lable --- language: "en" --- # Exporters Extensions Scroll Exporters migrated 2026-07-07 to forge, this changes the storage format of the macros in the Exporter Extensions app as well. We need to add support for this. * scroll-ignore * scroll-ignore-inline * scroll-only * scroll-only-inline * scroll-content-block * scroll-tablelayout * scroll-portrait * scroll-landscape * scroll-bookmark * scroll-title * scroll-pagebreak * scroll-export-button ## Scroll Ignor on a scroll site ### Scroll Ignor but scroll site not selected If you see me on the site, this is how it should be, because I was unselected. ### Scroll Inline Ignor on a scroll site Here is my text Here is my text --- language: "en" --- # Filter by label on conditional content Testing conditional content with Turtle content * 📄 [Filter by label on conditional content](https://goodsoftware.k15t.dev/spiegelei/filter-by-label-on-conditional-content.md) * 📄 [(release 6-en) Mirrow Docs](https://goodsoftware.k15t.dev/spiegelei/mirrow-docs-4.md) * 📄 [(release 5-en) Mirrow Docs](https://goodsoftware.k15t.dev/spiegelei/mirrow-docs-3.md) * 📄 [(release 4-en) Preparation](https://goodsoftware.k15t.dev/spiegelei/preparation-1.md) * 📄 [(release 4-en) Second egg](https://goodsoftware.k15t.dev/spiegelei/second-egg-1.md) * 📄 [(release 5-en) Page 2](https://goodsoftware.k15t.dev/spiegelei/release-5-en-page-2.md) * 📄 [(release 6-en) Page 2](https://goodsoftware.k15t.dev/spiegelei/release-6-en-page-2.md) * 📄 [(release 6-en) This page is NEW in this version](https://goodsoftware.k15t.dev/spiegelei/release-6-en-this-page-is-new-in-this-version.md) * 📄 [(release 6-en) Page 1](https://goodsoftware.k15t.dev/spiegelei/release-6-en-page-1.md) * 📄 [(release 5-en) Page 1](https://goodsoftware.k15t.dev/spiegelei/release-5-en-page-1.md) * 📄 [(release 4-en) Include Page macro can show content from page that does not belong to the current variant](https://goodsoftware.k15t.dev/spiegelei/release-4-en-include-page-macro-can-show-content-f.md) * 📄 [(release 6-en) Second egg](https://goodsoftware.k15t.dev/spiegelei/second-egg-3.md) * 📄 [(release 6-en) My new page](https://goodsoftware.k15t.dev/spiegelei/my-new-page-3.md) * 📄 [(release 5-en) Second egg](https://goodsoftware.k15t.dev/spiegelei/second-egg-4.md) * 📄 [(release 4-en) Page 1](https://goodsoftware.k15t.dev/spiegelei/release-4-en-page-1.md) * 📄 [Filter by label on conditional content](https://goodsoftware.k15t.dev/spiegelei/filter-by-label-on-conditional-content.md) * 📄 [(release 6-en) Mirrow Docs](https://goodsoftware.k15t.dev/spiegelei/mirrow-docs-4.md) * 📄 [(release 5-en) Mirrow Docs](https://goodsoftware.k15t.dev/spiegelei/mirrow-docs-3.md) * 📄 [(release 4-en) Preparation](https://goodsoftware.k15t.dev/spiegelei/preparation-1.md) * 📄 [(release 4-en) Second egg](https://goodsoftware.k15t.dev/spiegelei/second-egg-1.md) * 📄 [(release 5-en) Page 2](https://goodsoftware.k15t.dev/spiegelei/release-5-en-page-2.md) * 📄 [(release 6-en) Page 2](https://goodsoftware.k15t.dev/spiegelei/release-6-en-page-2.md) * 📄 [(release 6-en) This page is NEW in this version](https://goodsoftware.k15t.dev/spiegelei/release-6-en-this-page-is-new-in-this-version.md) * 📄 [(release 6-en) Page 1](https://goodsoftware.k15t.dev/spiegelei/release-6-en-page-1.md) * 📄 [(release 5-en) Page 1](https://goodsoftware.k15t.dev/spiegelei/release-5-en-page-1.md) * 📄 [(release 4-en) Include Page macro can show content from page that does not belong to the current variant](https://goodsoftware.k15t.dev/spiegelei/release-4-en-include-page-macro-can-show-content-f.md) * 📄 [(release 6-en) Second egg](https://goodsoftware.k15t.dev/spiegelei/second-egg-3.md) * 📄 [(release 6-en) My new page](https://goodsoftware.k15t.dev/spiegelei/my-new-page-3.md) * 📄 [(release 5-en) Second egg](https://goodsoftware.k15t.dev/spiegelei/second-egg-4.md) * 📄 [(release 4-en) Page 1](https://goodsoftware.k15t.dev/spiegelei/release-4-en-page-1.md) --- language: "en" --- # First Egg Frist egg This change is made in Release 2 after the version was created and the version was added to the site. this is conditional content for **turtle** and **duck** only. Hello this is *special for turtle* conditional content on an inline fromat *special turtle and duck* | **content** | This page property should be visible for duck only | |-------------|----------------------------------------------------| --- language: "en" --- # (release 4-en) First Egg Frist egg This change is made in Release 2 after the version was created and the version was added to the site. --- language: "en" --- # (release 6-en) First Egg Frist egg This change is made in Release 2 after the version was created and the version was added to the site. --- language: "en" --- # (release 5-en) First Egg Frist egg This change is made in Release 2 after the version was created and the version was added to the site. --- language: "en" --- # Image captions whaaaaaat? This is a testing page if captions on images work. ![image-20251013-091630.png](https://goodsoftware.k15t.dev/__attachments/a_a5dbe0ce63b253bd17206dfbc1581362d50e806b6c6819f14b5b8bb8cbcf49c7/image-20251013-091630.png?cb=53405d48611127294fd0fa3848b76c69) Add some new captions now ![image-20251009-100252.png](https://goodsoftware.k15t.dev/__attachments/a_50c43805125461da9a4eafbee167fad6746b062f8ca797b33d7160b7d5d44124/image-20251009-100252.png?cb=ee5abefda8b6961bc3f0a4ef3a8ff949) What is happening if there is a very long caption---probably not an ideal user experience but could be also sometimes the case, right? --- language: "en" --- # Image map New image map [This is wild](https://goodsoftware.k15t.dev/spiegelei/release-2-and-a-child-egg-1.md "This is wild") Image Map, image deleted --- language: "en" --- # Images inside tables |-----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|----------------------| | **Egg** FRESH | *Mirror* ✨ | ++Reflection++ glow | | `Sunny side up` | | Golden yolk glow | | BOILED Boiled egg | * Polished shell | Oval echo **crack!** | | ![sweating.gif](https://goodsoftware.k15t.dev/__attachments/a_614e81f6653e4e69357d1ca83746d2e9bf743937687a43938e0513f919e537f7/sweating.gif?cb=7a20ddcc3657f1307bc4a3341bb5a7ec) | | | --- language: "en" --- # Include Page macro can show content from page that does not belong to the current variant This is my page 1 include Page 1 is labeled so that is part of the both variants A and B Page 2 is labeled so that it is part of only the variant DUCK When a customer includes a page via the Include Content (Include page) macro on the page Main article that belongs to all variants, and the included page Page 2 belongs only to variant A, content from variant A is shown also when viewing the Main article in variant B. Customer expects that browsing the Main article in the variant A shows only content belonging to the variant A, and browsing in the variant B shows only content belonging to the variant B. **Steps to Reproduce:** 1. Create a Main article that belongs to the both variants A and B 2. Add an Include Page macro including Page 1 1. Page 1 is labeled so that is part of the both variants A and B 3. Set up a second Include Page macro that includes Page 2 1. Page 2 is labeled so that it is part of only the variant A 4. Publish the site 5. Browse the Main article using the variant A 6. Switch to the variant B **Expected Result:** Each variant displays only the content that matches the selected variant. Include Page macro pointing to Page 2 (that only belongs to variant A) should resolve to empty content when browsing in the variant B. **Actual Result:** When browsing in the variant B, Scroll Conditional Content from Page 2 that should only belong to variant A is incorrectly displayed on the Main article. **Workaround:** Content authors can avoid this by either: (a) Ensuring any included page is accessible in all variants that the including page is in, or (b) Wrapping the Include Page macro in a Scroll Conditional Content macro labeled only for the variants the included content supports --- language: "en" --- # Include Scroll Sites No Publish Content This content includes the label `scroll-sites-no-publish` ![firehorse.gif](https://goodsoftware.k15t.dev/__attachments/a_0b4d274be1741eae0878a77174bbd264454218ac4f9654bfbe6cee53c828a638/firehorse.gif?cb=fafef05504172d29d4aea1abf8777961) Love my fire horse And here I link to the page which has the label to no publish the page → [Scroll No Publish Content](https://goodsoftware.k15t.dev/spiegelei/scroll-no-publish-content.md) --- language: "en" --- # Inline URL Links I am a URL link shown inline pointing to --\> this should show now the meta data of the link. In this case. Scroll Sites \| Launch branded, high-performance.... This should show the URL starting with https: .... I just need an edit --- language: "en" --- # Inserted Excerpt with warning panel ## This is a headline And here we have a short introduction text. * Adding some lists here * and there **This is a headline** And now we are adding long numbered text. 1. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor 2. incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. D 1. uis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariat 2. ur. Excepteur sint occaecat cupida 3. tat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. The following panel is from outside the content source added to the site **The source page of this panel is outside the added content** And now we are adding long numbered text. 1. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor 2. incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. D 1. uis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariat 2. ur. Excepteur sint occaecat cupida 3. tat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. --- language: "en" --- # IVPT-2205 Hello, this is my testing excerpt ✌️ Hello, this is my testing excerpt ✌️ --- language: "en" --- # IVPT-2223 | BookstoreType |||| | XML Element | Type | Required | Description | |------------------------|------------------------------------------------------------------------------|----------|--------------------------------------------------------------------------------------------------------------------| | Attribute: id | ID | Required | | | Attribute: established | gYear | Optional | | | name | string * Whitespacepreserve * Occurrence1 | Required | | | location | \[AddressType\] * Occurrence1 | Required | | | AddressType / street | string * Whitespacepreserve * Occurrence1 | Required | | | AddressType / city | string * Whitespacepreserve * Occurrence1 | Required | | | AddressType / state | \[StateCodeType\] * Pattern\[A-Z\]{2} * Whitespacepreserve * Occurrence1 | Required | | | AddressType / zip | \[ZipCodeType\] * Pattern\\d{5}(-\\d{4})? * Whitespacepreserve * Occurrence1 | Required | | | AddressType / country | string * Whitespacepreserve * Occurrence1 | Required | | | inventory | \[InventoryType\] * Occurrence1 | Required | \\totalItems\\\\ | | InventoryType / book | \[BookType\] * Occurrence0..unbounded | Optional | \\bookId\\\\language\\\\available\\\\ | --- language: "en" --- # juhuuu, let's get more pans dddd --- language: "en" --- # KS-41669 | Interface abbreviation | Meaning | |------------------------|----------------| | BM | Base module | | MX | MX module | | MI | Multi-input | | DO | Digital output | | e.g. MX-1: RS485-2 means the RS485-2 interface of the first connected MX module || **Interface abbreviations and meanings** --- language: "en" --- # KS-41878 ## **VSM Service Management** ### Unknown AttachmentManaged versus Unmanaged Environments Platform management forms a key overlay to the maintenance strategy and should be viewed as a separate but enhanced service over and above basic break-fix. Management services provide business focused information that represents a higher value to End User Customers through such enhancements as maximizing availability and providing detailed information that enables informed technology investment decisions to be made. When used as an overlay to maintenance, effective management of technical environments translates to a reduction of reactive maintenance activities by up to 80 per cent. ### Driving Proactivity VSM provides a never before seen view of the inner-workings of UC and Contact Center environments, enabling a proactive approach to delivering services. VSM Capacity reporting works at both an infrastructure and application level to effectively forecast problems before they arise and become service impacting. Technology departments fully understand that it is always much easier (and less stressful for engineers) to undertake planned changes to an environment to prevent a future incident as opposed to reacting to a reported incident. ### Maximizing Availability Reported incidents usually occur with little or no notice, and more often than not put staff under severe pressure due to the business disruption. VSM empowers Partners and End User Customers to forecast many different types of issues so they can be dealt with in a planned fashion, increasing Availability and minimizing business disruption. ### Improving Efficiency in Reactive Services Using VSM Capacity Management provides a wealth of information useful in reactive services such as fault investigation or Root Cause Analysis activities. VSM retains at least 12 months of data mined from many different sources. This enables engineers to 'travel back in time' to when the incident occurred to look at the circumstances in intricate detail. Often the information provided by VSM is not otherwise accessible or in its raw form is difficult to reconcile. In addition, the ability for VSM to depict a myriad of text-based data in a graphical format enables problems to be recognized at a glance. ### Direct Benefits of Platform Management In the following pages there are many examples of reports taken from real-world platforms encountering real-world issues. Virsae Partners and Customers providing supporting services to these platforms have been able to: * Provide design validation and tuning following an implementation * Predict and address incidents before they arise * React more quickly to restore service through ready access to information * Access detailed information to enable detailed root cause analysis * Identify opportunities for Service Improvement Planning * Identify in business as usual conditions opportunities for consolidation of assets * Provide solid information to improve accuracy of forecasting and budgeting *** ** * ** *** *** ** * ** *** ## **Useful links** | **Link** | |----------------------------------------------------| | [VSM Release Notes](https://goodsoftware.k15t.dev/spiegelei/release-notes.md) | | [VSM Support](https://support.virsae.com/) | | [Blogs](https://marketing.virsae.com/virsae-blog/) | ## **Latest Media** ### **Virsae and VOSS Form Strategic Partnership** A major step forward in AI-powered UC and CX management: VOSS and Virsae have announced a new partnership to deliver next-gen AI automation and analytics for collaboration and customer experience. 👉[Read more here](https://www.virsae.com/virsae-news/virsae-and-voss-form-partnership-to-power-next-gen-ai-automation-and-analytics/) Unknown Attachment --- language: "en" --- # KS-42236 These changes are created as [Party Variations](https://dev.wiki.k15t.dev/wiki/pages/createpage.action?spaceKey=carospiege&title=%28v1.50.4%29%20Party%20Variations&linkCreation=true&fromPageId=52758970369) in Altus. ## Change a Party's name works with approvals Various name fields may be changed on a Party, depending on the type: **Individuals**: title, first name, last name, middle names, suffix, known as, alternative name and salutation. **Organisations**: organisation sub-type, organisation name, organisation legal name and salutation. To change an aspect of a Party's name: 1. [Find the Party](https://goodsoftware.k15t.dev/spiegelei/v1-50-4-search-for-a-party-instrument-or-account.md) and view the **Party details** (the default view). 2. Click **Variations**on the right side of the horizontal navigation. Unknown Attachment 3. Click **Create Variation**. 4. Select **Change Name** from the **Variations**dropdown list. 5. **Edit the fields** required for the change. 6. Enter a **Reason**for the change. 7. Click **Save**. The change will be listed in the Variations log and cannot be deleted. If your organisation is using [++approval workflows++](https://goodsoftware.k15t.dev/spiegelei/v1-50-4-work-with-approval-requests.md) for this process, you will receive a workflow notification to advise that an approval request has been submitted for review. Unknown Attachment See also: [++Withdraw an approval request++](https://goodsoftware.k15t.dev/spiegelei/v1-50-4-search-for-a-party-instrument-or-account.md) ## Change a Party's details works with approvals **Individual Party** personal details such as gender, date of birth, country of birth, country of citizenship, country of residence, resident type, marital status and method of correspondence can all be changed with this variation. The Date of Birth field is ***required***for an individual, so if adding other details, you will need it in order to save your change. **Organisation Party** details can have principal country of business, country of residence for tax purposes and method of correspondence changed via this variation. 1. [Find the Party](https://goodsoftware.k15t.dev/spiegelei/v1-50-4-search-for-a-party-instrument-or-account.md) and view the **Party details** (the default view). 2. Click **Variations**on the right side of the horizontal navigation. Unknown Attachment 3. Click **Create Variation**. 4. Select **Change Party Details** from the **Variations**dropdown list. 5. **Edit the fields** required for the change. 6. Enter a **Reason**for the change. 7. Click **Save**. The change will be listed in the Variations log and cannot be deleted. If your organisation is using [++approval workflows++](https://goodsoftware.k15t.dev/spiegelei/v1-50-4-work-with-approval-requests.md) for this process, you will receive a workflow notification to advise that an approval request has been submitted for review. Unknown Attachment See also: [++Withdraw an approval request++](https://goodsoftware.k15t.dev/spiegelei/v1-50-4-search-for-a-party-instrument-or-account.md) ## Change a Party Number works with approvals A Party Number should be unique, however, sometimes importing or merging legacy data can create duplicates. In these cases, one of the duplicates should be changed. NB. Change a Party Number is only available for individual parties, not organisations. 1. [Find the Party](https://goodsoftware.k15t.dev/spiegelei/v1-50-4-search-for-a-party-instrument-or-account.md) and view the **Party details** (the default view). 2. Click **Variations**on the right side of the horizontal navigation. Unknown Attachment 3. Click **Create Variation**. 4. Select **Change Party Number** from the **Variations**dropdown list. 5. Edit the existing **Party Number**, perhaps following your organisation's format for these. 6. Enter an **ABA** (Australian Bankers Association) **Lodgement Reference** if you have one. 7. Enter a **Reason**for the change. 8. Click **Save**. Unknown Attachment The change will be listed in the Variations log and cannot be deleted. The altered party number will appear in the Party Details as the Alternative Number. Subsequent changes can also be made. Unknown Attachment If your organisation is using [++approval workflows++](https://goodsoftware.k15t.dev/spiegelei/v1-50-4-work-with-approval-requests.md) for this process, you will receive a workflow notification to advise that an approval request has been submitted for review. Unknown Attachment See also: [++Withdraw an approval request++](https://goodsoftware.k15t.dev/spiegelei/v1-50-4-search-for-a-party-instrument-or-account.md) **Approval workflows** may be used with these variations. * To enable the Approval Workflows feature, contact Interfi Systems. * To enable the workflow for this variation, see the [Approval Configuration Admin guide](https://dev.wiki.k15t.dev/wiki/pages/createpage.action?spaceKey=carospiege&title=%28v1.50.4%29%20Approval%20Workflow%20Configuration&linkCreation=true&fromPageId=52758970369). --- language: "en" --- # KS-42502 ## Summary Minimize your phone costs and improve your telecommunication bandwidth with SIP services. You may want to use SIP services to support basic inbound and outbound calls, inbound Toll-free calls, and/or integrate your UC solution with legacy or analog devices or services. ## Availability SIP trunk services are available in the United States, Canada, Mexico, South America, Europe, Asia, Oceania [BYOC only](https://nuwavecomm.atlassian.net/wiki/spaces/iug/pages/166920313), and Africa. ## What we offer ### Standard SIP services * Inbound and outbound calling for North America * International number inbound calling * Inbound toll-free calling * PSTN and on-premises PBX connectivity for voice * [++Disaster plan management++](https://dev.wiki.k15t.dev/wiki/pages/createpage.action?spaceKey=carospiege&title=Disaster%20plans&linkCreation=true&fromPageId=52823523329) ### UC integration with analog devices We can use SIP trunks to connect your UC solution with any analog line (or multiple analog lines) via ATA to voice, such as: * Legacy fax machines * Legacy analog phones/PBX lines * Paging devices and activation * Alarm lines * Multiple Soft clients * Doorbell activation * Elevator call button * Extension dialing to other external UC platforms ### SIP Interoperability (compatibility testing) Interoperability tests if two endpoints can communicate. We offer this compatibility testing to make sure your network can connect to our voice trunks to meet your unique needs before moving to your live environment. --- language: "en" --- # KS-42520 ## ![check mark](https://goodsoftware.k15t.dev/__attachments/a_c396eb54b43b957a542558eb3397b54fa4f82b5a6d3da751ff7e221a4164c685/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Heading Previous Setup (Scroll Viewport): Following your older documentation, we used to place our Call to Action (CTA) content inside an Excerpt macro (named "CTA") on our Confluence pages. On the portal, this rendered perfectly with all rich text formatting intact (headings, bold text, lists, etc.). Some **bold text** here * This is my testing list * And another list ## ![check mark](https://goodsoftware.k15t.dev/__attachments/a_c396eb54b43b957a542558eb3397b54fa4f82b5a6d3da751ff7e221a4164c685/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Heading Previous Setup (Scroll Viewport): Following your older documentation, we used to place our Call to Action (CTA) content inside an Excerpt macro (named "CTA") on our Confluence pages. On the portal, this rendered perfectly with all rich text formatting intact (headings, bold text, lists, etc.). ## ![check mark](https://goodsoftware.k15t.dev/__attachments/a_c396eb54b43b957a542558eb3397b54fa4f82b5a6d3da751ff7e221a4164c685/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Heading Previous Setup (Scroll Viewport): Following your older documentation, we used to place our Call to Action (CTA) content inside an Excerpt macro (named "CTA") on our Confluence pages. On the portal, this rendered perfectly with all rich text formatting intact (headings, bold text, lists, etc.). ## ![check mark](https://goodsoftware.k15t.dev/__attachments/a_c396eb54b43b957a542558eb3397b54fa4f82b5a6d3da751ff7e221a4164c685/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Heading Previous Setup (Scroll Viewport): Following your older documentation, we used to place our Call to Action (CTA) content inside an Excerpt macro (named "CTA") on our Confluence pages. On the portal, this rendered perfectly with all rich text formatting intact (headings, bold text, lists, etc.). [Next Page](https://goodsoftware.k15t.dev/llms-full.txt/1)