Skip to content
Closed
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
106 changes: 106 additions & 0 deletions guide/contribute/target-audience.md
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,106 @@
---
layout: guide
title: Target audience
description: Defining the target audience for the Bitcoin Design Guide
nav_order: 2
parent: Contribute to guide
permalink: /guide/contribute/target-audience/
image: https://bitcoin.design/assets/images/guide/contribute/target-audience/target-audience-preview.jpg
main_classes: -no-top-padding
---

{% include picture.html
image = "/assets/images/guide/contribute/review/review.jpg"
retina = "/assets/images/guide/contribute/review/review@2x.jpg"
mobile = "/assets/images/guide/contribute/review/review-mobile.jpg"
mobileRetina = "/assets/images/guide/contribute/review/review-mobile@2x.jpg"
alt-text = "Reviewing content changes"
width = 1600
height = 800
layout = "full-width"
%}

# Who are we writing the Bitcoin design guide for?

[INTO PARAGRAPH GOES HERE]

- Designer
- Project manager
- Developer
- Bitcoiner

## The designer
[INTRO PARAGRAPH NEDDED HERE]

*The designers are our main audience for the design guide.
Who they are and what they know (and don’t know) There are also few designers in the space, and they struggle to wrap their heads around the topic. They may be the least incentivized and have the highest barriers to learn and figure things out.*

### Scenarios

- Trained designer who was worked in an agency before and is now starting work on a Bitcoin product
- A passionate designer without formal training or experience and is helping out an open-source bitcoin product
- Trained designer with an idea for a product who wants to quickly prototype a somewhat realistic application (could be for a client project, a designathon, a Dribbble shot, etc)
- A designer who is interested in open design and is looking for a project to help out with (differentiate between major involvement vs helping out occasionally)

### Solutions

- Explain why bitcoin matters and how it works without getting into a ton of technical detail
- Help navigate open source and open design
- Showcase great products and concepts
- Provide specific approaches and resources to help in day-to-day work
- Provide design resources (UI Kit)

## The developer
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge

- Has a deep understanding of the protocol and apis
- Has started building solo and lacks design resources
- Is not sure which patterns are good or bad for ux
- Is trying to create a new experience and has no design references

### Scenarios

- Solo developer starting their own project
- Open source developer wanting to understand ux implications of their PR
- Open source developer wanting to justify their design decisions to other contributors
- Developer with a product idea but self funded and lacks design resources
- Developer with a bit of design experience

### Solutions

- UI Kit / flexible solutions that can be mixed and matched
- Design & technical foundations of bitcoin to help onboard a non bitcoin designer to their team
- Design Patterns / Understand ux tradeoffs of patterns they are considering to implement
- Use Cases / Gain wider perspectives on user archetypes and stages of learning they go through

## The product manager
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge
- Top-level understanding of design and development basics
- Interested in use cases, advantages, disadvantages of technologies and features

### Scenarios
- Wants to implement a better design process in a project
- Is looking for designers to contribute to their project
- Is looking for ways to evaluate if their product is implementing things the right way

### Solutions

- Open design and design workflow information
- Best practices documentation
- Primer and overview pages
- Pages on solving specific problems to forward to the team

#4 The bitcoiner
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge
- Knows a lot about bitcoin but has no design or development experience

### Scenarios
?
### Solutions
?
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
[WIP] Create target-audience.md by pavlenex · Pull Request #233 · BitcoinDesign/Guide · GitHub
Skip to content
Closed
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
106 changes: 106 additions & 0 deletions guide/contribute/target-audience.md
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,106 @@
---
layout: guide
title: Target audience
description: Defining the target audience for the Bitcoin Design Guide
nav_order: 2
parent: Contribute to guide
permalink: /guide/contribute/target-audience/
image: https://bitcoin.design/assets/images/guide/contribute/target-audience/target-audience-preview.jpg
main_classes: -no-top-padding
---

