11 ms·

The high CPU and memory usage was due to a large gif which was included two times. This gif accidentally was 1280p with 20fps and was about 40mb large. For some

The high CPU and memory usage was due to a large gif which was included two times. This gif accidentally was 1280p with 20fps and was about 40mb large. For some reason, the resizer did not properly work. Anyways, the gif is now removed. I hope the performance gets much better now. The CPU fans on macbooks going up where probably due to a lack of a dedicated graphics card. This happened to me with my macbook and large gifs too. If the problems don't go away, please create an issue in the repo so we can work on improving this! It would be important to include your steps so we are able to reproduce these issues. edit:// Since this comment is on the top, I'll address a few more questions here too. If you missed the demo, it's here: http://editor.ory.am/ http://editor.ory.am/ First, this is a layout editor first- and foremost. Behind the scenes, React, Redux and slate.js ( http://slatejs.org/ http://slatejs.org/ ) is being used. Each cell is a React component that you can implement yourself. In fact, the text component itself is a plugin that wraps slate.js. Second, we're integrating this editor in Germany's largest e-learning platform (wiki-esque) with ~1 million MAUs: https://de.serlo.org https://de.serlo.org And lastly we're working on a business model behind it, with our ory sites product (early access): http://ory.am/sites/ http://ory.am/sites/ If you want to check out our other open source products, feel free to do so: https://github.com/ory https://github.com/ory

rtcoms 9y ago
> First, this is a layout editor first- and foremost. Behind the scenes, React, Redux and slate.js ( http://slatejs.org/ http://slatejs.org/ ) is being used. Would it make sense to have a separate repo for layout editor ?
- arekkas 9y ago
  Not sure what you mean? This is already the case, all cells that you can use in the demo are actually plugins. Check this directory: https://github.com/ory/editor/tree/master/packages/plugins/content https://github.com/ory/editor/tree/master/packages/plugins/c...
ctoth 9y ago
This does not appear to work at all with my screen reader. Accessibility as afterthought, as always. I used to look forward to trying to help people fix their stuff to be accessible, but now I'm just tired of every single fucking thing somebody creates being broken for me because everything is a complete heaping pile of inaccessible garbage and nobody even thinks about accessibility. It's not like there aren't thousands of pages of documentation on how to make stuff accessible... but the libraries keep getting released without accessibility, and then people build components using several of these libraries and they're useless, and then people build entire apps out of these components... And the web that I used to know and love and get around just find goes dark. And this is going to get integrated into some big educational site? So I guess it sucks to be a blind student in Germany. What a mess. Sorry for the negativity, but this just really, really gets old.
- Operyl 9y ago
  It must really suck, and when I work on small(but large) personal projects I feel bad that someone might not be able to use it. What are some good resources to start thinking accessibility first? I remember in the past it was .. a project and a half in and of itself.
  - speedemin 9y ago
    I really like the A11ycasts show by Google Chrome Developers https://www.youtube.com/playlist?list=PLNYkxOF6rcICWx0C9LVWWVqvHlYJyqw7g https://www.youtube.com/playlist?list=PLNYkxOF6rcICWx0C9LVWW...
  - ctoth 9y ago
    The nice thing is it's very easy to get started, and no matter what you're working on, be it a web project, a mobile app, or even something for desktop there are loads of resources out there, as well as people who care. For web stuff, over the last month or so I've been pointing people to the relatively new but still pretty nice A11y Style Guide[0] This is obviously for just getting started. When we get into more complicated markup, I often find fantastic resources, articles, and examples from companies like SSB BART or Deque (no affiliation with either) When mobile accessibility comes up, few people do it better than the BBC, and they have a great resource on it[1] I'm also working on a playbook for mobile accessibility, but that's still under development. The really important and kind of awesome thing is that it's extremely easier to test the accessibility of whatever you're building as you build it. Unlike the bad old days where screen readers costs $1,000 and no developers had access to them, on mobile or Mac screen readers are built directly into your device, and on Windows NVDA is completely free from [2] Hope this gives you a starting point, and if you have more questions feel free to reach out, email in profile. [0]: https://a11y-style-guide.com https://a11y-style-guide.com [1]http://www.bbc.co.uk/guidelines/futuremedia/accessibility/mobile_access.shtml http://www.bbc.co.uk/guidelines/futuremedia/accessibility/mo... [2]https://NVAccess.org https://NVAccess.org

rtcoms 9y ago

> First, this is a layout editor first- and foremost. Behind the scenes, React, Redux and slate.js ( http://slatejs.org/ http://slatejs.org/ ) is being used. Would it make sense to have a separate repo for layout editor ?

arekkas 9y ago
Not sure what you mean? This is already the case, all cells that you can use in the demo are actually plugins. Check this directory: https://github.com/ory/editor/tree/master/packages/plugins/content https://github.com/ory/editor/tree/master/packages/plugins/c...

ctoth 9y ago

This does not appear to work at all with my screen reader. Accessibility as afterthought, as always. I used to look forward to trying to help people fix their stuff to be accessible, but now I'm just tired of every single fucking thing somebody creates being broken for me because everything is a complete heaping pile of inaccessible garbage and nobody even thinks about accessibility. It's not like there aren't thousands of pages of documentation on how to make stuff accessible... but the libraries keep getting released without accessibility, and then people build components using several of these libraries and they're useless, and then people build entire apps out of these components... And the web that I used to know and love and get around just find goes dark. And this is going to get integrated into some big educational site? So I guess it sucks to be a blind student in Germany. What a mess. Sorry for the negativity, but this just really, really gets old.

Operyl 9y ago
It must really suck, and when I work on small(but large) personal projects I feel bad that someone might not be able to use it. What are some good resources to start thinking accessibility first? I remember in the past it was .. a project and a half in and of itself.
- speedemin 9y ago
  I really like the A11ycasts show by Google Chrome Developers https://www.youtube.com/playlist?list=PLNYkxOF6rcICWx0C9LVWWVqvHlYJyqw7g https://www.youtube.com/playlist?list=PLNYkxOF6rcICWx0C9LVWW...
- ctoth 9y ago
  The nice thing is it's very easy to get started, and no matter what you're working on, be it a web project, a mobile app, or even something for desktop there are loads of resources out there, as well as people who care. For web stuff, over the last month or so I've been pointing people to the relatively new but still pretty nice A11y Style Guide[0] This is obviously for just getting started. When we get into more complicated markup, I often find fantastic resources, articles, and examples from companies like SSB BART or Deque (no affiliation with either) When mobile accessibility comes up, few people do it better than the BBC, and they have a great resource on it[1] I'm also working on a playbook for mobile accessibility, but that's still under development. The really important and kind of awesome thing is that it's extremely easier to test the accessibility of whatever you're building as you build it. Unlike the bad old days where screen readers costs $1,000 and no developers had access to them, on mobile or Mac screen readers are built directly into your device, and on Windows NVDA is completely free from [2] Hope this gives you a starting point, and if you have more questions feel free to reach out, email in profile. [0]: https://a11y-style-guide.com https://a11y-style-guide.com [1]http://www.bbc.co.uk/guidelines/futuremedia/accessibility/mobile_access.shtml http://www.bbc.co.uk/guidelines/futuremedia/accessibility/mo... [2]https://NVAccess.org https://NVAccess.org