From 83577ab447b64e1a088a61dc1e2988cba2e5dd70 Mon Sep 17 00:00:00 2001 From: Nick O'Leary Date: Tue, 9 Aug 2016 23:41:28 +0100 Subject: [PATCH] Updated Design: Palette Management UI (markdown) --- Design:-Palette-Management-UI.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Design:-Palette-Management-UI.md b/Design:-Palette-Management-UI.md index 9277c65..b87ea49 100644 --- a/Design:-Palette-Management-UI.md +++ b/Design:-Palette-Management-UI.md @@ -100,5 +100,11 @@ By default, the catalog will be one we provide. But it needs to be possible cust ] } +### Further considerations + +A use case for providing a custom catalogue is to provide a smaller curated list of nodes - but still picked from the nodes that are publicly available. That will work with the current design where the module passed over the runtime api is assumed to be npm installable from npmjs.org. + +Another use case is to provide a catalogue of nodes from an alternative npm repository. In that instance, the catalogue must also provide sufficient information to allow the runtime to target that repo when running the npm install. + \ No newline at end of file