This patch slightly adjusts the font size of list items in the main
menu. I probably wouldn't mind making it even a bit bigger, but that's
probably worth a separate discussion.
Reasons for this adjustment:
1. Don't use different font sizes in the same lement.
While the buttons rendered at 14px, the search text rendered at 16px.
They should have the same font-size.
2. The buttons were below the base text size controlled by Tailwind CSS.
This means, it also puts the font size below the recommended
font-size for mobile devices (Google/Apple guidelines). This patch
puts them at the base level.
This patch removes the map marker from the adventures list item of the
main menu dropdown. It is not being rendered and given that all other
elements do not have an icon, it is probably a remnant of old code and
left by accident.
This is a slight improvement to pull request #576. I noticed that on a
tablet, the AdventureLog in the navigation bar would not render, even
though there would be enpugh free space. This patch moves the breakpoint
for hiding the text one step further towards smaller devices.
The width of collection cards can vary quite a bit. Additionally, the
cards look different than the cards within a collection. It would be
nice if the design would be more or leyy the same for all of them.
This patch adjusts the collection card design by adapting the classes
from the cards within the collection (I literally just copied the
classes from ChecklistCard). This is another step in making the user
interface more homogeneous.
The tab-based selection of views in a collection doesn't really work on
mobile devices since it needs too much horizontal space. This leads to
text overflowing buttons as well as half of the tab bar disappearing
behind the right edge of the phone screen.
This patch modifies the navigation by keeping the current tabs in
desktop mode, but switching to a very compact dropdown on mobile
devices.
The functionality of both elements is identical.
This patch makes it less likely for elements of the navigation bar to
overlap each other on mobile devices. It also makes spacing a bit more
homogeneous.
The patch basically just adjust some spacing as and hides the map icon
on mobile devices.
This patch updates the Dockerfile to use Node.js 22 for running the
frontend. Given that the security support of Node.js 18 ends in 6 days
(30 Apr 2025), upgrading definitely makes sense.
Additionally, this also seems to fix the broken JSON generated by the
recently upgrraded version of @sveltejs/kit, thus fixing #584.
Similar to #552 (658764f) the card title and badges of the
transportation card can overlap. This patch adjusts the transportation
card to list the badges below the title similar to the other cards.
Often, you end up having short notes or even just a simple link and it
is somewhat tedious to go into the details to retrieve the additional
information.
This patch displays a preview of the note content and a maximum of three
links on the notes card directly. This makes accessing information much
faster.
This fixes #562.
This is a very simple patch fixing the rendering issue of the “Remove
from collection” option in the adventure dropdown.-
Together with #552, this should fix #539.
This patch prevents overlapping UI eelements in the ledging card. It
adjusts the UI to be more like the adventure cards when it comes to font
size and element placing.
This partly fixes #539
If you are in a collection – e.g on “All Linked Items” – and go into an
adventure, going back will cause you to end up on the itinerary. This is
quite annoying if you have a number of options for a trip linked already
but whenever you go back, you have to scroll up again, click on “All
Linked Items”, and scroll down again to get to the next adventure in
line.
This patch makes AdventureLog remember the tab you were in and going
back and forth in the browser history will actually work.
Opening the share dialog, the frontend is requesting `/auth/users/`
which is always redirected to `/auth/users`. That's an unnecessary extra
step.
This patch makes the front-end request `/auth/users` in the first place.
