We Buy Ideas
============


STATUS
------
PLACEHOLDER / DEVELOPMENT REQUIREMENTS


FORM
----

Name:
    We Buy Ideas

Form Directory:
    /we-buy-ideas/

Proposed Database Table:
    form_we_buy_ideas

Database Field Prefix:
    wbi_


IMPORTANT
---------

The proposed database information above is documentation only.

This communications scaffolding DOES NOT create the database table.

The actual table, columns, indexes, relationships, and SQL must be designed
and reviewed when this form is implemented.


EMAIL TEMPLATES
---------------

user.txt
    Confirmation/response sent to the person submitting the form.

admin.txt
    Notification sent to configured administrator(s).


SMS/TEXT TEMPLATES
------------------

Equivalent placeholder templates exist under:

    /communications/text/we-buy-ideas/

SMS/Text functionality is NOT currently implemented.


COMMON REPLACEMENT FIELDS
-------------------------

    [first_name]
    [last_name]
    [company_name]
    [email]
    [phone]
    [address]
    [city]
    [state]
    [domain_name]
    [submission_id]
    [date]
    [time]
    [date_time]


FORM-SPECIFIC REPLACEMENT FIELDS
--------------------------------

    [user_id]
    [idea_title]
    [idea_description]
    [message]
    [created]


POSSIBLE ADMINISTRATOR ACTION FIELDS
------------------------------------

    [view_submission_url]
    [edit_submission_url]
    [mark_junk_url]
    [respond_url]

ALL protected administrator action links require authenticated administrator
login.

The action URL/token itself NEVER grants authorization.


FUTURE RESPONSE EMAILS
----------------------

    Additional response templates may be defined later.


DATABASE TODO
-------------

When this form is developed:

1. Review the proposed table name:
       form_we_buy_ideas

2. Review the proposed field prefix:
       wbi_

3. Determine required columns.

4. Consider:
       - Primary ID
       - User ID where applicable
       - Domain ID where applicable
       - Domain name where applicable
       - Customer/contact information
       - Form-specific values
       - Message
       - Status
       - Source
       - IP address
       - User agent where useful
       - Created date/time
       - Updated date/time
       - Internal notes

5. Determine indexes.

6. Determine relationships.

7. Review SQL before creating the table.


FORM DEVELOPMENT TODO
---------------------

When this form is developed:

1. Create/review database table.
2. Create form HTML.
3. Create server-side submission handler.
4. Add server-side validation.
5. Add CSRF protection.
6. Add spam/bot controls.
7. Add database saving.
8. Add success handling.
9. Add error handling.
10. Map common replacement fields.
11. Define form-specific replacement fields.
12. Build user email.
13. Build administrator email.
14. Configure administrator recipient(s).
15. Configure From and Reply-To.
16. Build response templates where required.
17. Build authenticated administrator actions where required.
18. Build communication logging.
19. Test standalone form.
20. Test Corporate Website include.
21. Test Geo-Network include.
22. Test user email.
23. Test administrator email.
24. Test multiple administrator recipients where required.
25. Review before production.


TEMPLATE RULES
--------------

Templates contain CONTENT and [replacement_fields] only.

Do NOT put the following in templates:

- PHP
- SQL
- Credentials
- Passwords
- Authentication logic
- Recipient lookup logic
- Action-token logic
- Sending logic


REFERENCE
---------

See:

/communications/README.txt

/communications/REPLACEMENT-FIELD-STANDARDS.txt

/communications/actions/README.txt

/communications/config/README.txt

/communications/logs/README.txt