Same for me. We have a glossary with short explanations of important terms. We used the excerpt-include-macro to add this explanation on other pages as part of the description there. With that we had a single place where we defined terms. With the excerpt-include-macro no reader had to follow the link to get this valuable information.

This is an undesirable difference between the legacy Server-Version and the Cloud-Version.

This would be very useful for us with our migration from server to cloud! It is also a potential deal breaker for another team in my organisation who is considering moving their help documentation to confluence.

In server, the 'excerpt include' macro text displays inline (without inserting hard returns), so we used this macro extensively as way to include icons and snippets of text within paragraphs. By keeping icons and snippets in one place, and then using the 'Excerpt include' macro, we could:

• easily insert commonly used instructions and icons consistently
• easy to change them. e.g. if we updated an icon, we just need to update it on page that had the 'excerpt' macro, rather than searching through every page and replacing them one by one

For example:

• We have an page with an excerpt that contains an icon and (the 'remove surrounding panel' has been ticked)
• On another page, we use the 'include page macro' to include the icon. In the editor view, it displays inline, which is what we're hoping for
• When we publish the page it inserts unwanted hard returns around the macro (same as in the original description for this issue

It would be great if it appeared in line in the same way as it appears in the editor view.

When we migrate to cloud, if a new line is inserted before and after the 'Excerpt include' macro, then we'll have to replace all our 'excerpt include' macros with the actual content and in addition to the time this would take, we will lose quite a bit of efficiency and ease of maintenance in our future editing.