There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: .github/renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: Invalid schedule: 'Invalid schedule: Failed to parse "monday before 5am"'

Context

We currently store a number of RFCs in the root of our blockprotocol/blockprotocol repository on GitHub, under a top-level rfcs directory. We want to leave this where it currently resides.

However, we want to ensure that the accepted RFCs within it (all of those RFC documents available here) are directly browsable on the Þ website, as standalone pages.

Functional Requirements

These standalone pages should:

• be hosted at URLs such as:
  • EITHER blockprotocol.org/docs/spec/roadmap/0352-graph-type-system (in the case of this example RFC);
  • OR if this PR follows completion of #1186, then at blockprotocol.org/roadmap/0352-graph-type-system instead (as roadmap will no longer be found nestled within docs/spec/roadmap, but at the top-level)
• appear in the left-hand navigation sidebar on blockprotocol.org docs and spec pages (e.g. here), nestled beneath the parent page "Roadmap > Proposed Changes > RFCs".

Links to these standalone pages should auto-appear in ascending RFC number order, under the "RFCs" section of the roadmap page, replacing the current "Browse here" link.

Prior work

This work builds on the changes introduced in #1183 ✅ and #1108 ✅ - these are now merged.

_BP-8

Request For Block (RFB)

Creating org charts or plotting any other kind of linked parent/child relationship is not widely supported within existing block-based editors, but such functionality is useful in the context of a linked data graph.

We'd like the ability to create, edit and view parent-child diagrams such as org-charts inline with a block.

🎨 Existing tools and prior art

• LucidChart
• Canva
• SmartDraw
• Creately
• Orginio
• TheOrg

Users can create types, and the detail of those types is shown in two tables (one for properties on the type, and one for links from the type) – for example at https://blockprotocol.org/@hash/types/entity-type/address-block/v/2

This view is currently broken on mobile, because the tables are too wide for the screen. The goal is to implement a working mobile view for this page.

The form itself is generated from a library, and its internal elements should not be styled as part of this solution. One potential and acceptable solution is to wrap the tables with something with a max width, allow a horizontal scrollbar to appear, meaning the user can swipe / scroll to see more of the tables.

Closed by #1210

_{From SyncLinear.com | BP-3}

Following Storybook setup in #1132 and the introduction of support for blocks in Storybook (#1133) we'd like to enable Playwright testing within our instance.

See: https://storybook.js.org/addons/storybook-addon-playwright

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Pending Approval

These branches will be created by Renovate only once you click their checkbox below.