{% include picture.html
image = "/assets/images/guide/contribute/review/review.jpg"
retina = "/assets/images/guide/contribute/review/review@2x.jpg"
mobile = "/assets/images/guide/contribute/review/review-mobile.jpg"
mobileRetina = "/assets/images/guide/contribute/review/review-mobile@2x.jpg"
alt-text = "Reviewing content changes"
width = 1600
height = 800
layout = "full-width"
%}

# Who are we writing the Bitcoin design guide for?

[INTO PARAGRAPH GOES HERE]

- Designer
- Project manager
- Developer
- Bitcoiner

## The designer
[INTRO PARAGRAPH NEDDED HERE]

*The designers are our main audience for the design guide.
Who they are and what they know (and don’t know) There are also few designers in the space, and they struggle to wrap their heads around the topic. They may be the least incentivized and have the highest barriers to learn and figure things out.*

### Scenarios

- Trained designer who was worked in an agency before and is now starting work on a Bitcoin product
- A passionate designer without formal training or experience and is helping out an open-source bitcoin product
- Trained designer with an idea for a product who wants to quickly prototype a somewhat realistic application (could be for a client project, a designathon, a Dribbble shot, etc)
- A designer who is interested in open design and is looking for a project to help out with (differentiate between major involvement vs helping out occasionally)

### Solutions

- Explain why bitcoin matters and how it works without getting into a ton of technical detail
- Help navigate open source and open design
- Showcase great products and concepts
- Provide specific approaches and resources to help in day-to-day work
- Provide design resources (UI Kit)

## The developer
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge

- Has a deep understanding of the protocol and apis
- Has started building solo and lacks design resources
- Is not sure which patterns are good or bad for ux
- Is trying to create a new experience and has no design references

### Scenarios

- Solo developer starting their own project
- Open source developer wanting to understand ux implications of their PR
- Open source developer wanting to justify their design decisions to other contributors
- Developer with a product idea but self funded and lacks design resources
- Developer with a bit of design experience

### Solutions

- UI Kit / flexible solutions that can be mixed and matched
- Design & technical foundations of bitcoin to help onboard a non bitcoin designer to their team
- Design Patterns / Understand ux tradeoffs of patterns they are considering to implement
- Use Cases / Gain wider perspectives on user archetypes and stages of learning they go through

## The product manager
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge
- Top-level understanding of design and development basics
- Interested in use cases, advantages, disadvantages of technologies and features

### Scenarios
- Wants to implement a better design process in a project
- Is looking for designers to contribute to their project
- Is looking for ways to evaluate if their product is implementing things the right way

### Solutions

- Open design and design workflow information
- Best practices documentation
- Primer and overview pages
- Pages on solving specific problems to forward to the team

#4 The bitcoiner
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge
- Knows a lot about bitcoin but has no design or development experience

### Scenarios
?
### Solutions
?
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' [WIP] Create target-audience.md by pavlenex · Pull Request #233 · BitcoinDesign/Guide · GitHub
Skip to content
Closed
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
106 changes: 106 additions & 0 deletions guide/contribute/target-audience.md
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,106 @@
---
layout: guide
title: Target audience
description: Defining the target audience for the Bitcoin Design Guide
nav_order: 2
parent: Contribute to guide
permalink: /guide/contribute/target-audience/
image: https://bitcoin.design/assets/images/guide/contribute/target-audience/target-audience-preview.jpg
main_classes: -no-top-padding
---

{% include picture.html
image = "/assets/images/guide/contribute/review/review.jpg"
retina = "/assets/images/guide/contribute/review/review@2x.jpg"
mobile = "/assets/images/guide/contribute/review/review-mobile.jpg"
mobileRetina = "/assets/images/guide/contribute/review/review-mobile@2x.jpg"
alt-text = "Reviewing content changes"
width = 1600
height = 800
layout = "full-width"
%}

# Who are we writing the Bitcoin design guide for?

[INTO PARAGRAPH GOES HERE]

