new landing page wording

Author: jekuer

.vitepress/config.ts

@@ -261,7 +261,7 @@ export default {
           { text: 'Styles', link: '/api/styles' },
           { text: 'RSVP Templates', link: '/api/rsvp' },
           { text: "CTA Templates", link: '/api/cta' },
-          { text: "Landingpage Templates", link: '/api/landingpages' },
+          { text: "Landing Page Templates", link: '/api/landingpages' },
           { text: 'Webhooks', link: '/api/webhooks' },
           { text: 'Miscellaneous', link: '/api/miscellaneous' },
         ]

src/api/events.md

@@ -144,7 +144,7 @@ Additionally, the API does not allow to set the status of an event - it will alw
   "recurrence_count": 10, // example: repeat 10 times
   "recurrence_weekstart": "MO", // example for Monday
   "layout": "id-of-a-style-template", // take the id from the url in the application or the response when creating one via API
-  "landingpage": "id-of-a-landingpage-template", // take the id from the url in the application or the response when creating one via API
+  "landingpage": "id-of-a-landing-page-template", // take the id from the url in the application or the response when creating one via API
   "iCalFileName": "overriding the ics file name",
   "rsvp": true,
   "rsvp_block": "id-of-an-rsvp-block", // take the id from the url in the application or the response when creating one via API
@@ -167,7 +167,7 @@ Additionally, the API does not allow to set the status of an event - it will alw
 
 You can use the ProKey for further processing and several additional measures:
 
-* We automatically set up a landingpage you can use. Its url would be `https://caldn.net/:prokey`.
+* We automatically set up a landing page you can use. Its url would be `https://caldn.net/:prokey`.
 * In most cases, we auto-create an ics file for you. You can download it from `https://event.caldn.net/:prokey/event.ics`. Mind the specialties here:
   * We are not able to generate a file, if you are using dynamic dates like "today+4" (you can still use the link option for "ical" below);
   * We are not able to generate a file for RSVP forms - here, we generate them dynamically for each attendee and send personalized ones within the confirmation emails;

src/api/groups.md

@@ -79,7 +79,7 @@ Mind that you cannot add events on group creation. **You can only link events to
   "subscription": "no", // can be "no" or "external" - the latter one requires a subscription_cal_url
   "subscription_cal_url": null, // url to an external calendar. Needs to start with "http"! Usually ends with ".ics"
   "layout": "id-of-a-style-template", // take the id from the url in the application or the response when creating one via API
-  "landingpage": "id-of-a-landingpage-template", // take the id from the url in the application or the response when creating one via API
+  "landingpage": "id-of-a-landing-page-template", // take the id from the url in the application or the response when creating one via API
   "cta": true,
   "cta_block": "id-of-a-cta-block" // take the id from the url in the application or the response when creating one via API
 }

src/api/landingpages.md

@@ -1,33 +1,33 @@
 
-# Landingpage Template API
+# Landing Page Template API
 
 ::: info Mind the difference!
-This is about the Landingpage template.
+This is about the landing page template.
 
-A functional Landingpage consists of 2 base elements. Such a template block, holding the data about the structure and style of the page, as well as an [event](/api/events.html) or [subscription group](/api/groups.html), which defines the underlying date(s).
+A functional landing page consists of 2 base elements. Such a template block, holding the data about the structure and style of the page, as well as an [event](/api/events.html) or [subscription group](/api/groups.html), which defines the underlying date(s).
 :::
 
-## Get all/latest Landingpage templates
+## Get all/latest landing page templates
 
 ```
 GET /landingpage/all
 ```
 
-Gets a list with the ids of all available landingpage templates.
+Gets a list with the ids of all available landing page templates.
 
 ```
 GET /landingpage/latest
 ```
 
-Gets the latest landingpage template.
+Gets the latest landing page template.
 
-## Get one Landingpage template
+## Get one landing page template
 
 ```
 GET /landingpage/:id
 ```
 
-Reading a specific landingpage template does not allow for any additional parameters. It only takes the id in the request url and simply provides you with all data for this one.
+Reading a specific landing page template does not allow for any additional parameters. It only takes the id in the request url and simply provides you with all data for this one.
 
 ### Potential response
 
@@ -57,13 +57,13 @@ Reading a specific landingpage template does not allow for any additional parame
 
 <br />
 
-## Add a Landingpage template
+## Add a landing page template
 
 ```
 POST /landingpage
 ```
 
-Creating a new landingpage template requires you to at least provide the "name" field in the body.
+Creating a new landing page template requires you to at least provide the "name" field in the body.
 
 ```json
 {
@@ -111,17 +111,17 @@ The id from a successful creation can be used for further processing, like using
 
 <br />
 
-## Update a Landingpage template
+## Update a landing page template
 
 ```
 PATCH /landingpage/:id
 ```
 
-Updating a landingpage template follows the same rules as creating one.
+Updating a landing page template follows the same rules as creating one.
 
 <br />
 
-## Delete a Landingpage template
+## Delete a landing page template
 
 ```
 DELETE /landingpage/:id
