DevPacks > Components?

[ben]

@logrunner

I have some of my own DevPacks that I am using on my website. The previous advice, as I recall, was that going forward they shouldn’t be used as they aren’t as efficient as the encrypted Components derived from DevPacks and there is an overhead associated with the use of DevPacks?

If these DevPacks are just for your own projects, there’s no real need to convert them for distribution.

DevPacks do have some overhead because Elements needs to, amongst other things, watch for file changes and compile your DevPack on the fly. That overhead is one of the reasons why we don’t allow distributing DevPacks widely.

@logrunner

So how will I go about encrypting these and using them on my website if they are only for my own use.

Encryption happens automatically when you add a DevPack to the Elements Store. You will be able to add your DevPacks to the store directly in Elements, it’s a seamless system that “just works” without ever having to leave the app!

Also, there are no issues using DevPacks on your own website.

@logrunner

Will there be a mechanism for uploading these DevPacks to the Elements Store but having the resultant Components marked as private?

There isn’t a dedicated “private” option, but you can remove your pack from the store listings. If they’re only for your use, you don’t need to upload or encrypt them at all.

@logrunner

if I were to make Components available on the Elements Store for free, I presume I don’t need to have a Stripe account?

Correct. You won’t need a Stripe account to share free packs.