[WIP] Create target-audience.md

[pavlenex]

This is literally copy-pasted version of this Google Document.
The goal of this PR is to kick things off, lay out the structure and engage contributors into filling the gaps.

Feel free to suggest edits, comment on the structure, etc. This is a very very rough draft.

Once fully polished:
Closes#51

[GBKS]

Thanks @pavlenex for breathing life back into this one. This originally came up, IIRC, from a question by @ConorOkus. I believe it's also relevant to the discussions here, about the backup page speaking to the end-user vs a product builder.

[danielnordh]

Is it supposed to be linked to from the 'Contribute' section, and be listed in the side nav?
I can't find a link to the page.

I think the content of that doc is directionally correct (we are not making the guide for end users, and there are a few personas in that group). It is not written for general consumption however, so a copy and paste might need a fair amount of cleanup.

I also feel however, that as a community we are likely to create content that is relevant, and needed, for end users.
So it remains a question where that content should go.

• Sub-resources: bitcoin.design/resources/backups etc.
• Sub-domains: backups.bitcoin.design
• Separate microsites: bitcoinbackups.org, selfcustody.org, bitcoinforbeginners.org ...

[GBKS]

@danielnordh try this link here.

Looks like links on PR preview pages are now messed up and always link to bitcoin.design instead of keeping you on that preview domain. A side effect of fixing the canonical URLs. Will have to review this.

[GBKS]

If we don't want to have a full page on this topic, we can just expand the Know your reader paragraph in the content guidelines page a bit further.

[pavlenex]

Is it supposed to be linked to from the 'Contribute' section, and be listed in the side nav?

@danielnordh Yes, I haven't done any navigation additions yet it seems.

I also feel however, that as a community we are likely to create content that is relevant, and needed, for end users.

I agree, I assume that's what we meant with Bitcoiners1 persona?

@danielnordh if you have any concrete ideas, feel free to take over or suggest them, I just copy-pasted the work from Google Doc so we can keep the ball rolling, it needs a bit more work that's for sure.

[pavlenex]

Considering condensing this for now to a simple paragraph in the https://bitcoin.design/guide/contribute/content-guidelines/#speak-to-the-reader since there's no major consensus to proceed with this in-depth for now. It's getting clearer at this point that we write for designers, developers, and sometimes even users who can benefit from itit.

[GBKS]

@pavlenex I created a PR with that minor update to the "Know your reader" paragraph in the "Content guidelines" page. See #263.

Let's get some comments on whether that minor update is enough or we need this bigger page. I'm voting for the minor update.

This audience definition is just for the guide (IMHO). If we do workshops or other projects, they can have other audiences, whether that's a subset or a different group of people. So I'd keep this one fairly simple.

[pavlenex]

This is literally copy-pasted version of this Google Document.
The goal of this PR is to kick things off, lay out the structure and engage contributors into filling the gaps.

Feel free to suggest edits, comment on the structure, etc. This is a very very rough draft.

Once fully polished:
Closes#51

[GBKS]

Thanks @pavlenex for breathing life back into this one. This originally came up, IIRC, from a question by @ConorOkus. I believe it's also relevant to the discussions here, about the backup page speaking to the end-user vs a product builder.

[danielnordh]

Is it supposed to be linked to from the 'Contribute' section, and be listed in the side nav?
I can't find a link to the page.

I think the content of that doc is directionally correct (we are not making the guide for end users, and there are a few personas in that group). It is not written for general consumption however, so a copy and paste might need a fair amount of cleanup.

I also feel however, that as a community we are likely to create content that is relevant, and needed, for end users.
So it remains a question where that content should go.

• Sub-resources: bitcoin.design/resources/backups etc.
• Sub-domains: backups.bitcoin.design
• Separate microsites: bitcoinbackups.org, selfcustody.org, bitcoinforbeginners.org ...

[GBKS]

@danielnordh try this link here.

Looks like links on PR preview pages are now messed up and always link to bitcoin.design instead of keeping you on that preview domain. A side effect of fixing the canonical URLs. Will have to review this.

[GBKS]

If we don't want to have a full page on this topic, we can just expand the Know your reader paragraph in the content guidelines page a bit further.

[pavlenex]

Is it supposed to be linked to from the 'Contribute' section, and be listed in the side nav?

