Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refresh website branding #19

Open
strugee opened this issue Aug 12, 2017 · 3 comments
Open

Refresh website branding #19

strugee opened this issue Aug 12, 2017 · 3 comments

Comments

@strugee
Copy link
Member

strugee commented Aug 12, 2017

I've been thinking recently about how we present the project. The current website is a lot better than it used to be, but it's still not great and doesn't do a good job of explaining the project.

I think we should focus on three main things that differentiate us from other ActivityStreams/(future) ActivityPub projects:

  • Security - we innovate on this space with things like shipping a restrictive systemd file, and we have additional enhancements planned like automatic HTTPS (Automatic Let's Encrypt support pump.io#1259) and chroot jails on by default (chroot jail pump.io#1258)
  • Great admin experience - it's dead-simple to install and set up because of npm and good MongoDB packaging (even easier than Wordpress' 5-minute install, which is only 5 minutes if you already have a database, web server, etc.). We're also always looking to make this better with things like zero-downtime restarts (Investigate zero-downtime upgrades pump.io#1295)
  • Flexibility through open standards - the pump.io project has historically been deeply involved in the standards community (specifically AP derives from the pump.io API). We also drive new standards and explicitly track useful protocol extensions in our issue tracker. We should focus on how this makes us open and flexible, such that we can go beyond just "social network" usecases (i.e. solid, high-performance, generic ActivityStreams distribution)

Thoughts?

@strugee
Copy link
Member Author

strugee commented Nov 17, 2017

Evan notes in the meeting today that we should also find a way to incorporate slimness/speed into this.

@strugee
Copy link
Member Author

strugee commented Nov 17, 2017

<e_s_p> So another strength I like is that we build on the Web
<e_s_p> Like, not with plugins or modules, but with other web sites
<e_s_p> bridges, apps, etc.
<strugee> e_s_p: yeah, good point. will include some language about that in the standards item

@strugee
Copy link
Member Author

strugee commented Apr 4, 2018

Also would be nice to include something about the fact that we have pretty good compatibility/security support policies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant