You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 29, 2022. It is now read-only.
I've published the docs from the tip of #38 to the repo's GitHub Pages endpoint as an example. It's pretty spiffy, and 100% documented!
I'm not sure how we ultimately want to handle this; should the GitHub Pages site be the current docs from master? Or do we keep archival versions? (Realm, for instance, does the latter.)
How we decide to implement it changes the level to which we can automate it. The workflow is currently all manual, but we could potentially get Travis to do it when we merge stuff to master.
The doc comments should be updated and expanded for new users.
We can publish a nicely formatted docset as a github pages site associated with this repo.
The text was updated successfully, but these errors were encountered: