Refactor/knowledge types #551
Conversation
✅ Deploy Preview for pr-sliced ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
i18n/en/docusaurus-plugin-content-docs/current/about/understanding/knowledge-types.md
Outdated
Show resolved
Hide resolved
i18n/en/docusaurus-plugin-content-docs/current/about/understanding/knowledge-types.md
Show resolved
Hide resolved
| - **Fundamental knowledge** | ||
| Knowledge that practically does not change over time. | ||
| *Algorithms, computer science, the mechanisms of the YAP and its API, etc.* | ||
| ### Fundamental knowledge |
There was a problem hiding this comment.
question: why did you decide to use headings instead of a list?
In my opinion, this page should not exist in the form that it currently exists in, and instead it should be a part of a larger page discussing the benefits of FSD. With that in mind, I'd actually prefer to shorten this page as much as possible so that it wouldn't occupy too much space when it's merged into another page.
There was a problem hiding this comment.
I think we can refactor itI think we can rewrite it when we paste it into another page. In general, lists with large items are harder to read.
There was a problem hiding this comment.
I agree about the large lists. However, I think we can approach this from another direction by reducing the text content (I'd argue, without losing too much informational value).
I took the liberty of experimenting and came up with this, what do you think about it?
I changed it back into a list and reworded the description of the third point to be shorter.
Text content of that edit for ease of further tweaking
* **Fundamental knowledge**
Knowledge that does not change much over time, such as algorithms, computer science, programming language mechanisms and its APIs.
* **Technology stack**
Knowledge of the set of technical solutions used in a project, including programming languages, frameworks, and libraries.
* **Project knowledge**
Knowledge that is specific to the current project and not valuable outside of it. This knowledge is essential for newly-onboarded developers to be able to contribute effectively.There was a problem hiding this comment.
Introduced the change, let me know if there's anything else you'd like to tweak, otherwise we can merge this
…ding/knowledge-types.md Co-authored-by: Lev Chelyadinov <[email protected]>
…hko/documentation into refactor/knowledge-types
xxtereshko
requested review from
illright
and removed request for
skrylnikov,
sandrig and
unordinarity
Background
Changelog
See diff.