📘 Update guestbook updates branch

.github/workflows/crowdin-download-workflow.yml

@@ -1,14 +1,15 @@
 name: Crowdin Download Action
 
 on:
+  workflow_call:
   workflow_dispatch:
     inputs:
       target_branch:
         description: "Branch to run this workflow on"
         required: true
         default: "main"
-  schedule:
-    - cron: '25 20 * * *' # Runs daily at 20:25 UTC (15:25 Central)
+  # schedule:
+  #   - cron: "20 14,18,22 * * 1,2,3,4,5" # Runs at 20 minutes past beginning/middle/end of day Mon-Fri (UTC-6) (an hour after the upload action)
 
 permissions:
   contents: write
@@ -19,10 +20,8 @@ jobs:
     runs-on: ubuntu-latest
 
     env:
-      TARGET_BRANCH:
-        ${{ github.event.inputs.target_branch || 'main' }}
-      BRANCH_NAME:
-        feature/crowdin-download-${{ github.event.inputs.target_branch || 'main' }}
+      TARGET_BRANCH: ${{ github.event.inputs.target_branch || 'main' }}
+      BRANCH_NAME: feature/crowdin-download-${{ github.event.inputs.target_branch || 'main' }}
 
     steps:
       - name: Checkout target branch

.github/workflows/crowdin-manual-workflow.yml

@@ -0,0 +1,12 @@
+name: Crowdin Manual Upload and Download
+
+on:
+  workflow_dispatch:
+
+jobs:
+  trigger-upload:
+    uses: ./.github/workflows/crowdin-upload-workflow.yml
+
+  trigger-download:
+    needs: [ trigger-upload ]
+    uses: ./.github/workflows/crowdin-download-workflow.yml

.github/workflows/crowdin-upload-workflow.yml

@@ -1,9 +1,10 @@
 name: Crowdin Upload Action
 
 on:
+  workflow_call:
   workflow_dispatch:
-  schedule:
-    - cron: '25 13 * * *' # Runs daily at 13:25 UTC (08:25 Central)
+  # schedule:
+  #   - cron: "20 13,17,21 * * 1,2,3,4,5" # Runs at 20 minutes past beginning/middle/end of day Mon-Fri (UTC-6)
 
 jobs:
   crowdin-upload:

Dockerfile

@@ -24,12 +24,13 @@ RUN yarn stellar-cli:build --no-minify --cli-ref=main
 RUN yarn stellar-cli:fix-links
 
 ENV NODE_OPTIONS="--max-old-space-size=4096"
-RUN if [ "$BUILD_TRANSLATIONS" = "True" ]; then \
-    yarn docusaurus build --no-minify; \
-  else \
-    # In the preview build, we only want to build for English. Much quicker
-    yarn build --no-minify; \
-  fi
+# RUN if [ "$BUILD_TRANSLATIONS" = "True" ]; then \
+#     yarn docusaurus build --no-minify; \
+#   else \
+#     # In the preview build, we only want to build for English. Much quicker
+#     yarn build --no-minify; \
+#   fi
+RUN yarn build --no-minify
 
 FROM nginx:1.29
 

README.md

