You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that in order to embed the form (as opposed to just link out to it) I would need someone to pull code from the Google form editor (via Send > HTML ("<>" tab) > copy the snippet). Who has this access?
There's already a link to the form on the Get Involved page. And there's going to be a link to the bug report form in a persistent "warning" header on every page (Issue 104). This contact page feels redundant. Is the idea just to collect all forms in one place for people who are just scanning the site for a "Contact" link?
Given that context, I'm leaning toward including it in the footer, in order to not clutter the header. I'm open to thoughts/context!
@jaedoak Yeah, the idea is that the links get pretty buried and people who need it expect to find it quickly. Footer makes sense to me.
As for the embed, I think you should have access. It lives in the shared drive (I think under Project Management > Engagement or something similar...I don't remember the subfolder). Lemme know if you can't find it.
Description
There are a number of reasons a visitor might want to contact the FPS team but this isn't easily findable info.
Potential solution
Add a contact page, either to the global nav or footer, that embeds the current FPS interest form and includes a link to the bug report form.
The text was updated successfully, but these errors were encountered: