Clone

HTTPS: git clone https://vervis.peers.community/repos/rd83r

SSH: git clone USERNAME@vervis.peers.community:rd83r

Branches

Participants: fr33, iko

Which tool to use for programming the UI
- Svelte
- Purescript
- Miso
- Reflex
- Shpadoinkle
- Haskell->WASM
- Typescript
- Guile
Which tool to use for the CSS?
- Tailwind?
- Bulma.io?
- SASS?
Where to create and collaborate on the designs?
- Inkscape?
- Penpot?
- https://storybook.js.org
- Seafile/nextcloud for design files?
Process of working on the design, user stories etc.

Documents to have:

Domain concepts (person, team, issue, repo, etc.)
- MR? PR? Patch? Patch Tracker? MR Tracker? PR Tracker? Or no use of the term “tracker”?
Soft features / values / qualities to have in the project UI
Person stories
- Who wants to do what and why (not how in detail; that’s up to the developer)
- Possibly some implementation criteria
- Higher level than the actual implementation detail
Design concepts
New terminology to create a metaphor? Like tweets/toots?

Next tasks:

fr33:
- Revise the initial big concepts/stories document
- Domain concepts document
- Core/minimal feature set to focus on right now, list of priorities
- List of documents/links to make it easy to find stuff
- Look at the person stories, confirm they make sense to me, break down too big stuff like “follow feature” or “manage X”
iko:
- Wireframe core features
- Start design guide, specifically for palette
- Continue adding Person Stories for the features list

iko: initial colours for Vervis (design guide) were based around orange and azure blue. Modern and a touch of bold. This can be tweaked or scrapped, open to suggestions.
fr33’s idea: forge theme
- softer colours
- Have both bright/dark themes
- Pleasant on people’s eyes
- Visually simple - clear and obvious ways to find things, uncluttered interface
- iko: “forge” concept colours could be oranges, reds, earth tones, a bit of grey
fr33’s feedback rom the initial set of Vervis colours
- Orange too bright
- Dark blue indistinguishable as blue, almost black
- iko: maybe start with orange and replace blue?

iko: Person Stories aren’t a strict blocker, but it would help me understand where your priorities are, how features are used individually and in conjunction, how you see certain features being useful for your target audience. Since there are already some features added to the UI in the Yesod implementation, I started writing some of the PS for them retroactively (ideally this is done before the feature is implemented but if we agree they are core features then it’s more to document why they are core features, how the Vervis team visualises who is using them, how they are being used). This might be useful later if someone asks why x feature was designed this way and could there be other implementations or enhancements that can be added.

fr33: what OCAP means in terms of the UI: person has a token to access which resources, e.g. to open issues.
- However, I don’t actually want the term on the UI or in the vocabulary. It’s not a concept in the vocabulary, unless there’s a special UI or advance settings, or in a developer mode (and a button to toggle developer mode, e.g. the JSON objects).
fr33: on the origin of Deck / Loom
- When I put things in the db schema, it helps to have a term for concepts, alternatives to ticket tracker, patch tracker (multiple items with the name “tracker”)
- Deck - from a deck of cards, tickets collected in a deck. Borrowed from Nextcloud Deck. In kanban there’s also Deck so it might be confusing, it’s in the code only
- Loom - patch, textile, a loom is a machine to create textiles
- May be replaced eventually with other terms, e.g. issues