Commit 6e493b16 authored by guiu.rocafort.ferrer's avatar guiu.rocafort.ferrer

Updated English source files for Spanish translations to last version

parent 96345ba0
When videos are embedded in a guide page the video producer must provide
instructions for downloading the translatable caption file, translating, and
providing translations so they can be added to the video.
The following is a list of video producers and instructions for translating
captions from each.
Drupalize.Me
------------
https://drupalize.me
Captions for all videos produced by Drupalize.Me are provided in English and can
be translated to other languages using dotsub (https://dotsub.com). Instructions
for how to use dotsub to translate files can be found here:
https://drupalize.me/blog/201210/crowd-sourced-subtitles-free-drupal-videos
You may also use a tool of your choice for translating the captions; as long as
they can be exported and provided to us in SRT format we can incorporate them.
If you would like to use another tool please get in touch with us at
info@drupalize.me so we can incorporate your translations.
English, and any existing translated, captions can be downloaded from
https://dotsub.com/view/user/drupalizeme
Choose the video you would like to retrieve captions for and then use the
download tool on the resulting page.
Drupalize.Me currently has videos embedded on the following English language
guide pages:
- block-create-custom
- block-place
- config-basic
- config-install
- config-theme
- config-uninstall
- config-user
- content-create
- content-edit
- content-in-place-edit
- extend-config-versions
- extend-deploy
- extend-maintenance
- extend-manual-install
- extend-module-find
- extend-module-install
- extend-theme-find
- extend-theme-install
- install-composer
- install-dev-making
- install-prepare
- install-run
- language-add
- language-config-translate
- language-content-config
- language-content-translate
- menu-home
- menu-link-from-content
- menu-reorder
- planning-layout
- planning-structure
- prevent-cache-clear
- security-announce
- security-cron
- security-update-core
- security-update-module
- security-update-theme
- structure-adding-reference
- structure-content-display
- structure-content-type
- structure-content-type-delete
- structure-fields
- structure-form-editing
- structure-image-style-create
- structure-taxonomy-setup
- structure-text-format-config
- user-content
- user-new-role
- user-new-user
- user-permissions
- user-roles
- views-block
- views-create
- views-duplicate
......@@ -55,6 +55,11 @@ _Edit_ to make changes.
//==== Related concepts
==== Videos
// Video from Drupalize.Me.
video::https://www.youtube-nocookie.com/embed/sI2wrbn3cPg[title="Creating a Custom Block"]
==== Additional resources
https://www.drupal.org/docs/8/core/modules/block/overview[_Drupal.org_ community documentation page "Working with blocks (content in regions)"]
......
......@@ -40,10 +40,10 @@ it. The _Configure block_ window appears. Fill in the fields as shown below.
+
[width="100%",frame="topbot",options="header"]
|================================
|Field name | Value
| Title | Hours and location
| Display title | Checked
| Region | Sidebar second
|Field name |Explanation |Example value
|Title |Title to be displayed for the block |Hours and location
|Display title |Whether or not to display the title with the block |Checked
|Region |Which theme region to display it in |Sidebar second
|================================
+
You can also hide or display the block on specific pages. In the case of the
......@@ -55,8 +55,11 @@ because you want to show the block everywhere.
image:images/block-place-configure-block.png["Block configuration page",width="100%"]
--
. Click _Save block_. The _Block layout_ page appears. You can drag blocks to
change the order in which they will appear.
. Click _Save block_. The _Block layout_ page appears. You can drag the cross
bar handles of blocks to change their order within each region. As an
alternative to dragging, you can click the _Show row weights_ link at the top of
the table and select numerical weights (blocks with lower or more negative
weights will be shown first).
. Verify that the Opening hours and location block is listed in the _Sidebar
second_ region, and click _Save blocks_.
......@@ -71,11 +74,17 @@ image:images/block-place-sidebar.png["Page with a block placed on the Sidebar se
==== Expand your understanding
* Remove the _Powered by Drupal_ block from the _Footer_ region by setting the
region to _- None -_.
* Remove the _Powered by Drupal_ block from the _Footer fifth_ region by
clicking _Disable_ or _Remove_ in the _Operations_ dropdown button. Clicking
_Disable_ will let you enable the block easily later with the same
configuration; if you click _Remove_ and you want the block back, you would
need to go through the steps in this topic to place it in a region again. Note
that the names of the blocks that are provided by the core software, such as
_Powered by Drupal_ and _User login_, are shown in English on this page; see
<<language-concept>> for an explanation.
* Remove the _Tools_ block from the _Sidebar first_ region by setting the
region to _- None -_. This block is only visible to logged-in users.
* Remove the _Tools_ block from the _Sidebar first_ region. This block is only
visible to logged-in users.
* Place the _User login_ block in a region.
......@@ -85,6 +94,11 @@ to clear the cache. See <<prevent-cache-clear>>.
//==== Related concepts
==== Videos
// Video from Drupalize.Me.
video::https://www.youtube-nocookie.com/embed/iWW7Ja5p0hA[title="Placing a Block in a Region"]
//==== Additional resources
......
......@@ -45,8 +45,7 @@ place their content.
The available regions depend on the theme design. Only the Content region,
which contains the primary content, is required; others are optional. The
core Bartik theme provides the eighteen regions highlighted in the following
image.
core Bartik theme provides the regions highlighted in the following image.
// Bartik theme region preview at admin/structure/block/demo/bartik,
// after configuring the theme for the Farmers Market scenario.
......
......@@ -2,7 +2,8 @@
=== Installing a Module
[role="summary"]
How to install a core or contributed module, using the administrative interface or Drush.
How to install a core or contributed module, using the administrative interface
or Drush.
(((Module,enabling)))
(((Module,installing)))
......@@ -64,6 +65,11 @@ to clear the cache. See <<prevent-cache-clear>>.
// ==== Related concepts
==== Videos
// Video from Drupalize.Me.
video::https://www.youtube-nocookie.com/embed/HymQsDOcT3E[title="Installing a Module"]
==== Additional resources
http://www.drush.org[Drush]
......
......@@ -92,6 +92,11 @@ only after comment fields have been removed, which is a side effect of
//==== Related concepts
==== Videos
// Video from Drupalize.Me.
video::https://www.youtube-nocookie.com/embed/hUonnNkeF6g[title="Uninstalling Unused Modules"]
//==== Additional resources
......
......@@ -27,7 +27,7 @@ to user accounts.
. In the _Manage_ administrative menu, navigate to _Configuration_ > _People_ >
_Account settings_ (_admin/config/people/accounts_).
. Under _Registration and Cancellation_, select _Administrators only_ as the
. Under _Registration and cancellation_, select _Administrators only_ as the
people with permissions to register user accounts. You can check _Require email
verification when a visitor creates an account_ in case you want to change the
settings for account registration later on.
......@@ -48,14 +48,14 @@ useful for a staff member(s) communicating with vendors.
image:images/config-user_from_email.png["Notification email from address"]
--
. Optionally, edit the email templates in the _Emails_ section to customize
automated emails. There are seven email templates available with the core. They
are meant for different user-specific occasions. All of them can be personalized
and three can be disabled via checkboxes: activation, blocking, and
cancellation.
. Optionally, edit the email templates under _Emails_ to customize
automated emails. There are several email templates provided by the core
software. They are meant for different user-specific occasions. All of them can
be personalized and three can be disabled via checkboxes: activation, blocking,
and cancellation.
+
You can send out your own text (for example, welcoming the new vendors for whom
accounts were just created) by editing the the _Welcome (new user created by
accounts were just created) by editing the _Welcome (new user created by
administrator)_ template.
+
--
......@@ -74,6 +74,11 @@ image:images/config-user_email.png["Email notification on account events",width=
See <<user-chapter>> for more information about user accounts and permissions.
==== Videos
// Video from Drupalize.Me.
video::https://www.youtube-nocookie.com/embed/POhQTAX93R8[title="Configuring User Account Settings"]
==== Additional resources
https://www.drupal.org/security/secure-configuration[Security Guide] can help
......
......@@ -45,7 +45,8 @@ farmers market!
Open: Sundays, 9 AM to 2 PM, April to September
Location: Parking lot of Trust Bank, 1st & Union, downtown
|URL path settings > URL alias| Alternate relative path for the content | /home
|Published | Whether the content is published for public view or not | Checked
|URL alias > URL alias| Alternate relative path for the content | /home
|================================
+
By clicking the _Source_ button in the rich text editor toolbar, you can see the
......@@ -60,7 +61,7 @@ image:images/content-create-create-basic-page.png["Create a basic page",width="1
. Click _Back to content editing_.
. Click _Save and publish_. The content is saved and can be found on the
. Click _Save_. The content is saved and can be found on the
_Content_ page.
. Follow the same steps to create an About page, with title "About", and a body
......@@ -78,6 +79,11 @@ telling about the history of the farmer's market.
* <<content-paths>>
* <<content-edit>>
==== Videos
// Video from Drupalize.Me.
video::https://www.youtube-nocookie.com/embed/h312fekiSNE[title="Creating a Content Item"]
==== Additional resources
https://www.drupal.org/docs/8/core/modules/node/about-nodes[_Drupal.org_ community documentation page "About nodes"]
......
......@@ -26,7 +26,7 @@ A content item for the Home page must exist. See <<content-create>>.
. If the content item you want to edit was updated or created recently, it
should appear near the top of the content list on that page. If not, you can
use the _Type_, _Title_, or other filters to locate the content item.
use the _Content type_, _Title_, or other filters to locate the content item.
+
--
// Content list on admin/content, with filters above.
......@@ -37,7 +37,7 @@ image:images/content-edit-admin-content.png["Content administration page",width=
open the content editing form. Update the opening hours in the _Body_ field. See
<<content-create>> for an explanation of the fields and a screenshot.
. Check _Create new revision_ in the box on the right, if it is not already
. Check _Create new revision_ under _Published_, if it is not already
checked, and enter a _Revision log message_ explaining what changes you are
making (for example, you might enter "Updated opening hours"). This text
will appear in the revision log for the page.
......@@ -47,7 +47,7 @@ will appear in the revision log for the page.
image:images/content-edit-revision.png["Revision information section of the content edit page"]
--
. Click _Save and keep published_ to save your changes.
. Click _Save_ to save your changes.
. You will be redirected back to the _Content_ administrative page, and there
should be a message showing that the content item was updated.
......@@ -74,6 +74,11 @@ from this page.
//==== Related concepts
==== Videos
// Video from Drupalize.Me.
video::https://www.youtube-nocookie.com/embed/TAFZMcuOqG0[title="Editing a Content Item"]
//==== Additional resources
......
......@@ -51,7 +51,7 @@ will see each editable field on this content item outlined in blue; also,
a hovering dialog box will appear.
+
--
// Screen shot of About page with Quick Edit turned on for the node.
// Screenshot of About page with Quick Edit turned on for the node.
image:images/content-in-place-edit-hover-box.png["Quick edit mode",width="100%"]
--
......@@ -79,6 +79,11 @@ the quick editor.
// ==== Related concepts
==== Videos
// Video from Drupalize.Me.
video::https://www.youtube-nocookie.com/embed/6A6kbceIKKw[title="Editing with the In-Place Editor"]
// ==== Additional resources
......
......@@ -3,7 +3,8 @@
=== Synchronizing Configuration Versions
[role="summary"]
How to synchronize the configuration between a development and live site using the core Configuration Manager module.
How to synchronize the configuration between a development and live site using
the core Configuration Manager module.
(((Configuration,synchronizing between development and live site)))
(((Development site,synchronizing with live site)))
......@@ -76,10 +77,15 @@ the change between sites. See <<extend-deploy>>.
* After the step where you export the full configuration from the source site,
you might also want to unpack the archive and commit it to a version control
system, such as Git, to track changes in your site configuration. See
<<install-tools>>.
<<extend-git>>.
// ==== Related concepts
==== Videos
// Video from Drupalize.Me.
video::https://www.youtube-nocookie.com/embed/dLUGQk8GKa0[title="Synchronizing Configuration Versions"]
// ==== Additional resources
......
......@@ -58,7 +58,7 @@ image:images/extend-deploy-export-single.png["Export a single item"]
. Open the production site.
. In the _Manage_ administrative menu, navigate to _Configuration_ >
_Development_ > _Configuration synchronization_ _Import_ > _Single_
_Development_ > _Configuration synchronization_ > _Import_ > _Single item_
(_admin/config/development/configuration_). The _Import_ page appears.
. Select _View_ from the _Configuration type_ list.
......@@ -69,7 +69,7 @@ _Development_ > _Configuration synchronization_ _Import_ > _Single_
. Click _Confirm_.
. Verify that the new view is being created by navigating in the _Manage_
. Verify that the view was imported by navigating in the _Manage_
administrative menu to _Structure_ > _Views_.
==== Expand your understanding
......@@ -102,6 +102,11 @@ need to clear the cache. See <<prevent-cache-clear>>.
* <<install-dev-sites>>
* <<planning-workflow>>
==== Videos
// Video from Drupalize.Me.
video::https://www.youtube-nocookie.com/embed/hysqVDIfLTA[title="Deploying New Site Features"]
// ==== Additional resources
......
[[extend-git]]
=== Managing File and Configuration Revisions with Git
[role="summary"]
How to manage file and configuration revisions with the Git revision control
tool.
(((Tool,Git)))
(((Git tool,using)))
==== Goal
Use the Git revision control tool to manage revisions to files and configuration
on your site.
==== Prerequisite knowledge
* <<install-tools>>
* <<install-decide>>
* <<install-dev-sites>>
* How to set up a Git repository and find its _clone_ URL. For example, if
you want to use GitLab to host your repository, see
https://docs.gitlab.com/ee/gitlab-basics/create-project.html[GitLab "Create a project" page]
and
https://docs.gitlab.com/ee/gitlab-basics/command-line-commands.html[GitLab "Command Line basic commands" page].
And if you want to use GitHub to host your repository, see
https://help.github.com/en/articles/create-a-repo[GitHub "Create a repo" page]
and
https://help.github.com/en/articles/which-remote-url-should-i-use[GitHub "Which remote URL should I use" page].
* How to open and use a command terminal window and a plain-text editor.
* To manage configuration, how to unpack and pack archive files (such as _.zip_
and _.tar.gz_).
==== Site prerequisites
* You must have downloaded the software for your site, using one of the methods
in <<install-decide>>. If you want to manage configuration, you must have
installed the software and have a running site.
* Git client software must be installed on your site's server. See
https://git-scm.com/[Git] for instructions.
* You must have a new repository created and know its Git clone URL.
==== Steps
===== Initializing the repository
Do these steps once, after creating a Git repository, to connect your local
directory to the repository and add the initial files to it.
. Open a command terminal window, and change to the directory where your site's
files are located. This is your "top" directory.
. Determine where your web root is. If the _core_, _modules_, and _themes_
directories are located directly in this directory, then you are in your web
root. If you have used Composer to download the software, then these files are
located inside the _web_ subdirectory (which is your web root).
. In a plain text editor, create a new file called _.gitignore_ in the top
directory (or edit it if it already exists). This file contains a list of files
and directories that Git should ignore (not add to the repository). For example,
the _settings.php_ file for your site should not be added to Git, because it
contains your database account information, and the media files uploaded to
your site (usually in _sites/default/files_) should not be in Git either -- the
objective is to have the software in the repository, not the site content.
. Make sure the following lines are in the _.gitignore_ file. If your web root
is not your top directory, check each of these to see if they need a prefix. For
example, _sites_ may need to be replaced with _web/sites_.
+
----
sites/*/settings*.php
sites/*/files
config
----
. Enter the following commands:
+
----
git init
git add -A
----
. Optionally, verify the list of files you will be adding to your Git repository
by entering this command and scrolling through the (very long) list:
+
----
git status
----
. Enter the following commands. You can substitute your own _commit message_ for
"Initial file add" if you wish, and you will need to substitute your own Git
clone URL for the URL in the second command:
+
----
git commit -m "Initial file add"
git remote add origin https://gitlab.com/example-name/example-repo.git
git push -u origin master
----
. If you are using GitLab, GitHub, or another host with online access, you can
now go to your repository page and see that the files are there.
===== Updating files in the repository
Use these steps when you have updated, added, or deleted one or more files in
your site, in order to send the changes (_push_) to your repository.
. Open a command terminal window, and change to the directory where your site's
files are located.
. Check the list of files that have been added, changed, or deleted:
+
----
git status
----
. Optionally, for text files that have been changed (not images), look at the
differences between the new and old versions of the file:
+
----
git diff path/to/file.txt
----
. Stage all the changes for the next commit, and verify that they are staged:
+
----
git add -A
git status
----
. You can omit a particular file from the commit that you have already staged,
or add another file to the ones you have already staged. If a particular file
or directory keeps getting added by mistake, consider adding it to the
_.gitignore_ file so that it will be ignored by Git. Omit/add commands:
+
----
git reset HEAD path/to/file.txt
git add path/to/file.txt
----
. Commit and push your changes. Substitute something meaningful for the commit
message:
+
----
git commit -m "commit message here"
git push
----
. If you have other copies of your repository, update them by opening a command
window in the directory of each copy and running the following command:
+
----
git pull
----
===== Making a copy of the files in your repository
Follow these steps if you want to copy all the files in your repository to a
new location. For example, you might have both a local development copy of your
site and a production site, or several team members might all have local
copies of the site.
. Open a command window in the location where you want the files to be.
. Enter the following command, substituting your repository clone URL for the
URL, and the name of the subdirectory you want them in for _dirname_:
+
----
git clone https://gitlab.com/example-name/example-repo.git dirname
----
===== Managing configuration in the repository
. Follow the instructions on <<extend-config-versions>> to export a complete
archive of your site's configuration.
. If you have not already initialized configuration in the repository, unpack
the configuration archive into a new directory, preferably above the web root
directory, and follow the instructions above to add these files to your
repository.
. After initializing, whenever your site configuration changes, export and
unpack the configuration archive in the same location. Follow the instructions
above to update these files in your repository.
. To import updated configuration to another site, make an archive of the
configuration directory from your repository. Then follow the instructions on
<<extend-config-versions>> to upload and import this archive into the site.
// ==== Expand your understanding
==== Related concepts
<<install-dev-sites>>
// ==== Videos
// ==== Additional resources
*Attributions*
Adapted and edited by https://www.drupal.org/u/jhodgdon[Jennifer Hodgdon] from
https://www.drupal.org/node/803746["Building a Drupal site with Git"],
copyright 2000-2019 by the individual contributors to the
https://www.drupal.org/documentation[Drupal Community Documentation].
......@@ -3,7 +3,8 @@
=== Enabling and Disabling Maintenance Mode
[role="summary"]
How to enable maintenance mode to set up a "Site under maintenance" message, and how to disable it.
How to enable maintenance mode to set up a "Site under maintenance" message, and
how to disable it.
(((Maintenance mode,overview)))
(((Maintenance mode,enabling)))
......@@ -19,10 +20,17 @@ that the site is under maintenance.
<<security-concept>>
// ==== Site prerequisites
==== Site prerequisites
If you want to use Drush to enable or disable maintenance mode, Drush must be
installed. See <<install-tools>>.
==== Steps
===== Enabling maintenance mode
You can use the administrative interface or Drush to enable or disable
maintenance mode.
===== Enabling maintenance mode using the administrative interface
. In the _Manage_ administrative menu, navigate to _Configuration_ >
_Development_ > _Maintenance mode_ (_admin/config/development/maintenance_). The
......@@ -55,7 +63,7 @@ the cache. See <<prevent-cache-clear>>.
image:images/extend-maintenance-mode-enabled.png["Maintenance mode enabled",width="100%"]
--
===== Disabling maintenance mode
===== Disabling maintenance mode using the administrative interface
. In the _Manage_ administrative menu, navigate to _Configuration_ >
_Development_ > _Maintenance mode_ (_admin/config/development/maintenance_). The
......@@ -85,6 +93,31 @@ clearing the cache. See <<prevent-cache-clear>>.
image:images/extend-maintenance-mode-disabled.png["Maintenance mode disabled",width="100%"]
--
===== Enabling or disabling maintenance mode using Drush
. Follow the user interface steps above to edit the site maintenance message, if
desired.
. Run the following Drush commands to enable maintenance mode and clear the
cache:
+
----
drush sset system.maintenance_mode 1
drush cr
----
. Run the following Drush commands to disable maintenance mode and clear the
cache:
+
----
drush sset system.maintenance_mode 0
drush cr
----
. After running either set of commands, verify that your site is either in or
out of maintenance mode by visiting the site in a browser where you are not
logged in.
==== Expand your understanding
* <<security-update-core>>
......@@ -95,11 +128,17 @@ image:images/extend-maintenance-mode-disabled.png["Maintenance mode disabled",wi
//==== Related concepts
==== Videos
// Video from Drupalize.Me.
video::https://www.youtube-nocookie.com/embed/IQbqQs5h03Q[title="Enabling and Disabling Maintenance Mode"]
// ==== Additional resources
*Attributions*
Written and edited by https://www.drupal.org/u/batigolix[Boris Doesborg],
and https://www.drupal.org/u/jojyja[Jojy Alphonso] at
http://redcrackle.com[Red Crackle].
https://www.drupal.org/u/jojyja[Jojy Alphonso] at
http://redcrackle.com[Red Crackle], and
https://www.drupal.org/u/jhodgdon[Jennifer Hodgdon].
......@@ -40,7 +40,9 @@ described in this topic:
<<extend-module-install>>, <<extend-theme-install>>,
<<security-update-module>>, or <<security-update-theme>>
Skip this topic if none of the above applies to you.
Skip this topic if none of the above applies to you. If you are using Composer
to manage the files in your site, follow the file updating steps in
<<install-composer>> instead of this topic.
==== Steps