* Add Hugo build artifacts to .gitignore
Ignore docs/public/, docs/resources/, and docs/.hugo_build.lock so
generated Hugo output is never accidentally committed.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Add Hugo site infrastructure for Linutil docs
Adds the Hugo configuration, theme module (hextra), layout shortcodes,
i18n strings, static assets (favicons, nav logo), and archetype template
needed to build the documentation site.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Add docs site homepage
Adds the root _index.md with badges, the quick-start curl command, and
an important-note callout about frequent updates.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Add user guide content pages for Linutil
Rewrites all user guide sections from Winutil (Windows) content to
accurate Linutil (Linux) documentation:
- _index.md: overview, feature summary, quick links
- getting-started.md: how to run, install options, TUI navigation, keyboard shortcuts
- store/_index.md: application installation guide with category tables
- tweaks/_index.md: distro-specific system setup (Arch, Fedora, Debian, Ubuntu, Alpine)
- features/_index.md: security, gaming, emulators, and utilities reference
- updates/_index.md: how to keep Linutil up to date
- automation/_index.md: TOML config file usage and use-case examples
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Add FAQ, known issues, and contributing guide pages
- faq.md: answers for general usage, running, scripts, contributing, and updates
- KnownIssues.md: documents terminal size, rendering, distro support, Nvidia, and Cargo update issues
- CONTRIBUTING.md: full contributing guide based on .github/CONTRIBUTING.md, formatted for the docs site
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Add developer reference section and architecture docs
- dev/_index.md: landing page for the developer reference section
- dev/architecture.md: comprehensive architecture doc covering workspace
layout, data model (Tab/ListNode/Command), tab_data.toml format, task
list flags, preconditions system, script embedding via include_dir!,
the script execution pipeline (PTY/vt100/tui-term), TUI layout and
focus state machine, config file parsing, and key dependencies
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docgen: write walkthrough to docs/content/userguide/walkthrough.md
- Rename generated file from userguide.md to walkthrough.md to better
reflect that it is an auto-generated script reference/walkthrough
- Update USER_GUIDE path to docs/content/userguide/walkthrough.md so
cargo xtask docgen writes to the correct Hugo content location
- Update automation guide link to point to ../walkthrough/
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: remove unused Winutil screenshot assets
All images in docs/assets/images/ were Winutil (Windows) screenshots
copied over from the Winutil docs. None are referenced by any content
file. Keeping only favicon.png and navlogo.png at the assets root,
which are used by hugo.toml.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Update CNAME
* updated hugo configs
* docs: add preview.gif to homepage via Hugo mount
Mount .github/preview.gif directly into Hugo's static pipeline using
includeFiles so only the gif is exposed (no workflows or other .github
files). This means any update to .github/preview.gif is automatically
reflected on the site without any manual copying.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* added workflow
* Delete docs/assets/navlogo.png
can change this to something else
* Delete navlogo.png
* Update docs.yaml
* Update hugo.toml
* Update _index.md
* fix typo
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
so i decided to make labeling prs a bit easier and this workflow
automatically syncs issue labels to a newly created pr
(if it has a closing keyword for that issue of course). this WILL NOT
always be accurate so we still need to review manually. it's not a
replacement, just makes stuff easier.
fully tested on my fork
heyy so i decided to do a little autumn cleaning in our issue management
in linutil. i created a couple of new labels
([label list](https://github.com/ChrisTitusTech/linutil/labels)),
updated the issue templates to be more concise, and updated
`ALLOWED_USERS` in the `issue-slash-commands` workflow.
from now on, we'll be using the new priority labels for issues and PRs.
also, i'd like to say that we (the maintainers, so @ChrisTitusTech,
@afonsofrancof, and me) need to start labeling stuff accordingly again.
the releases still rely on PR labels.
for that, i created the `initial review required` label. it'll be added
to every issue upon creation, and then removed after a maintainer review
which would include adding priority and scope labels.
so chris, please start labeling RPs again :3
🚨 THIS IS MY COMEBACK PR I CAME BACK HELLO 🚨
so basically i added unit tests for critical core functions and also
some cats :3 hope its not an issue (im taking a break again if it is)
also figured would be nice to have `cargo test` in `publish.sh`
resolves#1023
dependabot[bot]