Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update userdocs for file status icons #971

Closed
2 tasks done
emteknetnz opened this issue May 26, 2020 · 5 comments · Fixed by #980 or silverstripe/silverstripe-userhelp-content#146
Closed
2 tasks done

Update userdocs for file status icons #971

emteknetnz opened this issue May 26, 2020 · 5 comments · Fixed by #980 or silverstripe/silverstripe-userhelp-content#146

Comments

@emteknetnz
Copy link
Member

emteknetnz commented May 26, 2020

Relates to work done in silverstripe/silverstripe-asset-admin#1066

and should cover both the two 'userform submission' icons and the 'restricted access' icons.

ACs (draft)

  • The meaning of the new icons are understood
  • It is clear how updating the file permissions will alter the icons
  • There is a clear connection within the guide on file permissions as a broader topic (this isn't only userforms related)
  • There is background provided on why these icons have been created, and what they aim to help with, i.e stronger exposure to the potential risk of not realising restricted files are being exposed to the public/ website visitors
  • All areas where these icons can be seen are noted

PRs

@sachajudd
Copy link
Contributor

sachajudd commented May 26, 2020

This will rely on #960 being merged and also preferably #970 in the near future but isn't a blocker.

@brynwhyman
Copy link

I've added some draft ACs to help set the scope

@clarkepaul
Copy link

This is currently in progress by the Silverstripe UX team.

@brynwhyman
Copy link

Ready for peer review :) added PRs to the description

@sachajudd sachajudd removed their assignment Jul 6, 2020
@sachajudd
Copy link
Contributor

Updated and reassigned to @bergice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment