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

Add UI to add and view Privacy policy and terms of use #2122

Closed
9 tasks done
bajiat opened this issue Feb 14, 2017 · 4 comments
Closed
9 tasks done

Add UI to add and view Privacy policy and terms of use #2122

bajiat opened this issue Feb 14, 2017 · 4 comments
Assignees
Milestone

Comments

@bajiat
Copy link
Contributor

bajiat commented Feb 14, 2017

User story

As an admin,
I want to be able to add privacy policy and terms of use to my deployment
so that I can meet the legal requirements.

As a user
I want to be able to see the privacy policy and terms of use
so that I know whether it is safe to register and give my user data.

Definition of done

  • Branding settings contain an option for adding a text or uploading a text file
    • for privacy policy.
    • for terms of use.
  • Text or file is stored.
  • Template footer needs to show links to
    • privacy policy
    • terms of use.
  • Links are only visible if the texts have been added.
  • There is a view/partial view/modal to show each of them.

Wireframe

  • In Setting -> Branding page, there is a new panel for adding Privacy Policy and Terms of Use panel.
    The panel comes before Colors pane and after site slogan field. (adding these is more important than changing color, so this pane should appear on top)
    The panel includes two file uploaders, one for Privacy Policy and one for Terms of Use.
    A help icon displays the text when clicked: "You can upload Privacy Policy and Terms of Use information as htm or html files. After uploading the file(s), related link(s) will appear on the site footer."
    brandingpage

  • HTML files can be uploaded here that defines Privacy Policy and Terms of Use for the site
    brandingpage2
    Attempting to upload a file with unsupported extension would prevent the upload. An alert text (made with CSS alert class) would be shown below related file uploader button
    brandingpage3

  • On adding privacy policy and terms of use files, links to see them appear in front page footer
    Terms of Use link also appears on the registration page.
    footer
    registrationpage
    When no file is uploaded, these links will not appear.

  • On clicking any of these links, user will be redirected to the related page on the site.
    (e.g. https://apinf.org/privacy_policy or https://apinf.org/terms_of_use)
    privacypolicy

@bajiat bajiat changed the title Add UI to add Privacy policy and terms of use Add UI to add and view Privacy policy and terms of use Feb 17, 2017
@bajiat
Copy link
Contributor Author

bajiat commented Feb 20, 2017

@NNN Would you be interested? If yes, please estimate

@bajiat
Copy link
Contributor Author

bajiat commented Feb 22, 2017

@Nazarah

Should we show alert with css alert class when someone wants to upload a file extension that is not .html? like a message "Only html file format is supported." and prevent the file uploading? Or we should include an info icon that provides this information?

At least we should give the alert that the only supported file extensions are htm or html. But I think the best option is to do both: alert for wrong file format and a help text (info icon)

@55 55 self-assigned this Feb 23, 2017
@bajiat bajiat added ready and removed planning labels Feb 23, 2017
@Nazarah
Copy link
Contributor

Nazarah commented Feb 24, 2017

@bajiat added the mentioned modifications in the wireframes.

@55
Copy link
Contributor

55 commented Mar 1, 2017

As discussed with @Nazarah @brylie, I will start off with simple solution, which inlcludes two area fields for user to paste correspoding text. As an enhancement we can add a richtext editor. We decided not to go with file upload. File upload here will lead us to new collections just for these files, iframes or others not the pretties ways to render documents, and other unnecessary long work to make it happen.

@55 55 mentioned this issue Mar 1, 2017
@55 55 added in progress and removed ready labels Mar 1, 2017
@55 55 added this to the Sprint 37 milestone Mar 1, 2017
@brylie brylie removed the in progress label Mar 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants