Skip to Content
author's profile photo Jelena Perfiljeva

[Status update]New community page - I literally can't even...

Caught the featured announcement on the home page: new page created for "Community news":

I guess this was well-intended and maybe there is some value, dunno. But here are my questions.

1. "News and tips". What do tips have to do with news? Is there Google News and Tips page? No! For a good reason. You look at tips only once, not daily or even monthly. (Now "news and jokes" would be a fine combination.)

2. Tag "#1dxcommdest" - who outside of SAP will remember that?

3. There is no "Follow" option. How would anyone know if the page is updated?

4. How will anyone find this page? It doesn't seem to have a link on the home page. If it's actual important news then put it right on the home page. That's what it's for! And put "tips" under Getting Started. We don't need more complexity.

[Head meets desk]

* Please Login or Register to Comment on or Follow discussions.


  • Feb 03, 2017 at 10:16 PM

    Are these "Tips in a Minute" called that way because they take that long to load?

  • Feb 06, 2017 at 08:19 AM

    Correct me if I am wrong, but the page seems to be static... this means additional effort to maintain yet another page, which is just as hard to find as about anything else in SAP community.
    I can't see how SAP Community Beta Tester Badge is relevant to news or tips - if I remember correctly, gamification in terms of missions and badges was postponed for the 'greater good' - until the most critical problems with the forum are solved.
    The process of reporting bugs and sharing feedback was already explained in another page - How duplicating information is going to help the SAP team and the forum members? And if both pages have to be maintained separately, what is the added value?

    What could add value on either of these pages, would be a link to display all open bugs and feature requests for SAP Community, their status and planned date for the fix, where the members can track the process of their submitted bug reports or check if what they are about to report as a problem, for which a fix is already under development.

  • Feb 06, 2017 at 08:29 AM

    Hi Jelena,

    thanks for pointing this out to us!
    I noticed it today, too (via Community Overview), here is what I was going to write:
    "As far as I can tell there's no new content, but maybe it's nice to have a(nother) place of aggregation."

    Reading your Points, I do agree to all of them!

    I could imagine checking that page from time to time, as I do with other pages, but I hope to get the news faster via RSS on the "Using"-Tag.

    I'm sure there are good intentions behind that page, and if it's not useful to us, maybe it's useful to others.


  • Feb 06, 2017 at 08:58 AM

    Oh, on 4.: It's linked on the About-Page now:

    • Feb 06, 2017 at 10:14 AM

      Apologies about the off-topic, but what have blogs in SAP Community got to do with the wrench?

      • Feb 06, 2017 at 10:23 AM

        According to the state of the Community sites, the wrench should be used as an overall symbol, right? :)

      • Feb 06, 2017 at 10:35 AM

        I guess they only have a limited number of default pictures to work with. Maybe it would be better to get rid of those and just use an orange line or something as distinction to the next line of text and links.

      • Feb 06, 2017 at 06:20 PM

        Old SCN also had funny picture choices after the migration. I think they got changed at some point later. Also if blog is in ABAP tag then wrench is totally relevant. :)

        SCN team could've ran a contest for new pictures. At least this would've distracted people from all the problems and gave them something to do. Opportunity missed!

  • Feb 06, 2017 at 08:59 AM

    The page is linked in the "About the Community" page on the right side. So... easy to find... ^^

    • Feb 06, 2017 at 05:42 PM

      Don't even get me started on "About the Community" page. It looks like something from a website a small mom-and-pop shop would put together based on a template they found in Google. Well, actually the SCN home page has kind of the same vibe...

      • Feb 06, 2017 at 08:01 PM

        I am not a web designer, so I searched in Google for web design guidelines images and, just 2 minutes later, I came across this article: Photos as Web Content. I suppose, that the web designers and UX experts in SAP are also aware of such studies and would apply the knowledge in pages.
        **Just because the article in the link is more than 6 years old, it does not mean that people's reading behavior has changed dramatically since then.**

        • Feb 06, 2017 at 08:22 PM

          Great article! I'm also not a web designer but had to look this up after the SCN migration (clearly the goal was to make us learn more new stuff! :) ) and made the same conclusions that web design is not good in general and especially not suitable for the knowledge sharing website.

          But finally this article shows actual eye movement tracking and how "users ignore stock photos of "generic people".

          I rest my case.

  • Feb 06, 2017 at 11:20 AM

    There's another point about something not being linked I wanted to make:

    A while ago, I found a blog that seem to have no original content.

    When I asked about it in the comments, I found out it's a link-target for social media.
    That's a use case I had never thought of, but seems totally valid to me now.

    I think my takeaways are:

    • even if I don't see the use for something, there still might be one;
    • even if something seems useless to me, it might be helpful for others;
    • asking helps gain understanding, so it’s good to always have a “comments”-section or some other offer for interaction and feedback.
      (I think this goes along with that #empathy thing!) ;- ) )



    • Feb 06, 2017 at 06:13 PM

      I really want to know who would find this page helpful. When I saw "content tagged with.." at first I thought "oh, finally, a dynamic page" but, as Veselina pointed out, it seems to be static.

      Agree with you on the "comments section". Well, CC has been our improvised "SCN feedback" section so far :)

  • Feb 06, 2017 at 08:19 PM

    #4 -- use search. anyone who wants news about something searches for it. ;)

    • Feb 06, 2017 at 09:03 PM

      "OK, Google and Siri, read me latest SCN, errr, SAP Community news"? Rrrrright... :)

    • author's profile photo Former Member
      Former Member
      Feb 08, 2017 at 07:00 PM

      I still need to get used to the new Community experience, but for the new Q&A feature, I would like to make a suggestion, which I hope it's easy to implement: In the main Q&A page, there is filter to sort by datetime. After putting in filter criteria, the sort function disappears. For those who would like to contribute by providing answers, we would quickly lose interest if we do not see questions catching attention on the first page of result.

      Or maybe the filter is there, but somehow I miss. Please point it out. Thanks.

  • Feb 07, 2017 at 12:30 PM

    I created the page because of complaints that we didn't have a centralized location for the release notes, planned updates, etc. -- such as this #1dxcommdest page from the SCN days:

    Now to address the points:

    1) I disagree. The Tip in a Minute videos are meant to help anyone, at any time, and there's no reason for me to assume that everyone has seen them already. I see value in providing an area where all these videos are compiled, along with links to FAQ information. (The old #1dxcommdest page also combined all of this information and more.)

    2) You'd be surprised. I've had people ask about that tag specifically, as they were accustomed to searching for it on SCN. That being said...I've never been crazy about that tag. It was around long before I joined the team, so I inherited it. I am taking steps to introduce a more intuitive tag -- and one that isn't a user tag (as I don't think Using is all that effective either for general SAP Community announcements).

    3) All of these static pages within About the Community are static pages, I'm afraid. I have requested that these pages have follow options. For now, I plan to promote via social media and the home page, which brings me to...

    4) I agree but I don't control the home page. And let's face it: Even if I did find it a spot on the home page, I'd still receive complaints that people can't find it there. I'll see what I can do...

    Addendum: "I really want to know who would find this page helpful."

    That would be me.

    [Head meets desk. Twice.]

    • Feb 07, 2017 at 07:53 PM

      I truly appreciate the hard work by the project team and the steps taken for a better transparency on what is delivered, I really do.
      But why it has to be presented in such complicated manner?
      Mozilla, even Microsoft, have found more efficient ways to achieve that:
      1. You have release notes (Mozilla) or update packs information (Microsoft)
      2. If you wish to learn more about a specific fix - there are links for more detailed info from the release notes or the security rollup page to CVEs (Mozilla) or MS Security Bulletin (Microsoft). Mozilla takes this a step further by providing links to Bugzilla.
      Translated to our case:
      1. Keep the Release notes in the Wiki (we have no other way to get notifications for changes), if - feasible, consider implementing stickies or a really unobtrusive news ticker (if downtime or service disruption is expected).
      2. Start writing the release highlights blogs in a way, so that each important bugfix or a new feature can be linked to an item in the release notes. If this is technically possible - consider a functionality to link to a specific position in a blog.
      3. Add links to the bug reports (in most cases these are questions in, optionally add a link to a public view of the bug tracker, which is used for this project.

      There is not much benefit in scattering the information and duplicating it in several places, if the pages are not dynamic - it only increases the work done for the project members, instead of using the time for testing new functionalities or clarifying requirements.
      As for tip in a minute: if a forum member, who is not newly registered, needs to re-read/replay the tips, then the provided solution is probably too complicated or there is not enough guidance during the process. #justmy2cents.

      • Feb 07, 2017 at 09:45 PM

        I suspect that the community was actually looking for just a simple document like we had in the SDN/SCN migration and in the beta. It was a list of the identified bugs and built-in links to the respective discussions/blogs and a status.

        Sadly, SCN is starting to remind me of this oldie but goodie:

      • Feb 08, 2017 at 06:54 PM

        Thanks for the suggestions, Veselina. I am trying to achieve some of the things you described -- but, frankly, only for the pages and content I can own. I'm not in a position to implement everything you described, but I can and will pass along to someone who is in a better position to gauge and execute.

        I must point out that I don't like saying, "Thanks, I'll pass it along." I say it an awful lot. And I do it. But from a member perspective, a "just do it" attitude and approach would be preferable, I know. In my case, I've taken charge of the areas within my control so I can push out information that I think the community wants. Any complexities are because of my shortcomings in attempts to tie so many moving pieces together -- and in no way a reflection on my colleagues or the various team members dedicated to improvements. Communications is my bailiwick...for better or worse. I figure getting the information out faster, even in a less than ideal fashion, is better than silence. I still believe that's the right philosophy, although I do regret any frustrations it may cause -- and I'll continue to listen to feedback to try to do things better.

    • Feb 07, 2017 at 08:05 PM

      Jerry, are you disagreeing that Tips have nothing to do with News? Not sure I understand the train of thought then... I was not saying no one needs tips at all, I was questioning them being combined with the news content on the same page. The SCN team has already made a mistake (IMHO) by combining "known issues" with FAQ. What is the reason for such odd content combinations? Do you have some kind of web page quota? Sorry but I just can't understand the logic. News are news and tips/FAQ is the whole different content type with much longer shelf life than typical news.

      I suspect SCN members would have no problem finding content on the home page if only (1) it was structured logically (and here I mean not SAP's own logic but a typical visitor's logic) and (2) SAP would get rid of the useless hero images taking up the whole screen. I understand that it's not your jurisdiction but then whoever is responsible for this needs to get out more IMHO.

      • Feb 08, 2017 at 06:32 PM

        My point is that with the old SCN, we had the #1dxcommdest (more on that in a sec) page which consolidated all information related to the launch. I was simply trying to replicate that approach with a page that combined everything about the new community -- from development updates to tips about how to get the most from the new platform. This seemed logical to me (and followed a pattern already established, which I assumed the community would prefer because they were accustomed to it from SCN), but defending my intent is moot at this point. Considering the criticism the page is getting here and elsewhere, I need to rethink and revamp it. While I'm at it, I'll put the whole #1dxcommdest reference out of its misery. I agree that it's outlived its usefulness and causes more confusion than clarity at this point.

        I also agree about this: I don't like the fact that the FAQ and known issues are tabs on a single page. I am taking steps to separate into two pages and, at the same time, update the "known issues" to reflect what's been fixed and what's been prioritized.

        All of these things are on my to-do list.

  • Add a comment
    10|10000 characters needed characters exceeded