- Designer
- Project manager
- Developer
- Bitcoiner

## The designer
[INTRO PARAGRAPH NEDDED HERE]

*The designers are our main audience for the design guide.
Who they are and what they know (and don’t know) There are also few designers in the space, and they struggle to wrap their heads around the topic. They may be the least incentivized and have the highest barriers to learn and figure things out.*

### Scenarios

- Trained designer who was worked in an agency before and is now starting work on a Bitcoin product
- A passionate designer without formal training or experience and is helping out an open-source bitcoin product
- Trained designer with an idea for a product who wants to quickly prototype a somewhat realistic application (could be for a client project, a designathon, a Dribbble shot, etc)
- A designer who is interested in open design and is looking for a project to help out with (differentiate between major involvement vs helping out occasionally)

### Solutions

- Explain why bitcoin matters and how it works without getting into a ton of technical detail
- Help navigate open source and open design
- Showcase great products and concepts
- Provide specific approaches and resources to help in day-to-day work
- Provide design resources (UI Kit)

## The developer
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge

- Has a deep understanding of the protocol and apis
- Has started building solo and lacks design resources
- Is not sure which patterns are good or bad for ux
- Is trying to create a new experience and has no design references

### Scenarios

- Solo developer starting their own project
- Open source developer wanting to understand ux implications of their PR
- Open source developer wanting to justify their design decisions to other contributors
- Developer with a product idea but self funded and lacks design resources
- Developer with a bit of design experience

### Solutions

- UI Kit / flexible solutions that can be mixed and matched
- Design & technical foundations of bitcoin to help onboard a non bitcoin designer to their team
- Design Patterns / Understand ux tradeoffs of patterns they are considering to implement
- Use Cases / Gain wider perspectives on user archetypes and stages of learning they go through

## The product manager
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge
- Top-level understanding of design and development basics
- Interested in use cases, advantages, disadvantages of technologies and features

### Scenarios
- Wants to implement a better design process in a project
- Is looking for designers to contribute to their project
- Is looking for ways to evaluate if their product is implementing things the right way

### Solutions

- Open design and design workflow information
- Best practices documentation
- Primer and overview pages
- Pages on solving specific problems to forward to the team

#4 The bitcoiner
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge
- Knows a lot about bitcoin but has no design or development experience

### Scenarios
?
### Solutions
?
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' [WIP] Create target-audience.md by pavlenex · Pull Request #233 · BitcoinDesign/Guide · GitHub
Skip to content
Closed
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
106 changes: 106 additions & 0 deletions guide/contribute/target-audience.md
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,106 @@
---
layout: guide
title: Target audience
description: Defining the target audience for the Bitcoin Design Guide
nav_order: 2
parent: Contribute to guide
permalink: /guide/contribute/target-audience/
image: https://bitcoin.design/assets/images/guide/contribute/target-audience/target-audience-preview.jpg
main_classes: -no-top-padding
---

{% include picture.html
image = "/assets/images/guide/contribute/review/review.jpg"
retina = "/assets/images/guide/contribute/review/review@2x.jpg"
mobile = "/assets/images/guide/contribute/review/review-mobile.jpg"
mobileRetina = "/assets/images/guide/contribute/review/review-mobile@2x.jpg"
alt-text = "Reviewing content changes"
width = 1600
height = 800
layout = "full-width"
%}

# Who are we writing the Bitcoin design guide for?

[INTO PARAGRAPH GOES HERE]

- Designer
- Project manager
- Developer
- Bitcoiner

## The designer
[INTRO PARAGRAPH NEDDED HERE]

*The designers are our main audience for the design guide.
Who they are and what they know (and don’t know) There are also few designers in the space, and they struggle to wrap their heads around the topic. They may be the least incentivized and have the highest barriers to learn and figure things out.*

### Scenarios

- Trained designer who was worked in an agency before and is now starting work on a Bitcoin product
- A passionate designer without formal training or experience and is helping out an open-source bitcoin product
- Trained designer with an idea for a product who wants to quickly prototype a somewhat realistic application (could be for a client project, a designathon, a Dribbble shot, etc)
- A designer who is interested in open design and is looking for a project to help out with (differentiate between major involvement vs helping out occasionally)

### Solutions

- Explain why bitcoin matters and how it works without getting into a ton of technical detail
- Help navigate open source and open design
- Showcase great products and concepts
- Provide specific approaches and resources to help in day-to-day work
- Provide design resources (UI Kit)

## The developer
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge

- Has a deep understanding of the protocol and apis
- Has started building solo and lacks design resources
- Is not sure which patterns are good or bad for ux
- Is trying to create a new experience and has no design references

### Scenarios

- Solo developer starting their own project
- Open source developer wanting to understand ux implications of their PR
- Open source developer wanting to justify their design decisions to other contributors
- Developer with a product idea but self funded and lacks design resources
- Developer with a bit of design experience

### Solutions

- UI Kit / flexible solutions that can be mixed and matched
- Design & technical foundations of bitcoin to help onboard a non bitcoin designer to their team
- Design Patterns / Understand ux tradeoffs of patterns they are considering to implement
- Use Cases / Gain wider perspectives on user archetypes and stages of learning they go through

## The product manager
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge
- Top-level understanding of design and development basics
- Interested in use cases, advantages, disadvantages of technologies and features

### Scenarios
- Wants to implement a better design process in a project
- Is looking for designers to contribute to their project
- Is looking for ways to evaluate if their product is implementing things the right way

### Solutions

- Open design and design workflow information
- Best practices documentation
- Primer and overview pages
- Pages on solving specific problems to forward to the team

#4 The bitcoiner
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge
- Knows a lot about bitcoin but has no design or development experience

### Scenarios
?
### Solutions
?
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' [WIP] Create target-audience.md by pavlenex · Pull Request #233 · BitcoinDesign/Guide · GitHub
Skip to content
Closed
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
106 changes: 106 additions & 0 deletions guide/contribute/target-audience.md
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,106 @@
---
layout: guide
title: Target audience
description: Defining the target audience for the Bitcoin Design Guide
nav_order: 2
parent: Contribute to guide
permalink: /guide/contribute/target-audience/
image: https://bitcoin.design/assets/images/guide/contribute/target-audience/target-audience-preview.jpg
main_classes: -no-top-padding
---

{% include picture.html
image = "/assets/images/guide/contribute/review/review.jpg"
retina = "/assets/images/guide/contribute/review/review@2x.jpg"
mobile = "/assets/images/guide/contribute/review/review-mobile.jpg"
mobileRetina = "/assets/images/guide/contribute/review/review-mobile@2x.jpg"
alt-text = "Reviewing content changes"
width = 1600
height = 800
layout = "full-width"
%}

# Who are we writing the Bitcoin design guide for?

[INTO PARAGRAPH GOES HERE]

- Designer
- Project manager
- Developer
- Bitcoiner

## The designer
[INTRO PARAGRAPH NEDDED HERE]

*The designers are our main audience for the design guide.
Who they are and what they know (and don’t know) There are also few designers in the space, and they struggle to wrap their heads around the topic. They may be the least incentivized and have the highest barriers to learn and figure things out.*

### Scenarios

- Trained designer who was worked in an agency before and is now starting work on a Bitcoin product
- A passionate designer without formal training or experience and is helping out an open-source bitcoin product
- Trained designer with an idea for a product who wants to quickly prototype a somewhat realistic application (could be for a client project, a designathon, a Dribbble shot, etc)
- A designer who is interested in open design and is looking for a project to help out with (differentiate between major involvement vs helping out occasionally)

### Solutions

- Explain why bitcoin matters and how it works without getting into a ton of technical detail
- Help navigate open source and open design
- Showcase great products and concepts
- Provide specific approaches and resources to help in day-to-day work
- Provide design resources (UI Kit)

