TJ CSL
  • TJ CSL
  • Services
    • Ion
      • Development
        • Overview
        • Setup
          • Docker Setup
          • Vagrant Setup
        • Environment
        • Fixtures
        • PR Workflow
        • Style Guide
        • Maintainer Workflow
        • Repository Maintenance
        • Data Generation
      • Production
      • User Experience
        • User Interface
    • Director
      • Development
        • Vagrant Setup
        • PR Workflow
        • Style Guide
        • Maintainer Workflow
      • Production
    • Workstations
    • Signage
      • Setup
      • Administration
      • Monitoring
      • Troubleshooting
      • Experimental
        • IonTap
        • SignageAdmin
    • Remote Access
      • Setup
      • Administration
    • Cluster
      • FAQ
      • Setup
        • SSH Setup
      • Administration
      • Slurm
      • Slurm Administration
      • Borg
    • Printing
      • Setup
      • Troubleshooting
    • WWW
      • Administration
      • Sites
        • Web Proxy
      • Setup
      • Troubleshooting
    • Academic Services
      • Tin
      • Othello
        • Administration
        • Setup
  • Technologies
    • Web
      • Nginx
      • Django
      • PHP-FPM
      • Node.js
      • Supervisord
    • DBs
      • PostgreSQL
      • MySQL
    • Authentication
      • Passcard
        • GPG Usage
      • SSHD
        • SSH Passwordless Login
      • FreeIPA
    • Storage
      • NFS
      • Ceph
        • Setup
        • Backups
        • CephFS
    • Operating Systems
      • Ubuntu Server
      • AlmaLinux
      • Debian
    • Tools
      • Ansible
      • Slack
      • GitBook
      • GitLab
        • Setup
        • Updating
    • Virtualization
      • QEMU/KVM
      • Libvirt
    • Advanced Computing
      • MPI
      • Tensorflow
    • Networking
      • Netbox
      • Cisco
      • Netboot
      • DNS
      • DHCP
      • NTP
      • BGP
    • Mail
      • Postfix
      • Dovecot
    • Monitoring
      • Prometheus
      • Grafana
      • Sentry
      • Uptime Robot
  • Machines
    • VM Servers
      • Utonium
      • Blossom
      • Bubbles
      • Buttercup
      • Antipodes
      • Chatham
      • Cocos
      • Galapagos
      • Gandalf
      • Gorgona
      • Overlord
      • Waverider
      • Torch
    • Ceph
      • Karel
      • Stobar
      • Wumpus
      • Waitaha
      • Barrel
      • Valdes
    • HPC Cluster
      • Zoidberg
    • Borg Cluster
    • Compute Sticks
    • Other
      • ASM
      • Duke
      • Snowy
      • Sauron
      • Sun Servers
        • Altair
        • Centauri
        • Deneb
        • Sirius
        • Vega
        • Betelgeuse
        • Ohare
    • Switches
      • Core0
      • Xnor
      • Xor
      • Imply
    • UPS
    • History
      • 2008 Sun AEG
      • 2011 Sun Upgrades
      • 2017 VM Disaster
      • 2018 Purchases
      • 2018 Cephpocalypse
    • VLANs
    • Remote Management
      • iLO
      • LOMs
    • Understudy
      • Switch Configuration
      • Server Configuration
        • Setting Up the Operating System
        • Network Configuration
        • Saruman
        • Fiordland
  • General
    • Sysadmins List
    • Organization
    • Documentation
      • Security
      • Runbooks
    • Communication
      • Terminology
    • Understudies
    • Account Structure
    • Machine Room
    • Branding
    • History
      • Fridge
      • The Brick
  • Procedures
    • Data Recovery
    • Account Provisioning
    • tjSTAR
      • Tech Support
    • Onboarding
      • New Sysadmin Onboarding
  • Guides
    • VM Creation
    • sshuttle Usage
    • Linux Wifi Setup
    • VNC Usage
    • Password Changes
    • Sun Server RAID Configuration
  • Policies
    • Data Release Policy
    • Upgrade Policy
    • Account Policy
    • Election Policy
  • Obsolete
    • Arcturus
    • Chuku
    • Cray SV1 Supercomputer
    • Ekhi
    • Mihr
    • Moloch
    • Sol
    • Rockhopper
    • Kerberos
    • LDAP
    • Agni
    • Moon
    • Apocalypse
    • AFS
      • OpenAFS
      • Setup
      • Client Setup
      • Administration
      • Troubleshooting
      • Directory Structure
      • Backups
      • Cross-Cell Authentication
    • Observium
    • OpenVPN
Powered by GitBook
On this page
  1. General

Branding

PreviousMachine RoomNextHistory

Last updated 4 years ago

Style Guide

Logo and Typeface

Logos

tjCSL uses the flat TJ icon logo.

Alternatively, the wordmark logo can also be used.

The logo can be used together with the unabbreviated "Computer Systems Lab", as shown, but should not be used with the wordmark logo.

When using on a white background, the logo or text should be #484848.

The logo can also be used on the blue #0048AB background.

Type

The typeface is .

Body Text

Avoid using light weights because they are less readable. For most applications, the regular weight should be enough.

Use adequate line spacing to improve readability.

Using Bold Weights

For eyecatching material, use the extra-bold weight. This weight should not be used in applications, but can be used in promotional materials such as pamphlets and posters to draw attention. Text in this weight should be:

  • short

  • to the point

  • eyecatching

Do: - overlay on images - keep the message short - use color to increase contrast

Don't: - use for body text - have illegible line spacing

Color

The main CSL color is #0048AB.

Text should be #484848.

Naming Conventions

tjCSL

The computer systems lab should be referred to as "the tjCSL".

Do:

  • Add "the" when using "tjCSL" to refer to the location or organization (ex: "We visited the tjCSL").

Don't:

  • Capitalize "The" (ex: "We visited The tjCSL").

Do:

  • Lowercase the "tj". This provides a hierarchy between the "TJHSST" entity and the "CSL" entity.

  • This also provides consistent with other TJ programs, such as "tjSTAR" and "tjTODAY"

Don't:

  • Insert spaces "tj CSL"

Projects can be namespaced (for instance, on IRC):

tjcsl-ion, tjcsl-director

This is an instance in which "tjcsl" can be all lowercase. Generally, one should maintain the proper capitalization.

Ion

The student intranet is our flagship product.

Examples of how to use the name:

  • Ion

    • "We use Ion to sign up for eighth periods."

    • "Ion runs on servers in the machine room."

  • Projects associated with Ion

    • "IonTap"

    • "IonGlance"

Examples of misuse of the name:

  • Ion

    • "ION"

    • "Intranet"

  • Projects associated with Ion

    • "Ion Tap"

    • "IONGlance"

    • "ionGlance"

Note that there should be no spaces in the names of related projects (e.g. "IonTap" is correct, "Ion Tap" is not)

Open Sans