Differences

This shows you the differences between two versions of the page.

--- edit_landing_page [2018/01/25 15:44] – [Naming Convention] lucy
+++ edit_landing_page [2019/05/22 17:38] – lucy
@@ Line 8: / Line 8: @@
   * Any Scripts or Style sheets
-The editor can only save html code which is compliant with W3C standard. You can always check your code with this validation service: https://validator.w3.org/. Code which is not W3C conform will not be saved by LUCY.
+The editor can only save HTML code which is compliant with W3C standard. You can always check your code with this validation service: https://validator.w3.org/. Code which is not W3C conform will not be saved by LUCY.
 ===== How to select a page that needs to be edited =====
-The html pages can be edited either in the generic template section or within a campaign. If you change them in the generic template section the changes will remain for all campaigns that use that template in the future. Therefore it might be better to make the changes of a page within a campaign. This will change only the template within that specific campaign.
+The HTML pages can be edited either in the generic template section or within a campaign. If you change them in the generic template section the changes will remain for all campaigns that use that template in the future. Therefore it might be better to make the changes of a page within a campaign. This will change only the template within that specific campaign.
@@ Line 30: / Line 30: @@
 ===== Creating new pages =====
-You can create a new page by going to actions --> new. Then give your page a name and tell LUCY what type it is (this matters: if you select a "web based" type, then the WYSIWYG editor will be missing the Trojan simulation buttons. To be on the safe side we recommend using the mixed type).
+You can create a new page by going to actions --> new. Then give your page a name and tell LUCY what type it is (this matters: if you select a "web-based" type, then the WYSIWYG editor will be missing the Trojan simulation buttons. To be on the safe side we recommend using the mixed type).
 {{ new_page.png?600 }}
@@ Line 78: / Line 78: @@
 {{ filemanager.png?600 }}
-You can use the upload button to upload the files or simply drag and drop one or multiple file into the browser. Depending on the file type LUCY will automatically place the files in the correct directory (images are later stored in a central image repository).
+You can use the upload button to upload the files or simply drag and drop one or multiple files into the browser. Depending on the file type LUCY will automatically place the files in the correct directory (images are later stored in a central image repository).
 {{ upload_file_manager.png?600 }}
@@ Line 117: / Line 117: @@
 The system uses 2 predefined file names for all pages that simulate some sort of a login:
-  * **index.html** - The first page that the user sees after clicking on the link in the email message. Usually it contains a login form (but you can use it for any other form as well: LUCY simply checks if there is a form based POST request, independent from the from variable names). All other pages are forbidden until the user enters login details on this page. The login form should use a POST method and either point to the same page (have an empty action attribute) or have an action set to "?login" (<FORM action="?login" method="post">). If you want to validate logins and passwords using [[regular_expressions_in_login_fields|regular expressions]] ("Login Regexp" and "Password Regexp" fields in Scenario Settings), please set the name of the login field to "Login" and the name of the password field to "Password".
+  * **index.html** - The first page that the user sees after clicking on the link in the email message. Usually, it contains a login form (but you can use it for any other form as well: LUCY simply checks if there is a form-based POST request, independent from the from variable names). All other pages are forbidden until the user enters login details on this page. The login form should use a POST method and either point to the same page (have an empty action attribute) or have an action set to "?login" (<FORM action="?login" method="post">). If you want to validate logins and passwords using [[regular_expressions_in_login_fields|regular expressions]] ("Login Regexp" and "Password Regexp" fields in Scenario Settings), please set the name of the login field to "Login" and the name of the password field to "Password".
-  * **account.html** - The page that the user sees after entering valid login and password values (or any other forma based data). If you are missing the account.html page, you will see the [[not_found_pages_404|standard 404 error page]] in LUCY, which also can be customized. If you want to redirect the user directly to some other page than the account.html (e.g. the awareness site), please check out [[redirecting_users|this chapter]].
+  * **account.html** - The page that the user sees after entering valid login and password values (or any other form-based data submitted on the index page). Please note, that all submitted data on the index page is recorded in LUCY and [[monitor_a_campaign_statistics|visible in the statistics]]. If you are missing the account.html page, you will see the [[not_found_pages_404|standard 404 error page]] in LUCY, which also can be customized. If you want to redirect the user directly to some other page than the account.html (e.g. the awareness site), please check out [[redirecting_users|this chapter]].
-For other pages you can choose any other name. This applies to web based templates. On file based templates, LUCY does not expect a second page. Therefore, you only have 1 index page. If you still need multiple pages, you need to solve this with JavaScript. Please check out the template "Encrypted Mail (Download Only)" as an example for a file based template with multiple pages.
+For other pages, you can choose any other name. This applies to web-based templates. On file-based templates, LUCY does not expect a second page. Therefore, you only have 1 index page. If you still need multiple pages, you need to solve this with JavaScript. Please check out the template "Encrypted Mail (Download Only)" as an example for a file-based template with multiple pages.
 ===== Links in LUCY =====
-**Example 1 - Links on page within the "authenticated area".** If you create a index.html page where you ask the user to submit some form data to LUCY, LUCY will automatically assume the user is now "authenticated" and will write a cookie "auth=1". On the second page (e.g. account.html) you can place a link in the code similar to this one:
+**Example 1 - Links on page within the "authenticated area".** If you create an index.html page where you ask the user to submit some form data to LUCY, LUCY will automatically assume the user is now "authenticated" and will write a cookie "auth=1". On the second page (e.g. account.html) you can place a link in the code similar to this one:
   <a href="mypage.html">This is a link to "mypage"</a>
@@ Line 133: / Line 133: @@
 {{ justsometext2.png?600 }}
-**Example 2 - Links within the index.html page, without submitting any data**: If that cookie (auth=1) does not exist, LUCY will think no authentication has been done and therefore always redirect the user back to the index page. As a result links will not work yet. You can create the following code in order for this to work (make sure you append "%link%" to the page that you want to have linked):
+**Example 2 - Links within the index.html page, without submitting any data**: If that cookie (auth=1) does not exist, LUCY will think no authentication has been done and therefore always redirect the user back to the index page. As a result link will not work yet. You can create the following code in order for this to work (make sure you append "%link%" to the page that you want to have linked):
@@ Line 197: / Line 197: @@
 {{ layer_add.png?600 }}
-Now you need to link the image to the malware simulation. In case you use the standard malware simulations within the file template section you can click on the image, then on the link symbol in the editor and insert a link like this example: %static%/info.doc?track (for the file template "MACRO - POST ONLY"). The "?track" variable at the end of the link allows you to track the download of the file. In case you want to customize the malware simulation you first need to make a copy of the according file template (a), then click on the copied file template (b) and download the according word file (c).
+Now you need to link the image to the malware simulation. In case you use the standard malware simulations within the file template section you can click on the image, then on the link symbol in the editor and insert a link like this example: %static%/info.doc?track (for the file template "MACRO - POST ONLY"). The "?track" variable at the end of the link allows you to track the download of the file. In case you want to customize the malware simulation you first need to make a copy of the matching file template (a), then click on the copied file template (b) and download the according word file (c).
 {{ file_template_new.png?600 }}
@@ Line 211: / Line 211: @@
 {{ custom_f.png?600 }}
-Next go back to the landing page editor and select the image you uploaded (1). Now click on the button "link symbol" (2). Insert the link to the new malware simulation. In case the word file is called "my-doc.doc" the path must be "%static%/my_doc.doc?track" (3). Please press ok and then save the changes to your template.
+Next, go back to the landing page editor and select the image you uploaded (1). Now click on the button "link symbol" (2). Insert the link to the new malware simulation. In case the word file is called "my-doc.doc" the path must be "%static%/my_doc.doc?track" (3). Please press ok and then save the changes to your template.
 {{ link_image2.png?600 }}