Currently, this page is for information only.
The Donate menu item could link directly to a donation form similar to this one instead of the present page.
However, it may desirables to use a Donation page to provide additional information about the tax deductibility of the donation, that a donation receipt will be sent automatically to the email address entered on the form, what AFORR will do with the money, etc.
We also could have separate buttons on this page to Donate and to pay Membership Dues, like this example.
Should "Sign up or Donate" be a single or two separate menu items?
How should these link to a "Sign up for AFORR email alert" mini-form embedded on the home page or another page?
Or should they go to (a) separate page(s) dedicated to Sign up and/or Donations?
What fields and information should be included on the 'Membership Form?
Would it make sense to collect the dues with that form?
Have a separate printable form that can be snail mailed with a personal check?
Are we intending to produce sporadic or regular hardcopy newsletters going forward
or just have a dedicated "Newsletter" page on the website?
Many groups that don't publish a respectably lavish magazine, have stopped producing hardcopy newsletters, but most of those will print out the web-pages and snail mail them to members who explicitly ask for it (and in some cases pay a few extra $ for that).
Additionally, we specify the "Option to send a message via email."
If we spread menu items, buttons, and links for these various interactive components throughout the website, it may be difficult for visitors to discovere the 'correct' one for doing what they intend to communicate, and they may try do use another one for some purpose that it isn't intended for.
Do we want to put all these capabilities on a single page?
If so, it would not be a problem to have links and buttons spread across various content areas to catch visitor's attention and to direct them to a user-friendly interface for the desired purpose.
We may create a form that the user can configure through radio buttons and/or check boxes to show the input fields that are appropriate and necessary.
Do we intend to let members, or even non-member individuals, register for an online account on our website?
It makes little sense if we do not provide some 'added-value' features. Otherwise it generates maintenance overhead only with no compelling benefit to the user and us. Most casual website visitors hate to create an account and to have to deal with a login and password, even if it's free!
Do we want a "Maintenance" menu item or a button, on the public part of the website, for us to log in?
(That may be given any other name.)
But is it even necessary?
If it's just intended for a small number of authorized individuals,
login buttons or menu items add unnecessary clutter and are easy targets for wannabe hackers or incessant bots that eat up bandwidth and energy.
Those of us who need to log in may as well use an unpublished URL extension, such as aforr.org?dx87