feat: Added local markdonw content after importing from strapi/sanity
This commit is contained in:
joostdecock
parent
3180abd2a3
commit
052a85e1a4
830 changed files with 35118 additions and 0 deletions
82
markdown/org/blog/announcing-freesewing-library/de.md
Normal file
82
markdown/org/blog/announcing-freesewing-library/de.md
Normal file
|
|
@ -0,0 +1,82 @@
|
|||
---
|
||||
author: "joostdecock"
|
||||
caption: "Ich trinke nicht, aber das schien für einen Festbeitrag angemessen zu sein ¯\\_(ツ)_/¯"
|
||||
date: "2018-08-25"
|
||||
image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a6b5a3918ad412f7fb434413fafcc82107109d87-1920x1276.jpg"
|
||||
intro: "Vor genau einem Jahr öffneten sich die Türen von FreeSewing.org für unsere Nutzer,während die von makemypattern.com eines dieser -Schilder erhielten."
|
||||
title: "Wir feiern ein Jahr von FreeSewing.org: Ankündigung der FreeSewing-Library"
|
||||
---
|
||||
|
||||
|
||||
Vor genau einem Jahr öffneten sich die Türen von FreeSewing.org für unsere Nutzer,während die von makemypattern.com eines dieser *Wir sind umgezogen*-Schilder erhielten.
|
||||
|
||||
Rückblickend auf [den Blogbeitrag von vor 12 Monaten](/blog/open-for-business), es ist fast unglaublich, dass die damals angekündigten Dinge erst ein Jahr alt sind. Das Konzept eines Entwurfs, die Vergleichsfunktion oder auch die Möglichkeit Schnittmuster papierlos zu übertragen. Sie alle feiern heute ihren ersten Geburtstag.
|
||||
|
||||
Aber nicht diese Website, weil [die bevorstehende DSGVO-Einführung](/blog/gdpr-plan) uns zwang unsere jekyll-basierte Website zugunsten eines neuen Frontends zu beerdigen. Dies geschah irgendwann im Mai.
|
||||
|
||||
## Weitere Sprachen mit weniger Sprachen
|
||||
|
||||
DSGVO war nur Teil dieser Geschichte. Weitere Gründe für den Rewrite unserer Seite waren unser Wunsch, mehrere Sprachen zu unterstützen und unseren Technologie-Stack zu vereinfachen.
|
||||
|
||||
Mit anderen Worten, wir wollten Menschen erreichen, die verschiedene Sprachen sprechen, und wollten die Anzahl der dafür erforderlichen Programmiersprachen überschaubar halten.
|
||||
|
||||
### Mehr natürliche Sprachen
|
||||
|
||||
In dieser Hinsicht haben wir uns bemerkenswert gut geschlagen. Sie werden zwar nicht alle Inhalte übersetzt vorfinden, aber die wichtigsten Funktionen dieser Website sind sind nun in fünf Sprachen verfügbar:
|
||||
|
||||
- Englisch
|
||||
- Deutsch
|
||||
- Spanisch
|
||||
- Französisch
|
||||
- Holländisch
|
||||
|
||||
Das ist wirklich zu 100% der großartigen Arbeit von [unseren wunderbaren Übersetzern](/i18n/) zu verdanken.
|
||||
|
||||
### Weniger Programmiersprachen
|
||||
|
||||
Der Wechsel von [Jekyll]() zu einem [Nuxt](https://nuxtjs.org/)-basierten Frontend hat [Ruby](https://www.ruby-lang.org/) aus unserem Technologystack entfernt. Freesewing.org läuft jetzt auf JavaScript, PHP und ein wenig C (was wir jetzt ignorieren werden).
|
||||
|
||||
Aber das Entfernen von Programmiersprachen ist kein *Selbstzweck*. Vielmehr besteht das zugrunde liegende Ziel darin, die Dinge zu vereinfachen, es den Menschen leichter zu machen, sich einzubringen und letztlich mehr Mitwirkende anzuziehen, damit das Projekt wachsen und florieren kann.
|
||||
|
||||
Jetzt ist die Gestaltung/Entwicklung von Schnittmustern kein unüberwindliches Hindernis mehr. Wir haben nun [Benjamin](/patterns/benjamin), [Florent](/patterns/florent), und [Sandy](/patterns/sandy), um dies aufzuzeigen. All diese Schnitte wurde von Menschen beigesteuert, für die Freewing zunächst neu war, sie gingen durch das Design-Tutorial und schufen am Ende ein eigenes Schnittmuster.
|
||||
|
||||
Wir würden uns wünschen, dass mehr Menschen in ihre Fußstapfen treten. Den Gestaltungsprozess so einfach wie möglich zu gestalten war lohnenswerte Zeitinvestition.
|
||||
|
||||
## Wir künden die FreeSewing-Library an
|
||||
|
||||
In den letzten zwei Monaten habe ich mir eine Auszeit vom Schnitte entwerfen und dem Nähen genommen, um an der nötigen [Technischen Weiterentwicklung ](Yhttps://en.wikipedia.org/wiki/Technical_debt) zu arbeitet.
|
||||
|
||||
Konkret habe ich mich dazu entschlossen, unser Core-Backend von Grund auf in JavaScript neu zu schreiben. Aber es gibt eine Wendung. Es ist nicht länger ein Backend. Es ist eine Library, die Sie benutzen können. sowohl in Ihrem Browser, als auch auf dem Server mit [node.js](https://nodejs.org/).
|
||||
|
||||
Sie befindet sich aktuell in der Version 0.10 und ist zusammen mit dem FreeSewing-Core feature complete. Sie ist [auf GitHub](https://github.com/freesewing/freesewing) und [NPM](https://www.npmjs.com/package/freesewing)verfügbar und ist vollständig dokumentiert unter [developer.freesewing.org](https://developer.freesewing.org/).
|
||||
|
||||
Obwohl die API mehr kann als der Core ist sie trotzdem schlanker:
|
||||
|
||||
|
||||
|
||||
Das ist eine gute Nachricht, wenn Sie sich fragen.
|
||||
|
||||
## Was passiert als Nächstes?
|
||||
|
||||
Es muss noch viel Arbeit geleistet werden, bevor wir sie auf freesewing.org einsetzen können:
|
||||
|
||||
|
||||
- Alle unsere bestehenden Schnittmuster müssen auf die JS-Version abgestimmt werden. [Brian](https://github.com/freesewing/brian) ist der erste Schnitt, der portiert wurde.
|
||||
- Ein Rewrite unseres Datenbackends in JS. Da wir dadurch die PHP-Programmiersprache aus unserem Stack entfernen können.
|
||||
- Eine neue Website mit der FreeSewing-Library und unserem neuen Daten-Backend erstellen.
|
||||
|
||||
Das ist wirklich eine Menge Arbeit, und obwohl ich hoffe, dass wir bis Ende des Jahres gute Fortschritte gemacht haben, kann ich nicht versprechen, dass dies geschehen wird.
|
||||
|
||||
## Aber ich will nur Schnittmuster
|
||||
|
||||
Die Chancen stehen gut, dass Sie sich nur für Schnittmuster interessieren. Was du willst, sind mehr Schnittmuster, bessere Schnitte, mehr verschiedene Schnittmuster. Und all dieses Neuschreiben ist nicht unbedingt das, womit wir Ihr Interesse wecken können.
|
||||
|
||||
Ich weiss das. Ja wirklich. Ich für meinen Teil habe eine Liste von Mustern, die ich gerne der Seite hinzugefügt sehen möchte. Und meine Arbeit an den anderen Bereichen des Projekts hält mich davon ab, sie hinzuzufügen.
|
||||
|
||||
Aber ich glaube, dass die Investition in eine optimierte Entwicklungsarbeit langfristig einen positiven Effekt haben wird.
|
||||
|
||||
Wenn wir nur ein paar zusätzliche Muster wollten, wäre dies nicht der richtige Ansatz. Aber wenn wir viele neue Schnittmuster wollen, glaube ich, dass es sich auszahlt.
|
||||
|
||||
Und ich möchte viele Schnittmuster haben.
|
||||
|
||||
|
||||
109
markdown/org/blog/announcing-freesewing-library/en.md
Normal file
109
markdown/org/blog/announcing-freesewing-library/en.md
Normal file
|
|
@ -0,0 +1,109 @@
|
|||
---
|
||||
author: "joostdecock"
|
||||
caption: "I don't drink, but this seemed appropriate for a celebration post ¯\\_(ツ)_/¯"
|
||||
date: "2018-08-25"
|
||||
image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a6b5a3918ad412f7fb434413fafcc82107109d87-1920x1276.jpg"
|
||||
intro: "Celebrating one year of freesewing.org: Announcing the freesewing library"
|
||||
title: "Celebrating one year of freesewing.org: Announcing the freesewing library"
|
||||
---
|
||||
|
||||
|
||||
Exactly one year ago, the doors of freesewing.org swung open for our users,
|
||||
while those of makemypattern.com get one of those *we've moved* signs.
|
||||
|
||||
Looking back at [that blog post from 12 months ago](/blog/open-for-business),
|
||||
it almost beggars belief that the things announced then are only one year old.
|
||||
The concept of a draft, the comparison functionality, or even paperless patterns.
|
||||
They all celebrate their first birthday today.
|
||||
|
||||
Not this site though, because [driven by the looming GDPR deadline](/blog/gdpr-plan), we dumped our Jekyll based site for a new front end sometime in May.
|
||||
|
||||
## More languages with less languages
|
||||
|
||||
GDPR was only part of that story.
|
||||
Other reasons for the rewrite were our desire to support multiple languages,
|
||||
and to simplify our technology stack.
|
||||
|
||||
In other words, we wanted to reach people who speak different languages,
|
||||
and wanted to limit the number of programming languages required to do so.
|
||||
|
||||
### More natural languages
|
||||
|
||||
We've done remarkably well on this front.
|
||||
While you won't find every last bit of content translated, this website's main features
|
||||
are now available in five languages:
|
||||
|
||||
- English
|
||||
- German
|
||||
- Spanish
|
||||
- French
|
||||
- Dutch
|
||||
|
||||
Which really is 100% thanks to the great work of [our wonderful translators](/i18n/).
|
||||
|
||||
### Less programming languages
|
||||
|
||||
The switch from [Jekyll]() to a [Nuxt](https://nuxtjs.org/)-based front-end
|
||||
has removed [Ruby](https://www.ruby-lang.org/) from our technology stack.
|
||||
Freesewing.org now runs on JavaScript, PHP and a little bit of C (which we'll ignore for now).
|
||||
|
||||
But removing programming languages is not a goal *an sich*.
|
||||
Rather, the underlying ambition is to simplify things, make it easier for people to get
|
||||
involved, and ultimately attract more contributors so that the project can grow and flourish.
|
||||
|
||||
Today, designing/developing patterns is not an insurmountable obstacle.
|
||||
We've got [benjamin](/patterns/benjamin), [florent](/patterns/florent),
|
||||
and [sandy](/patterns/sandy) to show for it.
|
||||
All of these were contributed by people for whom freesewing was initially new,
|
||||
they went through the design tutorial, and in the end created a pattern of their own.
|
||||
|
||||
We'd like more people to follow in their footsteps. So making the process as simple as
|
||||
possible is a worthy investment of our time.
|
||||
|
||||
## Announcing freesewing, the library
|
||||
|
||||
For the past 2 months, I have taken time off from pattern making and sewing to
|
||||
tackle our [technical debt](https://en.wikipedia.org/wiki/Technical_debt).
|
||||
|
||||
Specifically, I've set out to rewrite our core back-end from the ground up in JavaScript.
|
||||
But there's a twist. It's no longer a back-end. It's a library you can use
|
||||
both in your browser, or on the server with [node.js](https://nodejs.org/).
|
||||
|
||||
It is currently in version 0.10, and feature complete with freesewing core.
|
||||
It's [available on GitHub](https://github.com/freesewing/freesewing) and
|
||||
[NPM](https://www.npmjs.com/package/freesewing), and is fully documented at
|
||||
[developer.freesewing.org](https://developer.freesewing.org/).
|
||||
|
||||
And while its API is richer than core's, it's footprint is actually a lot smaller:
|
||||
|
||||
|
||||
|
||||
Which is good news, in case you were wondering.
|
||||
|
||||
## What happens next?
|
||||
|
||||
A lot of work needs to be done before we can actually use this on freesewing.org:
|
||||
|
||||
|
||||
- All our existing patterns need to be parted to the JS version. [Brian](https://github.com/freesewing/brian) is the first pattern to have been ported.
|
||||
- Rewrite our data back-end in JS. Since this will remove the PHP programming language from our stack.
|
||||
- Build a new website using the freesewing library and our new data back-end.
|
||||
|
||||
This really is a lot of work, and while I hope that by the end of the year we'll have made
|
||||
good progress, I can't promise it will be done.
|
||||
|
||||
## But I just want patterns
|
||||
|
||||
Chances are, all you care about is patterns.
|
||||
What you want is more patterns, better patterns, different patterns.
|
||||
And all of this rewriting is not exactly pushing your buttons.
|
||||
|
||||
I get that. I really do. I for one have a list of patterns I'd like to see added to the site.
|
||||
And my work on other aspects of the project keeps me from adding them.
|
||||
|
||||
But I believe that investing now in a streamlined developer experience will have a knock-on effect in the long term.
|
||||
|
||||
If we want a few extra patterns, this is not the right approach. But if we want a lot more patterns, I believe it is.
|
||||
|
||||
And I want a lot more patterns.
|
||||
|
||||
109
markdown/org/blog/announcing-freesewing-library/es.md
Normal file
109
markdown/org/blog/announcing-freesewing-library/es.md
Normal file
|
|
@ -0,0 +1,109 @@
|
|||
---
|
||||
author: "joostdecock"
|
||||
caption: "I don't drink, but this seemed appropriate for a celebration post ¯\\_(ツ)_/¯"
|
||||
date: "2018-08-25"
|
||||
image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a6b5a3918ad412f7fb434413fafcc82107109d87-1920x1276.jpg"
|
||||
intro: "Celebrating one year of freesewing.org: Announcing the freesewing library [No traducido]"
|
||||
title: "Celebrating one year of freesewing.org: Announcing the freesewing library [No traducido]"
|
||||
---
|
||||
|
||||
|
||||
Exactly one year ago, the doors of freesewing.org swung open for our users,
|
||||
while those of makemypattern.com get one of those *we've moved* signs.
|
||||
|
||||
Looking back at [that blog post from 12 months ago](/blog/open-for-business),
|
||||
it almost beggars belief that the things announced then are only one year old.
|
||||
The concept of a draft, the comparison functionality, or even paperless patterns.
|
||||
They all celebrate their first birthday today.
|
||||
|
||||
Not this site though, because [driven by the looming GDPR deadline](/blog/gdpr-plan), we dumped our Jekyll based site for a new front end sometime in May.
|
||||
|
||||
## More languages with less languages
|
||||
|
||||
GDPR was only part of that story.
|
||||
Other reasons for the rewrite were our desire to support multiple languages,
|
||||
and to simplify our technology stack.
|
||||
|
||||
In other words, we wanted to reach people who speak different languages,
|
||||
and wanted to limit the number of programming languages required to do so.
|
||||
|
||||
### More natural languages
|
||||
|
||||
We've done remarkably well on this front.
|
||||
While you won't find every last bit of content translated, this website's main features
|
||||
are now available in five languages:
|
||||
|
||||
- English
|
||||
- German
|
||||
- Spanish
|
||||
- French
|
||||
- Dutch
|
||||
|
||||
Which really is 100% thanks to the great work of [our wonderful translators](/i18n/).
|
||||
|
||||
### Less programming languages
|
||||
|
||||
The switch from [Jekyll]() to a [Nuxt](https://nuxtjs.org/)-based front-end
|
||||
has removed [Ruby](https://www.ruby-lang.org/) from our technology stack.
|
||||
Freesewing.org now runs on JavaScript, PHP and a little bit of C (which we'll ignore for now).
|
||||
|
||||
But removing programming languages is not a goal *an sich*.
|
||||
Rather, the underlying ambition is to simplify things, make it easier for people to get
|
||||
involved, and ultimately attract more contributors so that the project can grow and flourish.
|
||||
|
||||
Today, designing/developing patterns is not an insurmountable obstacle.
|
||||
We've got [benjamin](/patterns/benjamin), [florent](/patterns/florent),
|
||||
and [sandy](/patterns/sandy) to show for it.
|
||||
All of these were contributed by people for whom freesewing was initially new,
|
||||
they went through the design tutorial, and in the end created a pattern of their own.
|
||||
|
||||
We'd like more people to follow in their footsteps. So making the process as simple as
|
||||
possible is a worthy investment of our time.
|
||||
|
||||
## Announcing freesewing, the library
|
||||
|
||||
For the past 2 months, I have taken time off from pattern making and sewing to
|
||||
tackle our [technical debt](https://en.wikipedia.org/wiki/Technical_debt).
|
||||
|
||||
Specifically, I've set out to rewrite our core back-end from the ground up in JavaScript.
|
||||
But there's a twist. It's no longer a back-end. It's a library you can use
|
||||
both in your browser, or on the server with [node.js](https://nodejs.org/).
|
||||
|
||||
It is currently in version 0.10, and feature complete with freesewing core.
|
||||
It's [available on GitHub](https://github.com/freesewing/freesewing) and
|
||||
[NPM](https://www.npmjs.com/package/freesewing), and is fully documented at
|
||||
[developer.freesewing.org](https://developer.freesewing.org/).
|
||||
|
||||
And while its API is richer than core's, it's footprint is actually a lot smaller:
|
||||
|
||||
|
||||
|
||||
Which is good news, in case you were wondering.
|
||||
|
||||
## What happens next?
|
||||
|
||||
A lot of work needs to be done before we can actually use this on freesewing.org:
|
||||
|
||||
|
||||
- All our existing patterns need to be parted to the JS version. [Brian](https://github.com/freesewing/brian) is the first pattern to have been ported.
|
||||
- Rewrite our data back-end in JS. Since this will remove the PHP programming language from our stack.
|
||||
- Build a new website using the freesewing library and our new data back-end.
|
||||
|
||||
This really is a lot of work, and while I hope that by the end of the year we'll have made
|
||||
good progress, I can't promise it will be done.
|
||||
|
||||
## But I just want patterns
|
||||
|
||||
Chances are, all you care about is patterns.
|
||||
What you want is more patterns, better patterns, different patterns.
|
||||
And all of this rewriting is not exactly pushing your buttons.
|
||||
|
||||
I get that. I really do. I for one have a list of patterns I'd like to see added to the site.
|
||||
And my work on other aspects of the project keeps me from adding them.
|
||||
|
||||
But I believe that investing now in a streamlined developer experience will have a knock-on effect in the long term.
|
||||
|
||||
If we want a few extra patterns, this is not the right approach. But if we want a lot more patterns, I believe it is.
|
||||
|
||||
And I want a lot more patterns.
|
||||
|
||||
109
markdown/org/blog/announcing-freesewing-library/fr.md
Normal file
109
markdown/org/blog/announcing-freesewing-library/fr.md
Normal file
|
|
@ -0,0 +1,109 @@
|
|||
---
|
||||
author: "joostdecock"
|
||||
caption: "I don't drink, but this seemed appropriate for a celebration post ¯\\_(ツ)_/¯"
|
||||
date: "2018-08-25"
|
||||
image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a6b5a3918ad412f7fb434413fafcc82107109d87-1920x1276.jpg"
|
||||
intro: "Celebrating one year of freesewing.org: Announcing the freesewing library [Non traduit]"
|
||||
title: "Celebrating one year of freesewing.org: Announcing the freesewing library [Non traduit]"
|
||||
---
|
||||
|
||||
|
||||
Exactly one year ago, the doors of freesewing.org swung open for our users,
|
||||
while those of makemypattern.com get one of those *we've moved* signs.
|
||||
|
||||
Looking back at [that blog post from 12 months ago](/blog/open-for-business),
|
||||
it almost beggars belief that the things announced then are only one year old.
|
||||
The concept of a draft, the comparison functionality, or even paperless patterns.
|
||||
They all celebrate their first birthday today.
|
||||
|
||||
Not this site though, because [driven by the looming GDPR deadline](/blog/gdpr-plan), we dumped our Jekyll based site for a new front end sometime in May.
|
||||
|
||||
## More languages with less languages
|
||||
|
||||
GDPR was only part of that story.
|
||||
Other reasons for the rewrite were our desire to support multiple languages,
|
||||
and to simplify our technology stack.
|
||||
|
||||
In other words, we wanted to reach people who speak different languages,
|
||||
and wanted to limit the number of programming languages required to do so.
|
||||
|
||||
### More natural languages
|
||||
|
||||
We've done remarkably well on this front.
|
||||
While you won't find every last bit of content translated, this website's main features
|
||||
are now available in five languages:
|
||||
|
||||
- English
|
||||
- German
|
||||
- Spanish
|
||||
- French
|
||||
- Dutch
|
||||
|
||||
Which really is 100% thanks to the great work of [our wonderful translators](/i18n/).
|
||||
|
||||
### Less programming languages
|
||||
|
||||
The switch from [Jekyll]() to a [Nuxt](https://nuxtjs.org/)-based front-end
|
||||
has removed [Ruby](https://www.ruby-lang.org/) from our technology stack.
|
||||
Freesewing.org now runs on JavaScript, PHP and a little bit of C (which we'll ignore for now).
|
||||
|
||||
But removing programming languages is not a goal *an sich*.
|
||||
Rather, the underlying ambition is to simplify things, make it easier for people to get
|
||||
involved, and ultimately attract more contributors so that the project can grow and flourish.
|
||||
|
||||
Today, designing/developing patterns is not an insurmountable obstacle.
|
||||
We've got [benjamin](/patterns/benjamin), [florent](/patterns/florent),
|
||||
and [sandy](/patterns/sandy) to show for it.
|
||||
All of these were contributed by people for whom freesewing was initially new,
|
||||
they went through the design tutorial, and in the end created a pattern of their own.
|
||||
|
||||
We'd like more people to follow in their footsteps. So making the process as simple as
|
||||
possible is a worthy investment of our time.
|
||||
|
||||
## Announcing freesewing, the library
|
||||
|
||||
For the past 2 months, I have taken time off from pattern making and sewing to
|
||||
tackle our [technical debt](https://en.wikipedia.org/wiki/Technical_debt).
|
||||
|
||||
Specifically, I've set out to rewrite our core back-end from the ground up in JavaScript.
|
||||
But there's a twist. It's no longer a back-end. It's a library you can use
|
||||
both in your browser, or on the server with [node.js](https://nodejs.org/).
|
||||
|
||||
It is currently in version 0.10, and feature complete with freesewing core.
|
||||
It's [available on GitHub](https://github.com/freesewing/freesewing) and
|
||||
[NPM](https://www.npmjs.com/package/freesewing), and is fully documented at
|
||||
[developer.freesewing.org](https://developer.freesewing.org/).
|
||||
|
||||
And while its API is richer than core's, it's footprint is actually a lot smaller:
|
||||
|
||||
|
||||
|
||||
Which is good news, in case you were wondering.
|
||||
|
||||
## What happens next?
|
||||
|
||||
A lot of work needs to be done before we can actually use this on freesewing.org:
|
||||
|
||||
|
||||
- All our existing patterns need to be parted to the JS version. [Brian](https://github.com/freesewing/brian) is the first pattern to have been ported.
|
||||
- Rewrite our data back-end in JS. Since this will remove the PHP programming language from our stack.
|
||||
- Build a new website using the freesewing library and our new data back-end.
|
||||
|
||||
This really is a lot of work, and while I hope that by the end of the year we'll have made
|
||||
good progress, I can't promise it will be done.
|
||||
|
||||
## But I just want patterns
|
||||
|
||||
Chances are, all you care about is patterns.
|
||||
What you want is more patterns, better patterns, different patterns.
|
||||
And all of this rewriting is not exactly pushing your buttons.
|
||||
|
||||
I get that. I really do. I for one have a list of patterns I'd like to see added to the site.
|
||||
And my work on other aspects of the project keeps me from adding them.
|
||||
|
||||
But I believe that investing now in a streamlined developer experience will have a knock-on effect in the long term.
|
||||
|
||||
If we want a few extra patterns, this is not the right approach. But if we want a lot more patterns, I believe it is.
|
||||
|
||||
And I want a lot more patterns.
|
||||
|
||||
82
markdown/org/blog/announcing-freesewing-library/nl.md
Normal file
82
markdown/org/blog/announcing-freesewing-library/nl.md
Normal file
|
|
@ -0,0 +1,82 @@
|
|||
---
|
||||
author: "joostdecock"
|
||||
caption: "Ik drink niet, maar dit leek me gepast voor een feestpost ¯\\_(ツ)_/¯"
|
||||
date: "2018-08-25"
|
||||
image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a6b5a3918ad412f7fb434413fafcc82107109d87-1920x1276.jpg"
|
||||
intro: "Precies een jaar geleden zwaaiden de deuren van FreeSewing.org open voor onze gebruikers. Op die van MakeMyPattern.com plakten we van die -bordjes."
|
||||
title: "Het eerste verjaardagsfeestje van FreeSewing.org, en de nieuwe FreeSewing-bibliotheek"
|
||||
---
|
||||
|
||||
|
||||
Precies een jaar geleden zwaaiden de deuren van FreeSewing.org open voor onze gebruikers. Op die van MakeMyPattern.com plakten we van die *We zijn verhuisd*-bordjes.
|
||||
|
||||
Als ik terugkijk naar [die blogpost van 12 maanden geleden](/blog/open-for-business), kan ik bijna niet geloven dat de dingen die ik toen aankondigde, nu nog maar een jaar oud zijn. Het concept van een schets, de vergelijkingsfunctie, papierloze patronen zelfs ... Ze vieren vandaag allemaal hun eerste verjaardag.
|
||||
|
||||
Maar deze site niet. Want [omwille van de naderende GDPR-deadline](/blog/gdpr-plan) hebben we onze Jekyll-site gedumpt voor een nieuwe front-end in de loop van mei.
|
||||
|
||||
## Meer talen met minder talen
|
||||
|
||||
GDPR was maar een deel van dat verhaal. Er waren meer redenen voor die rewrite: we wilden meerdere talen kunnen ondersteunen en onze technology stack vereenvoudigen.
|
||||
|
||||
Met andere woorden, we wilden mensen bereiken die verschillende talen spreken, en we wilden het aantal programmeertalen dat we daarvoor nodig hadden, beperken.
|
||||
|
||||
### Meer natuurlijke talen
|
||||
|
||||
Op dit vlak hebben we het echt goed gedaan. Je vindt hier niet elk morzeltje content in alle verschillende talen. Maar de belangrijkste functies van de website zijn nu wel beschikbaar in vijf talen:
|
||||
|
||||
- Engels
|
||||
- Duits
|
||||
- Spaans
|
||||
- Frans
|
||||
- Nederlands
|
||||
|
||||
En dat hebben we echt voor 100% te danken aan het sterke werk van [onze geweldige vertalers](/i18n/).
|
||||
|
||||
### Minder programmeertalen
|
||||
|
||||
De overstap van [Jekyll](https://jekyllrb.com/) naar een op [Nuxt](https://nuxtjs.org/) gebaseerde fonrt-end heeft [Ruby](https://www.ruby-lang.org/) uit onze technology stack geschrapt. FreeSewing.org loopt nu op JavaScript, PHP en een klein beetje C. Dat laatste negeren we voorlopig.
|
||||
|
||||
Maar programmeertalen verwijderen is geen doel op zich. De onderliggende ambitie is om dingen te vereenvoudigen en het zo gemakkelijker te maken voor anderen om betrokken te raken. Uiteindelijk willen we meer bijdragers aantrekken zodat het project kan groeien en bloeien.
|
||||
|
||||
Patronen ontwerpen en developen is vandaag geen onoverkomelijk obstakel. We hebben [Benjamin](/patterns/benjamin), [Florent](/patterns/florent) en [Sandy](/patterns/sandy) om dat te bewijzen. Die zijn allemaal bijgedragen door mensen voor wie FreeSewing in eerste instantie nieuw was. Ze hebben de ontwerptutorial gevolgd en uiteindelijk hun eigen patroon gemaakt.
|
||||
|
||||
We zouden graag meer mensen in hun voetstappen zien volgen. Dus was het een goede investering van onze tijd om het proces zo eenvoudig mogelijk te maken.
|
||||
|
||||
## De FreeSewing-bibliotheek
|
||||
|
||||
De afgelopen twee maanden heb ik het patroontekenen even op pauze gezet om onze [technische schuld](https://en.wikipedia.org/wiki/Technical_debt) aan te pakken.
|
||||
|
||||
Meer specifiek ben ik begonnen met de back-end in core van nul af aan te herschrijven in JavaScript. Maar hier komt de plotwending. Het is geen back-end meer. Het is voortaan een bibliotheek die je kan gebruiken in je browser of op de server met [node.js](https://nodejs.org/).
|
||||
|
||||
Dit zit momenteel in versie 0.10 en heeft alle functies van FreeSewing core. Je kan de bibliotheek vinden op [GitHub](https://github.com/freesewing/freesewing) en [NPM](https://www.npmjs.com/package/freesewing). Hij is volledig gedocumenteerd op [developer.freesewing.org](https://developer.freesewing.org/).
|
||||
|
||||
De API is rijker dan die van core. En toch heeft het een veel kleinere voetafdruk:
|
||||
|
||||
|
||||
|
||||
Als je nog niet zeker was: dat is goed nieuws.
|
||||
|
||||
## Wat gebeurt er nu?
|
||||
|
||||
We hebben nog veel werk voordat we dit ook echt kunnen gebruiken op FreeSewing.org:
|
||||
|
||||
|
||||
- Al onze bestaande patronen moeten geëxporteerd worden naar de JS-versie. [Brian](https://github.com/freesewing/brian) was het eerste patroon waarmee we dat al gedaan hebben.
|
||||
- Dat gaat de PHP-programmeertaal uit onze stack verwijderen. Dus moeten we de data in onze back-end herschrijven in JS.
|
||||
- We moeten een nieuwe website bouwen aan de hand van de FreeSewing-bibliotheek en onze data back-end.
|
||||
|
||||
Dat is echt veel werk. Ik hoop dat we al een heel eind verder staan aan het einde van dit jaar, maar ik durf niet te beloven dat het helemaal klaar zal zijn.
|
||||
|
||||
## Maar ik wil gewoon patronen
|
||||
|
||||
De kans is groot dat je eigenlijk alleen om de patronen geeft. Je wil meer patronen, betere patronen, andere patronen. En al dit gedoe over herschrijven doet het niet echt voor jou.
|
||||
|
||||
Ik snap het. Echt. Ik heb zelf een hele lijst van patronen die ik graag op onze website zou hebben. En terwijl ik met andere aspecten van het project bezig ben, heb ik geen tijd om die patronen toe te voegen.
|
||||
|
||||
Maar ik geloof dat als we nu investeren in een gestroomlijnde development-ervaring, we daar op de lange termijn de vruchten van gaan plukken.
|
||||
|
||||
Als we een paar extra patronen willen, dan is dit niet de juiste aanpak. Maar als we véél meer patronen willen, dan is het dat volgens mij wel.
|
||||
|
||||
En ik wil veel meer patronen.
|
||||
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue