Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/templates/zerver/navbar.html

173 lines
8.5 KiB
HTML
Raw Normal View History

notifications: Prompt user to enable desktop notifications. This is a two-step notifications process that will ask a user to enable notifications and if they click exit give them three options: 1. Enable notifications. 2. Ask later. 3. Never ask on this computer again. The first two are self-explanatory (ask later = next session it asks again). The third is captured and stored in localStorage and a check is done on page load to see whether or not notifications should be displayed. Commit modified heavily by Brock Whittaker <brock@zulipchat.com>. Fixes #1189.
2017-09-23 11:27:18 +02:00
<div id="panels">
<div id="desktop-notifications-panel" class="alert alert-info">
<span class="close" data-dismiss="alert" aria-label="{{ _('Close') }}">&times;</span>
<div data-step="1">
onboarding: Revise text in prompt to enable desktop notifications. Making the same point (that you can configure the notifications in settings) at both steps felt pushy. I think the first prompt is actually best kept to a minimum of words, so leave that one with just the ask. In the second step, try an active pitch. This could go either way, or be any number of other messages, but the settings line felt a little defensive to me, like it was suggesting that our notifications would be noisy and here's a way you can try to mitigate that. I think with our default settings (and in an org with mostly-reasonable humans, but even a large and busy one) they're actually not at all noisy; and if we learn of situations where that's not true, we'll work to fix that. So, try this line instead. A style note: I chose "your team" here to refer to the people the user communicates with in their organization. We consistently say either "organization" or sometimes "realm" for the concrete thing in the product that is the whole universe of streams and users, etc., that a given account lives in; but that feels too formal here. Conversely, one reason we don't say "team" for an organization is that it feels too cozy and small, more appropriate for 8 people who interact every day than for 80 or 8000 people; but this line is mainly about those 8 people even if the organization has 8000. There are some examples of this already in the codebase; see `git grep -w team`. i18n note: These passages of a couple of connected sentences should generally be marked for translation as one message, not several separate ones. That helps the translator be sure of the context so they can translate appropriately. For example, in the second prompt in this version, there's an implicit "because" relationship between the two sentences, and in some languages (I'm 90% sure this is true in Japanese), it would be weird to leave it implicit and the second sentence should contain the equivalent of "That's because".
2017-10-23 23:43:12 +02:00
{% trans %}Zulip needs your permission to
<a class="request-desktop-notifications alert-link">enable desktop notifications.</a>
{% endtrans %}
notifications: Prompt user to enable desktop notifications. This is a two-step notifications process that will ask a user to enable notifications and if they click exit give them three options: 1. Enable notifications. 2. Ask later. 3. Never ask on this computer again. The first two are self-explanatory (ask later = next session it asks again). The third is captured and stored in localStorage and a check is done on page load to see whether or not notifications should be displayed. Commit modified heavily by Brock Whittaker <brock@zulipchat.com>. Fixes #1189.
2017-09-23 11:27:18 +02:00
</div>
<div data-step="2" style="display: none">
onboarding: Revise text in prompt to enable desktop notifications. Making the same point (that you can configure the notifications in settings) at both steps felt pushy. I think the first prompt is actually best kept to a minimum of words, so leave that one with just the ask. In the second step, try an active pitch. This could go either way, or be any number of other messages, but the settings line felt a little defensive to me, like it was suggesting that our notifications would be noisy and here's a way you can try to mitigate that. I think with our default settings (and in an org with mostly-reasonable humans, but even a large and busy one) they're actually not at all noisy; and if we learn of situations where that's not true, we'll work to fix that. So, try this line instead. A style note: I chose "your team" here to refer to the people the user communicates with in their organization. We consistently say either "organization" or sometimes "realm" for the concrete thing in the product that is the whole universe of streams and users, etc., that a given account lives in; but that feels too formal here. Conversely, one reason we don't say "team" for an organization is that it feels too cozy and small, more appropriate for 8 people who interact every day than for 80 or 8000 people; but this line is mainly about those 8 people even if the organization has 8000. There are some examples of this already in the codebase; see `git grep -w team`. i18n note: These passages of a couple of connected sentences should generally be marked for translation as one message, not several separate ones. That helps the translator be sure of the context so they can translate appropriately. For example, in the second prompt in this version, there's an implicit "because" relationship between the two sentences, and in some languages (I'm 90% sure this is true in Japanese), it would be weird to leave it implicit and the second sentence should contain the equivalent of "That's because".
2017-10-23 23:43:12 +02:00
{{ _('We strongly recommend enabling desktop notifications. They help Zulip keep your team connected.') }}
notifications: Prompt user to enable desktop notifications. This is a two-step notifications process that will ask a user to enable notifications and if they click exit give them three options: 1. Enable notifications. 2. Ask later. 3. Never ask on this computer again. The first two are self-explanatory (ask later = next session it asks again). The third is captured and stored in localStorage and a check is done on page load to see whether or not notifications should be displayed. Commit modified heavily by Brock Whittaker <brock@zulipchat.com>. Fixes #1189.
2017-09-23 11:27:18 +02:00
<span class="buttons">
<a class="alert-link request-desktop-notifications">{{ _('Enable notifications') }}</a>
&bull;
<a class="alert-link exit">{{ _('Ask me later') }}</a>
&bull;
<a class="alert-link reject-notifications">{{ _('Never ask on this computer') }}</a>
</span>
</div>
</div>
</div>
Switch to fixed sidebar layout and remove bootstrap layout hooks. (imported from commit 060340a2febb7b8df6477a3419e7588a8503e377)
2013-08-13 12:52:26 +02:00
<div class="header">
Change logo/type on left sidebar column. This changes to a new logo/type on the left sidebar column.
2016-11-03 21:05:10 +01:00
<nav class="header-main rightside-userlist" id="top_navbar">
Switch to fixed sidebar layout and remove bootstrap layout hooks. (imported from commit 060340a2febb7b8df6477a3419e7588a8503e377)
2013-08-13 12:52:26 +02:00
<div class="column-left">
navbar: Remove text-decoration from brand logo link.
2017-09-12 18:51:57 +02:00
<a class="brand no-style" href="#">
navbar.html: Add empty alt to nav-logo.
2017-08-21 16:29:18 +02:00
<img src="/static/images/logo/zulip-icon-128x128.png" class="nav-logo no-drag" alt=""/>
Change logo/type on left sidebar column. This changes to a new logo/type on the left sidebar column.
2016-11-03 21:05:10 +01:00
<div class="company-name">
zulip
</div>
</a>
Modify crumbbar style to look like an arrowbar Also: * Change fixed element positioning and fix bugs * Move settings dropdown back to the right and add left padding to left sidebar (imported from commit fcf903b59617687f94618a01ce7544b69f408130)
2014-01-09 16:58:51 +01:00
</div>
<div class="column-middle" id="navbar-middle">
<div class="column-middle-inner">
<div id="streamlist-toggle" {%if embedded %} style="visibility: hidden"{% endif %}>
<a href="#" id="streamlist-toggle-button" role="button"><i class="icon-vector-reorder"></i>
<span id="streamlist-toggle-unreadcount">0</span>
</a>
</div>
<div id="searchbox" class="searchbox-rightmargin">
<div id="tab_bar" class="notdisplayed">
</div>
<form id="searchbox_form" class="form-search navbar-search">
<div id="search_arrows" class="input-append">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<input class="search-query input-block-level" id="search_query" type="text" placeholder="{{ _('Search') }}"
frontend: Add hotkey information to title/inline text. This should make many Zulip hotkeys significantly more discoverable.
2017-08-16 19:25:53 +02:00
autocomplete="off" aria-label="{{ _('Search') }}" title="{{ _('Search') }} (/)"/>
Modify crumbbar style to look like an arrowbar Also: * Change fixed element positioning and fix bugs * Move settings dropdown back to the right and add left padding to left sidebar (imported from commit fcf903b59617687f94618a01ce7544b69f408130)
2014-01-09 16:58:51 +01:00
{# Start the button off disabled since there is no active search #}
frontend: Add aria-label attributes to textareas/input fields.
2017-07-12 11:13:37 +02:00
<button class="btn search_button" type="button" id="search_exit" disabled="disabled" aria-label="{{ _('Exit search') }}"><i class="icon-vector-remove"></i></button>
Remove 1px space above search bar border.
2017-09-14 23:12:03 +02:00
<a class="search_icon" href="#search-operators" data-overlay-trigger="search-operators" title="{{ _('Search help') }}"><i class="icon-vector-search"></i></a>
Modify crumbbar style to look like an arrowbar Also: * Change fixed element positioning and fix bugs * Move settings dropdown back to the right and add left padding to left sidebar (imported from commit fcf903b59617687f94618a01ce7544b69f408130)
2014-01-09 16:58:51 +01:00
</div>
</form>
</div>{# /searchbox #}
</div>
</div>
<div class="column-right">
<div id="userlist-toggle">
<a href="#" id="userlist-toggle-button" role="button"><i class="icon-vector-group"></i>
<span id="userlist-toggle-unreadcount">0</span>
</a>
</div>
<div id="navbar-buttons" {%if embedded %} style="visibility: hidden"{% endif %}>
Move navbar code into its own "navbar.html". (imported from commit 4fa1c5d5ffa0af0ae8d608fad762470bf737205c)
2013-01-31 22:32:29 +01:00
<ul class="nav" role="navigation">
[bugfix] Fix the recent gear hovering regression. It's a long story, but we need to set the actual-dropdown-menu class for the gear, since it messes with bootstrap's notion of active. (imported from commit 94f2d9ee65014bc954e088e6c913d9682b7322f6)
2013-07-27 00:00:20 +02:00
<li class="dropdown actual-dropdown-menu" id="gear-menu">
frontend: Add hotkey information to title/inline text. This should make many Zulip hotkeys significantly more discoverable.
2017-08-16 19:25:53 +02:00
<a id="settings-dropdown" href="#" role="button" class="dropdown-toggle" data-target="nada" data-toggle="dropdown" title="{{ _('Menu') }} (g)">
Make settings menu more apparent (imported from commit 15e5db5c4792d39b54fa5a354f1156cde355160b)
2013-10-09 00:37:07 +02:00
<i class="icon-vector-cog"></i><i class="icon-vector-caret-down settings-dropdown-caret"></i>
Move navbar code into its own "navbar.html". (imported from commit 4fa1c5d5ffa0af0ae8d608fad762470bf737205c)
2013-01-31 22:32:29 +01:00
</a>
Additional fixes for relayout regressions. Specifically: * Fix the settings menu positioning and appearance * Restyle menu and add arrow on top * Remove labels from new message buttons in narrow windows and adjust the close button on the composition pane (imported from commit 586753b6526289b32ec0a90b62d8b2ac1c8182cd)
2013-08-15 23:03:28 +02:00
<ul class="dropdown-menu" role="menu" aria-labelledby="settings-dropdown">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
{#
Use a template comment instead of an HTML comment We don't really want this kind of comment leaking out to our users. (imported from commit 96249197d971d7cafc5cc663974a107116b44c8b)
2013-11-04 17:35:07 +01:00
It is quite ingrained in our frontend code that your Home
view is a Bootstrap Nav tab, even though we don't show the tab
anymore
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
#}
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<li class="invisible" style="display:none;" role="presentation"><a href="#home" data-toggle="tab"></a></li>
frontend: Remove purposeless title attributes from gear menu.
2017-08-16 12:33:02 +02:00
<li role="presentation">
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<a href="#streams" role="menuitem">
Rename 'Manage Streams' to 'Manage streams'.
2017-01-15 20:22:51 +01:00
<i class="icon-vector-exchange"></i> {{ _('Manage streams') }}
Move navbar code into its own "navbar.html". (imported from commit 4fa1c5d5ffa0af0ae8d608fad762470bf737205c)
2013-01-31 22:32:29 +01:00
</a>
</li>
frontend: Remove purposeless title attributes from gear menu.
2017-08-16 12:33:02 +02:00
<li role="presentation">
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<a href="#settings" role="menuitem">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<i class="icon-vector-wrench"></i> {{ _('Settings') }}
Move navbar code into its own "navbar.html". (imported from commit 4fa1c5d5ffa0af0ae8d608fad762470bf737205c)
2013-01-31 22:32:29 +01:00
</a>
</li>
frontend: Remove purposeless title attributes from gear menu.
2017-08-16 12:33:02 +02:00
<li class="admin-menu-item" role="presentation">
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<a href="#organization" role="menuitem">
gear-menu: Re-add the organization settings link. This re-adds the organization settings link and toggles the text dependent on whether the user is an administrator or not. Fixes: #4201.
2017-04-10 23:17:31 +02:00
<i class="icon-vector-bolt"></i>
<span>{{ _('Manage organization') }}</span>
navbar: Rearrange the icons.
2017-02-01 01:53:36 +01:00
</a>
</li>
<li class="divider"></li>
frontend: Remove purposeless title attributes from gear menu.
2017-08-16 12:33:02 +02:00
<li role="presentation">
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<a href="/help" target="_blank" role="menuitem">
navbar: Add a link to the /help/ site.
2017-02-01 01:53:36 +01:00
<i class="icon-vector-question-sign"></i> {{ _('User documentation') }}
</a>
</li>
frontend: Remove purposeless title attributes from gear menu.
2017-08-16 12:33:02 +02:00
<li role="presentation">
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<a tabindex="0" role="menuitem" data-overlay-trigger="keyboard-shortcuts">
frontend: Add hotkey information to title/inline text. This should make many Zulip hotkeys significantly more discoverable.
2017-08-16 19:25:53 +02:00
<i class="icon-vector-keyboard"></i> {{ _('Keyboard shortcuts') }} (?)
Move navbar code into its own "navbar.html". (imported from commit 4fa1c5d5ffa0af0ae8d608fad762470bf737205c)
2013-01-31 22:32:29 +01:00
</a>
</li>
frontend: Remove purposeless title attributes from gear menu.
2017-08-16 12:33:02 +02:00
<li role="presentation">
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<a tabindex="0" role="menuitem" data-overlay-trigger="markdown-help">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<i class="icon-vector-pencil"></i> {{ _('Message formatting') }}
Make message formatting accessible from gear drop-down. (imported from commit bbd7a0562bc96206b2d692433aa8c35cf3f9010a)
2013-03-25 22:17:22 +01:00
</a>
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
</li>
frontend: Remove purposeless title attributes from gear menu.
2017-08-16 12:33:02 +02:00
<li role="presentation">
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<a tabindex="0" role="menuitem" data-overlay-trigger="search-operators">
navbar: Rearrange the icons.
2017-02-01 01:53:36 +01:00
<i class="icon-vector-search"></i> {{ _('Search operators') }}
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
</a>
Make message formatting accessible from gear drop-down. (imported from commit bbd7a0562bc96206b2d692433aa8c35cf3f9010a)
2013-03-25 22:17:22 +01:00
</li>
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<li class="divider" role="presentation"></li>
frontend: Remove purposeless title attributes from gear menu.
2017-08-16 12:33:02 +02:00
<li role="presentation">
apps: Link directly to the upstream /apps page. Now that this page redirects to upstream, make our own links to it point directly upstream. This saves a redirect, and makes it more transparent where the link points if the user examines it before following.
2017-06-06 02:06:52 +02:00
<a href="{{ apps_page_url }}" target="_blank" role="menuitem">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<i class="icon-vector-desktop"></i> {{ _('Desktop & mobile apps') }}
Add gear menu items for the apps, integrations, and API. This will hopefully make them more discoverable. (imported from commit 931dd7d7ee6d5904ebb1da9c1b810f2e3701b215)
2013-09-17 23:11:00 +02:00
</a>
</li>
frontend: Remove purposeless title attributes from gear menu.
2017-08-16 12:33:02 +02:00
<li role="presentation">
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<a href="/integrations" target="_blank" role="menuitem">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<i class="icon-vector-github"></i> {{ _('Integrations') }}
Add gear menu items for the apps, integrations, and API. This will hopefully make them more discoverable. (imported from commit 931dd7d7ee6d5904ebb1da9c1b810f2e3701b215)
2013-09-17 23:11:00 +02:00
</a>
</li>
frontend: Remove purposeless title attributes from gear menu.
2017-08-16 12:33:02 +02:00
<li role="presentation">
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<a href="/api" target="_blank" role="menuitem">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<i class="icon-vector-sitemap"></i> {{ _('API documentation') }}
Add gear menu items for the apps, integrations, and API. This will hopefully make them more discoverable. (imported from commit 931dd7d7ee6d5904ebb1da9c1b810f2e3701b215)
2013-09-17 23:11:00 +02:00
</a>
navbar: Add link to /stats from the gear menu. This adds a link to the Zulip statistics UI, making it easy for users to discover. We'd been waiting on doing this until the visual design of that page was satisfactory, which it is now. Fixes #5774.
2017-07-16 23:34:24 +02:00
</li>
frontend: Remove purposeless title attributes from gear menu.
2017-08-16 12:33:02 +02:00
<li role="presentation">
navbar: Add link to /stats from the gear menu. This adds a link to the Zulip statistics UI, making it easy for users to discover. We'd been waiting on doing this until the visual design of that page was satisfactory, which it is now. Fixes #5774.
2017-07-16 23:34:24 +02:00
<a href="/stats" target="_blank" role="menuitem">
<i class="icon-vector-bar-chart"></i>
<span>{{ _('Statistics') }}</span>
</a>
Add gear menu items for the apps, integrations, and API. This will hopefully make them more discoverable. (imported from commit 931dd7d7ee6d5904ebb1da9c1b810f2e3701b215)
2013-09-17 23:11:00 +02:00
</li>
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<li class="divider" role="presentation"></li>
navbar: Rearrange the icons.
2017-02-01 01:53:36 +01:00
{% if enable_feedback %}
frontend: Remove purposeless title attributes from gear menu.
2017-08-16 12:33:02 +02:00
<li role="presentation">
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<a href="#feedback" class="feedback" role="menuitem">
navbar: Rearrange the icons.
2017-02-01 01:53:36 +01:00
<i class="icon-vector-comment"></i> {{ _('Feedback') }}
Add administrative panel to allow for user deactivations etc. We now show a list of users and allow you to deactivate a user using the same process as `python manage.py deactivate_user`. We add a new menu item accessible from the gear icon which will eventually have much more than just this, but we have a good start here. Here we also add a property to UserProfile which determines whether you're eligible to access the administration panel, and then have code which shows the menu option if so. This introduces a new JS file, admin.js. (imported from commit 52296fdedb46b4f32d541df43022ffccfb277297)
2013-08-12 23:31:23 +02:00
</a>
</li>
navbar: Rearrange the icons.
2017-02-01 01:53:36 +01:00
{% endif %}
Move navbar code into its own "navbar.html". (imported from commit 4fa1c5d5ffa0af0ae8d608fad762470bf737205c)
2013-01-31 22:32:29 +01:00
{% if show_invites %}
frontend: Remove purposeless title attributes from gear menu.
2017-08-16 12:33:02 +02:00
<li role="presentation">
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<a href="#invite" role="menuitem">
Change instances of 'coworkers' to 'users'. In order to genericize use of Zulip outside companies, all instances of coworkers have been changed to users. NOTABLE EXCEPTION: When the Zulip instance is domain- locked, the reference to coworkers remains. The reason for this is twofold: first, the majority of Zulip instances which require a particular domain will be locked to a company, and second, the template variable for the domain necessary should be added to the alert so it is clear to the user what the domain needs to be for access. Fixes: #861.
2016-06-02 21:15:37 +02:00
<i class="icon-vector-plus-sign"></i> {{ _('Invite users') }}
Move navbar code into its own "navbar.html". (imported from commit 4fa1c5d5ffa0af0ae8d608fad762470bf737205c)
2013-01-31 22:32:29 +01:00
</a>
</li>
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<li class="divider" role="presentation"></li>
navbar: Rearrange the icons.
2017-02-01 01:53:36 +01:00
{% endif %}
Add Webathena login button to our mirroring page. (imported from commit 43d8323bb502299027436a8c94c04f55d87bf953)
2013-08-27 21:15:15 +02:00
{% if show_webathena %}
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<li title="{% trans %}Grant Zulip the Kerberos tickets needed to run your Zephyr mirror via Webathena{% endtrans %}" id="webathena_login_menu" role="presentation">
<a href="#webathena" class="webathena_login" role="menuitem">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<i class="icon-vector-bolt"></i>{{ _('Link with Webathena') }}
Add Webathena login button to our mirroring page. (imported from commit 43d8323bb502299027436a8c94c04f55d87bf953)
2013-08-27 21:15:15 +02:00
</a>
</li>
{% endif %}
frontend: Remove purposeless title attributes from gear menu.
2017-08-16 12:33:02 +02:00
<li role="presentation">
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<a href="#logout" class="logout_button" role="menuitem">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<i class="icon-vector-off"></i> {{ _('Log out') }}
Move navbar code into its own "navbar.html". (imported from commit 4fa1c5d5ffa0af0ae8d608fad762470bf737205c)
2013-01-31 22:32:29 +01:00
</a>
</li>
{% if show_debug %}
frontend: Remove purposeless title attributes from gear menu.
2017-08-16 12:33:02 +02:00
<li role="presentation">
Fix ARIA markup for settings menu The settings dropdown was marked as having the "menu" ARIA role, but contained no items with the "menuitem" role. I assigned this role to the focusable link elements, and gave the intervening "li" elements (and other "li" elements used as separators and such) the "presentation" role to allow those to be gracefully ignored when appropriate. Some of the links previously had the "button" role, which I think was a holdover from a previous UI layout. Fixes #5000.
2017-05-26 01:04:14 +02:00
<a href="#debug" data-toggle="tab" role="menuitem">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<i class="icon-vector-barcode"></i> {{ _('Debug') }}
Move navbar code into its own "navbar.html". (imported from commit 4fa1c5d5ffa0af0ae8d608fad762470bf737205c)
2013-01-31 22:32:29 +01:00
</a>
</li>
{% endif %}
</ul>
</li>
</ul>
</div>
Move crumbbar to header and change visual appearance (imported from commit 435e3b46b615f6c496be10b7d170ed3e4201787d)
2014-01-08 16:12:22 +01:00
</div>
Change logo/type on left sidebar column. This changes to a new logo/type on the left sidebar column.
2016-11-03 21:05:10 +01:00
</nav>
Switch to fixed sidebar layout and remove bootstrap layout hooks. (imported from commit 060340a2febb7b8df6477a3419e7588a8503e377)
2013-08-13 12:52:26 +02:00
</div>