Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

JonathanDHolden
Copy link
Contributor

content design edits

content design edits
Copy link

netlify bot commented Jul 13, 2024

Deploy Preview for inspiring-euclid-d918c8 ready!

Name Link
🔨 Latest commit 66876da
🔍 Latest deploy log https://app.netlify.com/sites/inspiring-euclid-d918c8/deploys/669232131132470008739bbf
😎 Deploy Preview https://deploy-preview-251--inspiring-euclid-d918c8.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

As a minimum a Directory Item must belong to a _Primary_ Channel, and this can be any Channel which accepts Directory Items of that type e.g. School. The _Primary_ Channel is required as it is the basis for the inferred URL and breadcrumb (as described above). Items may also belong to multiple _Other_ Channel. These additional Channels do not influence the URL or breadcrumb, but will include the Item in its list, and do still impact the available Facets (as described below).

In order to allow users to filter Directory Items by Directory Facets, Items must be 'tagged' with the appropriate Facets. When creating\editing an Item, the available Facets is determined by the Channels it belongs to. For example, consider the following Channels:
In order to allow users to filter Directory Items by Directory Facets, Items must be 'tagged' with the appropriate Facets. When creating or editing an Item, the available Facets are determined by the Channels they belong to. For example, consider the following Channels:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I this this "they belong to" is incorrect here. We should update that to "the node belongs to". It's the channels that the current node is attached to that defines what facets are available (I think).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I took so long getting back to this, I had no idea there was a response...

Anyhow, I don't think content designers know what nodes are, there is no mention of nodes on the page to help, and I'm afraid that I don't understand the suggested update. @markconroy

Copy link
Member

@markconroy markconroy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this @JonathanDHolden. Just one tiny change requested by me and I think we're good then.

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

Successfully merging this pull request may close these issues.

2 participants