-
Notifications
You must be signed in to change notification settings - Fork 20
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
[docs] Switch NJK to WEBC for layout #1428
Comments
i'm concerned about webc's lack of a satisfying dsd support. as an alternative to webc, I would like us to consider lit-11ty |
yes, that or something like it. the idea being that instead of webc components we'd write uxdot-specific lit components and ssr them by way of dsd, using the plugin |
Do we need a list of Here is a shortlist that exist or might be additionally needed (with screenshots of specific parts I'm referencing):
Anyone have any other elements on the page they think might serve well as uxdot/components? |
Given inclusion with 11ty-plugin-lit, how do we handle eleventy based templating? Are we still using njk for that? Do we just pair that down as much as possible what can go into a component and what can't? Example: I want to loop through 11ty's data cascade? |
we already have docs/assets/elements (iirc) and more in the docs: sample pr |
Ok so the idea is there but no actual way to do that yet. If we are to get this done this quarter, then that doesn't look promising given the timeline. So will we have to fall back to something like: |
maybe lit/lit#2485 (comment) |
Going a different route with components. |
Cleanup for potential move to using elventy-lit-plugin has been done in the docs rewrite PR: #1465 |
Do it.
The text was updated successfully, but these errors were encountered: