diff --git a/source/en/attributions.txt b/source/en/attributions.txt index 20a5b89..f8c4422 100644 --- a/source/en/attributions.txt +++ b/source/en/attributions.txt @@ -336,6 +336,10 @@ Here is a list of the sections of the document and their sources and authorship: Written by https://www.drupal.org/u/diana.lakatos[Diána Lakatos] at http://pronovix.com[Pronovix]. +<>:: + Written by https://www.drupal.org/u/hey_germano[Sarah German] at + https://www.advomatic.com[Advomatic]. + ==== Preventing and Fixing Problems <>:: diff --git a/source/en/security-announce.txt b/source/en/security-announce.txt index 802c9df..1b89be1 100644 --- a/source/en/security-announce.txt +++ b/source/en/security-announce.txt @@ -1,127 +1,47 @@ -// This template is for a topic that covers how to perform a task. -// -// To use this template: -// - Copy it to your source directory with a new name, such as -// "block-creating.txt". [The project coordinators may already have done -// that for you.] -// - Follow the instructions that are contained in lines starting with // -// throughout this file. -// - Replace placeholder text with your content. -// - Before you submit your topic, remove all the lines in the file that -// start with // -- these are comments that do not belong in the topic. Also -// remove any blank lines that are before the ID line. -// - Then, if there are sections that do not apply to your topic (for example, -// Prerequisites might not), put // before the ==== on that line and leave -// those lines in the topic file. So it would look like: -//==== Prerequisite knowledge - - -// The first thing in the file is an ID: replace the text in the brackets below -// so that it matches the name of the file (without the .txt extension; for -// example, [[block-create]] if the file name is block-create.txt. [[security-announce]] -// The topic title goes on the next line. Use "Title Case" for topic titles. -// Titles for task topics should be in the format "Verbing a Noun". -=== UNWRITTEN - Keeping Track of Updates -// The next thing that is needed is an entry for the index: -// - Replace the text in (((Nouns,verbing))) with an appropriate index entry, -// such as (((Blocks,creating))). You can add additional index entries if -// appropriate. -// - Refer to the Guidelines if you have questions. -// - Also remove the // before the ((( so that this becomes an index entry -// and not a comment. -//(((Nouns,verbing))) +=== Keeping Track of Updates +(((Updates,following))) ==== Goal -// Describe the goal of this task here. This should be the goal for the reader, -// so describe the end result, like "Create an About page". It should relate to -// the Scenario and be specific rather than generic. - -Remove this placeholder text. - +Keep your site safe and up-to-date by keeping up with the latest security updates. ==== Prerequisite knowledge -// This section should mostly link to topic and concept tasks within -// the guide that someone would need to understand before trying this task. -// Some of the entries could be background knowledge that is needed that is -// not covered in the guide. -// -// Some ideas (remove the // to make these not comments): -//* <> -//* <> -//* How to upload files from your local server to your web server. - -Remove this placeholder text. - - -==== Site prerequisites - -// The items below are an example of what might go here for a task where -// a "most recent image" view is created. They describe things that must be -// present on the site (configuration, content, etc.) in order to perform -// this task. -// -// Some ideas (remove the // to make these not comments): -//* A content type is defined with an Image field. See <>. -//* At least one published content item of this type exists. See -// <>. - -Remove this placeholder text. +* <> +//==== Site prerequisites ==== Steps -// This is where you describe the actual steps needed to perform this task. -// Remember to use the scenario and be specific, not generic. - -. Text of step one goes here. The subsequent lines of this step need - to be indented by two spaces. +There are a few different ways to receive notifications of security releases: - And it could be a couple of paragraphs. +. In the _Manage_ administrative menu, navigate to + _Reports_ > _Available updates_ > Update Manager settings. Fill in the email addresses + to be notified when updates are available, and click _Save configuration_. -[start=2] -. Text of step two goes here. If you preview the output and the numbering is - wrong, you can use this start=(number) line to set the numbering correctly. +. Subscribe to the security announcements email list. To subscribe, log in to Drupal.org, + go to your user profile page and subscribe to the security newsletter on the _Edit » My newsletters_ tab. -. Text of step 3. +. Follow @drupalsecurity on Twitter. -Notes: - -* If your task involves filling out a form, include a screen shot. -* Also include a table of fields and values to fill in. -* The last step should be something that shows them the task has been - completed. Include a screen shot. - -==== Follow-on tasks - -// In this section, you can make cross-references to other task topics in this -// book that are related. You can also make suggestions for tasks that someone -// who just learned this task might be able to do that are not in the book -- -// try to think of tasks that would help someone solidify and broaden their -// skills and knowledge, especially other tasks related to the scenario. -// -// Some ideas (remove the // to make these not comments): -//* <> -//* Brief description of another task not in the book. - -Remove this placeholder text. +. Subscribe to RSS feeds for http://drupal.org/security/rss.xml[core], + http://drupal.org/security/contrib/rss.xml[contrib] and + http://drupal.org/security/psa/rss.xml[public service announcements]. +//==== Follow-on tasks ==== Related concepts -// In this section, add links to related concept topics, if any. - -Remove this placeholder text. - +* <> +* <> +* <> +* <> ==== Additional resources -// In this section, make a list of outside references: videos, Drupal.org -// documentation, etc. Make sure all links have link text showing the name -// of the article or page it being linked to. - -Remove this placeholder text. +* https://www.drupal.org/security[Security advisories] +* https://www.drupal.org/security-team[Security team] +* https://twitter.com/drupalsecurity[Drupal Security on Twitter] \ No newline at end of file