-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updates readme #31
Updates readme #31
Conversation
README.md
Outdated
|
||
`near-social-viewer` is a [web component (custom element)](https://developer.mozilla.org/en-US/docs/Web/API/Web_components) that implements the [near-social-vm](https://github.com/NearSocial/VM) for rendering code stored on-chain in the [SocialDB](https://github.com/NearSocial/social-db) smart contract (social.near). It is the simplest way to create your own [near social viewer](https://github.com/NearSocial/viewer) and it is the easiest method for embedding [Widgets](https://thewiki.near.page/near.social_widgets) into any web application. | ||
|
||
<strong>The latest version of this package is deployed to [nearfs](https://github.com/vgrichina/nearfs) at:</strong> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we also mention that it is published to NPM? And also having this nearfs link means we have to make sure to update it for every release. How do we automate that in a good way? Should we rather publish releases with a file pointing to the NEARFS link?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a good idea.
Do we need the full web4 in the address or can we just do the cid?
And is it right to think this should go in package.json, like this?
"nearfs": { // or ipfs?
"cid": "..."
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@petersalomonsen pull request for this here: #39
**Note: this includes changes from #39 **
Main modifications:
This is an ongoing pull request to update the documentation until next release.
Since we merged #27, we have full parity with near-social-vm -- and after we merge #26, we will be able to fully replace bos-workspace's gateway with a near-bos-webcomponent