TreeMap
무료 오픈소스 디스크 사용량 시각화 도구로, 사각형 트리맵·중복 파일 탐색·디스크 가득 예측·정리 시 파일을 휴지통으로만 이동한다
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기TFA Invitation Buddy: build a rules-ready TFA IQT invitation to paste into Tabroom. Independent tool, not affiliated with TFA.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Answer a few questions, and get a rules-ready tournament invitation you can paste into Tabroom.
Disclaimer: TFA Invitation Buddy is an independent tool. It is not affiliated with, endorsed by, or sponsored by the Texas Forensic Association. It is provided as a convenience, does not constitute official guidance, and does not guarantee compliance. The tournament host is responsible for making sure the invitation and tournament follow the current TFA rules.
Schools hosting a TFA Invitational Qualifying Tournament (IQT) answer a guided questionnaire. The tool builds an invitation that you can:
.html file,.docx file.There are two modes, switchable at any time from the Builder mode switch at the top of the page. Your answers are kept when you switch.
| Mode | What you get |
|---|---|
| TFA Required Information Only | Tournament basics (name, host school(s), swing, dates, qualification offered), an optional Events Offered list, and only the disclosures the TFA Constitution requires on an IQT invitation: judge panels, sweepstakes formula, power-matching, bracket breaking, debate topics, Congress docket, and host-school eligibility. If you offer Congress, it also includes the per-item limit and Presiding Officer statements when you use those options. |
| Detailed Invitation Builder | A complete invitation: everything above, plus a welcome letter and dated updates, bid and swing details, the full deadline set, other (non-TFA) events and divisions, schedule, per-event fees and policies, judging expectations, awards and qualification points, debate and IE format (including extemp topic areas), eligibility and tournament policies, logistics, contacts, and additional information. These fields were modeled on several well-regarded Texas invitations. |
How it works:
index.html, and works offline once loaded.Check Tabroom's handling of the HTML before you publish. The tool's HTML output uses only simple tags (h2, h3, p, ul, ol, li, strong, em, a, br, and basic tables with inline borders). However, it has not been verified against Tabroom's editor.
If you post parts of the invitation on separate Tabroom pages (for example "Judge Information" or "Debate Topics"), use the per-section Copy buttons on the Review step.
If Tabroom strips or changes something, the HTML renderer is one small, isolated function (toTabroomHTML and the TAB style constants in index.html), so it's easy to adjust.
git init
git add index.html README.md DECISIONS.md TESTING.md
git commit -m "TFA Invitation Buddy"
tfa-invitation-buddy), leave it empty (no README), and create it.YOUR-NAME with your GitHub user name:
git branch -M main
git remote add origin https://github.com/YOUR-NAME/tfa-invitation-buddy.git
git push -u origin main
https://YOUR-NAME.github.io/tfa-invitation-buddy/.You can also open index.html directly from your computer; no server is needed.
All rule content lives at the top of the <script> in index.html, above the line END OF CONFIGURATION. You should not need to touch the engine or renderers below it.
| What changed | Where to edit |
|---|---|
| Rules version (footer and About text) | CONFIG.rulesVersion and CONFIG.rulesVersionAbout |
| Disclaimer, tagline, TFA link | CONFIG.disclaimer, CONFIG.tagline, CONFIG.tfaUrl |
| Events (add, rename, regroup) | CONFIG.events. Each event's flags (panel, topic, ws, congress, prelims, minPrelims, fee, minEntries) decide which questions it switches on. |
| Minimum entries, minimum schools, minimum events | minEntries on each event; CONFIG.minSchoolsForPoints; CONFIG.minEvents |
| IQT date windows | CONFIG.iqtWindows |
| Rounds-per-day limit | CONFIG.maxRoundsPerDay, CONFIG.maxRoundsMinDays |
| Question wording, help, "Why?" text, citations | the matching entry in RULES (title, help, why, and each field's label) |
| Validation messages | the question's required: strings and its validate() function |
| Output wording | the question's output() function |
| Section order in the invitation | SECTIONS |
| Form steps | STEPS, plus each question's step |
After editing, open index.html and walk through both modes. Check that the Review checklist and preview look right.
Every "Why?" tooltip quotes its citation (for example "IQT Manual, Requirements #19 and #25a (pp. 101–102)"). To check them against a new Constitution:
RULES, search the PDF for the rule's key phrase. Confirm the item number, page, and wording, then update why and CONFIG.rulesVersion.DECISIONS.md lists the places where the spec and the 2026 Constitution differ and how each was handled.
index.html: the whole tool (inline CSS and JavaScript, no dependencies)DECISIONS.md: assumptions, defaults used, and spec/Constitution conflictsTESTING.md: the test report