move images to public folder

Author: andrewjschuang

docs-v2/pages/account/billing-settings.mdx

@@ -16,11 +16,11 @@ If you've already upgraded, you'll see an option to **Manage Subscription** here
 
 Hover over a specific column in the chart to see the number of credits run for that specific day:
 
-![Daily credits tooltip](./images/daily-invocations-tooltip.png)
+![Daily credits tooltip](/images/account/daily-invocations-tooltip.png)
 
 _Click_ on a specific column to see credits for that day, broken out by workflow / source:
 
-![Credits broken out by workflow / source](./images/usage-by-resource.png)
+![Credits broken out by workflow / source](/images/account/usage-by-resource.png)
 
 Users on the free tier will see the last 30 days of usage in this chart. Users on [paid plans](https://pipedream.com/pricing) will see the cumulative usage tied to their current billing period.
 

docs-v2/pages/core/contributing/components/actions-quickstart.mdx

@@ -96,7 +96,7 @@ To test the action:
 3. Click the **+** button to add a step to your workflow
 
 4. Click on **My Actions** and then select the **Action Demo** action to add it to your workflow.
-   ![Click on the My Actions button to show all of your privately published actions](./images/v3/using-private-actions.png)
+   ![Click on the My Actions button to show all of your privately published actions](/images/components/v3/using-private-actions.png)
 5. Deploy your workflow
 
 6. Click **RUN NOW** to execute your workflow and action

docs-v2/pages/core/contributing/components/api.mdx

@@ -303,11 +303,11 @@ When you define a prop in an app file, and that prop depends on the value of ano
 
 You create Trello _boards_ for new projects. Boards contain _lists_. For example, this **Active** board contains two lists:
 
-![Trello board example](./images/trello-board-example.png)
+![Trello board example](/images/components/trello-board-example.png)
 
 In Pipedream, users can choose from lists on a specific board:
 
-![Trello board and lists props](./images/trello-props.png)
+![Trello board and lists props](/images/components/trello-props.png)
 
 Both **Board** and **Lists** are defined in the Trello app file:
 
@@ -719,7 +719,7 @@ export default defineComponent({
 
 Refer to GitHub's component sources in the `pipedream` repo for an [example implementation](https://github.com/PipedreamHQ/pipedream/blob/b447d71f658d10d6a7432e8f5153bbda56ba9810/components/github/sources/common/common-flex.mjs#L27).
 
-![Info alert prop in GitHub source](./images/info-alert-prop-github.png)
+![Info alert prop in GitHub source](/images/components/info-alert-prop-github.png)
 
 #### Limits on props
 
@@ -903,7 +903,7 @@ async run({ $ }) {
 
 `$.summary` is used to surface brief, user-friendly summaries about what happened when an action step succeeds. For example, when [adding items to a Spotify playlist](https://github.com/PipedreamHQ/pipedream/blob/master/components/spotify/actions/add-items-to-playlist/add-items-to-playlist.mjs#L51):
 
-![Spotify example with $summary](./images/spotify-$summary-example.png)
+![Spotify example with $summary](/images/components/spotify-$summary-example.png)
 
 Example implementation:
 

docs-v2/pages/core/contributing/components/guidelines.mdx

@@ -470,7 +470,7 @@ Examples:
   understand what values they can enter, with specific values highlighted using
   backticks and links to external content.
 
-  ![image-20210326151706682](./images/image-20210326151706682.png)
+  ![image-20210326151706682](/images/components/image-20210326151706682.png)
 
 ### Optional vs Required Props
 
@@ -482,7 +482,7 @@ connect their account and enter a search term. The remaining fields are optional
 for users who want to filter the results, but they do not require any action to
 activate the source:
 
-![image-20210326151930885](./images/image-20210326151930885.png)
+![image-20210326151930885](/images/components/image-20210326151930885.png)
 
 ### Default Values
 

docs-v2/pages/core/contributing/components/index.mdx

@@ -60,15 +60,15 @@ Private action components published from the [CLI](/workflows/cli/reference/#pd-
 
 To use a published action, add a new step to your workflow and click **My Actions**. Your privately published action components will appear in this list.
 
-![Use the "My Actions" section in a new step to include your private actions](./images/v3/using-private-actions.png)
+![Use the "My Actions" section in a new step to include your private actions](/images/components/v3/using-private-actions.png)
 
 ### Using Private Sources
 
 Private source components deployed from your account via the [CLI](/workflows/cli/reference/#pd-deploy) will automatically create a new Source in your account with the prop configuration you specified.
 
 Then in the workflow builder, when creating the trigger, select the *Existing* sources tab in the upper right corner to select your deployed source:
 
-![Selecting a pre-exisiting deployed source as the trigger for the workflow](./images/v3/using-private-sources.png)
+![Selecting a pre-exisiting deployed source as the trigger for the workflow](/images/components/v3/using-private-sources.png)
 
 You can also deploy new instances of a source from the [Components dashboard](https://res.cloudinary.com/pipedreamin/image/upload/v1618550730/docs/components/image-20210411165325045_ia5sd5.png). To deploy a new instance of a source, click the menu on the right hand side and select **Create source**.
 

docs-v2/pages/core/contributing/components/sources-quickstart.mdx

@@ -106,7 +106,7 @@ Open the URL returned by the CLI (`https://pipedream.com/sources/dc_v3uXKz` in t
 
 Then click **RUN NOW** to invoke your source. Your event will appear in real-time, and you can select it to inspect the emitted data.
 
-![source](./images/quickstart/hello-world-1.gif)
+![source](/images/components/quickstart/hello-world-1.gif)
 
 ### Maintain state across executions
 
@@ -165,7 +165,7 @@ export default {
 
 Save the changes to your local file. Your component on Pipedream should automatically update. Return to the Pipedream UI and press **RUN NOW** — you should see the execution count appear in the event list.
 
-![source](./images/quickstart/hello-world-2.gif)
+![source](/images/components/quickstart/hello-world-2.gif)
 
 ### Invoke your code on a schedule
 
@@ -212,7 +212,7 @@ export default {
 
 Save the changes to your file (your component on Pipedream should automatically update). and then, return to the Pipedream UI and **reload the page**. You should now see the timer settings in the summary and a countdown to the next execution (you can still run your component manually). Your component will now run every 15 minutes.
 
-![source](./images/quickstart/hello-world-3.gif)
+![source](/images/components/quickstart/hello-world-3.gif)
 
 **Note**: if you'd like to change the schedule of your deployed component, visit the **Configuration** tab in the Pipedream UI and change the schedule accordingly. Changing the value of `intervalSeconds` within the component's code will not change the schedule of the running instance of the component. You can also set one value as the default `intervalSeconds` in the component's code, but run
 
@@ -298,7 +298,7 @@ curl -d '{ "message": "hello world!" }' \
   "INSERT-YOUR-ENDPOINT-URL-HERE"
 ```
 
-![source](./images/quickstart/hello-world-4.gif)
+![source](/images/components/quickstart/hello-world-4.gif)
 
 ## Emit new RSS items on a schedule (~10 mins)
 

docs-v2/pages/core/data-management/data-stores.mdx

@@ -34,21 +34,21 @@ To insert data into a data store:
 2. Search for the **Data Stores** app and select it.
 3. Select the **Add or update a single record** pre-built action.
 
-![Insert a single row into a data store](pages/images/v3/data-stores/add-or-update-a-single-record.png)
+![Insert a single row into a data store](/images/data-stores/add-or-update-a-single-record.png)
 
 Configure the action:
 
 1. **Select or create a Data Store** — create a new data store or choose an existing data store.
 2. **Key** - the unique ID for this data that you'll use for lookup later
 3. **Value** - The data to store at the specified `key`
 
-![Configure the action](pages/images/v3/data-stores/configuring-data-store-update-action.png)
+![Configure the action](/images/data-stores/configuring-data-store-update-action.png)
 
 For example, to store the timestamp when the workflow was initially triggered, set the **Key** to **Triggered At** and the **Value** to `{{steps.trigger.context.ts}}`.
 
 The **Key** must evaluate to a string. You can pass a static string, reference [exports](/workflows/#step-exports) from a previous step, or use [any valid expression](/core/workflows/using-props#entering-expressions).
 
-![Workflow trigger example](pages/images/v3/data-stores/update-data-store-key-by-reference.png)
+![Workflow trigger example](/images/data-stores/update-data-store-key-by-reference.png)
 
 <Callout type="info">
   Need to store multiple records in one action? Use the **Add or update multiple
@@ -63,7 +63,7 @@ The **Get record** action will retrieve the latest value of a data point in one
 2. Search for the **Data Stores** app and select it.
 3. Select the **Add or update a single record** pre-built action.
 
-![Create a get record action](pages/images/v3/data-stores/get-a-record-action-selection.png)
+![Create a get record action](/images/data-stores/get-a-record-action-selection.png)
 
 Configure the action:
 
@@ -72,13 +72,13 @@ Configure the action:
 3. **Create new record if key is not found** - if the specified key isn't found, you can create a new record
 4. **Value** - The data to store at the specified `key`
 
-![Get record action](pages/images/v3/data-stores/configure-data-store-retrieve-record.png)
+![Get record action](/images/data-stores/configure-data-store-retrieve-record.png)
 
 ### Deleting Data
 
 To delete a single record from your data store, use the **Delete a single record** action in a step:
 
-![Select the delete record step](pages/images/v3/data-stores/select-delete-a-record.png)
+![Select the delete record step](/images/data-stores/select-delete-a-record.png)
 
 Then configure the action:
 
@@ -87,7 +87,7 @@ Then configure the action:
 
 For example, you can delete the data at the **Triggered At** key that we've created in the steps above:
 
-![Delete a record example](pages/images/v3/data-stores/delete-a-single-record.png)
+![Delete a record example](/images/data-stores/delete-a-single-record.png)
 
 Deleting a record does not delete the entire data store. [To delete an entire data store, use the Pipedream Data Stores Dashboard](#deleting-data-stores).