-
Notifications
You must be signed in to change notification settings - Fork 2
Getting Started: For Officers
This tutorial builds upon what was introduced in Getting Started: For Members
As an officer your Admin menu will have more options than an ordinary member. This is because your account is part of the officers group. Most of these new options are to give you the ability to edit various resources that are used to populate the public facing website.
Note: If you are an officer and you do not see any of the sections described here please ask another officer to add you to the officer group
After creating an announcement you can create its printable label by clicking Create Announcement Label on the right hand side of its edit form. At the time of this writing this feature is not used for anything else but to created standardized announcement labels.
You should generally never have to modify groups. Upon being elected an officer a current officer should have added you to the officers group. All Users are part of the members group giving them the permissions described in Getting Started: For Members. At a minimum members should always have auth | user | Can change user and robocrm | robo user | Can change robo user giving them the ability to edit their own information.
In addition to the Member fields described in Getting Started: For Members officers can view all members and register new members.
Clicking on the button Add User in the upper-right hand corner of the Users page you will be brought to a form asking some basic information about the new member. Thanks to CMU's LDAP directory(and Scotty Labs API) all you need is the new member's Andrew ID and when you "tab" out of the username field the rest of the fields should become auto-populated if they are a CMU Student. If they are not a CMU student you must enter the remaining fields manually. If they are not auto-populated and the member is a CMU student please contact root.
The FAQ page is composed of ordered categories which are composed of ordered questions.
At the time of this writing the gallery is just used to display images on the front-page carousel. Images can be uploaded and have a title and description displayed on them using the provided fields. Images will not be displayed on the front-page unless the display field is set regardless of their ordering.
These are the links that are provided in the left-hand footer of the website.
Here you can edit officer information.
Note: This section is only used to provide officer information for the website & API. This list is independent of being part of the officers group which gives you the permissions listed in this tutorial.
The officer description field is what is displayed on an officer's detail page of the website. It's purpose is to allow new members to get a feel for who you are so it should be somewhat serious but also lighthearted.
The memo field is what is listed on your officer photo in the club. It should be short and likely not very serious. This field is not displayed on the public website.
To generate an officer label click the Create Officer Label button.
Here you can create a page from a rich text editor and/or raw HTML. At the time of this writing the only pages of this type are the 'Home' and 'About' pages.
Here you can upload and edit the posters listed on the posters section of the website.
Building upon what was described in the Getting Started: For Members officers have the ability to view all projects and edit a project's display field. If this field is set, the project will be displayed on the public website.
Here you can create redirects for Hackathon Signup Forms, shortened urls, etc.
Resources are otherwise known as "static resources". Here you can upload images, presentations, PDFs, etc that can be linked to from elsewhere on the website.
These are similar to Links which are displayed in the center of the public website's footer.
Here you can add and update sponsors.
Note: A sponsor should never be deleted. Instead, just uncheck active.
This controls what is displayed on the tshirts page and accessible through the tshirts API endpoint.