Changelog

This page contains a list of all changes and updates made to the website. You can use the search bar below to search for a version!

Not all changes warrant a new changelog! When a change is very small and/or urgent, it may not show up here.

Minor update v26.23.8

Release date: June 15th, 2026

• + Added Japanese font support.
• ~ Reworked the entirety of the contributors page, and implemented a better convention for contributor roles.

Minor update v26.23.7

Release date: June 14th, 2026

A bit of an internal update today.

• ƒ Fixed an issue where the privacy policy link within the analytics panel would take you to the 404 page.
• ƒ Fixed a logic issue within the analytics panel, where the panel would still show up on mobile devices in the privacy policy page.
• ~ Reworked the current font size convention to use em units instead of px. This would allow responsive layouts to be easier to implement, and also improve readability on mobile devices.
• ~ Improved the design of the analytics panel, in order to make it friendly for devices with a significantly short width.
• ~ Renamed the frontpage stylesheet from styles.css to welcome.css in order to match the new conventions.
• ~ Improved phrasing of some paragraphs within certain sections of the website.

Minor update v26.23.6

Release date: June 13th, 2026

Small update today.

• ƒ Fixed an issue where the frozen state wouldn't get removed after the analytics panel is hidden.
• ~ Completely overhauled the margin system. Please do note that the pages within /troubleshooting hasn't been updated along yet. We will work on this soon.
• ~ Improved the structure within changelogs.
• ~ Improved analytics toggle logic.
• ~ Unified <meta> tag usage across pages.

Minor update v26.23.5

Release date: June 12th, 2026

This update is part of the navigation UI/UX overhaul. We do not have an ETA for the actual overhaul yet, but it will take place sometime in June.

• + Added a .frozen attribute to the main element, so some panels can disable user interaction with the main content when necessary.
• + Added a link to the core-api project's changelog within the projects page .
• + Added a completely alternate layout to the warning panel for mobile devices.
• + Implemented a redirect from /projects/core-api/changelog/:path* to https://api.lanzoor.dev/docs/changelog/:path* to match the projects convention.
• ~ Improved the color pallete of the warning panel.
• ~ Updated the privacy policy to v2.3 in order to match so it matches the new changes.
• ~ Updated the logic of the script loaded by the privacy policy to hide the panel when you make a choice via the button.

Minor update v26.23.4

Release date: June 10th, 2026

• ~ Fixed some in-site links using the _blank attribute in the projects page .
• ~p Altered the color scheme of codeblocks.
• - Removed the annoying margin for code and kbd elements.

Minor update v26.23.3

Release date: June 9th, 2026

• + Added a link to core-status within the projects page .
• + Added a changelog page at /projects/core/changelog , which is exactly what you're looking at right now!
• ~ Improved top panel link hover animations. Implemented a better color pallete and a more noticable text shadow.
• ~ The anti-JPA project has been moved to the legacy category. This project will be archived for a while, and will be deleted eventually.
• ~p Changed the position of the left panel to the right.
• - Removed the outdated status page at /troubleshooting/status.html, in favor of the new work-in-progress one.

Legend

Naming Conventions for Changes

Change Writing Conventions

Changes are written in the past tense rather than the imperative mood commonly used in Git commits. This improves readability for visitors who are not familiar with development workflows.

Each change entry ends with a period (.).

Change Order

Changes are generally ordered from the most significant to the least significant.

Change Prefixes

Every change is prefixed with a symbol indicating what happened.

• A purple f (ƒ) indicates that an issue has been fixed.
• A green plus sign (+) indicates that something has been added.
• A yellow tilde (~) indicates that something has been changed or improved.
• A red minus sign (-) indicates that something has been removed.
• In some cases, a blue p may appear after the symbol. This means the change is provisional and may be reverted in the future.

Please note that change prefixes are only intended as a quick summary of a change. They are subjective and may not fully describe everything included in an update. For example, an entry marked with a plus sign may also contain modifications to existing features.