Repository navigation
Correct stale statements on tala.run and rename the vxs storage keys - #35
Merged
Merged
Conversation
An audit of the site against the compiler repository found statements that no longer hold, in all four languages: - the overview named BUILD.kts as the project definition, while Tazel reads one of five names; it now says a project file, BUILD.kts or one of four other names; - the overview and the getting-started guide named Windows and macOS as the only development hosts. Ubuntu 26.04 LTS and Fedora 43 are official hosts too, and the guide says which toolchain they use; - the getting-started guide listed the counterparts of the examples in C#, C++ and Java; the examples also have Rust ones; - the project-file page wrote build/debug/Example without the .exe a Windows build has. The talac, Tazel and syntax pages were checked against Documents/CLI.md, Documents/PROJECT_FILES.md and Spec/Language and are otherwise accurate. Of the 43 links in the repository, only the address inside the Fira Sans licence text no longer answers; that text is third-party and verbatim. The browser storage keys still carried the former name of the language: vxs-locale-choice, vxs-theme and vxs-forum-theme become tala-locale-choice, tala-theme and tala-forum-theme. A value under a former key moves to the current one on the first page load, so no visitor loses a choice; a forum test covers the move. The npm package is renamed from @visual-xsharp/website to @progmasoft/tala-website, and the forum assets get a new version query so Cloudflare serves the new script.
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
1 participant
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.
I checked the site against
Documents/CLI.md,Documents/PROJECT_FILES.md,Spec/Languageand the Examples of the compiler repository.Corrected, in all four languages:
BUILD.kts; it can have one of five names.build/debug/ExampleisExample.exeon Windows.Accurate as they stand: the talac, Tazel and syntax pages. That includes
//rounding,**being right-associative,data/objectand the entry rule.Links: of the 43, only the address inside the Fira Sans licence text no longer answers. That text is third-party and verbatim, so it stays.
Storage keys: the
vxs-*keys becometala-*, and a stored value moves to the new key on the first load. The npm package is renamed to@progmasoft/tala-website, and the forum assets get a new version query.Self-review: read the whole diff and checked the four-language replacements. Format check,
npm test(44),vue-tscandvite buildpass. In the browser, the new Getting Started and Overview text appeared, and the key migration carried over a light theme and a German choice.