-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add the newsletter form page into the website #79
Comments
I think that placement is too central. I like how https://bitcoinops.org does it with a form in the footer and at the top of a secondary page where we list past issues. @aassoiants or others have opinions? |
I see. Please consider the fact that tldr homepage and others pages gather so much information that the footer is deep and hard to reach. |
I think a secondary page with the archive of past issues makes the most sense |
Ok I am looking forward to see the design of that page and this one too #64 . |
We have the newsletter page now https://tldr.bitcoinsearch.xyz/newsletter |
In terms of UI, i think the TLDR Newsletter page should look identical to the Bitcoin Optech Newsletter page. That is, each Newsletter release is discrete (by date), clickable, and quickly summarized. What will the content of the newsletter be? Will it be a list of individual summarized emails? Will there be a summary for the overall Newsletter issue? It could be fun to have an overall summary - what's been discussed since the last issue. And then a "This Month in Bitcoin History," "New Posts," and "Ongoing Discussions" section |
Context: In order to gather email addresses that will be used as recipients of the tldr newsletter, a form has been set up.
Solution: The form needs to be added in the TLDR website, between the summaries and the active discussions.
Link of the form: https://mailchi.mp/sensatoshi/bitcoin-tldr-newsletter
Desired behavior: The form should disappear as soon as the user has subscribed.
Desired position:
The text was updated successfully, but these errors were encountered: