{"id":455,"date":"2023-01-30T18:50:42","date_gmt":"2023-01-30T18:50:42","guid":{"rendered":"https:\/\/in.nau.edu\/naugo\/?page_id=455"},"modified":"2026-01-30T20:05:50","modified_gmt":"2026-01-30T20:05:50","slug":"policies","status":"publish","type":"page","link":"https:\/\/in.nau.edu\/naugo\/policies\/","title":{"rendered":"Policies & Guidelines"},"content":{"rendered":"

NAUgo<\/em> Policies & Guidelines<\/h3>\n
\n\n
\n \n
\n
1.1 ITS Website Policies Accordion Closed<\/span><\/h4>\n <\/span>\n <\/div>\n <\/a>\n
\n \n\n
NAUgo<\/em> adheres to all policies outlined in the following ITS documents…<\/p>\n
\n
Website Creation & Usage<\/a><\/li>\n
Website Procedures<\/a><\/li>\n<\/ul>\n<\/body><\/html>\n\n <\/div>\n<\/div>\n\n\n
\n \n
\n
1.2 App Content Guidelines Accordion Closed<\/span><\/h4>\n <\/span>\n <\/div>\n <\/a>\n
\n \n\n
One Source:<\/strong> Content on the NAUgo<\/em> app will not be a duplication of NAU website content. If there is information on a NAU website that a client would like to appear on the app, it must be done via iFrame, Cards of External Content, or External HTML content blocks.<\/p>\n
Permanent Content:<\/strong> In order to qualify for a screen or collection of screens, the department or organization must serve a majority of the appropriate student population and meet the following criteria:<\/p>\n
\n
Offers transactional tools for the student, offering convenience (example: Cline Library);<\/li>\n
Offers multiple events throughout the year; or<\/li>\n
Offer brief information about services accompanied by actionable links (phone, website, email).<\/li>\n<\/ul>\n
Permanent screens cannot<\/strong> be a replication of NAU.edu website content.<\/p>\n
All permanent requests are approved by the NAUgo<\/em> steering committee.<\/p>\n<\/body><\/html>\n\n <\/div>\n<\/div>\n\n\n
\n \n
\n
1.3 Push Notification Guidelines Accordion Closed<\/span><\/h4>\n <\/span>\n <\/div>\n <\/a>\n
\n \n\n
Any University Partners requesting a push notification sent out via NAUgo<\/em> to promote a NAU event must submit that event to the NAU Events Calendar by the deadline. If the event is not submitted, the NAUgo<\/em> events administrator will make the decision if the event appears in the app.<\/p>\n
Push notifications are used sparingly, and all requests are reviewed by the appropriate team: Many push notifications are approved by the Student Affairs Campus Life Communications team; others are approved by Academic Affairs or the NAUgo<\/em> steering committee.<\/p>\n
\n
Benefit<\/strong>: The NAUgo<\/em> events module is accessed over 100,000 time per academic year. If a department has an event, the NAUgo<\/em> events module will reach more of our students, faculty, and staff than any other digital production.<\/p>\n
\n
Implementation<\/strong>:<\/p>\n
\n
To submit an event, please see the NAU Events Calendar Submitting Events<\/a> page.<\/li>\n
To request a push notification via NAUgo<\/em>, please visit the Content Request Form<\/a>.<\/li>\n<\/ul>\n<\/body><\/html>\n\n <\/div>\n<\/div>\n\n\n
\n \n
\n
1.4 Feature Event Guidelines Accordion Closed<\/span><\/h4>\n <\/span>\n <\/div>\n <\/a>\n
\n \n\n\n\n\n\n
\n
\n
\n \n
\n
\n Submission Criteria Tab Open<\/span>\n <\/h4>\n <\/div>\n <\/a>\n <\/li>\n
\n \n
\n
\n Benefits Tab Closed<\/span>\n <\/h4>\n <\/div>\n <\/a>\n <\/li>\n
\n \n
\n
\n Implementation Tab Closed<\/span>\n <\/h4>\n <\/div>\n <\/a>\n <\/li>\n
\n \n
\n
\n Content Guidelines Tab Closed<\/span>\n <\/h4>\n <\/div>\n <\/a>\n <\/li>\n <\/ul>\n \n
\n \n
\n
Submission Criteria Accordion Open<\/span><\/h4>\n <\/span>\n <\/div>\n <\/a>\n
\n \n\n\n
Feature Events may be subject to approval by the NAUgo<\/em> Steering Committee.<\/strong><\/p>\n
Any University Partners requesting a feature event to be published via NAUgo<\/em> to promote a NAU event(s) must submit that event(s) to the NAU Events Calendar by the deadline.<\/p>\n
Featured Events will be limited to events which are newsworthy or potentially of interest to the majority of the users in the current experience. Decisions about what to include in Featured Events rests with the Student Affairs Campus Life Communications team, aided by the following criteria:<\/p>\n
\n
The event(s) advertised in the Featured Event should be relevant to the broader community that is being served by the experience (examples include Welcome Week, Homecoming, Veterans Week)<\/li>\n
The Featured Event must be relevant to the experience (we wouldn’t include an on-campus career fair in the Online experience, but might for the Flagstaff experience)<\/li>\n<\/ul>\n
Requests that meet the criteria will be prioritized based on institutional priorities.
\n<\/p>\n\n <\/body><\/html>\n\n <\/div>\n<\/div>\n\n \n
\n \n
\n
Benefits Accordion Closed<\/span><\/h4>\n <\/span>\n <\/div>\n <\/a>\n
\n \n\n\n
Feature Events may be subject to approval by the NAUgo<\/em> Steering Committee.<\/strong><\/p>\n
The NAUgo<\/em> Feature Event accessed via the NAUgo<\/em> home screen will be seen by 10s of thousands of our students, faculty, and staff, more than any other digital production.
\n<\/p>\n\n <\/body><\/html>\n\n <\/div>\n<\/div>\n\n \n
\n \n
\n
Implementation Accordion Closed<\/span><\/h4>\n <\/span>\n <\/div>\n <\/a>\n
\n \n\n\n
Feature Events may be subject to approval by the NAUgo<\/em> Steering Committee.<\/strong><\/p>\n
\n
To submit an event, please see the NAU Events Calendar Submitting Events<\/a> page.<\/li>\n
To request a feature event on NAUgo<\/em>, please visit the Content Request Form<\/a>.<\/li>\n<\/ul>\n\n\n <\/body><\/html>\n\n <\/div>\n<\/div>\n\n \n
\n \n
\n
Content Guidelines Accordion Closed<\/span><\/h4>\n <\/span>\n <\/div>\n <\/a>\n
\n \n\n\n
Feature Events may be subject to approval by the NAUgo<\/em> Steering Committee.<\/strong><\/p>\n
Website vs. Mobile App Text Content<\/h5>\n
Text content on websites is consumed by users in a very different way than on mobile apps.<\/p>\n
NAU.edu is primarily used to provide detailed information and was designed to be viewed in a wide, desktop browser format. This is an opportunity to provide blocks of content such as historical context, emotive language, and longer descriptions.<\/p>\n
NAUgo<\/em> is used to perform tasks and provide interactive functionality. Users do not expect that they will spend a lot of time reading paragraphs of content on the app (and they will simply skip over it without reading it!). They use NAUgo<\/em> to get more transactional data such as time, date, and location of an event. Therefore, we recommend that large blocks of text be reserved for the website and your app text content be brief and to the point.<\/p>\n
Text Content Tips & Tricks<\/h5>\n
Want your content to be easily consumed by your users?<\/p>\n
Instead using a comma separated list in a paragraph, try a bulleted list. Bulleted lists can help readers digest content quickly and efficiently. Readers may also perceive the bullets as shortcuts to important information.<\/p>\n
Visual content is a good way of breaking up text content. Using images, videos, or graphics to break up text content provides more visual interest and makes text feel less intimidating.<\/p>\n
Let the NAUgo Design Team Help!<\/h5>\n
We know that you are the expert in planning your event, not in the finer points of app content design. But, don’t worry, our expert designers are here to help!<\/p>\n
We want to promote your event in the best way possible for our users. When we receive content that is not easily transformed to an app screen, we may need to make some changes while retaining the spirit of the original message. This may mean that we have to make some small changes so that we can stay within our brand guidelines. But NOTHING goes live without your final approval. Typically, compromises are made on both sides yielding the best result.<\/p>\n\n\n <\/body><\/html>\n\n <\/div>\n<\/div>\n\n <\/div>\n\n<\/body><\/html>\n\n <\/div>\n<\/div>\n\n","protected":false},"excerpt":{"rendered":"
NAUgo Policies & Guidelines<\/p>\n","protected":false},"author":209,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_relevanssi_hide_post":"","_relevanssi_hide_content":"","_relevanssi_pin_for_all":"","_relevanssi_pin_keywords":"","_relevanssi_unpin_keywords":"","_relevanssi_related_keywords":"","_relevanssi_related_include_ids":"","_relevanssi_related_exclude_ids":"","_relevanssi_related_no_append":"","_relevanssi_related_not_related":"","_relevanssi_related_posts":"","_relevanssi_noindex_reason":"","ring_central_script_selection":"","footnotes":""},"class_list":["post-455","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/in.nau.edu\/naugo\/wp-json\/wp\/v2\/pages\/455","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/in.nau.edu\/naugo\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/in.nau.edu\/naugo\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/in.nau.edu\/naugo\/wp-json\/wp\/v2\/users\/209"}],"replies":[{"embeddable":true,"href":"https:\/\/in.nau.edu\/naugo\/wp-json\/wp\/v2\/comments?post=455"}],"version-history":[{"count":64,"href":"https:\/\/in.nau.edu\/naugo\/wp-json\/wp\/v2\/pages\/455\/revisions"}],"predecessor-version":[{"id":1232,"href":"https:\/\/in.nau.edu\/naugo\/wp-json\/wp\/v2\/pages\/455\/revisions\/1232"}],"wp:attachment":[{"href":"https:\/\/in.nau.edu\/naugo\/wp-json\/wp\/v2\/media?parent=455"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}