Welcome.
You are at a good starting point, but it needs more thought. I’m going to approach this in a way that software developers may find interesting.
- Some code is knowledge, and knowledge is like high-level code:
- Each high-level expression is like a Logseq block.
- High-level, meaning not written for computers, but for humans.
- This includes composite expressions, up to the level of function definitions.
- A composite expression is a hierarchy of Logseq blocks.
- A good atomic note should be relatively easy to transform into code.
- Each high-level module is like a Logseq page.
- High-level, meaning not an arbitrary packaging of related functions, but a local namespace (not Logseq namespace), gathering all functions that model a well-identified concept within a knowledge domain.
- A module is not a datatype, but a unique concept from the perspective of a project.
- A single concept may need multiple datatypes to be fully modeled.
- A concept may be a common word.
- Not every common word is a module.
- Not every common word deserves its own page.
- Should not spam the graph with pages for every single common word.
- Some common words should be fine as common blocks.
- Not every common word is a module.
- Each project is like a Logseq graph.
- A project combines some modules to provide a solution within a company.
- One Logseq graph per project, is the ideal separation.
- Difficult in practice, because of overlapping.
- Each high-level expression is like a Logseq block.
- A journal is a log.
- Logs should be read-only (except for fixing mistakes from the perspective of the past).
- Throughout a project’s life the requirements change.
- In your scenario, that means that some older journal entries become outdated.
- That would turn non-journal pages into a mix of valid info with outdated one.
- In your scenario, that means that some older journal entries become outdated.
- Therefore, a journal cannot serve well as the ultimate source of truth.
- It takes a knowledgeable human to decide which entries remain valid.
- Non-journal pages should be carefully edited to always contain the currently valid info.
Sometimes tools are advertised as if they do everything automatically. Get to know the tool and use it for its real merits.