@danielnordh Yes, I haven't done any navigation additions yet it seems.

I also feel however, that as a community we are likely to create content that is relevant, and needed, for end users.

I agree, I assume that's what we meant with Bitcoiners1 persona?

@danielnordh if you have any concrete ideas, feel free to take over or suggest them, I just copy-pasted the work from Google Doc so we can keep the ball rolling, it needs a bit more work that's for sure.

[pavlenex]

Considering condensing this for now to a simple paragraph in the https://bitcoin.design/guide/contribute/content-guidelines/#speak-to-the-reader since there's no major consensus to proceed with this in-depth for now. It's getting clearer at this point that we write for designers, developers, and sometimes even users who can benefit from itit.

[GBKS]

@pavlenex I created a PR with that minor update to the "Know your reader" paragraph in the "Content guidelines" page. See #263.

Let's get some comments on whether that minor update is enough or we need this bigger page. I'm voting for the minor update.

This audience definition is just for the guide (IMHO). If we do workshops or other projects, they can have other audiences, whether that's a subset or a different group of people. So I'd keep this one fairly simple.

[pavlenex]

This is literally copy-pasted version of this Google Document.
The goal of this PR is to kick things off, lay out the structure and engage contributors into filling the gaps.

Feel free to suggest edits, comment on the structure, etc. This is a very very rough draft.

Once fully polished:
Closes#51

[GBKS]

Thanks @pavlenex for breathing life back into this one. This originally came up, IIRC, from a question by @ConorOkus. I believe it's also relevant to the discussions here, about the backup page speaking to the end-user vs a product builder.

[danielnordh]

Is it supposed to be linked to from the 'Contribute' section, and be listed in the side nav?
I can't find a link to the page.

I think the content of that doc is directionally correct (we are not making the guide for end users, and there are a few personas in that group). It is not written for general consumption however, so a copy and paste might need a fair amount of cleanup.

I also feel however, that as a community we are likely to create content that is relevant, and needed, for end users.
So it remains a question where that content should go.

• Sub-resources: bitcoin.design/resources/backups etc.
• Sub-domains: backups.bitcoin.design
• Separate microsites: bitcoinbackups.org, selfcustody.org, bitcoinforbeginners.org ...

[GBKS]

@danielnordh try this link here.

Looks like links on PR preview pages are now messed up and always link to bitcoin.design instead of keeping you on that preview domain. A side effect of fixing the canonical URLs. Will have to review this.

[GBKS]

If we don't want to have a full page on this topic, we can just expand the Know your reader paragraph in the content guidelines page a bit further.

[pavlenex]

Is it supposed to be linked to from the 'Contribute' section, and be listed in the side nav?

@danielnordh Yes, I haven't done any navigation additions yet it seems.

I also feel however, that as a community we are likely to create content that is relevant, and needed, for end users.

I agree, I assume that's what we meant with Bitcoiners1 persona?

@danielnordh if you have any concrete ideas, feel free to take over or suggest them, I just copy-pasted the work from Google Doc so we can keep the ball rolling, it needs a bit more work that's for sure.

[pavlenex]

Considering condensing this for now to a simple paragraph in the https://bitcoin.design/guide/contribute/content-guidelines/#speak-to-the-reader since there's no major consensus to proceed with this in-depth for now. It's getting clearer at this point that we write for designers, developers, and sometimes even users who can benefit from itit.

[GBKS]

@pavlenex I created a PR with that minor update to the "Know your reader" paragraph in the "Content guidelines" page. See #263.

Let's get some comments on whether that minor update is enough or we need this bigger page. I'm voting for the minor update.

This audience definition is just for the guide (IMHO). If we do workshops or other projects, they can have other audiences, whether that's a subset or a different group of people. So I'd keep this one fairly simple.

[pavlenex]

This is literally copy-pasted version of this Google Document.
The goal of this PR is to kick things off, lay out the structure and engage contributors into filling the gaps.

Feel free to suggest edits, comment on the structure, etc. This is a very very rough draft.

Once fully polished:
Closes#51

[GBKS]

Thanks @pavlenex for breathing life back into this one. This originally came up, IIRC, from a question by @ConorOkus. I believe it's also relevant to the discussions here, about the backup page speaking to the end-user vs a product builder.

[danielnordh]

Is it supposed to be linked to from the 'Contribute' section, and be listed in the side nav?
I can't find a link to the page.

I think the content of that doc is directionally correct (we are not making the guide for end users, and there are a few personas in that group). It is not written for general consumption however, so a copy and paste might need a fair amount of cleanup.

I also feel however, that as a community we are likely to create content that is relevant, and needed, for end users.
So it remains a question where that content should go.

• Sub-resources: bitcoin.design/resources/backups etc.
• Sub-domains: backups.bitcoin.design
• Separate microsites: bitcoinbackups.org, selfcustody.org, bitcoinforbeginners.org ...

[GBKS]

@danielnordh try this link here.

Looks like links on PR preview pages are now messed up and always link to bitcoin.design instead of keeping you on that preview domain. A side effect of fixing the canonical URLs. Will have to review this.

[GBKS]

If we don't want to have a full page on this topic, we can just expand the Know your reader paragraph in the content guidelines page a bit further.

[pavlenex]

Is it supposed to be linked to from the 'Contribute' section, and be listed in the side nav?

@danielnordh Yes, I haven't done any navigation additions yet it seems.

I also feel however, that as a community we are likely to create content that is relevant, and needed, for end users.

I agree, I assume that's what we meant with Bitcoiners1 persona?

@danielnordh if you have any concrete ideas, feel free to take over or suggest them, I just copy-pasted the work from Google Doc so we can keep the ball rolling, it needs a bit more work that's for sure.

[pavlenex]

Considering condensing this for now to a simple paragraph in the https://bitcoin.design/guide/contribute/content-guidelines/#speak-to-the-reader since there's no major consensus to proceed with this in-depth for now. It's getting clearer at this point that we write for designers, developers, and sometimes even users who can benefit from itit.

[GBKS]

@pavlenex I created a PR with that minor update to the "Know your reader" paragraph in the "Content guidelines" page. See #263.

Let's get some comments on whether that minor update is enough or we need this bigger page. I'm voting for the minor update.

This audience definition is just for the guide (IMHO). If we do workshops or other projects, they can have other audiences, whether that's a subset or a different group of people. So I'd keep this one fairly simple.

[pavlenex]

This is literally copy-pasted version of this Google Document.
The goal of this PR is to kick things off, lay out the structure and engage contributors into filling the gaps.

Feel free to suggest edits, comment on the structure, etc. This is a very very rough draft.

Once fully polished:
Closes#51

[GBKS]

Thanks @pavlenex for breathing life back into this one. This originally came up, IIRC, from a question by @ConorOkus. I believe it's also relevant to the discussions here, about the backup page speaking to the end-user vs a product builder.

[danielnordh]

Is it supposed to be linked to from the 'Contribute' section, and be listed in the side nav?
I can't find a link to the page.

I think the content of that doc is directionally correct (we are not making the guide for end users, and there are a few personas in that group). It is not written for general consumption however, so a copy and paste might need a fair amount of cleanup.

I also feel however, that as a community we are likely to create content that is relevant, and needed, for end users.
So it remains a question where that content should go.

• Sub-resources: bitcoin.design/resources/backups etc.
• Sub-domains: backups.bitcoin.design
• Separate microsites: bitcoinbackups.org, selfcustody.org, bitcoinforbeginners.org ...

[GBKS]

@danielnordh try this link here.

Looks like links on PR preview pages are now messed up and always link to bitcoin.design instead of keeping you on that preview domain. A side effect of fixing the canonical URLs. Will have to review this.

[GBKS]

If we don't want to have a full page on this topic, we can just expand the Know your reader paragraph in the content guidelines page a bit further.

[pavlenex]

Is it supposed to be linked to from the 'Contribute' section, and be listed in the side nav?

@danielnordh Yes, I haven't done any navigation additions yet it seems.

I also feel however, that as a community we are likely to create content that is relevant, and needed, for end users.

I agree, I assume that's what we meant with Bitcoiners1 persona?

@danielnordh if you have any concrete ideas, feel free to take over or suggest them, I just copy-pasted the work from Google Doc so we can keep the ball rolling, it needs a bit more work that's for sure.

[pavlenex]

