fix targets xd2

content/admin/Administration Panel/Email.adoc

@@ -15,7 +15,7 @@ weight: 40
 Configuring email for *SuiteCRM* provides a wide range of features, including sending personal emails to 
 contacts, automatic creation of cases, sending notifications for events using 
 link:../../../user/advanced-modules/workflow/[workflows] and sending email marketing 
-link:../../../usercampaigns/[campaigns]. 
+link:../../../../user/core-modules/usercampaigns/[campaigns]. 
 
 This document explains the different types of mail accounts and how to set them up. For information 
 on reading and sending email in SuiteCRM using the Emails module, see the 
@@ -65,7 +65,7 @@ Set up a group account from the <<Inbound Email>> page.
 
 *Bounce Handling Accounts*
 
-A Bounce Handling account is used with link:../../core-modules/campaigns/[Campaigns] to handle bounced 
+A Bounce Handling account is used with link:../../../user/core-modules/campaigns/[Campaigns] to handle bounced 
 mail notifications when emails are undelivered. You will need to set up a Bounce Handling account in 
 order to send a Campaign.
 
@@ -186,15 +186,15 @@ all incoming emails. These associated emails can then be viewed via the History
 This setting is selected by default in *SuiteCRM*.
 
 ==== Create Case From Email
-Check this box to set up *SuiteCRM* to create a link:../../core-modules/cases[Case] record from an incoming email. 
+Check this box to set up *SuiteCRM* to create a link:../../../user/core-modules/cases[Case] record from an incoming email. 
 
 image:EmailsCreateCase2.png[Create Case]
 
 Select a *Distribution Method* to specify how cases created from incoming email are assigned to users.
 
 [cols="20,80"]
 |===
-|*Use AOP default*|This will use the link:../../../user/advanced-modules/advanced-open-cases-with-portal[AOP default settings], 
+|*Use AOP default*|This will use the link:../../../../user/advanced-modules/advanced-open-cases-with-portal[AOP default settings], 
 configurable via the Admin panel. 
 |*Single User*| Enter a username or click the select arrow to search for a user. 
 Every automatically created case will be assigned to the specified user. image:EmailsCreateCaseSingleUser.png[Single User]

content/admin/Administration Panel/System.adoc

@@ -60,7 +60,7 @@ for invitees when scheduling calls and meetings.
 
 === Logger Settings
 Specify log filename, extension and size as well as the log level here.
-See the link:../developer/logging/[chapter on logging] for more information.
+See the link: ./../../../developer/logging/[chapter on logging] for more information.
 
 Click the View Log link to view the log file.
 

content/blog/ListView-conditional-formatting.adoc

@@ -18,7 +18,7 @@ In this post we’ll be adding a simple coloured border to the
 ''Industry'' field in the Accounts list view. We’ll end up with
 something similar to this:
 
-:imagesdir: ./../../../images/en/community
+:imagesdir: ./../../images/en/community
 
 image:02IndustryColours.png[Coloured fields on the list view]
 

content/blog/creating-an-alert.adoc

@@ -7,7 +7,7 @@ source: http://www.jsmackin.co.uk/suitecrm/suitecrm-creating-an-alert/
 hidden: true
 ---
 
-:imagesdir: ./../../../images/en/community
+:imagesdir: ./../../images/en/community
 
 Alerts in the menu bar are an excellent way of calling user's attention. 
 What if you what to create a custom alert through code? It's easy, here's how to do it.

content/blog/creating-custom-field-types.adoc

@@ -46,7 +46,7 @@ $mod_strings['fieldTypes']['ColourPicker'] = 'Colour Picker';
 After a quick repair and rebuild this gives us the option to create a
 field with type ``Colour Picker'':
 
-:imagesdir: ./../../../images/en/community
+:imagesdir: ./../../images/en/community
 
 image:03ColourPickerStudio.png[ColourPickerStudio]
 

content/blog/suitecrm-super-logger.adoc

@@ -8,7 +8,7 @@ hidden: true
 ---
 
 I’ve previously created a very simple module for SuiteCRM which adds coloured
-logging link:./../../../files/suitesuperlogger.zip[(SuiteCRM Super Logger)].
+logging link:/files/suitesuperlogger.zip[(SuiteCRM Super Logger)].
 I’ve now expanded it somewhat to add extra features.
 
 It’s now called *SuiteSuperLogger* and allows specifying the log format in the

content/developer/API/version-8/Managing Tokens.adoc

@@ -3,7 +3,7 @@ title: Managing Tokens
 weight: 5
 ---
 
-:imagesdir: ./../../../../../images/en/developer
+:imagesdir: ./../../../../images/en/developer
 
 
 The OAuth 2 admin panel displays which session have been successfully

content/developer/Introduction.es.adoc

@@ -73,7 +73,7 @@ o consultados a fin de mejorar la performance,
 tales como las plantillas (templates) de Smarty. El modo desarrollador desactiva algunos de
 esos procesos de caching, de manera que los cambios en los archivos modificados
 se vean de forma inmediata (salvando algunas excepciones, tales como las del caso 
-de link:../extension-framework/[extensions]).
+de link:../../../developer/extension-framework/[extensions]).
 Esta opción puede ser activada tanto desde la edición del archivo de configuración como desde la página
 General settings (ajustes generales) dentro del administrador.
 
@@ -83,7 +83,7 @@ General settings (ajustes generales) dentro del administrador.
 El nivel por defecto de log de errores de SuiteCRM es `fatal`. Éste es un buen nivel de log para instancias de producción,
 pero quizás en entorno de desarrollo usted desee mantener el nivel del log en `info` o `debug`, de manera que la salida del
 log sea más verboso en caso de que algo salga mal y se pueda capturar la referencia al error.
-Para más información, puede dirigirse a link:../logging/[chapter on logging]
+Para más información, puede dirigirse a link:k:../../../developer/logging/[chapter on logging]
 
 [discrete]
 ==== Display errors (Muestra de mensajes de error)

content/developer/Scheduled Tasks.adoc

@@ -3,7 +3,7 @@ weight: 13
 title: "Scheduled Tasks"
 ---
 
-:imagesdir: ./../images/en/developer
+:imagesdir: ./../../images/en/developer
 
 = 13. Scheduled Tasks
 

themes/hugo-theme-learn/layouts/404.html

@@ -49,7 +49,7 @@ <h1>{{T "title-404"}}</h1>
           <p>{{T "message-404"}}</p>
           <p></p>
           <p><a href="{{.Site.BaseURL}}">{{T "Go-to-homepage"}}</a></p>
-          <p><img src="{{ .Site.BaseURL }}/images/gopher-404.jpg" style="width:50%"></img></p>
+          <p><img src="{{ .Site.BaseURL }}/images/gopher-404.jpg" style="width:50%" alt="Page not found."></img></p>
         </div>
       </div>