The complete developer guide as a PDF document with code examples, can be found here: Developer-Manual

We provide a few ready-made CMS modules, so the web admin doesn’t have to write custom code to use the GpsNose platform. These modules use the low-level GpsNose SDK, calling different JSON services automatically.

The CMS module wraps the SDK calls to simplify using the provided functionality, like:

  1. Administer the GpsNose connection to the website (manage mashups and sub-communities)
  2. Read and write community members’ data for the primary- or sub-community
  3. Provide you with some ready-to-go HTML libraries/templates, so you don’t need to wrap the GpsNose data yourself for the browser-viewing.

Here you can see the schematic layers dependencies between your website, the CMS & SDK modules and the GpsNose platform behind it:

Currently, there are these CMS modules available or will be available (hopefully soon):

  • .NET Web.Framework – this is actually not a real “CMS module”, rather it’s a NuGet package, which you can plug into your website, to get all the needed dependencies, UI-components, web.config configuration and such done for you. You can checkout the SDK.Samples package to get running. Notice: this is the “classic MVC Framework” package, not a “aspnet core” one, which might come in the near future as well. The underlying SDK is already fully .NET core made, so it’s just a matter of wrapping it all up and porting from .NET MVC to Core MVC.
  • Typo3 CMS Module – this is a real PHP based Typo3 module, with all the bells and whistles, like linking your mashup site to GpsNose, generating QR-tokens etc.
  • WordPress CMS Module – this module is currently being developed and will provide hopefully all the functionality available in the Typo3 module.