## The developer
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge

- Has a deep understanding of the protocol and apis
- Has started building solo and lacks design resources
- Is not sure which patterns are good or bad for ux
- Is trying to create a new experience and has no design references

### Scenarios

- Solo developer starting their own project
- Open source developer wanting to understand ux implications of their PR
- Open source developer wanting to justify their design decisions to other contributors
- Developer with a product idea but self funded and lacks design resources
- Developer with a bit of design experience

### Solutions

- UI Kit / flexible solutions that can be mixed and matched
- Design & technical foundations of bitcoin to help onboard a non bitcoin designer to their team
- Design Patterns / Understand ux tradeoffs of patterns they are considering to implement
- Use Cases / Gain wider perspectives on user archetypes and stages of learning they go through

## The product manager
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge
- Top-level understanding of design and development basics
- Interested in use cases, advantages, disadvantages of technologies and features

### Scenarios
- Wants to implement a better design process in a project
- Is looking for designers to contribute to their project
- Is looking for ways to evaluate if their product is implementing things the right way

### Solutions

- Open design and design workflow information
- Best practices documentation
- Primer and overview pages
- Pages on solving specific problems to forward to the team

#4 The bitcoiner
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge
- Knows a lot about bitcoin but has no design or development experience

### Scenarios
?
### Solutions
?
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' [WIP] Create target-audience.md by pavlenex · Pull Request #233 · BitcoinDesign/Guide · GitHub
Skip to content
Closed
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
106 changes: 106 additions & 0 deletions guide/contribute/target-audience.md
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,106 @@
---
layout: guide
title: Target audience
description: Defining the target audience for the Bitcoin Design Guide
nav_order: 2
parent: Contribute to guide
permalink: /guide/contribute/target-audience/
image: https://bitcoin.design/assets/images/guide/contribute/target-audience/target-audience-preview.jpg
main_classes: -no-top-padding
---

{% include picture.html
image = "/assets/images/guide/contribute/review/review.jpg"
retina = "/assets/images/guide/contribute/review/review@2x.jpg"
mobile = "/assets/images/guide/contribute/review/review-mobile.jpg"
mobileRetina = "/assets/images/guide/contribute/review/review-mobile@2x.jpg"
alt-text = "Reviewing content changes"
width = 1600
height = 800
layout = "full-width"
%}

# Who are we writing the Bitcoin design guide for?

[INTO PARAGRAPH GOES HERE]

- Designer
- Project manager
- Developer
- Bitcoiner

## The designer
[INTRO PARAGRAPH NEDDED HERE]

*The designers are our main audience for the design guide.
Who they are and what they know (and don’t know) There are also few designers in the space, and they struggle to wrap their heads around the topic. They may be the least incentivized and have the highest barriers to learn and figure things out.*

### Scenarios

- Trained designer who was worked in an agency before and is now starting work on a Bitcoin product
- A passionate designer without formal training or experience and is helping out an open-source bitcoin product
- Trained designer with an idea for a product who wants to quickly prototype a somewhat realistic application (could be for a client project, a designathon, a Dribbble shot, etc)
- A designer who is interested in open design and is looking for a project to help out with (differentiate between major involvement vs helping out occasionally)

### Solutions

- Explain why bitcoin matters and how it works without getting into a ton of technical detail
- Help navigate open source and open design
- Showcase great products and concepts
- Provide specific approaches and resources to help in day-to-day work
- Provide design resources (UI Kit)

## The developer
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge

- Has a deep understanding of the protocol and apis
- Has started building solo and lacks design resources
- Is not sure which patterns are good or bad for ux
- Is trying to create a new experience and has no design references

### Scenarios

- Solo developer starting their own project
- Open source developer wanting to understand ux implications of their PR
- Open source developer wanting to justify their design decisions to other contributors
- Developer with a product idea but self funded and lacks design resources
- Developer with a bit of design experience

