Repository navigation
Conversation
Add bilingual author guidance and draft release notes for load-time invocation adaptation, startup diagnostics and module-level degradation. Keep latest sidebars in parity and qualify the introduction by version. Refs UltiKits/UltiTools-Reborn#655 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
WR-01: Limit per-reference warnings to module-owned scanned packages and document bundled-library INFO summaries in both languages. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Preserve released 6.3.2 and 6.3.1 navigation alongside the 6.4.0 draft and older-server guidance. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs: v6.4.0 framework guidance (scheduled tasks, crash-safe YAML)
docs(compat): document pre-1.21 module support for 6.4.0
docs(config): legacy config parser API removed in v6.4.0
The tab row, the nav bar title, the sidebar and the article used to disagree on their left boundary: the tab row tracked the article card (292/1420 at a 1440 viewport) while the nav bar and the sidebar sat on the page edge. The tab row now uses the same algorithm as the nav bar wrapper: max-width 1440, centred, 32px padding. Measured left edge of the first tab, the first character of the nav bar title and #VPSidebarNav at 1440/1600/1920 is 32/112/272 for all three. The version switcher leaves the tab row. Layout.vue renders it in nav-bar-content-before on desktop and in the screen menu on mobile, from config/version-pages.generated.mjs, the manifest VersionNoticeBar already reads. The has-sidebar title goes back into the flow at max-content so the switcher sits next to the title text: measured 28px gap (16px box gap plus 12px trigger padding) instead of the roughly 116px the default 272px absolute title box left. SecondNavBar's announcement takes its version from the same manifest; it used to read props.versioningPlugin off the switcher's nav entry, which no longer exists, and would otherwise render the text without a version number. The nav bar divider moves from the left of the social links to between the social links and the Dev Portal button: 1px by 24px in --vp-c-divider, inside the >=1280px band where the social links are in that row. The search button gets a background of its own. Upstream paints .DocSearch-Button with var(--vp-c-bg-alt), which this theme sets to the same value as --vp-c-bg (#000000 dark, #ffffff light), so the field was invisible against the nav bar. --vp-c-default-soft renders as #101315 on the dark bar and #eff0f3 on the light one; hover keeps that fill and only changes the border to the brand colour. Below 768px the button stays the bare icon. @nolebase/vitepress-plugin-enhanced-readabilities is dropped: package.json, both CSS imports, the nav bar and screen menu components, and the SSR noExternal entry. Its menu node was also why the default nav menu could not be shown in the 768-959px band; the tab row carries the nav entries, and that band keeps the hamburger and screen menu. scripts/check-rendered-links.sh now expects one active-version marker per static page instead of two: the mobile copy lives inside VPNavScreen's v-if="open" and never reaches the rendered HTML. Verified with npm run typecheck, npm run build and LC_ALL=C bash scripts/check-rendered-links.sh --clean (0 failures), plus headless Chromium measurements over CDP at 1440/1600/1920/960/800 in both appearances: no horizontal page overflow, one marker per page, no console errors.
fix(theme): unify the nav bar and tab row boundaries
Replace the English and Chinese 6.4.0 release-notes drafts with the final release text, including the five modules released at 2.1.0 (UltiLogin, UltiMail, UltiKits, UltiTrade, UltiRemoteBag) with links. Drop the Draft label from both sidebars and from the older-servers guide's link. Co-authored-by: a <a@a> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* docs(versions): freeze the published 6.3.2 documentation Cut docs/archive/v6.3.2 and examples-archive/v6.3.2 with scripts/archive-version.sh from published master 29f2980, and freeze the 6.3.2 guide sidebars from the same commit, with API navigation pinned to the 6.3.2 Javadoc. Register v6.3.2 in ARCHIVE_SIDEBARS, BACKFILL_VERSIONS and the sidebar checker's exact runtime-route exemptions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(versions): advance the documentation to 6.4.0 Set versionsConfig.current to v6.4.0 and examples/pom.xml's ultitools.version to 6.4.0, and point the bilingual Release Notes navigation at the 6.4.0 notes. examples/ and the version-consistency check need Maven Central to serve UltiTools-API 6.4.0 before they pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(versions): point current dependency snippets at 6.4.0 The version switch left the Maven and Gradle coordinates in the current quick-start and external plugin API guides (both locales) at 6.3.2. Historical "as of v6.3.2" statements and release notes are unchanged, and archived pages are untouched. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: a <a@a> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Deploying ultitools-dev-doc with
|
| Latest commit: |
a235777
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://56210403.ultitools-dev-doc.pages.dev |
| Branch Preview URL: | https://alpha.ultitools-dev-doc.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release the UltiTools-API 6.4.0 documentation: promote
alphatomaster(dev.ultikits.com deploys frommaster).UltiTools-API 6.4.0 is published on Maven Central and as the GitHub release
v6.4.0of UltiTools-Reborn.What this ships
archive/v6.3.2, with frozen examples and sidebars, and the site's current version moved to 6.4.0 (versionsConfig.current,examples/pom.xml, current dependency snippets) (docs: archive v6.3.2 and advance the documentation to v6.4.0 #191).alphasince the last promotion (release: promote alpha to master (site fixes, 6.3.x doc corrections) #182): 6.4.0 older-server module support and start-up diagnostics (docs: v6.4.0 framework guidance (scheduled tasks, crash-safe YAML) #151, docs(compat): document pre-1.21 module support for 6.4.0 #152), the removed legacy config parser API (docs(config): legacy config parser API removed in v6.4.0 #181), and the theme navigation boundary fix (fix(theme): unify the nav bar and tab row boundaries #188).Checks
All required checks passed on
alphabefore this promotion, including the examples compile against UltiTools-API 6.4.0 from Maven Central and the version-consistency check.🤖 Generated with Claude Code