@@ -132,5 +132,5 @@ Deleting a landinpgage template is simple. Only provide the prokey and it gets r
 **Be careful with this call!**
 
 ::: warning This does not delete events or groups!
-They remain active, but will then use the generic default landingpage template instead.
+They remain active, but will then use the generic default landing page template instead.
 :::

src/application-manual/analytics.md

@@ -7,7 +7,7 @@ outline: [2,3]
 For regular events, we track when users save them to their calendars.
 
 ::: warning To be more precise...
-We track the initiation of the save process via clicks at the landingpage, from email direct links, and from Add to Calendar Buttons with active Proxy option. The actual save can not be tracked, since it happens in the calendar app.
+We track the initiation of the save process via clicks at the landing page, from email direct links, and from Add to Calendar Buttons with active Proxy option. The actual save can not be tracked, since it happens in the calendar app.
 :::
 
 We also only do this for regular events, not for RSVP setups. In the RSVP case, we show the replies instead (enough tracking needed).

src/application-manual/elements.md

@@ -18,12 +18,12 @@ The hierarchy looks likes this:
       |  └─ Email template per RSVP email type *(optional)*
       ├─ CTA template *(optional)*
       ├─ Style *(optional)*
-      └─ Landingpage template *(optional)*
+      └─ Landing page template *(optional)*
 ```
 
 You will face this hierarchy during the creation of element. Still, within the app, they are organized a little different, in order to make them easily accessible - see the main navigation (Events - Styles - Templates).
 
-*Styles, CTA-, and Landingpage templates can be also related to a group, if the group is set up as subscription.*
+*Styles, CTA-, and landing page templates can be also related to a group, if the group is set up as subscription.*
 
 Webhooks, Team, and Settings are additional elements, which are described here as well.
 
@@ -61,7 +61,7 @@ All events you create, can be linked to an event with just one click. This makes
 *Bascially, "Styles" are also templates. We differentiate, because they play a more vital role, but that's all.*
 
 ::: info Mind that there are some exceptions.
-Landingpages and RSVP emails are also partly styled within the respective template blocks and not only by the *style*!
+Landing pages and RSVP emails are also partly styled within the respective template blocks and not only by the *style*!
 :::
 
 ## Templates
@@ -93,13 +93,13 @@ When setting them, you overwrite the default emails, that we send for any RSVP i
 
 You can also adjust the look of the email within the template.
 
-### Landingpages
+### Landing pages
 
-For every event, we automatically generate a nice responsive landingpage for it.
+For every event, we automatically generate a nice responsive landing page for it.
 
 This makes it easy to share your RSVP or event on social media and beyond.
 
-By creating a [landingpage template](/application-manual/styles-and-templates.html#landingpages), you can adjust the look as well as additional content of this landingpage.
+By creating a [landing page template](/application-manual/styles-and-templates.html#landingpages), you can adjust the look as well as additional content of this landing page.
 Link this template to the event/group and you are done.
 
 ## Webhooks

src/application-manual/groups-and-events.md

@@ -38,7 +38,7 @@ Once a group has events attached, you can no longer change this, since it change
 
 In the subscription case, you won't see this table, but the style and CTA inputs, which you already know from the creation.
 
-At the very top, you either only see the ProKey to copy (non-subscription case) or a complete summary with everything you need for sharing and integration purposes. From email links to your auto-created landingpage and more. Here, you also find the link to the **analytics** dashboard for this event group.
+At the very top, you either only see the ProKey to copy (non-subscription case) or a complete summary with everything you need for sharing and integration purposes. From email links to your auto-created landing page and more. Here, you also find the link to the **analytics** dashboard for this event group.
 
 ## The event
 
@@ -76,10 +76,10 @@ In all cases, you can always check the result at the dynamic preview.
 Once created, you can always update the event on the detail page.
 There, you basically find the same structure as on creation.
 
-At the very top, you find a complete summary with everything you need for sharing and integration purposes. From email links to your auto-created landingpage and more. Here, you also find the link to the [analytics](/application-manual/analytics.html) dashboard for this event. This would be the overview of RSVP sign-ups in the RSVP case or analytics about when and how often people saved an event to their calendars (in the non-RSVP case).
+At the very top, you find a complete summary with everything you need for sharing and integration purposes. From email links to your auto-created landing page and more. Here, you also find the link to the [analytics](/application-manual/analytics.html) dashboard for this event. This would be the overview of RSVP sign-ups in the RSVP case or analytics about when and how often people saved an event to their calendars (in the non-RSVP case).
 
 Also at the top, you have the option to set an event to private. 
-This will block the auto-generation of a landingpage and ics file, but will still allow you to generate ics files via API or use a button with [dynamic date properties in WordPress](/integration/wordpress.html#dynamic-connections).
+This will block the auto-generation of a landing page and ics file, but will still allow you to generate ics files via API or use a button with [dynamic date properties in WordPress](/integration/wordpress.html#dynamic-connections).
 
 ::: warning Mind Auto-Adjustments
 Depending on what you select as well as different cases on the user side, we automatically adjust some details. For example, when you create a recurring event, some calendar types will not show up, as not all do support this feature (in an Add to Calendar Button scope).

src/application-manual/styles-and-templates.md

@@ -9,9 +9,9 @@ While you can create them right during event creation, you can also do this at t
 
 As it might be obvious already, styles define the look and feel of your published elements. They, however, also account for usability and UX - like which calendar providers are available for an Add to Calendar Button.
 
-Templates exist for RSVP forms and emails, Call to Action (CTA) screens, as well as landingpages.
+Templates exist for RSVP forms and emails, Call to Action (CTA) screens, as well as landing pages.
 
-While RSVP forms, landingpage templates, CTA screens, and styles can be linked to events; emails can be linked to RSVP forms.
+While RSVP forms, landing page templates, CTA screens, and styles can be linked to events; emails can be linked to RSVP forms.
 
 ::: info Build your world!
 The Add to Calendar system is structured in way to offer you a maximum of flexibilty when it comes to you building your specific setup.
@@ -45,7 +45,7 @@ In case you are building an RSVP form, using an RSVP remplate is mandatory as it
 
 The same applies for Call to Action templates.
 
-Email and Landingpage templates, on the other hand, are rather optional. If you do not work with them, our default will be delivered. Using them gives you the power to customize all details of your user's journey.
+Email and landing page templates, on the other hand, are rather optional. If you do not work with them, our default will be delivered. Using them gives you the power to customize all details of your user's journey.
 
 [Open in the app ❯](https://app.add-to-calendar-pro.com/templates)
 
@@ -107,14 +107,14 @@ Test your email via the button on the very right side of the page! It sends an e
 Mind that here you can only define a custom FROM name and set your custom reply-to address.  
 To define the sender email address, you need to set this up globally at the settings page.
 
-### Landingpage
+### Landing page
 
-Landingpage templates are basically additional configurations for the auto-generated landingpages for your events.
+Landing page templates are basically additional configurations for the auto-generated landing pages for your events.
 
-Those landingpages can be used to share your event on social media or anywhere else. They also come into play, when you use our email links or proxy the Add to Calendar Button (required for analytics). In those cases, especially if something goes wrong (we do some pre-checks with the requested calendar provider), we show some guidance to the user - with the landingpage style.
-For the RSVP case, any communication, like DOI, the user editing his response, etc., uses this landingpage layout as well.
+Those landing pages can be used to share your event on social media or anywhere else. They also come into play, when you use our email links or proxy the Add to Calendar Button (required for analytics). In those cases, especially if something goes wrong (we do some pre-checks with the requested calendar provider), we show some guidance to the user - with the landing page style.
+For the RSVP case, any communication, like DOI, the user editing his response, etc., uses this landing page layout as well.
 
-As you see, there is a big chance, your users are getting in contact with your event's or RSVP's landingpage.
+As you see, there is a big chance, your users are getting in contact with your event's or RSVP's landing page.
 
 With a respective template, linkable to an event/group, you can customize this page.
 

src/application-manual/troubleshooting.md

@@ -28,7 +28,7 @@ The events we push:
 
 ## Tracking does not seem to work
 
-We track the initiation of the save process via clicks at the landingpage, from email direct links, and from Add to Calendar Buttons with active `Proxy` option. If the `Proxy` option is not set at the style, while you are using the Add to Calendar Button outside of the auto-generated landingpage, clicks cannot be tracked.
+We track the initiation of the save process via clicks at the landing page, from email direct links, and from Add to Calendar Buttons with active `Proxy` option. If the `Proxy` option is not set at the style, while you are using the Add to Calendar Button outside of the auto-generated landing page, clicks cannot be tracked.
 
 Another case would be when you share the generated ics file directly - we cannot track this either.
 
@@ -48,7 +48,7 @@ This is basically necessary for things like email links or even the Add to Calen
 
 If you do not want this to happen - because, for example, you put sensitive information into the event details - you can set an event (or group) to private. Click the flap on the top of the big box at the beginning of the details page.
 
-A private event has no public ics file or landingpage. The Add to Calendar Button will also not work as it requires to pull the information via the web. However, you can still [generate ics files via our API](/api/miscellaneous.html#retrieve-ics-file-body). 
+A private event has no public ics file or landing page. The Add to Calendar Button will also not work as it requires to pull the information via the web. However, you can still [generate ics files via our API](/api/miscellaneous.html#retrieve-ics-file-body). 
 
 This makes it an ideal case for [dynamic checkout flows](/recipes/dynamic-checkout.html) with sensitive information!
 
@@ -66,7 +66,7 @@ To achieve this, you would need to duplicate your event and connect the 2 events
 
 ## Social preview image not updating
 
-When sharing a link to the landingpage, we automatically generate a preview image, which displays the event details. This helps to spread the word more prominently.
+When sharing a link to the landing page, we automatically generate a preview image, which displays the event details. This helps to spread the word more prominently.
 
 At each update, this image gets updated as well. However, external tools and websites usually cache this image, which makes it not updating immediately. Some refresh there cache only after 7 days, if at all.