{% extends "scitex_ui/standalone_shell.html" %}
{% load static %}
{% comment %}
Board v3 now extends the scitex-ui workspace shell (operator-asked,
TG msg 302 / 303 — wants Alt+I element-inspector + shared chrome
parity with the legacy GraphView). All inline content is repacked
into the shell's three blocks: extra_css holds the page-local
styles, app_content holds the kanban + BLOCKING-YOU panel + detail
modal, extra_js holds the page logic.
Alt+I element-inspector wires up automatically via scitex-ui's
context_processor (settings.py guards the install at scitex-ui
≥0.5.0). For older scitex-ui installs the inspector degrades
silently; the board itself works either way.
The favicon link is injected via extra_css (the shell template has
no favicon block; extra_css renders inside ).
{% endcomment %}
{% block extra_css %}
{# combobox.css (loaded below the page-CSS so its specificity sits ON TOP if needed) #}
{% comment %}
searchQuery.js — GitHub-style qualifier-syntax parser (project:/agent:/
status:/...). Exposes window.STX.searchQuery; the page logic below
delegates `fuzzyMatch` to it whenever the input contains a recognized
qualifier. Operator TG 12315/12316: photographed typing
`project: paper-scitex-clew` into the search bar — they already
expected GitHub-style syntax. Pure JS module, no DOM deps; unit
tests at tests/scitex_todo/test__search_query.js.
NB: Django's `{# … #}` syntax is single-line only — a multi-line
block leaks its body into the rendered HTML. Use `{% comment %}` for
any multi-line note inside a template (board v0.5.4 fix — PR #105).
{% endcomment %}
{% comment %}
searchSuggest.js — autocomplete/Tab-completion engine, extends PR #102.
Pure module; the inline script in extra_js below wires it to the
#f-search input. Exposes window.STX.searchSuggest. Operator TG 12318.
{% endcomment %}
{% endblock extra_css %}
{% block app_content %}
{% comment %}
Filterbar reorg (operator TG, lead a2a `b48f7c2c438b464698183d2e95d3bb04`,
2026-06-12). Three explicit groups end the flex-wrap chaos:
.fb-left — identity (title + version + LIVE chip)
.fb-center — search (input + autocomplete suggest)
.fb-right — operations (Layout | Sort | Filters | Recent
count | Group | Add Task | blocking
me | overflow controls)
Active-filter chips + qualifier hint pills move to a second row
`
{# end .filterbar #}
{% comment %}
Filterbar second row — active filter chips + qualifier-hint pills.
Hidden via CSS when both children are empty so the main filterbar
stays at ~50 px on the default state. Populated by
renderActiveFilterChips() / renderQualifierHints() in extra_js.
{% endcomment %}
{% comment %}
BLOCKING-YOU 360 px aside REMOVED (P12, lead a2a 2026-06-12). The
"right-end giant lane" the operator photographed is now a normal
project column synthesized client-side as the `user` lane (see
USER_LANE_KEY in _renderColumnView): every task with
`status === "blocked" && blocker === "operator-decision"` shows up
in a column titled `user` at normal width, with normal drag-reorder
/ pin / column-context-menu. Tasks still live in their REAL project
column too; the user lane is a render-time aggregation, not a
schema change. The mobile `#by-fab` drawer toggle is removed with
the aside; the "🚧 blocking me" filterbar toggle (#t-block) still
works because it's a filter, not a drawer.
NB: PR #108 inadvertently left the aside HTML + `#block-rows`
placeholder in place while removing the JS that populated it —
operator saw "loading…" forever in the right sidebar. This commit
finishes the job.
{% endcomment %}
·selected:
0·
0 matches.
loading…
v3 LIVE · real data · operator schema (ADR-0007) · GUI→code (ADR-0006)…
💬 Comments