Building a Text Editor for a Digital-First Newsroom
open.nytimes.com
Building a Text Editor for a Digital-First Newsroom
1–10 of 176 posts
Re: Building a Text Editor for a Digital-First Newsroom
#2> If you’re like most people in America, you use a text editor nearly every day.
Filter bubble detected.
Re: Building a Text Editor for a Digital-First Newsroom
#3> If you’re like most people in America, you use a text editor nearly every day. Filter bubble detected.
The author does not say "work in a text editor", only "use". Considering she's including text editors on mobile devices, which the majority of America will utilize today, that's not a particularly bold statement.
Re: Building a Text Editor for a Digital-First Newsroom
#4Data Warning: 100 MB.
Viewing the header illustration for more than a few seconds crashes my iPad Safari tab. Scrolling until it is off the viewport prevents this.
EDIT: Dev Tools reports 74.8 MB transferred with an ad blocker. The illustration is a single 69.2 MB gif.
EDIT: 101 MB in total when you scroll to the bottom. Three more gifs: 18.1 MB, 7.1 MB, 4.7 MB.
Re: Building a Text Editor for a Digital-First Newsroom
#5Cool, but it's yet another case of re-engineering the same thing. (edit: its not entirely new).
Splitting editors into an abstracted structure for finer control over data and presentation is something that's been done for a decade now in various text editors. Medium and Basecamp started similar projects and there's Mobiledoc which is trying to standardize the format. It'd be nice if all this effort focused on a single project so we could all just get a decent editor instead of different versions with various states of functionality.
FYI, my running list of editors: https://gist.github.com/manigandham/65543a0bc2bf7006a487
Re: Building a Text Editor for a Digital-First Newsroom
#6Data Warning: 100 MB. Viewing the header illustration for more than a few seconds crashes my iPad Safari tab. Scrolling until it is off the viewport prevents this. EDIT: Dev Tools reports 74.8 MB transferred with an ad blocker. The illustration is a single 69.2 MB gif. EDIT: 101 MB in total when you scroll to the bottom. Three more gifs: 18.1 MB, 7.1 MB, 4.7 MB.
Unbelievable
Re: Building a Text Editor for a Digital-First Newsroom
#7Anyone know if Oak is (or will be) released as Open Source?
Re: Building a Text Editor for a Digital-First Newsroom
#8Data Warning: 100 MB. Viewing the header illustration for more than a few seconds crashes my iPad Safari tab. Scrolling until it is off the viewport prevents this. EDIT: Dev Tools reports 74.8 MB transferred with an ad blocker. The illustration is a single 69.2 MB gif. EDIT: 101 MB in total when you scroll to the bottom. Three more gifs: 18.1 MB, 7.1 MB, 4.7 MB.
Why are they gifs instead of mp4s? Yikes. Also, since they are screenshots without a lot of movement, they really should compress better than that even as gifs.
Re: Building a Text Editor for a Digital-First Newsroom
#9Whew, what a gross way to over-engineer a text editor. If the NYTimes structured themselves like a dev team, they could use common sense tools to get much better results.
Why is the journalist responsible for how it's presented? Wouldn't it make more sense to have some kind of product manager or designer handle this? And why is the journalist responsible for programming the look and feel of the their article? Why not have a front end dev do that?
Re: Building a Text Editor for a Digital-First Newsroom
#10Cool, but it's yet another case of re-engineering the same thing. (edit: its not entirely new). Splitting editors into an abstracted structure for finer control over data and presentation is something that's been done for a decade now in various text editors. Medium and Basecamp started similar projects and there's Mobiledoc which is trying to standardize the format. It'd be nice if all this effort focused on a singl…
Considering that they have built it on top of ProseMirror makes it seem pretty reasonable approach in terms of "reinventing the wheel"