Considering condensing this for now to a simple paragraph in the https://bitcoin.design/guide/contribute/content-guidelines/#speak-to-the-reader since there's no major consensus to proceed with this in-depth for now. It's getting clearer at this point that we write for designers, developers, and sometimes even users who can benefit from itit.

[GBKS]

@pavlenex I created a PR with that minor update to the "Know your reader" paragraph in the "Content guidelines" page. See #263.

Let's get some comments on whether that minor update is enough or we need this bigger page. I'm voting for the minor update.

This audience definition is just for the guide (IMHO). If we do workshops or other projects, they can have other audiences, whether that's a subset or a different group of people. So I'd keep this one fairly simple.

[pavlenex]

This is literally copy-pasted version of this Google Document.
The goal of this PR is to kick things off, lay out the structure and engage contributors into filling the gaps.

Feel free to suggest edits, comment on the structure, etc. This is a very very rough draft.

Once fully polished:
Closes#51

[GBKS]

Thanks @pavlenex for breathing life back into this one. This originally came up, IIRC, from a question by @ConorOkus. I believe it's also relevant to the discussions here, about the backup page speaking to the end-user vs a product builder.

[danielnordh]

Is it supposed to be linked to from the 'Contribute' section, and be listed in the side nav?
I can't find a link to the page.

I think the content of that doc is directionally correct (we are not making the guide for end users, and there are a few personas in that group). It is not written for general consumption however, so a copy and paste might need a fair amount of cleanup.

I also feel however, that as a community we are likely to create content that is relevant, and needed, for end users.
So it remains a question where that content should go.

• Sub-resources: bitcoin.design/resources/backups etc.
• Sub-domains: backups.bitcoin.design
• Separate microsites: bitcoinbackups.org, selfcustody.org, bitcoinforbeginners.org ...

[GBKS]

@danielnordh try this link here.

Looks like links on PR preview pages are now messed up and always link to bitcoin.design instead of keeping you on that preview domain. A side effect of fixing the canonical URLs. Will have to review this.

[GBKS]

If we don't want to have a full page on this topic, we can just expand the Know your reader paragraph in the content guidelines page a bit further.

[pavlenex]

Is it supposed to be linked to from the 'Contribute' section, and be listed in the side nav?

@danielnordh Yes, I haven't done any navigation additions yet it seems.

I also feel however, that as a community we are likely to create content that is relevant, and needed, for end users.

I agree, I assume that's what we meant with Bitcoiners1 persona?

@danielnordh if you have any concrete ideas, feel free to take over or suggest them, I just copy-pasted the work from Google Doc so we can keep the ball rolling, it needs a bit more work that's for sure.

[pavlenex]

Considering condensing this for now to a simple paragraph in the https://bitcoin.design/guide/contribute/content-guidelines/#speak-to-the-reader since there's no major consensus to proceed with this in-depth for now. It's getting clearer at this point that we write for designers, developers, and sometimes even users who can benefit from itit.

[GBKS]

@pavlenex I created a PR with that minor update to the "Know your reader" paragraph in the "Content guidelines" page. See #263.

Let's get some comments on whether that minor update is enough or we need this bigger page. I'm voting for the minor update.

This audience definition is just for the guide (IMHO). If we do workshops or other projects, they can have other audiences, whether that's a subset or a different group of people. So I'd keep this one fairly simple.

[pavlenex]

This is literally copy-pasted version of this Google Document.
The goal of this PR is to kick things off, lay out the structure and engage contributors into filling the gaps.

Feel free to suggest edits, comment on the structure, etc. This is a very very rough draft.

Once fully polished:
Closes#51

[GBKS]

Thanks @pavlenex for breathing life back into this one. This originally came up, IIRC, from a question by @ConorOkus. I believe it's also relevant to the discussions here, about the backup page speaking to the end-user vs a product builder.

[danielnordh]

Is it supposed to be linked to from the 'Contribute' section, and be listed in the side nav?
I can't find a link to the page.

I think the content of that doc is directionally correct (we are not making the guide for end users, and there are a few personas in that group). It is not written for general consumption however, so a copy and paste might need a fair amount of cleanup.

I also feel however, that as a community we are likely to create content that is relevant, and needed, for end users.
So it remains a question where that content should go.

• Sub-resources: bitcoin.design/resources/backups etc.
• Sub-domains: backups.bitcoin.design
• Separate microsites: bitcoinbackups.org, selfcustody.org, bitcoinforbeginners.org ...

