The ProseMirror website https://prosemirror.net
  • JavaScript 57.2%
  • HTML 35.4%
  • CSS 5.9%
  • Makefile 1.5%
Find a file
2026-04-01 22:00:00 +02:00
bin Stop running Bublé on output code 2023-05-01 19:18:27 +02:00
example Fix stale position issue in lint example 2025-12-09 10:11:03 +01:00
markdown Update links to github 2026-04-01 22:00:00 +02:00
pages Update links to github 2026-04-01 22:00:00 +02:00
public Add missing logo file 2025-10-29 17:37:19 +01:00
src Update links to github 2026-04-01 22:00:00 +02:00
templates Update links to github 2026-04-01 22:00:00 +02:00
.gitignore Add an Atom feed for the release changelog 2025-01-06 12:11:16 +01:00
LICENSE Update maintainer email 2023-01-24 08:24:19 +01:00
logo.svg Tweak logo 2017-07-24 14:25:43 +02:00
logo_dark.svg Tweak logo 2017-07-24 14:25:43 +02:00
Makefile Add an Atom feed for the release changelog 2025-01-06 12:11:16 +01:00
package.json Update links to github 2026-04-01 22:00:00 +02:00
README.md Update links to github 2026-04-01 22:00:00 +02:00
tsconfig.json Fix reference guide build 2024-04-25 16:20:04 +02:00

Prosemirror.net

These are the sources for https://prosemirror.net

This currently contains a front-page, the examples (including server-side code to support the collaborative demo), the guide, and the scripts to build the reference docs.

Installation

Install Node.js.

Install the module's dependencies:

npm install

Build the documentation and all the demos' JavaScript source

make

That will populate the public/ directory with an instance of the website. You could point a webserver at it to try it out.

To work on the demos, or to experiment with the collaborative demo, it is a good idea to use the dev server:

npm run devserver -- --port 8888

That will get you a server at localhost:8888 that serves the files in public/, along with the collaborative editing backend, and updates the demo pages to use moduleserve so that you can run the demos directly from the source files, rather than using the bundled code. You can now edit them and see the changes with a single refresh. (Though the server-side collaborative code still needs a server refresh to update.)

Note that this is not secure (it provides file system access of HTTP) and not fast (the browser will fetch each module individually), and should only be used for development, on your local machine, bound to localhost.