Evaluation of `What's New!` and `Discussions`

    Stories

      Reader or Member wants to read relevant documents and discussions.

      Site owner: Stay on top of a single community activity.

        We can achieve this only on web.

      Stay on top of whole directory activity.

      Stay on top of a single document activity.

      Read what the community thinks about this document.

        Discussions with context.

      Create a new Document

        User needs to know the location.

      Stay on top of my communities' activity.

        We can achieve this by creating custom feeds with documents.

      Read Discussions sorted by latest activity.

      Stay on top of my interests.

        Learn what are my intersts

          screen a feed

          (screen a list of topics —aka documents, with the comments)

        subscribe to my interests

    Personas

      Site Owner: community organizer, knowledge manager, expert on seed,

      Members: site readers, subscribers, writers, collaborators, which want to participate on the common goal of the site community.

      Reader:

    Customer Journey

      Site owner creates a site

      Writes Community Goal and initial Knowledge Structure to achieve the Goal.

      Members read the Knowledge Structure.

      Members add thoughts about the goal and Knowledge Structure.

      Site owner learns what is new.

      Site owner creates documents from those thoughts.

    Principles

      Decentralization.

      Knowledge creation

    Ideas

      Opportunity to simplify the product as a much as possible

        As simple as Twitter. No thinking about where to put a comment.

          Add

        As Wikipedia and Roam Research. No thinking about where to put a document. Just add links and backlinks to the document.

          No topics

        Only chose the community of people...

        we should give more imporance to member than site owner.

          site owner can add more items.

    HMWs

      Hard to find responses on the Discussion Feed.

      Confusing when I am on the Site Feed versus the Document Feed.

      I like to have the Comment Box always visible!

      Losing Context all the time from a feed item, a library item, or an email item to the document.

      How does it work on mobile and web.

      Filters: new comments only.

      Problems starts when there is more than one directory.

      I want only one feed

      Discussions References versus Targets

      I want to see the feed on the main page

      HMW know when I am seeing the whole directory activity or only the document activity.

      HMW, mention somebody on the web.

      HMW open my notification directly on the app

    Burdi

      I need chronological order.

    Why communities are hard to bootstrap?

        Community engagement

      Hypothesis:

        The app doesn't work

        We don't have email notifications for members (subscribers) Isabella Velez

          Substack style

        Members don't understand the app

          A reader needs to understand that this is a community, it is not a landing page, where the reader can collaborate and participate.

          We need a feed on the web

            Do we have feed on mobile web?

        Members don't understand how to engage: Bad UX

          Add discussions to query blocks

          Comment Box on Web Sites

            Signing redirect

          difficult to discuss

          difficult to read the feed

            a feed is a social layer

          I want web and mobile web: I don't want to make my members download the app

        The whole Join Community experience:

          I want to see the list of members.

          I can't invite members.

          Only members can add comments.

          Private Discussions for non-members

        Private Sites

        Not enough community members

        Not good site owner