-
-
Notifications
You must be signed in to change notification settings - Fork 116
docs: improvement of architecture documentation #483
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
@copilot summarize the architecture from a high level overview and describe the interplay between the several packages and their roles. Focus on the purpose of these inter relation and make clear in which stage (build vs. runtime) the specific packages act and interact. |
|
@jankapunkt I've opened a new pull request, #484, to work on those changes. Once the pull request is ready, I'll request review from you. |
…build/runtime stages Co-authored-by: jankapunkt <1135285+jankapunkt@users.noreply.github.com>
…Instance, and View Co-authored-by: jankapunkt <1135285+jankapunkt@users.noreply.github.com>
…eferences View Co-authored-by: jankapunkt <1135285+jankapunkt@users.noreply.github.com>
|
I think we have a CI issue, this PR is not touching any code... |
docs: add comprehensive architecture overview with build/runtime stages, package roles, and key terms
|
|
|
@copilot can you sign the CLA? |
|
@jankapunkt I've opened a new pull request, #485, to work on those changes. Once the pull request is ready, I'll request review from you. |
|
We can continue with this, once #486 is merged |
|
I read through the rendered version, and with my rather limited Blaze knowledge, I find it really helpful. I'm just thinking whether it'd make sense to move the summary to the top, as it's a good mental model for Blaze. Besides that, I'd merge it as-is, since it's much better than the current overview, plus it can be iterated over. |
This is ongoing work on an extensive architecture overview, see #482