Milestone: Vac.dev public repositioning

oskarth commented 2 years ago

Problem

As we are moving from just focusing on just Waku/secure messaging to that being one specific project, we want to update our public positioning of Vac. This increases clarity for ourselves as well as other people who run into us for the first time.

This was a topic during offsite. This milestone is about making sure we do a solid pass over all our relevant public positioning.

Scope

Basic touch on main public venues. Specifically places where Vac is talked about as doing "secure messaging" only.

List of issues:

[x] Internal clarity during offsite
[x] Site: https://github.com/vacp2p/vac.dev/issues/80
[x] Site: https://github.com/vacp2p/vac.dev/issues/81
[x] Site: https://github.com/vacp2p/vac.dev/issues/82
[ ] Site: https://github.com/vacp2p/vac.dev/issues/73 (possibly out of scope but nice to include here)
[ ] Update Twitter with logo/tagline
[ ] Update Github profile with logo/tagline
[ ] Create basic .github/about.md to link to nwaku etc
[ ] rfc.vac.dev
[ ] Vac book update
[ ] Update new site https://staging.vac.dev/ to vac.dev
[ ] Tweet out new site

NOTE: Scope not fixed yet - probably more issues.

Risks and uncertainty

Need to define more clear subset for when this work is "done". Otherwise risk work keeps dragging out.

Acceptance criteria

Lists above, and we are happy with how we are presenting ourselves beyond just secure messaging.

Out of scope

Design changes (e.g.)

Notes and links

See offsite notes for details.

Future steps

Possibly design tweaks and write-up.

oskarth commented 2 years ago

We also want a place to put papers.

Publications -> Blog and papers
Libraries? -> Repos

fryorcraken commented 2 years ago

Is there a decision on the tag line?

oskarth commented 2 years ago

@fryorcraken Under https://staging.vac.dev/ it is currently Vac - Communication & Privacy - did Vac - Communication, Privacy, Etc before but ended up with too many Etc so trying this out

vacp2p / vac.dev