[GBKS]

@danielnordh try this link here.

Looks like links on PR preview pages are now messed up and always link to bitcoin.design instead of keeping you on that preview domain. A side effect of fixing the canonical URLs. Will have to review this.

[GBKS]

If we don't want to have a full page on this topic, we can just expand the Know your reader paragraph in the content guidelines page a bit further.

[pavlenex]

Is it supposed to be linked to from the 'Contribute' section, and be listed in the side nav?

@danielnordh Yes, I haven't done any navigation additions yet it seems.

I also feel however, that as a community we are likely to create content that is relevant, and needed, for end users.

I agree, I assume that's what we meant with Bitcoiners1 persona?

@danielnordh if you have any concrete ideas, feel free to take over or suggest them, I just copy-pasted the work from Google Doc so we can keep the ball rolling, it needs a bit more work that's for sure.

[pavlenex]

Considering condensing this for now to a simple paragraph in the https://bitcoin.design/guide/contribute/content-guidelines/#speak-to-the-reader since there's no major consensus to proceed with this in-depth for now. It's getting clearer at this point that we write for designers, developers, and sometimes even users who can benefit from itit.

[GBKS]

@pavlenex I created a PR with that minor update to the "Know your reader" paragraph in the "Content guidelines" page. See #263.

Let's get some comments on whether that minor update is enough or we need this bigger page. I'm voting for the minor update.

This audience definition is just for the guide (IMHO). If we do workshops or other projects, they can have other audiences, whether that's a subset or a different group of people. So I'd keep this one fairly simple.

[pavlenex]

This is literally copy-pasted version of this Google Document.
The goal of this PR is to kick things off, lay out the structure and engage contributors into filling the gaps.

Feel free to suggest edits, comment on the structure, etc. This is a very very rough draft.

Once fully polished:
Closes#51

[GBKS]

Thanks @pavlenex for breathing life back into this one. This originally came up, IIRC, from a question by @ConorOkus. I believe it's also relevant to the discussions here, about the backup page speaking to the end-user vs a product builder.

[danielnordh]

Is it supposed to be linked to from the 'Contribute' section, and be listed in the side nav?
I can't find a link to the page.

I think the content of that doc is directionally correct (we are not making the guide for end users, and there are a few personas in that group). It is not written for general consumption however, so a copy and paste might need a fair amount of cleanup.

I also feel however, that as a community we are likely to create content that is relevant, and needed, for end users.
So it remains a question where that content should go.

• Sub-resources: bitcoin.design/resources/backups etc.
• Sub-domains: backups.bitcoin.design
• Separate microsites: bitcoinbackups.org, selfcustody.org, bitcoinforbeginners.org ...

[GBKS]

@danielnordh try this link here.

Looks like links on PR preview pages are now messed up and always link to bitcoin.design instead of keeping you on that preview domain. A side effect of fixing the canonical URLs. Will have to review this.

[GBKS]

If we don't want to have a full page on this topic, we can just expand the Know your reader paragraph in the content guidelines page a bit further.

[pavlenex]

Is it supposed to be linked to from the 'Contribute' section, and be listed in the side nav?

@danielnordh Yes, I haven't done any navigation additions yet it seems.

I also feel however, that as a community we are likely to create content that is relevant, and needed, for end users.

I agree, I assume that's what we meant with Bitcoiners1 persona?

@danielnordh if you have any concrete ideas, feel free to take over or suggest them, I just copy-pasted the work from Google Doc so we can keep the ball rolling, it needs a bit more work that's for sure.

[pavlenex]

Considering condensing this for now to a simple paragraph in the https://bitcoin.design/guide/contribute/content-guidelines/#speak-to-the-reader since there's no major consensus to proceed with this in-depth for now. It's getting clearer at this point that we write for designers, developers, and sometimes even users who can benefit from itit.

[GBKS]

@pavlenex I created a PR with that minor update to the "Know your reader" paragraph in the "Content guidelines" page. See #263.

Let's get some comments on whether that minor update is enough or we need this bigger page. I'm voting for the minor update.

This audience definition is just for the guide (IMHO). If we do workshops or other projects, they can have other audiences, whether that's a subset or a different group of people. So I'd keep this one fairly simple.