SharePoint
Feedback by UserVoice

Clint Lechner

My feedback

  1. 335 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    50 comments  ·  Sites and Collaboration » Document Libraries  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Clint Lechner commented  · 

    DO NOT REVERT BACK. Absolutely no reason to do so. We're trying to push using the online experience over desktop apps and users HATED when it was in VIEW mode and there were a million clicks to open a document.

    There's no reason to revert back. At all. If a document changes, then use verion history and change it back. If you don't know what version history is, learn about it immediately. Autosave and version history are two of the greatest features of Office 365 and if they aren't used you're missing out.

    An error occurred while saving the comment
    Clint Lechner commented  · 

    Absolutely do NOT change this. Default should always be edit. This is one of those times where learning a better process is far more advantageous in the long run, even if the beginning of the journey is frustrating. This move forced us to teach about version control and it has been a huge success (after a little education). This is also a great opportunity to talk about auto-save as well.

  2. 124 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    in the plans  ·  8 comments  ·  Sites and Collaboration » Modern Pages  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Clint Lechner commented  · 

    It's safe to say this is dead

  3. 170 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    16 comments  ·  Sites and Collaboration » Communication Sites  ·  Flag idea as inappropriate…  ·  Admin →

    We’ve reduced the height of the hero web part when in full width columns, but still maintain as much of the aspect ratio as possible. On a very large monitor this can still make the hero quite tall. Authors could also drag hero our of the full width column, into a one column layout (with gutters) , which significantly reduces the height. How would you imagine it should work differently in the full width, or is moving to a one column layout the right choice for reduced height? Thanks!

    An error occurred while saving the comment
    Clint Lechner commented  · 

    Agreed, love the hero part but we need a smaller option.

Feedback and Knowledge Base