🗂️ Clean up image paths #2230

JFWooten4 · 2026-02-06T07:57:07Z

This extends great work from #1403 to streamline the file names. A lot of PNG prefixes duplicate the new paths, so they look a little messy. It also introduces standardized lowercase URL paths and descriptive metadata text.

(still need to clarify on min/base fee syntax for 1044)

Id. at link 2

See public drafting at https://x.com/JFWooten4/status/1853966327318520003

- By the time this pull merges, the volume/trade approx should hit. - Fixed missing API doc structure MethodTable explainer. - Added Lumenauts video to SCP explainer for accessability.

Effectively all protocol 18 coverage references AMMs because AMMs are generally the more common industry term. While I appreciate that exact diction can be alluring (https://github.com/orgs/WhyDRS/discussions/21), might we scope the introductory page at least to explain rather than confuse readers?

For diction in _Id_, _see also_ R282 at JFWooten4/free-markets@dba9447#r149283300

And simplify the go newTxBuilder preconditions

Gives defereance to full disaply decimals rather than two-digit truncation. As an aside, are there any reputable anchors using display_digitals in their tomls?

Addresses the logic combination and Go documentation. Since we're using it to build an obj to add ops to, signing should stay as is.

JS translate 1/2 for "DocCard/index" perfects stellar#2116

implements stellar#1828 translated into mermaid

* clawback text * stellarbeat no more I coulds't find an equivalent Atlas replacement * channel accounts * claimable balances setup * format prettier

…ides

This defers to the inline styling from stellar#2188, but keeps it as a flat approach like all the other scripts there, as I don't envision this component growing a whole ton. There is something to be said about video implementations going forward on something like Livepeer, but I'd imagine that'd be something different—like the DriveVideo.tsx.

socket-security · 2026-02-06T07:57:37Z

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		License policy violation: npm `confbox` under BSD-3-Clause AND MIT Location: Package overview From: `?` → `npm/@docusaurus/theme-mermaid@3.9.2` → `npm/confbox@0.2.2` ℹ Read more on: This package \| This alert \| What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/confbox@0.2.2`. 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.
Warn		License policy violation: npm `lightningcss-darwin-arm64` under MPL-2.0 Location: Package overview From: `?` → `npm/@docusaurus/faster@3.9.2` → `npm/lightningcss-darwin-arm64@1.29.3` ℹ Read more on: This package \| This alert \| What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/lightningcss-darwin-arm64@1.29.3`. 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.
Warn		License policy violation: npm `lightningcss-darwin-x64` under MPL-2.0 Location: Package overview From: `?` → `npm/@docusaurus/faster@3.9.2` → `npm/lightningcss-darwin-x64@1.29.3` ℹ Read more on: This package \| This alert \| What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/lightningcss-darwin-x64@1.29.3`. 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.
Warn		License policy violation: npm `lightningcss-freebsd-x64` under MPL-2.0 Location: Package overview From: `?` → `npm/@docusaurus/faster@3.9.2` → `npm/lightningcss-freebsd-x64@1.29.3` ℹ Read more on: This package \| This alert \| What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/lightningcss-freebsd-x64@1.29.3`. 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.
Warn		License policy violation: npm `lightningcss-linux-arm-gnueabihf` under MPL-2.0 Location: Package overview From: `?` → `npm/@docusaurus/faster@3.9.2` → `npm/lightningcss-linux-arm-gnueabihf@1.29.3` ℹ Read more on: This package \| This alert \| What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/lightningcss-linux-arm-gnueabihf@1.29.3`. 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.
Warn		License policy violation: npm `lightningcss-linux-arm64-gnu` under MPL-2.0 Location: Package overview From: `?` → `npm/@docusaurus/faster@3.9.2` → `npm/lightningcss-linux-arm64-gnu@1.29.3` ℹ Read more on: This package \| This alert \| What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/lightningcss-linux-arm64-gnu@1.29.3`. 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.
Warn		License policy violation: npm `lightningcss-linux-arm64-musl` under MPL-2.0 Location: Package overview From: `?` → `npm/@docusaurus/faster@3.9.2` → `npm/lightningcss-linux-arm64-musl@1.29.3` ℹ Read more on: This package \| This alert \| What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/lightningcss-linux-arm64-musl@1.29.3`. 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.
Warn		License policy violation: npm `lightningcss-linux-x64-gnu` under MPL-2.0 Location: Package overview From: `?` → `npm/@docusaurus/faster@3.9.2` → `npm/lightningcss-linux-x64-gnu@1.29.3` ℹ Read more on: This package \| This alert \| What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/lightningcss-linux-x64-gnu@1.29.3`. 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.
Warn		License policy violation: npm `lightningcss-linux-x64-musl` under MPL-2.0 Location: Package overview From: `?` → `npm/@docusaurus/faster@3.9.2` → `npm/lightningcss-linux-x64-musl@1.29.3` ℹ Read more on: This package \| This alert \| What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/lightningcss-linux-x64-musl@1.29.3`. 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.
Warn		License policy violation: npm `lightningcss-win32-arm64-msvc` under MPL-2.0 Location: Package overview From: `?` → `npm/@docusaurus/faster@3.9.2` → `npm/lightningcss-win32-arm64-msvc@1.29.3` ℹ Read more on: This package \| This alert \| What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/lightningcss-win32-arm64-msvc@1.29.3`. 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.
Warn		License policy violation: npm `lightningcss-win32-x64-msvc` under MPL-2.0 Location: Package overview From: `?` → `npm/@docusaurus/faster@3.9.2` → `npm/lightningcss-win32-x64-msvc@1.29.3` ℹ Read more on: This package \| This alert \| What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/lightningcss-win32-x64-msvc@1.29.3`. 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.
Warn		License policy violation: npm `lightningcss` under MPL-2.0 Location: Package overview From: `?` → `npm/@docusaurus/faster@3.9.2` → `npm/lightningcss@1.29.3` ℹ Read more on: This package \| This alert \| What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/lightningcss@1.29.3`. 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.
Warn		License policy violation: npm `protobufjs` under BSD-3-Clause Location: Package overview From: `?` → `npm/@redocly/cli@2.14.1` → `npm/protobufjs@7.5.0` ℹ Read more on: This package \| This alert \| What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/protobufjs@7.5.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

…llar#2219) The phrase "Rust on Stellar" translates poorly in Google Translate for certain languages (e.g., Hindi interprets "Rust on" as "war on"). Renamed to "Developing Smart Contracts" to avoid confusion. Fixes stellar#2191

* Add ZK page to docs * copilot review suggestions * dropdown, content * Update docs/build/apps/zk.mdx Co-authored-by: Elliot Voris <elliot@stellar.org> * Update docs/build/apps/zk.mdx Co-authored-by: Elliot Voris <elliot@stellar.org> * Update docs/build/apps/zk.mdx Co-authored-by: Elliot Voris <elliot@stellar.org> * Update docs/build/apps/zk.mdx Co-authored-by: Elliot Voris <elliot@stellar.org> * new host function descriptions --------- Co-authored-by: Elliot Voris <elliot@stellar.org>

* Testnet reset 2026 dates * 2025->2026

* Adding January meeting notes * Adding January meeting notes

* Initial plan * Add Online IDE (Soropg) page to developer tools * Soroban -> Stellar --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: Bri Wylde <92327786+briwylde08@users.noreply.github.com>

* Add OZ relayer status * Update format

JFWooten4 · 2026-02-06T08:12:24Z

This started on the wrong branch and the last 6 commits got a little messed up.

JFWooten4 added 30 commits October 17, 2024 19:58

Merge branch 'stellar:main' into refresh-classic-guides

33f342e

👽 Translate java to JS

09fffca

🔁 Last example java & go

03d2199

Merge branch 'stellar:main' into refresh-classic-guides

1c8851d

🔁 Closing example explanation, diagrams

cb9687a

🔁 Put back set timeouts

06183cc

🔁 Cleanup remaining frame items

cbe3aca

🔁 Comment active-tense transitive verbs

b45f8b2

🔁 Finalize the story flow

a73d966

🔁 Polish off minor syntax

a3c5d64

🔗 Remove depricated community link

eac05da

🔎 Clarify note on trustlines

91b40fd

🫴🏽 Finish most cleaning up

7109cb5

(still need to clarify on min/base fee syntax for 1044)

Merge branch 'main' into refresh-classic-guides

320de48

🔗 Update simplified syntax reference

0948700

🦞 Clean up final examples

19fbf45

💱 Remove items explicitly moved

75a3ea0

Id. at link 2

💱 Remove duplicate placeholder drafts

9bc3c63

💱 Sidebar section intro description

2a2638c

💱 First rewrite run through

9d01898

See public drafting at https://x.com/JFWooten4/status/1853966327318520003

💱 Clean up scaffolding leftovers

32455bb

- By the time this pull merges, the volume/trade approx should hit. - Fixed missing API doc structure MethodTable explainer. - Added Lumenauts video to SCP explainer for accessability.

💱 Translate starting AMM preamble

da7e8a3

💱 Translate two AMM steps

f8a304f

For diction in _Id_, _see also_ R282 at JFWooten4/free-markets@dba9447#r149283300

📍 Follow up on this

535b09b

💱 Translate removing AMM liquidity

be7abb0

And simplify the go newTxBuilder preconditions

💱 Translate Java wrap-up example

eb18115

Gives defereance to full disaply decimals rather than two-digit truncation. As an aside, are there any reputable anchors using display_digitals in their tomls?

💱 Last legacy, 535b09b fix

f871bab

Addresses the logic combination and Go documentation. Since we're using it to build an obj to add ops to, signing should stay as is.

💱 Clean up go conclusion

b7f4a07

📌 Simplify starting frame, independence

5492eb3

JFWooten4 added 18 commits December 15, 2025 17:37

merge from main (origin)

4989d6b

JS translate 1/2 for "DocCard/index" perfects stellar#2116

local build syntax 1/2

33e09b2

JS translate 2/2

04c4ff6

local build syntax 2/2

ab00f1a

back ts norm yarn

958d97e

canonical Go SDK

13d4880

fix int'l import compatability

6c7f621

merge clawbacks starting diagram

e1ee103

implements stellar#1828 translated into mermaid

🤖 (#15)

356f57b

* clawback text * stellarbeat no more I coulds't find an equivalent Atlas replacement * channel accounts * claimable balances setup * format prettier

remove channel footnote

1347d20

translate migration RPC data calls

03a38ba

Merge https://github.com/stellar/stellar-docs into refresh-classic-gu…

bc5d772

…ides

other 2132 cleanup components

89cd342

Merge https://github.com/stellar/stellar-docs into refresh-classic-gu…

463874d

…ides

Merge https://github.com/stellar/stellar-docs into refresh-classic-gu…

61aba47

…ides

fix broken links, imports

58336e2

start lowercase file names

4154db2

kaankacar and others added 6 commits February 6, 2026 03:02

Testnet reset 2026 dates (stellar#2223)

6d509b4

* Testnet reset 2026 dates * 2025->2026

Adding January meeting notes (stellar#2227)

66c9b7b

* Adding January meeting notes * Adding January meeting notes

Add OZ relayer status (stellar#2226)

79d2161

* Add OZ relayer status * Update format

JFWooten4 force-pushed the organize-paths branch from 6febf0f to 79d2161 Compare February 6, 2026 08:04

JFWooten4 closed this Feb 6, 2026

JFWooten4 mentioned this pull request Feb 6, 2026

🎨 Clean up images, imports #2231

Open

JFWooten4 deleted the organize-paths branch February 6, 2026 20:26

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

🗂️ Clean up image paths #2230

🗂️ Clean up image paths #2230

Uh oh!

JFWooten4 commented Feb 6, 2026

Uh oh!

socket-security bot commented Feb 6, 2026 •

edited

Loading

Uh oh!

JFWooten4 commented Feb 6, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

🗂️ Clean up image paths #2230

🗂️ Clean up image paths #2230

Uh oh!

Conversation

JFWooten4 commented Feb 6, 2026

Uh oh!

socket-security bot commented Feb 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

JFWooten4 commented Feb 6, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

socket-security bot commented Feb 6, 2026 •

edited

Loading