As all plugins, the first thing you should do after the installation is to validate the settings. As in WPLDP, you have a specific settings allowing users to initialize the Resources Containers based on the PAIR (Project - Actors - Ideas - Resources) ontology.

For that, please go to Settings -> WpLDP Settings, check the "Initialize the PAIRs Containers" available option and save.

Once saved, you should be able to access the definition of the PAIRs basics containers located in Resources -> Containers.

The containers are equivalent to the folders containing your resources in a filesystem, with a major difference which is that they also imply the data model of the resources themselves. So, if you look into one of the containers definition, you will see that there is a Model metadata associated to it, consisting into a JSON simplified version of the PAIR Object Model.

The complete PAIR ontology for use in purely Semantic Web applications can be found here..

Once the plugin is properly installed and configured, you should be able to access a new "Resources" menu in the backend, located as follows:

The submenus allows you to access resources based on the default PAIRs containers. If you use custom containers definition, you will only get access to a global Resources listing.

Those submenus allows you to create new resources. When creating a new resource, the first thing to do is to select its associated containers, to get the proper data model:

Once done, form fields should automatically be available, according to the chosen data model:

This form allows you to enter information regarding your resources, and to associate it to other available resources. (Available on your site for now, and on distant sites in a close future). Once saved, this information will be available publicly in a JSON Linked Data format, at the URL provided on the edit page.

And, this is it. Next step is to use or to get a UI able to consume those data natively, as in the AV - Proof of concept (embedded in the plugin by the way :-) )