James Loftus-Mercer

My feedback

  1. 175 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    I almost hear 3 feedback items here:
    1) Service hooks to integrate with other tools such as Slack, MSTeams etc.
    - This makes sense.

    2) Simple notifications on page updates
    2.1) Ability to follow a page to accomplish (2) i.e get notifications on page updates
    - This resonates with me a lot. I think we need to introduce Follow for a wiki page.

    3) Notifications when anything in the whole Wiki repo is updated. I feel this is a more admin rather than a user level feature .. am I thinking right?

    James Loftus-Mercer commented  · 

    +1 to Jeff Crowley's suggestion for a "recent updates" digest feature. As documentation repos grow and evolve, it can be very useful to be able to see "what's new" at a glance.

    I would love for that to be folder/section based, given that a single wiki can easily contain both important-to-daily-life policy docs as well as detailed references that devs don't necessarily need to follow as much (but conversely, reviewers of reference docs SHOULD follow every change to those).

    I don't particularly care if this takes the form of a widget, page, API, and/or email notification, but it would be very useful in maintaining large wikis.

  2. 46 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    James Loftus-Mercer commented  · 

    Should we expect permalink functionality in wikis published from our own Git repos as well as provisioned wikis?

    I use both extensively.

    James Loftus-Mercer supported this idea  · 
  3. 13 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    James Loftus-Mercer supported this idea  · 
    James Loftus-Mercer commented  · 

    I propose a variation that would keep things flexible (and also address Atwood's feedback, I believe): introduce an easy `save as draft` option for individual comments, plus a `send all drafts` action.

    The formal completion actions (accept/reject/waiting-for-author/etc) can all implicitly `send all drafts`, but it is useful to be able to send a batch of related comments without toggling your overall completion status.

  4. 17 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    James Loftus-Mercer supported this idea  · 
  5. 363 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    James Loftus-Mercer supported this idea  · 
  6. 83 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    James Loftus-Mercer supported this idea  · 
  7. 18 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    James Loftus-Mercer supported this idea  · 

Feedback and Knowledge Base