Skip to content
This repository has been archived by the owner on Jun 2, 2020. It is now read-only.

Design a glossary of IPFS-related terms #372

Closed
ericronne opened this issue Nov 11, 2019 · 8 comments
Closed

Design a glossary of IPFS-related terms #372

ericronne opened this issue Nov 11, 2019 · 8 comments
Labels
dif/medium Prior experience is likely helpful effort/days Estimated to take multiple days, but less than a week topic/design-front-end Front-end implementation of UX/UI work topic/design-ux UX strategy, research, not solely visual design topic/design-visual Visual design ONLY, not part of a larger UX effort

Comments

@ericronne
Copy link
Contributor

Here are some design options for a glossary feature, for discussion.

A - Simple pop-up

glossary-A

B - Sliding panel

glossary-B

Toggle visibility with nav button …

glossary-B-button-action

Or tab

glossary-tab

Related issues

Define and implement tagging taxonomy for beta-site content
Create concepts dictionary (meta-concept-doc) aka glossary

@ericronne ericronne added topic/design-visual Visual design ONLY, not part of a larger UX effort topic/design-front-end Front-end implementation of UX/UI work topic/design-ux UX strategy, research, not solely visual design labels Nov 11, 2019
@ericronne ericronne changed the title Glossary design concepts Design a glossary of IPFS-related terms Nov 12, 2019
@ericronne
Copy link
Contributor Author

My design is based on this code by 18F.

Live example

@jessicaschilling
Copy link
Contributor

@ericronne My personal favorite might just be the pop-ups (particularly considering mobile), but kind of want to leave this choice in @cwaring's hands vis-a-vis ease of implementation. They've all got their strengths, so I might be inclined to go with the simplest one to build.

@jessicaschilling jessicaschilling added dif/medium Prior experience is likely helpful docs-ipfs effort/days Estimated to take multiple days, but less than a week labels Nov 12, 2019
@ericronne
Copy link
Contributor Author

The 18f code is mobile friendly out of the box (not sure about vue-friendliness). +1 to @cwaring's call, 🙌
foLaM0rrNB

Copy link
Contributor

If this is being built in VuePress, any chance it can be built to be compatible with Vue as well so it can be used on ProtoSchool? See this open issue: ProtoSchool/protoschool.github.io#99

@cwaring
Copy link
Collaborator

cwaring commented Nov 13, 2019

I do love this idea but it could be an entire product by itself. As @terichadbourne pointed out the real value might come from a plugin that could work on any of our websites/apps. If we are considering i18n too it does start to get quite complex so we'll have to draft out the scope or MVP for testing on the docs site first.

@ericronne
Copy link
Contributor Author

I would exclude the glossary from the beta launch and bump it to next q as an enhancement.

@jessicaschilling
Copy link
Contributor

+1 - I think that was actually always the idea.

@jessicaschilling
Copy link
Contributor

Closing this issue in favor of already-existing #56, and linking in #56 to this discussion so we can implement visuals when we start work on this project.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dif/medium Prior experience is likely helpful effort/days Estimated to take multiple days, but less than a week topic/design-front-end Front-end implementation of UX/UI work topic/design-ux UX strategy, research, not solely visual design topic/design-visual Visual design ONLY, not part of a larger UX effort
Projects
None yet
Development

No branches or pull requests

4 participants