Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
  • Confluence

    4 articles in this category

      Related Pages for Confluence - discovering content just got easier

      Related information has been used on written content since it's inception, and now Confluence is adding functionality for this as well. It is a feature that not always is welcome, however, but don't worry, you get plenty of control to decide if it should be used or not. Not just per space, but even down to page level.
      While we don't have specifics on the algorithms that make this new Related information work, but we can probably assume that labels and keywords in title and headers in the content is used somehow. We do know that the related pages will honor permissions, so you can only see pages you have access to. The official information have this to say:
      When this rolls out, it will be turned on by default, which may be a bit annoying. Fortunately, you can turn this off for whole spaces in the Space settings under Space settings > Related pages. You can also turn this on or off on individual pages under More actions (•••), then Advanced details > and either Show related pages or Hide related pages.
      In the first iteration of related pages, it will not support Blogs or Jira Service Management customer portals. While this might seem strange as these two areas are where you normally would use this feature, but I think it is a good thing as they can tweak the algorithms a bit before taking that step. This should help make that feature better when it is released. This should help a lot with support if the algorithm is good enough, which I think it will be once they get some data from Confluence usage and tweak a bit first.

       

      5 new features in Confluence to kick off the new year with

      Nothing makes starting a new year as exciting as getting new, fun toys to play around with, and for Confluence we have five of them to talk about today! Not only will you get some nice new ways to present your pages and data withing, but we also get some features that might very well change the way you work. So let us dive in.
      #1 Page Status - a game changer?

      I don't think I have seen anyone using Confluence without having a status in the page properties to indicate the current status of a document. Now we get a built-in function for this that looks very useful indeed. I can think of a million uses for this, but the question is how this works with things like page properties reports and different listing macros.
       
      #2 Presenter Mode

      The presenter mode looked a bit weird at first, but it has quite a few use cases where it works very well. One being training or education, and another is to present reports to stakeholders. I think it is a pretty nifty feature to be honest!
       
       
      #3 Table visualization

      The wet dream of so many managers is to visualize data with graphs. While this may be a very limited experience compared to other tools, it is very much a step in the right direction.
       
      #4 Multiple Excerpt Macros

      For me who advocate the usage of one source of truth, this is a very good addition. I often use excerpts for design documentation and for non-functional requirements, and I have sometimes wished I could have two or more sections to embed in different ways. With his update, I can now manage these things more freely. I like it. A lot.
       
      #5 The new Confluence Home

      This change looks really great and I can't wait to see it live. If you want to read more about this change, then check out this article: https://community.atlassian.com/t5/Confluence-Cloud-articles/Say-hello-to-the-new-Confluence-Home/ba-p/1892543
       
      These are just a few of the new changes coming to Confluence in 2022 and I will do my best to cover all of them here on the blog and on the YouTube channel.
      Which is your favorite of these and why?

      End of support for Confluence gadgets - four gadgets are being deprecated in May

      Atlassian is ending their support of four gadgets for Confluence Cloud at the end of May. The gadgets will still work after that if you are already using them, but you will not be able to add them into the legacy editor or the new editor using the macro browser, slash command, or a shortcut key. Three out of four gadgets are replaced with macros.
      The time has come for gadgets to fade away and be replaced by the more modern macros for Confluence Cloud. While the gadgets will still work on your confluence pages, you will no longer be able to add them to pages. That goes for legacy and new editor as well as for macro browser, slash command and shortcut. If you want similar functionality then there are macros suggested for all but the news gadget.
      Activity Stream gadget
      The Activity stream gadget shows a list of recently changed content in your site. Atlassian recommend using the Recently Updated macro as an alternative in Confluence. 
      Confluence Page gadget
      This gadget displays the contents of a Confluence page. Atlassian recommend using the Include Page macro as an alternative in Confluence.  
      Confluence Quick Nav gadget
      This gadget provides a search field that can be used to search for page titles in Confluence. Atlassian recommend using the Livesearch macro as an alternative in Confluence. 

      News gadget
      This gadget previously displayed blogs and other news from Atlassian. It has no suggested alternative.
       
      End of support means that Atlassian will no longer fix bugs for these gadgets. If your Confluence site is integrated with a Jira site, any Jira gadgets installed in Confluence ARE NOT IMPACTED by this change. You can continue to insert Jira gadgets into any Confluence page.

      The new page comments on Confluence Cloud

      Confluence cloud get some new features for the comments in the coming weeks. It includes quick commands and access to more macros. My question however is if we actually need this or if comments in general need a different approach?
       
      "Comments are where important discussions happen inside Confluence. Feedback and questions in page comments shape ideas and keep work moving forward. We've dedicated a lot of time to improving the experience, because we know comments are important to our customers and their team collaboration. The new experience is meant to help your teams better express themselves and have meaningful conversations."
       
      In my experience comments in Confluence is not really used as much as I think Atlassian believe. Mostly this is because inline commenting is often more efficient or because commenting is used less due to direct communication. So adding more features to the commenting part of the Confluence experience does seem a bit unnecessary.
      One concern I have about bloating the comment section is that we will see it used instead of editing the pages properly. I have seen in in other areas where it become easier to just add comments than actually use the proper way to document. Adding more functions also have the risk of making the comment section harder to use. Just adding large images and tables with data makes this area quite messy.
      Still, I like the "/" command that is very similar to the one used by Notion and having the option to use comments in a more powerful way is not necessarily a bad thing. Interestingly enough the news met with several questions on when comments will be available in edit mode, which seem to be a more requested feature at the moment...
       

×
×
  • Create New...