-
Notifications
You must be signed in to change notification settings - Fork 205
Update components/rendering guide #137
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
Conversation
A live preview of this PR will be available at the URL(s) below. https://pr137-ab07dd5---lit-dev-bvxw3ycs6q-uw.a.run.app/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some initial feedback
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't feel like this section is paying for itself. Suggest removing it and just putting links to the other relevant sections in the Overview
: Shadow DOM, Lifecycle, and Template overview.
The part about the performant template maybe can be added as a sub-section to lifecycle#render.
packages/lit-dev-content/site/_includes/projects/docs/templates/compose/my-page.ts
Outdated
Show resolved
Hide resolved
@@ -6,79 +6,66 @@ eleventyNavigation: | |||
order: 2 | |||
--- | |||
|
|||
{% todo %} | |||
A Lit component typically implements its UI by rendering an encapsulated DOM tree. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sentence isn't adding much for me. Remove?
Adds intro, interactive examples.
I am not real happy about the "Designing a performant template" section ... I think the info is good but the example is kind of longwinded. Welcome input on that.
I think Justin was the one who requested adding a "when components render" section, so let me know if this is what you were thinking of. (The info was already kind of there, but previously formed part of the "Designing a performant template" section.)