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
You can look at this for more detail. But I will summarize what I think are the important ones here:
Resource
source: The file object. url: The expected target url full_url: url prefixed with the site base url mentioned in site.yaml meta: Holds all the meta data - inherited from parent node or site and the ones in the page header
Node
source: The folder object. url: The expected target url full_url: url prefixed with the site base url mentioned in site.yaml meta: Holds all the meta data - inherited from the site and the ones mentioned in meta.yaml in the folder
Apart from the standard Node methods this also has the following lookup methods:
resource_from_relative_path, resource_from_relative_deploy_path, resource_from_path - Lookup a resource object based on path, path relative to content, relative to deploy folder, or full source path respectively.
Similar methods for Node.
Apart from these, these may also have additional properties added by individual plugins. For example, the grouper, tagger and sorter add the walk methods to the Node object.
What properties does a
resource
have? Anode
?The text was updated successfully, but these errors were encountered: