Giter VIP home page Giter VIP logo

psibeta's Introduction

psibeta

Website for the Psi Beta chapter of the national Theta Tau fraternity.

If you're reading this, you've probably been elected Webmaster! Congratulations! Webmaster is a great position, and requires only a little bit of work in the beginning or end of the semester.

Most of the website has been created using JSON so alot of it is just tedious copy pasting. Make sure you double check your commas though, JSON is a bit finicky and will crash if you misplace anything!

Tips: For ACTIVES: Please make sure to double check a master list with the scribe! This will be the most intensive page, and all officers/previous semester's officers will need to be adjusted accordingly, as well as moving alumni off the Actives page and adding the JI's.

I would have a secondary list (or screen) with all the new JI's names, majors, numbers, and pledge names.

Go through the list and for the previous semester's officers, add a letter to their officer title.

Have a list of the new officers and add letters to the offcer names.

The template for the ACTIVES.json is as follows: { "img": "353.jpg", "name": "Bryan Boucher", "pin": "353", "pledge_name": "Toofbrush", "pledge_class": "Chi Beta F'12", "major": "Electrical", "officer_letters": "TT! ZZ!" },

For ALUMNI: For the most part, all you really need to do is move the members from the actives tab to the alumni tab. The template is also literally the same.

For OFFICERS: For the most part, officers is also the same. Might help to have a seperate list to refer to for the new semester's officer's names, pins, pledge names, pledge classes, majors, and emails. Double letters are given when they are done with their position.

Template for Officer Position is as follows: { "img": "488.jpg", "name": "Kirtana Moorthy", "pin": "488", "pledge_name": "Lumbergh", "pledge_class": "Theta Gamma F'16", "major": "Electrical", "officer_letters": "U!", "email": "[email protected]", "position": "Outer Guard" },

The officer letters are as follows: Regent: X! Vice Regent: Y! Scribe: V! Treasurer: Z! Pledge Marshal: W! Corresponding Secretary: R! Outer Guard: U! Inner Guard: T! Webmaster: 0xDEADBEEF (This one can change, just make sure it's hex so A-F letters only)

For RUSH: Make sure to talk to the rush chairs and have this up IMMEDIATELY. This is the most important thing you should do and make sure you do this before everything else.

Template for Rush is as follows: { "type": "Info Session #1", "date": "8/31", "time": "5:00 PM", "location": "RLM 7.116", "gmaps": "https://goo.gl/maps/JNQn2Y1KTuM2" },

The google maps for each event does need to be updated if the events are in different locations. You can always move around events that'll be pretty common.

psibeta's People

Contributors

petitjeanluis avatar scascketta avatar cmkauff avatar yparekh39 avatar josephbae96 avatar mobuttahsmooth avatar khalidgit avatar pln324 avatar jmm9683 avatar mmeleen avatar

Watchers

James Cloos avatar  avatar  avatar  avatar  avatar  avatar

psibeta's Issues

Update repo to reflect UT hosting environment

The hosting environment that Cockrell provides is FUBAR, but for the time being, we have to use it. Certain resources cannot be loaded (.json have to be renamed them to .txt), and apparently have to be placed under the /includes/ directory.

Fix navbar on mobile screens

The navbar will collapse on mobile screens, but it doesn't expand when clicked. The position also needs to be fixed a bit.

Formatting on the website.

Morgan, Diana, and Michelle's formating within the members page is slightly longer(at least from a desktop view). I'm seeing 195x343px for most people and 195x367px for those three. It looks like the problem isn't with the picture, but with the caption.

Style member page

We need some styling on the members page. I think some basic styles to create a thumbnail (similar to this) for each member will do the job.

DRY up HTML

We have a lot of repetition in our HTML files for the head, navbar, and footer. If we were writing a dynamic application, it'd be easy to avoid this by using a framework's templating engine (like Jinja2), however this is static.

I think our best bet is to use HTML Imports as decreed by the W3C. All the other solutions seem a little hacky, and hard to understand for newbs. Using the polyfill from the Polymer team should solve compatibility issues.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.