summaryrefslogtreecommitdiff
path: root/plugins/af_readability/vendor/andreskrey/readability.php/test/test-pages/medium-1/expected.html
diff options
context:
space:
mode:
authorAndrew Dolgov <[email protected]>2021-02-26 17:35:58 +0300
committerAndrew Dolgov <[email protected]>2021-02-26 17:35:58 +0300
commitcf1ede0ba8c687d9bfadf1c372546657968f1dd8 (patch)
tree3394cbf3d1cd60d4e1e42f8ef0aa88c4eef368b9 /plugins/af_readability/vendor/andreskrey/readability.php/test/test-pages/medium-1/expected.html
parent1baf8c521785ab4dc8f474fdd772280737c7e254 (diff)
pull latest readability-php via composer
Diffstat (limited to 'plugins/af_readability/vendor/andreskrey/readability.php/test/test-pages/medium-1/expected.html')
-rw-r--r--plugins/af_readability/vendor/andreskrey/readability.php/test/test-pages/medium-1/expected.html286
1 files changed, 286 insertions, 0 deletions
diff --git a/plugins/af_readability/vendor/andreskrey/readability.php/test/test-pages/medium-1/expected.html b/plugins/af_readability/vendor/andreskrey/readability.php/test/test-pages/medium-1/expected.html
new file mode 100644
index 000000000..679d8b75b
--- /dev/null
+++ b/plugins/af_readability/vendor/andreskrey/readability.php/test/test-pages/medium-1/expected.html
@@ -0,0 +1,286 @@
+<div>
+ <h2 data-align="center" id="3c62" name="3c62">Open Journalism Project:</h2>
+
+ <h4 data-align="center" id="425a" name="425a"><em>Better Student Journalism</em></h4>
+
+
+
+ <p id="d178" name="d178">We pushed out the first version of the <a data-href="http://pippinlee.github.io/open-journalism-project/" href="http://pippinlee.github.io/open-journalism-project/" rel="nofollow">Open Journalism site</a> in January. Our goal is for the
+ site to be a place to teach students what they should know about journalism
+ on the web. It should be fun too.</p>
+ <p id="01ed" name="01ed">Topics like <a data-href="http://pippinlee.github.io/open-journalism-project/Mapping/" href="http://pippinlee.github.io/open-journalism-project/Mapping/" rel="nofollow">mapping</a>, <a data-href="http://pippinlee.github.io/open-journalism-project/Security/" href="http://pippinlee.github.io/open-journalism-project/Security/" rel="nofollow">security</a>, command
+ line tools, and <a data-href="http://pippinlee.github.io/open-journalism-project/Open-source/" href="http://pippinlee.github.io/open-journalism-project/Open-source/" rel="nofollow">open source</a> are
+ all concepts that should be made more accessible, and should be easily
+ understood at a basic level by all journalists. We’re focusing on students
+ because we know student journalism well, and we believe that teaching maturing
+ journalists about the web will provide them with an important lens to view
+ the world with. This is how we got to where we are now.</p>
+ <h3 id="0348" name="0348">Circa 2011</h3>
+ <p id="f923" name="f923">In late 2011 I sat in the design room of our university’s student newsroom
+ with some of the other editors: Kate Hudson, Brent Rose, and Nicholas Maronese.
+ I was working as the photo editor then—something I loved doing. I was very
+ happy travelling and photographing people while listening to their stories.</p>
+ <p id="c9d4" name="c9d4">Photography was my lucky way of experiencing the many types of people
+ my generation seemed to avoid, as well as many the public spends too much
+ time discussing. One of my habits as a photographer was scouring sites
+ like Flickr to see how others could frame the world in ways I hadn’t previously
+ considered.</p>
+ <figure id="06e8" name="06e8"><div>
+
+ <p><img data-action="zoom" data-action-value="1*AzYWbe4cZkMMEUbfRjysLQ.png" data-height="500" data-image-id="1*AzYWbe4cZkMMEUbfRjysLQ.png" data-width="1000" src="https://d262ilb51hltx0.cloudfront.net/max/800/1*AzYWbe4cZkMMEUbfRjysLQ.png"></img></p></div>
+ <figcaption>topleftpixel.com</figcaption></figure><p id="930f" name="930f">I started discovering beautiful things the <a data-href="http://wvs.topleftpixel.com/13/02/06/timelapse-strips-homewood.htm" href="http://wvs.topleftpixel.com/13/02/06/timelapse-strips-homewood.htm" rel="nofollow">web could do with images</a>:
+ things not possible with print. Just as every generation revolts against
+ walking in the previous generations shoes, I found myself questioning the
+ expectations that I came up against as a photo editor. In our newsroom
+ the expectations were built from an outdated information world. We were
+ expected to fill old shoes.</p>
+ <p id="2674" name="2674">So we sat in our student newsroom—not very happy with what we were doing.
+ Our weekly newspaper had remained essentially unchanged for 40+ years.
+ Each editorial position had the same requirement every year. The <em>big</em> change
+ happened in the 80s when the paper started using colour. We’d also stumbled
+ into having a website, but it was updated just once a week with the release
+ of the newspaper.</p>
+ <p id="e498" name="e498">Information had changed form, but the student newsroom hadn’t, and it
+ was becoming harder to romanticize the dusty newsprint smell coming from
+ the shoes we were handed down from previous generations of editors. It
+ was, we were told, all part of “becoming a journalist.”</p>
+ <figure id="12da" name="12da"><div>
+
+ <p><img data-action="zoom" data-action-value="1*d0Hp6KlzyIcGHcL6to1sYQ.png" data-height="451" data-image-id="1*d0Hp6KlzyIcGHcL6to1sYQ.png" data-width="868" src="https://d262ilb51hltx0.cloudfront.net/max/800/1*d0Hp6KlzyIcGHcL6to1sYQ.png"></img></p></div>
+ </figure><h3 id="e2f0" name="e2f0">We don’t know what we don’t know</h3>
+ <p id="8263" name="8263">We spent much of the rest of the school year asking “what should we be
+ doing in the newsroom?”, which mainly led us to ask “how do we use the
+ web to tell stories?” It was a straightforward question that led to many
+ more questions about the web: something we knew little about. Out in the
+ real world, traditional journalists were struggling to keep their jobs
+ in a dying print world. They wore the same design of shoes that we were
+ supposed to fill. Being pushed to repeat old, failing strategies and blocked
+ from trying something new scared us.</p>
+ <p id="231e" name="231e">We had questions, so we started doing some research. We talked with student
+ newsrooms in Canada and the United States, and filled too many Google Doc
+ files with notes. Looking at the notes now, they scream of fear. We annotated
+ our notes with naive solutions, often involving scrambled and immature
+ odysseys into the future of online journalism.</p>
+ <p id="6ec3" name="6ec3">There was a lot we didn’t know. We didn’t know <strong>how to build a mobile app</strong>.
+ We didn’t know <strong>if we should build a mobile app</strong>.
+ We didn’t know <strong>how to run a server</strong>.
+ We didn’t know <strong>where to go to find a server</strong>.
+ We didn’t know <strong>how the web worked</strong>.
+ We didn’t know <strong>how people used the web to read news</strong>.
+ We didn’t know <strong>what news should be on the web</strong>.
+ If news is just information, what does that even look like?</p>
+ <p id="f373" name="f373">We asked these questions to many students at other papers to get a consensus
+ of what had worked and what hadn’t. They reported similar questions and
+ fears about the web but followed with “print advertising is keeping us
+ afloat so we can’t abandon it”.</p>
+ <p id="034b" name="034b">In other words, we knew that we should be building a newer pair of shoes,
+ but we didn’t know what the function of the shoes should be.</p>
+ <h3 id="ea15" name="ea15">Common problems in student newsrooms (2011)</h3>
+ <p id="a90b" name="a90b">Our questioning of other student journalists in 15 student newsrooms brought
+ up a few repeating issues.</p>
+ <ul><li id="a586" name="a586">Lack of mentorship</li>
+ <li id="a953" name="a953">A news process that lacked consideration of the web</li>
+ <li id="6286" name="6286">No editor/position specific to the web</li>
+ <li id="04c1" name="04c1">Little exposure to many of the cool projects being put together by professional
+ newsrooms</li>
+ <li id="a1fb" name="a1fb">Lack of diverse skills within the newsroom. Writers made up 95% of the
+ personnel. Students with other skills were not sought because journalism
+ was seen as “a career with words.” The other 5% were designers, designing
+ words on computers, for print.</li>
+ <li id="0be9" name="0be9">Not enough discussion between the business side and web efforts</li>
+ </ul><figure id="79ed" name="79ed"><div>
+
+ <p><img data-action="zoom" data-action-value="1*_9KYIFrk_PqWFgptsMDeww.png" data-height="500" data-image-id="1*_9KYIFrk_PqWFgptsMDeww.png" data-width="1086" src="https://d262ilb51hltx0.cloudfront.net/max/800/1*_9KYIFrk_PqWFgptsMDeww.png"></img></p></div>
+ <figcaption>From our 2011 research</figcaption></figure><h3 id="8d0c" name="8d0c">Common problems in student newsrooms (2013)</h3>
+ <p id="3ef6" name="3ef6">Two years later, we went back and looked at what had changed. We talked
+ to a dozen more newsrooms and weren’t surprised by our findings.</p>
+ <ul><li id="abb1" name="abb1">Still no mentorship or link to professional newsrooms building stories
+ for the web</li>
+ <li id="9250" name="9250">Very little control of website and technology</li>
+ <li id="d822" name="d822">The lack of exposure that student journalists have to interactive storytelling.
+ While some newsrooms are in touch with what’s happening with the web and
+ journalism, there still exists a huge gap between the student newsroom
+ and its professional counterpart</li>
+ <li id="6bf2" name="6bf2">No time in the current news development cycle for student newsrooms to
+ experiment with the web</li>
+ <li id="e62f" name="e62f">Lack of skill diversity (specifically coding, interaction design, and
+ statistics)</li>
+ <li id="f4f0" name="f4f0">Overly restricted access to student website technology. Changes are primarily
+ visual rather than functional.</li>
+ <li id="8b8d" name="8b8d">Significantly reduced print production of many papers</li>
+ <li id="dfe0" name="dfe0">Computers aren’t set up for experimenting with software and code, and
+ often locked down</li>
+ </ul><p id="52cd" name="52cd">Newsrooms have traditionally been covered in copies of The New York Times
+ or Globe and Mail. Instead newsrooms should try spend at 20 minutes each
+ week going over the coolest/weirdest online storytelling in an effort to
+ expose each other to what is possible. “<a data-href="http://nytlabs.com/" href="http://nytlabs.com/" rel="nofollow">Hey, what has the New York Times R&amp;D lab been up to this week?</a>”</p>
+ <p id="0142" name="0142">Instead of having computers that are locked down, try setting aside a
+ few office computers that allow students to play and “break”, or encourage
+ editors to buy their own Macbooks so they’re always able to practice with
+ code and new tools on their own.</p>
+ <p id="5d29" name="5d29">From all this we realized that changing a student newsroom is difficult.
+ It takes patience. It requires that the business and editorial departments
+ of the student newsroom be on the same (web)page. The shoes of the future
+ must be different from the shoes we were given.</p>
+ <p id="1ffc" name="1ffc">We need to rethink how long the new shoe design will be valid. It’s more
+ important that we focus on the process behind making footwear than on actually
+ creating a specific shoe. We shouldn’t be building a shoe to last 40 years.
+ Our footwear design process will allow us to change and adapt as technology
+ evolves. The media landscape will change, so having a newsroom that can
+ change with it will be critical.</p>
+ <p id="2888" name="2888"><strong>We are building a shoe machine, not a shoe.</strong>
+ </p>
+
+ <h3 id="9c30" name="9c30">A train or light at the end of the tunnel: are student newsrooms changing for the better?</h3>
+
+ <p id="4634" name="4634">In our 2013 research we found that almost 50% of student newsrooms had
+ created roles specifically for the web. <strong>This sounds great, but is still problematic in its current state.</strong>
+ </p>
+ <figure id="416f" name="416f"><div>
+
+ <p><img data-height="560" data-image-id="1*Vh2MpQjqjPkzYJaaWExoVg.png" data-width="624" src="https://d262ilb51hltx0.cloudfront.net/max/800/1*Vh2MpQjqjPkzYJaaWExoVg.png"></img></p></div>
+ <figcaption><strong>We designed many of these slides to help explain to ourselves what we were doing</strong>
+ </figcaption></figure><p id="39e6" name="39e6">When a newsroom decides to create a position for the web, it’s often with
+ the intent of having content flow steadily from writers onto the web. This
+ is a big improvement from just uploading stories to the web whenever there
+ is a print issue. <em>However…</em>
+ </p>
+ <ol><li id="91b5" name="91b5"><strong>The handoff</strong>
+ <br></br>Problems arise because web editors are given roles that absolve the rest
+ of the editors from thinking about the web. All editors should be involved
+ in the process of story development for the web. While it’s a good idea
+ to have one specific editor manage the website, contributors and editors
+ should all play with and learn about the web. Instead of “can you make
+ a computer do XYZ for me?”, we should be saying “can you show me how to
+ make a computer do XYZ?”</li>
+ <li id="6448" name="6448"><strong>Not just social media<br></br></strong>A
+ web editor could do much more than simply being in charge of the social
+ media accounts for the student paper. Their responsibility could include
+ teaching all other editors to be listening to what’s happening online.
+ The web editor can take advantage of live information to change how the
+ student newsroom reports news in real time.</li>
+ <li id="ab30" name="ab30"><strong>Web (interactive) editor<br></br></strong>The
+ goal of having a web editor should be for someone to build and tell stories
+ that take full advantage of the web as their medium. Too often the web’s
+ interactivity is not considered when developing the story. The web then
+ ends up as a resting place for print words.</li>
+ </ol><p id="e983" name="e983">Editors at newsrooms are still figuring out how to convince writers of
+ the benefit to having their content online. There’s still a stronger draw
+ to writers seeing their name in print than on the web. Showing writers
+ that their stories can be told in new ways to larger audiences is a convincing
+ argument that the web is a starting point for telling a story, not its
+ graveyard.</p>
+ <p id="5c11" name="5c11">When everyone in the newsroom approaches their website with the intention
+ of using it to explore the web as a medium, they all start to ask “what
+ is possible?” and “what can be done?” You can’t expect students to think
+ in terms of the web if it’s treated as a place for print words to hang
+ out on a web page.</p>
+ <p id="4eb1" name="4eb1">We’re OK with this problem, if we see newsrooms continue to take small
+ steps towards having all their editors involved in the stories for the
+ web.</p>
+ <figure id="7aab" name="7aab"><div>
+
+ <p><img data-action="zoom" data-action-value="1*2Ln_DmC95Xpz6LzgywkcFQ.png" data-height="718" data-image-id="1*2Ln_DmC95Xpz6LzgywkcFQ.png" data-width="1315" src="https://d262ilb51hltx0.cloudfront.net/max/800/1*2Ln_DmC95Xpz6LzgywkcFQ.png"></img></p></div>
+ <figcaption>The current Open Journalism site was a few years in the making. This was
+ an original launch page we use in 2012</figcaption></figure><h3 id="08f5" name="08f5">What we know</h3>
+ <ul><li id="f7fe" name="f7fe"><strong>New process</strong>
+ <br></br>Our rough research has told us newsrooms need to be reorganized. This
+ includes every part of the newsroom’s workflow: from where a story and
+ its information comes from, to thinking of every word, pixel, and interaction
+ the reader will have with your stories. If I was a photo editor that wanted
+ to re-think my process with digital tools in mind, I’d start by asking
+ “how are photo assignments processed and sent out?”, “how do we receive
+ images?”, “what formats do images need to be exported in?”, “what type
+ of screens will the images be viewed on?”, and “how are the designers getting
+ these images?” Making a student newsroom digital isn’t about producing
+ “digital manifestos”, it’s about being curious enough that you’ll want
+ to to continue experimenting with your process until you’ve found one that
+ fits your newsroom’s needs.</li>
+ <li id="d757" name="d757"><strong>More (remote) mentorship</strong>
+ <br></br>Lack of mentorship is still a big problem. <a data-href="http://www.google.com/get/journalismfellowship/" href="http://www.google.com/get/journalismfellowship/" rel="nofollow">Google’s fellowship program</a> is great. The fact that it
+ only caters to United States students isn’t. There are only a handful of
+ internships in Canada where students interested in journalism can get experience
+ writing code and building interactive stories. We’re OK with this for now,
+ as we expect internships and mentorship over the next 5 years between professional
+ newsrooms and student newsrooms will only increase. It’s worth noting that
+ some of that mentorship will likely be done remotely.</li>
+ <li id="a9b8" name="a9b8"><strong>Changing a newsroom culture</strong>
+ <br></br>Skill diversity needs to change. We encourage every student newsroom we
+ talk to, to start building a partnership with their school’s Computer Science
+ department. It will take some work, but you’ll find there are many CS undergrads
+ that love playing with web technologies, and using data to tell stories.
+ Changing who is in the newsroom should be one of the first steps newsrooms
+ take to changing how they tell stories. The same goes with getting designers
+ who understand the wonderful interactive elements of the web and students
+ who love statistics and exploring data. Getting students who are amazing
+ at design, data, code, words, and images into one room is one of the coolest
+ experience I’ve had. Everyone benefits from a more diverse newsroom.</li>
+ </ul><h3 id="a67e" name="a67e">What we don’t know</h3>
+ <ul><li id="7320" name="7320"><strong>Sharing curiosity for the web</strong>
+ <br></br>We don’t know how to best teach students about the web. It’s not efficient
+ for us to teach coding classes. We do go into newsrooms and get them running
+ their first code exercises, but if someone wants to learn to program, we
+ can only provide the initial push and curiosity. We will be trying out
+ “labs” with a few schools next school year to hopefully get a better idea
+ of how to teach students about the web.</li>
+ <li id="8b23" name="8b23"><strong>Business</strong>
+ <br></br>We don’t know how to convince the business side of student papers that
+ they should invest in the web. At the very least we’re able to explain
+ that having students graduate with their current skill set is painful in
+ the current job market.</li>
+ <li id="191e" name="191e"><strong>The future</strong>
+ <br></br>We don’t know what journalism or the web will be like in 10 years, but
+ we can start encouraging students to keep an open mind about the skills
+ they’ll need. We’re less interested in preparing students for the current
+ newsroom climate, than we are in teaching students to have the ability
+ to learn new tools quickly as they come and go.</li>
+ </ul></div><div>
+ <h3 id="009a" name="009a">What we’re trying to share with others</h3>
+ <ul><li id="8bfa" name="8bfa"><strong>A concise guide to building stories for the web</strong>
+ <br></br>There are too many options to get started. We hope to provide an opinionated
+ guide that follows both our experiences, research, and observations from
+ trying to teach our peers.</li>
+ </ul><p id="8196" name="8196">Student newsrooms don’t have investors to please. Student newsrooms can
+ change their website every week if they want to try a new design or interaction.
+ As long as students start treating the web as a different medium, and start
+ building stories around that idea, then we’ll know we’re moving forward.</p>
+ <h3 id="f6c6" name="f6c6">A note to professional news orgs</h3>
+ <p id="d8f5" name="d8f5">We’re also asking professional newsrooms to be more open about their process
+ of developing stories for the web. You play a big part in this. This means
+ writing about it, and sharing code. We need to start building a bridge
+ between student journalism and professional newsrooms.</p>
+ <figure id="7ed3" name="7ed3"><div>
+
+ <p><img data-height="400" data-image-id="1*bXaR_NBJdoHpRc8lUWSsow.png" data-width="686" src="https://d262ilb51hltx0.cloudfront.net/max/800/1*bXaR_NBJdoHpRc8lUWSsow.png"></img></p></div>
+ <figcaption>2012</figcaption></figure><h3 id="ee1b" name="ee1b">This is a start</h3>
+ <p id="ebf9" name="ebf9">We going to continue slowly growing the content on <a data-href="http://pippinlee.github.io/open-journalism-project/" href="http://pippinlee.github.io/open-journalism-project/" rel="nofollow">Open Journalism</a>. We still consider this the beta version,
+ but expect to polish it, and beef up the content for a real launch at the
+ beginning of the summer.</p>
+ <p id="bd44" name="bd44">We expect to have more original tutorials as well as the beginnings of
+ what a curriculum may look like that a student newsroom can adopt to start
+ guiding their transition to become a web first newsroom. We’re also going
+ to be working with the <a data-href="http://queensjournal.ca/" href="http://queensjournal.ca/" rel="nofollow">Queen’s Journal</a> and
+ <a data-href="http://ubyssey.ca/" href="http://ubyssey.ca/" rel="nofollow">The Ubyssey</a>next school year to better understand how to make the student
+ newsroom a place for experimenting with telling stories on the web. If
+ this sound like a good idea in your newsroom, we’re still looking to add
+ 1 more school.</p>
+ <p id="abd5" name="abd5">We’re trying out some new shoes. And while they’re not self-lacing, and
+ smell a bit different, we feel lacing up a new pair of kicks can change
+ a lot.</p>
+ <figure id="4c68" name="4c68"><div>
+
+ <p><img data-action="zoom" data-action-value="1*lulfisQxgSQ209vPHMAifg.png" data-height="534" data-image-id="1*lulfisQxgSQ209vPHMAifg.png" data-width="950" src="https://d262ilb51hltx0.cloudfront.net/max/800/1*lulfisQxgSQ209vPHMAifg.png"></img></p></div>
+ </figure>
+ <p id="2c5c" name="2c5c"><strong>Let’s talk. Let’s listen.</strong>
+ </p>
+ <p id="63ec" name="63ec"><strong>We’re still in the early stages of what this project will look like, so if you want to help or have thoughts, let’s talk.</strong>
+ </p>
+ <p id="9376" name="9376"><a data-href="mailto:[email protected]" href="mailto:[email protected]" rel="nofollow"><strong>[email protected]</strong></a>
+ </p>
+
+
+ <p id="ea00" name="ea00"><em>This isn’t supposed to be a </em>
+ <strong><em>manifesto™©</em>
+ </strong><em> we just think it’s pretty cool to share what we’ve learned so far, and hope you’ll do the same. We’re all in this together.</em>
+ </p>
+ </div> \ No newline at end of file