diff options
| author | ewy <ewy0@protonmail.com> | 2026-06-14 18:23:44 +0200 |
|---|---|---|
| committer | ewy <ewy0@protonmail.com> | 2026-06-14 18:23:44 +0200 |
| commit | 936fb0c8676861f1ab15a255018a2bf82fa81aab (patch) | |
| tree | d0c72f6d0f37f60373d7a7b0c1c2b61346aef02b | |
| parent | 40577525de2a01ca0b21a5d88757295ae7735580 (diff) | |
update web
| -rw-r--r-- | README.md | 12 | ||||
| -rw-r--r-- | web/index.html | 95 |
2 files changed, 73 insertions, 34 deletions
@@ -58,7 +58,9 @@ pik remembers your projects, and you can invoke stuff almost anywhere. to view e pik reads the first comment line from your targets and informs you in the tui! -## current features +## features + +Run `pik --help` to view the manpage. It is created at runtime by `pik`, so it is always up to date. * run targets by their approximate name: `pik build` will trigger `.pik/build.sh`, or `.pik/build.py`, or `make build` depending on what's possible. @@ -91,6 +93,9 @@ pik reads the first comment line from your targets and informs you in the tui! * search with `/` and `?`, scroll results with `n` and `N` ### supported pik runners + +these files can be run by invoking them through pik: + * python * shell * executable files @@ -98,11 +103,12 @@ pik reads the first comment line from your targets and informs you in the tui! ### supported external runners +these existing systems can be invoked through pik, meaning you can use pik's call site features (etc.) while still using +your preferred system. + * `just` * `make` * `pyproject.toml` -* -* if you want any more let me know and it should be done very fast ## planned features diff --git a/web/index.html b/web/index.html index 273d93d..4dcb703 100644 --- a/web/index.html +++ b/web/index.html @@ -11,15 +11,45 @@ content="width=device-width, user-scalable=no, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0"> <meta http-equiv="X-UA-Compatible" content="ie=edge"> <link rel="icon" href="data:,"/> - <meta content="pik - file-based task runner" property="og:title" /> - <meta content="https://mepik.dev" property="og:url" /> + <meta content="pik - file-based task runner" property="og:title"/> + <meta content="https://mepik.dev" property="og:url"/> - <meta content="file-based task runner" property="og:description" /> + <meta content="file-based task runner" property="og:description"/> - <meta content="#f2cae2" data-react-helmet="true" name="theme-color" /> - <link type="text/css" rel="stylesheet" href="https://ewy.one/terminal.css" /> + <meta content="#f2cae2" data-react-helmet="true" name="theme-color"/> + <link type="text/css" rel="stylesheet" href="https://ewy.one/terminal.css"/> <title>pik - file based task runner</title> <style> + pre { + border: solid black 4px; + font-family: "Symbols Nerd Font Mono", monospace; + padding: 4px; + user-select: none; + background-color: var(--black); + line-height: 1.1em; + font-size: 12px; + + & .sel { + background-color: rgba(11, 141, 0, 0.41); + } + + & .src { + background-color: #be40e3; + } + + & .cat { + background-color: var(--white); + color: var(--black); + } + + & span { + } + + & .faint { + opacity: 0.5; + } + } + img { box-sizing: border-box; max-width: 100%; @@ -54,22 +84,37 @@ <span>file-based task runner</span> </header> <main> - <section> - <img src="https://uwu.ewy.one/satty-20260502-18:45:46.png" alt="screenshot of the pik terminal interface" style="margin-top: -8px;"/> - <small>these assets were all created during ongoing development</small> + <section aria-hidden="true"> + <pre> +<span class="src">▌ pik ~/Projects/pik</span> +<span class="sel">▌ ⏵ build.sh <span class="faint">build pik</span></span> +▌ coverage.sh <span class="faint">coverage report</span> +▌ install.sh <span class="faint">install pik to ~/.local/bin</span> +▌ integrations.sh +▌ man.sh +▌ script.override.sh <span class="faint">example script</span> +▌ script.sh <span class="faint">example script</span> +▌ test.sh +▌ thing.py +▌ unittest.sh +<span class="cat">▌ web</span> +▌ web deploy.sh <span class="faint">gets run on server</span> +▌ web update.sh <span class="faint">update files on website</span> +▌ master +6 ~1 + +<span class="src">▌ ewout ~/</span> +▌ time.sh <span class="faint">show the current time</span> +<span class="faint"> use --edit to open a target in your $EDITOR</span></pre> </section> <section class="important"> <p> targets are files </p> <p> - integrates with build systems and other task runners - </p> - <p> - can be creatively invoked and associated + integrates with other task runners and build systems </p> <p> - tui which assists, reminds and teaches + tui and cli as first class citizens </p> <p> persistent memory allows calling from anywhere @@ -93,31 +138,19 @@ </li> </ul> </section> - <section> - <img src="img/pik.svg" alt="an animation of the program 'pik' being used, at first in the terminal interface, and then invoking a target through arguments" /> - </section> - <section> - <figure> - <img src="https://uwu.ewy.one/satty-20260417-00:10:15.png" /> - <blockquote>fig. 1: the pik tui</blockquote> - </figure> - </section> - <section> - <figure> - <img src="https://uwu.ewy.one/satty-20260414-21:39:11.png" /> - <blockquote>fig. 2: the pik experience</blockquote> - </figure> - </section> </main> <footer> <section> proudly powered by <a href="https://ewy.one">ewy</a> </section> <section class="warranty"> - THERE IS NO WARRANTY FOR THE SOFTWARE, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN - WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE SOFTWARE “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER + THERE IS NO WARRANTY FOR THE SOFTWARE, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED + IN + WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE SOFTWARE “AS IS” WITHOUT WARRANTY OF ANY KIND, + EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A - PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE IS WITH THE CUSTOMER. SHOULD + PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE IS WITH THE CUSTOMER. + SHOULD THE SOFTWARE PROVE DEFECTIVE, THE CUSTOMER ASSUMES THE COST OF ALL NECESSARY SERVICING, REPAIR, OR CORRECTION. </section> </footer> |
