Hello All,

Am a newbie to Drupal, is Drupal right solution for the following requirements?

1. On click of 'Privacy Statements' in en email, User will be redirected to a 'Privacy Statements' page. Display 'Privacy Statements' such as 'browser Cookie storage', 'how the user information will be used', and 'other terms and Conditions'.
2. Multi language support of 'Privacy Statement'.
3, More importantly, user consent capturing (whether user accepts/declines the privacy statement). Once he makes the choice, he should not be prompted for user consent again. User will not create an account instead the email link will have a unique id for every user.

Thanks,
Novice

Comments

bander2’s picture

Drupal seems like overkill. I would develop a simple PHP application for this.

- Brendan

akashlee’s picture

I should have mentioned the workflow needed by business team
- Content Creation by one team and approval to publish them by other team
- Maintaining versions of all articles/content for audit purpose
- Flexible Vanity URL, and change them as and when needed
- Business team must be able to edit the content and publish without depending on the development team

Thanks,
Novice

Sam Moore’s picture

Drupal can do 1,2 and 4. You'll want to look at Workbench for content review workflow (https://www.drupal.org/project/workbench), and turn on revisions for #2.
#3 is more likely a server setting (read up on Virtual Hosts), as the Drupal codebase generally doesn't care what its hostname is.

bander2’s picture

In your OP, you are creating only one page, a "Privacy Statements" is that right? What are all the urls and workflows for?

- Brendan

akashlee’s picture

- Privacy Statements will be presented in multiple languages
- One page per language
- Each page will have its own URL such as /privacy/en (english), /privacy/fr (france), /privacy/jn (Japanese)
- Workflow : Author must create the content, and Approver must approve the content for publishing after the review
- User Consent : User after going through the privacy statements he can accept / decline them, when the same user visits again accept / decline should not be prompted as he already provided his consent, We must be able to store the user choice in a database.

bander2’s picture

Sam has answered how it can be done with Drupal. Personally, even with the additional workflow requirement, I would probably not use Drupal. I mean are we literally talking about a website that solely consists of privacy statements? One page translated into 5-10 languages (or 5-10 pages if you count a translation as a page)?

Setting up Drupal and a workflow is a lot of work for 5-10 even 20 pages. I would create a simple PHP application and manage the workflow with email/phone calls.

- Brendan