The atsign.dev repo is home to the code behind our developer site. As everything we have to offer is open-source, why not make our website open-source too, to prove that we aren't using cookies or anything that tracks your presence.

We hope that this site has the A -> Z of everything you will need to develop with the @platform.

If you are a developer, this is your site - come join us and help us improve the content and the experience. We are always learning from you.

If you are new to the @platform, learn about how the platform works and how this can make such a big difference for you by cutting down on time to develop and market applications.

The site gives you all the tools, samples, examples and documentation needed to get started on the @platform and SDK. The site also provides access to the various communities where you can collaborate and talk to other developers working on the platform.

If this is your first time here, we strongly recommend navigating through our ‘getting started’ page. There, you will find all of the steps you will need to take in order to start developing your very own @platform application.

If you’d like to see what an @platform application looks like, feel free to visit our ‘sample apps’ page! Here, you will find a list of demonstrative applications showing off the many verbs/methods that exist on the @platform. The most basic of this list is ‘at_hello_world’ and the most advanced are ‘at_cookbook’ and ‘@mosphere’

If you think there should be a change made, or think there could be anything done better, feel free to raise a pull request to the trunk branch.

Take a look at CONTRIBUTING.md for further instructions.

When changes are merged to trunk they get published to the staging site devstaging.atsign.wtf by running the HugoBuild GitHub Action, which publishes to the gh-pages branch in this repo.

When a release is tagged with a semanic version number (e.g. 1.0.8) the DeployProd Action runs, which publishes to the gh-pages branch in the atsign.dev-prod repo.

Some of the content here is taken from pub.dev, which is the authorative source for API docs. The UpdateLibraries Action is set to run at 1415 daily to check for any updates to API docs for our packages.