Skip to content
New issue

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

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

Already on GitHub? # to your account

Add Details for Supply Chain Use Case #82

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

magowan
Copy link
Member

@magowan magowan commented Jan 27, 2025

The Use Case working group generated slides describing Use Cases, this PR brings the description of the Supply Chain Use case into the website content..

@magowan magowan requested a review from bpradipt January 27, 2025 15:22
Copy link

netlify bot commented Jan 27, 2025

Deploy Preview for frolicking-manatee-96c0c8 ready!

Name Link
🔨 Latest commit b1c6359
🔍 Latest deploy log https://app.netlify.com/sites/frolicking-manatee-96c0c8/deploys/6797efacaea5e90008e027d6
😎 Deploy Preview https://deploy-preview-82--frolicking-manatee-96c0c8.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.

@fitzthum
Copy link
Member

You can fix the prose linter complaints by adding stuff to the allow list at styles/config/vocabularies/coco/accept.txt

The Use Case working group generated slides describing Use Cases, this PR brings the description of the Supply Chain Use case into the website content..

Signed-off-by: James Magowan <magowan@uk.ibm.com>
@magowan magowan force-pushed the UseCase_SupplyChain branch from 6e94b88 to b1c6359 Compare January 27, 2025 20:42
@magowan
Copy link
Member Author

magowan commented Jan 27, 2025

You can fix the prose linter complaints by adding stuff to the allow list at styles/config/vocabularies/coco/accept.txt

Fixed

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

Successfully merging this pull request may close these issues.

2 participants