We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Stylo: a user friendly text editor for humanities scholars

00:00

Formal Metadata

Title
Stylo: a user friendly text editor for humanities scholars
Title of Series
Number of Parts
490
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
As an editor for WYSIWYM text, Stylo is designed to change the entire digital editorial chain of scholarly journals the field of human sciences. Stylo (https://stylo.ecrituresnumeriques.ca) is designed to simplify the writing and editing of scientific articles in the humanities and social sciences. It is intended for authors and publishers engaged in high quality scientific publishing. Although the structuring of documents is fundamental for digital distribution, this aspect is currently delayed until the end of the editorial process. This task should, however, be undertaken early on in the process; it must be considered by the author himself. The philosophy behind Stylo consists in returning the task of managing the publication markup to researchers. This repositioning of tasks relating to the editorial process relies on the author’s semantic rather than graphic skills. This lightning talk will be the opportunity to present this tool and several publishing projects realized with Stylo.
Text editorDigital signalContext awarenessContent (media)Structured programmingWordDuality (mathematics)GoogolGame theoryStudent's t-testMereologyProcess (computing)Probability density functionCollaborative softwareContext awarenessPlanningDuality (mathematics)WordGraph (mathematics)Data structureField (computer science)Software developerArtistic renderingSource codeVariety (linguistics)Content (media)Latent heatText editorFreewarePresentation of a groupSemantics (computer science)Electric generatorPower (physics)TwitterOcean currentMetadataLimit (category theory)Multiplication signGoodness of fitDigitizingResultantCausalityLattice (order)Escape characterMathematical singularityPoint (geometry)UsabilityCondition numberProfil (magazine)ECosPhysical systemGroup actionExtension (kinesiology)TunisGraphics tabletPrisoner's dilemmaWebsiteSoftwareType theorySpeech synthesisComputer animation
GoogolPoint cloudInformation privacyWordContent (media)Source codeManifoldProbability density functionInterface (computing)Data typeSinguläres IntegralModul <Datentyp>Text editorMarkup languageMetadataData managementDatabaseFront and back endsGraph (mathematics)Link (knot theory)Semantics (computer science)Level (video gaming)Source codeWritingComputing platformReal numberInterface (computing)File formatMarkup languageView (database)ManifoldDynamical systemData structureSingle-precision floating-point formatArtistic renderingPower (physics)Computer fileWordModul <Datentyp>InformationText editorComplex (psychology)MetadataRevision controlRadical (chemistry)Data managementConstraint (mathematics)Connected spaceMultiplication signUniqueness quantificationUsabilityHypothesisDifferent (Kate Ryan album)Computer-assisted translationVotingUser interfaceMetropolitan area networkTransportation theory (mathematics)GoogolSimilarity (geometry)Digital photographyWeb 2.0IRIS-TState of matterContent (media)Product (business)FreewareComputer animation
Normed vector spacePhysicsRing (mathematics)Maxima and minimaData managementInformationLevel (video gaming)MetadataGroup actionComputer animation
Execution unitPhysicsConvex hullMeta elementRevision controlTable (information)Content (media)Web 2.0Group actionAsynchronous Transfer ModeService (economics)Field (computer science)Text editorRight angleDefault (computer science)HypothesisMetadataInternet service providerQuicksortDifferent (Kate Ryan album)ExplosionMUDFreewareSource codeComputer animation
ChainDigital signalProbability density functionFatou-MengeProof theoryUniqueness quantificationText editorSource codeSoftware testingComplex (psychology)Computer fileDigitizingProbability density functionEntire functionChainMetadataProof theoryQuicksortCollaborationismProjective planeWeightSelectivity (electronic)Coefficient of determinationState of matterSimilarity (geometry)Fuzzy logicComputer clusterComputer animation
Point cloudFacebookOpen source
Transcript: English(auto-generated)
Okay. Hi. First of all, thank you for the Open Research Tools and Technology team. I'm honored to be part of this fantastic game. My name is Antoine Fouché. I'm an all-new PhD student because I'm 36 and I'm from Montreal, but I'm French.
You have already figured it with my beautiful accent. I'm going to talk about writing tools, publication, tuition, and freedom. My presentation is already available online, as you can see, and I'm using reveal.js so
you can watch my notes with the SK. So the plan. So you can understand the team's starting point. I have to explain at first the context. Then I will present the tools that are used by the majority in the scientific community,
and I call them tools of pain. Not that I'm not going to say burn all the word processors, but a little bit. The third part is about what we need for doing our job as researchers. Such as comfort. I like the new buzzword in the development community, DX, like UX, for developer experience.
And finally, I will present about great, beautiful, but powerful and free tools. And of course, I'm going to introduce Tilo, a gorgeous user-friendly text editor for humanities scholars. Okay. So first context with academic publishing, humanities scholars, and digital world.
Publishing ecosystem is not uniform, and academic publishing have specific requirements. First of all, it's all about semantic text with current footnotes, as you know, citation, and bibliographic data. In the publishing ecosystem, we love PDF.
But we need the web. It's a fact, even if sometimes you would like to see the frozen PDF format disappear. And it's all about XML. In academic publishing, XML is everywhere. It's the source of all joy and depression. Joy because we can do everything with XML.
Depression because mostly we create a big, big technical debt. Never forget that Docx is actually XML. The context with humanities scholars, it's all about text. I'm aware that we all come from a wide variety of fields here. So I need to clarify specificities for the humanities.
It's about text and sometimes data. If the text is the reason of the research, we must handle it with care. The context with the digital world, as seen as an evidence, our world is now a digital one. Even if you don't want to be connected or don't have an academia profile,
a Twitter dependency, or your own website, as researchers, we can't write a paper without metadata to generate content, bibliographic databases, or collaborative tools. And in the future, as we know, we will have to transform our research
into available data if we haven't already done so. Second part, the tool of paint with world LaTeX duality and Google Docs limitations. Microsoft Word, it's a realistic and depressing domination.
It's a proprietary software, as you know, and the major issue with Word and with LibreOffice Writer is the confusion between content and form, our structure and graphing rendering. Most of the time, Microsoft Word users think that graphing rendering is a structure, but a word in bold is not obviously an emphasis, although an emphasis can be in bold.
When a publisher requires a style sheet or gives some structured guidelines, it's not easy for the writer to understand and apply it. Those are the files that constitute a Word document when you typed hello and saved.
It's quite tricky just for one word. It's a picture from the information architect agency. LaTeX, it's very powerful, but too complicated. White and light tools like Overleaf reduce the complexity of LaTeX, but it's still a very restrictive tool.
We cannot ask the writer to not forget to close the bracket, for example, or to learn a new syntax. Google Docs is becoming very common with a lot of constraints. It's connection dependency, proprietary code, so bad for your privacy, as we know, and semantically limited.
It's the new Microsoft Word. What do we want now? Semantic content, data, meaningful artifacts, single source publishing, and easy interfaces. Semantic content, as researchers, we want to write text and to both inscribe and structure.
We need tools that allow to do that both. It's not just about Bolt and italic. Manifold artifacts like PDF, XML, HTML, Web, EPUB, and other formats like Docx, if you want.
And single source publishing, researchers and editors can't work on the same version of a document. Manifold artifacts, one source, like Word version for an author, InDesign version, XML version, it's hard to maintain three files version of one document.
What we want? Usable and efficient interfaces, easy and powerful. Interfaces like Google Docs introduce an attempt of efficient interfaces. We need different level of editing for the author, the editor, and data manager. Just a quick view of three tools that allow
structuration, dynamic bibliographic data, and Manifold artifacts with one unique source, like Markdown, CSL, and Pundock. Markdown is a great compromise between interoperability and simple markup. And Markdown is extensive with HTML classes.
Here an example of the markup and the rendering. As you can see, it's very simple. CSL for structural citations and bibliographies, with any bibliographic styles. There is many, many bibliographic styles. And Pundock for transform and convert,
from any source to a lot of formats. But you have to use a damn terminal. It's hard for a common user. Now, still, it's time to show you a tool as an answer of what researchers and editors want in human sciences field. Stilo is a modular and whizzy-whim.
What you see is what you mean, and not what you see is what you get. Text editor for scientific writing and publishing. First of all, Stilo is a modular solution for scientific writing. We bring Markdown, CSL, Pundock,
and a usable interface together. And we use hypothesis for real viewing. The text editor with markup Markdown, bibliographic data in BIPTECH, or using the Zotero API. Metadata management with YAML. And we have many other formats. And platform, the platform of Stilo
is in MongoDB, GraphQL, and ReactJS. Here, as you can see, Stilo is composed of three areas. It's not very nice.
In the center, you can see the content manager. It's just Markdown. On the left, you have the versioning, preview, export, bibliography, and informations.
And on the right, we have the metadata with three levels of management. Here's the version. On your left, table of contents, bibliography imported for BIPTECH files,
or from a collection of Zotero shared group. Editor mode for the metadata on the right. And another mode, the raw mode. You can add new fields as you want here. The preview is just an HTML export with a default still sheet.
And the preview, it's possible to annotate the preview for reviewing a paper, for example. We use Hypothesis, a great web annotation service. And Hypothesis allows you to use private groups for private annotations. And it's possible to export in many formats.
The file exports use three sorts of documents. The Markdown, of course. BIPTECH file for the bibliographic references. And the YAML for the metadata. We can use XSLT style sheet for the XML based on the schema of the requester.
Stilo changed the entire digital editorial chain of scholarly journals. And here, as you can see, an example for the nouvelle-vous journal with Stilo, HTML, and PDF.
For the end, Stilo lives in three acts a proof of concept, a unique tool to help scientific publishing, and now a piece of other tools like Nakala or Isidore.science to French project.
If you want some resources, you can find it here. And, of course, a team with Marcello, Artur, Margaux, me and many people who work on Stilo. Thank you.
Not now. It's an option.
We don't like very much that, but we have to do that. The question is real-time collaboration. Not now. It's asynchronous.
Because it's very low tech and we don't want to manage too much complexity. So it's for this year, I think, we have to... for us, too.