Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
354 changes: 177 additions & 177 deletions _compress_images_cache.yml

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion contribute.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Depending on your skills and interest, you can help in a number of ways. We desi

## Learn how we work

If you are not familiar with the concepts of open design, we have a [great intro]({{ '/guide/getting-started/open-design/' | relative_url }}) for you. Open, public collaboration gives a lot of freedom to each participant and relies on us organically coming up with the organizational structures we want. The result is that things can sometimes look unorganized or unintuitive from the outside. The big benefit is that you can choose how you want to participate. Let's jump in.
If you are not familiar with the concepts of open design, we have a [great intro]({{ '/guide/designing-products/open-design/' | relative_url }}) for you. Open, public collaboration gives a lot of freedom to each participant and relies on us organically coming up with the organizational structures we want. The result is that things can sometimes look unorganized or unintuitive from the outside. The big benefit is that you can choose how you want to participate. Let's jump in.

## How to get involved in the community

Expand Down
8 changes: 7 additions & 1 deletion guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,13 @@ We designed this guide to help anyone navigate those complexities—regardless o

### [Getting started]({{ '/guide/getting-started/introduction/' | relative_url }})

Provides top-level overviews of common visual language, software, and best practices for design collaboration.
Provides top-level overviews of common visual language, technology, software, and hardware.

---

### [Designing Bitcoin products]({{ '/guide/designing-products/introduction/' | relative_url }})

A close look at the design process, from the concept of open design to use cases and frameworks like the usage life cycle.

---

Expand Down
4 changes: 2 additions & 2 deletions guide/case-studies/cloud-backup.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Editor's notes

## Cash account / Daily spending

Imagine a product which tries to solve the problem of quickly and easily sending smaller amounts of money to friends and family, or for [small purchases]({{ '/guide/getting-started/personal-finance/#day-to-day-spending' | relative_url }}). Ease and speed of use will be important as usage is likely to be on mobile devices and on the go. Users are not expected to be well versed in bitcoin technology or advanced private key management, which makes it reasonable to worry more about self-inflicted loss than from theft.
Imagine a product which tries to solve the problem of quickly and easily sending smaller amounts of money to friends and family, or for [small purchases]({{ '/guide/designing-products/personal-finance/#day-to-day-spending' | relative_url }}). Ease and speed of use will be important as usage is likely to be on mobile devices and on the go. Users are not expected to be well versed in bitcoin technology or advanced private key management, which makes it reasonable to worry more about self-inflicted loss than from theft.

A single-key scheme with [automatic cloud backup]({{ '/guide/private-key-management/cloud-backup/' | relative_url }}) might be the best choice for the majority of users in this case. For more advanced users you could offer the option to opt-out of automatic cloud backup and instead use a [recovery phrase]({{ '/guide/private-key-management/manual-backup/' | relative_url }}).

Expand Down Expand Up @@ -116,7 +116,7 @@ The import sequence guides the user through entering the recovery phrase, which
**Case study resources**
- [Protoype](https://www.figma.com/proto/SRWlaxbDulsacpPQn2TTri/Case-study-prototypes?node-id=1%3A3&viewport=1357%2C576%2C1&scaling=scale-down)
- [Figma design file](https://www.figma.com/file/SRWlaxbDulsacpPQn2TTri/Case-study-prototypes?node-id=0%3A1)
- [Use case]({{ '/guide/getting-started/personal-finance/#day-to-day-spending' | relative_url }})
- [Use case]({{ '/guide/designing-products/personal-finance/#day-to-day-spending' | relative_url }})
- [Private key scheme]({{ '/guide/private-key-management/cloud-backup/' | relative_url }})
- [Backup guidance for users]({{ '/guide/private-key-management/backups/#encrypted-cloud-backup' | relative_url }})

2 changes: 1 addition & 1 deletion guide/case-studies/introduction.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
layout: guide
title: Case studies
description: A range of case study designs for Bitcoin applications.
nav_order: 7
nav_order: 8
has_children: true
permalink: /guide/case-studies/
main_classes: -no-top-padding
Expand Down
2 changes: 1 addition & 1 deletion guide/contribute/contribute.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
layout: guide
title: Contribute to guide
description: Additional material for both readers and writers of the guide.
nav_order: 8
nav_order: 9
has_children: true
permalink: /guide/contribute/
main_classes: -no-top-padding
Expand Down
2 changes: 1 addition & 1 deletion guide/contribute/illustration-guidelines.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ The basic design of this website was intentionally kept minimal, so authors have

We collaborate on visuals the same way we collaborate on text. Please make the source files for your illustrations publicly accessible. For file-based visuals (Sketch, Photoshop, etc), use cloud hosting like a Github repository, Dropbox folder or other similar service. For Figma file, share a link to the source file.

Each markdown file should contain a comment at the top that include links to these source files. For [example](https://raw.githubusercontent.com/BitcoinDesign/Guide/master/guide/getting-started/common-user-flows.md):
Each markdown file should contain a comment at the top that include links to these source files. For [example](https://raw.githubusercontent.com/BitcoinDesign/Guide/master/guide/designing-products/common-user-flows.md):

{% raw %}
```
Expand Down
Loading