Juho Vepsäläinen

Figure out how to relay attributes to components while retaining props

2

Use case: ```json { "type": "SiteLink", "attributes": { "aria-label": "Read more about Seminole tax hike" }, "props": { "children": "Buy tickets", "href": "https://ti.to/future-frontend/2023" } } ``` There are times when...

grapesjs has a powerful client-side editor and it may be worth studying in detail to understand how to expand the existing editor.

As shown by https://deno.com/blog/v1.38, using string concatenation has performance benefits. Porting breezewind to use the same idea may be worth a go if performance becomes an issue.

The idea would be to consume data (for example https://github.com/ReactFinland/graphql-api) and then generate JSON files as a static API. This would need a custom renderer plugin and some logic on...

The development server should restart if the project plugin definition changes. Now it's using a static lookup which is enough for most use cases as the definition doesn't change often.

Set up an incremental compiler

1

The idea would be to check an earlier compilation (hash against the JSON files?) and avoid compilation when possible. The current design already allows this but extra logic is needed.

http://jsonpatch.com/

Attach meta information to components

1

This should contain component name, description, examples, dependencies, and the component declaration. Likely a good convention would be to do `Component.meta.json` so that the information goes to a separate file...

Likely markdown transform needs to communicate this to the render result that's then able to attach highlight.js CSS to the `` based on need.

It should be possible to adjust the entire site (i.e. urls and related pages).