[documentation] security pages in handbook

[O Govinda]

Greg Knaddison-3 wrote:
> 
> 
> So far we've identified 3 groups of people we want to target with these
> pages:
> 
> 1) Drupal "site admins" who need to know how to configure their sites,
> how to get notifications about security updates, and what to do if
> they think they have been a victim of a security attack.
> 
> 2) Drupal coders - people who write modules and need to know how to do
> this safely.
> 
> 3) Evaluators / Managers who are less technical and need justification
> that yes, Drupal cares about this and yes, they should too in
> prioritizing their budgets and project plans.
> 
> 

Then I'd organize the hierarchy that way:

  1. Info for site admins (you're running a Drupal site)

  2. Info for coders  (you're writing code for Drupal)

  3. Info for evaluators (you're looking into possibly using Drupal)

If there's stuff (for example, "security team") relevant for two or all
three users, I'd post it redundantly under both or all three categories. 

Cordially, 
O Govinda
-- 
View this message in context: http://www.nabble.com/security-pages-in-handbook-tf4622042.html#a13212625
Sent from the Drupal - Doc mailing list archive at Nabble.com.