### Solutions

- UI Kit / flexible solutions that can be mixed and matched
- Design & technical foundations of bitcoin to help onboard a non bitcoin designer to their team
- Design Patterns / Understand ux tradeoffs of patterns they are considering to implement
- Use Cases / Gain wider perspectives on user archetypes and stages of learning they go through

## The product manager
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge
- Top-level understanding of design and development basics
- Interested in use cases, advantages, disadvantages of technologies and features

### Scenarios
- Wants to implement a better design process in a project
- Is looking for designers to contribute to their project
- Is looking for ways to evaluate if their product is implementing things the right way

### Solutions

- Open design and design workflow information
- Best practices documentation
- Primer and overview pages
- Pages on solving specific problems to forward to the team

#4 The bitcoiner
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge
- Knows a lot about bitcoin but has no design or development experience

### Scenarios
?
### Solutions
?
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' [WIP] Create target-audience.md by pavlenex · Pull Request #233 · BitcoinDesign/Guide · GitHub
Skip to content
Closed
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
106 changes: 106 additions & 0 deletions guide/contribute/target-audience.md
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,106 @@
---
layout: guide
title: Target audience
description: Defining the target audience for the Bitcoin Design Guide
nav_order: 2
parent: Contribute to guide
permalink: /guide/contribute/target-audience/
image: https://bitcoin.design/assets/images/guide/contribute/target-audience/target-audience-preview.jpg
main_classes: -no-top-padding
---

{% include picture.html
image = "/assets/images/guide/contribute/review/review.jpg"
retina = "/assets/images/guide/contribute/review/review@2x.jpg"
mobile = "/assets/images/guide/contribute/review/review-mobile.jpg"
mobileRetina = "/assets/images/guide/contribute/review/review-mobile@2x.jpg"
alt-text = "Reviewing content changes"
width = 1600
height = 800
layout = "full-width"
%}

# Who are we writing the Bitcoin design guide for?

[INTO PARAGRAPH GOES HERE]

- Designer
- Project manager
- Developer
- Bitcoiner

## The designer
[INTRO PARAGRAPH NEDDED HERE]

*The designers are our main audience for the design guide.
Who they are and what they know (and don’t know) There are also few designers in the space, and they struggle to wrap their heads around the topic. They may be the least incentivized and have the highest barriers to learn and figure things out.*

### Scenarios

- Trained designer who was worked in an agency before and is now starting work on a Bitcoin product
- A passionate designer without formal training or experience and is helping out an open-source bitcoin product
- Trained designer with an idea for a product who wants to quickly prototype a somewhat realistic application (could be for a client project, a designathon, a Dribbble shot, etc)
- A designer who is interested in open design and is looking for a project to help out with (differentiate between major involvement vs helping out occasionally)

### Solutions

- Explain why bitcoin matters and how it works without getting into a ton of technical detail
- Help navigate open source and open design
- Showcase great products and concepts
- Provide specific approaches and resources to help in day-to-day work
- Provide design resources (UI Kit)

## The developer
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge

- Has a deep understanding of the protocol and apis
- Has started building solo and lacks design resources
- Is not sure which patterns are good or bad for ux
- Is trying to create a new experience and has no design references

### Scenarios

- Solo developer starting their own project
- Open source developer wanting to understand ux implications of their PR
- Open source developer wanting to justify their design decisions to other contributors
- Developer with a product idea but self funded and lacks design resources
- Developer with a bit of design experience

### Solutions

- UI Kit / flexible solutions that can be mixed and matched
- Design & technical foundations of bitcoin to help onboard a non bitcoin designer to their team
- Design Patterns / Understand ux tradeoffs of patterns they are considering to implement
- Use Cases / Gain wider perspectives on user archetypes and stages of learning they go through

## The product manager
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge
- Top-level understanding of design and development basics
- Interested in use cases, advantages, disadvantages of technologies and features

### Scenarios
- Wants to implement a better design process in a project
- Is looking for designers to contribute to their project
- Is looking for ways to evaluate if their product is implementing things the right way

### Solutions

- Open design and design workflow information
- Best practices documentation
- Primer and overview pages
- Pages on solving specific problems to forward to the team

#4 The bitcoiner
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge
- Knows a lot about bitcoin but has no design or development experience

### Scenarios
?
### Solutions
?
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); [WIP] Create target-audience.md by pavlenex · Pull Request #233 · BitcoinDesign/Guide · GitHub
Skip to content
Closed
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
106 changes: 106 additions & 0 deletions guide/contribute/target-audience.md
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,106 @@
---
layout: guide
title: Target audience
description: Defining the target audience for the Bitcoin Design Guide
nav_order: 2
parent: Contribute to guide
permalink: /guide/contribute/target-audience/
image: https://bitcoin.design/assets/images/guide/contribute/target-audience/target-audience-preview.jpg
main_classes: -no-top-padding
---

{% include picture.html
image = "/assets/images/guide/contribute/review/review.jpg"
retina = "/assets/images/guide/contribute/review/review@2x.jpg"
mobile = "/assets/images/guide/contribute/review/review-mobile.jpg"
mobileRetina = "/assets/images/guide/contribute/review/review-mobile@2x.jpg"
alt-text = "Reviewing content changes"
width = 1600
height = 800
layout = "full-width"
%}

# Who are we writing the Bitcoin design guide for?

[INTO PARAGRAPH GOES HERE]

- Designer
- Project manager
- Developer
- Bitcoiner

## The designer
[INTRO PARAGRAPH NEDDED HERE]

*The designers are our main audience for the design guide.
Who they are and what they know (and don’t know) There are also few designers in the space, and they struggle to wrap their heads around the topic. They may be the least incentivized and have the highest barriers to learn and figure things out.*

### Scenarios

- Trained designer who was worked in an agency before and is now starting work on a Bitcoin product
- A passionate designer without formal training or experience and is helping out an open-source bitcoin product
- Trained designer with an idea for a product who wants to quickly prototype a somewhat realistic application (could be for a client project, a designathon, a Dribbble shot, etc)
- A designer who is interested in open design and is looking for a project to help out with (differentiate between major involvement vs helping out occasionally)

### Solutions

- Explain why bitcoin matters and how it works without getting into a ton of technical detail
- Help navigate open source and open design
- Showcase great products and concepts
- Provide specific approaches and resources to help in day-to-day work
- Provide design resources (UI Kit)

## The developer
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge

- Has a deep understanding of the protocol and apis
- Has started building solo and lacks design resources
- Is not sure which patterns are good or bad for ux
- Is trying to create a new experience and has no design references

### Scenarios

- Solo developer starting their own project
- Open source developer wanting to understand ux implications of their PR
- Open source developer wanting to justify their design decisions to other contributors
- Developer with a product idea but self funded and lacks design resources
- Developer with a bit of design experience

### Solutions

- UI Kit / flexible solutions that can be mixed and matched
- Design & technical foundations of bitcoin to help onboard a non bitcoin designer to their team
- Design Patterns / Understand ux tradeoffs of patterns they are considering to implement
- Use Cases / Gain wider perspectives on user archetypes and stages of learning they go through

## The product manager
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge
- Top-level understanding of design and development basics
- Interested in use cases, advantages, disadvantages of technologies and features

### Scenarios
- Wants to implement a better design process in a project
- Is looking for designers to contribute to their project
- Is looking for ways to evaluate if their product is implementing things the right way

### Solutions

- Open design and design workflow information
- Best practices documentation
- Primer and overview pages
- Pages on solving specific problems to forward to the team

#4 The bitcoiner
[INTRO PARAGRAPH NEDDED HERE]

### Prior knowledge
- Knows a lot about bitcoin but has no design or development experience

### Scenarios
?
### Solutions
?