Contributing to an individual Luggage feature requires a bit of setup before you are ready to create a pull request. You will need to fork the desired Luggage feature and create pull requests to the development branch from there. There exists already comprehensive documentation to help you understand Luggage's Git architecture. We will be following the same method as described there, but with an individual Luggage feature. So let's get started!
Mobile-First look-and-feel compliant with ISU standards and adapts to mobile devices.
Latest Technology with HTML 5 and CSS 3.
Free and open-source.
How to set up Luggage within a Wordpress root:
- Separate the DocumentRoot(s):
Luggage sites should be installed outside of the wordpress document root. For example, on one LAS web server, we are doing this in /srv/luggage/<deptcode>/<site>.
- The Virtualhost should be modified to add an alias for the site under (and yet outside of) the wordpress installation.
# Drupal Luggage Aliasses
Anonymous user a user who is not logged in to the website. This user only has the ability to view published content.
Authenticated User has several permissions to add content such as a page, news article, event, etc., however, this user may only edit their own content.
Content Editor has the ability to add content and edit all content. This user may also publish and unpublish any content on the site.
As of Luggage 3.2.2 we've made it easier to query Luggage for its version number. There are two ways to get the version number: on the site status page, and via drush.
Version from status page
admin/reports/status and find the version in the list of status reports
The web team has developed a new Podcast feature! This feature allows for easy podcast playback along with the ability to incorporate related links and images for your podcast subscribers. Learn more!