Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What properties does a resource have? A node? #3

Open
alanhogan opened this issue Apr 29, 2011 · 1 comment
Open

What properties does a resource have? A node? #3

alanhogan opened this issue Apr 29, 2011 · 1 comment

Comments

@alanhogan
Copy link

What properties does a resource have? A node?

@navilan
Copy link
Member

navilan commented Apr 29, 2011

Hi,

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

Methods

walk - Walks child nodes
walk_resources - Walks contained resources recusively

Content Node (site.content)

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants