<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Packages on</title><link>https://platform-docs.slingr.io/extensions/packages/</link><description>Recent content in Packages on</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 16 Nov 2020 13:59:39 +0100</lastBuildDate><atom:link href="https://platform-docs.slingr.io/extensions/packages/index.xml" rel="self" type="application/rss+xml"/><item><title>Overview</title><link>https://platform-docs.slingr.io/extensions/packages/overview/</link><pubDate>Mon, 16 Nov 2020 13:59:39 +0100</pubDate><guid>https://platform-docs.slingr.io/extensions/packages/overview/</guid><description>What are packages? # In Slingr, packages are a way to reuse code across apps. For example, a package can provide features to access another service&amp;rsquo;s API (like Stripe, Slack or QuickBooks) by helping with authentication, data transformations, etc. Another common use case is for libraries, where they can offer a set of scripts with commonly used methods (encryption or math utilities, for example).
A wide range of official packages are available, designed to facilitate and enrich the development experience.</description></item><item><title>Create your own package</title><link>https://platform-docs.slingr.io/extensions/packages/create-your-own-package/</link><pubDate>Mon, 16 Nov 2020 13:59:39 +0100</pubDate><guid>https://platform-docs.slingr.io/extensions/packages/create-your-own-package/</guid><description>You have the capability to create your packages and import them into your apps. This is particularly useful for reusing components across multiple apps. A common example is a package that facilitates the use of an external service&amp;rsquo;s API.
The process of creating a new package involves three fundamental steps:
Package development: design and set up your new package in a Git repository. Package registration: register your developed package within the Slingr developer portal.</description></item><item><title>Packages features</title><link>https://platform-docs.slingr.io/extensions/packages/package-development/</link><pubDate>Mon, 16 Nov 2020 13:59:39 +0100</pubDate><guid>https://platform-docs.slingr.io/extensions/packages/package-development/</guid><description>When developing a new package, we strongly suggest to look at the skeleton-package repo, that already has the basic structure of a package. Another option, is to look at an existing package that you think could be similar. For example, if you are creating a package for a Google service you might want to check the packages for other Google services we have and use them as templates.
Usually, a package will have the following file structure:</description></item><item><title>Official Packages</title><link>https://platform-docs.slingr.io/extensions/packages/official_packages/</link><pubDate>Mon, 16 Nov 2020 13:59:39 +0100</pubDate><guid>https://platform-docs.slingr.io/extensions/packages/official_packages/</guid><description>Here you can find the list of our officially-supported packages:
HTTP OAuth Slingr Utils Cryptography Mandrill PandaDoc Veritone Endicia Infura Dall-E ShipEngine ChatGTP Eversign Alchemer Dendi PDF Twilio Microsoft Sharepoint Quickchart Stripe Webflow Slack Quickbooks Payments Quickbooks GitHub MailChimp Chargify Gmelius Gmail Google Calendar Google Workspace Google People Google Contacts Google Slides Google Drive DocuSign</description></item></channel></rss>