Skip to content

new vitepress 2 page#261

Closed
m1ga wants to merge 1 commit into
mainfrom
vitepress2
Closed

new vitepress 2 page#261
m1ga wants to merge 1 commit into
mainfrom
vitepress2

Conversation

@m1ga

@m1ga m1ga commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Starting from scratch with Vitepress 2

Bildschirmfoto_20260626_000609 Bildschirmfoto_20260626_000617 Bildschirmfoto_20260626_000631 Bildschirmfoto_20260626_000641

Note:
won't work at the moment as it tries to load the Titanium SDK apidocs locally. Will change that tomorrow

@m1ga m1ga marked this pull request as draft June 26, 2026 16:13
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedvitepress@​2.0.0-alpha.17981008689100
Updatedjs-yaml@​3.14.1 ⏵ 4.2.089 -11100 +310091100

View full report

@socket-security

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm js-yaml is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package-lock.jsonnpm/js-yaml@4.2.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/js-yaml@4.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@cb1kenobi

Copy link
Copy Markdown
Member

Shoot, I didn't catch you soon enough. Apologies in advance, but instead of creating a branch off main that nukes all of the files, create a new orphan branch with a fresh history by running git switch --orphan <branch-name>. Forget the pull request, just push to that new orphaned branch. Build the site. Have fun. I can set up CI and deploy whatever you have in that branch to a new.titaniumsdk.com or something. When the site is good, then we simply rename main to old-site or something and rename the orphan branch to main.

@m1ga

m1ga commented Jun 26, 2026

Copy link
Copy Markdown
Contributor Author

ah nice! Didn't know that command 👍 Thanks for the tip. Will do that tomorrow

@m1ga m1ga closed this Jun 27, 2026
@m1ga m1ga deleted the vitepress2 branch June 27, 2026 06:33
@m1ga

m1ga commented Jun 27, 2026

Copy link
Copy Markdown
Contributor Author

done: https://github.com/tidev/titanium-docs/tree/vitepress2

It will now clone all modules and the main sdk repo and I've added the icons back to the platforms box and the links to the header:

Bildschirmfoto_20260627_090952 Bildschirmfoto_20260627_090928 Bildschirmfoto_20260627_091025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants