<commit_before>Philosophy: one thing to do things

Questions:

-   "The props object and the state object of an observer component are automatically
    made observable to make it easier to create @computed properties that derive from props inside such a component." - Does the props bit still apply to function
    component. Though computed doesn't apply anyhow, unless `useLocalStore` is in
    use.

-   What to do about the egghead lessons? They have a reference the decorator
    syntax. -> consolidate into a single page and explain the decorator story on it.

-   The README is rather long. Credits, testimonials, and sponsors in multiple
    places.

-   How to name "compatible property tracking" as opposed to proxy-based?
    How does one configure it, or it is an automatic fallback?

-   What to do about translations? They will be out of date.

-   Is there a way to regenerate assets? flow.png for instance uses
    decorators and needs to be updated.

-   When we introduce actions we need a link to an actions section that describes
    how to turn off strict state reinforcing.

Todo

-   [ ] Netlify preview for docs PR.
-   [ ] Any code sandbox links need to be updated. jsfiddle as well.
-   [ ] Codemod might change to a new package to reduce size. Documentation needs to be updated.
-   [ ] There are a lot of references to external documentation resources. They can probably use a pruning.
-   [ ] We can still write a separate document that introduces "observable" and explains you need to wrap things in `action` if you want to modify things. Is that the right way forward?
-   [ ] Update the 'Getting started tutorial'? It's maintained separately from the documentation - should we attempt to integrate it? The problem with that it is has live code. Docusaurus can run React snippets but the HTML page has very fancy animations. Update it as is?
-   [ ] Remove reference to the https://github.com/mobxjs/mobx-react-boilerplate projects, modify github README there that it's out of date and retired.

Fragments
<commit_msg>todo item.<commit_after>Philosophy: one thing to do things

Questions:

-   "The props object and the state object of an observer component are automatically
    made observable to make it easier to create @computed properties that derive from props inside such a component." - Does the props bit still apply to function
    component. Though computed doesn't apply anyhow, unless `useLocalStore` is in
    use.

-   What to do about the egghead lessons? They have a reference the decorator
    syntax. -> consolidate into a single page and explain the decorator story on it.

-   The README is rather long. Credits, testimonials, and sponsors in multiple
    places.

-   How to name "compatible property tracking" as opposed to proxy-based?
    How does one configure it, or it is an automatic fallback?

-   What to do about translations? They will be out of date.

-   Is there a way to regenerate assets? flow.png for instance uses
    decorators and needs to be updated.

-   When we introduce actions we need a link to an actions section that describes
    how to turn off strict state reinforcing.

Todo

-   [ ] Netlify preview for docs PR.
-   [ ] Any code sandbox links need to be updated. jsfiddle as well.
-   [ ] Codemod might change to a new package to reduce size. Documentation needs to be updated.
-   [ ] There are a lot of references to external documentation resources. They can probably use a pruning.
-   [ ] We can still write a separate document that introduces "observable" and explains you need to wrap things in `action` if you want to modify things. Is that the right way forward?
-   [ ] Update the 'Getting started tutorial'? It's maintained separately from the documentation - should we attempt to integrate it? The problem with that it is has live code. Docusaurus can run React snippets but the HTML page has very fancy animations. Update it as is?
-   [ ] Remove reference to the https://github.com/mobxjs/mobx-react-boilerplate projects, modify github README there that it's out of date and retired.
-   [ ] makeAutoObservable is handy, but you probably shouldn't use it on a React component to make local state observable. We should say that somewhere.

Fragments

{'fraction_non_alphanumeric': 0.04798870853916726, 'fraction_numerical': 0.0, 'mean_word_length': 3.51380042462845, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3772940', 'n_tokens_mistral': 1096, 'n_tokens_neox': 1053, 'n_words': 634}