• Replace npm package npm-run-all with npm-run-all2 5.0.0
• Update GitHub Action returntocorp/semgrep to cffeb57
• Update GitHub Action actions/cache to v3.3.3
• Update GitHub Action actions/setup-node to v3.8.2
• Update GitHub Action actions/upload-artifact to v3.1.3
• Update GitHub Action changesets/action to v1.4.7
• Update GitHub Action codecov/codecov-action to v3.1.6
• Update Rust crate serde_json to 1.0.117
• Update Rust crate serde to 1.0.203
• Update Rust crate thiserror to 1.0.61
• Update npm package @babel/plugin-proposal-private-property-in-object to v7.21.11
• Update npm package @blockprotocol/core to v0.1.3
• Update npm package @blockprotocol/hook to v0.1.8
• Update npm package @blockprotocol/service to v0.1.5
• Update npm package @hashintel/design-system to v0.0.8
• Update npm package @hashintel/type-editor to v0.0.25
• Update npm package @mapbox/search-js-core to ^1.0.0-beta.21
• Update npm package @stripe/react-stripe-js to ^1.16.5
• Update npm package @twind/next to ^1.0.10
• Update npm package @types/command-line-args to ^5.2.3
• Update npm package @types/command-line-usage to ^5.0.4
• Update npm package @types/cors to ^2.8.17
• Update npm package @types/dedent to ^0.7.2
• Update npm package @types/dotenv-webpack to ^7.0.7
• Update npm package @types/hosted-git-info to ^3.0.5
• Update npm package @types/is-ci to v3.0.4
• Update npm package @types/lodash.debounce to v4.0.9
• Update npm package @types/md5 to ^2.3.5
• Update npm package @types/mime-types to ^2.1.4
• Update npm package @types/mime to ^3.0.4
• Update npm package @types/nprogress to ^0.2.3
• Update npm package @types/pacote to v11.1.8
• Update npm package @types/passport to ^1.0.16
• Update npm package @types/prompt to ^1.1.8
• Update npm package @types/react-gtm-module to ^2.0.3
• Update npm package @types/react-html-parser to ^2.0.6
• Update npm package @types/tar to ^6.1.13
• Update npm package @types/tmp to ^0.2.6
• Update npm package @types/wait-on to v5.3.4
• Update npm package @types/wordpress__blocks to v11.0.9
• Update npm package babel-loader to ^9.1.3
• Update npm package babel-plugin-inline-react-svg to v2.0.2
• Update npm package formdata-node to ^5.0.1
• Update npm package html-to-text to ^8.2.1
• Update npm package immer to ^9.0.21
• Update npm package json-schema-to-typescript to ^11.0.5
• Update npm package jsonschema to ^1.4.1
• Update npm package micromatch to ^4.0.7 (micromatch, @types/micromatch)
• Update npm package mongodb to ^4.17.2
• Update npm package next-http-proxy-middleware to ^1.2.6
• Update npm package next-session to ^4.0.5
• Update npm package nodemailer to ^6.9.13 (nodemailer, @types/nodemailer)
• Update npm package notistack to ^2.0.8
• Update npm package pacote to v12.0.3
• Update npm package patch-package to v6.5.1
• Update npm package playwright-test-coverage to ^1.2.12
• Update npm package prettier to v2.8.8
• Update npm package react-resizable to ^3.0.5 (react-resizable, @types/react-resizable)
• Update npm package react-toastify to v9.1.3
• Update npm package react-transition-group to ^4.4.5
• Update npm package remark-parse to ^10.0.2
• Update npm package serve-handler to ^6.1.5 (serve-handler, @types/serve-handler)
• Update npm package slugify to ^1.6.6
• Update npm package style-loader to ^3.3.4
• Update npm package styled-jsx to ^5.1.6
• Update npm package suppress-experimental-warnings to ^1.1.17
• Update npm package ts-node to ^10.9.2
• Update npm package twind to ^0.16.19
• Update npm package yarn-deduplicate to v6.0.2
• Update rust-wasm-bindgen monorepo (wasm-bindgen, wasm-bindgen-test)
• Update Font Awesome to v6.5.2 (@fortawesome/fontawesome-svg-core, @fortawesome/free-brands-svg-icons, @fortawesome/free-regular-svg-icons, @fortawesome/free-solid-svg-icons)
• Update GitHub Action Swatinem/rust-cache to v2.7.3
• Update GitHub Action actions/dependency-review-action to v3.1.5
• Update GitHub Action github/codeql-action to v2.25.8
• Update GitHub Action taiki-e/install-action to v2.38.0
• Update Rust crate url to 2.5.0
• Update aws-sdk-js-v3 monorepo to v3.592.0 (@aws-sdk/client-s3, @aws-sdk/client-ses)
• Update babel monorepo to ^7.24.7 (@babel/core, @babel/eslint-parser, @babel/plugin-proposal-decorators, @babel/plugin-transform-runtime, @babel/preset-env, @babel/preset-react, @babel/preset-typescript, @babel/runtime)
• Update dependency sentry/sdk to ^3.6.0
• Update emotion monorepo (@emotion/cache, @emotion/react, @emotion/server, @emotion/styled)
• Update material-ui monorepo (@mui/icons-material, @mui/material, @mui/system)
• Update npm package @blockprotocol/graph to v0.3.4
• Update npm package @changesets/changelog-github to v0.5.0
• Update npm package @changesets/cli to v2.27.5
• Update npm package @cloudflare/stream-react to ^1.9.1
• Update npm package @lit-labs/react to v1.2.1
• Update npm package @next/bundle-analyzer to v13.5.6
• Update npm package @openapitools/openapi-generator-cli to v2.13.4
• Update npm package @rollup/plugin-commonjs to v24.1.0
• Update npm package @rollup/plugin-json to v6.1.0
• Update npm package @rollup/plugin-wasm to v6.2.2
• Update npm package @storybook/testing-library to ^0.2.2
• Update npm package @stripe/stripe-js to ^1.54.2
• Update npm package @types/lodash to v4.17.4
• Update npm package @types/node to ^18.19.34
• Update npm package @types/react-is to v18.3.0
• Update npm package ajv to ^8.16.0
• Update npm package algoliasearch to v4.23.3
• Update npm package axios-retry to v3.9.1
• Update npm package axios to ^1.7.2
• Update npm package busboy to ^1.6.0 (busboy, @types/busboy)
• Update npm package chalk to v5.3.0
• Update npm package check-dependency-version-consistency to v3.3.0
• Update npm package cookie-signature to ^1.2.1 (cookie-signature, @types/cookie-signature)
• Update npm package core-js to ^3.37.1
• Update npm package css-loader to ^6.11.0
• Update npm package date-fns to ^2.30.0
• Update npm package dotenv-flow to v3.3.0 (dotenv-flow, @types/dotenv-flow)
• Update npm package dotenv-webpack to ^8.1.0
• Update npm package echarts to v5.5.0
• Update npm package eslint-config-prettier to v8.10.0
• Update npm package eslint-import-resolver-typescript to v3.6.1
• Update npm package eslint-plugin-import to v2.29.1
• Update npm package eslint-plugin-jest to v27.9.0
• Update npm package eslint-plugin-jsx-a11y to v6.8.0
• Update npm package eslint-plugin-react to v7.34.2
• Update npm package eslint-plugin-storybook to v0.8.0
• Update npm package eslint to v8.57.0
• Update npm package express-session to ^1.18.0 (express-session, @types/express-session)
• Update npm package express-validator to ^6.15.0
• Update npm package framer-motion to v10.18.0
• Update npm package globby to ^13.2.2
• Update npm package html-webpack-plugin to ^5.6.0
• Update npm package knip to ^1.17.0
• Update npm package lint-staged to v13.3.0
• Update npm package lit to ^2.8.0
• Update npm package lockfile-lint to v4.13.2
• Update npm package markdownlint-cli2 to v0.13.0
• Update npm package material-ui-popup-state to ^5.1.2
• Update npm package next-connect to ^0.13.0
• Update npm package next-mdx-remote to ^4.4.1
• Update npm package next-seo to ^5.15.0
• Update npm package node to >=16.20.2
• Update npm package openai to ^3.3.0
• Update npm package passport to ^0.7.0
• Update npm package prettier-plugin-packagejson to v2.5.0
• Update npm package prettier-plugin-sh to v0.14.0
• Update npm package prismjs to ^1.29.0 (prismjs, @types/prismjs)
• Update npm package react-hook-form to v7.51.5
• Update npm package react-slick to ^0.30.2 (react-slick, @types/react-slick)
• Update npm package remark-mdx to ^2.3.0
• Update npm package rollup to v3.29.4
• Update npm package sanitize-html to v2.13.0 (sanitize-html, @types/sanitize-html)
• Update npm package sass to ^1.77.4
• Update npm package slate-react to ^0.105.0
• Update npm package slate to ^0.103.0
• Update npm package stripe to ^11.18.0
• Update npm package suppress-exit-code to v3.2.0
• Update npm package ts-jest to v29.1.4
• Update npm package ts-loader to v9.5.1
• Update npm package tslib to v2.6.3
• Update npm package turbo to v1.13.4
• Update npm package typescript-json-schema to ^0.63.0
• Update npm package typescript to v4.9.5
• Update npm package use-local-storage-state to ^18.3.3
• Update npm package webpack-assets-manifest to ^5.2.1 (webpack-assets-manifest, @types/webpack-assets-manifest)
• Update npm package webpack-bundle-analyzer to v4.10.2 (webpack-bundle-analyzer, @types/webpack-bundle-analyzer)
• Update npm package webpack-cli to ^5.1.4
• Update npm package webpack-dev-server to ^4.15.2
• Update npm package webpack to v5.91.0
• Update playwright monorepo to ^1.44.1 (@playwright/test, playwright)
• Update react monorepo (@types/react, @types/react-dom, eslint-plugin-react-hooks, react, react-dom)
• Update rjsf monorepo to v5.18.4 (@rjsf/core, @rjsf/utils, @rjsf/validator-ajv8)
• Update sentry-javascript monorepo (@sentry/integrations, @sentry/nextjs, @sentry/react)
• Update storybook monorepo to ^7.6.19 (@storybook/addon-essentials, @storybook/addon-interactions, @storybook/addon-links, @storybook/blocks, @storybook/react, @storybook/react-webpack5, storybook)
• Update typescript-eslint monorepo to v5.62.0 (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Update wordpress monorepo (@wordpress/api-fetch, @wordpress/block-editor, @wordpress/blocks, @wordpress/components, @wordpress/data, @wordpress/scripts)
• Update GitHub Action actions/cache to v4
• Update GitHub Action actions/checkout to v4
• Update GitHub Action actions/dependency-review-action to v4
• Update GitHub Action actions/labeler to v5
• Update GitHub Action actions/setup-node to v4
• Update GitHub Action actions/upload-artifact to v4
• Update GitHub Action andstor/file-existence-action to v3
• Update GitHub Action codecov/codecov-action to v4
• Update GitHub Action github/codeql-action to v3
• Update dependency sentry/sdk to v4
• Update npm package @apidevtools/json-schema-ref-parser to v11
• Update npm package @fortawesome/fontawesome-svg-core to v6
• Update npm package @lit-labs/react to v2
• Update npm package @next/bundle-analyzer to v14
• Update npm package @rollup/plugin-commonjs to v26
• Update npm package @rollup/plugin-typescript to v11
• Update npm package @stripe/react-stripe-js to v2
• Update npm package @stripe/stripe-js to v3
• Update npm package @types/wordpress__block-editor to v11
• Update npm package @types/wordpress__blocks to v12
• Update npm package ajv-formats to v3
• Update npm package axios-retry to v4
• Update npm package check-dependency-version-consistency to v4
• Update npm package clsx to v2
• Update npm package command-line-usage to v7
• Update npm package concurrently to v8
• Update npm package connect-mongo to v5
• Update npm package copy-webpack-plugin to v12
• Update npm package css-loader to v7
• Update npm package date-fns to v3
• Update npm package dedent to v1
• Update npm package dotenv-flow to v4
• Update npm package envalid to v8
• Update npm package es-module-lexer to v1
• Update npm package eslint-config-prettier to v9
• Update npm package eslint-plugin-jest to v28
• Update npm package eslint-plugin-simple-import-sort to v12
• Update npm package eslint-plugin-unicorn to v53
• Update npm package eslint to v9
• Update npm package execa to v9
• Update npm package express-validator to v7
• Update npm package find-up to v7
• Update npm package formdata-node to v6
• Update npm package framer-motion to v11
• Update npm package fs-extra to v11 (fs-extra, @types/fs-extra)
• Update npm package globby to v14
• Update npm package hosted-git-info to v7
• Update npm package html-to-text to v9 (html-to-text, @types/html-to-text)
• Update npm package husky to v9
• Update npm package immer to v10
• Update npm package json-schema-to-typescript to v14
• Update npm package knip to v5
• Update npm package lint-staged to v15
• Update npm package lit to v3
• Update npm package mime to v4 (mime, @types/mime)
• Update npm package mongodb to v6
• Update npm package next-connect to v1
• Update npm package next-mdx-remote to v5
• Update npm package next-seo to v6
• Update npm package node to v20 (node, @types/node)
• Update npm package notistack to v3
• Update npm package openai to v4
• Update npm package pacote to v18
• Update npm package patch-package to v8
• Update npm package prettier to v3
• Update npm package react-toastify to v10
• Update npm package realm-web to v2
• Update npm package remark-mdx to v3
• Update npm package rimraf to v5
• Update npm package rollup to v4
• Update npm package sass-loader to v14
• Update npm package stripe to v15
• Update npm package style-loader to v4
• Update npm package suppress-experimental-warnings to v2
• Update npm package turbo to v2
• Update npm package typescript to v5
• Update npm package unified to v11
• Update npm package untildify to v5
• Update npm package use-local-storage-state to v19
• Update npm package uuid to v9.0.1 (uuid, @types/uuid)
• Update npm package wait-on to v7
• Update npm package webpack-dev-server to v5
• Update remark (major) (remark-gfm, remark-parse)
• Update sentry-javascript monorepo to v8 (major) (@sentry/nextjs, @sentry/react)
• Update storybook monorepo to v8 (major) (@storybook/addon-essentials, @storybook/addon-interactions, @storybook/addon-links, @storybook/blocks, @storybook/react, @storybook/react-webpack5, storybook)
• Update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Update wordpress monorepo (major) (@wordpress/api-fetch, @wordpress/block-editor, @wordpress/blocks, @wordpress/components, @wordpress/data, @wordpress/scripts)
• 🔐 Create all pending approval PRs at once 🔐

Pending Status Checks

These updates await pending status checks. To force their creation now, click the checkbox below.

• Update npm package nyc to v17
• Update npm package uuid to v10

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update npm package sanitize-html to v2.12.1 [SECURITY]
• Update jest monorepo (@types/jest, jest)

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• Update npm package sharp to ^0.32.0 [SECURITY]
• Update npm package tar to v6.2.1 [SECURITY]

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Request For Block (RFB)

Given a set of availability rules, dates or a calendar allow end users of a block to book events on an external calendar inline wherever this block is embedded. The target cal/source to check availability via would be editable when viewing the block in edit-mode. When in view-only mode, users should be constrained to making bookings only.

Could additionally support Cal.com/Calendly/equivalent services via their APIs where available, rather than requiring embedding apps to integrate with calendar sources directly, or block embedders to configure direct connections via a block's settings.

🚀 Potential future extensions

• Resource-linked appointment bookings where calendar availability is not the only constraining factor (i.e. things like inventory or room availability can be taken into account through simple logical operators - or something like ownership of a specific NFT, which Cal enables)
• Optional payment processing inline, as afforded by Calendly's Stripe integration, services like Square Appointments

🎨 Existing tools and prior art

• Calendly
• Cal - available under AGPL this could potentially be wrapped? 🤔 UK-based, too, and also super open. Founders: @baileypumfleet @PeerRich -- aligned thesis and goals?
• Fantastical Scheduling

Currently it is only showing as active when on the "General" page. This should be extended to "Billing" and "API Keys" as well.

_{From SyncLinear.com | BP-21}

Community members in China have reached out to us about providing translations of the specification and docs site.

We use NextJS on the Block Protocol website. This makes it easy to support internationalization of content, but some set up work is required. See https://nextjs.org/docs/advanced-features/i18n-routing

We're interested in hearing from community members with interest in helping us get the site ready for i18n, or who wish to provide translations.

Following #1132 we'd like to be able to load blocks into Storybook, in preparation for running Playwright tests.

See also hashintel/hash#2278

Request For Block (RFB)

In workspace and content management-style applications that utilize blocks the ability to record and store audio and video inline is useful.

We'd like to see a block which employs commonly supported browser APIs such as MediaDevices and MediaStream to allow users to record webcam/audio input which embedding applications can then save.

🎨 Existing tools and prior art

• Loom

@CiaranMn Please can you add new package summaries to section 2 of the ‘Repository contents’ bit of the root README.md — it contains 4 pkgs, but we now have a few more that can be added: https://github.com/blockprotocol/blockprotocol/tree/main/packages Cheers.

Request For Block (RFB)

Quick radio-button poll block to easily allow single-option voting on questions.

To be expanded upon here. Discussion encouraged below.

🤩 Inspired by

• Twitter Polls

_{From SyncLinear.com | BP-20}

Request For Block (RFB)

Kanban-like columnar boards for easily viewing and sorting information in a visual fashion.

To be expanded upon here. Discussion encouraged below.

🤩 Inspired by

• Trello
• Asana

📚 Background reading

• Kanban boards on Wikipedia

We intend to add search functionality to the Block Protocol Hub. While it's just our minimal set of example/starter blocks it's not hard to locate what you're looking for. But as the library grows we expect this to become useful.

In the meantime block search is available via the API (blockprotocol.org account required).

When visiting anchor links on certain pages, the title may be obscured/hidden behind the navbar. This should be in view. See the attached example.

_{From SyncLinear.com | BP-22}

We should look into reconfiguring it, or manually approve affected PRs until such time as we support direct upload on the BP site itself.

• Originally posted by @CLAassistant in #183 (comment)

See: Add the Save in 1Password button to your website (1Password developer documentation)

Follow the above docs to build a save request and then add the button to the API Keys page on the Þ site to allow users to save directly to their password managers.

API keys should use the identity value for the data attribute type.

Please note: the Save to 1Password button does not work on iOS or Android, so the button should be omitted when the page is viewed on mobile devices.

Figma designs to follow.

_BP-11

I'm trying to create a new block app, with the instructions on this page [edit: added link]. I use the following commands:

npx create-block-app test-block
cd test-block
yarn install

The yarn install command fails with the following error:

[3/4] ⠈ mock-block-dock
error /Users/austin/projects/test-block/node_modules/mock-block-dock: Command failed.
Exit code: 1
Command: yarn build
Arguments:
Directory: /Users/austin/projects/test-block/node_modules/mock-block-dock
Output:
yarn run v1.22.17
$ yarn clean; yarn build:cjs; yarn build:esm
$ rimraf ./dist/
$ tsc --p tsconfig.build.json --module commonjs --outDir dist/cjs
error TS5058: The specified path does not exist: 'tsconfig.build.json'.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
$ tsc --p tsconfig.build.json
error TS5058: The specified path does not exist: 'tsconfig.build.json'.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I'm on macOS version 12.1 / Node v16.3.1 / npm v8.4.0 / yarn 1.22.17. Please let me know if you need any more details -- I'd really like to contribute to this project. Thanks in advance!

Request For Block (RFB)

An inline way to quickly generate 'guesstimates' re: the probability of anything happening, similar to the functionality provided on GetGuesstimate.com, or perhaps even using/extending it's open-source core.

To be expanded upon here. Discussion encouraged below.

🤩 Inspired by

• @OAGr / Ozzie Gooen's awesome Guesstimate application.

The log in/sign up buttons in the header of the blockprotocol.org website appear in highly delayed fashion when on slow internet.

Once the /api/me query returns, either an avatar OR sign in / sign up buttons will appear.

We want to reduce the layout shift that occurs, which results in nav elements appearing to jump about, or appear out of the blue.

_BP-18

In the same way we animate the transition between "Blocks" and "Types" in the listings sidebar on https://blockprotocol.org/hub, we want to ensure that the purple "Active" indicator under the "Dashboard" and "My Account" tabs (e.g. as seen at https://blockprotocol.org/dashboard) animates upon switching between them. The same animation style can be used here as was used previously on the Hub.

_{From SyncLinear.com | BP-23}

This dashboard has moved. Please see #1321

You can see a list of all types a user has created on their profile page, for example: https://blockprotocol.org/@hash/all-types

This view is broken on mobile because the card for each type can go off the screen – possibly because of the white-space: pre on the a. The main goal is to have this list view correctly on mobile, and not overflow the screen horizontally (and a horizontal scroll bar should not appear).

It would be nice to maintain whitespace formatting in the descriptions inside each card – for example, this card's description is supposed to have a line-break which is lost when white-space: pre is removed. But this is not a hard requirement if it proves difficult – the main goal is to avoid horizontal overflow.

_BP-1

Is your feature request related to a problem? Please describe.
Hello! I was thinking about building some kind of block based editor for email templates with mjml, and I came across this open source spec! I found it interesting but since my current application is using nuxt (or vue), the starter templates don't exactly match what I'm looking for

Describe the solution you'd like
I know it means more maintenance from the library side, so it's just a request here, but it would be great to see a create-block-app starter template for vue/nuxt that works out of the box, it would be great if it could include some documentation regarding things like monorepos since I would kind of like to develop separate blocks package e.g. block-mj-text, export it out and use it in my main nuxt application for an editor, kind of like this react example here https://github.com/usewaypoint/email-builder-js/tree/main/packages
It would be great if the development workflow could be simplified to the point like this where there's just an output html/vue/whatever component that's exported, and I can just use it without worrying about build config e.g. minimal package that exports a single vue component https://github.com/Esposter/Esposter/tree/main/packages/block-mj-text
I share the same rollup/tsconfig things across my packages (and .tsconfig is mainly generated by nuxt), so would need some guidance on what configuration is absolutely necessary for the build for blocks to work and how I could fit the block protocol workflow into developing separate block packages like this with minimum maintenance, it would be great to at least hear some thoughts, thanks!

The current state of my pnpm monorepo for reference if it helps:
https://github.com/Esposter/Esposter/tree/main/packages

Example block-based editors that I was inspired by:
https://emailbuilder.top
https://usewaypoint.github.io/email-builder-js/#sample/reservation-reminder

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Following #1379, we want to replace the currently out-of-date block preview panel on block preview pages with a full-width embedded version of mock-block-dock.

Request For Block (RFB)

Venn diagrams are useful for pedagogic and classification purposes. They are primarily useful in helping visualize relationships between sets of entities. A block that allows for the easy inline creation and editing (and/or viewing) of Venn diagrams would be beneficial. As with many types of diagrams this is not a capability commonly found in existing block-based editors today.

Features to support

The above graphic from Canva illustrates the various components of Venn diagrams.

Text font, size and color, as well as shape size, color and arrange should be customizable.

Description pending.

See https://www.figma.com/file/Fpmde3E9nJMb4VLkPTYgrM/blockprotocol.org?node-id=3896%3A28986&t=NttHCDekRCmydJgO-1 (private)

_BP-10

We'd like users to be able to create and manage blocks and schemas within shared organizational namespaces, and not just under single-user personal accounts. We'll be adding this functionality soon.

Issue description coming soon.

Public Figma link to be added.

_{From SyncLinear.com | BP-5}

The generated app feels a little outdated:

• It doesn't support nullish coalescing (in my case in an imported es6 third party module)
• Using old versions of webpack
• Uses outdated version of babel (why is it using babel in a typescript project?)

FWIW I see the potential and have some components that would be very suitable with very little work, but the lack of nullish coalescing and my unfamiliarity with babel started to make it a chore.

I don't mean to be negative, and am sorry that the above is all I can contribute at the moment,

Our current process for listing blocks on the Block Protocol Hub requires users to open a Pull Request against this repository under a hub/@[your-username] folder.

This process doesn't scale with the registry's ambition to provide a home for all blocks, but didn't require us to write any custom code when getting the website up quickly -- so was our starting practice.

Going forward we want users to be able to upload blocks by simply linking to external third-party repositories or packages hosted elsewhere, and do this directly from the BP website (as well as perhaps a command line tool). Additionally, we'd like to allow users to create private blocks that are only visible to other users within their org or who have a particular permission set, similar to how private npm packages work.

On the page documenting how to link data between entities the example for the user has an entityId of 41 but the related example shows the linkId and relatedSourceId having a value of 42. This inconsistent example is confusing.

{
  "entityId": "41",
  "entityTypeId": "User",
  "name": "Bob"
}

{
  "linkId": "user-42-company-456",
  "sourceEntityId": "42",
  "destinationEntityId": "456",
  "path": "company"
}

If there a place we can submit PRs to the docs site?

The schema editor in HASH (our example, open-source, block-embedding application) provides users with the ability to create schemas that 'extend' other schemas, inheriting all of their expected properties.

The lightweight editor on the current Block Protocol website does not yet provide this functionality. We do, however, intend to port it across.

See #428 for more on extending and duplicating types.

Cci

Building on the updated BP Hub designs in Figma.

See above for what we currently have.

We want to vertically and horizontally center this, add the word "Loading…" beneath it (to help minimize confusion), and change the color to gray.40

_{From SyncLinear.com | BP-24}

_{From SyncLinear.com | BP-15}

Request For Block (RFB)

Spaced repetition flashcards that accept arbitrary entities as inputs.

To be expanded upon here. Discussion encouraged below.

🤩 Inspired by

• @andymatuschak / Andy Matuschak's Orbit project
• @mnielsen / Michael Nielsen's essay on Augmenting Long-term Memory

📚 Background reading

• Spaced repetition memory systems make memory a choice by Andy Matuschak
• Spaced repetition for efficient learning by Gwern Branwen

Look to leverage our existing BrowserStack subscription with something like BrowserStack Percy's integration w/ Playwright: https://docs.percy.io/docs/playwright

We want the sidebar shown on the blockprotocol.org/docs pages to remain as-is, containing the same links in the same order as present. However we want the URL that the spec directory is accessible at to bumped up a level from blockprotocol.org/docs/spec to blockprotocol.org/spec.

It was originally at this location, but at some point was moved as part of what was intended to be a short-lived quick hack, which provided an easy way for us to achieve a unified left-hand navigation sidebar that tied together the documentation with the specification.

In addition to moving spec, we also want to move roadmap from blockprotocol.org/docs/roadmap to blockprotocol.org/roadmap.

This PR follows:

1. #1183
2. #1108

May interact with if done concurrently:

1. #1185

_BP-9

blockprotocol.org does not support dark mode currently. Should we work on it and make it comfortable to read doc at night? 👀

The Block Protocol spec specifically calls out the security concern inherent in running arbitrary code from untrusted third-parties. It mentions the iFrame-based approach to sandboxing employed by our example embedding application, HASH, whose source code is public. We do not (yet) however provide inline docs and examples re: how embedding applications can harden themselves against malicious actors and protect their users from ne'er-do-wellers. We intend to. This issue captures the matter as an outstanding area for expansion.

We've additionally been exploring alternative approaches to the iFrame/postMessage paradigm, in particular how WebAssembly might be used. We'd welcome contributions from community members and interested parties re: either, as well as further/additional, emerging or novel approaches not already considered.

We want to set up a Storybook instance at design.blockprotocol.org containing the forthcoming Þ (block) design system, and related components.

Initially this will be empty. As a follow-up we will add individual components to it. This will eventually then feature in our documentation for block developers, as we encourage use of the block design system, and the Þ Style module.

An example of Storybook running in a comparable public monorepo can be found in this subdirectory of the HASH repo. This implementation/scaffolding should be mirrored in the libs/@blockprotocol/design-system directory of this repo (without any of the underlying components contained inside of the original HASH Storybook being ported across).

Cloudflare DNS records and a Vercel project have already been set up for design.blockprotocol.org. Custom Vercel commands have been used, identical to those in the above linked hashintel/hash monorepo's Storybook setup. These are as follows:

• Build Command: yarn build-storybook
• Output Directory: storybook-static
• Install Command: cd ..; yarn install
• Development Command: default, left blank

You can read more about in Vercel's development and build settings docs.

The root directory specified in Vercel is libs/@blockprotocol/design-system.

_BP-2

Description coming soon

Figma link coming soon

_BP-7

Our current landing page for WordPress users at https://blockprotocol.org/wordpress predates the general availability of the WordPress plugin. Although it remains in early beta, we can now speak about its benefits more directly and completely.

Figma links:

• Landing page design
• Collapsed accordion state

Other links:

• Current webpage for comparison's sake

_{From SyncLinear.com | BP-19}