Files
www.gittip.com/templates/profile.html
Chad Whitacre e4692a690d Rationalize the CSS for nav
The box that's front and center in the visual design has three levels
for nav. Rather than classing all of these levels as "buttons" and
distinguishing them as "tips," "nav," and the one-off "rip," now we
class them all as "nav," and then use "level-1," etc. for the three
levels.
2013-03-08 00:43:09 -05:00

22 lines
857 B
HTML

{% extends "participant.html" %}
{% block head2 %}
<script src="/assets/{{ __version__ }}/profile.js"></script>
{% if user.ADMIN %}<script src="/assets/{{ __version__ }}/admin.js"></script>{% end %}
<script>$(document).ready(Gittip.initTipButtons)</script>
{% end %}
{% block heading %}<h2 class="top"><span>{{ hero }}</span></h2>{% end %}
{% block nav %}
{% if participant.id == user.id or user.ADMIN %}
<div class="nav level-2">
<h2>Navigation</h2>
{% set current_page = path.raw.split('/')[2] %}
{% set pages = [('/', 'Profile'), ('/giving/', 'Giving'), ('/history/', 'History'), ('/widgets/', 'Widgets')] %}
{% for slug, name in pages %}
<a href="/{{ participant.id }}{{ slug }}"><button{% if slug.strip('/') == current_page %} class="selected"{% end %}>{{ name }}</button></a>
{% end %}
</div>
{% end %}
{% end %}