new window for external links

Author: espen

_endpoints/bookings.md

@@ -191,7 +191,7 @@ To add a new person along with a booking you must populate `person_attributes` w
 
 `POST /bookings/recurring` will create recurring bookings based on a pattern.
 
-The recurrence format follows the [iCalendar specification](https://tools.ietf.org/html/rfc5545). The attributes for recurrence are: `RRULE`, `RDATE`, `EXDATE`. For an introduction and examples of these parameters see [this section from the iCalendar specification](http://www.kanzaki.com/docs/ical/rrule.html).
+The recurrence format follows the [iCalendar specification](https://tools.ietf.org/html/rfc5545){:target="_blank"}. The attributes for recurrence are: `RRULE`, `RDATE`, `EXDATE`. For an introduction and examples of these parameters see [this section from the iCalendar specification](http://www.kanzaki.com/docs/ical/rrule.html){:target="_blank"}.
 
 In the iCalendar specification the recurrence is based on values in `DTSTART` and `DTEND`. This is set by `booked_from` and `booked_to` from `booking`.
 

_endpoints/events.md

@@ -74,7 +74,7 @@ Response
 
 `POST /events/recurring` will create a multiple events.
 
-The recurrence format follows the [iCalendar specification](https://tools.ietf.org/html/rfc5545). The attributes for recurrence are: `RRULE`, `RDATE`, `EXDATE`. For an introduction and examples of these parameters see [this section from the iCalendar specification](http://www.kanzaki.com/docs/ical/rrule.html).
+The recurrence format follows the [iCalendar specification](https://tools.ietf.org/html/rfc5545){:target="_blank"}. The attributes for recurrence are: `RRULE`, `RDATE`, `EXDATE`. For an introduction and examples of these parameters see [this section from the iCalendar specification](http://www.kanzaki.com/docs/ical/rrule.html){:target="_blank"}.
 
 In the iCalendar specification the recurrence is based on values in `DTSTART` and `DTEND`. This is set by `starts_at` and `ends_at` from `event`.
 

_guides/api-libraries.md

@@ -5,8 +5,8 @@ nav_order: 12
 
 Makeplans does not officially support API libraries but they might be useful for you. Please note that these projects are **not** made by Makeplans but made publicly available by other developers who have used the Makeplans API. Any questions should be made directly to the responsible developers. If you find any errors or areas of improvement please make a pull request to improve the project.
 
-* [NodeJS by Mable](https://github.com/mableteam/makeplans).
-* [CakePHP by Pollenizer](https://github.com/Pollenizer/CakePHP-Makeplans-Plugin).
-* [Go by drewwells](https://github.com/drewwells/makeplans).
+* [NodeJS by Mable](https://github.com/mableteam/makeplans){:target="_blank"}.
+* [CakePHP by Pollenizer](https://github.com/Pollenizer/CakePHP-Makeplans-Plugin){:target="_blank"}.
+* [Go by drewwells](https://github.com/drewwells/makeplans){:target="_blank"}.
 
 A big thanks to everyone who has contributed to these libraries!

_guides/getting-started.md

@@ -5,13 +5,13 @@ nav_order: 1
 
 1) Read this documentation.
 
-2) [Sign up for a trial account in our test environment](https://app.test.makeplans.net/client/new)
+2) [Sign up for a trial account in our test environment](https://app.test.makeplans.net/client/new){:target="_blank"}
 
 3) Go to Setup -> Integrations -> API. Enable the API and get the API-key.
 
 4) Profit.
 
-When your integration is ready to be released you can sign up for a [real account](https://app.makeplans.com/client/new).
+When your integration is ready to be released you can sign up for a [real account](https://app.makeplans.com/client/new){:target="_blank"}.
 
 Limitations of the test environment:
 * SMS reminders are not triggered.

_guides/pagination.md

@@ -5,7 +5,7 @@ nav_order: 10
 
 Maximum 50 items are returned per response for all endpoints except `bookings` which returns 750. Specify page with parameter `page`. Pagination is used for: bookings, events, people and resource exception dates. All other objects return all available items. Please note that currently there is no way to specify exact part of the dataset. Thus an item might appear in both page 2 and 3 if the complete dataset for the query has changed.
 
-[RFC 8288](https://datatracker.ietf.org/doc/html/rfc8288) is used for pagination linking. You will find URLs for first, prev, next and last pages in the `Link` HTTP Header. In addition metadata is added in the following HTTP Headers: `Current-Page`, `Page-Items`, `Total-Count`, `Total-Pages`.
+[RFC 8288](https://datatracker.ietf.org/doc/html/rfc8288){:target="_blank"} is used for pagination linking. You will find URLs for first, prev, next and last pages in the `Link` HTTP Header. In addition metadata is added in the following HTTP Headers: `Current-Page`, `Page-Items`, `Total-Count`, `Total-Pages`.
 
 ## Example request and response
 

partner.md

@@ -38,7 +38,7 @@ The initial user is set as admin on the account. The attributes for creation are
 
 ##### Time zone
 
-Currently a custom time zone naming is used. Please see [this list](https://github.com/rails/rails/blob/v7.1.3.4/activesupport/lib/active_support/values/time_zone.rb#L33) of used names and their mappings.
+Currently a custom time zone naming is used. Please see [this list](https://github.com/rails/rails/blob/v7.1.3.4/activesupport/lib/active_support/values/time_zone.rb#L33){:target="_blank"} of used names and their mappings.
 
 In the future this will become more standard compliant.