Clarify demo (HF space) jargon

[egrace479]

Add "demos" in parentheses next to "spaces" in catalog byline and the dropdown for clarification. This was discussed offline with @dboghrat as a simpler solution, since the proposed text was too long.

Closes #122.

[hlapp]

Perhaps we should simply replace "Spaces" with "Demos"? In the future we might have demos in places different than just HF Spaces, and widening that search to still surface all demos might get more involved. But on the flip side treating instead demos as HF Spaces and demos hosted in other ways differently would become confusing for the users. (For example, would we then have drop-down items "Spaces (demos)" and "Demos (not Spaces)"? Hopefully not.)

Conversely, do we have an existing example or conceivable plans to host something on a HF Space that is not a demo? I think not.

Therefore, I'd argue we should simply replace "Spaces" with "Demos".

[egrace479]

Perhaps we should simply replace "Spaces" with "Demos"? In the future we might have demos in places different than just HF Spaces, and widening that search to still surface all demos might get more involved. But on the flip side treating instead demos as HF Spaces and demos hosted in other ways differently would become confusing for the users. (For example, would we then have drop-down items "Spaces (demos)" and "Demos (not Spaces)"? Hopefully not.)

Conversely, do we have an existing example or conceivable plans to host something on a HF Space that is not a demo? I think not.

Therefore, I'd argue we should simply replace "Spaces" with "Demos".

I'm inclined to agree with this change, especially with planned updates to have options other than HF (discussed in person with external collaborators this week).

[hlapp]

LGTM 👍🏻

[hlapp]

This reminds me that the list of keywords in the citation files (this one and .zenodo.json) is perhaps worth re-thinking. If these are the keywords that govern when this repo shows for a keyword being searched, several of the keywords seems too generic for expecting this repo to be an appropriate member in set of matches. For example, I'd say it's questionable whether this repo should show up when someone searches for "data", "demos", or "models.

Adding "demos" here doesn't really change the nature of the keywords (if they're too general, they already were so; if they were reasonably good, this should not change that), so may as well be part of the change set. But maybe worth discussing as a separate issue.