From aeeb960566206ef9c35986d70bbd02a175b26b04 Mon Sep 17 00:00:00 2001 From: Sunny Side Up Date: Wed, 21 Feb 2024 20:50:47 +1300 Subject: [PATCH] DOC: fixing yml annotation --- docs/en/index.md | 42 ++++++++++++++++++++++-------------------- 1 file changed, 22 insertions(+), 20 deletions(-) diff --git a/docs/en/index.md b/docs/en/index.md index 5a4357d..a517d52 100644 --- a/docs/en/index.md +++ b/docs/en/index.md @@ -30,32 +30,34 @@ manually, including requesting to have the page excluded from the sitemap. Most module configuration is done via the Silverstripe CMS Config API. Create a new config file `mysite/_config/googlesitemaps.yml` with the following outline: - --- - Name: customgooglesitemaps - After: googlesitemaps - --- - Wilr\GoogleSitemaps\GoogleSitemap: - -enabled: true -objects_per_sitemap: 1000 -google_notification_enabled: false -use_show_in_search: true +```yml +--- +Name: customgooglesitemaps +After: googlesitemaps +--- +Wilr\GoogleSitemaps\GoogleSitemap: + enabled: true + objects_per_sitemap: 1000 + google_notification_enabled: false + use_show_in_search: true +``` You can now alter any of those properties to set your needs. A popular option is to turn on automatic pinging so that Google is notified of any updates to your page. You can set this in the file we created in the last paragraph by editing the `google_notification_enabled` option to true - --- - Name: customgooglesitemaps - After: googlesitemaps - --- - Wilr\GoogleSitemaps\GoogleSitemap: - -enabled: true -objects_per_sitemap: 1000 -google_notification_enabled: true -use_show_in_search: true +```yml +--- +Name: customgooglesitemaps +After: googlesitemaps +--- +Wilr\GoogleSitemaps\GoogleSitemap: + enabled: true + objects_per_sitemap: 1000 + google_notification_enabled: true + use_show_in_search: true +``` ### Including DataObjects