Cross-References

Cross-references allow you to create links between related content nodes within your curriculum. These connections help users navigate related content, understand prerequisites, and see how concepts build on each other.

Overview

Cross-references enable you to:

• Link related content - Connect activities to supporting lessons
• Show prerequisites - Indicate what should come first
• Reference content - Point to definitions, examples, or resources
• Build learning paths - Create logical sequences through content

Reference Types

CurryCMS supports several reference types, each with a specific purpose:

Creating References

Adding a Reference

1. Open a content node for editing
2. Navigate to the References section
3. Click Add Reference
4. Select the reference type
5. Search for the target content node
6. Click Add

Target Search

When adding a reference:

1. Start typing the target node's title
2. Results appear as you type (typeahead search)
3. Results show title and node type
4. Click to select the target

Note: You can only reference content within the same curriculum.

Reference Panel

The references panel shows:

• Outgoing references - Links from this node to others
• Reference type - The relationship type
• Target node - What this node links to
• Remove button - Delete the reference

Managing References

Viewing References

In the content node editor:

1. Scroll to the References section
2. See all outgoing references
3. Click a reference to navigate to the target

Removing References

1. Find the reference in the References section
2. Click the Remove button (X icon)
3. The reference is deleted immediately

Stale References

If a referenced content node is deleted:

• The reference becomes stale
• Stale references show a warning indicator
• The target no longer exists

Clearing stale references:

1. Look for the "Clear Stale" button
2. Click to remove all stale references
3. Confirm the action

Reference Directions

References are directional:

• Source node - The node that has the reference
• Target node - The node being referenced

Example:
- Lesson A references Activity B (A → B)
- Activity B does NOT automatically reference Lesson A

To create bidirectional links, add references from both nodes.

Best Practices

Use Meaningful Types

Choose reference types that accurately describe the relationship:

Do:
- Use "Prerequisite" for content that must come first
- Use "Support" for supplementary materials
- Use "Reviewing" for review or practice content

Don't:
- Use "Referenced Content" for everything
- Create vague or arbitrary connections

Be Selective

Quality over quantity:

• Link to truly related content
• Don't create circular or redundant references
• Review references when updating content

Consider the User

Think about how references help learners:

• Prerequisites help sequencing
• Support links provide depth
• References aid navigation

Reference Types Explained

Support

Links to content that supports or enhances understanding:

• Supplementary activities
• Additional examples
• Extension materials
• Teacher resources

Prerequisite

Links to content that should be completed before this node:

• Prior lessons in a sequence
• Foundational skills
• Required background knowledge

Responding to Student Thinking

Links to resources for addressing student responses:

• Common misconceptions
• Intervention strategies
• Differentiation approaches
• Discussion prompts

Reviewing

Links to content that reviews these concepts:

• Practice activities
• Review games
• Assessment prep
• Study guides

Summary

Links to content that summarizes or consolidates:

• Lesson summaries
• Unit overviews
• Key takeaways
• Quick reference guides

Unlock

Links to content that gates or unlocks this node:

• Prerequisites that must be completed
• Assessments that open access
• Conditional content paths

Referenced Content

General links to related content:

• Definitions or vocabulary
• Examples or illustrations
• Related topics
• External resources (linked internally)

Use After

Links to content designed to follow this node:

• Follow-up activities
• Next steps
• Application exercises
• Extension challenges

References in Editions

When publishing an edition:

• All references are included in the snapshot
• Target nodes must exist in the same curriculum
• Stale references should be cleared before publishing

Common Questions

"Can I reference content in another curriculum?"

No, references can only link to content within the same curriculum. For cross-curriculum connections, consider:
- Using glossary terms (shared concepts)
- Creating variants with shared structure
- Documenting relationships externally

"What happens when I delete a referenced node?"

The reference becomes "stale":
- It still exists in the source node
- Shows as broken/missing
- Use "Clear Stale" to clean up

"Do references affect the content tree?"

References don't change the tree structure. They're metadata connections, not hierarchical relationships.

"Can I bulk-add references?"

Currently, references are added individually. For bulk operations, use the API or request import assistance.

"Are references visible to end users?"

References are primarily for authors and the CMS. How (or if) they're exposed to end users depends on your publishing/rendering implementation.

"Do references inherit to variants?"

References belong to the content node. In variants:
- Inherited nodes keep parent's references
- Overridden nodes can have different references
- Added nodes start with no references

Related Documentation:
- Working with Content - Content editing basics
- Glossary Terms - Linking vocabulary
- Publishing Editions - Edition content