Merge pull request #674 from OpenFn/v3

V3

Author: taylordowns2000

adaptors/collections.md

@@ -24,7 +24,7 @@ Learn more about Collections and common use cases in the
 :::caution
 
 Collections must be created in the
-[Platform Admin page](https://docs.openfn.org/documentation/build/collections#managing-collections)
+[Platform Admin page](/documentation/build/collections#managing-collections)
 before they can be used.
 
 :::
@@ -60,17 +60,17 @@ fetch all keys which relate to Mr Benn in 2024).
 The Collections API gives you four functions to read, write and remove data from
 a collection.
 
-- Use [`collections.get()`](adaptors/packages/collections-docs#collections_get)
+- Use [`collections.get()`](/adaptors/packages/collections-docs#collections_get)
   to fetch a single value, or batch-download a range of values.
 - Use
-  [`collections.each()`](adaptors/packages/collections-docs#collections_each) to
+  [`collections.each()`](/adaptors/packages/collections-docs#collections_each) to
   efficiently iterate over a range of items in a collection. Recommended for
   large data sets.
-- Use [`collections.set()`](adaptors/packages/collections-docs#collections_set)
+- Use [`collections.set()`](/adaptors/packages/collections-docs#collections_set)
   to upload one or more values to a collection. `set()` is always an "upsert":
   if a key already exists, it's value will be replaced by the new value
 - Use
-  [`collections.remove()`](adaptors/packages/collections-docs#collections_remove)
+  [`collections.remove()`](/adaptors/packages/collections-docs#collections_remove)
   to remove one or more values.
 
 Detailed usage examples are provided below.
@@ -184,7 +184,7 @@ collections.get('my-collection', 'commcare-fhir-value-mappings').then(state => {
   state.mappings = state.data;
   return state;
 });
-collecions.each($.inputs, state => {
+collections.each($.inputs, state => {
   const mappedString = state.mappings[state.data.diagnosis];
   state.resources ??= {};
   state.resources[state.data.id] = mappedString;
@@ -238,7 +238,7 @@ collections.each(
 
 You can use `createdBefore` and `createdAfter` dates, which must be ISO 1806
 formatted strings. The `createdBefore` timestamp will match all dates less than
-or equal to (<=) the _start_ of the provided date. Conversely, `createdAfter`
+or equal to (&lt;=) the _start_ of the provided date. Conversely, `createdAfter`
 will match dates greater than or equal to the _end_ of the provided date.
 
 By default, all matching values will be returned to you, but you can limit how

adaptors/dynamics.md

@@ -16,7 +16,7 @@ title: Dynamics Adaptor
 
 See [Microsoft docs](https://learn.microsoft.com/en-us/azure/active-directory/) for the latest on supported authentication methods. When integrating with Dynamics via OpenFn, **Access Token** is supported. See this adaptor's [Configuration docs](/adaptors/packages/dynamics-configuration-schema) for more on the required authentication parameters.
 
-See platform docs on [managing credentials](documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
+See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
 
 ```
 {

adaptors/googlehealthcare.md

@@ -17,7 +17,7 @@ The [Google Cloud Healthcare API](https://cloud.google.com/healthcare-api) is a
 1. See [Google Cloud Healthcare API docs](https://cloud.google.com/healthcare-api/docs/authentication#:~:text=You%20can%20authenticate%20to%20the,CLI%20credentials%20and%20ADC%20credentials.) for the latest on supported authentication methods.
 2. When integrating with Google Cloud Healthcare via OpenFn, there is one primary authentication method that is supported: **Access Token**. See this adaptor's [Configuration docs](/adaptors/packages/googlehealthcare-configuration-schema) for more on the required authentication parameters.
 
-See platform docs on [managing credentials](documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
+See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
 
 ```
 {

adaptors/hubtel.md

@@ -19,7 +19,7 @@ Hubtel supports two primary integration options with OpenFn:
 2. When integrating with Hubtel via OpenFn, authentication via **API Key** is supported.
 3. See this adaptor's [Configuration docs](/adaptors/packages/hubtel-configuration-schema) for more on the required authentication parameters.
 
-See platform docs on [managing credentials](documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
+See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
 
 ```
 {

adaptors/mailchimp.md

@@ -18,7 +18,7 @@ Mailchimp supports two primary integration options:
 
 When integrating with Mailchimp via OpenFn, authentication via **API Key** is supported ([see MC docs](https://mailchimp.com/developer/marketing/docs/fundamentals/#connecting-to-the-api). See this adaptor's [Configuration docs](/adaptors/packages/mailchimp-configuration-schema) for more on the required authentication parameters.
 
-See platform docs on [managing credentials](documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
+See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
 
 ```
 {

adaptors/ocl.md

@@ -18,7 +18,7 @@ This option is suited for scheduled synchronization or workflows requiring regul
 ## Authentication
 When integrating with OCL via OpenFn, you must provide a username and password to generate an authorization token ([see OCL docs](https://docs.openconceptlab.org/en/latest/oclapi/overview.html#authentication-and-authorization)). See this adaptor's [Configuration docs](/adaptors/packages/ocl-configuration-schema) for more on the required authentication parameters.
 
-See platform docs on [managing credentials](documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
+See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
 
 ```
 {

adaptors/odoo.md

@@ -21,7 +21,7 @@ Odoo supports two primary integration options with OpenFn:
 2. When integrating with Odoo via OpenFn, authentication via **User Credentials** is supported.
 3. See this adaptor's [Configuration docs](/adaptors/packages/odoo-configuration-schema) for more on the required authentication parameters.
 
-See platform docs on [managing credentials](documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
+See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
 
 ```
 {

adaptors/openmrs.md

@@ -29,7 +29,7 @@ When integrating with OpenMRS via OpenFn, **Basic Authentication** is supported.
 The `instanceUrl`, `username` an `password` properties are all required to
 access your OpenMRS instance.
 
-See [Managing Credentials](documentation/manage-projects/manage-credentials) to
+See [Managing Credentials](/documentation/manage-projects/manage-credentials) to
 configure a credential in OpenFn.
 
 If working locally or if using a Raw JSON credential type, then your

adaptors/sftp.md

@@ -16,7 +16,7 @@ Using this adaptor, you can read and write files (e.g., `csv`, `xls`, `json` fil
 
 When integrating with a SFTP server via OpenFn, you can provide a `username` and `password` for an authorized user to authenticate. See this adaptor's [Configuration docs](/adaptors/packages/sftp-configuration-schema) for more on the required authentication parameters.
 
-See platform docs on [managing credentials](documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
+See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
 
 ```
 {

articles/2020-06-16-how-information-is-organized.md

@@ -1,9 +1,7 @@
 ---
 layout: post
 title: 'How Information Is Organized... In Organizations'
-author: Taylor Downs
-author_url: https://github.com/taylordowns2000
-author_image_url: https://avatars.githubusercontent.com/taylordowns2000
+authors: taylor
 tags: [how-to, tips]
 image: /img/informationorganized.jpg
 featured: false
@@ -61,7 +59,7 @@ technology.
 
 ### Boxes and crow's feet
 
-![]({{ site.baseurl }}/assets/images/box5.png)
+![](/img/box5.png)
 
 The box is my favorite. It represents an entity in your data system. Entities
 (like `teachers`) have attributes (like `name`, `phone number`, `date of birth`,
@@ -71,7 +69,7 @@ gender, etc. These are the fields on your teacher entity. By submitting one of
 these forms, you’ll add a new teacher to your database. If you’re an Excel
 person, the attributes are columns in your `teachers` table.
 
-![]({{ site.baseurl }}/assets/images/crowsfeet2.png)
+![](/img/crowsfeet2.png)
 
 The crow’s foot is my second favorite. It’s used to show relationships between
 entities. We know that teachers are related to the sessions that they conduct.
@@ -85,7 +83,7 @@ relationship. The crow’s foot (that little three-pronged fella) denotes the
 many. One teacher can have many sessions. One session, however, can only have
 one teacher. See the diagram below.
 
-![]({{ site.baseurl }}/assets/images/objectmodel3.png)
+![](/img/objectmodel3.png)
 
 If we focus just on `teacher` and `session` and think back to MS Excel, we can
 envision a `teachers` table and a `sessions` table. Let’s put them on different
@@ -131,4 +129,5 @@ interchangeable parts. Alas, the middle way is probably the best.
 That’s all for now. More soon.
 
 _Need help organizing or scaling your organization's information or process
-flows? Contact our team of ICT4D specialists at <[email protected]>._
+flows? Contact our team of ICT4D specialists at
+[[email protected]](mailto:[email protected])._