Merge pull request #1061 from o1-labs/next-ssr-guide

Add server component cache disclaimer to tutorial 4

.github/workflows/algolia-search.yml

@@ -5,6 +5,7 @@
 #
 
 name: Algolia-Search
+
 on:
   push:
     branches:

docs/zkapps/tutorials/04-zkapp-ui-with-react.mdx

@@ -332,6 +332,12 @@ async setActiveInstanceToDevnet() {
   Depending on the network you are going to work with you might want to consider changing the GraphQL endpoint in the `setActiveInstanceToDevnet` function.
   Mind the supported networks by `Auro Wallet` though.
 
+:::info
+
+In this example, the `o1js` code is included in a client component and executed on the client side using an effect after the page loads. If you're integrating `o1js` within a server component, be aware that Next.js's caching mechanism might cause `o1js` to return outdated data. To prevent this, you can disable caching by adding `export const revalidate = 0;` to your component. For more details, refer to the [Next.js caching documentation](https://nextjs.org/docs/app/building-your-application/caching#opting-out-2).
+
+:::
+
 ### Add state
 
 These `04-zkapp-browser-ui/ui/app/page.tsx` statements creates mutable state that you can reference in the UI. The state updates as the application runs:

docs/zkapps/writing-a-zkapp/feature-overview/offchain-storage.mdx

@@ -185,4 +185,4 @@ This feature remains experimental, indicating that it is currently under active
 
 - [Experimental Offchain Storage part 1](https://github.com/o1-labs/o1js/pull/1630)
 - [Experimental Offchain Storage part 2](https://github.com/o1-labs/o1js/pull/1652)
-- [An end-to-end example utilizing Offchain storage](https://github.com/o1-labs/o1js/blob/main/src/lib/mina/actions/offchain-contract.unit-test.ts)
+- [An end-to-end example utilizing Offchain storage](https://github.com/o1-labs/o1js/blob/main/src/lib/mina/actions/offchain-contract-tests/ExampleContract.ts)