Repository navigation
v4.0.0 - #512
v4.0.0#512shaundillon wants to merge 8 commits into
Conversation
|
Wow, this is exciting news! |
| "html-janitor": "./bower_components/html-janitor/src/html-janitor", | ||
| "lodash-amd": "../bower_components/lodash-amd" | ||
| "html-janitor": "./node_modules/html-janitor/src/html-janitor", | ||
| "lodash-amd": "../node_modules/lodash-amd" |
There was a problem hiding this comment.
html-janitor is ./ lodash-amd is ../ - I assume it works, but is it right?
| @@ -1,3 +1,11 @@ | |||
| # 4.0.0 | |||
|
|
|||
| - Builds using [webpack 2](https://webpack.js.org/) | |||
There was a problem hiding this comment.
webpack 2
Ya sure about that? 😉 (3.5.1)
| { | ||
| "name": "scribe-editor", | ||
| "version": "3.3.0", | ||
| "version": "4.0.0", |
There was a problem hiding this comment.
Maybe we want to publish Scribe underneath https://www.npmjs.com/org/guardian now?
| }, | ||
|
|
||
| resolve: { | ||
| extensions: ['.js', '.jsx', '.json'] |
| // .babelrc | ||
| { | ||
| "presets": [ | ||
| ["es2015"] |
There was a problem hiding this comment.
Maybe in a differnt PR when we review browser matrix but babel-preset-env instead of es2015 with the browser support?
| "q": "~1.5.0", | ||
| "request": "~2.81.0", | ||
| "requirejs": "~2.1.9", | ||
| "scribe-plugin-blockquote-command": "guardian/scribe-plugin-blockquote-command#master", |
There was a problem hiding this comment.
Are you missing https://www.npmjs.com/package/scribe-common from the package.json?
There was a problem hiding this comment.
Actually, yeah - does this break?
https://github.com/guardian/scribe/pull/512/files#diff-6c813d37994412127bb214a95c332ce6R39
|
Hi all, A year later (sorry about that!) it's worth giving an update about our plans for Scribe. Scribe is heavily used internally in our content management systems, including the main digital CMS. We have had many requests internally to improve noting [*] in Scribe but were unable to make much progress continuing to work directly with As such we’ve been working to move our implementation on top of Prose Mirror. The results are exciting and are setting us up for other interesting things in the future like collaborative editing. We will do a new point release with @RichieAHBs pull request so we can continue with our migration. We will also endeavour to merge existing PRs where possible. As our Prose Mirror based work continues, we hope to bring it together to provide a new major version of Scribe. This should maintain the “easy to embed” nature of the library whilst being a more robust platform for improvements in the future. I hope we can share more of our plans in the coming 6 months. [*] noting is where sub-editors will mark text so it is still visible (marked) in the CMS but does not appear in the resulting content. The nuances are many and varied and Scribes implementation relied on invisible characters which themselves sometimes lead to incorrect spacing and formatting in the resulting content. |
This takes some steps towards modernising scribe. We're now actively developing scribe again and these steps move some way towards making this process easier.
Major changes are:
Build is moved to Webpack 2(Due to issues getting Webpack to build AMD nicely, this will be in an upcoming version in order to get this out)