Danger
Training exercise.

[WEATHER UI](https://creativest.apishowdown.com/weather)

[WEATHER MD](https://creativest.apishowdown.com/weather/md)

## What made you smile?

- The concept of the feature is great.
- Works well with React pages


## What did you find confusing?

- In the docs it's saying that "getServerProps function receives two parameters". But there are actually described 3 parameters.
![Screenshot 2025-03-05 at 15.44.08.png](/assets/screenshot-2025-03-05-at-15.44.08.be540941b2e2b84d5ce40f002414ab55517587bf64b07bebf0718ce71a40271b.9c1bb791.png)
- Inserting `img` markdoc tag in editor produces opening and closing tag (though it is unary tag).
- It is hard to debug what is inside `$pageProps` in markdown pages. We decided to create a tsx page instead and renamed old markdown page. Since we had active and renamed markdown page in file editor - Webview rendered it and got stuck on that url. Full Webview restart did not help to switch to valid url.
- When making changes to react page inside editor Webview reacts on every change and reloads too often and page ends up with javascript errors.
- It is hard to debug what data comes from calls to third-party services inside `.props.ts`.
- We were not able to use api functions endpoint inside `.props.ts` file.
- Working with `$pageProps` in markdown file is very unstable. Sometimes it works, sometimes it crashes, sometimes it does not return any data. Relatead to MD files.
- If `$pageProps` has image link, it is not possible to render image in md file. We tried three ways: `![]()`, image html tag (`<img />`) and image markdoc tag `{% img %}`.
- If `$pageProps` has type integer or float, it breaks md file.