Prior to this month’s meeting, the team requested participants send in questions ahead of time so the conversation could be somewhat focused, at least to begin with.<\/p>\n
<\/p>\n
<\/p>\n
September 30th<\/strong> is the target launch date for several sites as well as major integrations. These integrations include the much anticipated Faculty\/Staff directory.<\/p>\n The team needs to prioritize among the sites that have already started. We have to show measurable progress to university leadership about progress on sites. We will contact you with more information soon. We will ask for your priorities within your areas.<\/p>\n <\/b>Q. How do we know what\u2019s in the queue?<\/b><\/p>\n A. This list is being finalized now.<\/p>\n Begin with moving pages one-to-one from Ektron to WordPress.<\/p>\n It’s important to remember that both DIY and supported site migrations need information architecture work. Depending on the group, a lighter approach to the Information Architecture work can help provide the basic guidance to get your site launched.<\/p>\n We\u2019re testing a new approach to theme updates. This new approach will keep development and launch to a regular schedule. Most of the shortcodes you learned in training are still available. Most of the changes that we are seeing now are in layout & styling.<\/p>\n If you have a specific concern that hasn\u2019t yet been addressed, let us know.<\/p>\n We could use help from the WUG to test release candidates for theme updates. We don\u2019t yet have a plan or process for this, but if you\u2019re interested in helping us test, let us know, and we\u2019ll contact you when we\u2019re ready for your help.<\/p>\n This integration is on the current quarter\u2019s list of integrations. We\u2019ll tap into data from both the NAU directory and Faculty 180, which houses faculty profile info. We are aware that directory information is often out of date, which stems from each department\u2019s ownership of their own directory data. As we have been working on this integration, we\u2019ve identified issues that are being circulated up to leadership.<\/p>\n Q. Will a person\u2019s info come from the department\u2019s list of, for example, phone numbers, or will it come instead from the information that each individual controls?<\/strong><\/p>\n A.\u00a0The information will come from the NAU Directory tables. Departments may update this information through the Directory Maintainer tool. Each department has a directory administrator. The solution does not differ for Faculty and Staff. The web team is not the team responsible for data governance of either Faculty 180 or directory data.<\/p>\n Q. Should we book appointments with Marketing to get head shot photos of our unit members? Will those images be used for the directory pages on our web site? We don\u2019t want to send our people for photos now if we\u2019re going to have to send them for some other photos later.<\/strong><\/p>\n A. We don’t have a confirmed process for this. Check with Marketing on specific photography questions.<\/p>\n For now, submit request to create a form to the PubOps team. By Oct. 1, Gravity Forms will be more widely available and well documented.\u00a0<\/span>Eventually we\u2019ll create some documentation, training, and perhaps videos so people can eventually do self-serve form building.\u00a0<\/span>Will eventually develop some form templates for common types of forms.<\/span><\/p>\n Q. Will Gravity Forms replace anything we\u2019ve already built in OnBase?<\/b><\/p>\n A. We don\u2019t have a good way to turn OnBase stuff into Gravity Forms. Best solution for now is to just link to existing OnBase forms.<\/span><\/p>\n Q. What does a Gravity Form generate?<\/b><\/p>\n A. These forms can send out email notifications. Content submitted through the forms can\u00a0<\/span>also be stored in a WordPress database and can be exported as CSV.<\/span><\/p>\n Q. What about security of certain kinds of forms (example: complaint forms)? Who can see them in the WP database?<\/b><\/p>\n A. If you have that kind of need, let the PubOps team know. We can create special roles for you to limit who has access to secure or private data.<\/span><\/p>\n
\n
\nTips for getting started<\/h2>\n
\nUpdates to the WordPress theme<\/h2>\n
\nFaculty & staff directory<\/h2>\n
\n
\n
\nForms<\/h2>\n
GravityForms features<\/b><\/h3>\n
\n
\n
\n
\n
\nCalendars<\/h2>\n