Thanks for the PR :)
I was thinking about this, and I wonder if we should have both. There are different user stories really, and the postorius link could be a nice call to action.
Using the...
As a <role> I can <capability>, so that <receive benefit>
...user story format, we could have...
As a person who is interested in 57 North I can sign up for the mailing list, so that I can get updates on 57North via email.
...and...
As a person who is curious about the mailing list I can see what people mail about, so that I can see if I want to sign up.
We could have something like...
Mailing lists:
* Announce: [view] or [signup]
* Discus: [view] or [signup]
...and that'd cater for both user stories, and also be a bit of a call-to-action for sign-up.
I also think it is worse, but it is a mailman issue more than anything. Mailman should have the subscribe link anywhere there is a sign up link. You suggestion is fine by me
Hey @adventureloop
Thanks for the PR :) I was thinking about this, and I wonder if we should have both. There are different user stories really, and the postorius link could be a nice call to action.
Using the...
As a <role> I can <capability>, so that <receive benefit>
...user story format, we could have...As a person who is interested in 57 North I can sign up for the mailing list, so that I can get updates on 57North via email.
...and...As a person who is curious about the mailing list I can see what people mail about, so that I can see if I want to sign up.
We could have something like...
...and that'd cater for both user stories, and also be a bit of a call-to-action for sign-up.
The current mail kitty link...
The postorius link...
At the moment the footer looks like...