about summary refs log tree commit diff
path: root/templates
Commit message (Collapse)AuthorAgeFilesLines
* Reduce unwraps in u-ate and u-drank handlingVika2024-09-071-10/+10
|
* kittybox-frontend-renderer: use p-summary if availableVika2024-09-071-5/+15
|
* kittybox-frontend-renderer: fix testsVika2024-08-281-3/+3
|
* Indicate `u-uid` as `rel=canonical`Vika2024-08-261-5/+5
| | | | | | | | | | | This only displays on top-level entries, not ones in feeds. This should help search indexers know which URI is the canonical for a given link. I wonder why Google doesn't bother to parse MF2 markup. Do they think themselves monarchs of the Internet, able to show peasants their place? their search results are shitty anyway, I'd rather ask GPT-2. Yes, GPT TWO. Not even 3, 4 or 4o!
* Appease most clippy warningsVika2024-08-261-4/+4
| | | | | | The warnings only remain in places where I need them to remain, because I either need a reminder to implement something, or I need to refactor and simplify the code in question.
* indieauth_metadata -> indieauth-metadataVika2024-08-241-1/+1
|
* kittybox-util: 0.1.0 -> 0.2.0Vika2024-08-202-3/+3
| | | | Micropub types are now more coherent and gathered in one place.
* onboarding: attempt to fix the redirection bugVika2024-08-181-2/+2
|
* feat: logins!!Vika2024-08-184-29/+35
| | | | | | | | yes you can finally sign in this is also supposed to show private posts intended for you! maybe i can also reveal my email to those who sign in! :3
* kittybox-frontend-renderer: add a notice to pester me on non-descriptive errorsVika2024-08-181-0/+5
|
* kittybox-frontend-renderer: fix onboarding CSS a littleVika2024-08-181-1/+4
|
* onboarding: provide official alternate onboarding flow for no-JSVika2024-08-181-0/+38
| | | | | | | | | | | | | This documents the onboarding request schema so somebody unwilling or unable to run JavaScript (why would you subject yourself to this?) is still able to use Kittybox. Since JavaScript is used to provide form interactivity and complex data structures in the onboarding flow, whoever cannot run JS will have to manually compose the onboarding request, and this will help them a little. I just need to remember to update this if the schema ever changes.
* Upgrade dependencies and fix deprecated functionalityVika2024-08-022-47/+45
| | | | | | | I think I managed to not lose any functionality from my dependencies. sqlparser remains unupgraded, but that's mostly because it is only used in one example and it's not worth it to upgrade right now.
* Start working on login functionalityVika2024-07-091-1/+1
|
* kittybox-indieauth: 0.1.0 -> 0.2.0Vika2024-07-091-1/+1
| | | | | | | | | Added fundamental AutoAuth types. This library can now be used to augment existing authorization and token endpoints with AutoAuth capabilities. See https://github.com/sknebel/AutoAuth/blob/master/AutoAuth.md for the latest spec draft.
* WIP: admin (not wired up yet, and DEFINITELY NOT SECURE, DO NOT WIRE UP)Vika2024-07-082-0/+7
|
* kittybox-templates: fix icons on bookmark postsVika2024-03-041-27/+16
|
* kittybox-templates: fix misaligned links in mini-h-cardsVika2024-03-041-0/+1
|
* templates: fix build with Cargo 1.73+Vika2024-01-291-1/+1
|
* lint: no extra whitespace on line endingsVika2024-01-292-2/+2
|
* Fix bug with likes/bookmarks on h-entries lacking URLs in markupVika2023-10-151-1/+21
|
* Remove extraneous JS filesVika2023-07-312-119/+0
|
* Moved the entire Kittybox tree into the rootVika2023-07-2918-0/+2346
|
* flake.nix: reorganizeVika2022-05-245-1127/+0
| | | | | | | | | | | | - Kittybox's source code is moved to a subfolder - This improves build caching by Nix since it doesn't take changes to other files into account - Package and test definitions were spun into separate files - This makes my flake.nix much easier to navigate - This also makes it somewhat possible to use without flakes (but it is still not easy, so use flakes!) - Some attributes were moved in compliance with Nix 2.8's changes to flake schema
* templates: prepare for facepiles a bit betterVika2022-05-231-16/+29
| | | | | | | | This bit of code is still disabled for now though. I need to actually gather and render facepiles. Additionally, now details won't even show if there were no reactions to the post, which saves space.
* templates: render like and bookmark posts correctlyVika2022-05-232-1/+109
| | | | | | | | | | | | | They really use the same framework, so for now a unit test for like posts is sufficient. Of course, for proper coverage, one can introduce tests for bookmarks too, especially if one chooses to render them differently. The logic will be pretty much the same though. Replies might use the same logic, since those are also Webmention-oriented posts. (It looks like another way to classify MF2 documents is slowly forming in my brain. Maybe I should write about it on my blog.)
* templates: simplify logicVika2022-05-231-24/+29
| | | | | | | There were lots of unneccesary Option::unwrap() invocations that could be replaced with `if let` statements. This makes the code cleaner and less likely to panic in case a corrupted, incomplete or manually injected MF2-JSON document needs to be rendered.
* templates: add a banner for Kittybox in the footerVika2022-05-231-0/+7
| | | | Now everyone will know where to get my software if they see it.
* templates: add unit test for articlesVika2022-05-231-45/+116
| | | | | | It mostly checks the same old things as with notes, but does check for a name (and as it's explicitly provided, it does work with the buggy version of the `microformats` crate.
* templates: more MF2 generatorsVika2022-05-231-5/+62
| | | | | | | | | | New generators include: - Articles (h-entry with a name) - Replies (notes with an in-reply-to) - Likes (h-entries with a like-of) For replies and likes, there are variants with an h-cite (full reply context) or a link (partial reply context).
* templates: introduce unit testsVika2022-05-232-0/+161
| | | | | | | | | | | | | | | These unit tests generate a random MF2-JSON post, convert it to MF2-HTML using the template and then read it back using the `microformats` crate. The only problem is that it has a nasty bug with overstuffing implied properties. This is being worked on: https://gitlab.com/maxburon/microformats-parser/-/issues/7 For now the tests marked as ignored because they fail. But the function itself that generates them should remain here for documentation and potential code sharing with the `microformats` crate, potentially even migrating to a subcrate there.
* Split into different cratesVika2022-05-075-0/+705
Templates and utility types are now separate crates to speed up compilation, linting and potential reuse/replacement. Potentially more crates could be split out/modularized, resulting in speedups, smaller binaries (whenever features are excluded) and even more reuse capabilities.