<?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 rasmusskjoldan on Medium]]></title>
        <description><![CDATA[Stories by rasmusskjoldan on Medium]]></description>
        <link>https://medium.com/@rasmusskjoldan?source=rss-75a5c934e84a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AlyhOVHaOxmViWbLICj1mg.jpeg</url>
            <title>Stories by rasmusskjoldan on Medium</title>
            <link>https://medium.com/@rasmusskjoldan?source=rss-75a5c934e84a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 07:40:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rasmusskjoldan/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[Open design, take two]]></title>
            <link>https://medium.com/@rasmusskjoldan/open-design-take-two-2e549aefb564?source=rss-75a5c934e84a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e549aefb564</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[open-source-design]]></category>
            <category><![CDATA[software-design]]></category>
            <category><![CDATA[magnolia-cms]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[rasmusskjoldan]]></dc:creator>
            <pubDate>Fri, 05 Jan 2018 09:21:38 GMT</pubDate>
            <atom:updated>2018-01-05T22:42:18.074Z</atom:updated>
            <content:encoded><![CDATA[<p>I’d like to share this story about open source design, an absolute favorite topic of mine. It’s been an important one to me for ages. But it died out, only to be reenergized recently.</p><p>Many years ago, back in 2006, I helped lead the design team of <a href="https://typo3.org/">TYPO3</a> which produced <a href="https://typo3.org/about/the-brand/style-guide/">the logo, font and styleguide</a> that has now been in use for over a decade.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VRXrFah_KHCSoHvp5nd_8Q.png" /></figure><p>We even created a full-featured free TYPO3 font called <a href="https://typo3.org/about/the-brand/style-guide/the-typo3-font/">Share</a>—drawn by <a href="https://carrois.com/">Ralph du Carrois</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jmmEA3Ryci1Ie6THLujfWQ.png" /><figcaption><a href="https://www.dafont.com/share-regular.font">https://www.dafont.com/share-regular.font</a></figcaption></figure><p>Back then, I had a very hard time onboarding new designers to the community and its open source project. The coders seemed to just keep coming — whereas one or two new designers were found, in a good year. And they often left again all too quickly.</p><p>I began wondering what it would take to make open source software interesting to designers — and we tried all sorts of things. We released the visual identity elements of TYPO3 under <a href="https://creativecommons.org/licenses/by-nd/2.5/">a Creative Commons license</a>, we reached out to everyone, met with designers to explain how awesome it was to share — and pretty much every attempt failed, miserably.</p><p>Open source was nice for developers — but the designers we found, typically wanted to be the sole créateur of what they designed and not part of a collaborative team producing things together — or they couldn’t see why they should do something without getting paid for the deliverables. They simply did not appreciate the concept of open source. And we failed to communicate it.</p><p>I reached out to several other open source projects to hear how it was working out for them. They pretty much all said the same thing as I eventually noted:</p><p>“Just give up”.</p><p>— Open source just didn’t translate well to design. Instead, just collect some dough and get agencies or <a href="http://www.d7ux.org/">freelancers to help out</a>.</p><p>One thing worked, though: Opening up the design <em>process.</em></p><p>Here’s an <a href="http://rasmusskjoldan.com/post/102960730333/gathering-input-ideas-on-dashboard-functionality">example</a> of how we opened up the design process on <a href="https://www.neos.io/">the Neos project</a>, three years ago, for building a system of composable dashboard elements:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pySNBRVvSbPMjxs31q9zKg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NVDBeeI67bg3qx10QAVHxw.jpeg" /></figure><p>We did that many times on the Neos team and it worked well — and brought us valuable feedback.</p><p>But in terms of real open design — as in<em> collaborating on the design</em>, it was a long drought. From 2008 to 2015, I occasionally looked into what was going on. But I had given up. Some interesting open source architecture projects emerged here and there — but they all seemed to have similar problems with gaining momentum. The vanity of design culture seemed to play a big part.</p><p>Yet, here’s the thing. It is actually growing now.</p><p>Take a lot at <a href="https://www.goabstract.com/">Abstract</a> for example, version-control of your Sketch files:<br><a href="https://www.goabstract.com/">goabstract.com</a></p><p>Or look to Mozilla’s <a href="https://blog.mozilla.org/opendesign/">open design</a> efforts:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eO8odTOH8hewa1ft3JyoUQ.png" /></figure><p>Red Hat</p><p>Brad Frost also wrote a nice piece about <a href="http://bradfrost.com/blog/post/designing-in-the-open/">designing in the open</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*Z96p5CcSoSGzddJ7LOR-Qw.png" /></figure><blockquote>“<strong>It’s uncomfortable to share works in progress</strong>– We as humans fear failure. We hate making mistakes. We don’t like sharing things that aren’t the best representations of who we are.”</blockquote><p>And most notably, things like the <a href="http://opensourcedesign.net/summit/">Open Source Design Summit</a> just happened:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v_Dj8o-GeR1mjN6_gzIpig.jpeg" /><figcaption>Group photo from the first open source design summit</figcaption></figure><p>I met with Open Source Design in Berlin after the summit and I consider myself reborn when it comes to open design. I’ll be a proud member of that community and try to help as much as I can.</p><p>We surely are a crowd in love with technology — turned designers — but I think open source design now honestly has a promising future. One where we can build on top of each other’s design patterns and where we can easily enable our communities to help build our products.</p><p>Look at this recent, stellar example from the <a href="https://www.netlifycms.org/">Netlify CMS</a> community:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kxEu3pShJfQKZxHOfq8KOA.png" /><figcaption>UI sketches from a community contributor to the Netlify CMS: <a href="http://t.umblr.com/redirect?z=https%3A%2F%2Fgithub.com%2Fnetlify%2Fnetlify-cms%2Fissues%2F490&amp;t=MmQyZjczNTVjODNhY2U1ZjE5MThkMzZmMThmMDAxOThmNDZkOTVlOCx6Z0N5THBqQQ%3D%3D&amp;b=t%3A4QVBPgj7fI93qXw9UjnaPg&amp;p=http%3A%2F%2Frasmusskjoldan.com%2Fpost%2F166745634138%2Fopen-design-take-two&amp;m=1">github.com/netlify/netlify-cms/issues/490</a></figcaption></figure><p>There’s also <a href="https://github.com/netlify/netlify-cms/issues/982">a brand new effort</a> to do an Abstract project for the Netlify CMS.</p><h3>Open design at Magnolia</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PJuZgTptoK6TSBsQxe5DhQ.png" /></figure><p>Today at <a href="https://www.magnolia-cms.com/">Magnolia</a> where I head product management and UX, we’re seeing this related pattern:</p><p>Agencies and customers working with our software are asking for (and getting) the Sketch files of our composable UI — to let them re-assemble author interfaces to match their projects. We’re also looking at other ways to open up our design to allow for contributions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qDXuyjAGZ73R50c0_stv4Q.jpeg" /><figcaption>Sketch file covering all the UI components of the Magnolia CMS, composable for projects that need tailored author experiences</figcaption></figure><p>A big thanks to the folks from <a href="http://opensourcedesign.net/">Open Source Design</a> for showing the way, in a place I thought would continue to be dark and impenetrable.</p><p>What are other good examples? I know they’re out there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e549aefb564" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making an iPad Pro my primary computer (and it’s not a test)]]></title>
            <link>https://medium.com/@rasmusskjoldan/making-an-ipad-pro-my-primary-computer-and-it-s-not-a-test-9befc5c45a36?source=rss-75a5c934e84a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9befc5c45a36</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[ipad-pro]]></category>
            <dc:creator><![CDATA[rasmusskjoldan]]></dc:creator>
            <pubDate>Tue, 19 Jan 2016 20:43:01 GMT</pubDate>
            <atom:updated>2016-01-23T13:57:52.920Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dXxrfyUgAdevMYC8d9NQcw.jpeg" /><figcaption>My desk at the Magnolia headquarters in Basel.</figcaption></figure><p>In late December 2015, I replaced my Macbook Pro with an iPad Pro to take on the role as primary workstation. These are my notes on how that went down. Since so many others have described — in detail — the annoyances that come with working fully on iOS, I’m going to focus on other more positive aspects. And honestly, if you think the big question is if the iPad Pro can replace the laptop or not, you’re in for a little treat. After my first 3 full weeks of working all-day on the iPad, it became clear that there’s something far more interesting going on than the replacement viability debate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*biWyCFXYf49e8T1Hjlvsow.jpeg" /><figcaption>Enjoy that I can configure the keyboard and screen to match the surroundings. This is me on a long train ride in Switzerland.</figcaption></figure><h4>The harddisk is no longer my home</h4><p>I’ve switched completely from a MacBook Pro to an iPad Pro. You might think this is just yet another test if it really can — or cannot — replace the “real computer”. But the more I observe my own usage pattern after moving to the iPad, this becomes clearer:</p><p>The entire discussion about whether or not the iPad Pro can replace the laptop is not the real question to explore. I’m not switching from one thing to another one thing — but from relying largely on one main computer accessing many things — to a much more modular computing setup. The harddisk is no longer what I keep organized and controlled. The main computer is gone. I’m no longer trying to set up that one computer to make it match everything that I do and aspire to. I just need thinner and much more modular clients to jack me in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DOmwZFJ4D_bbstp58Xcfrw.jpeg" /><figcaption>Before trying it out, I was worrying a bit about how setup would work on a plane. But it works and you’re allowed to use Bluetooth to pair the devices.</figcaption></figure><p>Letting go of access to the file system effectively pushes you — big time — towards accessing and creating your assets via multiple devices in multiple ways. We’ve talked about this for a long time but even though I’ve depended on assets in the cloud for years, using many devices to access them, this transition to an iPad Pro was the last great push. One that I will probably never return from. And it was a push in that direction far more powerful than any ChromeBook could have sparked.</p><p>My digital home is just no longer the disks I control but anything I have the password to. That coupled with a physically modular setup gives you something much more surprising and deeper than any small or big annoyance you can spot while moving from OS X.</p><p>Now let’s dive into the observations and also look at the peripherals I added to make it work.</p><h3>The details</h3><p>Remember that unlike other posts on the subject, this is not a temporary test, a review or an experiment. I’ve spent all the money I had for buying new gear — so it HAS to work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f7cgni67EYWsASCap9lcoA.jpeg" /><figcaption>Surprisingly, I can work for hours with the tablet just being held up by the Smart Cover on my knees. Oh, the joy of not having an overheating MBP on the lap anymore.</figcaption></figure><p>Now why would I spend so much time going into details about all this?</p><p>First of all, selecting tools will always impact your work. It’s important.</p><p>If you place yourself in front of an email app, you will start spending time answering emails. If you have windows to move around, you’ll see yourself spending time doing so. Same goes for hardware; when you pick a laptop with loads of memory, you will fire up more apps and multitask more. It goes on: Certain cameras will push you to take certain types of photos…</p><p>So my questions easily turn into these kinds: Will defaulting to a safe choice of workstation also lead to a certain type of work output? How will a more uncommon setup impact the results of those endless hours I spent with the tools? After my first weeks, it’s become clear it does indeed impact the output.</p><p>The other reason for posting about is this: Most of the iPad Pro reviews state that the Pro cannot replace your laptop. After looking through the list of pros and cons I wrote down, I realized it just wasn’t the case for my needs. That simple realization about the overwhelming amount of reviews may be helpful to others, otherwise turning down full-time tablet computing. And on that note, “<a href="http://www.speirs.org/blog/2015/11/30/can-the-macbook-pro-replace-your-ipad">Can the MacBook Pro Replace Your iPad?</a>” is a fun read :-)</p><h4>Using (not testing) the software I help build</h4><p>Because I work in product management at <a href="https://www.magnolia-cms.com/">Magnolia International</a> — a company that has invested in iPad compatibility for several years — I also want to champion using our own CMS with the iPad. I think specialized testing of such will always be inferior to working on your normal gear, doing real work. When Magnolia 5.0 was released, it was a pretty big deal that you could use an advanced CMS on an iPad. Today, that doesn’t sound quite as wild — but when you look at most of the enterprise class CMS’s out there, there’s typically still a long way ahead.</p><h4>The discharged gear</h4><p>Until New Years 2015, I ran on a retina MBP, mid-2014, 13 inch, 2.8 ghz with 16 gigs — on betas of El Capitan. Some of the software I used most frequently included Adobe Photoshop, InDesign, Illustrator, Axure, Slack, Hipchat, PhoneView, Stache, 1Password, OmniFocus, <a href="http://jadengeller.github.io/Helium/">Helium</a>, Kaleidoscope , Evernote, every alpha/beta browser I could get my hands on — and a ton of other stuff that I’m already starting to forget but which was all very important, eh.</p><h4>My new setup</h4><p>Here’s what I bought instead:</p><ul><li>iPad Pro 128, WIFI, Silver</li><li>Magic Keyboard 2</li><li>Apple Pencil</li><li>A Smart Cover (white like the silver iPad front)</li><li>iPhone 6s Plus (I will get back to why that’s of importance in this context)</li></ul><h4>Mobility &amp; convenience</h4><p>I also ordered these accesories which I think are important to make it all work out. I work from both Copenhagen and Basel — which means the gear also needs to work well while traveling.</p><p><a href="http://iskelter.com/product/canvas-smart-desk-for-ipad-pro/">iSkelter Canvas Smart Desk</a> (the pro, iPad variant)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KW0ftxt4ziM7z4n_txfdqA.jpeg" /></figure><p><a href="https://www.sfbags.com/collections/magic-keyboard-cases/products/magic-keyboard-socket">Waterfield Magic Keyboard Socket</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vqVExAWyaDN5i6MpYhMIIA.jpeg" /></figure><p><a href="http://wrappersuk.com/collections/ipad-pro-cover/products/ipad-pro-wool-felt-cover-grey-portrait?variant=10457254851">Wrappers iPad Pro Wool Felt Cover Grey Portrait</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eJIPtEtBLrxIYN-SU0B9Qw.jpeg" /></figure><h3>The backdrop</h3><p>The way I look at it, choosing a computer setup is similar to choosing an instrument for a musician. I’m not at all deep into the technical specifications of computers — just like musicians often aren’t that concerned with the factual specifications of their instrument. But how it plays out, what they can do with it, how it looks and feels — and quite simply what they can create in symbiosis with the instrument… That counts.</p><p>My folks are both musicians and seeing my dad speculate over the subtlest delicate differences between the sounds of two grand pianos is a level of gear obsession to which I will never aspire.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gk5uyO9Xai0mKXwKxqH5Iw.jpeg" /><figcaption>The iSkelter lapdesk. Multitasking surprisingly happens naturally via the iPhone when something is cooking on the iPad</figcaption></figure><h4>But what about Photoshop?</h4><p>Apart from having to give back my old computer to my now former employer, the job change also meant new responsibilites and thus, new computer tasks. In the past, I’ve been producing tons of UI and design files for both screen and print. In my new job, I don’t have any design tasks — which basically just meant I didn’t necessarily have to run Adobe CC anymore. That’s a pretty big thing to let go of for someone who has been using Photoshop for hours every day for 20 years.</p><p>When it dawned upon me that I had the option to do something new with my tech setup, I spent countless hours in November and December of 2015 researching. And I put a great deal of thought into it after I figured out that I didn’t need to just go with an ordinary full OS X setup anymore. The easy choice would have been to just go out and buy a Macbook Air. Apart from the fact that I find the Air somewhat ugly, I just wanted to explore the options more.</p><p>I started by <a href="https://www.facebook.com/rasmusskjoldan/posts/10153264023276593">asking friends on Facebook</a> for help. Lots of great and insightful input from them — but unfortunately it’s all in Danish.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AaU-FtjlGS8Wsa8we808EQ.jpeg" /><figcaption>The pro with the magic keyboard on a flight.</figcaption></figure><h4>The big list of cons</h4><p>I then made a list of what I would be saying goodbye to if I left OS X.</p><p>What surprised me was this:</p><p>The list really wasn’t that long. Some of the painpoints of trying to move to an iPad Pro which others have described are just not relevant to everyone.</p><p>The only big issue was a private theme: Using Bridge and Photoshop for my decade-long photography addiction. But given that it was almost only a private concern, that naturally meant I should just get me a cheap used MBP for that. I also used to be a heavy Axure user — but now I can’t wait to start using something else. Some have pointed out that using multiple applications (more than 2 in split-screen) is a big thing only possible in iOS X. To me, I was looking forward to blinders. Because my computer can do a gazillion things at once, it doesn’t mean that it’s a good habit.</p><p>Btw. if you want a different view on how to use the iPad Pro as primary computer, be sure to check out <a href="https://medium.com/@jon/how-i-work-on-an-ipad-pro-ec2894304a47">Jon Wheatley’s good post on Medium</a>, too.</p><p>After having looked closely at that list of cons and trying out the iPad Pro several times, the choice ended up being straightforward. I could see it all come together and could suddenly feel the realism in the project.</p><h3>Help. Am running in circles!</h3><p>Interestingly so, my new setup greatly closely resembles a computer setup I used many years ago. I was the editor of a mobile computing section of an online Mac publication back in the late 90&#39;s. Back then, my mobile gear was a Newton MessagePad 130 with its stylus and an external, corded keyboard — plus a now vintage Nokia phone with a modem connecting the MessagePad to the Internet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/926/1*wDh6EQaQzQzuT4joxg3ybw.jpeg" /><figcaption>The setup I had in 1998–1999: A Newton MessagePad with the external keyboard. Am I running in circles?</figcaption></figure><p>What I really like about the iPad Pro + Pencil + a Magic Keyboard is just the same. It’s not all stable at times but the advantages of modularity far outweigh the annoyances.</p><h3>Hello, modular computing</h3><p>What this really comes down to is that I enjoy accessing and creating stuff in ways that work well with the context I’m in, from moment to moment. Just like with the Newton MessagePad, I’ve chosen a setup that’s as modular as it can be. The variations of how to use the iPad are plentiful. With or without the detached Bluetooth keyboard, with or without the Pencil — standing, sitting or lying — in combination with the phone — or even with an OS X computer capable of running those apps that iOS cannot (I have a Mac Mini for backup access to my old files when I need to pull them into the cloud). Adobe’s handovers to desktop apps are well done for example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IPVgps1KgOYqEjw9Mm0zPQ.jpeg" /><figcaption>Adobe Comp is a very impressive tool.</figcaption></figure><p>The big surprise on repeat:</p><blockquote><em>My digital home is no longer the disks I control but anything I have the password to.</em></blockquote><p>Be that storage on my iPad Pro, cloud services, external drives or SSD’s at home. The point is that I’ve stopped trying to control the files in the file system on disks but am relying solely on ‘access’ through whatever. It feels quite liberating to give up all the control mania of <em>the one computer</em>, carrying the one disk that almost came to the point of mirroring my personality.</p><p>I can easily think of going away from the iPad Pro. But giving up this modular computing style is probably not going to happen anytime soon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9befc5c45a36" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>