@@ -15,8 +15,6 @@ Welcome to the official home repository for [Documentation][docs] for the [Stell
 - [Using Markdown](#using-markdown)
   - [Markdown Basics](#markdown-basics)
   - [Custom Markdown](#custom-markdown)
-    - [Alert](#alert)
-    - [Code Example](#code-example)
 
 ## Contributing
 
@@ -151,44 +149,39 @@ Our repository uses some custom React components that can be used inside the
 **Make sure that there is an empty line within the wrapper.** For example,
 
 ```text
-<Alert>
+<CodeExample>
 <!-- EMPTY LINE AFTER THE COMPONENT'S OPENING TAG IS REQUIRED -->
 
-Note: the testnet is reset every three months, so when building on it, make sure you have a plan to recreate necessary accounts and other data. For more info, check out the [best practices for using the testnet](../../learn/fundamentals/networks.mdx).
-
-<!-- EMPTY LINE BEFORE THE COMPONENT'S CLOSING TAG IS REQUIRED -->
-</Alert>
+```javascript
+console.log("hello world");
 ```
 
-#### Alert
-
-![Testnet reset alert](./readme-imgs/alert.png)
-
-`<Alert />` is used to convey hints, warnings, etc. For example,
-[Build a SEP-31 Anchor on Testnet][alert-example]
-
-```markdown
-import { Alert } from "@site/src/components/Alert";
-
-<Alert>
-
-Note: the testnet is reset every three months, so when building on it, make sure you have a plan to recreate necessary accounts and other data. For more info, check out the [best practices for using the testnet](../../fundamentals-and-concepts/testnet-and-pubnet).
+```python
+print("hello world")
+```
 
-</Alert>
+<!-- EMPTY LINE BEFORE THE COMPONENT'S CLOSING TAG IS REQUIRED -->
+</CodeExample>
 ```
 
 #### Code Example
 
 ![Create account code example](./readme-imgs/code-example.png)
 
-`<CodeExample />` is a code snippet component. You can include snippets for more
-than one language. See an example including a snippet for `JavaScript` and
-`Python` below. It is using [Prism React Renderer][prism] for syntax
-highlighting.
+`<CodeExample />` is a code snippet component. You can use this component when
+you want to include snippets for more than one language. See an example
+including a snippet for `JavaScript` and `Python` below. It is using [Prism
+React Renderer][prism] for syntax highlighting. If you're only making a code
+snippet for a _single programming language_, you should just stick with a
+"normal" markdown code fence using backticks.
 
-````markdown
-import { CodeExample } from "@site/src/components/CodeExample";
+> [!NOTE]
+> The `CodeExample` component has been added to the list of globally available
+> components, in `/src/theme/MDXComponents.ts`. This means it's not required to
+> `import { CodeExample } ...` in a page if you're planning to use it. It's just
+> always available in MDX file.
 
+````markdown
 <CodeExample>
 
 ```js
@@ -222,21 +215,30 @@ Languages that are currently being used in Documentation and API Reference are
 below:
 
 ```js
-// https://github.com/stellar/stellar-docs/blob/main/src/components/CodeExample.js
+// https://github.com/stellar/stellar-docs/blob/main/config/constants.ts
 
-const CODE_LANGS = {
+export const CODE_LANGS = {
   bash: 'bash',
   cpp: 'C++',
   curl: 'cURL',
+  dart: 'Flutter',
+  flutter: 'Flutter',
+  swift: 'Swift',
+  docker: 'Dockerfile',
   go: 'Go',
   html: 'html',
+  kotlin: 'Kotlin',
+  kt: 'Kotlin',
   java: 'Java',
   javascript: 'JavaScript',
   js: 'JavaScript',
   json: 'JSON',
   json5: 'JSON5',
   python: 'Python',
   scss: 'SCSS',
+  sql: 'SQL',
+  rust: 'Rust',
+  php: 'PHP',
   toml: 'TOML',
   ts: 'TypeScript',
   tsx: 'TSX',
@@ -248,7 +250,6 @@ const CODE_LANGS = {
 **Remember that this is a community; we build together! 🫱🏻‍🫲🏽 Our code of conduct is [here](https://www.stellar.org/community/code-of-conduct) and our Privacy Policy is [here](https://www.stellar.org/privacy-policy).**
 
 [docs]: https://developers.stellar.org/docs
-[api]: https://developers.stellar.org/docs/data/apis
 [stellar]: https://stellar.org
 [contrib]: https://github.com/stellar/.github/blob/master/CONTRIBUTING.md
 [coc]: https://github.com/stellar/.github/blob/master/CODE_OF_CONDUCT.md