A widget/component a piece of code that a user owns under their data tree. In order to publish a widget you need NEAR to pay for the storage costs + transaction gas to save the widget code to the social.near contract. You can do this directly from any of the supported gateways. However it is important to note based on the configurations of the gateway you are publishing to, not all functionality will be available to the widget despite the code being able to be rendered to every gateway.
In order to create a widget prior knowledge of JavaScript & ReactJS is helpful
To create a widget you can either “Fork” an existing widget in the “Developer” tab of alpha.near.org navbar OR you can create a fresh widget from the “Editor” section.
To do this from near.social just click the create tag. It is importing to note you will be brought to different components you are building in the past and you have the ability to add a fresh widget with the “Add” tab amongst your docks of componenets in your bOS IDE.
<aside> ⚠️ Don’t Want to Run NEAR Social in Your Browser start Running A Component Locally
</aside>
Want a quick start guide to forking widget, check out the Widget Factory! https://alpha.near.org/#/hack.near/widget/Factory or Manza from Metapool Components Library https://near.social/#/manzanal.near/widget/CommonComponentsLibrary?tab=home
Please note that to deploy the component, you'll need to sign in with a NEAR account and to make a deposit of a small amount of NEAR for the storage cost. This is because any bOS gateway uses the NEAR blockchain as its underneath.
<aside> 📚 Not saving widget metadata is like turning in a proposal named 0294583.docx Sure you have cool data in there but people would be hesitant to click it.
</aside>