<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Julia Donaldson on Medium]]></title>
        <description><![CDATA[Stories by Julia Donaldson on Medium]]></description>
        <link>https://medium.com/@julia.donaldson?source=rss-ea1a8d50a909------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5v3CE2gyoDzYymGLj5e3NA.jpeg</url>
            <title>Stories by Julia Donaldson on Medium</title>
            <link>https://medium.com/@julia.donaldson?source=rss-ea1a8d50a909------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:49:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@julia.donaldson/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Using Mobiledoc in Ember applications]]></title>
            <link>https://medium.com/@julia.donaldson/using-mobiledoc-in-ember-applications-b97e91581f68?source=rss-ea1a8d50a909------2</link>
            <guid isPermaLink="false">https://medium.com/p/b97e91581f68</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[ember]]></category>
            <category><![CDATA[mobiledoc]]></category>
            <dc:creator><![CDATA[Julia Donaldson]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 17:11:31 GMT</pubDate>
            <atom:updated>2019-03-22T19:19:59.155Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently discovered <a href="https://bustle.github.io/mobiledoc-kit/demo/">Mobiledoc</a> while working on a project that required a custom text editor for creating posts. It is a fantastic solution for anyone looking to edit and display rich content in their application.</p><p>The majority of the API documentation focuses on the implementation of Mobiledoc with plain Javascript — one of the benefits of Mobiledoc is that it is framework-agnostic. However, I found myself wanting more examples within the context of an Ember application. This small tutorial outlines what I have learned using Mobiledoc with Ember.</p><p>For this demo, I created a basic blog app that lets users add memes and dancing bananas to their posts. The memes are Mobiledoc cards and the dancing bananas are Mobiledoc atoms, both created using Ember components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yQSUUshCvZ7V8ptLr_Bn5Q.png" /><figcaption>Blog app with posts created with Mobiledoc</figcaption></figure><h4>Let’s get started:</h4><p>First, install the two addons that are available for using Mobiledoc in Ember applications:</p><pre>$ ember install ember-mobiledoc-editor<br>$ ember install ember-mobiledoc-dom-renderer</pre><p>With these, we essentially get two main components — the <a href="https://github.com/bustle/ember-mobiledoc-editor">editor component</a> and the <a href="https://github.com/bustle/ember-mobiledoc-dom-renderer">renderer component</a>.</p><p>For this example, we want to include the {{mobiledoc-editor}} component as part of our form for creating new blog posts.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1f48841adb9afbe75d8deb96ba4d098c/href">https://medium.com/media/1f48841adb9afbe75d8deb96ba4d098c/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vtJFp07RF68mBO1a_1clzw.png" /><figcaption>The new post form with {{mobiledoc-editor}} and our custom toolbar component</figcaption></figure><p>I’m using the component’s block form which allows me to pass the editor into my own custom toolbar component {{editor-toolbar}}.</p><p>The editor addon does provide a basic toolbar component, but it is not as easily customizable. Instead, I combined the smaller provided components {{mobiledoc-markup-button}}, {{mobiledoc-section-button}}, and {{mobiledoc-link-button}} to customize my own toolbar for use in any editor instance. This will also allow me to easily add custom buttons and actions later.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ecbaaeefc3b11310644bc6e36e929e07/href">https://medium.com/media/ecbaaeefc3b11310644bc6e36e929e07/href</a></iframe><p>The {{mobiledoc-editor}} component’s on-change attribute accepts an action that will send every time the document within the editor is updated. In this example, we pass an action called mobiledocWasUpdated that will update our controller’s mobiledoc property.</p><p>The editor serializes the post into Mobiledoc JSON format, so once the form is submitted, the createPost action will stringify the Mobiledoc object and save it as the post’s body.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6c84f92cf049eeb2cfb80a864d3aef1e/href">https://medium.com/media/6c84f92cf049eeb2cfb80a864d3aef1e/href</a></iframe><p>Now that we have implemented the editor component within our form to create new blog posts, we need to render the post’s content when we view that post.</p><p>Each post’s body is saved and sent to our backend as a JSON string. I added a computed property on the model that returns the parsed mobiledoc object for rendering.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/071e45add9a57ba3841f676b44dc7b7e/href">https://medium.com/media/071e45add9a57ba3841f676b44dc7b7e/href</a></iframe><p>To display each post, I created a component called {{post-view}} that contains the {{render-mobiledoc}} component. We simply need to pass the post’s mobiledoc into the component for it to render to the DOM.</p><p>The post’s content will be rendered as individual DOM elements, giving us the the freedom to display and style the content uniquely for different scenarios within an application — a powerful aspect of Mobiledoc.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d3a4be4cfef8e9ed7afa395c897cef63/href">https://medium.com/media/d3a4be4cfef8e9ed7afa395c897cef63/href</a></iframe><p>Now we have basic Mobiledoc editing and rendering working in our app!</p><h4>Adding cards and atoms</h4><p>Now we can add cards and atoms to create even richer, more customized content for our posts. Cards are blocks of rich content, while atoms are inline. Thanks to the addons we installed, we can use Ember components as cards and atoms within our Mobiledoc.</p><p>Let’s make a component card that lets users add and create their own meme as part of their blog post.</p><p>First, create a button with an action for adding the card in our toolbar component. The editor we pass into our toolbar provides us with two actions for adding cards, ‘addCard’ and ‘addCardInEditMode’. We will add our card in edit mode, which will render the ‘card editor’ template into our editor so the user can edit immediately.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/86c018f497a1a81e4a21d6f3cb3f8fc3/href">https://medium.com/media/86c018f497a1a81e4a21d6f3cb3f8fc3/href</a></iframe><p>Now we need to create the components for our meme-card. In order to be able to both display and edit the card in our posts, we must generate two components.</p><p>The component {{meme-card}} will be called for displaying the card, and the component {{meme-card-editor}} will be called for editing the card. (The ‘editor’ suffix is necessary for the addon to recognize the two templates as belonging to the same card.)</p><pre>$ ember generate component meme-card<br>$ ember generate component meme-card-editor</pre><p>Here are the components:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1f1788ab17d3e41a0b1c95b209b2c56f/href">https://medium.com/media/1f1788ab17d3e41a0b1c95b209b2c56f/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/55d895e082655be02d7b806dc32e0723/href">https://medium.com/media/55d895e082655be02d7b806dc32e0723/href</a></iframe><p>The {{mobiledoc-editor}} component provides us with the functions ‘saveCard’, ‘editCard’, and ‘removeCard’. The editCard action toggles the card between it’s display and editor components. To save changes made to the card, the updated values are passed in using the hash helper. This becomes the card’s payload in the serialized mobiledoc. The saveCard action must fire for the card’s payload to be updated in the larger mobiledoc object.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v3cBAJHBf5FOjbJbM3XBeA.png" /><figcaption>editing the card using the {{meme-card-editor}} component</figcaption></figure><p>The power of Mobiledoc, especially in Ember, is that component cards are extremely customizable and can do a lot on their own. All of the logic that lets our user choose images and input text for their meme is contained within our custom meme-card-editor component:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c8955716e4bda68ae876c5e819834655/href">https://medium.com/media/c8955716e4bda68ae876c5e819834655/href</a></iframe><p>In this particular example, my component for displaying the meme-card does not have any custom logic. However, we could potentially add logic for manipulating the payload data if we wanted to.</p><p>The last step is to pass our card into our {{mobiledoc-editor}} and {{render-mobiledoc}} components.</p><p>The {{render-mobiledoc}} component takes an array of the component card names (as strings). The {{mobiledoc-editor}} component takes an array of cards (objects). The addon ember-mobiledoc-editor provides a ‘createComponentCard’ helper that returns a card object from our component.</p><p>I decided to create helpers to return the arrays needed, so as I add more cards, I can easily pass all of them into any instance of an editor or renderer.</p><pre>$ ember generate helper mobiledoc-component-cards<br>$ ember generate helper mobiledoc-card-names</pre><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/53cc7a0fc975eb30b585188211109a81/href">https://medium.com/media/53cc7a0fc975eb30b585188211109a81/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ce30c4aa8e85bac1455aecf12aee42eb/href">https://medium.com/media/ce30c4aa8e85bac1455aecf12aee42eb/href</a></iframe><p>Use the helpers to pass the card names to the renderer and the component cards to the editor, as shown below.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b8803c5bcaee6b6d6fa0041090e8f838/href">https://medium.com/media/b8803c5bcaee6b6d6fa0041090e8f838/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b55bd81603454d1c5704073da7b25762/href">https://medium.com/media/b55bd81603454d1c5704073da7b25762/href</a></iframe><p>And that’s it! Our meme component card is implemented and works.</p><p>The mobiledoc-editor addon also supports the creation of component atoms (the dancing bananas in this example). Atoms are inline sections of content that are imbedded directly in a line of text. The Github <a href="https://github.com/bustle/mobiledoc-kit/blob/master/ATOMS.md">documentation</a> describes atoms as “effectively read-only inline cards.” They do not toggle between a display and edit state.</p><p>Adding a component atom is done in the exact same manner as cards, so I won’t repeat the steps. However, you can take a look at the code <a href="https://github.com/donaldsonjulia/mobiledoc-demo-app">here</a> and see how I added a dancing banana atom to this same project as an example.</p><p>View the demo app: <a href="https://mobiledoc-demo-app.firebaseapp.com/">https://mobiledoc-demo-app.firebaseapp.com</a></p><p>View the code: <a href="https://github.com/donaldsonjulia/mobiledoc-demo-app">https://github.com/donaldsonjulia/mobiledoc-demo-app</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b97e91581f68" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ember.js, mentorship, and the confidence gap]]></title>
            <link>https://medium.com/@julia.donaldson/ember-mentorship-and-the-confidence-gap-8c0b93dc1ccd?source=rss-ea1a8d50a909------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c0b93dc1ccd</guid>
            <category><![CDATA[imposter-syndrome]]></category>
            <category><![CDATA[ember]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[mentorship]]></category>
            <dc:creator><![CDATA[Julia Donaldson]]></dc:creator>
            <pubDate>Thu, 07 Sep 2017 18:15:31 GMT</pubDate>
            <atom:updated>2019-03-22T19:20:58.648Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DGeq_vHq3c_Kso0k-VCN8w.png" /><figcaption>A Q&amp;A app I built using Ember</figcaption></figure><p>Less than a year ago, I graduated from bootcamp with a keen sense of accomplishment and unbridled optimism. I was excited to embark on a new career as a frontend developer and continue to grow as a coder. My decision to quit my previous job to pursue an interest in web development felt more like the right decision than ever.</p><p>What I had not anticipated was just how challenging the entry-level hurdle would be. Most “junior-level” job postings came with minimum requirements of years of experience, a degree in computer science, and a “deep proficiency” in full-stack development with multiple languages and frameworks. Suddenly, everything I had worked so hard to learn and build seemed inadequate.</p><p>As weeks passed, I found myself increasingly paralyzed by imposter-syndrome. My passion, skills, and willingness to work hard seemed completely overshadowed by my lack of professional experience as a developer. Most companies politely told me that they were only interested in much more experienced applicants. I felt more and more like an outsider in the tech world — as a woman, yes, but most of all because I was a beginner.</p><p>Much has been written on imposter-syndrome and its prevalence among even the most senior and accomplished developers in the industry. The trouble with imposter-syndrome as a new developer is that you don’t have as much evidence with which to argue against your insecurity. Sure, my Github account had plenty of small apps and projects built as learning exercises, but I was extremely self-critical and none of them felt like “real-world” projects to me. Mentorship with Ember changed that for me.</p><p>I was fortunate to find mentorship through <a href="https://www.thisdot.co/">This Dot</a> and its co-founder, <a href="https://medium.com/u/eccf3ca48bae">Taras Mankovski</a>, who urged me to explore Ember as a framework. Ember provided a convention-based architecture that guided me as a new developer and reinforced best-practices in my code.</p><p>Learning Ember not only taught me how to build applications “the Ember way”, but how to better conceptualize the building of web applications in general. Ember’s test suite made test-driven development approachable and easy-to-adopt. And the extensive library of Ember CLI addons is not only a fantastic resource for easily implementing features, but also a valuable resource for learning from other developer’s code.</p><p>Ember increased my productivity and as a result I felt emboldened to add new features to my apps. The framework’s built-in conventions gave me the confidence to spend less time worrying about things like “did I configure this correctly?” and instead to push myself forward as a developer by trying new things. I spent less time feeling insecure and more time writing code. Simply put, the process of learning and building with Ember makes me feel like less of an imposter, and more like a developer.</p><p>Recently I spoke with an accomplished, senior developer who shared his own story of breaking into the industry years ago. He told me that a pivotal moment for him in his early career was the realization that he did not need anyone’s permission to write code and build web apps. He didn’t need to wait for a job title to be a web developer, he was a web developer because he was building web applications. For me, mentorship with Ember was the key to bridging that confidence gap.</p><p>Ember magnifies the skillset you bring to it, which makes it ideal as a framework for new developers like me. You can do a lot, fast. And yet it is equally as powerful for more advanced developers. You can be creative and focus on big ideas, instead of boilerplate configuration. It encourages me to be more ambitious with my projects, and helps me to build things I am proud of.</p><p>Mentorship has been game-changing for me as a new developer. What I did not expect was to find an additional mentor in Ember itself. The framework and its larger community of enthusiasts have embraced and guided me as I continue to learn and grow. Ember not only helps me to build ambitious web applications, but it also encourages me to be ambitious web developer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c0b93dc1ccd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>