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

Form for community mailing list #229

Closed
leecalcote opened this issue Dec 23, 2021 · 5 comments · Fixed by #234
Closed

Form for community mailing list #229

leecalcote opened this issue Dec 23, 2021 · 5 comments · Fixed by #234
Assignees

Comments

@leecalcote
Copy link
Member

This one was really for me to create a Google Group mailing list, which I believe we have now (see the mailing list section on the main page). Yes, you're right - we essentially want the same thing that we have on amp-spec.io and meshery.io. We essentially have that now, but are missing two things:

  1. a text field to receive visitor's email address, so that they can subscribe to the community mailer. Example - https://smp-spec.io#subscribe
  2. a formatting issue on https://getnighthawk.dev/subscribe. Margin is needed to separate the nav bar and prevent overlap:

Screen Shot 2021-12-23 at 10 45 59 AM

Originally posted by @leecalcote in #44 (comment)

@Abhijay007
Copy link
Contributor

I want to work on this issue, please assign this issue to me !!

@theBeginner86
Copy link
Member

@Abhijay007 🚀

@Abhijay007
Copy link
Contributor

2022-01-03.04-20-48.mp4

@leecalcote I am done with the formatting, do it need to add anything else? can a open a pr for this now?

@leecalcote
Copy link
Member Author

Looks pretty good, @Abhijay007. Yes.

Let's change our working structure to: when you're ready for feedback, pop open a PR. 👍

@Abhijay007
Copy link
Contributor

Looks pretty good, @Abhijay007. Yes.

Let's change our working structure to: when you're ready for feedback, pop open a PR. 👍

ok

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

Successfully merging a pull request may close this issue.

3 participants