Simon Winter

### Summary **Description:** Like the previous work, the vscode extension should have a side panel that allows people to see details about a particular block. This will mean we have...

### Summary **Description:** Review the existing website repo. If necessary replace Next.js, or set up the skeleton of the page. The page structure itself will be dependent on content that...

### Summary Following on the work of #2174, there are a few issues that have fallen out of this issue: - [x] there are new `in-flow` & `on-demand` components. They...

fix(node colours): Revisit the colour theming for nodes

1

### Summary Currently we're relying on very generic tailwind colours to set our node background colours etc. ```ts const nodeColours = (name: string) => ({ colour: colours[name][100], borderColour: colours[name][200], })...

### Summary Currently there are a couple of challenges to the saving of the settings panel: - [ ] GET ~/secrets is fetched on every page load. It should only...

### Summary The input fields now are designed to have a button which clears the field. Once pressed the field resets. - [ ] Ensure the look and feel matches...

### Summary The latest designs feature an animation when the save me button is pressed: - [ ] Includes an overlay to prevent clicking on any fields while in progress...

### Summary Ensure that the config panel's error states match the latest designs: - [ ] Show an error toast - [ ] highlight the corresponding fields that have errors...

**Description** Updates to allow the theme to be applied inside vscode. Includes: - styling of default theme - changes to layout for node cards (to include a more flexible header)...

Hi there 👋, I originally asked this question in the discussion - willing to help out to document this if necessary! https://github.com/wq/wq/discussions/63 > I'm really enjoying using wq! I remember...