From 052a85e1a4e5b7c9810fdac817d6a150f7ed903a Mon Sep 17 00:00:00 2001 From: joostdecock Date: Sat, 15 Jul 2023 19:53:03 +0200 Subject: [PATCH] feat: Added local markdonw content after importing from strapi/sanity --- markdown/org/blog/2-20-for-dolls/de.md | 25 ++ markdown/org/blog/2-20-for-dolls/en.md | 25 ++ markdown/org/blog/2-20-for-dolls/es.md | 25 ++ markdown/org/blog/2-20-for-dolls/fr.md | 25 ++ markdown/org/blog/2-20-for-dolls/nl.md | 25 ++ markdown/org/blog/2019-yearly-report/de.md | 51 +++ markdown/org/blog/2019-yearly-report/en.md | 91 ++++ markdown/org/blog/2019-yearly-report/es.md | 91 ++++ markdown/org/blog/2019-yearly-report/fr.md | 51 +++ markdown/org/blog/2019-yearly-report/nl.md | 51 +++ markdown/org/blog/2021-wrapup/de.md | 51 +++ markdown/org/blog/2021-wrapup/en.md | 51 +++ markdown/org/blog/2021-wrapup/es.md | 51 +++ markdown/org/blog/2021-wrapup/fr.md | 51 +++ markdown/org/blog/2021-wrapup/nl.md | 51 +++ markdown/org/blog/a-call-for-help/de.md | 167 +++++++ markdown/org/blog/a-call-for-help/en.md | 194 ++++++++ markdown/org/blog/a-call-for-help/es.md | 194 ++++++++ markdown/org/blog/a-call-for-help/fr.md | 167 +++++++ markdown/org/blog/a-call-for-help/nl.md | 167 +++++++ markdown/org/blog/albert-apron/de.md | 23 + markdown/org/blog/albert-apron/en.md | 23 + markdown/org/blog/albert-apron/es.md | 23 + markdown/org/blog/albert-apron/fr.md | 23 + markdown/org/blog/albert-apron/nl.md | 23 + markdown/org/blog/all-contributors/de.md | 35 ++ markdown/org/blog/all-contributors/en.md | 35 ++ markdown/org/blog/all-contributors/es.md | 35 ++ markdown/org/blog/all-contributors/fr.md | 35 ++ markdown/org/blog/all-contributors/nl.md | 35 ++ markdown/org/blog/annnouncing-yuri/de.md | 14 + markdown/org/blog/annnouncing-yuri/en.md | 14 + markdown/org/blog/annnouncing-yuri/es.md | 14 + markdown/org/blog/annnouncing-yuri/fr.md | 14 + markdown/org/blog/annnouncing-yuri/nl.md | 14 + markdown/org/blog/announcing-carlita/de.md | 88 ++++ markdown/org/blog/announcing-carlita/en.md | 88 ++++ markdown/org/blog/announcing-carlita/es.md | 88 ++++ markdown/org/blog/announcing-carlita/fr.md | 76 ++++ markdown/org/blog/announcing-carlita/nl.md | 76 ++++ .../blog/announcing-carlton-and-bent/de.md | 86 ++++ .../blog/announcing-carlton-and-bent/en.md | 86 ++++ .../blog/announcing-carlton-and-bent/es.md | 86 ++++ .../blog/announcing-carlton-and-bent/fr.md | 60 +++ .../blog/announcing-carlton-and-bent/nl.md | 60 +++ markdown/org/blog/announcing-charlie/de.md | 63 +++ markdown/org/blog/announcing-charlie/en.md | 88 ++++ markdown/org/blog/announcing-charlie/es.md | 88 ++++ markdown/org/blog/announcing-charlie/fr.md | 88 ++++ markdown/org/blog/announcing-charlie/nl.md | 88 ++++ .../blog/announcing-freesewing-library/de.md | 82 ++++ .../blog/announcing-freesewing-library/en.md | 109 +++++ .../blog/announcing-freesewing-library/es.md | 109 +++++ .../blog/announcing-freesewing-library/fr.md | 109 +++++ .../blog/announcing-freesewing-library/nl.md | 82 ++++ markdown/org/blog/announcing-freesewing/de.md | 51 +++ markdown/org/blog/announcing-freesewing/en.md | 70 +++ markdown/org/blog/announcing-freesewing/es.md | 70 +++ markdown/org/blog/announcing-freesewing/fr.md | 51 +++ markdown/org/blog/announcing-freesewing/nl.md | 51 +++ markdown/org/blog/announcing-hortensia/de.md | 31 ++ markdown/org/blog/announcing-hortensia/en.md | 34 ++ markdown/org/blog/announcing-hortensia/es.md | 34 ++ markdown/org/blog/announcing-hortensia/fr.md | 31 ++ markdown/org/blog/announcing-hortensia/nl.md | 34 ++ markdown/org/blog/announcing-penelope/de.md | 33 ++ markdown/org/blog/announcing-penelope/en.md | 46 ++ markdown/org/blog/announcing-penelope/es.md | 46 ++ markdown/org/blog/announcing-penelope/fr.md | 46 ++ markdown/org/blog/announcing-penelope/nl.md | 33 ++ markdown/org/blog/announcing-sandy/de.md | 23 + markdown/org/blog/announcing-sandy/en.md | 22 + markdown/org/blog/announcing-sandy/es.md | 22 + markdown/org/blog/announcing-sandy/fr.md | 22 + markdown/org/blog/announcing-sandy/nl.md | 23 + markdown/org/blog/announcing-shin/de.md | 31 ++ markdown/org/blog/announcing-shin/en.md | 36 ++ markdown/org/blog/announcing-shin/es.md | 36 ++ markdown/org/blog/announcing-shin/fr.md | 36 ++ markdown/org/blog/announcing-shin/nl.md | 31 ++ markdown/org/blog/announcing-sven/de.md | 21 + markdown/org/blog/announcing-sven/en.md | 19 + markdown/org/blog/announcing-sven/es.md | 19 + markdown/org/blog/announcing-sven/fr.md | 19 + markdown/org/blog/announcing-sven/nl.md | 21 + markdown/org/blog/announcing-teagan/de.md | 47 ++ markdown/org/blog/announcing-teagan/en.md | 46 ++ markdown/org/blog/announcing-teagan/es.md | 47 ++ markdown/org/blog/announcing-teagan/fr.md | 47 ++ markdown/org/blog/announcing-teagan/nl.md | 36 ++ markdown/org/blog/announcing-ursula/de.md | 23 + markdown/org/blog/announcing-ursula/en.md | 23 + markdown/org/blog/announcing-ursula/es.md | 23 + markdown/org/blog/announcing-ursula/fr.md | 23 + markdown/org/blog/announcing-ursula/nl.md | 23 + markdown/org/blog/announcing-v2/de.md | 53 +++ markdown/org/blog/announcing-v2/en.md | 58 +++ markdown/org/blog/announcing-v2/es.md | 58 +++ markdown/org/blog/announcing-v2/fr.md | 53 +++ markdown/org/blog/announcing-v2/nl.md | 53 +++ markdown/org/blog/bella-bodice-block/de.md | 39 ++ markdown/org/blog/bella-bodice-block/en.md | 39 ++ markdown/org/blog/bella-bodice-block/es.md | 39 ++ markdown/org/blog/bella-bodice-block/fr.md | 32 ++ markdown/org/blog/bella-bodice-block/nl.md | 32 ++ markdown/org/blog/benjamin-bow-tie-beta/de.md | 39 ++ markdown/org/blog/benjamin-bow-tie-beta/en.md | 48 ++ markdown/org/blog/benjamin-bow-tie-beta/es.md | 48 ++ markdown/org/blog/benjamin-bow-tie-beta/fr.md | 48 ++ markdown/org/blog/benjamin-bow-tie-beta/nl.md | 39 ++ .../breanna-measurements-sizes-in-2-2/de.md | 99 +++++ .../breanna-measurements-sizes-in-2-2/en.md | 151 +++++++ .../breanna-measurements-sizes-in-2-2/es.md | 151 +++++++ .../breanna-measurements-sizes-in-2-2/fr.md | 151 +++++++ .../breanna-measurements-sizes-in-2-2/nl.md | 99 +++++ markdown/org/blog/bye-2020/de.md | 55 +++ markdown/org/blog/bye-2020/en.md | 55 +++ markdown/org/blog/bye-2020/es.md | 55 +++ markdown/org/blog/bye-2020/fr.md | 50 +++ markdown/org/blog/bye-2020/nl.md | 55 +++ markdown/org/blog/calling-all-patrons/de.md | 128 ++++++ markdown/org/blog/calling-all-patrons/en.md | 161 +++++++ markdown/org/blog/calling-all-patrons/es.md | 161 +++++++ markdown/org/blog/calling-all-patrons/fr.md | 128 ++++++ markdown/org/blog/calling-all-patrons/nl.md | 128 ++++++ .../blog/core-1-8-jaeger-across-back/de.md | 64 +++ .../blog/core-1-8-jaeger-across-back/en.md | 68 +++ .../blog/core-1-8-jaeger-across-back/es.md | 68 +++ .../blog/core-1-8-jaeger-across-back/fr.md | 68 +++ .../blog/core-1-8-jaeger-across-back/nl.md | 64 +++ markdown/org/blog/core-v1-3-0-is-out/de.md | 104 +++++ markdown/org/blog/core-v1-3-0-is-out/en.md | 104 +++++ markdown/org/blog/core-v1-3-0-is-out/es.md | 104 +++++ markdown/org/blog/core-v1-3-0-is-out/fr.md | 104 +++++ markdown/org/blog/core-v1-3-0-is-out/nl.md | 104 +++++ .../org/blog/cornelius-cycling-breeches/de.md | 29 ++ .../org/blog/cornelius-cycling-breeches/en.md | 36 ++ .../org/blog/cornelius-cycling-breeches/es.md | 36 ++ .../org/blog/cornelius-cycling-breeches/fr.md | 29 ++ .../org/blog/cornelius-cycling-breeches/nl.md | 36 ++ markdown/org/blog/email-spam-problems/de.md | 117 +++++ markdown/org/blog/email-spam-problems/en.md | 138 ++++++ markdown/org/blog/email-spam-problems/es.md | 138 ++++++ markdown/org/blog/email-spam-problems/fr.md | 138 ++++++ markdown/org/blog/email-spam-problems/nl.md | 138 ++++++ markdown/org/blog/facemask-frenzy/de.md | 42 ++ markdown/org/blog/facemask-frenzy/en.md | 42 ++ markdown/org/blog/facemask-frenzy/es.md | 42 ++ markdown/org/blog/facemask-frenzy/fr.md | 42 ++ markdown/org/blog/facemask-frenzy/nl.md | 41 ++ markdown/org/blog/florence-face-mask/de.md | 28 ++ markdown/org/blog/florence-face-mask/en.md | 37 ++ markdown/org/blog/florence-face-mask/es.md | 37 ++ markdown/org/blog/florence-face-mask/fr.md | 28 ++ markdown/org/blog/florence-face-mask/nl.md | 37 ++ markdown/org/blog/florent-flat-cap-beta/de.md | 35 ++ markdown/org/blog/florent-flat-cap-beta/en.md | 47 ++ markdown/org/blog/florent-flat-cap-beta/es.md | 47 ++ markdown/org/blog/florent-flat-cap-beta/fr.md | 47 ++ markdown/org/blog/florent-flat-cap-beta/nl.md | 47 ++ markdown/org/blog/freesewing-2-19/de.md | 40 ++ markdown/org/blog/freesewing-2-19/en.md | 40 ++ markdown/org/blog/freesewing-2-19/es.md | 40 ++ markdown/org/blog/freesewing-2-19/fr.md | 40 ++ markdown/org/blog/freesewing-2-19/nl.md | 40 ++ markdown/org/blog/freesewing-2-21/en.md | 48 ++ .../org/blog/freesewing-goes-jamstack/de.md | 103 +++++ .../org/blog/freesewing-goes-jamstack/en.md | 106 +++++ .../org/blog/freesewing-goes-jamstack/es.md | 106 +++++ .../org/blog/freesewing-goes-jamstack/fr.md | 106 +++++ .../org/blog/freesewing-goes-jamstack/nl.md | 106 +++++ markdown/org/blog/freesewing-v2-1/de.md | 86 ++++ markdown/org/blog/freesewing-v2-1/en.md | 92 ++++ markdown/org/blog/freesewing-v2-1/es.md | 92 ++++ markdown/org/blog/freesewing-v2-1/fr.md | 87 ++++ markdown/org/blog/freesewing-v2-1/nl.md | 92 ++++ markdown/org/blog/freesewing-v2-7/de.md | 75 ++++ markdown/org/blog/freesewing-v2-7/en.md | 75 ++++ markdown/org/blog/freesewing-v2-7/es.md | 75 ++++ markdown/org/blog/freesewing-v2-7/fr.md | 76 ++++ markdown/org/blog/freesewing-v2-7/nl.md | 75 ++++ markdown/org/blog/gdpr-plan/de.md | 320 ++++++++++++++ markdown/org/blog/gdpr-plan/en.md | 367 +++++++++++++++ markdown/org/blog/gdpr-plan/es.md | 367 +++++++++++++++ markdown/org/blog/gdpr-plan/fr.md | 320 ++++++++++++++ markdown/org/blog/gdpr-plan/nl.md | 367 +++++++++++++++ markdown/org/blog/gdpr-ready/de.md | 111 +++++ markdown/org/blog/gdpr-ready/en.md | 111 +++++ markdown/org/blog/gdpr-ready/es.md | 111 +++++ markdown/org/blog/gdpr-ready/fr.md | 111 +++++ markdown/org/blog/gdpr-ready/nl.md | 111 +++++ .../org/blog/halloween-cosplays-2021/de.md | 147 +++++++ .../org/blog/halloween-cosplays-2021/en.md | 147 +++++++ .../org/blog/halloween-cosplays-2021/es.md | 147 +++++++ .../org/blog/halloween-cosplays-2021/fr.md | 147 +++++++ .../org/blog/halloween-cosplays-2021/nl.md | 147 +++++++ markdown/org/blog/halloween-ideas-2021/de.md | 66 +++ markdown/org/blog/halloween-ideas-2021/en.md | 66 +++ markdown/org/blog/halloween-ideas-2021/es.md | 66 +++ markdown/org/blog/halloween-ideas-2021/fr.md | 66 +++ markdown/org/blog/halloween-ideas-2021/nl.md | 66 +++ .../org/blog/holmes-deerstalker-hat/de.md | 27 ++ .../org/blog/holmes-deerstalker-hat/en.md | 27 ++ .../org/blog/holmes-deerstalker-hat/es.md | 27 ++ .../org/blog/holmes-deerstalker-hat/fr.md | 21 + .../org/blog/holmes-deerstalker-hat/nl.md | 27 ++ markdown/org/blog/huey-hoodie-beta/de.md | 46 ++ markdown/org/blog/huey-hoodie-beta/en.md | 52 +++ markdown/org/blog/huey-hoodie-beta/es.md | 52 +++ markdown/org/blog/huey-hoodie-beta/fr.md | 52 +++ markdown/org/blog/huey-hoodie-beta/nl.md | 52 +++ markdown/org/blog/lets-meet-up-in-2019/de.md | 61 +++ markdown/org/blog/lets-meet-up-in-2019/en.md | 109 +++++ markdown/org/blog/lets-meet-up-in-2019/es.md | 109 +++++ markdown/org/blog/lets-meet-up-in-2019/fr.md | 109 +++++ markdown/org/blog/lets-meet-up-in-2019/nl.md | 109 +++++ markdown/org/blog/meet-paco/de.md | 37 ++ markdown/org/blog/meet-paco/en.md | 37 ++ markdown/org/blog/meet-paco/es.md | 37 ++ markdown/org/blog/meet-paco/fr.md | 34 ++ markdown/org/blog/meet-paco/nl.md | 34 ++ markdown/org/blog/open-for-business/de.md | 210 +++++++++ markdown/org/blog/open-for-business/en.md | 210 +++++++++ markdown/org/blog/open-for-business/es.md | 210 +++++++++ markdown/org/blog/open-for-business/fr.md | 210 +++++++++ markdown/org/blog/open-for-business/nl.md | 210 +++++++++ markdown/org/blog/privacy-choices/de.md | 63 +++ markdown/org/blog/privacy-choices/en.md | 65 +++ markdown/org/blog/privacy-choices/es.md | 65 +++ markdown/org/blog/privacy-choices/fr.md | 65 +++ markdown/org/blog/privacy-choices/nl.md | 65 +++ markdown/org/blog/react-17/de.md | 97 ++++ markdown/org/blog/react-17/en.md | 98 +++++ markdown/org/blog/react-17/es.md | 98 +++++ markdown/org/blog/react-17/fr.md | 98 +++++ markdown/org/blog/react-17/nl.md | 98 +++++ markdown/org/blog/roundup-2017-09/de.md | 115 +++++ markdown/org/blog/roundup-2017-09/en.md | 115 +++++ markdown/org/blog/roundup-2017-09/es.md | 115 +++++ markdown/org/blog/roundup-2017-09/fr.md | 115 +++++ markdown/org/blog/roundup-2017-09/nl.md | 115 +++++ markdown/org/blog/roundup-2017-10/de.md | 96 ++++ markdown/org/blog/roundup-2017-10/en.md | 96 ++++ markdown/org/blog/roundup-2017-10/es.md | 96 ++++ markdown/org/blog/roundup-2017-10/fr.md | 96 ++++ markdown/org/blog/roundup-2017-10/nl.md | 96 ++++ markdown/org/blog/roundup-2017-11/de.md | 164 +++++++ markdown/org/blog/roundup-2017-11/en.md | 164 +++++++ markdown/org/blog/roundup-2017-11/es.md | 164 +++++++ markdown/org/blog/roundup-2017-11/fr.md | 164 +++++++ markdown/org/blog/roundup-2017-11/nl.md | 164 +++++++ markdown/org/blog/roundup-2017-12/de.md | 159 +++++++ markdown/org/blog/roundup-2017-12/en.md | 159 +++++++ markdown/org/blog/roundup-2017-12/es.md | 159 +++++++ markdown/org/blog/roundup-2017-12/fr.md | 159 +++++++ markdown/org/blog/roundup-2017-12/nl.md | 159 +++++++ markdown/org/blog/roundup-2018-01/de.md | 135 ++++++ markdown/org/blog/roundup-2018-01/en.md | 135 ++++++ markdown/org/blog/roundup-2018-01/es.md | 135 ++++++ markdown/org/blog/roundup-2018-01/fr.md | 135 ++++++ markdown/org/blog/roundup-2018-01/nl.md | 135 ++++++ markdown/org/blog/roundup-2018-02/de.md | 100 +++++ markdown/org/blog/roundup-2018-02/en.md | 100 +++++ markdown/org/blog/roundup-2018-02/es.md | 100 +++++ markdown/org/blog/roundup-2018-02/fr.md | 100 +++++ markdown/org/blog/roundup-2018-02/nl.md | 100 +++++ markdown/org/blog/roundup-2018-03/de.md | 82 ++++ markdown/org/blog/roundup-2018-03/en.md | 82 ++++ markdown/org/blog/roundup-2018-03/es.md | 82 ++++ markdown/org/blog/roundup-2018-03/fr.md | 82 ++++ markdown/org/blog/roundup-2018-03/nl.md | 82 ++++ markdown/org/blog/roundup-2018-04/de.md | 27 ++ markdown/org/blog/roundup-2018-04/en.md | 30 ++ markdown/org/blog/roundup-2018-04/es.md | 30 ++ markdown/org/blog/roundup-2018-04/fr.md | 30 ++ markdown/org/blog/roundup-2018-04/nl.md | 30 ++ markdown/org/blog/roundup-2018-05/de.md | 55 +++ markdown/org/blog/roundup-2018-05/en.md | 55 +++ markdown/org/blog/roundup-2018-05/es.md | 55 +++ markdown/org/blog/roundup-2018-05/fr.md | 55 +++ markdown/org/blog/roundup-2018-05/nl.md | 55 +++ markdown/org/blog/roundup-2018-06/de.md | 54 +++ markdown/org/blog/roundup-2018-06/en.md | 54 +++ markdown/org/blog/roundup-2018-06/es.md | 54 +++ markdown/org/blog/roundup-2018-06/fr.md | 54 +++ markdown/org/blog/roundup-2018-06/nl.md | 54 +++ markdown/org/blog/roundup-2018-07/de.md | 39 ++ markdown/org/blog/roundup-2018-07/en.md | 39 ++ markdown/org/blog/roundup-2018-07/es.md | 39 ++ markdown/org/blog/roundup-2018-07/fr.md | 39 ++ markdown/org/blog/roundup-2018-07/nl.md | 39 ++ markdown/org/blog/roundup-2018-09/de.md | 52 +++ markdown/org/blog/roundup-2018-09/en.md | 52 +++ markdown/org/blog/roundup-2018-09/es.md | 52 +++ markdown/org/blog/roundup-2018-09/fr.md | 52 +++ markdown/org/blog/roundup-2018-09/nl.md | 52 +++ markdown/org/blog/roundup-2018-10/de.md | 43 ++ markdown/org/blog/roundup-2018-10/en.md | 43 ++ markdown/org/blog/roundup-2018-10/es.md | 43 ++ markdown/org/blog/roundup-2018-10/fr.md | 43 ++ markdown/org/blog/roundup-2018-10/nl.md | 43 ++ markdown/org/blog/roundup-2018-11/de.md | 52 +++ markdown/org/blog/roundup-2018-11/en.md | 52 +++ markdown/org/blog/roundup-2018-11/es.md | 52 +++ markdown/org/blog/roundup-2018-11/fr.md | 52 +++ markdown/org/blog/roundup-2018-11/nl.md | 52 +++ markdown/org/blog/roundup-2019-01/de.md | 144 ++++++ markdown/org/blog/roundup-2019-01/en.md | 144 ++++++ markdown/org/blog/roundup-2019-01/es.md | 144 ++++++ markdown/org/blog/roundup-2019-01/fr.md | 144 ++++++ markdown/org/blog/roundup-2019-01/nl.md | 144 ++++++ markdown/org/blog/the-refashioners-2017/de.md | 158 +++++++ markdown/org/blog/the-refashioners-2017/en.md | 158 +++++++ markdown/org/blog/the-refashioners-2017/es.md | 158 +++++++ markdown/org/blog/the-refashioners-2017/fr.md | 158 +++++++ markdown/org/blog/the-refashioners-2017/nl.md | 158 +++++++ markdown/org/blog/v2-22-then-v3/en.md | 27 ++ markdown/org/newsletter/2021q2/en.md | 416 ++++++++++++++++++ markdown/org/newsletter/2021q3/en.md | 299 +++++++++++++ markdown/org/newsletter/2021q4/en.md | 154 +++++++ markdown/org/newsletter/2022q1/en.md | 187 ++++++++ markdown/org/newsletter/2022q2/en.md | 203 +++++++++ markdown/org/newsletter/2022q3/en.md | 242 ++++++++++ markdown/org/newsletter/2022q4/en.md | 194 ++++++++ markdown/org/newsletter/2023q1/en.md | 152 +++++++ markdown/org/newsletter/2023q2/en.md | 173 ++++++++ markdown/org/newsletter/2023q3/en.md | 279 ++++++++++++ markdown/org/showcase/aaron-by-joost/de.md | 12 + markdown/org/showcase/aaron-by-joost/en.md | 11 + markdown/org/showcase/aaron-by-joost/es.md | 11 + markdown/org/showcase/aaron-by-joost/fr.md | 12 + markdown/org/showcase/aaron-by-joost/nl.md | 12 + .../org/showcase/airline-blanket-sven/de.md | 12 + .../org/showcase/airline-blanket-sven/en.md | 14 + .../org/showcase/airline-blanket-sven/es.md | 14 + .../org/showcase/airline-blanket-sven/fr.md | 12 + .../org/showcase/airline-blanket-sven/nl.md | 12 + markdown/org/showcase/albert-by-wouter/de.md | 12 + markdown/org/showcase/albert-by-wouter/en.md | 13 + markdown/org/showcase/albert-by-wouter/es.md | 13 + markdown/org/showcase/albert-by-wouter/fr.md | 12 + markdown/org/showcase/albert-by-wouter/nl.md | 13 + markdown/org/showcase/anneke-huey-black/de.md | 21 + markdown/org/showcase/anneke-huey-black/en.md | 23 + markdown/org/showcase/anneke-huey-black/es.md | 23 + markdown/org/showcase/anneke-huey-black/fr.md | 22 + markdown/org/showcase/anneke-huey-black/nl.md | 20 + markdown/org/showcase/anneke-huey-grey/de.md | 12 + markdown/org/showcase/anneke-huey-grey/en.md | 11 + markdown/org/showcase/anneke-huey-grey/es.md | 11 + markdown/org/showcase/anneke-huey-grey/fr.md | 12 + markdown/org/showcase/anneke-huey-grey/nl.md | 12 + markdown/org/showcase/anneke-huey/de.md | 20 + markdown/org/showcase/anneke-huey/en.md | 18 + markdown/org/showcase/anneke-huey/es.md | 18 + markdown/org/showcase/anneke-huey/fr.md | 20 + markdown/org/showcase/anneke-huey/nl.md | 20 + markdown/org/showcase/bella-block/de.md | 18 + markdown/org/showcase/bella-block/en.md | 19 + markdown/org/showcase/bella-block/es.md | 19 + markdown/org/showcase/bella-block/fr.md | 18 + markdown/org/showcase/bella-block/nl.md | 18 + markdown/org/showcase/bella-by-karen/de.md | 18 + markdown/org/showcase/bella-by-karen/en.md | 18 + markdown/org/showcase/bella-by-karen/es.md | 18 + markdown/org/showcase/bella-by-karen/fr.md | 18 + markdown/org/showcase/bella-by-karen/nl.md | 18 + markdown/org/showcase/black-bruce/de.md | 22 + markdown/org/showcase/black-bruce/en.md | 29 ++ markdown/org/showcase/black-bruce/es.md | 29 ++ markdown/org/showcase/black-bruce/fr.md | 22 + markdown/org/showcase/black-bruce/nl.md | 22 + markdown/org/showcase/black-hugo/de.md | 12 + markdown/org/showcase/black-hugo/en.md | 12 + markdown/org/showcase/black-hugo/es.md | 12 + markdown/org/showcase/black-hugo/fr.md | 12 + markdown/org/showcase/black-hugo/nl.md | 12 + markdown/org/showcase/bleach-dyed-bruce/de.md | 24 + markdown/org/showcase/bleach-dyed-bruce/en.md | 25 ++ markdown/org/showcase/bleach-dyed-bruce/es.md | 25 ++ markdown/org/showcase/bleach-dyed-bruce/fr.md | 24 + markdown/org/showcase/bleach-dyed-bruce/nl.md | 24 + markdown/org/showcase/blue-simon/de.md | 22 + markdown/org/showcase/blue-simon/en.md | 22 + markdown/org/showcase/blue-simon/es.md | 22 + markdown/org/showcase/blue-simon/fr.md | 22 + markdown/org/showcase/blue-simon/nl.md | 22 + markdown/org/showcase/blue-theo/de.md | 11 + markdown/org/showcase/blue-theo/en.md | 10 + markdown/org/showcase/blue-theo/es.md | 10 + markdown/org/showcase/blue-theo/fr.md | 11 + markdown/org/showcase/blue-theo/nl.md | 11 + markdown/org/showcase/bound-wahid/de.md | 21 + markdown/org/showcase/bound-wahid/en.md | 23 + markdown/org/showcase/bound-wahid/es.md | 23 + markdown/org/showcase/bound-wahid/fr.md | 21 + markdown/org/showcase/bound-wahid/nl.md | 21 + markdown/org/showcase/brian-by-stefan-1/de.md | 14 + markdown/org/showcase/brian-by-stefan-1/en.md | 15 + markdown/org/showcase/brian-by-stefan-1/es.md | 15 + markdown/org/showcase/brian-by-stefan-1/fr.md | 14 + markdown/org/showcase/brian-by-stefan-1/nl.md | 14 + markdown/org/showcase/brian-by-stefan-2/de.md | 15 + markdown/org/showcase/brian-by-stefan-2/en.md | 15 + markdown/org/showcase/brian-by-stefan-2/es.md | 15 + markdown/org/showcase/brian-by-stefan-2/fr.md | 14 + markdown/org/showcase/brian-by-stefan-2/nl.md | 14 + markdown/org/showcase/brian-by-stefan-3/de.md | 15 + markdown/org/showcase/brian-by-stefan-3/en.md | 15 + markdown/org/showcase/brian-by-stefan-3/es.md | 15 + markdown/org/showcase/brian-by-stefan-3/fr.md | 14 + markdown/org/showcase/brian-by-stefan-3/nl.md | 14 + markdown/org/showcase/brian-by-stefan-4/de.md | 15 + markdown/org/showcase/brian-by-stefan-4/en.md | 15 + markdown/org/showcase/brian-by-stefan-4/es.md | 15 + markdown/org/showcase/brian-by-stefan-4/fr.md | 14 + markdown/org/showcase/brian-by-stefan-4/nl.md | 14 + markdown/org/showcase/bruce-on-doll/de.md | 12 + markdown/org/showcase/bruce-on-doll/en.md | 13 + markdown/org/showcase/bruce-on-doll/es.md | 13 + markdown/org/showcase/bruce-on-doll/fr.md | 12 + markdown/org/showcase/bruce-on-doll/nl.md | 12 + markdown/org/showcase/bruce-three-pack/de.md | 21 + markdown/org/showcase/bruce-three-pack/en.md | 21 + markdown/org/showcase/bruce-three-pack/es.md | 21 + markdown/org/showcase/bruce-three-pack/fr.md | 20 + markdown/org/showcase/bruce-three-pack/nl.md | 19 + markdown/org/showcase/bruces-by-paul/de.md | 10 + markdown/org/showcase/bruces-by-paul/en.md | 10 + markdown/org/showcase/bruces-by-paul/es.md | 10 + markdown/org/showcase/bruces-by-paul/fr.md | 10 + markdown/org/showcase/bruces-by-paul/nl.md | 10 + markdown/org/showcase/bulbasaur-huey/de.md | 25 ++ markdown/org/showcase/bulbasaur-huey/en.md | 25 ++ markdown/org/showcase/bulbasaur-huey/es.md | 25 ++ markdown/org/showcase/bulbasaur-huey/fr.md | 25 ++ markdown/org/showcase/bulbasaur-huey/nl.md | 25 ++ markdown/org/showcase/carlton-by-rudy/de.md | 24 + markdown/org/showcase/carlton-by-rudy/en.md | 24 + markdown/org/showcase/carlton-by-rudy/es.md | 24 + markdown/org/showcase/carlton-by-rudy/fr.md | 24 + markdown/org/showcase/carlton-by-rudy/nl.md | 24 + markdown/org/showcase/casual-pink-simon/de.md | 11 + markdown/org/showcase/casual-pink-simon/en.md | 10 + markdown/org/showcase/casual-pink-simon/es.md | 10 + markdown/org/showcase/casual-pink-simon/fr.md | 11 + markdown/org/showcase/casual-pink-simon/nl.md | 11 + markdown/org/showcase/charlie-by-bob/de.md | 18 + markdown/org/showcase/charlie-by-bob/en.md | 18 + markdown/org/showcase/charlie-by-bob/es.md | 18 + markdown/org/showcase/charlie-by-bob/fr.md | 18 + markdown/org/showcase/charlie-by-bob/nl.md | 18 + .../org/showcase/charlie-by-joost-2/de.md | 18 + .../org/showcase/charlie-by-joost-2/en.md | 18 + .../org/showcase/charlie-by-joost-2/es.md | 18 + .../org/showcase/charlie-by-joost-2/fr.md | 18 + .../org/showcase/charlie-by-joost-2/nl.md | 18 + markdown/org/showcase/charlie-by-joost/de.md | 18 + markdown/org/showcase/charlie-by-joost/en.md | 14 + markdown/org/showcase/charlie-by-joost/es.md | 14 + markdown/org/showcase/charlie-by-joost/fr.md | 18 + markdown/org/showcase/charlie-by-joost/nl.md | 14 + markdown/org/showcase/charlie-on-sorcha/de.md | 16 + markdown/org/showcase/charlie-on-sorcha/en.md | 16 + markdown/org/showcase/charlie-on-sorcha/es.md | 16 + markdown/org/showcase/charlie-on-sorcha/fr.md | 16 + markdown/org/showcase/charlie-on-sorcha/nl.md | 16 + markdown/org/showcase/claire-does-sven/de.md | 12 + markdown/org/showcase/claire-does-sven/en.md | 12 + markdown/org/showcase/claire-does-sven/es.md | 12 + markdown/org/showcase/claire-does-sven/fr.md | 12 + markdown/org/showcase/claire-does-sven/nl.md | 12 + markdown/org/showcase/corduroy-theo/de.md | 12 + markdown/org/showcase/corduroy-theo/en.md | 13 + markdown/org/showcase/corduroy-theo/es.md | 13 + markdown/org/showcase/corduroy-theo/fr.md | 12 + markdown/org/showcase/corduroy-theo/nl.md | 12 + .../org/showcase/cornelius-by-wouter/de.md | 22 + .../org/showcase/cornelius-by-wouter/en.md | 22 + .../org/showcase/cornelius-by-wouter/es.md | 22 + .../org/showcase/cornelius-by-wouter/fr.md | 22 + .../org/showcase/cornelius-by-wouter/nl.md | 22 + .../org/showcase/fantastic-four-hugo/de.md | 14 + .../org/showcase/fantastic-four-hugo/en.md | 15 + .../org/showcase/fantastic-four-hugo/es.md | 15 + .../org/showcase/fantastic-four-hugo/fr.md | 14 + .../org/showcase/fantastic-four-hugo/nl.md | 14 + markdown/org/showcase/fighter-hoodie/de.md | 26 ++ markdown/org/showcase/fighter-hoodie/en.md | 26 ++ markdown/org/showcase/fighter-hoodie/es.md | 26 ++ markdown/org/showcase/fighter-hoodie/fr.md | 26 ++ markdown/org/showcase/fighter-hoodie/nl.md | 26 ++ markdown/org/showcase/florence-jv/de.md | 12 + markdown/org/showcase/florence-jv/en.md | 12 + markdown/org/showcase/florence-jv/es.md | 12 + markdown/org/showcase/florence-jv/fr.md | 12 + markdown/org/showcase/florence-jv/nl.md | 12 + markdown/org/showcase/florence/de.md | 17 + markdown/org/showcase/florence/en.md | 18 + markdown/org/showcase/florence/es.md | 18 + markdown/org/showcase/florence/fr.md | 17 + markdown/org/showcase/florence/nl.md | 18 + markdown/org/showcase/florent-by-enno/de.md | 12 + markdown/org/showcase/florent-by-enno/en.md | 12 + markdown/org/showcase/florent-by-enno/es.md | 12 + markdown/org/showcase/florent-by-enno/fr.md | 12 + markdown/org/showcase/florent-by-enno/nl.md | 12 + .../org/showcase/florent-by-michele/de.md | 16 + .../org/showcase/florent-by-michele/en.md | 16 + .../org/showcase/florent-by-michele/es.md | 16 + .../org/showcase/florent-by-michele/fr.md | 17 + .../org/showcase/florent-by-michele/nl.md | 16 + markdown/org/showcase/florent-by-wim/de.md | 15 + markdown/org/showcase/florent-by-wim/en.md | 15 + markdown/org/showcase/florent-by-wim/es.md | 15 + markdown/org/showcase/florent-by-wim/fr.md | 15 + markdown/org/showcase/florent-by-wim/nl.md | 15 + markdown/org/showcase/florent-by-wouter/de.md | 16 + markdown/org/showcase/florent-by-wouter/en.md | 19 + markdown/org/showcase/florent-by-wouter/es.md | 19 + markdown/org/showcase/florent-by-wouter/fr.md | 16 + markdown/org/showcase/florent-by-wouter/nl.md | 16 + markdown/org/showcase/french-terry-sven/de.md | 14 + markdown/org/showcase/french-terry-sven/en.md | 15 + markdown/org/showcase/french-terry-sven/es.md | 15 + markdown/org/showcase/french-terry-sven/fr.md | 14 + markdown/org/showcase/french-terry-sven/nl.md | 14 + markdown/org/showcase/green-wahid/de.md | 12 + markdown/org/showcase/green-wahid/en.md | 13 + markdown/org/showcase/green-wahid/es.md | 13 + markdown/org/showcase/green-wahid/fr.md | 12 + markdown/org/showcase/green-wahid/nl.md | 12 + markdown/org/showcase/grey-sven/de.md | 14 + markdown/org/showcase/grey-sven/en.md | 15 + markdown/org/showcase/grey-sven/es.md | 15 + markdown/org/showcase/grey-sven/fr.md | 14 + markdown/org/showcase/grey-sven/nl.md | 14 + .../org/showcase/hortensia-by-wouter/de.md | 24 + .../org/showcase/hortensia-by-wouter/en.md | 24 + .../org/showcase/hortensia-by-wouter/es.md | 24 + .../org/showcase/hortensia-by-wouter/fr.md | 24 + .../org/showcase/hortensia-by-wouter/nl.md | 24 + markdown/org/showcase/huey-by-minty/de.md | 18 + markdown/org/showcase/huey-by-minty/en.md | 18 + markdown/org/showcase/huey-by-minty/es.md | 18 + markdown/org/showcase/huey-by-minty/fr.md | 18 + markdown/org/showcase/huey-by-minty/nl.md | 18 + markdown/org/showcase/huey-by-paul/de.md | 11 + markdown/org/showcase/huey-by-paul/en.md | 10 + markdown/org/showcase/huey-by-paul/es.md | 10 + markdown/org/showcase/huey-by-paul/fr.md | 11 + markdown/org/showcase/huey-by-paul/nl.md | 11 + markdown/org/showcase/hugo-by-karin/de.md | 12 + markdown/org/showcase/hugo-by-karin/en.md | 12 + markdown/org/showcase/hugo-by-karin/es.md | 12 + markdown/org/showcase/hugo-by-karin/fr.md | 12 + markdown/org/showcase/hugo-by-karin/nl.md | 12 + markdown/org/showcase/hugo-by-lainey/de.md | 12 + markdown/org/showcase/hugo-by-lainey/en.md | 12 + markdown/org/showcase/hugo-by-lainey/es.md | 12 + markdown/org/showcase/hugo-by-lainey/fr.md | 12 + markdown/org/showcase/hugo-by-lainey/nl.md | 12 + markdown/org/showcase/hugo-saul/de.md | 16 + markdown/org/showcase/hugo-saul/en.md | 15 + markdown/org/showcase/hugo-saul/es.md | 15 + markdown/org/showcase/hugo-saul/fr.md | 16 + markdown/org/showcase/hugo-saul/nl.md | 15 + markdown/org/showcase/husband-hugo/de.md | 18 + markdown/org/showcase/husband-hugo/en.md | 17 + markdown/org/showcase/husband-hugo/es.md | 17 + markdown/org/showcase/husband-hugo/fr.md | 18 + markdown/org/showcase/husband-hugo/nl.md | 18 + markdown/org/showcase/liberty-trayvon/de.md | 18 + markdown/org/showcase/liberty-trayvon/en.md | 19 + markdown/org/showcase/liberty-trayvon/es.md | 19 + markdown/org/showcase/liberty-trayvon/fr.md | 18 + markdown/org/showcase/liberty-trayvon/nl.md | 18 + .../org/showcase/linnen-jaeger-by-paul/de.md | 11 + .../org/showcase/linnen-jaeger-by-paul/en.md | 10 + .../org/showcase/linnen-jaeger-by-paul/es.md | 10 + .../org/showcase/linnen-jaeger-by-paul/fr.md | 11 + .../org/showcase/linnen-jaeger-by-paul/nl.md | 11 + markdown/org/showcase/linnen-theo/de.md | 11 + markdown/org/showcase/linnen-theo/en.md | 10 + markdown/org/showcase/linnen-theo/es.md | 10 + markdown/org/showcase/linnen-theo/fr.md | 11 + markdown/org/showcase/linnen-theo/nl.md | 10 + markdown/org/showcase/mark-wears-simon/de.md | 16 + markdown/org/showcase/mark-wears-simon/en.md | 18 + markdown/org/showcase/mark-wears-simon/es.md | 18 + markdown/org/showcase/mark-wears-simon/fr.md | 16 + markdown/org/showcase/mark-wears-simon/nl.md | 16 + markdown/org/showcase/matching-simon/de.md | 29 ++ markdown/org/showcase/matching-simon/en.md | 29 ++ markdown/org/showcase/matching-simon/es.md | 29 ++ markdown/org/showcase/matching-simon/fr.md | 29 ++ markdown/org/showcase/matching-simon/nl.md | 29 ++ .../org/showcase/more-wahid-by-adam/de.md | 19 + .../org/showcase/more-wahid-by-adam/en.md | 19 + .../org/showcase/more-wahid-by-adam/es.md | 19 + .../org/showcase/more-wahid-by-adam/fr.md | 19 + .../org/showcase/more-wahid-by-adam/nl.md | 19 + markdown/org/showcase/nani-hugo/de.md | 11 + markdown/org/showcase/nani-hugo/en.md | 10 + markdown/org/showcase/nani-hugo/es.md | 10 + markdown/org/showcase/nani-hugo/fr.md | 11 + markdown/org/showcase/nani-hugo/nl.md | 11 + markdown/org/showcase/nsfw-bruce/de.md | 11 + markdown/org/showcase/nsfw-bruce/en.md | 10 + markdown/org/showcase/nsfw-bruce/es.md | 10 + markdown/org/showcase/nsfw-bruce/fr.md | 11 + markdown/org/showcase/nsfw-bruce/nl.md | 11 + .../outfit-wahid-theo-florent-by-paul/de.md | 12 + .../outfit-wahid-theo-florent-by-paul/en.md | 12 + .../outfit-wahid-theo-florent-by-paul/fr.md | 12 + .../outfit-wahid-theo-florent-by-paul/nl.md | 12 + .../outfit-wahid-theo-simon-by-paul/de.md | 10 + .../outfit-wahid-theo-simon-by-paul/en.md | 10 + .../outfit-wahid-theo-simon-by-paul/es.md | 10 + .../outfit-wahid-theo-simon-by-paul/fr.md | 10 + markdown/org/showcase/paco-by-joost/de.md | 14 + markdown/org/showcase/paco-by-joost/en.md | 14 + markdown/org/showcase/paco-by-joost/es.md | 14 + markdown/org/showcase/paco-by-joost/fr.md | 14 + markdown/org/showcase/paco-by-joost/nl.md | 14 + markdown/org/showcase/paco-by-karen/de.md | 18 + markdown/org/showcase/paco-by-karen/en.md | 18 + markdown/org/showcase/paco-by-karen/es.md | 18 + markdown/org/showcase/paco-by-karen/fr.md | 18 + markdown/org/showcase/paco-by-karen/nl.md | 18 + markdown/org/showcase/pirate-bruce/de.md | 12 + markdown/org/showcase/pirate-bruce/en.md | 12 + markdown/org/showcase/pirate-bruce/es.md | 12 + markdown/org/showcase/pirate-bruce/fr.md | 12 + markdown/org/showcase/pirate-bruce/nl.md | 12 + markdown/org/showcase/purple-bruce/de.md | 12 + markdown/org/showcase/purple-bruce/en.md | 12 + markdown/org/showcase/purple-bruce/es.md | 12 + markdown/org/showcase/purple-bruce/fr.md | 12 + markdown/org/showcase/purple-bruce/nl.md | 12 + markdown/org/showcase/purple-huey/de.md | 14 + markdown/org/showcase/purple-huey/en.md | 15 + markdown/org/showcase/purple-huey/es.md | 15 + markdown/org/showcase/purple-huey/fr.md | 14 + markdown/org/showcase/purple-huey/nl.md | 14 + .../org/showcase/quilted-jersey-huey/de.md | 22 + .../org/showcase/quilted-jersey-huey/en.md | 22 + .../org/showcase/quilted-jersey-huey/es.md | 22 + .../org/showcase/quilted-jersey-huey/fr.md | 22 + .../org/showcase/quilted-jersey-huey/nl.md | 22 + markdown/org/showcase/red-button-simon/de.md | 12 + markdown/org/showcase/red-button-simon/en.md | 11 + markdown/org/showcase/red-button-simon/es.md | 11 + markdown/org/showcase/red-button-simon/fr.md | 12 + markdown/org/showcase/red-button-simon/nl.md | 12 + markdown/org/showcase/red-theo/de.md | 14 + markdown/org/showcase/red-theo/en.md | 14 + markdown/org/showcase/red-theo/es.md | 14 + markdown/org/showcase/red-theo/fr.md | 14 + markdown/org/showcase/red-theo/nl.md | 14 + markdown/org/showcase/ricos-huey/de.md | 12 + markdown/org/showcase/ricos-huey/en.md | 12 + markdown/org/showcase/ricos-huey/es.md | 12 + markdown/org/showcase/ricos-huey/fr.md | 12 + markdown/org/showcase/ricos-huey/nl.md | 12 + markdown/org/showcase/ricos-sven/de.md | 14 + markdown/org/showcase/ricos-sven/en.md | 14 + markdown/org/showcase/ricos-sven/es.md | 14 + markdown/org/showcase/ricos-sven/fr.md | 14 + markdown/org/showcase/ricos-sven/nl.md | 14 + markdown/org/showcase/sample-wahid/de.md | 11 + markdown/org/showcase/sample-wahid/en.md | 10 + markdown/org/showcase/sample-wahid/es.md | 10 + markdown/org/showcase/sample-wahid/fr.md | 11 + markdown/org/showcase/sample-wahid/nl.md | 11 + markdown/org/showcase/sandy-by-adam/de.md | 11 + markdown/org/showcase/sandy-by-adam/en.md | 10 + markdown/org/showcase/sandy-by-adam/es.md | 10 + markdown/org/showcase/sandy-by-adam/fr.md | 11 + markdown/org/showcase/sandy-by-adam/nl.md | 11 + markdown/org/showcase/sandy-by-anneke/de.md | 18 + markdown/org/showcase/sandy-by-anneke/en.md | 18 + markdown/org/showcase/sandy-by-anneke/es.md | 18 + markdown/org/showcase/sandy-by-anneke/fr.md | 18 + markdown/org/showcase/sandy-by-anneke/nl.md | 18 + markdown/org/showcase/sandy-by-jv/de.md | 18 + markdown/org/showcase/sandy-by-jv/en.md | 18 + markdown/org/showcase/sandy-by-jv/es.md | 18 + markdown/org/showcase/sandy-by-jv/fr.md | 18 + markdown/org/showcase/sandy-by-jv/nl.md | 18 + markdown/org/showcase/sandy-by-karin/de.md | 18 + markdown/org/showcase/sandy-by-karin/en.md | 17 + markdown/org/showcase/sandy-by-karin/es.md | 17 + markdown/org/showcase/sandy-by-karin/fr.md | 19 + markdown/org/showcase/sandy-by-karin/nl.md | 19 + markdown/org/showcase/sandy-by-sunshine/de.md | 20 + markdown/org/showcase/sandy-by-sunshine/en.md | 20 + markdown/org/showcase/sandy-by-sunshine/es.md | 20 + markdown/org/showcase/sandy-by-sunshine/fr.md | 20 + markdown/org/showcase/sandy-by-sunshine/nl.md | 20 + markdown/org/showcase/simon-by-mick/de.md | 16 + markdown/org/showcase/simon-by-mick/en.md | 15 + markdown/org/showcase/simon-by-mick/es.md | 15 + markdown/org/showcase/simon-by-mick/fr.md | 16 + markdown/org/showcase/simon-by-mick/nl.md | 15 + .../org/showcase/simon-by-sewandrew/de.md | 18 + .../org/showcase/simon-by-sewandrew/en.md | 18 + .../org/showcase/simon-by-sewandrew/es.md | 18 + .../org/showcase/simon-by-sewandrew/fr.md | 18 + .../org/showcase/simon-by-sewandrew/nl.md | 18 + markdown/org/showcase/simon-by-stefan/de.md | 12 + markdown/org/showcase/simon-by-stefan/en.md | 12 + markdown/org/showcase/simon-by-stefan/es.md | 12 + markdown/org/showcase/simon-by-stefan/fr.md | 12 + markdown/org/showcase/simon-by-stefan/nl.md | 12 + .../org/showcase/simon-for-schorsch/de.md | 15 + .../org/showcase/simon-for-schorsch/en.md | 14 + .../org/showcase/simon-for-schorsch/es.md | 15 + .../org/showcase/simon-for-schorsch/fr.md | 15 + .../org/showcase/simon-for-schorsch/nl.md | 15 + markdown/org/showcase/simon-on-snook/de.md | 20 + markdown/org/showcase/simon-on-snook/en.md | 20 + markdown/org/showcase/simon-on-snook/es.md | 20 + markdown/org/showcase/simon-on-snook/fr.md | 20 + markdown/org/showcase/simon-on-snook/nl.md | 20 + .../org/showcase/simon-white-stripe/de.md | 16 + .../org/showcase/simon-white-stripe/en.md | 15 + .../org/showcase/simon-white-stripe/es.md | 15 + .../org/showcase/simon-white-stripe/fr.md | 16 + .../org/showcase/simon-white-stripe/nl.md | 15 + markdown/org/showcase/speckles-simon/de.md | 19 + markdown/org/showcase/speckles-simon/en.md | 20 + markdown/org/showcase/speckles-simon/es.md | 20 + markdown/org/showcase/speckles-simon/fr.md | 19 + markdown/org/showcase/speckles-simon/nl.md | 19 + markdown/org/showcase/sven-nr1/de.md | 11 + markdown/org/showcase/sven-nr1/en.md | 10 + markdown/org/showcase/sven-nr1/es.md | 10 + markdown/org/showcase/sven-nr1/fr.md | 11 + markdown/org/showcase/sven-nr1/nl.md | 11 + markdown/org/showcase/sven-nr2/de.md | 11 + markdown/org/showcase/sven-nr2/en.md | 10 + markdown/org/showcase/sven-nr2/es.md | 10 + markdown/org/showcase/sven-nr2/fr.md | 11 + markdown/org/showcase/sven-nr2/nl.md | 11 + markdown/org/showcase/sven-nr3/de.md | 11 + markdown/org/showcase/sven-nr3/en.md | 10 + markdown/org/showcase/sven-nr3/es.md | 10 + markdown/org/showcase/sven-nr3/fr.md | 11 + markdown/org/showcase/sven-nr3/nl.md | 11 + markdown/org/showcase/tartan-fu-mask/de.md | 16 + markdown/org/showcase/tartan-fu-mask/en.md | 16 + markdown/org/showcase/tartan-fu-mask/es.md | 16 + markdown/org/showcase/tartan-fu-mask/fr.md | 16 + markdown/org/showcase/tartan-fu-mask/nl.md | 16 + markdown/org/showcase/teagan-karen/de.md | 12 + markdown/org/showcase/teagan-karen/en.md | 11 + markdown/org/showcase/teagan-karen/es.md | 11 + markdown/org/showcase/teagan-karen/fr.md | 12 + markdown/org/showcase/teagan-karen/nl.md | 11 + markdown/org/showcase/theo-by-theodore/de.md | 17 + markdown/org/showcase/theo-by-theodore/en.md | 17 + markdown/org/showcase/theo-by-theodore/es.md | 17 + markdown/org/showcase/theo-by-theodore/fr.md | 17 + markdown/org/showcase/theo-by-theodore/nl.md | 17 + markdown/org/showcase/theo-jeroen/de.md | 18 + markdown/org/showcase/theo-jeroen/en.md | 17 + markdown/org/showcase/theo-jeroen/es.md | 17 + markdown/org/showcase/theo-jeroen/fr.md | 18 + markdown/org/showcase/theo-jeroen/nl.md | 17 + markdown/org/showcase/tight-aaron/de.md | 11 + markdown/org/showcase/tight-aaron/en.md | 10 + markdown/org/showcase/tight-aaron/es.md | 10 + markdown/org/showcase/tight-aaron/fr.md | 11 + markdown/org/showcase/tight-aaron/nl.md | 11 + markdown/org/showcase/titan-by-deby/de.md | 12 + markdown/org/showcase/titan-by-deby/en.md | 13 + markdown/org/showcase/titan-by-deby/es.md | 13 + markdown/org/showcase/titan-by-deby/fr.md | 12 + markdown/org/showcase/titan-by-deby/nl.md | 12 + markdown/org/showcase/wahid-by-adam/de.md | 19 + markdown/org/showcase/wahid-by-adam/en.md | 20 + markdown/org/showcase/wahid-by-adam/es.md | 20 + markdown/org/showcase/wahid-by-adam/fr.md | 19 + markdown/org/showcase/wahid-by-adam/nl.md | 19 + markdown/org/showcase/wahid-by-minty/de.md | 18 + markdown/org/showcase/wahid-by-minty/en.md | 18 + markdown/org/showcase/wahid-by-minty/es.md | 18 + markdown/org/showcase/wahid-by-minty/fr.md | 18 + markdown/org/showcase/wahid-by-minty/nl.md | 18 + markdown/org/showcase/wahid-by-pho/de.md | 22 + markdown/org/showcase/wahid-by-pho/en.md | 22 + markdown/org/showcase/wahid-by-pho/es.md | 22 + markdown/org/showcase/wahid-by-pho/fr.md | 22 + markdown/org/showcase/wahid-by-pho/nl.md | 22 + markdown/org/showcase/wahid-jeroen/de.md | 18 + markdown/org/showcase/wahid-jeroen/en.md | 17 + markdown/org/showcase/wahid-jeroen/es.md | 17 + markdown/org/showcase/wahid-jeroen/fr.md | 18 + markdown/org/showcase/wahid-jeroen/nl.md | 17 + markdown/org/showcase/wahid-kaena/de.md | 18 + markdown/org/showcase/wahid-kaena/en.md | 18 + markdown/org/showcase/wahid-kaena/es.md | 18 + markdown/org/showcase/wahid-kaena/fr.md | 18 + markdown/org/showcase/wahid-kaena/nl.md | 18 + markdown/org/showcase/waralee-by-wouter/de.md | 14 + markdown/org/showcase/waralee-by-wouter/en.md | 14 + markdown/org/showcase/waralee-by-wouter/es.md | 14 + markdown/org/showcase/waralee-by-wouter/fr.md | 14 + markdown/org/showcase/waralee-by-wouter/nl.md | 14 + .../org/showcase/wonder-warrior-jacket/de.md | 12 + .../org/showcase/wonder-warrior-jacket/en.md | 14 + .../org/showcase/wonder-warrior-jacket/es.md | 14 + .../org/showcase/wonder-warrior-jacket/fr.md | 12 + .../org/showcase/wonder-warrior-jacket/nl.md | 12 + .../org/showcase/wonder-woman-simon/de.md | 21 + .../org/showcase/wonder-woman-simon/en.md | 24 + .../org/showcase/wonder-woman-simon/es.md | 24 + .../org/showcase/wonder-woman-simon/fr.md | 21 + .../org/showcase/wonder-woman-simon/nl.md | 21 + .../org/showcase/yellow-button-simon/de.md | 12 + .../org/showcase/yellow-button-simon/en.md | 12 + .../org/showcase/yellow-button-simon/es.md | 12 + .../org/showcase/yellow-button-simon/fr.md | 12 + .../org/showcase/yellow-button-simon/nl.md | 12 + markdown/org/showcase/yoga-set-by-paul/de.md | 11 + markdown/org/showcase/yoga-set-by-paul/en.md | 10 + markdown/org/showcase/yoga-set-by-paul/es.md | 10 + markdown/org/showcase/yoga-set-by-paul/fr.md | 11 + markdown/org/showcase/yoga-set-by-paul/nl.md | 11 + 830 files changed, 35118 insertions(+) create mode 100644 markdown/org/blog/2-20-for-dolls/de.md create mode 100644 markdown/org/blog/2-20-for-dolls/en.md create mode 100644 markdown/org/blog/2-20-for-dolls/es.md create mode 100644 markdown/org/blog/2-20-for-dolls/fr.md create mode 100644 markdown/org/blog/2-20-for-dolls/nl.md create mode 100644 markdown/org/blog/2019-yearly-report/de.md create mode 100644 markdown/org/blog/2019-yearly-report/en.md create mode 100644 markdown/org/blog/2019-yearly-report/es.md create mode 100644 markdown/org/blog/2019-yearly-report/fr.md create mode 100644 markdown/org/blog/2019-yearly-report/nl.md create mode 100644 markdown/org/blog/2021-wrapup/de.md create mode 100644 markdown/org/blog/2021-wrapup/en.md create mode 100644 markdown/org/blog/2021-wrapup/es.md create mode 100644 markdown/org/blog/2021-wrapup/fr.md create mode 100644 markdown/org/blog/2021-wrapup/nl.md create mode 100644 markdown/org/blog/a-call-for-help/de.md create mode 100644 markdown/org/blog/a-call-for-help/en.md create mode 100644 markdown/org/blog/a-call-for-help/es.md create mode 100644 markdown/org/blog/a-call-for-help/fr.md create mode 100644 markdown/org/blog/a-call-for-help/nl.md create mode 100644 markdown/org/blog/albert-apron/de.md create mode 100644 markdown/org/blog/albert-apron/en.md create mode 100644 markdown/org/blog/albert-apron/es.md create mode 100644 markdown/org/blog/albert-apron/fr.md create mode 100644 markdown/org/blog/albert-apron/nl.md create mode 100644 markdown/org/blog/all-contributors/de.md create mode 100644 markdown/org/blog/all-contributors/en.md create mode 100644 markdown/org/blog/all-contributors/es.md create mode 100644 markdown/org/blog/all-contributors/fr.md create mode 100644 markdown/org/blog/all-contributors/nl.md create mode 100644 markdown/org/blog/annnouncing-yuri/de.md create mode 100644 markdown/org/blog/annnouncing-yuri/en.md create mode 100644 markdown/org/blog/annnouncing-yuri/es.md create mode 100644 markdown/org/blog/annnouncing-yuri/fr.md create mode 100644 markdown/org/blog/annnouncing-yuri/nl.md create mode 100644 markdown/org/blog/announcing-carlita/de.md create mode 100644 markdown/org/blog/announcing-carlita/en.md create mode 100644 markdown/org/blog/announcing-carlita/es.md create mode 100644 markdown/org/blog/announcing-carlita/fr.md create mode 100644 markdown/org/blog/announcing-carlita/nl.md create mode 100644 markdown/org/blog/announcing-carlton-and-bent/de.md create mode 100644 markdown/org/blog/announcing-carlton-and-bent/en.md create mode 100644 markdown/org/blog/announcing-carlton-and-bent/es.md create mode 100644 markdown/org/blog/announcing-carlton-and-bent/fr.md create mode 100644 markdown/org/blog/announcing-carlton-and-bent/nl.md create mode 100644 markdown/org/blog/announcing-charlie/de.md create mode 100644 markdown/org/blog/announcing-charlie/en.md create mode 100644 markdown/org/blog/announcing-charlie/es.md create mode 100644 markdown/org/blog/announcing-charlie/fr.md create mode 100644 markdown/org/blog/announcing-charlie/nl.md create mode 100644 markdown/org/blog/announcing-freesewing-library/de.md create mode 100644 markdown/org/blog/announcing-freesewing-library/en.md create mode 100644 markdown/org/blog/announcing-freesewing-library/es.md create mode 100644 markdown/org/blog/announcing-freesewing-library/fr.md create mode 100644 markdown/org/blog/announcing-freesewing-library/nl.md create mode 100644 markdown/org/blog/announcing-freesewing/de.md create mode 100644 markdown/org/blog/announcing-freesewing/en.md create mode 100644 markdown/org/blog/announcing-freesewing/es.md create mode 100644 markdown/org/blog/announcing-freesewing/fr.md create mode 100644 markdown/org/blog/announcing-freesewing/nl.md create mode 100644 markdown/org/blog/announcing-hortensia/de.md create mode 100644 markdown/org/blog/announcing-hortensia/en.md create mode 100644 markdown/org/blog/announcing-hortensia/es.md create mode 100644 markdown/org/blog/announcing-hortensia/fr.md create mode 100644 markdown/org/blog/announcing-hortensia/nl.md create mode 100644 markdown/org/blog/announcing-penelope/de.md create mode 100644 markdown/org/blog/announcing-penelope/en.md create mode 100644 markdown/org/blog/announcing-penelope/es.md create mode 100644 markdown/org/blog/announcing-penelope/fr.md create mode 100644 markdown/org/blog/announcing-penelope/nl.md create mode 100644 markdown/org/blog/announcing-sandy/de.md create mode 100644 markdown/org/blog/announcing-sandy/en.md create mode 100644 markdown/org/blog/announcing-sandy/es.md create mode 100644 markdown/org/blog/announcing-sandy/fr.md create mode 100644 markdown/org/blog/announcing-sandy/nl.md create mode 100644 markdown/org/blog/announcing-shin/de.md create mode 100644 markdown/org/blog/announcing-shin/en.md create mode 100644 markdown/org/blog/announcing-shin/es.md create mode 100644 markdown/org/blog/announcing-shin/fr.md create mode 100644 markdown/org/blog/announcing-shin/nl.md create mode 100644 markdown/org/blog/announcing-sven/de.md create mode 100644 markdown/org/blog/announcing-sven/en.md create mode 100644 markdown/org/blog/announcing-sven/es.md create mode 100644 markdown/org/blog/announcing-sven/fr.md create mode 100644 markdown/org/blog/announcing-sven/nl.md create mode 100644 markdown/org/blog/announcing-teagan/de.md create mode 100644 markdown/org/blog/announcing-teagan/en.md create mode 100644 markdown/org/blog/announcing-teagan/es.md create mode 100644 markdown/org/blog/announcing-teagan/fr.md create mode 100644 markdown/org/blog/announcing-teagan/nl.md create mode 100644 markdown/org/blog/announcing-ursula/de.md create mode 100644 markdown/org/blog/announcing-ursula/en.md create mode 100644 markdown/org/blog/announcing-ursula/es.md create mode 100644 markdown/org/blog/announcing-ursula/fr.md create mode 100644 markdown/org/blog/announcing-ursula/nl.md create mode 100644 markdown/org/blog/announcing-v2/de.md create mode 100644 markdown/org/blog/announcing-v2/en.md create mode 100644 markdown/org/blog/announcing-v2/es.md create mode 100644 markdown/org/blog/announcing-v2/fr.md create mode 100644 markdown/org/blog/announcing-v2/nl.md create mode 100644 markdown/org/blog/bella-bodice-block/de.md create mode 100644 markdown/org/blog/bella-bodice-block/en.md create mode 100644 markdown/org/blog/bella-bodice-block/es.md create mode 100644 markdown/org/blog/bella-bodice-block/fr.md create mode 100644 markdown/org/blog/bella-bodice-block/nl.md create mode 100644 markdown/org/blog/benjamin-bow-tie-beta/de.md create mode 100644 markdown/org/blog/benjamin-bow-tie-beta/en.md create mode 100644 markdown/org/blog/benjamin-bow-tie-beta/es.md create mode 100644 markdown/org/blog/benjamin-bow-tie-beta/fr.md create mode 100644 markdown/org/blog/benjamin-bow-tie-beta/nl.md create mode 100644 markdown/org/blog/breanna-measurements-sizes-in-2-2/de.md create mode 100644 markdown/org/blog/breanna-measurements-sizes-in-2-2/en.md create mode 100644 markdown/org/blog/breanna-measurements-sizes-in-2-2/es.md create mode 100644 markdown/org/blog/breanna-measurements-sizes-in-2-2/fr.md create mode 100644 markdown/org/blog/breanna-measurements-sizes-in-2-2/nl.md create mode 100644 markdown/org/blog/bye-2020/de.md create mode 100644 markdown/org/blog/bye-2020/en.md create mode 100644 markdown/org/blog/bye-2020/es.md create mode 100644 markdown/org/blog/bye-2020/fr.md create mode 100644 markdown/org/blog/bye-2020/nl.md create mode 100644 markdown/org/blog/calling-all-patrons/de.md create mode 100644 markdown/org/blog/calling-all-patrons/en.md create mode 100644 markdown/org/blog/calling-all-patrons/es.md create mode 100644 markdown/org/blog/calling-all-patrons/fr.md create mode 100644 markdown/org/blog/calling-all-patrons/nl.md create mode 100644 markdown/org/blog/core-1-8-jaeger-across-back/de.md create mode 100644 markdown/org/blog/core-1-8-jaeger-across-back/en.md create mode 100644 markdown/org/blog/core-1-8-jaeger-across-back/es.md create mode 100644 markdown/org/blog/core-1-8-jaeger-across-back/fr.md create mode 100644 markdown/org/blog/core-1-8-jaeger-across-back/nl.md create mode 100644 markdown/org/blog/core-v1-3-0-is-out/de.md create mode 100644 markdown/org/blog/core-v1-3-0-is-out/en.md create mode 100644 markdown/org/blog/core-v1-3-0-is-out/es.md create mode 100644 markdown/org/blog/core-v1-3-0-is-out/fr.md create mode 100644 markdown/org/blog/core-v1-3-0-is-out/nl.md create mode 100644 markdown/org/blog/cornelius-cycling-breeches/de.md create mode 100644 markdown/org/blog/cornelius-cycling-breeches/en.md create mode 100644 markdown/org/blog/cornelius-cycling-breeches/es.md create mode 100644 markdown/org/blog/cornelius-cycling-breeches/fr.md create mode 100644 markdown/org/blog/cornelius-cycling-breeches/nl.md create mode 100644 markdown/org/blog/email-spam-problems/de.md create mode 100644 markdown/org/blog/email-spam-problems/en.md create mode 100644 markdown/org/blog/email-spam-problems/es.md create mode 100644 markdown/org/blog/email-spam-problems/fr.md create mode 100644 markdown/org/blog/email-spam-problems/nl.md create mode 100644 markdown/org/blog/facemask-frenzy/de.md create mode 100644 markdown/org/blog/facemask-frenzy/en.md create mode 100644 markdown/org/blog/facemask-frenzy/es.md create mode 100644 markdown/org/blog/facemask-frenzy/fr.md create mode 100644 markdown/org/blog/facemask-frenzy/nl.md create mode 100644 markdown/org/blog/florence-face-mask/de.md create mode 100644 markdown/org/blog/florence-face-mask/en.md create mode 100644 markdown/org/blog/florence-face-mask/es.md create mode 100644 markdown/org/blog/florence-face-mask/fr.md create mode 100644 markdown/org/blog/florence-face-mask/nl.md create mode 100644 markdown/org/blog/florent-flat-cap-beta/de.md create mode 100644 markdown/org/blog/florent-flat-cap-beta/en.md create mode 100644 markdown/org/blog/florent-flat-cap-beta/es.md create mode 100644 markdown/org/blog/florent-flat-cap-beta/fr.md create mode 100644 markdown/org/blog/florent-flat-cap-beta/nl.md create mode 100644 markdown/org/blog/freesewing-2-19/de.md create mode 100644 markdown/org/blog/freesewing-2-19/en.md create mode 100644 markdown/org/blog/freesewing-2-19/es.md create mode 100644 markdown/org/blog/freesewing-2-19/fr.md create mode 100644 markdown/org/blog/freesewing-2-19/nl.md create mode 100644 markdown/org/blog/freesewing-2-21/en.md create mode 100644 markdown/org/blog/freesewing-goes-jamstack/de.md create mode 100644 markdown/org/blog/freesewing-goes-jamstack/en.md create mode 100644 markdown/org/blog/freesewing-goes-jamstack/es.md create mode 100644 markdown/org/blog/freesewing-goes-jamstack/fr.md create mode 100644 markdown/org/blog/freesewing-goes-jamstack/nl.md create mode 100644 markdown/org/blog/freesewing-v2-1/de.md create mode 100644 markdown/org/blog/freesewing-v2-1/en.md create mode 100644 markdown/org/blog/freesewing-v2-1/es.md create mode 100644 markdown/org/blog/freesewing-v2-1/fr.md create mode 100644 markdown/org/blog/freesewing-v2-1/nl.md create mode 100644 markdown/org/blog/freesewing-v2-7/de.md create mode 100644 markdown/org/blog/freesewing-v2-7/en.md create mode 100644 markdown/org/blog/freesewing-v2-7/es.md create mode 100644 markdown/org/blog/freesewing-v2-7/fr.md create mode 100644 markdown/org/blog/freesewing-v2-7/nl.md create mode 100644 markdown/org/blog/gdpr-plan/de.md create mode 100644 markdown/org/blog/gdpr-plan/en.md create mode 100644 markdown/org/blog/gdpr-plan/es.md create mode 100644 markdown/org/blog/gdpr-plan/fr.md create mode 100644 markdown/org/blog/gdpr-plan/nl.md create mode 100644 markdown/org/blog/gdpr-ready/de.md create mode 100644 markdown/org/blog/gdpr-ready/en.md create mode 100644 markdown/org/blog/gdpr-ready/es.md create mode 100644 markdown/org/blog/gdpr-ready/fr.md create mode 100644 markdown/org/blog/gdpr-ready/nl.md create mode 100644 markdown/org/blog/halloween-cosplays-2021/de.md create mode 100644 markdown/org/blog/halloween-cosplays-2021/en.md create mode 100644 markdown/org/blog/halloween-cosplays-2021/es.md create mode 100644 markdown/org/blog/halloween-cosplays-2021/fr.md create mode 100644 markdown/org/blog/halloween-cosplays-2021/nl.md create mode 100644 markdown/org/blog/halloween-ideas-2021/de.md create mode 100644 markdown/org/blog/halloween-ideas-2021/en.md create mode 100644 markdown/org/blog/halloween-ideas-2021/es.md create mode 100644 markdown/org/blog/halloween-ideas-2021/fr.md create mode 100644 markdown/org/blog/halloween-ideas-2021/nl.md create mode 100644 markdown/org/blog/holmes-deerstalker-hat/de.md create mode 100644 markdown/org/blog/holmes-deerstalker-hat/en.md create mode 100644 markdown/org/blog/holmes-deerstalker-hat/es.md create mode 100644 markdown/org/blog/holmes-deerstalker-hat/fr.md create mode 100644 markdown/org/blog/holmes-deerstalker-hat/nl.md create mode 100644 markdown/org/blog/huey-hoodie-beta/de.md create mode 100644 markdown/org/blog/huey-hoodie-beta/en.md create mode 100644 markdown/org/blog/huey-hoodie-beta/es.md create mode 100644 markdown/org/blog/huey-hoodie-beta/fr.md create mode 100644 markdown/org/blog/huey-hoodie-beta/nl.md create mode 100644 markdown/org/blog/lets-meet-up-in-2019/de.md create mode 100644 markdown/org/blog/lets-meet-up-in-2019/en.md create mode 100644 markdown/org/blog/lets-meet-up-in-2019/es.md create mode 100644 markdown/org/blog/lets-meet-up-in-2019/fr.md create mode 100644 markdown/org/blog/lets-meet-up-in-2019/nl.md create mode 100644 markdown/org/blog/meet-paco/de.md create mode 100644 markdown/org/blog/meet-paco/en.md create mode 100644 markdown/org/blog/meet-paco/es.md create mode 100644 markdown/org/blog/meet-paco/fr.md create mode 100644 markdown/org/blog/meet-paco/nl.md create mode 100644 markdown/org/blog/open-for-business/de.md create mode 100644 markdown/org/blog/open-for-business/en.md create mode 100644 markdown/org/blog/open-for-business/es.md create mode 100644 markdown/org/blog/open-for-business/fr.md create mode 100644 markdown/org/blog/open-for-business/nl.md create mode 100644 markdown/org/blog/privacy-choices/de.md create mode 100644 markdown/org/blog/privacy-choices/en.md create mode 100644 markdown/org/blog/privacy-choices/es.md create mode 100644 markdown/org/blog/privacy-choices/fr.md create mode 100644 markdown/org/blog/privacy-choices/nl.md create mode 100644 markdown/org/blog/react-17/de.md create mode 100644 markdown/org/blog/react-17/en.md create mode 100644 markdown/org/blog/react-17/es.md create mode 100644 markdown/org/blog/react-17/fr.md create mode 100644 markdown/org/blog/react-17/nl.md create mode 100644 markdown/org/blog/roundup-2017-09/de.md create mode 100644 markdown/org/blog/roundup-2017-09/en.md create mode 100644 markdown/org/blog/roundup-2017-09/es.md create mode 100644 markdown/org/blog/roundup-2017-09/fr.md create mode 100644 markdown/org/blog/roundup-2017-09/nl.md create mode 100644 markdown/org/blog/roundup-2017-10/de.md create mode 100644 markdown/org/blog/roundup-2017-10/en.md create mode 100644 markdown/org/blog/roundup-2017-10/es.md create mode 100644 markdown/org/blog/roundup-2017-10/fr.md create mode 100644 markdown/org/blog/roundup-2017-10/nl.md create mode 100644 markdown/org/blog/roundup-2017-11/de.md create mode 100644 markdown/org/blog/roundup-2017-11/en.md create mode 100644 markdown/org/blog/roundup-2017-11/es.md create mode 100644 markdown/org/blog/roundup-2017-11/fr.md create mode 100644 markdown/org/blog/roundup-2017-11/nl.md create mode 100644 markdown/org/blog/roundup-2017-12/de.md create mode 100644 markdown/org/blog/roundup-2017-12/en.md create mode 100644 markdown/org/blog/roundup-2017-12/es.md create mode 100644 markdown/org/blog/roundup-2017-12/fr.md create mode 100644 markdown/org/blog/roundup-2017-12/nl.md create mode 100644 markdown/org/blog/roundup-2018-01/de.md create mode 100644 markdown/org/blog/roundup-2018-01/en.md create mode 100644 markdown/org/blog/roundup-2018-01/es.md create mode 100644 markdown/org/blog/roundup-2018-01/fr.md create mode 100644 markdown/org/blog/roundup-2018-01/nl.md create mode 100644 markdown/org/blog/roundup-2018-02/de.md create mode 100644 markdown/org/blog/roundup-2018-02/en.md create mode 100644 markdown/org/blog/roundup-2018-02/es.md create mode 100644 markdown/org/blog/roundup-2018-02/fr.md create mode 100644 markdown/org/blog/roundup-2018-02/nl.md create mode 100644 markdown/org/blog/roundup-2018-03/de.md create mode 100644 markdown/org/blog/roundup-2018-03/en.md create mode 100644 markdown/org/blog/roundup-2018-03/es.md create mode 100644 markdown/org/blog/roundup-2018-03/fr.md create mode 100644 markdown/org/blog/roundup-2018-03/nl.md create mode 100644 markdown/org/blog/roundup-2018-04/de.md create mode 100644 markdown/org/blog/roundup-2018-04/en.md create mode 100644 markdown/org/blog/roundup-2018-04/es.md create mode 100644 markdown/org/blog/roundup-2018-04/fr.md create mode 100644 markdown/org/blog/roundup-2018-04/nl.md create mode 100644 markdown/org/blog/roundup-2018-05/de.md create mode 100644 markdown/org/blog/roundup-2018-05/en.md create mode 100644 markdown/org/blog/roundup-2018-05/es.md create mode 100644 markdown/org/blog/roundup-2018-05/fr.md create mode 100644 markdown/org/blog/roundup-2018-05/nl.md create mode 100644 markdown/org/blog/roundup-2018-06/de.md create mode 100644 markdown/org/blog/roundup-2018-06/en.md create mode 100644 markdown/org/blog/roundup-2018-06/es.md create mode 100644 markdown/org/blog/roundup-2018-06/fr.md create mode 100644 markdown/org/blog/roundup-2018-06/nl.md create mode 100644 markdown/org/blog/roundup-2018-07/de.md create mode 100644 markdown/org/blog/roundup-2018-07/en.md create mode 100644 markdown/org/blog/roundup-2018-07/es.md create mode 100644 markdown/org/blog/roundup-2018-07/fr.md create mode 100644 markdown/org/blog/roundup-2018-07/nl.md create mode 100644 markdown/org/blog/roundup-2018-09/de.md create mode 100644 markdown/org/blog/roundup-2018-09/en.md create mode 100644 markdown/org/blog/roundup-2018-09/es.md create mode 100644 markdown/org/blog/roundup-2018-09/fr.md create mode 100644 markdown/org/blog/roundup-2018-09/nl.md create mode 100644 markdown/org/blog/roundup-2018-10/de.md create mode 100644 markdown/org/blog/roundup-2018-10/en.md create mode 100644 markdown/org/blog/roundup-2018-10/es.md create mode 100644 markdown/org/blog/roundup-2018-10/fr.md create mode 100644 markdown/org/blog/roundup-2018-10/nl.md create mode 100644 markdown/org/blog/roundup-2018-11/de.md create mode 100644 markdown/org/blog/roundup-2018-11/en.md create mode 100644 markdown/org/blog/roundup-2018-11/es.md create mode 100644 markdown/org/blog/roundup-2018-11/fr.md create mode 100644 markdown/org/blog/roundup-2018-11/nl.md create mode 100644 markdown/org/blog/roundup-2019-01/de.md create mode 100644 markdown/org/blog/roundup-2019-01/en.md create mode 100644 markdown/org/blog/roundup-2019-01/es.md create mode 100644 markdown/org/blog/roundup-2019-01/fr.md create mode 100644 markdown/org/blog/roundup-2019-01/nl.md create mode 100644 markdown/org/blog/the-refashioners-2017/de.md create mode 100644 markdown/org/blog/the-refashioners-2017/en.md create mode 100644 markdown/org/blog/the-refashioners-2017/es.md create mode 100644 markdown/org/blog/the-refashioners-2017/fr.md create mode 100644 markdown/org/blog/the-refashioners-2017/nl.md create mode 100644 markdown/org/blog/v2-22-then-v3/en.md create mode 100644 markdown/org/newsletter/2021q2/en.md create mode 100644 markdown/org/newsletter/2021q3/en.md create mode 100644 markdown/org/newsletter/2021q4/en.md create mode 100644 markdown/org/newsletter/2022q1/en.md create mode 100644 markdown/org/newsletter/2022q2/en.md create mode 100644 markdown/org/newsletter/2022q3/en.md create mode 100644 markdown/org/newsletter/2022q4/en.md create mode 100644 markdown/org/newsletter/2023q1/en.md create mode 100644 markdown/org/newsletter/2023q2/en.md create mode 100644 markdown/org/newsletter/2023q3/en.md create mode 100644 markdown/org/showcase/aaron-by-joost/de.md create mode 100644 markdown/org/showcase/aaron-by-joost/en.md create mode 100644 markdown/org/showcase/aaron-by-joost/es.md create mode 100644 markdown/org/showcase/aaron-by-joost/fr.md create mode 100644 markdown/org/showcase/aaron-by-joost/nl.md create mode 100644 markdown/org/showcase/airline-blanket-sven/de.md create mode 100644 markdown/org/showcase/airline-blanket-sven/en.md create mode 100644 markdown/org/showcase/airline-blanket-sven/es.md create mode 100644 markdown/org/showcase/airline-blanket-sven/fr.md create mode 100644 markdown/org/showcase/airline-blanket-sven/nl.md create mode 100644 markdown/org/showcase/albert-by-wouter/de.md create mode 100644 markdown/org/showcase/albert-by-wouter/en.md create mode 100644 markdown/org/showcase/albert-by-wouter/es.md create mode 100644 markdown/org/showcase/albert-by-wouter/fr.md create mode 100644 markdown/org/showcase/albert-by-wouter/nl.md create mode 100644 markdown/org/showcase/anneke-huey-black/de.md create mode 100644 markdown/org/showcase/anneke-huey-black/en.md create mode 100644 markdown/org/showcase/anneke-huey-black/es.md create mode 100644 markdown/org/showcase/anneke-huey-black/fr.md create mode 100644 markdown/org/showcase/anneke-huey-black/nl.md create mode 100644 markdown/org/showcase/anneke-huey-grey/de.md create mode 100644 markdown/org/showcase/anneke-huey-grey/en.md create mode 100644 markdown/org/showcase/anneke-huey-grey/es.md create mode 100644 markdown/org/showcase/anneke-huey-grey/fr.md create mode 100644 markdown/org/showcase/anneke-huey-grey/nl.md create mode 100644 markdown/org/showcase/anneke-huey/de.md create mode 100644 markdown/org/showcase/anneke-huey/en.md create mode 100644 markdown/org/showcase/anneke-huey/es.md create mode 100644 markdown/org/showcase/anneke-huey/fr.md create mode 100644 markdown/org/showcase/anneke-huey/nl.md create mode 100644 markdown/org/showcase/bella-block/de.md create mode 100644 markdown/org/showcase/bella-block/en.md create mode 100644 markdown/org/showcase/bella-block/es.md create mode 100644 markdown/org/showcase/bella-block/fr.md create mode 100644 markdown/org/showcase/bella-block/nl.md create mode 100644 markdown/org/showcase/bella-by-karen/de.md create mode 100644 markdown/org/showcase/bella-by-karen/en.md create mode 100644 markdown/org/showcase/bella-by-karen/es.md create mode 100644 markdown/org/showcase/bella-by-karen/fr.md create mode 100644 markdown/org/showcase/bella-by-karen/nl.md create mode 100644 markdown/org/showcase/black-bruce/de.md create mode 100644 markdown/org/showcase/black-bruce/en.md create mode 100644 markdown/org/showcase/black-bruce/es.md create mode 100644 markdown/org/showcase/black-bruce/fr.md create mode 100644 markdown/org/showcase/black-bruce/nl.md create mode 100644 markdown/org/showcase/black-hugo/de.md create mode 100644 markdown/org/showcase/black-hugo/en.md create mode 100644 markdown/org/showcase/black-hugo/es.md create mode 100644 markdown/org/showcase/black-hugo/fr.md create mode 100644 markdown/org/showcase/black-hugo/nl.md create mode 100644 markdown/org/showcase/bleach-dyed-bruce/de.md create mode 100644 markdown/org/showcase/bleach-dyed-bruce/en.md create mode 100644 markdown/org/showcase/bleach-dyed-bruce/es.md create mode 100644 markdown/org/showcase/bleach-dyed-bruce/fr.md create mode 100644 markdown/org/showcase/bleach-dyed-bruce/nl.md create mode 100644 markdown/org/showcase/blue-simon/de.md create mode 100644 markdown/org/showcase/blue-simon/en.md create mode 100644 markdown/org/showcase/blue-simon/es.md create mode 100644 markdown/org/showcase/blue-simon/fr.md create mode 100644 markdown/org/showcase/blue-simon/nl.md create mode 100644 markdown/org/showcase/blue-theo/de.md create mode 100644 markdown/org/showcase/blue-theo/en.md create mode 100644 markdown/org/showcase/blue-theo/es.md create mode 100644 markdown/org/showcase/blue-theo/fr.md create mode 100644 markdown/org/showcase/blue-theo/nl.md create mode 100644 markdown/org/showcase/bound-wahid/de.md create mode 100644 markdown/org/showcase/bound-wahid/en.md create mode 100644 markdown/org/showcase/bound-wahid/es.md create mode 100644 markdown/org/showcase/bound-wahid/fr.md create mode 100644 markdown/org/showcase/bound-wahid/nl.md create mode 100644 markdown/org/showcase/brian-by-stefan-1/de.md create mode 100644 markdown/org/showcase/brian-by-stefan-1/en.md create mode 100644 markdown/org/showcase/brian-by-stefan-1/es.md create mode 100644 markdown/org/showcase/brian-by-stefan-1/fr.md create mode 100644 markdown/org/showcase/brian-by-stefan-1/nl.md create mode 100644 markdown/org/showcase/brian-by-stefan-2/de.md create mode 100644 markdown/org/showcase/brian-by-stefan-2/en.md create mode 100644 markdown/org/showcase/brian-by-stefan-2/es.md create mode 100644 markdown/org/showcase/brian-by-stefan-2/fr.md create mode 100644 markdown/org/showcase/brian-by-stefan-2/nl.md create mode 100644 markdown/org/showcase/brian-by-stefan-3/de.md create mode 100644 markdown/org/showcase/brian-by-stefan-3/en.md create mode 100644 markdown/org/showcase/brian-by-stefan-3/es.md create mode 100644 markdown/org/showcase/brian-by-stefan-3/fr.md create mode 100644 markdown/org/showcase/brian-by-stefan-3/nl.md create mode 100644 markdown/org/showcase/brian-by-stefan-4/de.md create mode 100644 markdown/org/showcase/brian-by-stefan-4/en.md create mode 100644 markdown/org/showcase/brian-by-stefan-4/es.md create mode 100644 markdown/org/showcase/brian-by-stefan-4/fr.md create mode 100644 markdown/org/showcase/brian-by-stefan-4/nl.md create mode 100644 markdown/org/showcase/bruce-on-doll/de.md create mode 100644 markdown/org/showcase/bruce-on-doll/en.md create mode 100644 markdown/org/showcase/bruce-on-doll/es.md create mode 100644 markdown/org/showcase/bruce-on-doll/fr.md create mode 100644 markdown/org/showcase/bruce-on-doll/nl.md create mode 100644 markdown/org/showcase/bruce-three-pack/de.md create mode 100644 markdown/org/showcase/bruce-three-pack/en.md create mode 100644 markdown/org/showcase/bruce-three-pack/es.md create mode 100644 markdown/org/showcase/bruce-three-pack/fr.md create mode 100644 markdown/org/showcase/bruce-three-pack/nl.md create mode 100644 markdown/org/showcase/bruces-by-paul/de.md create mode 100644 markdown/org/showcase/bruces-by-paul/en.md create mode 100644 markdown/org/showcase/bruces-by-paul/es.md create mode 100644 markdown/org/showcase/bruces-by-paul/fr.md create mode 100644 markdown/org/showcase/bruces-by-paul/nl.md create mode 100644 markdown/org/showcase/bulbasaur-huey/de.md create mode 100644 markdown/org/showcase/bulbasaur-huey/en.md create mode 100644 markdown/org/showcase/bulbasaur-huey/es.md create mode 100644 markdown/org/showcase/bulbasaur-huey/fr.md create mode 100644 markdown/org/showcase/bulbasaur-huey/nl.md create mode 100644 markdown/org/showcase/carlton-by-rudy/de.md create mode 100644 markdown/org/showcase/carlton-by-rudy/en.md create mode 100644 markdown/org/showcase/carlton-by-rudy/es.md create mode 100644 markdown/org/showcase/carlton-by-rudy/fr.md create mode 100644 markdown/org/showcase/carlton-by-rudy/nl.md create mode 100644 markdown/org/showcase/casual-pink-simon/de.md create mode 100644 markdown/org/showcase/casual-pink-simon/en.md create mode 100644 markdown/org/showcase/casual-pink-simon/es.md create mode 100644 markdown/org/showcase/casual-pink-simon/fr.md create mode 100644 markdown/org/showcase/casual-pink-simon/nl.md create mode 100644 markdown/org/showcase/charlie-by-bob/de.md create mode 100644 markdown/org/showcase/charlie-by-bob/en.md create mode 100644 markdown/org/showcase/charlie-by-bob/es.md create mode 100644 markdown/org/showcase/charlie-by-bob/fr.md create mode 100644 markdown/org/showcase/charlie-by-bob/nl.md create mode 100644 markdown/org/showcase/charlie-by-joost-2/de.md create mode 100644 markdown/org/showcase/charlie-by-joost-2/en.md create mode 100644 markdown/org/showcase/charlie-by-joost-2/es.md create mode 100644 markdown/org/showcase/charlie-by-joost-2/fr.md create mode 100644 markdown/org/showcase/charlie-by-joost-2/nl.md create mode 100644 markdown/org/showcase/charlie-by-joost/de.md create mode 100644 markdown/org/showcase/charlie-by-joost/en.md create mode 100644 markdown/org/showcase/charlie-by-joost/es.md create mode 100644 markdown/org/showcase/charlie-by-joost/fr.md create mode 100644 markdown/org/showcase/charlie-by-joost/nl.md create mode 100644 markdown/org/showcase/charlie-on-sorcha/de.md create mode 100644 markdown/org/showcase/charlie-on-sorcha/en.md create mode 100644 markdown/org/showcase/charlie-on-sorcha/es.md create mode 100644 markdown/org/showcase/charlie-on-sorcha/fr.md create mode 100644 markdown/org/showcase/charlie-on-sorcha/nl.md create mode 100644 markdown/org/showcase/claire-does-sven/de.md create mode 100644 markdown/org/showcase/claire-does-sven/en.md create mode 100644 markdown/org/showcase/claire-does-sven/es.md create mode 100644 markdown/org/showcase/claire-does-sven/fr.md create mode 100644 markdown/org/showcase/claire-does-sven/nl.md create mode 100644 markdown/org/showcase/corduroy-theo/de.md create mode 100644 markdown/org/showcase/corduroy-theo/en.md create mode 100644 markdown/org/showcase/corduroy-theo/es.md create mode 100644 markdown/org/showcase/corduroy-theo/fr.md create mode 100644 markdown/org/showcase/corduroy-theo/nl.md create mode 100644 markdown/org/showcase/cornelius-by-wouter/de.md create mode 100644 markdown/org/showcase/cornelius-by-wouter/en.md create mode 100644 markdown/org/showcase/cornelius-by-wouter/es.md create mode 100644 markdown/org/showcase/cornelius-by-wouter/fr.md create mode 100644 markdown/org/showcase/cornelius-by-wouter/nl.md create mode 100644 markdown/org/showcase/fantastic-four-hugo/de.md create mode 100644 markdown/org/showcase/fantastic-four-hugo/en.md create mode 100644 markdown/org/showcase/fantastic-four-hugo/es.md create mode 100644 markdown/org/showcase/fantastic-four-hugo/fr.md create mode 100644 markdown/org/showcase/fantastic-four-hugo/nl.md create mode 100644 markdown/org/showcase/fighter-hoodie/de.md create mode 100644 markdown/org/showcase/fighter-hoodie/en.md create mode 100644 markdown/org/showcase/fighter-hoodie/es.md create mode 100644 markdown/org/showcase/fighter-hoodie/fr.md create mode 100644 markdown/org/showcase/fighter-hoodie/nl.md create mode 100644 markdown/org/showcase/florence-jv/de.md create mode 100644 markdown/org/showcase/florence-jv/en.md create mode 100644 markdown/org/showcase/florence-jv/es.md create mode 100644 markdown/org/showcase/florence-jv/fr.md create mode 100644 markdown/org/showcase/florence-jv/nl.md create mode 100644 markdown/org/showcase/florence/de.md create mode 100644 markdown/org/showcase/florence/en.md create mode 100644 markdown/org/showcase/florence/es.md create mode 100644 markdown/org/showcase/florence/fr.md create mode 100644 markdown/org/showcase/florence/nl.md create mode 100644 markdown/org/showcase/florent-by-enno/de.md create mode 100644 markdown/org/showcase/florent-by-enno/en.md create mode 100644 markdown/org/showcase/florent-by-enno/es.md create mode 100644 markdown/org/showcase/florent-by-enno/fr.md create mode 100644 markdown/org/showcase/florent-by-enno/nl.md create mode 100644 markdown/org/showcase/florent-by-michele/de.md create mode 100644 markdown/org/showcase/florent-by-michele/en.md create mode 100644 markdown/org/showcase/florent-by-michele/es.md create mode 100644 markdown/org/showcase/florent-by-michele/fr.md create mode 100644 markdown/org/showcase/florent-by-michele/nl.md create mode 100644 markdown/org/showcase/florent-by-wim/de.md create mode 100644 markdown/org/showcase/florent-by-wim/en.md create mode 100644 markdown/org/showcase/florent-by-wim/es.md create mode 100644 markdown/org/showcase/florent-by-wim/fr.md create mode 100644 markdown/org/showcase/florent-by-wim/nl.md create mode 100644 markdown/org/showcase/florent-by-wouter/de.md create mode 100644 markdown/org/showcase/florent-by-wouter/en.md create mode 100644 markdown/org/showcase/florent-by-wouter/es.md create mode 100644 markdown/org/showcase/florent-by-wouter/fr.md create mode 100644 markdown/org/showcase/florent-by-wouter/nl.md create mode 100644 markdown/org/showcase/french-terry-sven/de.md create mode 100644 markdown/org/showcase/french-terry-sven/en.md create mode 100644 markdown/org/showcase/french-terry-sven/es.md create mode 100644 markdown/org/showcase/french-terry-sven/fr.md create mode 100644 markdown/org/showcase/french-terry-sven/nl.md create mode 100644 markdown/org/showcase/green-wahid/de.md create mode 100644 markdown/org/showcase/green-wahid/en.md create mode 100644 markdown/org/showcase/green-wahid/es.md create mode 100644 markdown/org/showcase/green-wahid/fr.md create mode 100644 markdown/org/showcase/green-wahid/nl.md create mode 100644 markdown/org/showcase/grey-sven/de.md create mode 100644 markdown/org/showcase/grey-sven/en.md create mode 100644 markdown/org/showcase/grey-sven/es.md create mode 100644 markdown/org/showcase/grey-sven/fr.md create mode 100644 markdown/org/showcase/grey-sven/nl.md create mode 100644 markdown/org/showcase/hortensia-by-wouter/de.md create mode 100644 markdown/org/showcase/hortensia-by-wouter/en.md create mode 100644 markdown/org/showcase/hortensia-by-wouter/es.md create mode 100644 markdown/org/showcase/hortensia-by-wouter/fr.md create mode 100644 markdown/org/showcase/hortensia-by-wouter/nl.md create mode 100644 markdown/org/showcase/huey-by-minty/de.md create mode 100644 markdown/org/showcase/huey-by-minty/en.md create mode 100644 markdown/org/showcase/huey-by-minty/es.md create mode 100644 markdown/org/showcase/huey-by-minty/fr.md create mode 100644 markdown/org/showcase/huey-by-minty/nl.md create mode 100644 markdown/org/showcase/huey-by-paul/de.md create mode 100644 markdown/org/showcase/huey-by-paul/en.md create mode 100644 markdown/org/showcase/huey-by-paul/es.md create mode 100644 markdown/org/showcase/huey-by-paul/fr.md create mode 100644 markdown/org/showcase/huey-by-paul/nl.md create mode 100644 markdown/org/showcase/hugo-by-karin/de.md create mode 100644 markdown/org/showcase/hugo-by-karin/en.md create mode 100644 markdown/org/showcase/hugo-by-karin/es.md create mode 100644 markdown/org/showcase/hugo-by-karin/fr.md create mode 100644 markdown/org/showcase/hugo-by-karin/nl.md create mode 100644 markdown/org/showcase/hugo-by-lainey/de.md create mode 100644 markdown/org/showcase/hugo-by-lainey/en.md create mode 100644 markdown/org/showcase/hugo-by-lainey/es.md create mode 100644 markdown/org/showcase/hugo-by-lainey/fr.md create mode 100644 markdown/org/showcase/hugo-by-lainey/nl.md create mode 100644 markdown/org/showcase/hugo-saul/de.md create mode 100644 markdown/org/showcase/hugo-saul/en.md create mode 100644 markdown/org/showcase/hugo-saul/es.md create mode 100644 markdown/org/showcase/hugo-saul/fr.md create mode 100644 markdown/org/showcase/hugo-saul/nl.md create mode 100644 markdown/org/showcase/husband-hugo/de.md create mode 100644 markdown/org/showcase/husband-hugo/en.md create mode 100644 markdown/org/showcase/husband-hugo/es.md create mode 100644 markdown/org/showcase/husband-hugo/fr.md create mode 100644 markdown/org/showcase/husband-hugo/nl.md create mode 100644 markdown/org/showcase/liberty-trayvon/de.md create mode 100644 markdown/org/showcase/liberty-trayvon/en.md create mode 100644 markdown/org/showcase/liberty-trayvon/es.md create mode 100644 markdown/org/showcase/liberty-trayvon/fr.md create mode 100644 markdown/org/showcase/liberty-trayvon/nl.md create mode 100644 markdown/org/showcase/linnen-jaeger-by-paul/de.md create mode 100644 markdown/org/showcase/linnen-jaeger-by-paul/en.md create mode 100644 markdown/org/showcase/linnen-jaeger-by-paul/es.md create mode 100644 markdown/org/showcase/linnen-jaeger-by-paul/fr.md create mode 100644 markdown/org/showcase/linnen-jaeger-by-paul/nl.md create mode 100644 markdown/org/showcase/linnen-theo/de.md create mode 100644 markdown/org/showcase/linnen-theo/en.md create mode 100644 markdown/org/showcase/linnen-theo/es.md create mode 100644 markdown/org/showcase/linnen-theo/fr.md create mode 100644 markdown/org/showcase/linnen-theo/nl.md create mode 100644 markdown/org/showcase/mark-wears-simon/de.md create mode 100644 markdown/org/showcase/mark-wears-simon/en.md create mode 100644 markdown/org/showcase/mark-wears-simon/es.md create mode 100644 markdown/org/showcase/mark-wears-simon/fr.md create mode 100644 markdown/org/showcase/mark-wears-simon/nl.md create mode 100644 markdown/org/showcase/matching-simon/de.md create mode 100644 markdown/org/showcase/matching-simon/en.md create mode 100644 markdown/org/showcase/matching-simon/es.md create mode 100644 markdown/org/showcase/matching-simon/fr.md create mode 100644 markdown/org/showcase/matching-simon/nl.md create mode 100644 markdown/org/showcase/more-wahid-by-adam/de.md create mode 100644 markdown/org/showcase/more-wahid-by-adam/en.md create mode 100644 markdown/org/showcase/more-wahid-by-adam/es.md create mode 100644 markdown/org/showcase/more-wahid-by-adam/fr.md create mode 100644 markdown/org/showcase/more-wahid-by-adam/nl.md create mode 100644 markdown/org/showcase/nani-hugo/de.md create mode 100644 markdown/org/showcase/nani-hugo/en.md create mode 100644 markdown/org/showcase/nani-hugo/es.md create mode 100644 markdown/org/showcase/nani-hugo/fr.md create mode 100644 markdown/org/showcase/nani-hugo/nl.md create mode 100644 markdown/org/showcase/nsfw-bruce/de.md create mode 100644 markdown/org/showcase/nsfw-bruce/en.md create mode 100644 markdown/org/showcase/nsfw-bruce/es.md create mode 100644 markdown/org/showcase/nsfw-bruce/fr.md create mode 100644 markdown/org/showcase/nsfw-bruce/nl.md create mode 100644 markdown/org/showcase/outfit-wahid-theo-florent-by-paul/de.md create mode 100644 markdown/org/showcase/outfit-wahid-theo-florent-by-paul/en.md create mode 100644 markdown/org/showcase/outfit-wahid-theo-florent-by-paul/fr.md create mode 100644 markdown/org/showcase/outfit-wahid-theo-florent-by-paul/nl.md create mode 100644 markdown/org/showcase/outfit-wahid-theo-simon-by-paul/de.md create mode 100644 markdown/org/showcase/outfit-wahid-theo-simon-by-paul/en.md create mode 100644 markdown/org/showcase/outfit-wahid-theo-simon-by-paul/es.md create mode 100644 markdown/org/showcase/outfit-wahid-theo-simon-by-paul/fr.md create mode 100644 markdown/org/showcase/paco-by-joost/de.md create mode 100644 markdown/org/showcase/paco-by-joost/en.md create mode 100644 markdown/org/showcase/paco-by-joost/es.md create mode 100644 markdown/org/showcase/paco-by-joost/fr.md create mode 100644 markdown/org/showcase/paco-by-joost/nl.md create mode 100644 markdown/org/showcase/paco-by-karen/de.md create mode 100644 markdown/org/showcase/paco-by-karen/en.md create mode 100644 markdown/org/showcase/paco-by-karen/es.md create mode 100644 markdown/org/showcase/paco-by-karen/fr.md create mode 100644 markdown/org/showcase/paco-by-karen/nl.md create mode 100644 markdown/org/showcase/pirate-bruce/de.md create mode 100644 markdown/org/showcase/pirate-bruce/en.md create mode 100644 markdown/org/showcase/pirate-bruce/es.md create mode 100644 markdown/org/showcase/pirate-bruce/fr.md create mode 100644 markdown/org/showcase/pirate-bruce/nl.md create mode 100644 markdown/org/showcase/purple-bruce/de.md create mode 100644 markdown/org/showcase/purple-bruce/en.md create mode 100644 markdown/org/showcase/purple-bruce/es.md create mode 100644 markdown/org/showcase/purple-bruce/fr.md create mode 100644 markdown/org/showcase/purple-bruce/nl.md create mode 100644 markdown/org/showcase/purple-huey/de.md create mode 100644 markdown/org/showcase/purple-huey/en.md create mode 100644 markdown/org/showcase/purple-huey/es.md create mode 100644 markdown/org/showcase/purple-huey/fr.md create mode 100644 markdown/org/showcase/purple-huey/nl.md create mode 100644 markdown/org/showcase/quilted-jersey-huey/de.md create mode 100644 markdown/org/showcase/quilted-jersey-huey/en.md create mode 100644 markdown/org/showcase/quilted-jersey-huey/es.md create mode 100644 markdown/org/showcase/quilted-jersey-huey/fr.md create mode 100644 markdown/org/showcase/quilted-jersey-huey/nl.md create mode 100644 markdown/org/showcase/red-button-simon/de.md create mode 100644 markdown/org/showcase/red-button-simon/en.md create mode 100644 markdown/org/showcase/red-button-simon/es.md create mode 100644 markdown/org/showcase/red-button-simon/fr.md create mode 100644 markdown/org/showcase/red-button-simon/nl.md create mode 100644 markdown/org/showcase/red-theo/de.md create mode 100644 markdown/org/showcase/red-theo/en.md create mode 100644 markdown/org/showcase/red-theo/es.md create mode 100644 markdown/org/showcase/red-theo/fr.md create mode 100644 markdown/org/showcase/red-theo/nl.md create mode 100644 markdown/org/showcase/ricos-huey/de.md create mode 100644 markdown/org/showcase/ricos-huey/en.md create mode 100644 markdown/org/showcase/ricos-huey/es.md create mode 100644 markdown/org/showcase/ricos-huey/fr.md create mode 100644 markdown/org/showcase/ricos-huey/nl.md create mode 100644 markdown/org/showcase/ricos-sven/de.md create mode 100644 markdown/org/showcase/ricos-sven/en.md create mode 100644 markdown/org/showcase/ricos-sven/es.md create mode 100644 markdown/org/showcase/ricos-sven/fr.md create mode 100644 markdown/org/showcase/ricos-sven/nl.md create mode 100644 markdown/org/showcase/sample-wahid/de.md create mode 100644 markdown/org/showcase/sample-wahid/en.md create mode 100644 markdown/org/showcase/sample-wahid/es.md create mode 100644 markdown/org/showcase/sample-wahid/fr.md create mode 100644 markdown/org/showcase/sample-wahid/nl.md create mode 100644 markdown/org/showcase/sandy-by-adam/de.md create mode 100644 markdown/org/showcase/sandy-by-adam/en.md create mode 100644 markdown/org/showcase/sandy-by-adam/es.md create mode 100644 markdown/org/showcase/sandy-by-adam/fr.md create mode 100644 markdown/org/showcase/sandy-by-adam/nl.md create mode 100644 markdown/org/showcase/sandy-by-anneke/de.md create mode 100644 markdown/org/showcase/sandy-by-anneke/en.md create mode 100644 markdown/org/showcase/sandy-by-anneke/es.md create mode 100644 markdown/org/showcase/sandy-by-anneke/fr.md create mode 100644 markdown/org/showcase/sandy-by-anneke/nl.md create mode 100644 markdown/org/showcase/sandy-by-jv/de.md create mode 100644 markdown/org/showcase/sandy-by-jv/en.md create mode 100644 markdown/org/showcase/sandy-by-jv/es.md create mode 100644 markdown/org/showcase/sandy-by-jv/fr.md create mode 100644 markdown/org/showcase/sandy-by-jv/nl.md create mode 100644 markdown/org/showcase/sandy-by-karin/de.md create mode 100644 markdown/org/showcase/sandy-by-karin/en.md create mode 100644 markdown/org/showcase/sandy-by-karin/es.md create mode 100644 markdown/org/showcase/sandy-by-karin/fr.md create mode 100644 markdown/org/showcase/sandy-by-karin/nl.md create mode 100644 markdown/org/showcase/sandy-by-sunshine/de.md create mode 100644 markdown/org/showcase/sandy-by-sunshine/en.md create mode 100644 markdown/org/showcase/sandy-by-sunshine/es.md create mode 100644 markdown/org/showcase/sandy-by-sunshine/fr.md create mode 100644 markdown/org/showcase/sandy-by-sunshine/nl.md create mode 100644 markdown/org/showcase/simon-by-mick/de.md create mode 100644 markdown/org/showcase/simon-by-mick/en.md create mode 100644 markdown/org/showcase/simon-by-mick/es.md create mode 100644 markdown/org/showcase/simon-by-mick/fr.md create mode 100644 markdown/org/showcase/simon-by-mick/nl.md create mode 100644 markdown/org/showcase/simon-by-sewandrew/de.md create mode 100644 markdown/org/showcase/simon-by-sewandrew/en.md create mode 100644 markdown/org/showcase/simon-by-sewandrew/es.md create mode 100644 markdown/org/showcase/simon-by-sewandrew/fr.md create mode 100644 markdown/org/showcase/simon-by-sewandrew/nl.md create mode 100644 markdown/org/showcase/simon-by-stefan/de.md create mode 100644 markdown/org/showcase/simon-by-stefan/en.md create mode 100644 markdown/org/showcase/simon-by-stefan/es.md create mode 100644 markdown/org/showcase/simon-by-stefan/fr.md create mode 100644 markdown/org/showcase/simon-by-stefan/nl.md create mode 100644 markdown/org/showcase/simon-for-schorsch/de.md create mode 100644 markdown/org/showcase/simon-for-schorsch/en.md create mode 100644 markdown/org/showcase/simon-for-schorsch/es.md create mode 100644 markdown/org/showcase/simon-for-schorsch/fr.md create mode 100644 markdown/org/showcase/simon-for-schorsch/nl.md create mode 100644 markdown/org/showcase/simon-on-snook/de.md create mode 100644 markdown/org/showcase/simon-on-snook/en.md create mode 100644 markdown/org/showcase/simon-on-snook/es.md create mode 100644 markdown/org/showcase/simon-on-snook/fr.md create mode 100644 markdown/org/showcase/simon-on-snook/nl.md create mode 100644 markdown/org/showcase/simon-white-stripe/de.md create mode 100644 markdown/org/showcase/simon-white-stripe/en.md create mode 100644 markdown/org/showcase/simon-white-stripe/es.md create mode 100644 markdown/org/showcase/simon-white-stripe/fr.md create mode 100644 markdown/org/showcase/simon-white-stripe/nl.md create mode 100644 markdown/org/showcase/speckles-simon/de.md create mode 100644 markdown/org/showcase/speckles-simon/en.md create mode 100644 markdown/org/showcase/speckles-simon/es.md create mode 100644 markdown/org/showcase/speckles-simon/fr.md create mode 100644 markdown/org/showcase/speckles-simon/nl.md create mode 100644 markdown/org/showcase/sven-nr1/de.md create mode 100644 markdown/org/showcase/sven-nr1/en.md create mode 100644 markdown/org/showcase/sven-nr1/es.md create mode 100644 markdown/org/showcase/sven-nr1/fr.md create mode 100644 markdown/org/showcase/sven-nr1/nl.md create mode 100644 markdown/org/showcase/sven-nr2/de.md create mode 100644 markdown/org/showcase/sven-nr2/en.md create mode 100644 markdown/org/showcase/sven-nr2/es.md create mode 100644 markdown/org/showcase/sven-nr2/fr.md create mode 100644 markdown/org/showcase/sven-nr2/nl.md create mode 100644 markdown/org/showcase/sven-nr3/de.md create mode 100644 markdown/org/showcase/sven-nr3/en.md create mode 100644 markdown/org/showcase/sven-nr3/es.md create mode 100644 markdown/org/showcase/sven-nr3/fr.md create mode 100644 markdown/org/showcase/sven-nr3/nl.md create mode 100644 markdown/org/showcase/tartan-fu-mask/de.md create mode 100644 markdown/org/showcase/tartan-fu-mask/en.md create mode 100644 markdown/org/showcase/tartan-fu-mask/es.md create mode 100644 markdown/org/showcase/tartan-fu-mask/fr.md create mode 100644 markdown/org/showcase/tartan-fu-mask/nl.md create mode 100644 markdown/org/showcase/teagan-karen/de.md create mode 100644 markdown/org/showcase/teagan-karen/en.md create mode 100644 markdown/org/showcase/teagan-karen/es.md create mode 100644 markdown/org/showcase/teagan-karen/fr.md create mode 100644 markdown/org/showcase/teagan-karen/nl.md create mode 100644 markdown/org/showcase/theo-by-theodore/de.md create mode 100644 markdown/org/showcase/theo-by-theodore/en.md create mode 100644 markdown/org/showcase/theo-by-theodore/es.md create mode 100644 markdown/org/showcase/theo-by-theodore/fr.md create mode 100644 markdown/org/showcase/theo-by-theodore/nl.md create mode 100644 markdown/org/showcase/theo-jeroen/de.md create mode 100644 markdown/org/showcase/theo-jeroen/en.md create mode 100644 markdown/org/showcase/theo-jeroen/es.md create mode 100644 markdown/org/showcase/theo-jeroen/fr.md create mode 100644 markdown/org/showcase/theo-jeroen/nl.md create mode 100644 markdown/org/showcase/tight-aaron/de.md create mode 100644 markdown/org/showcase/tight-aaron/en.md create mode 100644 markdown/org/showcase/tight-aaron/es.md create mode 100644 markdown/org/showcase/tight-aaron/fr.md create mode 100644 markdown/org/showcase/tight-aaron/nl.md create mode 100644 markdown/org/showcase/titan-by-deby/de.md create mode 100644 markdown/org/showcase/titan-by-deby/en.md create mode 100644 markdown/org/showcase/titan-by-deby/es.md create mode 100644 markdown/org/showcase/titan-by-deby/fr.md create mode 100644 markdown/org/showcase/titan-by-deby/nl.md create mode 100644 markdown/org/showcase/wahid-by-adam/de.md create mode 100644 markdown/org/showcase/wahid-by-adam/en.md create mode 100644 markdown/org/showcase/wahid-by-adam/es.md create mode 100644 markdown/org/showcase/wahid-by-adam/fr.md create mode 100644 markdown/org/showcase/wahid-by-adam/nl.md create mode 100644 markdown/org/showcase/wahid-by-minty/de.md create mode 100644 markdown/org/showcase/wahid-by-minty/en.md create mode 100644 markdown/org/showcase/wahid-by-minty/es.md create mode 100644 markdown/org/showcase/wahid-by-minty/fr.md create mode 100644 markdown/org/showcase/wahid-by-minty/nl.md create mode 100644 markdown/org/showcase/wahid-by-pho/de.md create mode 100644 markdown/org/showcase/wahid-by-pho/en.md create mode 100644 markdown/org/showcase/wahid-by-pho/es.md create mode 100644 markdown/org/showcase/wahid-by-pho/fr.md create mode 100644 markdown/org/showcase/wahid-by-pho/nl.md create mode 100644 markdown/org/showcase/wahid-jeroen/de.md create mode 100644 markdown/org/showcase/wahid-jeroen/en.md create mode 100644 markdown/org/showcase/wahid-jeroen/es.md create mode 100644 markdown/org/showcase/wahid-jeroen/fr.md create mode 100644 markdown/org/showcase/wahid-jeroen/nl.md create mode 100644 markdown/org/showcase/wahid-kaena/de.md create mode 100644 markdown/org/showcase/wahid-kaena/en.md create mode 100644 markdown/org/showcase/wahid-kaena/es.md create mode 100644 markdown/org/showcase/wahid-kaena/fr.md create mode 100644 markdown/org/showcase/wahid-kaena/nl.md create mode 100644 markdown/org/showcase/waralee-by-wouter/de.md create mode 100644 markdown/org/showcase/waralee-by-wouter/en.md create mode 100644 markdown/org/showcase/waralee-by-wouter/es.md create mode 100644 markdown/org/showcase/waralee-by-wouter/fr.md create mode 100644 markdown/org/showcase/waralee-by-wouter/nl.md create mode 100644 markdown/org/showcase/wonder-warrior-jacket/de.md create mode 100644 markdown/org/showcase/wonder-warrior-jacket/en.md create mode 100644 markdown/org/showcase/wonder-warrior-jacket/es.md create mode 100644 markdown/org/showcase/wonder-warrior-jacket/fr.md create mode 100644 markdown/org/showcase/wonder-warrior-jacket/nl.md create mode 100644 markdown/org/showcase/wonder-woman-simon/de.md create mode 100644 markdown/org/showcase/wonder-woman-simon/en.md create mode 100644 markdown/org/showcase/wonder-woman-simon/es.md create mode 100644 markdown/org/showcase/wonder-woman-simon/fr.md create mode 100644 markdown/org/showcase/wonder-woman-simon/nl.md create mode 100644 markdown/org/showcase/yellow-button-simon/de.md create mode 100644 markdown/org/showcase/yellow-button-simon/en.md create mode 100644 markdown/org/showcase/yellow-button-simon/es.md create mode 100644 markdown/org/showcase/yellow-button-simon/fr.md create mode 100644 markdown/org/showcase/yellow-button-simon/nl.md create mode 100644 markdown/org/showcase/yoga-set-by-paul/de.md create mode 100644 markdown/org/showcase/yoga-set-by-paul/en.md create mode 100644 markdown/org/showcase/yoga-set-by-paul/es.md create mode 100644 markdown/org/showcase/yoga-set-by-paul/fr.md create mode 100644 markdown/org/showcase/yoga-set-by-paul/nl.md diff --git a/markdown/org/blog/2-20-for-dolls/de.md b/markdown/org/blog/2-20-for-dolls/de.md new file mode 100644 index 00000000000..791d506b6c3 --- /dev/null +++ b/markdown/org/blog/2-20-for-dolls/de.md @@ -0,0 +1,25 @@ +--- +author: "joostdecock" +caption: "Photo by Anna Doschechko [via Pexels]" +date: "2022-01-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9c6157f73a050c291cf5441d08c3a74db6670aee-1920x1280.jpg" +intro: "FreeSewing 2.20: Would you like it smaller? [Nicht übersetzt]" +title: "FreeSewing 2.20: Would you like it smaller? [Nicht übersetzt]" +--- + +I'm happy to announce that we've released FreeSewing 2.20, which comes with a feature request that was on our roadmap: Better support for doll clothes. +We have some passionate doll enthusiasts in our community which make sense when you consider that our patterns adapt seamlessly to all sorts of measurements, including those of dolls. + +But there's another issue that comes up when generating these tiny patterns, that is that while the pattern itself adapts to the doll measurements, things like font sizes and arrows and logos do not. +That causes doll patterns to look like a chaotic mess as the things that are typically taking up just a bit of space tend to overwhelm the actual pattern: + +![Image showing a doll pattern with snippets and text obfuscating the pattern](https://posts.freesewing.org/uploads/pres_scale_de0edf2cd7.png "This is Aaron for a 1/10 size doll in 2.19. Not great") + +![Image showing a doll pattern with snippets and text scaled down](https://posts.freesewing.org/uploads/post_scale_5a422f8c73.png "This is the same Aaron in 2.20. As you can see, it's much better") + +To make this happen, we've added [a new scale setting](/docs/guide/options/scale) that you can find under *Advanced* after enabling *Expert mode*. +We hope those of you making doll clothes will find this useful, and as always [we look forward to hearing your feedback](https://discord.freesewing.org/). + +## More in this release + +2.20 also packs a bunch of changes and improvements, check the [changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md#2200-2022-01-24) for the full list. diff --git a/markdown/org/blog/2-20-for-dolls/en.md b/markdown/org/blog/2-20-for-dolls/en.md new file mode 100644 index 00000000000..045c9d175fa --- /dev/null +++ b/markdown/org/blog/2-20-for-dolls/en.md @@ -0,0 +1,25 @@ +--- +author: "joostdecock" +caption: "Photo by Anna Doschechko [via Pexels]" +date: "2022-01-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9c6157f73a050c291cf5441d08c3a74db6670aee-1920x1280.jpg" +intro: "FreeSewing 2.20: Would you like it smaller?" +title: "FreeSewing 2.20: Would you like it smaller?" +--- + +I'm happy to announce that we've released FreeSewing 2.20, which comes with a feature request that was on our roadmap: Better support for doll clothes. +We have some passionate doll enthusiasts in our community which make sense when you consider that our patterns adapt seamlessly to all sorts of measurements, including those of dolls. + +But there's another issue that comes up when generating these tiny patterns, that is that while the pattern itself adapts to the doll measurements, things like font sizes and arrows and logos do not. +That causes doll patterns to look like a chaotic mess as the things that are typically taking up just a bit of space tend to overwhelm the actual pattern: + +![Image showing a doll pattern with snippets and text obfuscating the pattern](https://posts.freesewing.org/uploads/pres_scale_de0edf2cd7.png "This is Aaron for a 1/10 size doll in 2.19. Not great") + +![Image showing a doll pattern with snippets and text scaled down](https://posts.freesewing.org/uploads/post_scale_5a422f8c73.png "This is the same Aaron in 2.20. As you can see, it's much better") + +To make this happen, we've added [a new scale setting](/docs/guide/options/scale) that you can find under *Advanced* after enabling *Expert mode*. +We hope those of you making doll clothes will find this useful, and as always [we look forward to hearing your feedback](https://discord.freesewing.org/). + +## More in this release + +2.20 also packs a bunch of changes and improvements, check the [changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md#2200-2022-01-24) for the full list. diff --git a/markdown/org/blog/2-20-for-dolls/es.md b/markdown/org/blog/2-20-for-dolls/es.md new file mode 100644 index 00000000000..4f10ffc05a5 --- /dev/null +++ b/markdown/org/blog/2-20-for-dolls/es.md @@ -0,0 +1,25 @@ +--- +author: "joostdecock" +caption: "Photo by Anna Doschechko [via Pexels]" +date: "2022-01-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9c6157f73a050c291cf5441d08c3a74db6670aee-1920x1280.jpg" +intro: "FreeSewing 2.20: Would you like it smaller? [No traducido]" +title: "FreeSewing 2.20: Would you like it smaller? [No traducido]" +--- + +I'm happy to announce that we've released FreeSewing 2.20, which comes with a feature request that was on our roadmap: Better support for doll clothes. +We have some passionate doll enthusiasts in our community which make sense when you consider that our patterns adapt seamlessly to all sorts of measurements, including those of dolls. + +But there's another issue that comes up when generating these tiny patterns, that is that while the pattern itself adapts to the doll measurements, things like font sizes and arrows and logos do not. +That causes doll patterns to look like a chaotic mess as the things that are typically taking up just a bit of space tend to overwhelm the actual pattern: + +![Image showing a doll pattern with snippets and text obfuscating the pattern](https://posts.freesewing.org/uploads/pres_scale_de0edf2cd7.png "This is Aaron for a 1/10 size doll in 2.19. Not great") + +![Image showing a doll pattern with snippets and text scaled down](https://posts.freesewing.org/uploads/post_scale_5a422f8c73.png "This is the same Aaron in 2.20. As you can see, it's much better") + +To make this happen, we've added [a new scale setting](/docs/guide/options/scale) that you can find under *Advanced* after enabling *Expert mode*. +We hope those of you making doll clothes will find this useful, and as always [we look forward to hearing your feedback](https://discord.freesewing.org/). + +## More in this release + +2.20 also packs a bunch of changes and improvements, check the [changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md#2200-2022-01-24) for the full list. diff --git a/markdown/org/blog/2-20-for-dolls/fr.md b/markdown/org/blog/2-20-for-dolls/fr.md new file mode 100644 index 00000000000..f746c961f27 --- /dev/null +++ b/markdown/org/blog/2-20-for-dolls/fr.md @@ -0,0 +1,25 @@ +--- +author: "joostdecock" +caption: "Photo by Anna Doschechko [via Pexels]" +date: "2022-01-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9c6157f73a050c291cf5441d08c3a74db6670aee-1920x1280.jpg" +intro: "FreeSewing 2.20: Would you like it smaller? [Non traduit]" +title: "FreeSewing 2.20: Would you like it smaller? [Non traduit]" +--- + +I'm happy to announce that we've released FreeSewing 2.20, which comes with a feature request that was on our roadmap: Better support for doll clothes. +We have some passionate doll enthusiasts in our community which make sense when you consider that our patterns adapt seamlessly to all sorts of measurements, including those of dolls. + +But there's another issue that comes up when generating these tiny patterns, that is that while the pattern itself adapts to the doll measurements, things like font sizes and arrows and logos do not. +That causes doll patterns to look like a chaotic mess as the things that are typically taking up just a bit of space tend to overwhelm the actual pattern: + +![Image showing a doll pattern with snippets and text obfuscating the pattern](https://posts.freesewing.org/uploads/pres_scale_de0edf2cd7.png "This is Aaron for a 1/10 size doll in 2.19. Not great") + +![Image showing a doll pattern with snippets and text scaled down](https://posts.freesewing.org/uploads/post_scale_5a422f8c73.png "This is the same Aaron in 2.20. As you can see, it's much better") + +To make this happen, we've added [a new scale setting](/docs/guide/options/scale) that you can find under *Advanced* after enabling *Expert mode*. +We hope those of you making doll clothes will find this useful, and as always [we look forward to hearing your feedback](https://discord.freesewing.org/). + +## More in this release + +2.20 also packs a bunch of changes and improvements, check the [changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md#2200-2022-01-24) for the full list. diff --git a/markdown/org/blog/2-20-for-dolls/nl.md b/markdown/org/blog/2-20-for-dolls/nl.md new file mode 100644 index 00000000000..49001f81065 --- /dev/null +++ b/markdown/org/blog/2-20-for-dolls/nl.md @@ -0,0 +1,25 @@ +--- +author: "joostdecock" +caption: "Photo by Anna Doschechko [via Pexels]" +date: "2022-01-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9c6157f73a050c291cf5441d08c3a74db6670aee-1920x1280.jpg" +intro: "FreeSewing 2.20: Would you like it smaller? [Niet vertaald]" +title: "FreeSewing 2.20: Would you like it smaller? [Niet vertaald]" +--- + +I'm happy to announce that we've released FreeSewing 2.20, which comes with a feature request that was on our roadmap: Better support for doll clothes. +We have some passionate doll enthusiasts in our community which make sense when you consider that our patterns adapt seamlessly to all sorts of measurements, including those of dolls. + +But there's another issue that comes up when generating these tiny patterns, that is that while the pattern itself adapts to the doll measurements, things like font sizes and arrows and logos do not. +That causes doll patterns to look like a chaotic mess as the things that are typically taking up just a bit of space tend to overwhelm the actual pattern: + +![Image showing a doll pattern with snippets and text obfuscating the pattern](https://posts.freesewing.org/uploads/pres_scale_de0edf2cd7.png "This is Aaron for a 1/10 size doll in 2.19. Not great") + +![Image showing a doll pattern with snippets and text scaled down](https://posts.freesewing.org/uploads/post_scale_5a422f8c73.png "This is the same Aaron in 2.20. As you can see, it's much better") + +To make this happen, we've added [a new scale setting](/docs/guide/options/scale) that you can find under *Advanced* after enabling *Expert mode*. +We hope those of you making doll clothes will find this useful, and as always [we look forward to hearing your feedback](https://discord.freesewing.org/). + +## More in this release + +2.20 also packs a bunch of changes and improvements, check the [changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md#2200-2022-01-24) for the full list. diff --git a/markdown/org/blog/2019-yearly-report/de.md b/markdown/org/blog/2019-yearly-report/de.md new file mode 100644 index 00000000000..edf5d63da38 --- /dev/null +++ b/markdown/org/blog/2019-yearly-report/de.md @@ -0,0 +1,51 @@ +--- +author: "joostdecock" +caption: "Nahaufnahme eines Löwenzahns vor rosa Hintergrund" +date: "2019-12-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/83a131ff51bec913541a94356d1930aaa2c07f87-1920x1280.jpg" +intro: "Wahnsinn! Was für ein Jahr für FreeSewing. Im August haben wir die Version 2.0 veröffentlicht, was nichts Geringeres als als ein komplettes Umschreiben unseres gesamten Technologie-Stacks bedeutet hat. Die offensichtlichste Änderung für unsere Nutzer ist, dass ihr eure Schnittmuster jetzt live im Browser angepasst sehen könnt, während ihr die Einstellungen und Optionen anpasst. Das ist eines der Dinge, von denen ich wusste, dass sie mit dem heutigen Stand der Web-Technologie möglich sein sollten, aber es tatsächlich zu sehen übersteigt irgendwie meine Vorstellungskraft." +title: "4109 Gründe, sich über 2019 zu freuen" +--- + + +Wahnsinn! Was für ein Jahr für FreeSewing. Im August haben wir die Version 2.0 veröffentlicht, was nichts Geringeres als als ein komplettes Umschreiben unseres gesamten Technologie-Stacks bedeutet hat. Die offensichtlichste Änderung für unsere Nutzer ist, dass ihr eure Schnittmuster jetzt live im Browser angepasst sehen könnt, während ihr die Einstellungen und Optionen anpasst. Das ist eines der Dinge, von denen ich wusste, dass sie mit dem heutigen Stand der Web-Technologie möglich sein sollten, aber es tatsächlich zu sehen übersteigt irgendwie meine Vorstellungskraft. + +## Skalierung ist schwierig, aber wir haben beachtenswerte Fortschritte gemacht + +So cool wie unser neuer Technologie-Stack ist, ist es nicht die wichtigste Arbeit, die wir im letzten Jahr geleistet haben. Ja, es ist ist recht ordentlich und ja, es ist nur wegen der Arbeit am 2.0 möglich. Aber es ist die Arbeit an sich, die am wichtigsten ist. Der Hauptgrund für das Umschreiben von 2.0 war es, eine vertikale Skalierung des Projekts zu ermöglichen. Oder, um es, es ganz offen auszudrücken: Um es Freesewing zu erlauben sich dorthin zu entwickeln, wo ich es nicht alleine hintragen konnte. + +In gewisser Weise ist das (Software-)Projekt FreeSewing erwachsen geworden. Wir haben mehrere Personen, die regelmäßig etwas beitragen, [einen aktiven Chat-Room](https://discord.freesewing.org/), [eine speziell für Entwickler gedachte Website und Dokumentation für Übersetzer](https://freesewing.dev), eine Vielzahl an [Paketen, die wir auf NPM veröffentlichen](https://www.npmjs.com/search?q=keywords:freesewing), wir haben an der benötigten Upstream-Software Bugfixes und Verbesserungen gemacht, und wir haben nun auch andere Personen und Teams, die auf unsere Pakete angewiesen sind. + +Wir haben (derzeit) [23 verfügbare Schnittmuster](/patterns/) und wir veröffentlichen 62 Pakete auf NPM (die Node.js Paket-Registry). Seit wir Version 2.0 veröffentlicht haben, schreiben sich pro Monat durchschnittlich 450 Leute ein und unsere Gesamtzahl zeigt aktuell über 15,000 an. + +## Übersetzen war noch nie einfacher + +Seit v2 haben wir für [unsere Übersetzungen](https://freesewing.dev/guides/translator/) auf [Crowdin](https://crowdin.com) gewechselt. Übersetzung ist wohl der beste Weg, um den Zugang zu unserer Plattform zu demokratisieren, und ich möchte mich bei allen Menschen herzlich bedanken, die bei diesen Bemühungen geholfen haben und weiterhin helfen. + +Vielleicht ist das ein guter Zeitpunkt, um euch darauf hinzuweisen, dass auch ihr mithelfen könnt. Unsere [Dokumentation für Übersetzer](https://freesewing.dev/guides/translator/) ist ein guter Startpunkt, oder schaut in [unserem Chatroom](https://discord.freesewing.org/) vorbei. + +## Was wir für das nächste Jahr vor haben + +Unsere Pläne für das nächste Jahr lassen sich grob in zwei Kategorien unterteilen: die Verbesserung unserer Plattform und das Hinzufügen weiterer Schnittmuster. + +Mit dem Wachstum des Projekts wächst auch der Arbeitsaufwand, der erforderlich ist, um alles reibungslos am Laufen zu halten. Wir müssen noch weitere Performance-Verbesserungen vornehmen und Hilfsaufgaben erledigen, wie z. B. mehr Tests schreiben, damit wir mit Zuversicht die Dinge ändern können, anstatt zu riskieren, dass die Einführung einer neuen Funktion im weiteren Verlauf Fehler verursacht. + +Wir wissen auch, dass es viel Raum für die Verbesserung der Benutzererfahrung (UX) sowie des Designs und der Benutzeroberfläche (UI) gibt. Wir haben unser Bestes getan, aber es ist nicht wirklich unser Fachgebiet, und wir hoffen, dass wir noch mehr Mitwirkende finden, die uns in dieser Hinsicht helfen können. + +## v2.2 wird einen Damen-Grundschnitt enthalten + +Aber hey, du wolltest mehr Schnittmuster, richtig? Dir sei also versichert, dass das ganz oben auf unserer Todo-Liste steht. Wir werden dem Bereich Damenschnittmuster, der bisher unterrepräsentiert war, extra Aufmerksamkeit und Ressourcen widmen. Nicht nur, indem wir ihnen bestehende Muster zur Verfügung stellen (wie wir es kürzlich mit Simone, einer Damenversion unseres Simon-Musters, getan haben), sondern auch durch die Entwicklung eines speziellen Damengrundschnittes, auf dessen Grundlage weitere Schnittmuster entwickelt werden können. + +Wir haben dies als ein Muss für FreeSewing v2.2 vorgesehen, von dem wir hoffen, dass es irgendwann im Januar veröffentlicht werden kann. + +Wir suchen auch nach Möglichkeiten, mehr Designer für FreeSewing ins Boot zu holen. Ein Plan auf dem Zeichenbrett ist es, Designern Paar-Programmiersitzungen anzubieten wo sie uns durch ihre Vision führen, und wir setzen ihren Entwurf dann in FreeSewing um. Wir denken sogar darüber nach, diese Sitzungen per Live-Streaming zu übertragen, so dass jede interessierte Person vorbeischauen und es mitverfolgen kann. + +## Es ist die Zeit des Schenkens + +Dank unserer großartigen Förderer sind die Einnahmen auch in diesem Jahr gestiegen. Wie du vielleicht weißt, spendet FreeSewing 100% der Einnahmen an Ärzte ohne Grenzen/Médecins Sans Frontières. Daher hatte ich heute Morgen die große Ehre, einen Scheck über 4109,38€ auf [MSF](https://www.msf.org/) auszustellen. + +Das fühlte sich **wirklich gut** an, also vielen Dank an [alle unsere Förderer](/patrons) für ihre anhaltende Unterstützung. Wenn du Teil dieser großartigen Gruppe von Menschen werden möchtest, [kannst du dies hier tun](/patrons/join). + + + + diff --git a/markdown/org/blog/2019-yearly-report/en.md b/markdown/org/blog/2019-yearly-report/en.md new file mode 100644 index 00000000000..3a1df06d62f --- /dev/null +++ b/markdown/org/blog/2019-yearly-report/en.md @@ -0,0 +1,91 @@ +--- +author: "joostdecock" +caption: "Close-up of a dandelion against a pink background" +date: "2019-12-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/83a131ff51bec913541a94356d1930aaa2c07f87-1920x1280.jpg" +intro: "4109 reasons to be happy about 2019" +title: "4109 reasons to be happy about 2019" +--- + + +Wow! What a year it's been for FreeSewing. +In August we released version 2.0 which was nothing less than a complete rewrite +of our entire technology stack. +For our users, the most obvious change is that you get to see your pattern adapt +live in your browser as you tweak options and preferences. +It's one of those things that I knew should be possible with the state of web +technology today, yet seeing it actually happen still boggles my mind somehow. + +## Scaling is hard, but we made remarkable progress + +Cool as our new technoglogy stack is, it is not the most important work we've done over the last +year. Yes, it's pretty neat, and yes it's only possible because of the work done +on 2.0. But that work itself is what matters most. The main reason for the 2.0 +rewrite was to allow the project to scale horizontally. Or to put it bluntly, +to allow FreeSewing to go where I could not carry it on my own. + +In a way, FreeSewing has grown up as a (software) project. We have several people +making regular contributions, [an active chat room](https://discord.freesewing.org/), +[a dedicated website for developer and translator documentation](https://freesewing.dev), +a plethora of [packages we publish on NPM](https://www.npmjs.com/search?q=keywords:freesewing), +we've contributed fixes and improvements to upstream software we depend on, and we now +also have other people and teams who depend on the packages we put out. + +We (currently) have [23 patterns available](/patterns/), we publish 62 packages on NPM +(the Node.js package registry). Since putting out version 2.0, on average 450 people +sign up every month, and our total tally currently stands above 15.000. + +## Translation has never been easier + +Since v2, we've also switched to [Crowdin](https://crowdin.com) for +[our translations](https://freesewing.dev/guides/translator/). Translation is arguably +the best way to democratize access to our platform, and I'd like to give a shout-out to +all people who have helped and continue to help with these efforts. + +It's perhaps also a good time to point out that you too can help with this. +Our [documentation for translators](https://freesewing.dev/guides/translator/) is a good +place to get started, or stop by [our chat room](https://discord.freesewing.org/). + +## What we're planning for next year + +Our next year plans roughly fall apart into two categories: +improving our platform, and adding more patterns. + +As the project grows, so does the amount of work required to keep everything +running smoothly. We still have more performance improvements to do, as well as +auxiliary tasks such as writing more tests so we can go ahead and change things with +confidence, rather than risk that rolling out a new feature causes bugs down the line. + +We also know there is a lot of room for improvement of the user experience (UX), as +well as design and user interface (UI). We've been doing the best we can, but it's +not really our field of expertise, and we're hoping to find more contributors who can +help us in this regard. + +## v2.2 will include a ladies bodice block + +But hey, you want more patterns, right? So rest assured that that's high on our +todo list. We are going to apply some affirmative action towards the ladies who have +so far been under-served. Not only by making existing patterns available to them +(as we did recently with Simone, a ladies version of our Simon pattern) but also +by developing a dedicated ladies block to develop patterns on. + +We have earmarked this as a must-have for FreeSewing v2.2, which we hope to be able +to release sometime in January. + +We're also looking at ways to get more designers on board with FreeSewing. +One plan on the drawing board is to offer pair-programming sessions to designers +where they walk us through their vision, and we implement their design in FreeSewing. +We're even thinking of live-streaming these sessions so anybody who is interested +can drop by and follow along. + +## 'Tis the season for giving + +Thanks to our awesome patrons, revenue was up this year too. As you may or may not know, +FreeSewing donates 100% of its revenue to Médecins Sans Frontières/Doctors Without Borders. +So this morning, I had the great honour to write a 4109.38€ cheque to [MSF](https://www.msf.org/). + +That felt **real good** so thanks to [all our patrons](/patrons) for their continued support. +If you'd like to join this awesome group of people, [you can do so here](/patrons/join). + + + diff --git a/markdown/org/blog/2019-yearly-report/es.md b/markdown/org/blog/2019-yearly-report/es.md new file mode 100644 index 00000000000..2f8d14a4651 --- /dev/null +++ b/markdown/org/blog/2019-yearly-report/es.md @@ -0,0 +1,91 @@ +--- +author: "joostdecock" +caption: "Close-up of a dandelion against a pink background" +date: "2019-12-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/83a131ff51bec913541a94356d1930aaa2c07f87-1920x1280.jpg" +intro: "4109 reasons to be happy about 2019 [No traducido]" +title: "4109 reasons to be happy about 2019 [No traducido]" +--- + + +Wow! What a year it's been for FreeSewing. +In August we released version 2.0 which was nothing less than a complete rewrite +of our entire technology stack. +For our users, the most obvious change is that you get to see your pattern adapt +live in your browser as you tweak options and preferences. +It's one of those things that I knew should be possible with the state of web +technology today, yet seeing it actually happen still boggles my mind somehow. + +## Scaling is hard, but we made remarkable progress + +Cool as our new technoglogy stack is, it is not the most important work we've done over the last +year. Yes, it's pretty neat, and yes it's only possible because of the work done +on 2.0. But that work itself is what matters most. The main reason for the 2.0 +rewrite was to allow the project to scale horizontally. Or to put it bluntly, +to allow FreeSewing to go where I could not carry it on my own. + +In a way, FreeSewing has grown up as a (software) project. We have several people +making regular contributions, [an active chat room](https://discord.freesewing.org/), +[a dedicated website for developer and translator documentation](https://freesewing.dev), +a plethora of [packages we publish on NPM](https://www.npmjs.com/search?q=keywords:freesewing), +we've contributed fixes and improvements to upstream software we depend on, and we now +also have other people and teams who depend on the packages we put out. + +We (currently) have [23 patterns available](/patterns/), we publish 62 packages on NPM +(the Node.js package registry). Since putting out version 2.0, on average 450 people +sign up every month, and our total tally currently stands above 15.000. + +## Translation has never been easier + +Since v2, we've also switched to [Crowdin](https://crowdin.com) for +[our translations](https://freesewing.dev/guides/translator/). Translation is arguably +the best way to democratize access to our platform, and I'd like to give a shout-out to +all people who have helped and continue to help with these efforts. + +It's perhaps also a good time to point out that you too can help with this. +Our [documentation for translators](https://freesewing.dev/guides/translator/) is a good +place to get started, or stop by [our chat room](https://discord.freesewing.org/). + +## What we're planning for next year + +Our next year plans roughly fall apart into two categories: +improving our platform, and adding more patterns. + +As the project grows, so does the amount of work required to keep everything +running smoothly. We still have more performance improvements to do, as well as +auxiliary tasks such as writing more tests so we can go ahead and change things with +confidence, rather than risk that rolling out a new feature causes bugs down the line. + +We also know there is a lot of room for improvement of the user experience (UX), as +well as design and user interface (UI). We've been doing the best we can, but it's +not really our field of expertise, and we're hoping to find more contributors who can +help us in this regard. + +## v2.2 will include a ladies bodice block + +But hey, you want more patterns, right? So rest assured that that's high on our +todo list. We are going to apply some affirmative action towards the ladies who have +so far been under-served. Not only by making existing patterns available to them +(as we did recently with Simone, a ladies version of our Simon pattern) but also +by developing a dedicated ladies block to develop patterns on. + +We have earmarked this as a must-have for FreeSewing v2.2, which we hope to be able +to release sometime in January. + +We're also looking at ways to get more designers on board with FreeSewing. +One plan on the drawing board is to offer pair-programming sessions to designers +where they walk us through their vision, and we implement their design in FreeSewing. +We're even thinking of live-streaming these sessions so anybody who is interested +can drop by and follow along. + +## 'Tis the season for giving + +Thanks to our awesome patrons, revenue was up this year too. As you may or may not know, +FreeSewing donates 100% of its revenue to Médecins Sans Frontières/Doctors Without Borders. +So this morning, I had the great honour to write a 4109.38€ cheque to [MSF](https://www.msf.org/). + +That felt **real good** so thanks to [all our patrons](/patrons) for their continued support. +If you'd like to join this awesome group of people, [you can do so here](/patrons/join). + + + diff --git a/markdown/org/blog/2019-yearly-report/fr.md b/markdown/org/blog/2019-yearly-report/fr.md new file mode 100644 index 00000000000..851a3c07713 --- /dev/null +++ b/markdown/org/blog/2019-yearly-report/fr.md @@ -0,0 +1,51 @@ +--- +author: "joostdecock" +caption: "Gros plan d'un pissenlit sur fond rose" +date: "2019-12-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/83a131ff51bec913541a94356d1930aaa2c07f87-1920x1280.jpg" +intro: "Whaou ! Quelle année pour FreeSewing. En août, nous avons publié la version 2.0 qui n'était rien de moins qu'une réécriture complète de notre infrastructure technologique. Pour nos utilisateurs, le changement le plus important est la possibilité de visualiser en direct le patron lorsque vous modifiez les options et les préférences. C'est une chose que je savais possible avec la technologie web d'aujourd'hui, mais la voir fonctionner réellement me stupéfie encore toujours un peu." +title: "4109 raisons d'être contents de 2019" +--- + + +Whaou ! Quelle année pour FreeSewing. En août, nous avons publié la version 2.0 qui n'était rien de moins qu'une réécriture complète de notre infrastructure technologique. Pour nos utilisateurs, le changement le plus important est la possibilité de visualiser en direct le patron lorsque vous modifiez les options et les préférences. C'est une chose que je savais possible avec la technologie web d'aujourd'hui, mais la voir fonctionner réellement me stupéfie encore toujours un peu. + +## La mise à l'échelle est difficile, mais nous avons fait des progrès remarquables + +Aussi cool que soit notre nouvelle infrastructure, ce n'est pas le travail le plus important que nous ayons fait cette année. Oui, c'est plutôt sympa, et oui c'est possible uniquement grâce au travail effectué en 2.0. But that work itself is what matters most. Mais la raison principale de la réécriture de la version 2.0 était de permettre au projet de s'étendre horizontalement. Autrement dit, pour permettre à FreeSewing d'aller là où je ne pouvais pas le porter seul. + +D'une certaine manière, FreeSewing a grandi en tant que projet (logiciel). We have several people making regular contributions, [an active chat room](https://discord.freesewing.org/), [a dedicated website for developer and translator documentation](https://freesewing.dev), a plethora of [packages we publish on NPM](https://www.npmjs.com/search?q=keywords:freesewing), we've contributed fixes and improvements to upstream software we depend on, and we now also have other people and teams who depend on the packages we put out. + +Nous avons actuellement [23 patrons disponibles](/patterns/), nous avons publié 62 packages sur NPM (le registre de packages Node.js). Depuis la sortie de la version 2.0, en moyenne 450 personnes s'inscrivent chaque mois, et nous avons eu au total plus de 15.000 visiteurs. + +## La traduction n'a jamais été aussi facile + +Depuis la v2, nous sommes également passés à [Crowdin](https://crowdin.com) pour [nos traductions](https://freesewing.dev/guides/translator/). La traduction est sans doute le meilleur moyen de démocratiser l'accès à notre site, et je voudrais crier un grand merci à tous ceux qui ont aidé et continuent à aider. + +C'est d'ailleurs peut-être aussi le bon moment pour signaler que vous aussi, vous pouvez aider. Our [documentation for translators](https://freesewing.dev/guides/translator/) is a good place to get started, or stop by [our chat room](https://discord.freesewing.org/). + +## Ce qui est prévu l'an prochain + +Nos projets pour l'an prochain se divisent à peu près en deux catégories : améliorer notre site et ajouter plus de patrons. + +Au fur et à mesure que le projet grandit, la quantité de travail nécessaire pour que tout fonctionne bien grandit aussi. Nous devons améliorer encore les performances, et faire plus de tâches auxiliaires comme écrire des tests pour aller de l'avant sereinement, plutôt que de déployer une nouvelle fonctionnalité qui provoque des bugs. + +Nous savons aussi qu'il y a matière à améliorer l'expérience utilisateur (UX), ainsi que le design et l'interface utilisateur (UI). Nous avons fait le mieux possible, mais ce n'est pas vraiment notre domaine d'expertise, et nous espérons trouver plus de contributeurs qui pourraient nous aider dans ce domaine. + +## La v2.2 comprendra un patron de base de corsage femme + +Mais bon, vous voulez plus de patrons, non ? Soyez assurés que c'est en haut de notre liste de tâches . Nous allons réaliser faire des choses en faveur des dames qui, jusqu'à présent, ont été un peu oubliées. Non seulement en adaptant pour elles des patrons existants (comme récemment avec Simone, version femme de notre modèle Simon) mais aussi en développant un patron de base femme. + +Ce sera un incontournable de FreeSewing v2.2, que nous espérons pouvoir diffuser en janvier. + +Nous cherchons également à embarquer plus de designers à bord de FreeSewing. Un projet est d'offrir aux designers des sessions de programmation en binôme, où ils partageraient avec nous leur vision, que nous implémenterions dans FreeSewing. Nous pensons même diffuser ces sessions en direct afin que toute personne intéressée puisse les suivre. + +## C'est le temps des dons + +Grâce à nos forrmidables mécènes, les revenus ont encore augmenté cette année. Comme vous le savez peut-être, FreeSewing fait don de 100 % de ses revenus à Medecins Sans Frontières/Doctors Sans Frontières. Donc, ce matin, j'ai eu le grand honneur de faire un chèque de 4109,38€ à [MSF](https://www.msf.org/). + +Cela fait **vraiment du bien** alors merci à tous nos mécènes pour leur soutien continu. Si vous souhaitez rejoindre ce groupe génial, [vous pouvez le faire ici](/patrons/join). + + + + diff --git a/markdown/org/blog/2019-yearly-report/nl.md b/markdown/org/blog/2019-yearly-report/nl.md new file mode 100644 index 00000000000..5e8e6a4bfc2 --- /dev/null +++ b/markdown/org/blog/2019-yearly-report/nl.md @@ -0,0 +1,51 @@ +--- +author: "joostdecock" +caption: "Close-up van een paardebloem op een roze achtergrond" +date: "2019-12-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/83a131ff51bec913541a94356d1930aaa2c07f87-1920x1280.jpg" +intro: "Wow! Wat een jaar voor FreeSewing. In augustus hebben we versie 2.0 gelanceerd, en dat was niet minder dan een complete herwerking van onze hele technology stack. De meest opvallende verandering voor onze gebruikers is dat je het patroon live ziet veranderen in je browser wanneer je opties en voorkeuren aanpast. Het is een van die dingen waarvan ik wist dat ze mogelijk moesten zijn met de webtechnologie van vandaag. Maar het zien gebeuren is op de één of andere manier nog altijd ongelooflijk voor mij." +title: "4109 redenen om tevreden te zijn met 2019" +--- + + +Wow! Wat een jaar voor FreeSewing. In augustus hebben we versie 2.0 gelanceerd, en dat was niet minder dan een complete herwerking van onze hele technology stack. De meest opvallende verandering voor onze gebruikers is dat je het patroon live ziet veranderen in je browser wanneer je opties en voorkeuren aanpast. Het is een van die dingen waarvan ik wist dat ze mogelijk moesten zijn met de webtechnologie van vandaag. Maar het zien gebeuren is op de één of andere manier nog altijd ongelooflijk voor mij. + +## Schalen is moeilijk, maar we hebben mooie vooruitgang geboekt + +Hoe cool onze nieuwe technology stack ook is, het is niet het belangrijkste dat we in het afgelopen jaar hebben gedaan. Ja, het is best netjes, en ja, het zou niet mogelijk geweest zijn zonder al het werk aan versie 2.0. Maar het is juist dat werk dat er het meeste toe doet. De belangrijkste reden voor het herschrijven voor versie 2.0, is dat we ons project horizontaal willen schalen. Of, simpel gezegd, om FreeSewing te laten voortgaan voorbij wat ik zelf kon dragen. + +In zekere zin is FreeSewing volwassen geworden als (software)project. We have several people making regular contributions, [an active chat room](https://discord.freesewing.org/), [a dedicated website for developer and translator documentation](https://freesewing.dev), a plethora of [packages we publish on NPM](https://www.npmjs.com/search?q=keywords:freesewing), we've contributed fixes and improvements to upstream software we depend on, and we now also have other people and teams who depend on the packages we put out. + +We stellen (op dit moment) [23 patronen ter beschikking](/patterns/) en hebben 26 packages op NPM (het Node.js package-register). Sinds we versie 2.0 uitgebracht hebben, worden gemiddeld 450 mensen per maand lid. De teller staat nu op meer dan 15.000. + +## Vertaling is nog nooit zo gemakkelijk geweest + +Sinds v2 zijn we ook overgeschakeld op [Crowdin](https://crowdin.com) voor [onze vertalingen](https://freesewing.dev/guides/translator/). Vertaling is misschien wel de beste manier om toegang tot ons platform te democratiseren. Ik wil graag de mensen erkennen die hebben geholpen en blijven helpen bij deze inspanningen. + +Dit is misschien een goed moment om te vermelden dat jij hier ook bij kan helpen. Our [documentation for translators](https://freesewing.dev/guides/translator/) is a good place to get started, or stop by [our chat room](https://discord.freesewing.org/). + +## Wat we van plan zijn voor volgend jaar + +Onze plannen voor volgend jaar horen ruwweg thuis in twee categorieën: ons platform verbeteren en meer patronen toevoegen. + +Hoe groter het project wordt, hoe meer werk er ook bij komt kijken om alles vlot te laten draaien. We hebben nog heel wat prestatieverbeteringen te doen, net als allerlei bijkomende taken. Tests uitschrijven bijvoorbeeld, zodat we met meer zekerheid veranderingen kunnen implementeren in plaats van nieuwe functies uit te rollen waar later bugs in blijken te zitten. + +We weten ook dat er nog veel ruimte voor verbetering is in de user experience (UX), het design en de user interface (UI). We doen ons best, maar het is nu eenmaal niet echt onze expertise. We hopen dat we nog helpende handen kunnen vinden op dat vlak. + +## In v2.2 zit een damescorsage + +Maar hé, jij wil gewoon meer patronen, toch? Wees gerust: dat staat bovenaan ons lijstje. We gaan wat positieve discriminatie toepassen, want de dames zijn tot nu toe op hun honger blijven zitten. We gaan niet alleen bestaande patronen beschikbaar maken voor dames (zoals we onlangs gedaan hebben met Simone, een damesversie van ons Simonpatroon) maar ook een basiscorsage ontwikkelen waarop we straks kunnen voortbouwen met meer damespatronen. + +We hebben dit aangevinkt als een must-have voor FreeSewing v2.2, dat we hopelijk ergens in januari kunnen lanceren. + +We zijn ook op zoek naar manieren om meer ontwerpers te betrekken bij FreeSewing. Een van de plannen die op tafel liggen, is om in duoprogrammering te werken met ontwerpers. Zij leggen ons hun visie uit tot in de details, en wij zetten hun design om in een FreeSewing-patroon. We overwegen zelfs om die sessies live te streamen. Zo kan iedereen die interesse heeft, meekijken en -volgen. + +## Het is cadeautjesseizoen + +Met dank aan onze fantastische patrons, zijn ook onze inkomsten dit jaar toegenomen. Zoals je weet – of niet weet – doneert FreeSewing 100% van alle inkomsten aan Artsen Zonder Grenzen/Médecins Sans Frontières. Vanmorgen heb ik dus de eer gehad om een cheque van 4109,38 euro uit te schrijven aan [MSF](https://www.msf.org/). + +Dat voelde **fantastisch**. Dus dank je wel aan [al onze patrons](/patrons) voor hun voortdurende steun. Als je graag deel zou uitmaken van deze groep van topmensen, [dan kan dat hier](/patrons/join). + + + + diff --git a/markdown/org/blog/2021-wrapup/de.md b/markdown/org/blog/2021-wrapup/de.md new file mode 100644 index 00000000000..1d317a97aae --- /dev/null +++ b/markdown/org/blog/2021-wrapup/de.md @@ -0,0 +1,51 @@ +--- +author: "joostdecock" +caption: "Picture by Snapwire - Via pexels.com" +date: "2022-01-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/33d380890b215e6fc9c698b57469fdd0c24acc44-3072x2304.jpg" +intro: "I'm not going to do a whole blog post about 2021 stuff because I feel like most of us just sorta want to move on and forget about it, but if you were looking for a longer read, then here's the table of content of our latest newsletter edition that also went out today:" +title: "2021 wrap-up: A new FreeSewing.dev and announcing our bug bounty program [Nicht übersetzt]" +--- + + + +I'm not going to do a whole blog post about 2021 stuff because I feel like most of us just sorta want to move on and forget about it, but if you were looking for a longer read, then here's the table of content of [our latest newsletter edition](/newsletter/2022q1/) that also went out today: + +- 🎉 2021 is salted and burned +- 🧐 What our contributors have been up to in 2021 +- 🎖️ FreeSewing is now an 'all contributors' project +- 🚧 Why version 3 has been put on hold +- 🤓 What I've been up to in 2021 +- 🐛 FreeSewing's bug bounty program +- ⛑️ Yearly revenue and where it went (spoiler: same as always) +- 🤞 What I hope will happen this year + +Here, I'd like to cherry-pick just those things that I think are exciting right now. + +## freesewing.dev has been rebuilt + +[The effort I started in the summer](https://freesewing.dev/blog/project-2022) came to fruition on the last day of the year as I deployed the new [freesewing.dev](https://freesewing.dev/blog/project-2022) site in production. + +It's a complete redesign, and the code is now [hosted in our monorepo](https://github.com/freesewing/freesewing), which means that [our dedicated repository for freesewing.dev](https://github.com/freesewing/freesewing.dev) has now been archived. + +This effort implemented a bunch of items from [our v3 roadmap](https://github.com/freesewing/freesewing/discussions/1278) which has sort of grown into this long list of ideas/plans. From the top of my head: + +- Migrate to NextJS +- Better open graph support +- Migrate style to TailwindCSS +- Migrate blog posts and showcase posts to Strapi +- Migrate newsletter to Strapi +- Move markdown content into monorepo & merge Crowdin translation projects +- Add endpoint to backend for auto-generated open graph images + +Have all been implemented as a direct result or side effect of this effort. + +This site will also become the blueprint for an overhaul of freesewing.org, something that's on the planning for this year. + +## FreeSewing's bug bounty program + +Once again, [read our newsletter](/newsletter/2022q1/) for the entire backstory, but here's the gist of it: We are now launching the FreeSewing bug bounty program: + +> If you find a bug in one of our patterns, or in our core library, we will (with your permission) add you to our list of contributors, and send you a little something to say thanks. + +So keep your eyes peeled, and if something seems off, [let us know about it](https://discord.freesewing.org/) and we'll send you some goodies diff --git a/markdown/org/blog/2021-wrapup/en.md b/markdown/org/blog/2021-wrapup/en.md new file mode 100644 index 00000000000..0e48734deab --- /dev/null +++ b/markdown/org/blog/2021-wrapup/en.md @@ -0,0 +1,51 @@ +--- +author: "joostdecock" +caption: "Picture by Snapwire - Via pexels.com" +date: "2022-01-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/33d380890b215e6fc9c698b57469fdd0c24acc44-3072x2304.jpg" +intro: "I'm not going to do a whole blog post about 2021 stuff because I feel like most of us just sorta want to move on and forget about it, but if you were looking for a longer read, then here's the table of content of our latest newsletter edition that also went out today:" +title: "2021 wrap-up: A new FreeSewing.dev and announcing our bug bounty program" +--- + + + +I'm not going to do a whole blog post about 2021 stuff because I feel like most of us just sorta want to move on and forget about it, but if you were looking for a longer read, then here's the table of content of [our latest newsletter edition](/newsletter/2022q1/) that also went out today: + +- 🎉 2021 is salted and burned +- 🧐 What our contributors have been up to in 2021 +- 🎖️ FreeSewing is now an 'all contributors' project +- 🚧 Why version 3 has been put on hold +- 🤓 What I've been up to in 2021 +- 🐛 FreeSewing's bug bounty program +- ⛑️ Yearly revenue and where it went (spoiler: same as always) +- 🤞 What I hope will happen this year + +Here, I'd like to cherry-pick just those things that I think are exciting right now. + +## freesewing.dev has been rebuilt + +[The effort I started in the summer](https://freesewing.dev/blog/project-2022) came to fruition on the last day of the year as I deployed the new [freesewing.dev](https://freesewing.dev/blog/project-2022) site in production. + +It's a complete redesign, and the code is now [hosted in our monorepo](https://github.com/freesewing/freesewing), which means that [our dedicated repository for freesewing.dev](https://github.com/freesewing/freesewing.dev) has now been archived. + +This effort implemented a bunch of items from [our v3 roadmap](https://github.com/freesewing/freesewing/discussions/1278) which has sort of grown into this long list of ideas/plans. From the top of my head: + +- Migrate to NextJS +- Better open graph support +- Migrate style to TailwindCSS +- Migrate blog posts and showcase posts to Strapi +- Migrate newsletter to Strapi +- Move markdown content into monorepo & merge Crowdin translation projects +- Add endpoint to backend for auto-generated open graph images + +Have all been implemented as a direct result or side effect of this effort. + +This site will also become the blueprint for an overhaul of freesewing.org, something that's on the planning for this year. + +## FreeSewing's bug bounty program + +Once again, [read our newsletter](/newsletter/2022q1/) for the entire backstory, but here's the gist of it: We are now launching the FreeSewing bug bounty program: + +> If you find a bug in one of our patterns, or in our core library, we will (with your permission) add you to our list of contributors, and send you a little something to say thanks. + +So keep your eyes peeled, and if something seems off, [let us know about it](https://discord.freesewing.org/) and we'll send you some goodies diff --git a/markdown/org/blog/2021-wrapup/es.md b/markdown/org/blog/2021-wrapup/es.md new file mode 100644 index 00000000000..f1f262fe3ea --- /dev/null +++ b/markdown/org/blog/2021-wrapup/es.md @@ -0,0 +1,51 @@ +--- +author: "joostdecock" +caption: "Picture by Snapwire - Via pexels.com" +date: "2022-01-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/33d380890b215e6fc9c698b57469fdd0c24acc44-3072x2304.jpg" +intro: "I'm not going to do a whole blog post about 2021 stuff because I feel like most of us just sorta want to move on and forget about it, but if you were looking for a longer read, then here's the table of content of our latest newsletter edition that also went out today:" +title: "2021 wrap-up: A new FreeSewing.dev and announcing our bug bounty program [No traducido]" +--- + + + +I'm not going to do a whole blog post about 2021 stuff because I feel like most of us just sorta want to move on and forget about it, but if you were looking for a longer read, then here's the table of content of [our latest newsletter edition](/newsletter/2022q1/) that also went out today: + +- 🎉 2021 is salted and burned +- 🧐 What our contributors have been up to in 2021 +- 🎖️ FreeSewing is now an 'all contributors' project +- 🚧 Why version 3 has been put on hold +- 🤓 What I've been up to in 2021 +- 🐛 FreeSewing's bug bounty program +- ⛑️ Yearly revenue and where it went (spoiler: same as always) +- 🤞 What I hope will happen this year + +Here, I'd like to cherry-pick just those things that I think are exciting right now. + +## freesewing.dev has been rebuilt + +[The effort I started in the summer](https://freesewing.dev/blog/project-2022) came to fruition on the last day of the year as I deployed the new [freesewing.dev](https://freesewing.dev/blog/project-2022) site in production. + +It's a complete redesign, and the code is now [hosted in our monorepo](https://github.com/freesewing/freesewing), which means that [our dedicated repository for freesewing.dev](https://github.com/freesewing/freesewing.dev) has now been archived. + +This effort implemented a bunch of items from [our v3 roadmap](https://github.com/freesewing/freesewing/discussions/1278) which has sort of grown into this long list of ideas/plans. From the top of my head: + +- Migrate to NextJS +- Better open graph support +- Migrate style to TailwindCSS +- Migrate blog posts and showcase posts to Strapi +- Migrate newsletter to Strapi +- Move markdown content into monorepo & merge Crowdin translation projects +- Add endpoint to backend for auto-generated open graph images + +Have all been implemented as a direct result or side effect of this effort. + +This site will also become the blueprint for an overhaul of freesewing.org, something that's on the planning for this year. + +## FreeSewing's bug bounty program + +Once again, [read our newsletter](/newsletter/2022q1/) for the entire backstory, but here's the gist of it: We are now launching the FreeSewing bug bounty program: + +> If you find a bug in one of our patterns, or in our core library, we will (with your permission) add you to our list of contributors, and send you a little something to say thanks. + +So keep your eyes peeled, and if something seems off, [let us know about it](https://discord.freesewing.org/) and we'll send you some goodies diff --git a/markdown/org/blog/2021-wrapup/fr.md b/markdown/org/blog/2021-wrapup/fr.md new file mode 100644 index 00000000000..57eb1596f8c --- /dev/null +++ b/markdown/org/blog/2021-wrapup/fr.md @@ -0,0 +1,51 @@ +--- +author: "joostdecock" +caption: "Picture by Snapwire - Via pexels.com" +date: "2022-01-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/33d380890b215e6fc9c698b57469fdd0c24acc44-3072x2304.jpg" +intro: "I'm not going to do a whole blog post about 2021 stuff because I feel like most of us just sorta want to move on and forget about it, but if you were looking for a longer read, then here's the table of content of our latest newsletter edition that also went out today:" +title: "2021 wrap-up: A new FreeSewing.dev and announcing our bug bounty program [Non traduit]" +--- + + + +I'm not going to do a whole blog post about 2021 stuff because I feel like most of us just sorta want to move on and forget about it, but if you were looking for a longer read, then here's the table of content of [our latest newsletter edition](/newsletter/2022q1/) that also went out today: + +- 🎉 2021 is salted and burned +- 🧐 What our contributors have been up to in 2021 +- 🎖️ FreeSewing is now an 'all contributors' project +- 🚧 Why version 3 has been put on hold +- 🤓 What I've been up to in 2021 +- 🐛 FreeSewing's bug bounty program +- ⛑️ Yearly revenue and where it went (spoiler: same as always) +- 🤞 What I hope will happen this year + +Here, I'd like to cherry-pick just those things that I think are exciting right now. + +## freesewing.dev has been rebuilt + +[The effort I started in the summer](https://freesewing.dev/blog/project-2022) came to fruition on the last day of the year as I deployed the new [freesewing.dev](https://freesewing.dev/blog/project-2022) site in production. + +It's a complete redesign, and the code is now [hosted in our monorepo](https://github.com/freesewing/freesewing), which means that [our dedicated repository for freesewing.dev](https://github.com/freesewing/freesewing.dev) has now been archived. + +This effort implemented a bunch of items from [our v3 roadmap](https://github.com/freesewing/freesewing/discussions/1278) which has sort of grown into this long list of ideas/plans. From the top of my head: + +- Migrate to NextJS +- Better open graph support +- Migrate style to TailwindCSS +- Migrate blog posts and showcase posts to Strapi +- Migrate newsletter to Strapi +- Move markdown content into monorepo & merge Crowdin translation projects +- Add endpoint to backend for auto-generated open graph images + +Have all been implemented as a direct result or side effect of this effort. + +This site will also become the blueprint for an overhaul of freesewing.org, something that's on the planning for this year. + +## FreeSewing's bug bounty program + +Once again, [read our newsletter](/newsletter/2022q1/) for the entire backstory, but here's the gist of it: We are now launching the FreeSewing bug bounty program: + +> If you find a bug in one of our patterns, or in our core library, we will (with your permission) add you to our list of contributors, and send you a little something to say thanks. + +So keep your eyes peeled, and if something seems off, [let us know about it](https://discord.freesewing.org/) and we'll send you some goodies diff --git a/markdown/org/blog/2021-wrapup/nl.md b/markdown/org/blog/2021-wrapup/nl.md new file mode 100644 index 00000000000..5413fd08181 --- /dev/null +++ b/markdown/org/blog/2021-wrapup/nl.md @@ -0,0 +1,51 @@ +--- +author: "joostdecock" +caption: "Picture by Snapwire - Via pexels.com" +date: "2022-01-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/33d380890b215e6fc9c698b57469fdd0c24acc44-3072x2304.jpg" +intro: "I'm not going to do a whole blog post about 2021 stuff because I feel like most of us just sorta want to move on and forget about it, but if you were looking for a longer read, then here's the table of content of our latest newsletter edition that also went out today:" +title: "2021 wrap-up: A new FreeSewing.dev and announcing our bug bounty program [Niet vertaald]" +--- + + + +I'm not going to do a whole blog post about 2021 stuff because I feel like most of us just sorta want to move on and forget about it, but if you were looking for a longer read, then here's the table of content of [our latest newsletter edition](/newsletter/2022q1/) that also went out today: + +- 🎉 2021 is salted and burned +- 🧐 What our contributors have been up to in 2021 +- 🎖️ FreeSewing is now an 'all contributors' project +- 🚧 Why version 3 has been put on hold +- 🤓 What I've been up to in 2021 +- 🐛 FreeSewing's bug bounty program +- ⛑️ Yearly revenue and where it went (spoiler: same as always) +- 🤞 What I hope will happen this year + +Here, I'd like to cherry-pick just those things that I think are exciting right now. + +## freesewing.dev has been rebuilt + +[The effort I started in the summer](https://freesewing.dev/blog/project-2022) came to fruition on the last day of the year as I deployed the new [freesewing.dev](https://freesewing.dev/blog/project-2022) site in production. + +It's a complete redesign, and the code is now [hosted in our monorepo](https://github.com/freesewing/freesewing), which means that [our dedicated repository for freesewing.dev](https://github.com/freesewing/freesewing.dev) has now been archived. + +This effort implemented a bunch of items from [our v3 roadmap](https://github.com/freesewing/freesewing/discussions/1278) which has sort of grown into this long list of ideas/plans. From the top of my head: + +- Migrate to NextJS +- Better open graph support +- Migrate style to TailwindCSS +- Migrate blog posts and showcase posts to Strapi +- Migrate newsletter to Strapi +- Move markdown content into monorepo & merge Crowdin translation projects +- Add endpoint to backend for auto-generated open graph images + +Have all been implemented as a direct result or side effect of this effort. + +This site will also become the blueprint for an overhaul of freesewing.org, something that's on the planning for this year. + +## FreeSewing's bug bounty program + +Once again, [read our newsletter](/newsletter/2022q1/) for the entire backstory, but here's the gist of it: We are now launching the FreeSewing bug bounty program: + +> If you find a bug in one of our patterns, or in our core library, we will (with your permission) add you to our list of contributors, and send you a little something to say thanks. + +So keep your eyes peeled, and if something seems off, [let us know about it](https://discord.freesewing.org/) and we'll send you some goodies diff --git a/markdown/org/blog/a-call-for-help/de.md b/markdown/org/blog/a-call-for-help/de.md new file mode 100644 index 00000000000..2df419a1614 --- /dev/null +++ b/markdown/org/blog/a-call-for-help/de.md @@ -0,0 +1,167 @@ +--- +author: "joostdecock" +caption: "Anmerkung: Dieser Beitrag ist etwas lang. Aber auf keinen Fall so lang wie dieses Buch" +date: "2020-08-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1a143c96b4afc8c12d2014c5605bfd1e63d917d0-2000x1348.jpg" +intro: "Hallo zusammen, Joost hier. Ich schreibe diesen Beitrag, um einige Probleme anzugehen, die mich in letzter Zeit beunruhigt haben. Um genau zu sein, diese Probleme:" +title: "Bitte helft mit dabei, FreeSewing über das hinauswachsen zu lassen, was ich alleine tun kann" +--- + + +Hallo zusammen, Joost hier. Ich schreibe diesen Beitrag, um einige Probleme anzugehen, die mich in letzter Zeit beunruhigt haben. Um genau zu sein, diese Probleme: + + 1. [Es gibt zu viel zu tun für eine Person](#problem-1-there-is-too-much-work-for-one-person) + 2. [Ich habe das Gefühl, dass ich die Verbindung zu der Näh-Community verliere](#problem-2-i-feel-im-losing-track-of-the-community) + 3. [Ich bin unsicher, wie ich mit dem Problem des institutionellen Rassismus umgehen soll](#problem-3-i-feel-insecure-about-how-to-deal-with-the-issue-of-systemic-racism) + +Die gute Nachricht ist, dass es eine relativ kurze Liste ist. Die noch bessere Nachricht ist, dass alle diese Probleme mit der gleichen Lösung gelöst werden: [Community Building/Gemeinschaftsbildung](#community-building). + +Bevor wir darauf eingehen, schauen wir uns kurz jedes Problem an: + +## Problem 1: Es gibt zu viel zu tun für eine Person + +Im Laufe der letzten Woche habe ich [Working in public: The making and maintenance of open source software](https://www.amazon.com/dp/0578675862/) von [Nadia Eghbal](https://nadiaeghbal.com/) gelesen. + +Ich kaufte es, weil ich hoffte, Antworten auf einige der Fragen zu finden, die ich mir stelle. Fragen wie „*Wie machen andere Maintainer das?*“, oder “*Mache ich es falsch?*” + +Mit anderen Worten: Ich hatte gehofft, eine Lösung für etwas zu finden, das ich zunehmend als Problem betrachte: Die Unfähigkeit, meine eigene Arbeit so zu skalieren, wie ich das Projekt FreeSewing skalieren möchte. + +Ich will das Buch nicht spoilern, aber es gab keine einfachen Antworten darauf, wie dieses Problem angegangen werden sollte. Wie sich herausstellt, ist die große Mehrheit der Open-Source-Maintainer im selben Boot. Die meisten Projekte werden entweder von einer Person oder von einer Handvoll Personen betrieben. + +Das an sich ist kein Problem. Aber es legt eine feste Obergrenze fest, wie viel Projekte wie FreeSewing erreichen können. + +## Problem 2: Ich habe das Gefühl, dass ich die Verbindung zu der Näh-Community verliere + +Ich mache mir Sorgen, dass ich die Gemeinschaftsaspekte von FreeSewing vernachlässigt habe, es gibt keine Kommentare oder *soziale* Aspekte auf der Website. Ich hatte immer das Gefühl, dass es vergebliche Liebesmüh ist, Leute auf der eigenen Website einzusperren. Es ist besser, sie auf den Plattformen ihrer Wahl diskutieren zu lassen. + +Für die Näh-Community ist die Plattform der Wahl oft Instagram. Seit ich Instagram vor einem Jahren verlassen habe, habe ich das Gefühl, dass ich mich weiter von der Näh-Community entferne. + +Meine [Gründe](https://joost.decock.org/post/187710847164/24-hours-from-now-i-want-to-remove-my-instagram) zu gehen sind heute so gültig wie damals, aber ich wünschte, ich könnte mich auf eine Weise mit der Näh-Community verbinden, die für mich funktioniert. + +## Problem 3: Ich bin unsicher, wie ich mit dem Problem des institutionellen Rassismus umgehen soll. + +Das wichtigste vorweg: **Black Lives Matter** ✊🏾 + +Meine Unsicherheit ist auf meine Umgebung zurückzuführen. Ich bin ein weißer, cis-gender Mann mittleren Alters, der in einem Land geboren und aufgewachsen ist, das eine Geschichte hat, die mit dem Blut von People of Color getränkt ist ([dieses Land ist Belgien](https://en.wikipedia.org/wiki/Atrocities_in_the_Congo_Free_State)). Bis heute durchdringt beiläufiger Rassismus alle Aspekte der Gesellschaft, in der ich lebe. + +Eine einladende und vielfältige Community ist für mich *sine qua non*. Aber ich fühle mich schlecht ausgerüstet, um herauszufinden, wie ich eine auf FreeSewing erstellen kann. + +## Community Building + +Wie ich bereits sagte, spuken mir diese Dinge schon lange im Kopf herum, wenn auch viel verschwommener. Dann hörte ich mir Anfang diesen Monats [Black makers matter mit Julian Collins im Podcast Love To Sew](https://lovetosewpodcast.com/episodes/episode-156-black-makers-matter-with-julian-collins/) an. + +[Julian](https://www.instagram.com/juliancreates/) ist ein Förderer von FreeSewing (vielen Dank Julian) und beteiligt sich aktiv an der [Black Makers Matter](https://www.instagram.com/blkmakersmatter/) Bewegung auf Instagram. Ich wandte mich hilfesuchend an Julian und wir führten ein langes Gespräch über Zoom, wo wir über seine Arbeit sprachen und wie er die Community organisiert. + +Julian hatte eine Menge guter Ratschläge. Ich konnte es unmöglich alles in diesen Beitrag stopfen, aber es lässt sich zu Folgendem herunterkochen: + + - Fragen einfach Leute um Hilfe + - Stelle klar, was für eine Community du aufbauen möchtest + +Also nehme ich Julians Ratschlag zu Herzen und bitte um Hilfe. Bevor wir aber dorthin kommen, sollten wir sicherstellen, dass wir uns alle darüber einig sind, was für eine Art von Community wir hier versuchen zu bauen. + +## Schneller Check: Stimmst du den Wertvorstellungen von FreeSewing zu? + +Um sicherzustellen, dass deine Wertvorstellungen mit denen von FreeSewing in Einklang stehen, nimm dir bitte einen Moment Zeit, um dich mit dem Folgenden vertraut zu machen: + + - [Unsere Gemeinschaftsstandards](/docs/various/community-standards/) + - [Unsere Verhaltensregeln](https://freesewing.dev/contributors/code-of-conduct/) + - [Unser Umsatzversprechen](/docs/various/pledge/) + +Wenn dich das lesen hiervon froh und nicht wütend gemacht hast, können wir deine Hilfe gebrauchen :) + +## Bitte helft mit dabei, FreeSewing über das hinauswachsen zu lassen, was ich alleine tun kann + +Wir fangen einfach an: Wir haben vor, alle 2 Wochen ein Zoom/Skype/was-auch-immer Treffen abzuhalten, um herauszufinden, wie wir vorgehen möchten. Wir fangen im ersten Septemberwochenende an (nächstes Wochenende). Wir haben noch keine Zeit ausgewählt, denn es hängt von den Zeitzonen ab, in denen die Teilnehmer/innen leben. + +Wenn du gerne teilnehmen möchtest, [lass es uns bitte in unserem Chatroom wissen](https://discord.freesewing.org/). + +### Welche Art von Hilfe wird benötigt? + +Beggars can't be choosers. Jede Art von Hilfe ist willkommen, und ich möchte ganz sicher keine Freiwilligen abweisen. + +Allerdings entkräftet ein zu vager Aufruf die Botschaft. Deswegen habe ich unten eine Reihe an *Rollen* aufgelistet, um dir eine Idee zu geben, welche Art von Arbeit in FreeSewing gesteckt wird. Es soll keine vollständige Liste sein, sondern nur ein Ausgangspunkt für Diskussionen darüber. + +Die Reihenfolge ist alphabetisch (im englischen Originaltext, A. d. Ü.). + +**Backend-Entwickler/in** +Du lässt unser Backend Schritt halten mit den neuesten Frontend-Entwicklungen. Express ist dir nicht fremd. Node JS ist ein guter Freund. Oder vielleicht möchtest du, dass sie es werden. + +**Körper-Botschafter/in ** +Vielleicht bist du ungewöhnlich klein oder groß. Vielleicht hast du einen kleinen Hängebauch oder sehr große Brüste. Vielleicht hast du eine Behinderung, die Anpassungen in der Passform erfordert. Was auch immer es ist, du repräsentierst eine Minderheit was Passformen angeht und bist bereit, als Botschafter/in zu fungieren, um sicherzustellen, dass deine Bedürfnisse gehört und verstanden werden. + +**Community Builder** +You're an extrovert extraordinaire, or you're good at faking it. You enjoy chatting with all sorts of people, and networking is just you doing you. You're like the jelly that molds a group of individuals into a cohesive community. + +**Datenbank-Administrator/in** +Du kümmerst dich um unsere Datenbank. Andere Leute mögen das nicht für wichtig halten, aber du weißt es besser. Du bist mit MongoDB vertraut. + +**Devops Engineer** +Your aim is to make almost all these other roles irrelevant by automating the heck out of everything. CI and Github actions are fun for you. You like to sit back and have the robots do the work for you. + +**Frontend-Entwickler/in** +Du verbesserst unsere Webseiten, insbesondere freesewing.org und freesewing.dev. Beide sind mit [Gatsby](https://www.gatsbyjs.com/) gebaut, einem Open Source Framework um Frontends zu bauen, die mit [React](https://reactjs.org/) betrieben werden. Wenn du diese Dinge kennst oder sie gerne lernen würdest, ist das etwas für dich. + +**Illustrator/in** +Du erstellt Illustrationen, die die schriftliche Dokumentation begleiten. Wenn du ein Fahrrad aus dem Gedächtnis zeichnest, sieht es tatsächlich aus wie ein Fahrrad. + +**Inclusion & Diversity Manager** +You have skin in the game when it comes to inclusion and diversity. You'll help make our community welcoming and diverse. You won't be afraid to tell this pasty white dude when he's wrong. + +**Sprachbotschafter/in** +Du repräsentierst FreeSewing in einer nicht-englischsprachigen Community. Du kannst helfen, Fragen zu beantworten oder bei der Triage von Problemberichten. Oder du kannst uns darauf hinweisen, wo Übersetzungen fehlen. + +**Schnittmuster-Botschafter/in** +Du bist für ein bestimmtes FreeSewing Design/Schnittmuster verantwortlich. Du bist *die Person*, wenn es um Fragen zur Herstellung des Schnittmusters geht. Du stellst sicher, dass die Dokumentation nicht vergessen wird. And you can help with questions or triage problem reports to developers or designers. + +**Pattern Designer** +You come up with new pattern designs for FreeSewing. You might not know how to turn on a computer, but damn if you can't draft a bodice. + +**Pattern Developer** +You program new designs for FreeSewing. You might not know how to design sewing patterns, but you're not afraid of Javascript and are happy to team up with a designer to work on a new pattern together. + +**Proofreader** +You check original English text of translations for typos and/or grammar mistakes. You propose improvements and watch over a consistent style and tone across FreeSewing's documentation and written text. You're fluent in the language you're proofreading. + +**Social Media Platform Manager** +You represent FreeSewing on a *platform*, where platform could be Facebook, Twitter, Instagram, Tiktok, Snapchat, Reddit …. You manage the FreeSewing account on the platform, and use it to interact with the community. + +**Systemadministrator/in** +Du kümmerst dich um unsere Server. Du installierst Updates, stellst sicher, dass Zertifikate aktuell sind, das ganze Zeug. Dein Herz schlägt für Linux. You secretly automated most of your work with Ansible but hey, you put the playbooks in Git so no worries. + +**Technical Writer (code)** +You write documentation for freesewing.dev, our developers website. You have good writing skills and familiarity with code (Javascript). + +**Technical Writer (sewing)** +You write documentation for freesewing.org, our makers website. Du hast gute Schreibfähigkeiten und bist mit dem Nähen gut vertraut. + +**Übersetzer/in** +Du übersetzt FreeSewing in eine der zusätzlichen Sprachen (Französisch, Deutsch, Niederländisch, Spanisch) oder fügst eine neue hinzu, wenn du ehrgeizig bist. Du sprichst die Sprache fließend, in die du übersetzen willst, und hast ein gutes Verständnis von Englisch. + +**UX Designer/in** +Du weißt, was UX ist und sagst uns gerne, was schlecht ist und wie es besser gemacht werden kann. + +**Release Manager** +You pull the plug on new releases, you bundle our code, and publish new versions of our packages on NPM. + +**Webdesigner/in** +Du weißt, wie man Dinge schön macht, auch wenn du dir nicht sicher sind, wie du sie zum funktionieren bringst. Du weißt es zu schätzen, dass wir nicht #000 für schwarz verwenden. + +### Was habe ich davon? + +Wir können dir kein Geld bieten. Please [read our revenue pledge](/docs/various/pledge/) to understand why that is. + +What we can offer is responsibility, recognition, and a stake in something that strives to be a force for good in this world. + +It can also be an excellent learning opportunity for those of you who would like to pivot to a role in web development. And for as far as my time stretches — I will gladly teach and mentor people from underprivileged communities aiming for social mobility. + +## Fazit + +Vielleicht kannst du helfen. Vielleicht kennst du eine Person, die helfen kann oder für die dies ein wertvolles Lernerlebnis wäre. + +In jedem Fall würde ich es begrüßen, wenn du helfen könntest, die Nachricht zu verbreiten, dass ich um Hilfe bitte. + +Vielen Dank + +Joost + + diff --git a/markdown/org/blog/a-call-for-help/en.md b/markdown/org/blog/a-call-for-help/en.md new file mode 100644 index 00000000000..0cf10b21819 --- /dev/null +++ b/markdown/org/blog/a-call-for-help/en.md @@ -0,0 +1,194 @@ +--- +author: "joostdecock" +caption: "Note: This post is a long read. Although nowhere near as long as this book" +date: "2020-08-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1a143c96b4afc8c12d2014c5605bfd1e63d917d0-2000x1348.jpg" +intro: "Please help grow FreeSewing beyond what I can do on my own" +title: "Please help grow FreeSewing beyond what I can do on my own" +--- + + +Hi everyone, Joost here. +I'm writing this post to address some problems that have been worrying me lately. +Specifically, these problems: + + 1. [There is too much work for one person](#problem-1-there-is-too-much-work-for-one-person) + 2. [I feel I'm losing track of the sewing community](#problem-2-i-feel-im-losing-track-of-the-community) + 3. [I feel insecure about how to deal with the issue of systemic racism](#problem-3-i-feel-insecure-about-how-to-deal-with-the-issue-of-systemic-racism) + +The good news is that it's a relatively short list. +The even better news is that all of these problems be addressed by the same solution: [Community building](#community-building). + +Before we get into that, let's briefly look at each problem: + +## Problem 1: There is too much work for one person + +Over the course of the last week I read [Working in public: The making and maintenance of open source software](https://www.amazon.com/dp/0578675862/) by [Nadia Eghbal](https://nadiaeghbal.com/). + +I bought it because I was hoping to find answers to some of the questions that I ask myself. +Questions like “*How do other maintainers do it?*”, or “*Am I doing it wrong?*” + +In other words, I was hoping to find a fix for what I increasingly perceive as a problem: +The inability to scale my own labour in line with how I'd like to scale FreeSewing, the project. + +I don't want to spoil the book, but it didn't provide any straightforward answers on how to address that problem. +It turns out that the vast majority of open source maintainers are in the same boat. Most projects are run by either a single person, or a handful of people. + +There's nothing wrong with that. But it does put a firm upper limit on how much projects like FreeSewing can accomplish. + +## Problem 2: I feel I'm losing track of the sewing community + +I worry that I have been neglecting the communal aspects of FreeSewing, there are no comments or *social* aspects on the site. +I've always felt it was a fool's errand to try to corral people onto your own website. +Better to let them have discussions on the platforms of their choice. + +For the sewing community, the platform of choice is often Instagram. +Since I have left Instagram a year ago, I feel like I'm getting further away from the sewing community. + +My [reasons for leaving](https://joost.decock.org/post/187710847164/24-hours-from-now-i-want-to-remove-my-instagram) are as valid today as they were back then, +but I wish I could connect with the sewing community in a way that works for me. + +## Problem 3: I feel insecure about how to deal with the issue of systemic racism. + +First things first: **Black lives matter** ✊🏾 + +My insecurity stems from my environment. I am a white, middle-aged, cis-gender man +who was born and raised in a country with a history drenched in the blood of people of color +([that country is Belgium](https://en.wikipedia.org/wiki/Atrocities_in_the_Congo_Free_State)). +To this day, casual racism permeates all aspects of the society I live in. + +A welcoming and diverse community is a *sine qua non* for me. But I feel ill-equipped to figure out how to create one on FreeSewing. + +## Community building + +As I mentioned earlier, these things have been on my mind for a while, albeit they were a lot more fuzzy. +Then earlier this month I listened to [Black makers matter with Julian Collins on the podcast Love To Sew](https://lovetosewpodcast.com/episodes/episode-156-black-makers-matter-with-julian-collins/). + +[Julian](https://www.instagram.com/juliancreates/) is a patron of FreeSewing (thanks Julian) and actively involved with the [Black Makers Matter](https://www.instagram.com/blkmakersmatter/) movement on Instagram. I reached out to Julian looking for help, and we had a lengthy Zoom call where we talked about his work and how he goes about organizing the community. + +Julian had a lot of good advice. I couldn't possibly cram it all into this post, but it sort of boils down to: + + - Just ask people for help + - Be clear about what kind of community you want to build + +So I am taking Julian's advice to heart, and asking for help. Before we get to that though, let's make sure we're all on the same page about the kind of community we're trying to build here. + +## Quick check: Are you on board with FreeSewing's values? + +To ensure that your values are aligned with those of FreeSewing, please take a moment to familiarize yourself with: + + - [Our community standards](/docs/various/community-standards/) + - [Our code of conduct](https://freesewing.dev/contributors/code-of-conduct/) + - [Our revenue pledge](/docs/various/pledge/) + +If reading that made you happy rather than angry, we could use your help :) + +## Please help grow FreeSewing beyond what I can do on my own + +We're starting simple: We plan to hold a Zoom/Skype/Whatever call every 2 weeks to figure it out as we go. We start the first weekend of September (next weekend). +We haven't picked a time yet, for it will depend on the time zones the participants live in. + +If you'd like to attend, please [let us know in our chat room](https://discord.freesewing.org/). + +### What kind of help is needed? + +Beggars can't be choosers. All help is welcome, and I certainly don't want to turn down any volunteers. + +That being said, an overly vague call defuses the message. +So I've listed/included a number of *roles* below to give you an idea of the kind of work that goes into FreeSewing. +It's not meant to be an exhaustive list, but merely a starting point for a discussion. + +The order is alphabetic. + +**Backend Developer** +You keep our backend in step with the latest frontend developments. +Express is no stranger to you. Node JS is a good friend. Or maybe you'd like them to be. + +**Body Ambassador** +Maybe you're unusually short or tall. Maybe you have a bit of a pot belly or very large breasts. Maybe you have a disability that requires fit adjustments. Whatever it is, you represent a minority fitting issue, and are willing to act as an ambassador to make sure your needs are heard and understood. + +**Community Builder** +You're an extrovert extraordinaire, or you're good at faking it. You enjoy chatting with all sorts of people, and networking is just you doing you. You're like the jelly that molds a group of individuals into a cohesive community. + +**Database Administrator** +You look after our database. Other people might feel that's not important, but you know better. +You're familiar with MongoDB. + +**Devops Engineer** +Your aim is to make almost all these other roles irrelevant by automating the heck out of everything. +CI and Github actions are fun for you. You like to sit back and have the robots do the work for you. + +**Frontend Developer** +You improve our websites, specifically freesewing.org and freesewing.dev. Both of them are built with [Gatsby](https://www.gatsbyjs.com/), an open source framework for building frontends that is powered by [React](https://reactjs.org/). If you know these things, or would like to learn them, this is your jam. + +**Illustrator** +You create illustrations to go alongside the written documentation. If you draw a bicycle from memory, it actually looks like a bicycle. + +**Inclusion & Diversity Manager** +You have skin in the game when it comes to inclusion and diversity. You'll help make our community welcoming and diverse. You won't be afraid to tell this pasty white dude when he's wrong. + +**Language Ambassador** +You represent FreeSewing in a non-English community. You can help answer questions or triage problem reports. +Or you can point out where translations are missing. + +**Pattern Ambassador** +You'll be responsible for a specific FreeSewing design/pattern. +You'll be *the person* to ask questions about how to make that pattern. +You'll make sure the documentation is not forgotten. +And you can help with questions or triage problem reports to developers or designers. + +**Pattern Designer** +You come up with new pattern designs for FreeSewing. You might not know how to turn on a computer, but damn if you can't draft a bodice. + +**Pattern Developer** +You program new designs for FreeSewing. You might not know how to design sewing patterns, but you're not afraid of Javascript and are happy to team up with a designer to work on a new pattern together. + +**Proofreader** +You check original English text of translations for typos and/or grammar mistakes. You propose improvements and watch over a consistent style and tone across FreeSewing's documentation and written text. You're fluent in the language you're proofreading. + +**Social Media Platform Manager** +You represent FreeSewing on a *platform*, where platform could be Facebook, Twitter, Instagram, Tiktok, Snapchat, Reddit …. +You manage the FreeSewing account on the platform, and use it to interact with the community. + +**System Administrator** +You look after our servers. You install updates, make sure certificates are up-to-date, the works. +Linux is where your heart lies. You secretly automated most of your work with Ansible but hey, you put the playbooks in Git so no worries. + +**Technical Writer (code)** +You write documentation for freesewing.dev, our developers website. You have good writing skills and familiarity with code (Javascript). + +**Technical Writer (sewing)** +You write documentation for freesewing.org, our makers website. You have good writing skills and familiarity with sewing. + +**Translator** +You translate FreeSewing into one of its additional languages (French, German, Dutch, Spanish) or if you're ambitious, add a new one. You're fluent in the language you're translating to, and have a good grasp of English. + +**UX Designer** +You know what UX is and are happy to point out where it sucks and how it can be made better. + +**Release Manager** +You pull the plug on new releases, you bundle our code, and publish new versions of our packages on NPM. + +**Web Designer** +You know how to make things pretty, even if you're not sure how to actually make them work. You appreciate that we don't use #000 for black. + +### What's in it for me? + +We can't offer you money. Please [read our revenue pledge](/docs/various/pledge/) to understand why that is. + +What we can offer is responsibility, recognition, and a stake in something that strives to be a force for good in this world. + +It can also be an excellent learning opportunity for those of you who would like to pivot to a role in web development. +And for as far as my time stretches — I will gladly teach and mentor people from underprivileged communities aiming for social mobility. + +## Conclusion + +Maybe you can help. +Maybe you know somebody who can help, or for whom this would be a valuable learning experience. + +Either way, I'd appreciate it if you could help spread the message that I'm asking for help. + +Thank you, + +Joost + diff --git a/markdown/org/blog/a-call-for-help/es.md b/markdown/org/blog/a-call-for-help/es.md new file mode 100644 index 00000000000..d6c87580d24 --- /dev/null +++ b/markdown/org/blog/a-call-for-help/es.md @@ -0,0 +1,194 @@ +--- +author: "joostdecock" +caption: "Note: This post is a long read. Although nowhere near as long as this book" +date: "2020-08-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1a143c96b4afc8c12d2014c5605bfd1e63d917d0-2000x1348.jpg" +intro: "Please help grow FreeSewing beyond what I can do on my own [No traducido]" +title: "Please help grow FreeSewing beyond what I can do on my own [No traducido]" +--- + + +Hi everyone, Joost here. +I'm writing this post to address some problems that have been worrying me lately. +Specifically, these problems: + + 1. [There is too much work for one person](#problem-1-there-is-too-much-work-for-one-person) + 2. [I feel I'm losing track of the sewing community](#problem-2-i-feel-im-losing-track-of-the-community) + 3. [I feel insecure about how to deal with the issue of systemic racism](#problem-3-i-feel-insecure-about-how-to-deal-with-the-issue-of-systemic-racism) + +The good news is that it's a relatively short list. +The even better news is that all of these problems be addressed by the same solution: [Community building](#community-building). + +Before we get into that, let's briefly look at each problem: + +## Problem 1: There is too much work for one person + +Over the course of the last week I read [Working in public: The making and maintenance of open source software](https://www.amazon.com/dp/0578675862/) by [Nadia Eghbal](https://nadiaeghbal.com/). + +I bought it because I was hoping to find answers to some of the questions that I ask myself. +Questions like “*How do other maintainers do it?*”, or “*Am I doing it wrong?*” + +In other words, I was hoping to find a fix for what I increasingly perceive as a problem: +The inability to scale my own labour in line with how I'd like to scale FreeSewing, the project. + +I don't want to spoil the book, but it didn't provide any straightforward answers on how to address that problem. +It turns out that the vast majority of open source maintainers are in the same boat. Most projects are run by either a single person, or a handful of people. + +There's nothing wrong with that. But it does put a firm upper limit on how much projects like FreeSewing can accomplish. + +## Problem 2: I feel I'm losing track of the sewing community + +I worry that I have been neglecting the communal aspects of FreeSewing, there are no comments or *social* aspects on the site. +I've always felt it was a fool's errand to try to corral people onto your own website. +Better to let them have discussions on the platforms of their choice. + +For the sewing community, the platform of choice is often Instagram. +Since I have left Instagram a year ago, I feel like I'm getting further away from the sewing community. + +My [reasons for leaving](https://joost.decock.org/post/187710847164/24-hours-from-now-i-want-to-remove-my-instagram) are as valid today as they were back then, +but I wish I could connect with the sewing community in a way that works for me. + +## Problem 3: I feel insecure about how to deal with the issue of systemic racism. + +First things first: **Black lives matter** ✊🏾 + +My insecurity stems from my environment. I am a white, middle-aged, cis-gender man +who was born and raised in a country with a history drenched in the blood of people of color +([that country is Belgium](https://en.wikipedia.org/wiki/Atrocities_in_the_Congo_Free_State)). +To this day, casual racism permeates all aspects of the society I live in. + +A welcoming and diverse community is a *sine qua non* for me. But I feel ill-equipped to figure out how to create one on FreeSewing. + +## Community building + +As I mentioned earlier, these things have been on my mind for a while, albeit they were a lot more fuzzy. +Then earlier this month I listened to [Black makers matter with Julian Collins on the podcast Love To Sew](https://lovetosewpodcast.com/episodes/episode-156-black-makers-matter-with-julian-collins/). + +[Julian](https://www.instagram.com/juliancreates/) is a patron of FreeSewing (thanks Julian) and actively involved with the [Black Makers Matter](https://www.instagram.com/blkmakersmatter/) movement on Instagram. I reached out to Julian looking for help, and we had a lengthy Zoom call where we talked about his work and how he goes about organizing the community. + +Julian had a lot of good advice. I couldn't possibly cram it all into this post, but it sort of boils down to: + + - Just ask people for help + - Be clear about what kind of community you want to build + +So I am taking Julian's advice to heart, and asking for help. Before we get to that though, let's make sure we're all on the same page about the kind of community we're trying to build here. + +## Quick check: Are you on board with FreeSewing's values? + +To ensure that your values are aligned with those of FreeSewing, please take a moment to familiarize yourself with: + + - [Our community standards](/docs/various/community-standards/) + - [Our code of conduct](https://freesewing.dev/contributors/code-of-conduct/) + - [Our revenue pledge](/docs/various/pledge/) + +If reading that made you happy rather than angry, we could use your help :) + +## Please help grow FreeSewing beyond what I can do on my own + +We're starting simple: We plan to hold a Zoom/Skype/Whatever call every 2 weeks to figure it out as we go. We start the first weekend of September (next weekend). +We haven't picked a time yet, for it will depend on the time zones the participants live in. + +If you'd like to attend, please [let us know in our chat room](https://discord.freesewing.org/). + +### What kind of help is needed? + +Beggars can't be choosers. All help is welcome, and I certainly don't want to turn down any volunteers. + +That being said, an overly vague call defuses the message. +So I've listed/included a number of *roles* below to give you an idea of the kind of work that goes into FreeSewing. +It's not meant to be an exhaustive list, but merely a starting point for a discussion. + +The order is alphabetic. + +**Backend Developer** +You keep our backend in step with the latest frontend developments. +Express is no stranger to you. Node JS is a good friend. Or maybe you'd like them to be. + +**Body Ambassador** +Maybe you're unusually short or tall. Maybe you have a bit of a pot belly or very large breasts. Maybe you have a disability that requires fit adjustments. Whatever it is, you represent a minority fitting issue, and are willing to act as an ambassador to make sure your needs are heard and understood. + +**Community Builder** +You're an extrovert extraordinaire, or you're good at faking it. You enjoy chatting with all sorts of people, and networking is just you doing you. You're like the jelly that molds a group of individuals into a cohesive community. + +**Database Administrator** +You look after our database. Other people might feel that's not important, but you know better. +You're familiar with MongoDB. + +**Devops Engineer** +Your aim is to make almost all these other roles irrelevant by automating the heck out of everything. +CI and Github actions are fun for you. You like to sit back and have the robots do the work for you. + +**Frontend Developer** +You improve our websites, specifically freesewing.org and freesewing.dev. Both of them are built with [Gatsby](https://www.gatsbyjs.com/), an open source framework for building frontends that is powered by [React](https://reactjs.org/). If you know these things, or would like to learn them, this is your jam. + +**Illustrator** +You create illustrations to go alongside the written documentation. If you draw a bicycle from memory, it actually looks like a bicycle. + +**Inclusion & Diversity Manager** +You have skin in the game when it comes to inclusion and diversity. You'll help make our community welcoming and diverse. You won't be afraid to tell this pasty white dude when he's wrong. + +**Language Ambassador** +You represent FreeSewing in a non-English community. You can help answer questions or triage problem reports. +Or you can point out where translations are missing. + +**Pattern Ambassador** +You'll be responsible for a specific FreeSewing design/pattern. +You'll be *the person* to ask questions about how to make that pattern. +You'll make sure the documentation is not forgotten. +And you can help with questions or triage problem reports to developers or designers. + +**Pattern Designer** +You come up with new pattern designs for FreeSewing. You might not know how to turn on a computer, but damn if you can't draft a bodice. + +**Pattern Developer** +You program new designs for FreeSewing. You might not know how to design sewing patterns, but you're not afraid of Javascript and are happy to team up with a designer to work on a new pattern together. + +**Proofreader** +You check original English text of translations for typos and/or grammar mistakes. You propose improvements and watch over a consistent style and tone across FreeSewing's documentation and written text. You're fluent in the language you're proofreading. + +**Social Media Platform Manager** +You represent FreeSewing on a *platform*, where platform could be Facebook, Twitter, Instagram, Tiktok, Snapchat, Reddit …. +You manage the FreeSewing account on the platform, and use it to interact with the community. + +**System Administrator** +You look after our servers. You install updates, make sure certificates are up-to-date, the works. +Linux is where your heart lies. You secretly automated most of your work with Ansible but hey, you put the playbooks in Git so no worries. + +**Technical Writer (code)** +You write documentation for freesewing.dev, our developers website. You have good writing skills and familiarity with code (Javascript). + +**Technical Writer (sewing)** +You write documentation for freesewing.org, our makers website. You have good writing skills and familiarity with sewing. + +**Translator** +You translate FreeSewing into one of its additional languages (French, German, Dutch, Spanish) or if you're ambitious, add a new one. You're fluent in the language you're translating to, and have a good grasp of English. + +**UX Designer** +You know what UX is and are happy to point out where it sucks and how it can be made better. + +**Release Manager** +You pull the plug on new releases, you bundle our code, and publish new versions of our packages on NPM. + +**Web Designer** +You know how to make things pretty, even if you're not sure how to actually make them work. You appreciate that we don't use #000 for black. + +### What's in it for me? + +We can't offer you money. Please [read our revenue pledge](/docs/various/pledge/) to understand why that is. + +What we can offer is responsibility, recognition, and a stake in something that strives to be a force for good in this world. + +It can also be an excellent learning opportunity for those of you who would like to pivot to a role in web development. +And for as far as my time stretches — I will gladly teach and mentor people from underprivileged communities aiming for social mobility. + +## Conclusion + +Maybe you can help. +Maybe you know somebody who can help, or for whom this would be a valuable learning experience. + +Either way, I'd appreciate it if you could help spread the message that I'm asking for help. + +Thank you, + +Joost + diff --git a/markdown/org/blog/a-call-for-help/fr.md b/markdown/org/blog/a-call-for-help/fr.md new file mode 100644 index 00000000000..253a59c0e5a --- /dev/null +++ b/markdown/org/blog/a-call-for-help/fr.md @@ -0,0 +1,167 @@ +--- +author: "joostdecock" +caption: "Note: ceci est un long message. Bien que nettement moins que ce livre" +date: "2020-08-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1a143c96b4afc8c12d2014c5605bfd1e63d917d0-2000x1348.jpg" +intro: "Salut tout le monde, c'est Joost. J'écris ce message pour aborder certains problèmes qui m'ont ennuyé ces derniers temps. Plus spécifiquement, ces problèmes :" +title: "Aidez à faire grandir FreeSewing au-delà de ce que je peux faire seul" +--- + + +Salut tout le monde, c'est Joost. J'écris ce message pour aborder certains problèmes qui m'ont ennuyé ces derniers temps. Plus spécifiquement, ces problèmes : + + 1. [Il y a trop de travail pour une seule personne](#problem-1-there-is-too-much-work-for-one-person) + 2. [J'ai l'impression de perdre de le lien avec la communauté de couture](#problem-2-i-feel-im-losing-track-of-the-community) + 3. [Je ne me sens pas à l'aise sur la manière de traiter les problèmes de racisme](#problem-3-i-feel-insecure-about-how-to-deal-with-the-issue-of-systemic-racism) + +La bonne nouvelle est qu'il s'agit d'une liste relativement courte. La meilleure nouvelle est que tous ces problèmes peuvent être résolus par la même solution : [Développement Communautaire](#community-building). + +Avant d'entrer dans le vif du sujet, examinons brièvement chaque problème : + +## Problème 1 : Il y a trop de travail pour une personne + +Au cours de la semaine dernière, j'ai lu [Travailler en public : La création et la maintenance de logiciels open source](https://www.amazon.com/dp/0578675862/) par [Nadia Eghbal](https://nadiaeghbal.com/). + +Je l'ai acheté en espérant y trouver des réponses à certaines des questions que je me pose. Comme *Comment font les autres ?* ou *Suis-je en train de me tromper ?*” + +En d'autres termes, j''espérais trouver une solution à ce qui est pour moi un problème grandissant : l''incapacité à dimensionner mon propre travail à la façon dont je voudrais dimensionner le projet FreeSewing. + +Sans vouloir trop le critiquer, ce livre ne m'a fourni aucune réponse concrète sur la manière de résoudre ce problème. Il s'avère que la grande majorité des personnes travaillant en open source sont dans le même bateau. La plupart des projets sont maintenus par une seule personne ou une poignée de personnes. + +Il n'y a rien de mal à cela. Mais elle impose une limite sur le nombre de projets comme FreeSewing qui peuvent être réalisés. + +## Problème 2 : J'ai l'impression de perdre contact avec la communauté couture + +Je m'inquiète d'avoir négligé les aspects communautaires de FreeSewing, il n'y a pas de commentaires ni d'aspects *sociaux* sur le site. J'ai toujours pensé que c'était une erreur d'essayer de réunir les gens sur son propre site Web. Il vaut mieux les laisser discuter sur les plates-formes de leur choix. + +Pour la communauté couture, c'est souvent Instagram. Since I have left Instagram a year ago, I feel like I'm getting further away from the sewing community. + +Mes [raisons de partir](https://joost.decock.org/post/187710847164/24-hours-from-now-i-want-to-remove-my-instagram) sont les mêmes aujourd'hui qu'à l'époque, mais j'aimerais pouvoir me connecter avec la communauté couture d'une manière qui fonctionne pour moi. + +## Problème 3: Je ne me sens pas à l'aise sur la manière de traiter les problèmes de racisme. + +Premièrement : **Black lives matter**✊🏾 + +Mon malaise vient de mon environnement. Je suis un homme blanc cis-genre d'âge moyen, né et élevé dans un pays dont l'histoire est teintée du sang de gens de couleur ([ce pays est la Belgique](https://en.wikipedia.org/wiki/Atrocities_in_the_Congo_Free_State)). À ce jour, un racisme occasionnel imprègne tous les aspects de la société dans laquelle je vis. + +A welcoming and diverse community is a *sine qua non* for me. Mais je me sens mal équipé pour comprendre comment en créer une sur FreeSewing. + +## Développement communautaire + +Comme mentionné précédemment, ces choses me trottent dans la tête depuis un bon moment, même si elles sont plutôt floues. Puis plus tôt ce mois-ci, j'ai écouté ["Black makers matter" avec Julian Collins sur le podcast Love To Sew](https://lovetosewpodcast.com/episodes/episode-156-black-makers-matter-with-julian-collins/). + +[Julian](https://www.instagram.com/juliancreates/) est un mécène de FreeSewing (merci Julian) et il est activement impliqué dans le mouvement [Black makers matter](https://www.instagram.com/blkmakersmatter/) sur Instagram. J'ai contacté Julian à la recherche d'aide, et nous avons eu un long appel Zoom où nous avons parlé de son travail et comment il s'y prend pour organiser la communauté. + +Julian a eu beaucoup de bons conseils. Je ne pouvais raisonnablement pas tout détailler dans cet article, mais cela se résume à : + + - Il suffit de demander de l'aide aux gens + - Soyez clair sur le type de communauté que vous voulez construire + +Je prends donc à cœur les conseils de Julian, et je demande de l'aide. Avant d'y arriver, assurons-nous que nous sommes tous sur la même page sur le genre de communauté que nous essayons de construire ici. + +## Vérification rapide : Êtes-vous en ligne avec les valeurs de FreeSewing ? + +Pour vous assurer que vos valeurs sont alignées avec celles de FreeSewing, veuillez prendre un moment pour vous familiariser avec : + + - [Les standards de notre communauté](/docs/various/community-standards/) + - [Notre code de conduite](https://freesewing.dev/contributors/code-of-conduct/) + - [Notre engagement de revenus](/docs/various/pledge/) + +En supposant que cette lecture vous ait rendu plus heureux qu'en colère, nous pourrions utiliser votre aide :) + +## Aidez à faire grandir FreeSewing au-delà de ce que je peux faire seul + +Nous commençons simplement : nous prévoyons de tenir un Zoom/Skype/Autre toutes les 2 semaines pour faire le point au fur-et-à-mesure. Nous commençons le premier week-end de septembre (week-end prochain). Nous n'avons pas encore choisi d'heure, car cela dépendra des fuseaux horaires dans lesquels vivent les participants. + +If you'd like to attend, please [let us know in our chat room](https://discord.freesewing.org/). + +### De quelle aide avons nous besoin ? + +Les Mendiants ne peuvent faire les difficiles. Toute l'aide est la bienvenue, et je ne veux certainement rejeter aucun volontaire. + +Cela étant dit, un appel trop vague désavoue le message. J'ai donc écrit un certain nombre de *rôles* ci-dessous pour vous donner une idée du genre de travail dans FreeSewing. Il ne s'agit pas d'une liste exhaustive, mais simplement d'un point de départ pour une discussion. + +L'ordre est alphabétique. + +**Développeur Backend** +Vous gardez notre backend en phase avec les derniers développements du frontend. Express ne vous est pas étranger. Node JS est un bon ami. Ou peut-être aimeriez-vous qu'ils le soient. + +**Body Ambassadeur** +Peut-être que vous êtes inhabituellement petit ou grand. Peut-être que vous avez un peu de ventre ou une poitrine bien généreuse. Peut-être que vous avez un handicap qui nécessite des ajustements. Quoi qu'il en soit, vous représentez une minorité avec des problèmes d'ajustements, et êtes prêts à agir en tant qu'ambassadeur pour s'assurer que vos besoins soient entendus et compris. + +**Bâtisseur communautaire** +Vous êtes un extraordinaire extravagant, ou au moins bon imitateur. Vous aimez bavarder avec toutes sortes de personnes, et le réseautage est votre tasse de thé. Vous êtes comme la gelée qui transforme un groupe d'individus en une communauté unie. + +**Administrateur de la base de données** +Vous vous occupez de notre base de données. D'autres personnes pourraient avoir l'impression que ce n'est pas important, mais vous savez bien que ça l'est. Vous êtes familier avec MongoDB. + +**Ingénieur Devops** +Votre but est de rendre la quasi-totalité de ces autres rôles non pertinents en automatisant le plus de choses possible. Les actions de CI et Github sont amusantes pour vous. Vous aimez vous asseoir et demander aux robots de faire le travail pour vous. + +**Développeur Frontend** +Vous améliorez nos sites Web, en particulier freesewing.org et freesewing.dev. Tous deux sont construits avec [Gatsby](https://www.gatsbyjs.com/), un framework open source pour la construction de frontends qui est alimenté par [React](https://reactjs.org/). Si vous connaissez ces choses, ou si vous voulez les apprendre, c'est pour vous. + +**Illustrateur** +Vous créez des illustrations pour accompagner la documentation écrite. Quand vous tracez une bicyclette de tête, elle ressemble vraiment à une bicyclette. + +**Responsable de diversité & d'inclusion** +Vous êtes personnellement impliqué en matière d'inclusion et de diversité. Vous contribuerez à rendre notre communauté accueillante et diversifiée. Vous n'avez pas peur de dire à ce vilain blanc-bec quand il a tort. + +**Ambassadeur de langue** +Vous représentez FreeSewing dans une communauté non anglophone. Vous pouvez aider à répondre aux questions ou à trier les rapports de problèmes. Ou vous pouvez indiquer où les traductions sont manquantes. + +**Ambassadeur de patrons** +Vous serez responsable d'un design/patron FreeSewing spécifique. Tu seras *la personne* à qui poser des questions sur la réalisation de ce patron. Vous vous assurez qu'il n'y a aucun oubli dans la documentation. Et vous pouvez aider avec les questions ou le tri des rapports d'incident pour les développeurs ou les designers. + +**Concepteur de patrons** +Vous proposez de nouveaux designs de patrons pour FreeSewing. Vous ne savez peut-être pas comment allumer un ordinateur, mais vous déchirez en ébauche de corsage. + +**Développeur de patrons** +Vous programmez de nouveaux designs pour FreeSewing. Vous ne savez peut-être pas comment concevoir des patrons de couture, mais vous n'avez pas peur de Javascript et vous êtes heureux de faire équipe avec un concepteur pour travailler ensemble sur un nouveau patron. + +**Relecteur** +Vous vérifiez que la traduction du texte original en anglais ne contient pas de faute de frappe et/ou de grammaire. Vous proposez des améliorations et faites attention à un style et un ton cohérents à travers la documentation et le texte écrit de FreeSewing. Vous maîtrisez parfaitement la langue dont vous êtes relecteur. + +**Responsable de plateforme des réseaux sociaux** +Vous représentez FreeSewing sur une *plateforme * où la plateforme peut être Facebook, Twitter, Instagram, Tiktok, Snapchat, Reddit, …. Vous gérez le compte FreeSewing sur la plateforme, et l'utilisez pour interagir avec la communauté. + +**System Administrator** +You look after our servers. Installez les mises à jour, assurez-vous que les certificats sont à jour, et tout foctionne. Linux est votre grand chouchou. Vous avez secrètement automatisé la majeure partie de votre travail avec Ansible, mais bon, vous avez mis les playbooks dans Git donc ça va. + +**Rédacteur technique (code)** +Vous écrivez de la documentation pour freesewing.dev, notre site web de développeurs. Vous avez de bonnes compétences en programmation et vous êtes familier avec le code (Javascript). + +**Rédacteur technique (couture)** +Vous écrivez de la documentation pour freesewing.org, notre site web pour les ceux qui vont réaliser les patrons. You have good writing skills and familiarity with sewing. + +**Traducteur** +Vous traduisez dans une des langues supplémentaires de FreeSewing (français, allemand, néerlandais, espagnol) ou si vous êtes ambitieux, ajoutez-en une nouvelle. Vous maîtrisez parfaitement la langue dans laquelle vous traduisez et maîtrisez bien l'anglais. + +**UX Designer** +Vous savez ce qu'est l'UX et êtes heureux de signaler où ça ne va pas et comment cela peut être amélioré. + +**Responsable des versions** +Vous avez la main sur les nouvelles versions, vous groupez notre code et publiez de nouvelles versions de nos packages sur NPM. + +**Web Designer** +Vous savez comment rendre les choses jolies, même si vous ne savez pas comment les faire fonctionner. Vous appréciez que nous n'utilisions pas #000 pour le noir. + +### Qu'est-ce que j'y gagne ? + +Nous ne pouvons pas vous offrir d'argent. Veuillez [lire notre engagement en matière de revenus](/docs/various/pledge/) pour comprendre pourquoi. + +Ce que nous pouvons offrir, c'est la responsabilité, la reconnaissance et une participation dans quelque chose qui cherche à être une force pour le bien dans ce monde. + +Il peut également être une excellente occasion d’apprendre pour ceux d’entre vous qui voudraient jouer un rôle dans le développement du web. Et tant que mon temps pourra le permettre, je me ferai un plaisir d’enseigner et de superviser les gens des communautés défavorisées qui aspirent à la mobilité sociale. + +## Conclusion + +Peut-être que vous pouvez nous aider. Peut-être que vous connaissez quelqu'un qui peut aider, ou pour qui cela serait une expérience d'apprentissage précieuse. + +Quoi qu'il en soit, je vous serais reconnaissant si vous pouviez aider à faire passer le message que je demande de l'aide. + +Merci, + +Joost + + diff --git a/markdown/org/blog/a-call-for-help/nl.md b/markdown/org/blog/a-call-for-help/nl.md new file mode 100644 index 00000000000..f3e3e4144b2 --- /dev/null +++ b/markdown/org/blog/a-call-for-help/nl.md @@ -0,0 +1,167 @@ +--- +author: "joostdecock" +caption: "Note: This post is a long read. Although nowhere near as long as this book" +date: "2020-08-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1a143c96b4afc8c12d2014c5605bfd1e63d917d0-2000x1348.jpg" +intro: "Hallo iedereen, Joost hier. I'm writing this post to address some problems that have been worrying me lately. Specifically, these problems:" +title: "Help me om FreeSewing groter te laten worden dan wat ik zelf kan doen" +--- + + +Hallo iedereen, Joost hier. I'm writing this post to address some problems that have been worrying me lately. Specifically, these problems: + + 1. [There is too much work for one person](#problem-1-there-is-too-much-work-for-one-person) + 2. [I feel I'm losing track of the sewing community](#problem-2-i-feel-im-losing-track-of-the-community) + 3. [I feel insecure about how to deal with the issue of systemic racism](#problem-3-i-feel-insecure-about-how-to-deal-with-the-issue-of-systemic-racism) + +The good news is that it's a relatively short list. The even better news is that all of these problems be addressed by the same solution: [Community building](#community-building). + +Laat ons elk probleem even bekijken voor we daar verder op ingaan: + +## Problem 1: There is too much work for one person + +Over the course of the last week I read [Working in public: The making and maintenance of open source software](https://www.amazon.com/dp/0578675862/) by [Nadia Eghbal](https://nadiaeghbal.com/). + +Ik kocht het omdat ik hoopte op antwoorden voor een aantal vragen die ik mezelf stel. Questions like “*How do other maintainers do it?*”, or “*Am I doing it wrong?*” + +In andere woorden was ik op zoek naar een oplossing voor een probleem dat steeds groter wordt: het onvermogen om mijn eigen werk in verhouding te krijgen met wat ik wil voor FreeSewing als project. + +I don't want to spoil the book, but it didn't provide any straightforward answers on how to address that problem. It turns out that the vast majority of open source maintainers are in the same boat. Most projects are run by either a single person, or a handful of people. + +There's nothing wrong with that. But it does put a firm upper limit on how much projects like FreeSewing can accomplish. + +## Problem 2: I feel I'm losing track of the sewing community + +I worry that I have been neglecting the communal aspects of FreeSewing, there are no comments or *social* aspects on the site. I've always felt it was a fool's errand to try to corral people onto your own website. Better to let them have discussions on the platforms of their choice. + +Voor de naaigemeenschap is dat vaak Instagram. Since I have left Instagram a year ago, I feel like I'm getting further away from the sewing community. + +My [reasons for leaving](https://joost.decock.org/post/187710847164/24-hours-from-now-i-want-to-remove-my-instagram) are as valid today as they were back then, but I wish I could connect with the sewing community in a way that works for me. + +## Probleem 3: ik voel me onzeker over hoe ik moet omgaan met de problematiek rond systemisch racisme. + +Eerst en vooral: **Black lives matter**✊🏾 + +Mijn onzekerheid komt uit mijn omgeving. Ik ben een witte, cisgender man van middelbare leeftijd, geboren en getogen in een land met een geschiedenis die doordrenkt is met het bloed van gekleurde mensen ([dat land is België](https://en.wikipedia.org/wiki/Atrocities_in_the_Congo_Free_State)). Tot op vandaag dringt racistisch gedachtegoed door in alle aspecten van de maatschappij waarin ik leef. + +A welcoming and diverse community is a *sine qua non* for me. But I feel ill-equipped to figure out how to create one on FreeSewing. + +## Community building + +As I mentioned earlier, these things have been on my mind for a while, albeit they were a lot more fuzzy. Then earlier this month I listened to [Black makers matter with Julian Collins on the podcast Love To Sew](https://lovetosewpodcast.com/episodes/episode-156-black-makers-matter-with-julian-collins/). + +[Julian](https://www.instagram.com/juliancreates/) is a patron of FreeSewing (thanks Julian) and actively involved with the [Black Makers Matter](https://www.instagram.com/blkmakersmatter/) movement on Instagram. Ik sprak Julian aan om hulp te vragen, en we hadden een lang gesprek via Zoom waarin we over zijn werk spraken en hoe hij de community organiseert. + +Julian had een hoop goed advies. I couldn't possibly cram it all into this post, but it sort of boils down to: + + - Just ask people for help + - Be clear about what kind of community you want to build + +So I am taking Julian's advice to heart, and asking for help. Before we get to that though, let's make sure we're all on the same page about the kind of community we're trying to build here. + +## Even checken: Kan jij je vinden in de waarden van FreeSewing? + +To ensure that your values are aligned with those of FreeSewing, please take a moment to familiarize yourself with: + + - [Our community standards](/docs/various/community-standards/) + - [Our code of conduct](https://freesewing.dev/contributors/code-of-conduct/) + - [Our revenue pledge](/docs/various/pledge/) + +If reading that made you happy rather than angry, we could use your help :) + +## Help me om FreeSewing groter te laten worden dan wat ik zelf kan doen + +We're starting simple: We plan to hold a Zoom/Skype/Whatever call every 2 weeks to figure it out as we go. We start the first weekend of September (next weekend). We haven't picked a time yet, for it will depend on the time zones the participants live in. + +If you'd like to attend, please [let us know in our chat room](https://discord.freesewing.org/). + +### What kind of help is needed? + +Beggars can't be choosers. All help is welcome, and I certainly don't want to turn down any volunteers. + +That being said, an overly vague call defuses the message. So I've listed/included a number of *roles* below to give you an idea of the kind of work that goes into FreeSewing. It's not meant to be an exhaustive list, but merely a starting point for a discussion. + +The order is alphabetic. + +**Backend Developer** +You keep our backend in step with the latest frontend developments. Express is no stranger to you. Node JS is a good friend. Or maybe you'd like them to be. + +**Body Ambassador** +Maybe you're unusually short or tall. Maybe you have a bit of a pot belly or very large breasts. Maybe you have a disability that requires fit adjustments. Whatever it is, you represent a minority fitting issue, and are willing to act as an ambassador to make sure your needs are heard and understood. + +**Community Builder** +You're an extrovert extraordinaire, or you're good at faking it. You enjoy chatting with all sorts of people, and networking is just you doing you. You're like the jelly that molds a group of individuals into a cohesive community. + +**Database Administrator** +You look after our database. Other people might feel that's not important, but you know better. You're familiar with MongoDB. + +**Devops Engineer** +Your aim is to make almost all these other roles irrelevant by automating the heck out of everything. CI and Github actions are fun for you. You like to sit back and have the robots do the work for you. + +**Frontend Developer** +You improve our websites, specifically freesewing.org and freesewing.dev. Both of them are built with [Gatsby](https://www.gatsbyjs.com/), an open source framework for building frontends that is powered by [React](https://reactjs.org/). If you know these things, or would like to learn them, this is your jam. + +**Illustrator** +You create illustrations to go alongside the written documentation. If you draw a bicycle from memory, it actually looks like a bicycle. + +**Inclusion & Diversity Manager** +You have skin in the game when it comes to inclusion and diversity. You'll help make our community welcoming and diverse. You won't be afraid to tell this pasty white dude when he's wrong. + +**Language Ambassador** +You represent FreeSewing in a non-English community. You can help answer questions or triage problem reports. Or you can point out where translations are missing. + +**Pattern Ambassador** +You'll be responsible for a specific FreeSewing design/pattern. You'll be *the person* to ask questions about how to make that pattern. You'll make sure the documentation is not forgotten. And you can help with questions or triage problem reports to developers or designers. + +**Pattern Designer** +You come up with new pattern designs for FreeSewing. You might not know how to turn on a computer, but damn if you can't draft a bodice. + +**Pattern Developer** +You program new designs for FreeSewing. You might not know how to design sewing patterns, but you're not afraid of Javascript and are happy to team up with a designer to work on a new pattern together. + +**Proofreader** +You check original English text of translations for typos and/or grammar mistakes. You propose improvements and watch over a consistent style and tone across FreeSewing's documentation and written text. You're fluent in the language you're proofreading. + +**Social Media Platform Manager** +You represent FreeSewing on a *platform*, where platform could be Facebook, Twitter, Instagram, Tiktok, Snapchat, Reddit …. You manage the FreeSewing account on the platform, and use it to interact with the community. + +**System Administrator** +You look after our servers. You install updates, make sure certificates are up-to-date, the works. Linux is where your heart lies. You secretly automated most of your work with Ansible but hey, you put the playbooks in Git so no worries. + +**Technical Writer (code)** +You write documentation for freesewing.dev, our developers website. You have good writing skills and familiarity with code (Javascript). + +**Technical Writer (sewing)** +You write documentation for freesewing.org, our makers website. You have good writing skills and familiarity with sewing. + +**Translator** +You translate FreeSewing into one of its additional languages (French, German, Dutch, Spanish) or if you're ambitious, add a new one. You're fluent in the language you're translating to, and have a good grasp of English. + +**UX Designer** +You know what UX is and are happy to point out where it sucks and how it can be made better. + +**Release Manager** +You pull the plug on new releases, you bundle our code, and publish new versions of our packages on NPM. + +**Web Designer** +You know how to make things pretty, even if you're not sure how to actually make them work. You appreciate that we don't use #000 for black. + +### What's in it for me? + +We can't offer you money. Please [read our revenue pledge](/docs/various/pledge/) to understand why that is. + +What we can offer is responsibility, recognition, and a stake in something that strives to be a force for good in this world. + +It can also be an excellent learning opportunity for those of you who would like to pivot to a role in web development. And for as far as my time stretches — I will gladly teach and mentor people from underprivileged communities aiming for social mobility. + +## Conclusion + +Maybe you can help. Maybe you know somebody who can help, or for whom this would be a valuable learning experience. + +Either way, I'd appreciate it if you could help spread the message that I'm asking for help. + +Thank you, + +Joost + + diff --git a/markdown/org/blog/albert-apron/de.md b/markdown/org/blog/albert-apron/de.md new file mode 100644 index 00000000000..298f7f23084 --- /dev/null +++ b/markdown/org/blog/albert-apron/de.md @@ -0,0 +1,23 @@ +--- +author: "joostdecock" +caption: "Keep those home-made clothes clean while cooking with the Albert apron" +date: "2020-10-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/192f0da76422475ea9a36b7988d70f69bb89bbaf-1920x1282.jpg" +intro: "What do you do if your daughter needed an apron for school?" +title: "We haz apron now: FreeSewing 2.10 brings you Albert, a humble apron pattern [Nicht übersetzt]" +--- + + +What do you do if your daughter needed an apron for school? + + - Would you run out to the store and buy one? + - Would you fire up your sewing machine and make one? + - Would you say to yourself _hmm, better make a pattern first_ and then + share your FreeSewing pattern so that now everybody can have an apron? + +Because [that's what Wouter did](/showcase/albert-by-wouter/), so we wrapped it +into FreeSewing v2.10, and [voila](/designs/albert/). + +![Wouter's daughter wearing the Albert apron](https://posts.freesewing.org/uploads/albert_08ccbfc95b.jpg) + + diff --git a/markdown/org/blog/albert-apron/en.md b/markdown/org/blog/albert-apron/en.md new file mode 100644 index 00000000000..b1a6dbc0c54 --- /dev/null +++ b/markdown/org/blog/albert-apron/en.md @@ -0,0 +1,23 @@ +--- +author: "joostdecock" +caption: "Keep those home-made clothes clean while cooking with the Albert apron" +date: "2020-10-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/192f0da76422475ea9a36b7988d70f69bb89bbaf-1920x1282.jpg" +intro: "What do you do if your daughter needed an apron for school?" +title: "We haz apron now: FreeSewing 2.10 brings you Albert, a humble apron pattern" +--- + + +What do you do if your daughter needed an apron for school? + + - Would you run out to the store and buy one? + - Would you fire up your sewing machine and make one? + - Would you say to yourself _hmm, better make a pattern first_ and then + share your FreeSewing pattern so that now everybody can have an apron? + +Because [that's what Wouter did](/showcase/albert-by-wouter/), so we wrapped it +into FreeSewing v2.10, and [voila](/designs/albert/). + +![Wouter's daughter wearing the Albert apron](https://posts.freesewing.org/uploads/albert_08ccbfc95b.jpg) + + diff --git a/markdown/org/blog/albert-apron/es.md b/markdown/org/blog/albert-apron/es.md new file mode 100644 index 00000000000..43e2882d643 --- /dev/null +++ b/markdown/org/blog/albert-apron/es.md @@ -0,0 +1,23 @@ +--- +author: "joostdecock" +caption: "Keep those home-made clothes clean while cooking with the Albert apron" +date: "2020-10-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/192f0da76422475ea9a36b7988d70f69bb89bbaf-1920x1282.jpg" +intro: "What do you do if your daughter needed an apron for school?" +title: "We haz apron now: FreeSewing 2.10 brings you Albert, a humble apron pattern [No traducido]" +--- + + +What do you do if your daughter needed an apron for school? + + - Would you run out to the store and buy one? + - Would you fire up your sewing machine and make one? + - Would you say to yourself _hmm, better make a pattern first_ and then + share your FreeSewing pattern so that now everybody can have an apron? + +Because [that's what Wouter did](/showcase/albert-by-wouter/), so we wrapped it +into FreeSewing v2.10, and [voila](/designs/albert/). + +![Wouter's daughter wearing the Albert apron](https://posts.freesewing.org/uploads/albert_08ccbfc95b.jpg) + + diff --git a/markdown/org/blog/albert-apron/fr.md b/markdown/org/blog/albert-apron/fr.md new file mode 100644 index 00000000000..2bcec42d4d2 --- /dev/null +++ b/markdown/org/blog/albert-apron/fr.md @@ -0,0 +1,23 @@ +--- +author: "joostdecock" +caption: "Gardez vos vêtements faits maison propres en cuisinant avec le tablier Albert" +date: "2020-10-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/192f0da76422475ea9a36b7988d70f69bb89bbaf-1920x1282.jpg" +intro: "Que feriez-vous si votre fille avait besoin d'un tablier pour l'école ?" +title: "Nous avons un tablier maintenant : FreeSewing 2.10 vous apporte Albert, un humble patron de tablier" +--- + + +Que feriez-vous si votre fille avait besoin d'un tablier pour l'école ? + + - Vous rendriez-vous au magasin pour en acheter un ? + - Ou allumeriez-vous votre machine pour en coudre un ? + - Pourriez-vous vous dire _hmm, il faire un patron d'abord_ puis partager votre patron FreeSewing afin que tout le monde puisse maintenant avoir un tablier ? + +Parce que [c'est ce que Wouter a fait](/showcase/albert-by-wouter/), donc nous l'avons intégré dans FreeSewing v2.10, et [voilà](/designs/albert/). + +![Fille de Wouter portant le tablier Albert](albert.jpg) + + + + diff --git a/markdown/org/blog/albert-apron/nl.md b/markdown/org/blog/albert-apron/nl.md new file mode 100644 index 00000000000..4ba2a8cd649 --- /dev/null +++ b/markdown/org/blog/albert-apron/nl.md @@ -0,0 +1,23 @@ +--- +author: "joostdecock" +caption: "Keep those home-made clothes clean while cooking with the Albert apron" +date: "2020-10-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/192f0da76422475ea9a36b7988d70f69bb89bbaf-1920x1282.jpg" +intro: "What do you do if your daughter needed an apron for school?" +title: "We haz apron now: FreeSewing 2.10 brings you Albert, a humble apron pattern [Niet vertaald]" +--- + + +What do you do if your daughter needed an apron for school? + + - Would you run out to the store and buy one? + - Would you fire up your sewing machine and make one? + - Would you say to yourself _hmm, better make a pattern first_ and then + share your FreeSewing pattern so that now everybody can have an apron? + +Because [that's what Wouter did](/showcase/albert-by-wouter/), so we wrapped it +into FreeSewing v2.10, and [voila](/designs/albert/). + +![Wouter's daughter wearing the Albert apron](https://posts.freesewing.org/uploads/albert_08ccbfc95b.jpg) + + diff --git a/markdown/org/blog/all-contributors/de.md b/markdown/org/blog/all-contributors/de.md new file mode 100644 index 00000000000..98b83279ac5 --- /dev/null +++ b/markdown/org/blog/all-contributors/de.md @@ -0,0 +1,35 @@ +--- +author: "joostdecock" +caption: "We're saying thanks to our contributors and want to make sure their contributions get the credit they deserve" +date: "2021-11-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1488bc5a9940423308a38d2cd33edb86b6eed442-1920x1280.jpg" +intro: "During our last contributor call , we decided that we would implement the All Contributors specification as a way to honour all our contributors." +title: "Calling all contributors [Nicht übersetzt]" +--- + +During [our last contributor call](https://github.com/freesewing/freesewing/issues/1514), we decided that we would implement the [All Contributors specification](https://allcontributors.org/) as a way to honour all our contributors. + +If on the surface, a contributor call decision to honour contributors sounds like some sort of self-serving nonsense, let me reassure you that there's no risk of dislocated shoulders from patting ourselves on the back. Instead it's about (also) honouring those contributions that tend to go overlooked in Open Source. + +The All Contributors website summerazes it as: + +> This is a specification for recognizing contributors to an open source project in a way that rewards each and every contribution, not just code. +> +> People are giving themselves and their free time to contribute to open source projects in so many ways, so we believe everyone should be praised for their contributions (code or not). + +When we talk about *contributors* in open source projects, there is often the assumption that this is all the people who contribute code to the project. The fact the [GitHub lists the contributors of a project based on the actual commits](https://github.com/freesewing/freesewing/graphs/contributors) goes a long way to cement that view. + +But there's plenty of contributions that fly under the radar of an automated system based on the commit history. Things like documentation and blog posts, community building, answering questions or submitting bug reports, are all valuable contributions that deserve to be recognized. + +By implementing the All Contributors specification, we pledge to give those people credit for their contributions, and make that credit visible. In practice the list of contributors will be included in the `README.md` file of all our packages, as well as in the main `README.md` file of [our `freesewing/freesewing` monorepo](https://github.com/freesewing/freesewing). + +In the future, we also plan to make this list available on our website. + +## How does it work? + +Going forward, we will make an effort to add all contributors regardless of how they contribute to the project. But we'd also like to capture contributions that were made up until now. + +For this, we need your help. If you've contributed to FreeSewing, let us know. You can [let us know on Discord](https://discord.freesewing.org/), or you can [create an issue](https://github.com/freesewing/freesewing/issues/new?assignees=joostdecock&labels=%F0%9F%92%9C+all+contributors&template=all-contributors.md&title=All+Contributors%3A+Please+add+%28username+here%29), or you can comment on [any issue](https://github.com/freesewing/freesewing/issues) or [pull request](https://github.com/freesewing/freesewing/pulls) using [the instructions for the all-contributors bot](https://allcontributors.org/docs/en/bot/usage). + + +Don't be shy, add yourself :) diff --git a/markdown/org/blog/all-contributors/en.md b/markdown/org/blog/all-contributors/en.md new file mode 100644 index 00000000000..ff5fe2b063f --- /dev/null +++ b/markdown/org/blog/all-contributors/en.md @@ -0,0 +1,35 @@ +--- +author: "joostdecock" +caption: "We're saying thanks to our contributors and want to make sure their contributions get the credit they deserve" +date: "2021-11-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1488bc5a9940423308a38d2cd33edb86b6eed442-1920x1280.jpg" +intro: "During our last contributor call , we decided that we would implement the All Contributors specification as a way to honour all our contributors." +title: "Calling all contributors" +--- + +During [our last contributor call](https://github.com/freesewing/freesewing/issues/1514), we decided that we would implement the [All Contributors specification](https://allcontributors.org/) as a way to honour all our contributors. + +If on the surface, a contributor call decision to honour contributors sounds like some sort of self-serving nonsense, let me reassure you that there's no risk of dislocated shoulders from patting ourselves on the back. Instead it's about (also) honouring those contributions that tend to go overlooked in Open Source. + +The All Contributors website summerazes it as: + +> This is a specification for recognizing contributors to an open source project in a way that rewards each and every contribution, not just code. +> +> People are giving themselves and their free time to contribute to open source projects in so many ways, so we believe everyone should be praised for their contributions (code or not). + +When we talk about *contributors* in open source projects, there is often the assumption that this is all the people who contribute code to the project. The fact the [GitHub lists the contributors of a project based on the actual commits](https://github.com/freesewing/freesewing/graphs/contributors) goes a long way to cement that view. + +But there's plenty of contributions that fly under the radar of an automated system based on the commit history. Things like documentation and blog posts, community building, answering questions or submitting bug reports, are all valuable contributions that deserve to be recognized. + +By implementing the All Contributors specification, we pledge to give those people credit for their contributions, and make that credit visible. In practice the list of contributors will be included in the `README.md` file of all our packages, as well as in the main `README.md` file of [our `freesewing/freesewing` monorepo](https://github.com/freesewing/freesewing). + +In the future, we also plan to make this list available on our website. + +## How does it work? + +Going forward, we will make an effort to add all contributors regardless of how they contribute to the project. But we'd also like to capture contributions that were made up until now. + +For this, we need your help. If you've contributed to FreeSewing, let us know. You can [let us know on Discord](https://discord.freesewing.org/), or you can [create an issue](https://github.com/freesewing/freesewing/issues/new?assignees=joostdecock&labels=%F0%9F%92%9C+all+contributors&template=all-contributors.md&title=All+Contributors%3A+Please+add+%28username+here%29), or you can comment on [any issue](https://github.com/freesewing/freesewing/issues) or [pull request](https://github.com/freesewing/freesewing/pulls) using [the instructions for the all-contributors bot](https://allcontributors.org/docs/en/bot/usage). + + +Don't be shy, add yourself :) diff --git a/markdown/org/blog/all-contributors/es.md b/markdown/org/blog/all-contributors/es.md new file mode 100644 index 00000000000..1ba2e0c7448 --- /dev/null +++ b/markdown/org/blog/all-contributors/es.md @@ -0,0 +1,35 @@ +--- +author: "joostdecock" +caption: "We're saying thanks to our contributors and want to make sure their contributions get the credit they deserve" +date: "2021-11-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1488bc5a9940423308a38d2cd33edb86b6eed442-1920x1280.jpg" +intro: "During our last contributor call , we decided that we would implement the All Contributors specification as a way to honour all our contributors." +title: "Calling all contributors [No traducido]" +--- + +During [our last contributor call](https://github.com/freesewing/freesewing/issues/1514), we decided that we would implement the [All Contributors specification](https://allcontributors.org/) as a way to honour all our contributors. + +If on the surface, a contributor call decision to honour contributors sounds like some sort of self-serving nonsense, let me reassure you that there's no risk of dislocated shoulders from patting ourselves on the back. Instead it's about (also) honouring those contributions that tend to go overlooked in Open Source. + +The All Contributors website summerazes it as: + +> This is a specification for recognizing contributors to an open source project in a way that rewards each and every contribution, not just code. +> +> People are giving themselves and their free time to contribute to open source projects in so many ways, so we believe everyone should be praised for their contributions (code or not). + +When we talk about *contributors* in open source projects, there is often the assumption that this is all the people who contribute code to the project. The fact the [GitHub lists the contributors of a project based on the actual commits](https://github.com/freesewing/freesewing/graphs/contributors) goes a long way to cement that view. + +But there's plenty of contributions that fly under the radar of an automated system based on the commit history. Things like documentation and blog posts, community building, answering questions or submitting bug reports, are all valuable contributions that deserve to be recognized. + +By implementing the All Contributors specification, we pledge to give those people credit for their contributions, and make that credit visible. In practice the list of contributors will be included in the `README.md` file of all our packages, as well as in the main `README.md` file of [our `freesewing/freesewing` monorepo](https://github.com/freesewing/freesewing). + +In the future, we also plan to make this list available on our website. + +## How does it work? + +Going forward, we will make an effort to add all contributors regardless of how they contribute to the project. But we'd also like to capture contributions that were made up until now. + +For this, we need your help. If you've contributed to FreeSewing, let us know. You can [let us know on Discord](https://discord.freesewing.org/), or you can [create an issue](https://github.com/freesewing/freesewing/issues/new?assignees=joostdecock&labels=%F0%9F%92%9C+all+contributors&template=all-contributors.md&title=All+Contributors%3A+Please+add+%28username+here%29), or you can comment on [any issue](https://github.com/freesewing/freesewing/issues) or [pull request](https://github.com/freesewing/freesewing/pulls) using [the instructions for the all-contributors bot](https://allcontributors.org/docs/en/bot/usage). + + +Don't be shy, add yourself :) diff --git a/markdown/org/blog/all-contributors/fr.md b/markdown/org/blog/all-contributors/fr.md new file mode 100644 index 00000000000..a21535843bd --- /dev/null +++ b/markdown/org/blog/all-contributors/fr.md @@ -0,0 +1,35 @@ +--- +author: "joostdecock" +caption: "We're saying thanks to our contributors and want to make sure their contributions get the credit they deserve" +date: "2021-11-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1488bc5a9940423308a38d2cd33edb86b6eed442-1920x1280.jpg" +intro: "During our last contributor call , we decided that we would implement the All Contributors specification as a way to honour all our contributors." +title: "Calling all contributors [Non traduit]" +--- + +During [our last contributor call](https://github.com/freesewing/freesewing/issues/1514), we decided that we would implement the [All Contributors specification](https://allcontributors.org/) as a way to honour all our contributors. + +If on the surface, a contributor call decision to honour contributors sounds like some sort of self-serving nonsense, let me reassure you that there's no risk of dislocated shoulders from patting ourselves on the back. Instead it's about (also) honouring those contributions that tend to go overlooked in Open Source. + +The All Contributors website summerazes it as: + +> This is a specification for recognizing contributors to an open source project in a way that rewards each and every contribution, not just code. +> +> People are giving themselves and their free time to contribute to open source projects in so many ways, so we believe everyone should be praised for their contributions (code or not). + +When we talk about *contributors* in open source projects, there is often the assumption that this is all the people who contribute code to the project. The fact the [GitHub lists the contributors of a project based on the actual commits](https://github.com/freesewing/freesewing/graphs/contributors) goes a long way to cement that view. + +But there's plenty of contributions that fly under the radar of an automated system based on the commit history. Things like documentation and blog posts, community building, answering questions or submitting bug reports, are all valuable contributions that deserve to be recognized. + +By implementing the All Contributors specification, we pledge to give those people credit for their contributions, and make that credit visible. In practice the list of contributors will be included in the `README.md` file of all our packages, as well as in the main `README.md` file of [our `freesewing/freesewing` monorepo](https://github.com/freesewing/freesewing). + +In the future, we also plan to make this list available on our website. + +## How does it work? + +Going forward, we will make an effort to add all contributors regardless of how they contribute to the project. But we'd also like to capture contributions that were made up until now. + +For this, we need your help. If you've contributed to FreeSewing, let us know. You can [let us know on Discord](https://discord.freesewing.org/), or you can [create an issue](https://github.com/freesewing/freesewing/issues/new?assignees=joostdecock&labels=%F0%9F%92%9C+all+contributors&template=all-contributors.md&title=All+Contributors%3A+Please+add+%28username+here%29), or you can comment on [any issue](https://github.com/freesewing/freesewing/issues) or [pull request](https://github.com/freesewing/freesewing/pulls) using [the instructions for the all-contributors bot](https://allcontributors.org/docs/en/bot/usage). + + +Don't be shy, add yourself :) diff --git a/markdown/org/blog/all-contributors/nl.md b/markdown/org/blog/all-contributors/nl.md new file mode 100644 index 00000000000..00f556afdf2 --- /dev/null +++ b/markdown/org/blog/all-contributors/nl.md @@ -0,0 +1,35 @@ +--- +author: "joostdecock" +caption: "We're saying thanks to our contributors and want to make sure their contributions get the credit they deserve" +date: "2021-11-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1488bc5a9940423308a38d2cd33edb86b6eed442-1920x1280.jpg" +intro: "During our last contributor call , we decided that we would implement the All Contributors specification as a way to honour all our contributors." +title: "Calling all contributors [Niet vertaald]" +--- + +During [our last contributor call](https://github.com/freesewing/freesewing/issues/1514), we decided that we would implement the [All Contributors specification](https://allcontributors.org/) as a way to honour all our contributors. + +If on the surface, a contributor call decision to honour contributors sounds like some sort of self-serving nonsense, let me reassure you that there's no risk of dislocated shoulders from patting ourselves on the back. Instead it's about (also) honouring those contributions that tend to go overlooked in Open Source. + +The All Contributors website summerazes it as: + +> This is a specification for recognizing contributors to an open source project in a way that rewards each and every contribution, not just code. +> +> People are giving themselves and their free time to contribute to open source projects in so many ways, so we believe everyone should be praised for their contributions (code or not). + +When we talk about *contributors* in open source projects, there is often the assumption that this is all the people who contribute code to the project. The fact the [GitHub lists the contributors of a project based on the actual commits](https://github.com/freesewing/freesewing/graphs/contributors) goes a long way to cement that view. + +But there's plenty of contributions that fly under the radar of an automated system based on the commit history. Things like documentation and blog posts, community building, answering questions or submitting bug reports, are all valuable contributions that deserve to be recognized. + +By implementing the All Contributors specification, we pledge to give those people credit for their contributions, and make that credit visible. In practice the list of contributors will be included in the `README.md` file of all our packages, as well as in the main `README.md` file of [our `freesewing/freesewing` monorepo](https://github.com/freesewing/freesewing). + +In the future, we also plan to make this list available on our website. + +## How does it work? + +Going forward, we will make an effort to add all contributors regardless of how they contribute to the project. But we'd also like to capture contributions that were made up until now. + +For this, we need your help. If you've contributed to FreeSewing, let us know. You can [let us know on Discord](https://discord.freesewing.org/), or you can [create an issue](https://github.com/freesewing/freesewing/issues/new?assignees=joostdecock&labels=%F0%9F%92%9C+all+contributors&template=all-contributors.md&title=All+Contributors%3A+Please+add+%28username+here%29), or you can comment on [any issue](https://github.com/freesewing/freesewing/issues) or [pull request](https://github.com/freesewing/freesewing/pulls) using [the instructions for the all-contributors bot](https://allcontributors.org/docs/en/bot/usage). + + +Don't be shy, add yourself :) diff --git a/markdown/org/blog/annnouncing-yuri/de.md b/markdown/org/blog/annnouncing-yuri/de.md new file mode 100644 index 00000000000..6df59e00c38 --- /dev/null +++ b/markdown/org/blog/annnouncing-yuri/de.md @@ -0,0 +1,14 @@ +--- +author: "joostdecock" +caption: "Designer Hellgy struts their stuff, while their Yuri flows in a summer breeze" +date: "2021-09-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/af8e14596c0112734fb14e4a838853fb9dc0ac8a-1899x1266.jpg" +intro: "Announcing FreeSewing v2.18: Congratulations, it's a Yuri [Nicht übersetzt]" +title: "Announcing FreeSewing v2.18: Congratulations, it's a Yuri [Nicht übersetzt]" +--- + +I'm happy to announce the immediate availability of FreeSewing v2.18 and our latest addition to our catalog of designs: [The Yuri hoodie](/designs/yuri/) . +Designed by [Hellgy](https://twitter.com/hellgy) and coded by their bae [Biou](https://github.com/biou/), Yuri is everything they love about [our Huey hoodie](/designs/huey/) sans their arch enemy: zippers. + +Checkout [Hellgy's showcase for more pictures](/showcase/yuri-by-its-designer), or check out [the pattern page itself](/designs/yuri/) for all details. + diff --git a/markdown/org/blog/annnouncing-yuri/en.md b/markdown/org/blog/annnouncing-yuri/en.md new file mode 100644 index 00000000000..f228c4947ae --- /dev/null +++ b/markdown/org/blog/annnouncing-yuri/en.md @@ -0,0 +1,14 @@ +--- +author: "joostdecock" +caption: "Designer Hellgy struts their stuff, while their Yuri flows in a summer breeze" +date: "2021-09-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/af8e14596c0112734fb14e4a838853fb9dc0ac8a-1899x1266.jpg" +intro: "Announcing FreeSewing v2.18: Congratulations, it's a Yuri" +title: "Announcing FreeSewing v2.18: Congratulations, it's a Yuri" +--- + +I'm happy to announce the immediate availability of FreeSewing v2.18 and our latest addition to our catalog of designs: [The Yuri hoodie](/designs/yuri/) . +Designed by [Hellgy](https://twitter.com/hellgy) and coded by their bae [Biou](https://github.com/biou/), Yuri is everything they love about [our Huey hoodie](/designs/huey/) sans their arch enemy: zippers. + +Checkout [Hellgy's showcase for more pictures](/showcase/yuri-by-its-designer), or check out [the pattern page itself](/designs/yuri/) for all details. + diff --git a/markdown/org/blog/annnouncing-yuri/es.md b/markdown/org/blog/annnouncing-yuri/es.md new file mode 100644 index 00000000000..5330a0af708 --- /dev/null +++ b/markdown/org/blog/annnouncing-yuri/es.md @@ -0,0 +1,14 @@ +--- +author: "joostdecock" +caption: "Designer Hellgy struts their stuff, while their Yuri flows in a summer breeze" +date: "2021-09-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/af8e14596c0112734fb14e4a838853fb9dc0ac8a-1899x1266.jpg" +intro: "Announcing FreeSewing v2.18: Congratulations, it's a Yuri [No traducido]" +title: "Announcing FreeSewing v2.18: Congratulations, it's a Yuri [No traducido]" +--- + +I'm happy to announce the immediate availability of FreeSewing v2.18 and our latest addition to our catalog of designs: [The Yuri hoodie](/designs/yuri/) . +Designed by [Hellgy](https://twitter.com/hellgy) and coded by their bae [Biou](https://github.com/biou/), Yuri is everything they love about [our Huey hoodie](/designs/huey/) sans their arch enemy: zippers. + +Checkout [Hellgy's showcase for more pictures](/showcase/yuri-by-its-designer), or check out [the pattern page itself](/designs/yuri/) for all details. + diff --git a/markdown/org/blog/annnouncing-yuri/fr.md b/markdown/org/blog/annnouncing-yuri/fr.md new file mode 100644 index 00000000000..8e3c1d7ff86 --- /dev/null +++ b/markdown/org/blog/annnouncing-yuri/fr.md @@ -0,0 +1,14 @@ +--- +author: "joostdecock" +caption: "Designer Hellgy struts their stuff, while their Yuri flows in a summer breeze" +date: "2021-09-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/af8e14596c0112734fb14e4a838853fb9dc0ac8a-1899x1266.jpg" +intro: "Announcing FreeSewing v2.18: Congratulations, it's a Yuri [Non traduit]" +title: "Announcing FreeSewing v2.18: Congratulations, it's a Yuri [Non traduit]" +--- + +I'm happy to announce the immediate availability of FreeSewing v2.18 and our latest addition to our catalog of designs: [The Yuri hoodie](/designs/yuri/) . +Designed by [Hellgy](https://twitter.com/hellgy) and coded by their bae [Biou](https://github.com/biou/), Yuri is everything they love about [our Huey hoodie](/designs/huey/) sans their arch enemy: zippers. + +Checkout [Hellgy's showcase for more pictures](/showcase/yuri-by-its-designer), or check out [the pattern page itself](/designs/yuri/) for all details. + diff --git a/markdown/org/blog/annnouncing-yuri/nl.md b/markdown/org/blog/annnouncing-yuri/nl.md new file mode 100644 index 00000000000..ac34099d02e --- /dev/null +++ b/markdown/org/blog/annnouncing-yuri/nl.md @@ -0,0 +1,14 @@ +--- +author: "joostdecock" +caption: "Designer Hellgy struts their stuff, while their Yuri flows in a summer breeze" +date: "2021-09-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/af8e14596c0112734fb14e4a838853fb9dc0ac8a-1899x1266.jpg" +intro: "Announcing FreeSewing v2.18: Congratulations, it's a Yuri [Niet vertaald]" +title: "Announcing FreeSewing v2.18: Congratulations, it's a Yuri [Niet vertaald]" +--- + +I'm happy to announce the immediate availability of FreeSewing v2.18 and our latest addition to our catalog of designs: [The Yuri hoodie](/designs/yuri/) . +Designed by [Hellgy](https://twitter.com/hellgy) and coded by their bae [Biou](https://github.com/biou/), Yuri is everything they love about [our Huey hoodie](/designs/huey/) sans their arch enemy: zippers. + +Checkout [Hellgy's showcase for more pictures](/showcase/yuri-by-its-designer), or check out [the pattern page itself](/designs/yuri/) for all details. + diff --git a/markdown/org/blog/announcing-carlita/de.md b/markdown/org/blog/announcing-carlita/de.md new file mode 100644 index 00000000000..836296be67d --- /dev/null +++ b/markdown/org/blog/announcing-carlita/de.md @@ -0,0 +1,88 @@ +--- +author: "joostdecock" +caption: "Picture you and him, in matching coats." +date: "2018-01-26" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d0ac31adcf8e14cec377aada6c688394a15199d8-1920x1440.webp" +intro: "This one's for the ladies --- and I'm not (just) talking about that picture of heart-throb Benedict Cumberbatch at the top of this post." +title: "Announcing Carlita, the womenswear version of our Carlton coat. [Nicht übersetzt]" +--- + +This one's for the ladies --- and I'm not (just) talking about that picture of heart-throb Benedict Cumberbatch at the top of this post. + +Instead, I'm talking about the release of our latest pattern: +the [Carlita Coat](/patterns/carlita) which is out in beta as of today. + +Carlita is --- you guessed it --- the womenswear version of our Carlton coat, which recreates the iconic Sherlock +Holmes coat worn by BC on the BBC series. + +## How did we do it? + +For details on how this project came to be, +I refer you to [the Carlton announcement post](/blog/announcing-carlton-and-bent/). +Here, I'd like to focus on the specifics of how we turned this menswear pattern into a coat for ladies. + +We wanted to stay as close to the original as possible, so all we did was make changes to address +one challenge: fitting the breasts. + +### Princess, meet your seam + +We drew an extra princess seam in the front panel of the coat, through which we added shaping for the bust. + +To be able to do that accurately, Carlita requires three extra measurements in addition to the measurements required by Carlton. They are: + + - The [high bust](/docs/measurements/#highBust) + - The [bust span](/docs/measurements/#bustSpan) + - The [high point shoulder to bust](/docs/measurements/#highPointShoulderToBust) + +We use your high bust measurements to draft the coat, and then do a full bust adjustment on the +princess seam based on your (full) chest circumference, bust span and HPS to bust. + +### All of the pockets, but we had to move some of them + +The addition of the princess seam made the map pocket placement a bit difficult, +so we've slightly moved it, and aligned it vertically, rather than slightly tilted as it is in Carlton. + +This way, the pocket can be integrated in the princess seam, somewhere in the underboob region. + +### One extra option: The princess seam smooth factor + +Carlita also has one extra option that Carlton doesn't have, the somewhat elaborately named +[Princess seam smooth factor](/docs/patterns/carlita/options#princessSeamSmoothFactor). + +This controls how sharply the princess seam will revert back after having added the extra volume for your chest. + +A picture says more than a thousand words, so here's the option sampled on the relevant part of the pattern: + +![The effect of the option as shown by our sampler service](https://posts.freesewing.org/uploads/smooth_e8f395dd4a.png) + +As you can see, the option controls the urgency with which the princess seam reverts back to your waistline +after passing the fullest point of your bust. + +A low factor will make for a more fitted coat, but also a more curvy seam that is harder to sew. + +A higher smooth factor will smooth this out so it's a more sloped retreat to the downward seam. +This will make the coat less fitted under your chest, and the seam easier to sew. + +## A reminder about made-to-measure patterns + +This goes without saying for regular visitors to this site, but if you're new here, it's worth repeating: + +> This coat is not drafted with a certain cup size in mind. Instead, it will adapt to your chest based on your measurements. + +## Ladies, we need your feedback + +This is our first womenswear pattern with a fitted chest. +As such, we're breaking new ground here, and I'd be interested to see how this pattern adapts to a variety of body shapes/cup sizes. + +If you're planning to make this coat, or a muslin of it, please share your experience, and don't hesitate to get in +touch should you run into any issues. + + +I plan to design more womenswear patterns, so if there are any fit issues, I'd like to know about it sooner rather than later. + +## Shout-out + +Last but not least, I'd like to thank [Anneke](http://www.annekecaramin.com/) for her help throughout this project, and tolerating my countless rants about +my love/hate relationship with boobs. + + diff --git a/markdown/org/blog/announcing-carlita/en.md b/markdown/org/blog/announcing-carlita/en.md new file mode 100644 index 00000000000..611f1542371 --- /dev/null +++ b/markdown/org/blog/announcing-carlita/en.md @@ -0,0 +1,88 @@ +--- +author: "joostdecock" +caption: "Picture you and him, in matching coats." +date: "2018-01-26" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d0ac31adcf8e14cec377aada6c688394a15199d8-1920x1440.webp" +intro: "This one's for the ladies --- and I'm not (just) talking about that picture of heart-throb Benedict Cumberbatch at the top of this post." +title: "Announcing Carlita, the womenswear version of our Carlton coat." +--- + +This one's for the ladies --- and I'm not (just) talking about that picture of heart-throb Benedict Cumberbatch at the top of this post. + +Instead, I'm talking about the release of our latest pattern: +the [Carlita Coat](/patterns/carlita) which is out in beta as of today. + +Carlita is --- you guessed it --- the womenswear version of our Carlton coat, which recreates the iconic Sherlock +Holmes coat worn by BC on the BBC series. + +## How did we do it? + +For details on how this project came to be, +I refer you to [the Carlton announcement post](/blog/announcing-carlton-and-bent/). +Here, I'd like to focus on the specifics of how we turned this menswear pattern into a coat for ladies. + +We wanted to stay as close to the original as possible, so all we did was make changes to address +one challenge: fitting the breasts. + +### Princess, meet your seam + +We drew an extra princess seam in the front panel of the coat, through which we added shaping for the bust. + +To be able to do that accurately, Carlita requires three extra measurements in addition to the measurements required by Carlton. They are: + + - The [high bust](/docs/measurements/#highBust) + - The [bust span](/docs/measurements/#bustSpan) + - The [high point shoulder to bust](/docs/measurements/#highPointShoulderToBust) + +We use your high bust measurements to draft the coat, and then do a full bust adjustment on the +princess seam based on your (full) chest circumference, bust span and HPS to bust. + +### All of the pockets, but we had to move some of them + +The addition of the princess seam made the map pocket placement a bit difficult, +so we've slightly moved it, and aligned it vertically, rather than slightly tilted as it is in Carlton. + +This way, the pocket can be integrated in the princess seam, somewhere in the underboob region. + +### One extra option: The princess seam smooth factor + +Carlita also has one extra option that Carlton doesn't have, the somewhat elaborately named +[Princess seam smooth factor](/docs/patterns/carlita/options#princessSeamSmoothFactor). + +This controls how sharply the princess seam will revert back after having added the extra volume for your chest. + +A picture says more than a thousand words, so here's the option sampled on the relevant part of the pattern: + +![The effect of the option as shown by our sampler service](https://posts.freesewing.org/uploads/smooth_e8f395dd4a.png) + +As you can see, the option controls the urgency with which the princess seam reverts back to your waistline +after passing the fullest point of your bust. + +A low factor will make for a more fitted coat, but also a more curvy seam that is harder to sew. + +A higher smooth factor will smooth this out so it's a more sloped retreat to the downward seam. +This will make the coat less fitted under your chest, and the seam easier to sew. + +## A reminder about made-to-measure patterns + +This goes without saying for regular visitors to this site, but if you're new here, it's worth repeating: + +> This coat is not drafted with a certain cup size in mind. Instead, it will adapt to your chest based on your measurements. + +## Ladies, we need your feedback + +This is our first womenswear pattern with a fitted chest. +As such, we're breaking new ground here, and I'd be interested to see how this pattern adapts to a variety of body shapes/cup sizes. + +If you're planning to make this coat, or a muslin of it, please share your experience, and don't hesitate to get in +touch should you run into any issues. + + +I plan to design more womenswear patterns, so if there are any fit issues, I'd like to know about it sooner rather than later. + +## Shout-out + +Last but not least, I'd like to thank [Anneke](http://www.annekecaramin.com/) for her help throughout this project, and tolerating my countless rants about +my love/hate relationship with boobs. + + diff --git a/markdown/org/blog/announcing-carlita/es.md b/markdown/org/blog/announcing-carlita/es.md new file mode 100644 index 00000000000..4793fa8bd8d --- /dev/null +++ b/markdown/org/blog/announcing-carlita/es.md @@ -0,0 +1,88 @@ +--- +author: "joostdecock" +caption: "Picture you and him, in matching coats." +date: "2018-01-26" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d0ac31adcf8e14cec377aada6c688394a15199d8-1920x1440.webp" +intro: "This one's for the ladies --- and I'm not (just) talking about that picture of heart-throb Benedict Cumberbatch at the top of this post." +title: "Announcing Carlita, the womenswear version of our Carlton coat. [No traducido]" +--- + +This one's for the ladies --- and I'm not (just) talking about that picture of heart-throb Benedict Cumberbatch at the top of this post. + +Instead, I'm talking about the release of our latest pattern: +the [Carlita Coat](/patterns/carlita) which is out in beta as of today. + +Carlita is --- you guessed it --- the womenswear version of our Carlton coat, which recreates the iconic Sherlock +Holmes coat worn by BC on the BBC series. + +## How did we do it? + +For details on how this project came to be, +I refer you to [the Carlton announcement post](/blog/announcing-carlton-and-bent/). +Here, I'd like to focus on the specifics of how we turned this menswear pattern into a coat for ladies. + +We wanted to stay as close to the original as possible, so all we did was make changes to address +one challenge: fitting the breasts. + +### Princess, meet your seam + +We drew an extra princess seam in the front panel of the coat, through which we added shaping for the bust. + +To be able to do that accurately, Carlita requires three extra measurements in addition to the measurements required by Carlton. They are: + + - The [high bust](/docs/measurements/#highBust) + - The [bust span](/docs/measurements/#bustSpan) + - The [high point shoulder to bust](/docs/measurements/#highPointShoulderToBust) + +We use your high bust measurements to draft the coat, and then do a full bust adjustment on the +princess seam based on your (full) chest circumference, bust span and HPS to bust. + +### All of the pockets, but we had to move some of them + +The addition of the princess seam made the map pocket placement a bit difficult, +so we've slightly moved it, and aligned it vertically, rather than slightly tilted as it is in Carlton. + +This way, the pocket can be integrated in the princess seam, somewhere in the underboob region. + +### One extra option: The princess seam smooth factor + +Carlita also has one extra option that Carlton doesn't have, the somewhat elaborately named +[Princess seam smooth factor](/docs/patterns/carlita/options#princessSeamSmoothFactor). + +This controls how sharply the princess seam will revert back after having added the extra volume for your chest. + +A picture says more than a thousand words, so here's the option sampled on the relevant part of the pattern: + +![The effect of the option as shown by our sampler service](https://posts.freesewing.org/uploads/smooth_e8f395dd4a.png) + +As you can see, the option controls the urgency with which the princess seam reverts back to your waistline +after passing the fullest point of your bust. + +A low factor will make for a more fitted coat, but also a more curvy seam that is harder to sew. + +A higher smooth factor will smooth this out so it's a more sloped retreat to the downward seam. +This will make the coat less fitted under your chest, and the seam easier to sew. + +## A reminder about made-to-measure patterns + +This goes without saying for regular visitors to this site, but if you're new here, it's worth repeating: + +> This coat is not drafted with a certain cup size in mind. Instead, it will adapt to your chest based on your measurements. + +## Ladies, we need your feedback + +This is our first womenswear pattern with a fitted chest. +As such, we're breaking new ground here, and I'd be interested to see how this pattern adapts to a variety of body shapes/cup sizes. + +If you're planning to make this coat, or a muslin of it, please share your experience, and don't hesitate to get in +touch should you run into any issues. + + +I plan to design more womenswear patterns, so if there are any fit issues, I'd like to know about it sooner rather than later. + +## Shout-out + +Last but not least, I'd like to thank [Anneke](http://www.annekecaramin.com/) for her help throughout this project, and tolerating my countless rants about +my love/hate relationship with boobs. + + diff --git a/markdown/org/blog/announcing-carlita/fr.md b/markdown/org/blog/announcing-carlita/fr.md new file mode 100644 index 00000000000..2af8a0504a7 --- /dev/null +++ b/markdown/org/blog/announcing-carlita/fr.md @@ -0,0 +1,76 @@ +--- +author: "joostdecock" +caption: "Imaginez vous et lui, dans des manteaux assortis." +date: "2018-01-26" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d0ac31adcf8e14cec377aada6c688394a15199d8-1920x1440.webp" +intro: "Celui-ci est pour les dames -- et je ne parle pas (juste) de cette image du craquant Benoît Cumberbatch en haut de l'article." +title: "Annonce de Carlita, la version féminine de notre manteau Carlton." +--- + + +Celui-ci est pour les dames -- et je ne parle pas (juste) de cette image du craquant Benoît Cumberbatch en haut de l'article. + +Je parles plutôt de la publication de notre dernier parton : le [Manteau Carlita](/patterns/carlita) qui est sorti en version bêta à compter d'aujourd'hui. + +Carlita est -- vous l'avez deviné -- la version féminine de notre manteau Carlton, qui recrée l'emblématique manteau de Sherlock Holmes porté par Benoit C. dans la série sur BBC. + +## Comment y sommes-nous parvenus ? + +Pour plus de détails sur la manière dont ce projet est né, je vous renvoie à [l'article sur annonce de Carlton](/blog/announcing-carlton-and-bent/). Je voudrais ici me concentrer sur la façon dont nous avons transformé ce patron masculin en manteau pour dames. + +Nous voulions rester aussi près que possible de l'original donc tout ce que nous avons fait a été de faire des changements pour répondre à un seul défi : ajuster à la forme des seins. + +### Princesse, ajustez vos découpes + +Nous avons dessiné une découpe princesse supplémentaire sur le panneau avant du manteau, par laquelle nous avons ajouté du galbe pour le buste. + +Pour pouvoir le faire avec précision, Carlita nécessite trois mesures supplémentaires en plus des mesures requises par Carlton. Il y a : + + - Le [tour de buste supérieur](/docs/measurements/#highBust) + - L'[écart de poitrine](/docs/measurements/bustSpan) + - La [longueur devant depuis l'épaule](/docs/measurements/hpstohipsfront) + +Nous utilisons vos mensurations de buste supérieur (dessus poitrine) pour dessiner le manteau, puis effectuons un "Full Bust Adjustment (FBA)" (ajustement complet de poitrine) sur les découpes princesse en fonction de votre tour (complet) de poitrine, de l'écart de poitrine et de la longueur devant depuis l'épaule. + +### Toutes les poches, mais nous avons dû en déplacer certaines + +L'ajout des découpes princesse a rendu le placement de la poche poitrine un peu difficile, donc nous l'avons légèrement déplacée et alignée verticalement, plutôt que légèrement inclinée comme sur Carlton. + +De cette façon, la poche peut être intégrée dans la découpe princesse un peu plus bas sous la poitrine. + +### Une option supplémentaire : L'intensité de la découpe princesse + +Carlita a aussi une option supplémentaire que Carlton n'a pas, du nom un peu élaboré [Intensité de la découpe princesse](/docs/patterns/carlita/options#princessSeamSmoothFactor). + +Cette option permet de régler la netteté de la découpe princesse après avoir ajouté le volume supplémentaire de votre poitrine. + +Une image en dit plus que mille mots, donc voici une illustration de l'option sur la partie concernée du modèle : + +![L'effet de l'option comme le montre notre exemple](smooth.png) + +Comme vous pouvez le voir, l'option gère la "rapidité" avec laquelle la découpe princesse rejoint votre taille après avoir passé le point le plus large de votre buste. + +Une faible intensité permettra un manteau plus ajusté, mais aussi une couture plus courbée plus difficile à coudre. + +Une intensité plus lisse permettra de lisser la découpe de façon à ce qu'elle fasse un repli plus incliné vers la couture descendante. Cela rendra le manteau moins ajusté sous votre poitrine mais la couture plus facile à coudre. + +## Un rappel à propos des patrons sur-mesure + +Cela va sans dire pour les visiteurs réguliers de ce site, mais si vous êtes nouveau ici, cela vaut la peine d'être répété : + +> Ce manteau n'est pas conçu pour une certaine taille de bonnet prédéfini. Au lieu de cela, il s’adaptera à votre poitrine en fonction de vos mesures. + +## Mesdames, nous avons besoin de vos avis + +Il s'agit de notre premier modèle de vêtement féminin avec un ajustement poitrine. En tant que tel, nous innovons ici, et je serais intéressé de voir comment ce modèle s'adapte à une variété de morphologies/tailles de bonnet. + +Si vous prévoyez de fabriquer ce manteau, veuillez partager votre expérience, et n'hésitez pas à nous contacter si vous rencontrez des problèmes. + + +Je prévois de concevoir plus de modèles de vêtements féminins, donc s'il y a des problèmes de tombé ou d'ajustement, je voudrais le savoir le plus tôt possible. + +## Dédicace spéciale + +Enfin et surtout, je voudrais remercier [Anneke](http://www.annekecaramin.com/) pour son aide tout au long de ce projet et d'avoir toléré le nombre incalculable de fois où j'ai pesté à propos de ma relation amour/haine avec les seins. + + diff --git a/markdown/org/blog/announcing-carlita/nl.md b/markdown/org/blog/announcing-carlita/nl.md new file mode 100644 index 00000000000..bc1c332c085 --- /dev/null +++ b/markdown/org/blog/announcing-carlita/nl.md @@ -0,0 +1,76 @@ +--- +author: "joostdecock" +caption: "Beeld je naast hem in, met een matchende jas." +date: "2018-01-26" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d0ac31adcf8e14cec377aada6c688394a15199d8-1920x1440.webp" +intro: "Deze is voor de dames - en ik heb het niet (alleen) over die foto van hartenbreker Benedict Cumberbatch bovenaan deze post." +title: "We presenteren Carlita, de damesversie van onze Carlton jas." +--- + + +Deze is voor de dames - en ik heb het niet (alleen) over die foto van hartenbreker Benedict Cumberbatch bovenaan deze post. + +Ik heb het namelijk over de publicatie van ons laatste patroon: de [Carlita jas](/patterns/carlita), waarvan de betaversie vanaf vandaag beschikbaar is. + +Carlita is - ja raadt het nooit - de damensversie van onze Carlton jas, die een recreatie is van de iconische Sherlock Holmes jas, gedragen door BC in de BBC-serie. + +## Hoe hebben we dit gedaan? + +Voor details over het ontstaan van dit project verwijs ik je door naar de post [waarmee we Carlton aankondigden](/blog/announcing-carlton-and-bent/). Hier zou ik het liefst focussen op de specifieke dingen die we gedaan hebben om van dit herenpatroon een damesversie te maken. + +We wilden zo dicht mogelijk bij het origineel blijven, dus al wat we deden was dingen aanpassen om één uitdaging aan te gaan: passen voor iemand met borsten. + +### Prinses, ontmoet je naad + +We hebben een extra prinsessennaad toegevoegd aan het voorpand van de jas, en op deze manier ruimte voor de buste gemaakt. + +Om dat accuraat te doen heb je voor Carlita drie extra maten nodig, naast de maten die je al nodig had voor Carlton. Dit zijn: + + - De [hoge buste](/docs/measurements/#highBust) + - De [bustewijdte](/docs/measurements/#bustSpan) + - [Hoog schouder punt tot buste](/docs/measurements/#highPointShoulderToBust) + +We gebruiken de omtrek van de hoge buste om de jas te tekenen, en doen dan een aanpassing voor volle buste aan de prinsessennaad gebaseerd op je (volle) borstomtrek, bustewijdte en HSP tot buste. + +### Alle zakken, al hebben we ze wat moeten verplaatsen + +De toevoeging van de prinsessennaad maakte de plaatsing van de voorzak een beetje moeilijk, dus we hebben hem lichtjes verplaatst en verticaal gezet, in plaats van op een lichte diagonaal zoals bij Carlton. + +Op deze manier kan de zak geïntegreerd worden in de prinsessennaad, ergens onder je borsten. + +### Eén extra optie: De prinsessennaad ronding factor + +Carlita heeft ook een extra optie die Carlton niet heeft, de ietwat uitgebreid genaamde [prinsessennaad ronding factor](/docs/patterns/carlita/options#princessSeamSmoothFactor). + +Dit controleert hoe scherp de prinsessennaad terug naar binnen keert na het extra volume aan de buste te hebben toegevoegd. + +Een foto zegt meer dan duizend woorden, dus hier is de optie aangeduid op het relevante patroondeel: + +![Het effect van de optie zoals getoond door onze sample service](smooth.png) + +Zoals je kan zien controleert deze optie hoe fel de prinsessennaad terug naar je taille keert nadat ze over het volste deel van de buste gegaan is. + +Een lage factor zorgt voor een meer aansluitende jas, maar ook voor een fellere curve en een naad die moeilijker te naaien is. + +Een hogere ronding factor maakt dit minder fel zodat de overgang naar het lagere deel van de naad zachter verloopt. Dit maakt de jas iets minder aansluitend onder de buste, en de naad makkelijker te naaien. + +## Een herinnering over patronen op maat + +Dit is geen nieuws voor regelmatige bezoekers van deze website, maar als je hier nieuw bent is het de moeite om dit nog eens te horen: + +> Deze jas is niet getekend met een bepaalde cupmaat in het achterhoofd. In plaats daarvan past het patroon zich aan jouw borst aan, gebaseerd op jouw afmetingen. + +## Dames, laat van je horen + +Dit is ons eerste damespatroon met een aanpassende buste. Het is dus nieuw terrein voor ons, en ik wil graag weten hoe dit patroon zich aanpast aan een variëteit in lichaamsvormen en cupmaten. + +Als je van plan bent om deze jas te maken, of een toile, deel dan alsjeblieft je ervaring en aarzel niet ons te contacteren mocht je een probleem tegenkomen. + + +Het is mijn bedoeling meer damespatronen te ontwerpen, dus als er pasproblemen zijn hoor ik daar liever vroeger dan later over. + +## Shout-out + +Als laatste wil ik graag [Anneke](http://www.annekecaramin.com/) bedanken voor haar hulp tijdens dit project en het tolereren van mijn eindeloze tirades over mijn haat/liefde relatie met borsten. + + diff --git a/markdown/org/blog/announcing-carlton-and-bent/de.md b/markdown/org/blog/announcing-carlton-and-bent/de.md new file mode 100644 index 00000000000..1b73ce15c8f --- /dev/null +++ b/markdown/org/blog/announcing-carlton-and-bent/de.md @@ -0,0 +1,86 @@ +--- +author: "joostdecock" +caption: "You too can wear this coat. Although you're on your own for the hat. At least for now." +date: "2017-12-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/01c201b14f04bedbe2630bb3bd40d925fd6c1ce4-3500x2333.jpg" +intro: "Announcing Carlton, aka the Sherlock Holmes coat, and the Bent Body Block [Nicht übersetzt]" +title: "Announcing Carlton, aka the Sherlock Holmes coat, and the Bent Body Block [Nicht übersetzt]" +--- + +Good news everybody, we've got your cosplaying needs covered. That is, if you are cosplaying as Sherlock Holmes. +Our newest pattern release, [the Carlton Coat](/patterns/carlton) is exactly what the doctor prescribed if for some weird reason +your doctor wants you to look like everyone's favorite detective. + +My memory is foggy on the exact origin of this endeavor. It probably involved +me complaining about the cold and my lack of a warm winter coat, but apart from that, I'm not too sure. + +What I do remember is that at one point, +[Anneke](http://www.annekecaramin.com/) and myself decided that we would reverse-engineer the Sherlock Holmes coat. +More specifically, the coat worn by Benedict Cumberbatch in the BBC series Sherlock Holmes. + +![That coat though](https://posts.freesewing.org/uploads/bc_f20e01a16d.jpg) + +The coat is popular with cosplayers for obvious reasons, but it's also just a really nice coat, and +other brave souls [such as Melissa](http://blog.fehrtrade.com/gallery/868/the-sherlock-coat/) have tried their hand at it. + +I must admit that I didn't know Melissa made a similar coat until mine was finished. Furthermore, her blog post +mentions that she used the instructions in a livejournal post that is no longer available. + +Anneke and myself did no such thing and just put the pattern together based on screengrabs from the TV show. +We're hardcore like that. + +### About the coat + +Carlton is a double-breasted long overcoat in the tradition of horseback uniform coats +where the back of the coat isn't split, but rather has wide pleats that can drape over the back of the horse. +Or, more realistically, fan open behind you as you walk about. + +![Front view of Carlton on yours truly](https://posts.freesewing.org/uploads/front_e1d64f3ceb.jpg) +![Back view of Carlton on yours truly](https://posts.freesewing.org/uploads/back_05c04878c5.jpg) + +It comes with two patch pockets on the front, two map pockets at the chest, and two inner pockets. +Six pockets in total, so you'll have plenty of room for all your belongings. + +![Map and patch pockets on the outside](https://posts.freesewing.org/uploads/pockets_28099d1afe.jpg) +![Inner pockets on the inside](https://posts.freesewing.org/uploads/innerpocket_4e4e3f5119.jpg) + +I finished mine just in time for a trip to Köln to visit my beloved friend and tailor +[Sebastian Hoofs](http://sebastian-hoofs.de/massschneider/). +It was cold as eff over there, but the coat kept me nice and warm. Not surprising since it's made in a hefty +wool I picked up in [Bacci in Florence](http://www.baccitessuti.it/en/index.html) over the summer, and I took +the extra step of interlining it with French terry (I really don't like to be cold). + +![I have no affiliation with Bacci, I'm just a sucker for great fabric stores](https://posts.freesewing.org/uploads/bacci_043f91c96c.jpg) +![You can see the terry interlining where I peeled back the sleeve lining](https://posts.freesewing.org/uploads/interlining_220e0eab71.jpg) + +### Burn the patriarchy to the ground through the power of pockets + +Ladies take note: Carlita --- a female version of Carlton --- is currently on the drawing board. + +Initially, the plan was to release male and female versions side by side, but adapting the coat +has proven to be more involved than anticipated because, well, because boobs. + +I also feel like I have to +keep too many plates spinning right now, so I'm hopeful that getting Carlton out the door will +create some time/space to make Carlita follow soon(ish). Either way, I've promised Anneke that we'd +do a female version, and [she's a freesewing Captain now](/patrons), so I intend to keep that promise. + +Oh, and about that title: When Carlita's ready, she will have just as many pockets as Carlton. + +## Also, this: Introducing the Bent Body Block +We're actually releasing two patterns today. Apart from the Carlton Coat, there's also +the [Bent Body Block](/patterns/bent). + +Bent is a two-part sleeve variation of our [Brian Body Block](/patterns/bent). It's essentially a base +for coat and jacket patterns for menswear. + +I originally designed Bent as a base for my [refashioners 2017 zebra jacket](/blog/the-refashioners-2017/), +so you can expect that jacket pattern to also hit the site in the coming months. + +Carlton is also based on Bent, so we're giving you both today. + +Have wonderful and happy holidays if you're into that kind of thing. And happy making! + + + + diff --git a/markdown/org/blog/announcing-carlton-and-bent/en.md b/markdown/org/blog/announcing-carlton-and-bent/en.md new file mode 100644 index 00000000000..e4362a961e6 --- /dev/null +++ b/markdown/org/blog/announcing-carlton-and-bent/en.md @@ -0,0 +1,86 @@ +--- +author: "joostdecock" +caption: "You too can wear this coat. Although you're on your own for the hat. At least for now." +date: "2017-12-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/01c201b14f04bedbe2630bb3bd40d925fd6c1ce4-3500x2333.jpg" +intro: "Announcing Carlton, aka the Sherlock Holmes coat, and the Bent Body Block" +title: "Announcing Carlton, aka the Sherlock Holmes coat, and the Bent Body Block" +--- + +Good news everybody, we've got your cosplaying needs covered. That is, if you are cosplaying as Sherlock Holmes. +Our newest pattern release, [the Carlton Coat](/patterns/carlton) is exactly what the doctor prescribed if for some weird reason +your doctor wants you to look like everyone's favorite detective. + +My memory is foggy on the exact origin of this endeavor. It probably involved +me complaining about the cold and my lack of a warm winter coat, but apart from that, I'm not too sure. + +What I do remember is that at one point, +[Anneke](http://www.annekecaramin.com/) and myself decided that we would reverse-engineer the Sherlock Holmes coat. +More specifically, the coat worn by Benedict Cumberbatch in the BBC series Sherlock Holmes. + +![That coat though](https://posts.freesewing.org/uploads/bc_f20e01a16d.jpg) + +The coat is popular with cosplayers for obvious reasons, but it's also just a really nice coat, and +other brave souls [such as Melissa](http://blog.fehrtrade.com/gallery/868/the-sherlock-coat/) have tried their hand at it. + +I must admit that I didn't know Melissa made a similar coat until mine was finished. Furthermore, her blog post +mentions that she used the instructions in a livejournal post that is no longer available. + +Anneke and myself did no such thing and just put the pattern together based on screengrabs from the TV show. +We're hardcore like that. + +### About the coat + +Carlton is a double-breasted long overcoat in the tradition of horseback uniform coats +where the back of the coat isn't split, but rather has wide pleats that can drape over the back of the horse. +Or, more realistically, fan open behind you as you walk about. + +![Front view of Carlton on yours truly](https://posts.freesewing.org/uploads/front_e1d64f3ceb.jpg) +![Back view of Carlton on yours truly](https://posts.freesewing.org/uploads/back_05c04878c5.jpg) + +It comes with two patch pockets on the front, two map pockets at the chest, and two inner pockets. +Six pockets in total, so you'll have plenty of room for all your belongings. + +![Map and patch pockets on the outside](https://posts.freesewing.org/uploads/pockets_28099d1afe.jpg) +![Inner pockets on the inside](https://posts.freesewing.org/uploads/innerpocket_4e4e3f5119.jpg) + +I finished mine just in time for a trip to Köln to visit my beloved friend and tailor +[Sebastian Hoofs](http://sebastian-hoofs.de/massschneider/). +It was cold as eff over there, but the coat kept me nice and warm. Not surprising since it's made in a hefty +wool I picked up in [Bacci in Florence](http://www.baccitessuti.it/en/index.html) over the summer, and I took +the extra step of interlining it with French terry (I really don't like to be cold). + +![I have no affiliation with Bacci, I'm just a sucker for great fabric stores](https://posts.freesewing.org/uploads/bacci_043f91c96c.jpg) +![You can see the terry interlining where I peeled back the sleeve lining](https://posts.freesewing.org/uploads/interlining_220e0eab71.jpg) + +### Burn the patriarchy to the ground through the power of pockets + +Ladies take note: Carlita --- a female version of Carlton --- is currently on the drawing board. + +Initially, the plan was to release male and female versions side by side, but adapting the coat +has proven to be more involved than anticipated because, well, because boobs. + +I also feel like I have to +keep too many plates spinning right now, so I'm hopeful that getting Carlton out the door will +create some time/space to make Carlita follow soon(ish). Either way, I've promised Anneke that we'd +do a female version, and [she's a freesewing Captain now](/patrons), so I intend to keep that promise. + +Oh, and about that title: When Carlita's ready, she will have just as many pockets as Carlton. + +## Also, this: Introducing the Bent Body Block +We're actually releasing two patterns today. Apart from the Carlton Coat, there's also +the [Bent Body Block](/patterns/bent). + +Bent is a two-part sleeve variation of our [Brian Body Block](/patterns/bent). It's essentially a base +for coat and jacket patterns for menswear. + +I originally designed Bent as a base for my [refashioners 2017 zebra jacket](/blog/the-refashioners-2017/), +so you can expect that jacket pattern to also hit the site in the coming months. + +Carlton is also based on Bent, so we're giving you both today. + +Have wonderful and happy holidays if you're into that kind of thing. And happy making! + + + + diff --git a/markdown/org/blog/announcing-carlton-and-bent/es.md b/markdown/org/blog/announcing-carlton-and-bent/es.md new file mode 100644 index 00000000000..eaab94287df --- /dev/null +++ b/markdown/org/blog/announcing-carlton-and-bent/es.md @@ -0,0 +1,86 @@ +--- +author: "joostdecock" +caption: "You too can wear this coat. Although you're on your own for the hat. At least for now." +date: "2017-12-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/01c201b14f04bedbe2630bb3bd40d925fd6c1ce4-3500x2333.jpg" +intro: "Announcing Carlton, aka the Sherlock Holmes coat, and the Bent Body Block [No traducido]" +title: "Announcing Carlton, aka the Sherlock Holmes coat, and the Bent Body Block [No traducido]" +--- + +Good news everybody, we've got your cosplaying needs covered. That is, if you are cosplaying as Sherlock Holmes. +Our newest pattern release, [the Carlton Coat](/patterns/carlton) is exactly what the doctor prescribed if for some weird reason +your doctor wants you to look like everyone's favorite detective. + +My memory is foggy on the exact origin of this endeavor. It probably involved +me complaining about the cold and my lack of a warm winter coat, but apart from that, I'm not too sure. + +What I do remember is that at one point, +[Anneke](http://www.annekecaramin.com/) and myself decided that we would reverse-engineer the Sherlock Holmes coat. +More specifically, the coat worn by Benedict Cumberbatch in the BBC series Sherlock Holmes. + +![That coat though](https://posts.freesewing.org/uploads/bc_f20e01a16d.jpg) + +The coat is popular with cosplayers for obvious reasons, but it's also just a really nice coat, and +other brave souls [such as Melissa](http://blog.fehrtrade.com/gallery/868/the-sherlock-coat/) have tried their hand at it. + +I must admit that I didn't know Melissa made a similar coat until mine was finished. Furthermore, her blog post +mentions that she used the instructions in a livejournal post that is no longer available. + +Anneke and myself did no such thing and just put the pattern together based on screengrabs from the TV show. +We're hardcore like that. + +### About the coat + +Carlton is a double-breasted long overcoat in the tradition of horseback uniform coats +where the back of the coat isn't split, but rather has wide pleats that can drape over the back of the horse. +Or, more realistically, fan open behind you as you walk about. + +![Front view of Carlton on yours truly](https://posts.freesewing.org/uploads/front_e1d64f3ceb.jpg) +![Back view of Carlton on yours truly](https://posts.freesewing.org/uploads/back_05c04878c5.jpg) + +It comes with two patch pockets on the front, two map pockets at the chest, and two inner pockets. +Six pockets in total, so you'll have plenty of room for all your belongings. + +![Map and patch pockets on the outside](https://posts.freesewing.org/uploads/pockets_28099d1afe.jpg) +![Inner pockets on the inside](https://posts.freesewing.org/uploads/innerpocket_4e4e3f5119.jpg) + +I finished mine just in time for a trip to Köln to visit my beloved friend and tailor +[Sebastian Hoofs](http://sebastian-hoofs.de/massschneider/). +It was cold as eff over there, but the coat kept me nice and warm. Not surprising since it's made in a hefty +wool I picked up in [Bacci in Florence](http://www.baccitessuti.it/en/index.html) over the summer, and I took +the extra step of interlining it with French terry (I really don't like to be cold). + +![I have no affiliation with Bacci, I'm just a sucker for great fabric stores](https://posts.freesewing.org/uploads/bacci_043f91c96c.jpg) +![You can see the terry interlining where I peeled back the sleeve lining](https://posts.freesewing.org/uploads/interlining_220e0eab71.jpg) + +### Burn the patriarchy to the ground through the power of pockets + +Ladies take note: Carlita --- a female version of Carlton --- is currently on the drawing board. + +Initially, the plan was to release male and female versions side by side, but adapting the coat +has proven to be more involved than anticipated because, well, because boobs. + +I also feel like I have to +keep too many plates spinning right now, so I'm hopeful that getting Carlton out the door will +create some time/space to make Carlita follow soon(ish). Either way, I've promised Anneke that we'd +do a female version, and [she's a freesewing Captain now](/patrons), so I intend to keep that promise. + +Oh, and about that title: When Carlita's ready, she will have just as many pockets as Carlton. + +## Also, this: Introducing the Bent Body Block +We're actually releasing two patterns today. Apart from the Carlton Coat, there's also +the [Bent Body Block](/patterns/bent). + +Bent is a two-part sleeve variation of our [Brian Body Block](/patterns/bent). It's essentially a base +for coat and jacket patterns for menswear. + +I originally designed Bent as a base for my [refashioners 2017 zebra jacket](/blog/the-refashioners-2017/), +so you can expect that jacket pattern to also hit the site in the coming months. + +Carlton is also based on Bent, so we're giving you both today. + +Have wonderful and happy holidays if you're into that kind of thing. And happy making! + + + + diff --git a/markdown/org/blog/announcing-carlton-and-bent/fr.md b/markdown/org/blog/announcing-carlton-and-bent/fr.md new file mode 100644 index 00000000000..665ee0d8768 --- /dev/null +++ b/markdown/org/blog/announcing-carlton-and-bent/fr.md @@ -0,0 +1,60 @@ +--- +author: "joostdecock" +caption: "Vous aussi, vous pouvez porter ce manteau. Pour le chapeau, c'est vous qui verrez. Du moins, pour l'instant." +date: "2017-12-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/01c201b14f04bedbe2630bb3bd40d925fd6c1ce4-3500x2333.jpg" +intro: "Bonne nouvelle, vos désirs de cosplay vont être exhaucés. En tout cas, si vous endossez le rôle de Sherlock Holmes. Notre dernière version de patron, du manteau Carlton est totalement conforme à la prescription de votre médecin si pour une raison étrange, il veut que vous ressembliez au détective préféré de chacun." +title: "Annonce de Carlton, le manteau de Sherlock Holmes, et de Bent, haut de base" +--- + + +Bonne nouvelle, vos désirs de cosplay vont être exhaucés. En tout cas, si vous endossez le rôle de Sherlock Holmes. Notre dernière version de patron, [du manteau Carlton ](/patterns/carlton) est totalement conforme à la prescription de votre médecin si pour une raison étrange, il veut que vous ressembliez au détective préféré de chacun. + +Mes souvenirs sont flous quant à l'origine exacte de cette intiative. Mis à part que probablement, il faisait froid et que je n'avais pas de manteau chaud d'hiver, mystère. + +Je me souviens simplement qu'à un moment, [Anneke](http://www.annekecaramin.com/) et moi avons décidé que nous allions revisiter le manteau de Sherlock Holmes. Plus précisément, le manteau porté par Benedict Cumberbatch dans la série Sherlock Holmes de la BBC. + +![Principe de ce manteau](bc.jpg) + +Pour des raisons évidentes, ce manteau est populaire auprès des cosplayers, mais c'est aussi un manteau vraiment sympa, et d'autres valeureux [tels que Melissa](http://blog.fehrtrade.com/gallery/868/the-sherlock-coat/) se sont lancés dans sa réalisation. + +Je dois avouer qu'avant de finir le mien, je ne savais pas que Melissa avait fait un manteau similaire. De plus, son blog mentionne qu'elle a suivi les instructions d'un article (sur le site Livejournal) qui n'est plus disponible. + +Anneke et moi-même n'avons rien fait de tel ; nous avons créé le patron ensemble, sur la base des captures d'écran de l'émission télévisée. A la barbare, comme ça. + +### À propos du manteau + +Carlton est un manteau croisé, long, s'inspirant des uniformes de cavaliers, sans fente au dos, mais à la place de larges plis pouvant se draper sur le dos du cheval. Ou, de manière plus réaliste, se soulève derrière vous lorsque vous marchez. + +![Carlton vu de face](front.jpg) ![Carlton vu de dos](back.jpg) + +Il comporte deux poches appliquées sur le devant, deux poches poitrine et deux poches intérieures. Soit six poches au total, vous aurez donc beaucoup de place pour vos affaires. + +![Poches poitrine et poches applquées extérieures](pockets.jpg) ![Poches intérieures](innerpocket.jpg) + +J'ai terminé le mien juste à temps pour un voyage à K. pour rendre visite à mon cher ami et tailleur [Sebastian Hoofs](http://sebastian-hoofs.de/massschneider/). Il y faisait un froid de canard, mais le manteau m'a bien tenu chaud. Pas surprenant, car il est réalisé dans une laine lourde que j'ai trouvée chez [Bacci à Florence](http://www.baccitessuti.it/en/index.html) un été, et j'ai choisi l'option d'ajouter une sous-couche en molleton french terry (je n'aime vraiment pas avoir froid). + +![Je n'ai aucun lien avec Bacci, je suis juste un aspirateur à grands magasins de tissus](bacci.jpg) ![Vous pouvez voir la sous couche en molleton au dos de la doublure de manche](interlining.jpg) + +### Prenez le pouvoir grâce à ces poches magnifiques + +Aux filles : Carlita --- version féminine de Carlton --- est actuellement sur la planche à dessin. + +Initialement, le projet était de publier les versions masculine et féminine ensemble, mais l'adaptation s'est avérée plus compliquée que prévu à cause des seins. + +J'ai l'impression de faire tourner trop d'assiettes en même temps en ce moment, donc j'espère que la sortie de Carlton laissera un peu de temps/espace pour que Carlita suive bientôt. Quoi qu'il en soit, j'ai promis à Anneke que nous faisions une version femme, et [comme elle est un capitaine Freesewing maintenant](/patrons), j'ai l'intention de tenir cette promesse. + +Oh, et précision : quand Carlita sera prête, elle aura autant de poches que Carlton. + +## Introduction au patron de haut de base Bent +Nous publions en fait deux patrons aujourd'hui. En plus du manteau Carlton, il y a aussi le patron de haut de base [Bent](/patterns/bent). + +Bent est une variation en deux parties de notre [patron de haut de base Brian](/patterns/bent). C'est un patron de base pour des manteaux et vestes pour hommes. + +J'ai initialement conçu Bent comme une base pour ma veste zèbre [refashioners 2017](/blog/the-refashioners-2017/), donc ce patron de veste ne saurait tarder à arriver sur le site dans les mois à venir. + +Carlton étant également basé sur Bent, nous vous donnons les deux aujourd'hui. + +Passez des vacances merveilleuses et heureuses si vous êtes dans ce genre de choses. Et bonnes réalisations ! + + diff --git a/markdown/org/blog/announcing-carlton-and-bent/nl.md b/markdown/org/blog/announcing-carlton-and-bent/nl.md new file mode 100644 index 00000000000..232f6da9bf1 --- /dev/null +++ b/markdown/org/blog/announcing-carlton-and-bent/nl.md @@ -0,0 +1,60 @@ +--- +author: "joostdecock" +caption: "Ook jij kan deze jas dragen. De pet moet je ergens anders zoeken. Voorlopig toch." +date: "2017-12-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/01c201b14f04bedbe2630bb3bd40d925fd6c1ce4-3500x2333.jpg" +intro: "Goed nieuws vrienden, we helpen de cosplayers uit de nood. Zij die als Sherlock Holmes cosplayen toch. Ons nieuwste patroon, de Carlton jas , is exact wat de dokter je zou voorschrijven als de dokter om één of andere reden wil dat je erbij loopt als iedereen z'n favoriete detective." +title: "We presenteren Carlton, ofwel de Sherlock Holmes jas, en de Bent Basisvorm" +--- + + +Goed nieuws vrienden, we helpen de cosplayers uit de nood. Zij die als Sherlock Holmes cosplayen toch. Ons nieuwste patroon, de [Carlton jas](/patterns/carlton), is exact wat de dokter je zou voorschrijven als de dokter om één of andere reden wil dat je erbij loopt als iedereen z'n favoriete detective. + +Mijn geheugen laat me een beetje in de steek als het gaat om het begin van dit project. Waarschijnlijk had het te maken met mij die aan het klagen was over de kou en hoe ik een warme winterjas miste, maar buiten dat ben ik niet zo zeker. + +Wat ik wel nog weet is dat [Anneke](http://www.annekecaramin.com/) en ik op een gegeven moment beslisten dat we de Sherlock Holmes kas wilden namaken. Om precies te zijn, de jas die Benedict Cumberbatch draagt in de BBC-serie over Sherlock Holmes. + +![Die jas he](bc.jpg) + +De jas is om duidelijke redenen populair bij cosplayers, maar is op zich gewoon een heel mooie jas, en andere dappere zielen zoals [Melissa](http://blog.fehrtrade.com/gallery/868/the-sherlock-coat/) waagden zich er al aan. + +Ik moet toegeven dat ik niet wist dat Melissa deze jas gemaakt had tot de mijne af was. Bovendien vermeldt haar blogpost dat ze instructies gebruikte uit een Livejournal post die niet langer beschikbaar is. + +Anneke en ik hebben dat niet gedaan en gewoon een patroon gebaseerd op screenshots van het tv-programma. Zo hardcore zijn we wel. + +### Over de jas + +Carlton is een lange double-breasted overjas die teruggrijpt naar de traditionele uniformjassen voor ruiters waar de achterkant van de jas niet gesplitst is, maar wijde plooien heeft die over de rug van het paard kunnen liggen. Of, iets waarschijnlijker, achter je openwaaien terwijl je rondparadeert. + +![Voorzicht van Carlton op de auteur](front.jpg) ![Achterzicht van Carlton op de auteur](back.jpg) + +De jas heeft twee opgestikte zakken vooraan, twee borstzakken met paspel en twee binnenzakken. Zes zakken in totaal, dus meer dan genoeg ruimte voor al je spullen. + +![Borstzakken en opgestikte zakken aan de buitenkant](pockets.jpg) ![Binnenzakken aan de binnenkant](innerpocket.jpg) + +Ik maakte mijn jas net op tijd af voor een trip naar Keulen om mijn goede vriend en kleermaker [Sebastian Hoofs te bezoeken](http://sebastian-hoofs.de/massschneider/). Het was daar kouder dan zou mogen, maar de jas hield me lekker warm. Niet verrassend aangezien hij is gemaakt van een zware wol die ik tijdens de zomer vond bij [Bacci in Firenze](http://www.baccitessuti.it/en/index.html), en ik ook nog eens de extra moeite nam om een french terry tussenvoering toe te voegen (ik heb het echt niet graag koud). + +![Ik heb wordt niet betaald door Bacci, maar ben wel fan van goede stoffenwinkels](bacci.jpg) ![Je kan de french terry tussenvoering zien waar ik de mouwvoering naar achter gelegd heb](interlining.jpg) + +### Stamp het patriarchaat de grond in met de kracht van zakken + +Dames, opgelet: Carlita - een damesversie van Carlton - staat hoog op de agenda. + +Initieel waren we van plan de heren- en damesversie tegelijk uit te brengen, maar de jas aanpassen bleek iets moeilijker dan verwacht door, wel, door borsten. + +Ik heb ook het gevoel dat ik iets te veel hooi op mijn vork heb hangen, dus ik hoop dat het uitbrengen van Carlton een beetje tijd/ruimte creëert om Carlita te (binnenkort) te laten volgen. Hoe dan ook heb ik Anneke beloofd dat we een damesversie zouden maken, en aangezien ze nu een [freesewing Captain](/patrons) is wil ik die belofte zeker houden. + +Oh, en over die titel: als Carlita klaar is zal ze net evenveel zakken hebben als Carlton. + +## Ook dit nog: We presenteren de Bent Basisvorm +Eigenlijk komen er vandaag twee patronen uit. Naast de Carlton jas is er ook de [Bent Basisvorm](/patterns/bent). + +Bent is een variatie op onze [Brian Basisvorm](/patterns/bent), met een tweedelige mouw. Eigenlijk is het een basis voor patronen voor heren jasjes en -jassen. + +Ik ontwierp Bent initieel als een basis voor het [zebrajasje dat ik voor de Refashioners maakte in 2017](/blog/the-refashioners-2017/), dus dat jasjespatroon kan je in de komende maanden ook verwachten. + +Carlton is ook op Brent gebaseerd, dus vandaag krijg je ze allebei. + +Heel fijne feestdagen gewenst, als dat je ding is. En veel plezier met maken! + + diff --git a/markdown/org/blog/announcing-charlie/de.md b/markdown/org/blog/announcing-charlie/de.md new file mode 100644 index 00000000000..7687f33b17d --- /dev/null +++ b/markdown/org/blog/announcing-charlie/de.md @@ -0,0 +1,63 @@ +--- +author: "joostdecock" +caption: "Foto von Flo Dahm von Pexels" +date: "2021-04-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9e1cca6b6de79fadbd5201bad3b9b71375a53464-1920x1442.jpg" +intro: "Wir haben soeben FreeSewing v2.15 veröffentlicht und es kommt mit einem neuen Muster: Das Charlie Chinohosenmuster ." +title: "Charlie Chinos: Wer will ein paar neue Hosen?" +--- + + +Wir haben soeben FreeSewing v2.15 veröffentlicht und es kommt mit einem neuen Muster: [Das Charlie Chinohosenmuster](/designs/charlie/). + +Ich habe den Überblick darüber verloren, wie lange ein Schnittmuster für Chinos schon auf meiner To-Do Liste stand, aber die verwendete Einheit ist sicher Jahre. Ich bin sehr froh, dass ich endlich dort angekommen bin, wo ich hin wollte. + +Hier ist ein Bild davon, aber durch den dunklen Stoff erkennt man leider nicht so viel: + +![Einmal Charlie von Joost](joost.jpg) + +Stattdessen erzähle ich dir lieber, warum ich hierüber so begeistert bin. + +##### Basierend auf Titan + +Vorweg: Charlie basiert auf Titan, unserem Unisex-Hosengrundschnitt, der auch die Grundlage für [unseren Paco-Schnitt](/designs/paco/) ist. Wenn du also diese Schitte kennst, weißt du schon, wie dir Charlie passen wird. + +##### Mehr Körpermaße, mehr Optionen, besserer Sitz + +Um zu zeigen, für wie groß ich diese Verbesserung halte, habe ich [Theo](/designs/theo/) als veraltet markiert. Da Theo auf der Aldrich-Entwurfsmethode basiert, werden dort nur sehr wenige Körpermaße verwendet. Das funktioniert zwar gut für einige bestimmte Leute, ist aber dadurch nicht sehr vielseitig. + +Charlie passt sich unterschiedlich geformten Körpern besser an, und hat verdammt viele Optionen, die es dir ermöglichen, deine Hose so zu konfigurieren wie du sie haben willst. Falls du dich fragst: Theo hat 5 Optionen, während es bei Charlie 31 sind. + +Trotzallem werden wir Theo weiter zur Verfügung stellen. Veraltet bedeutet nur, dass wir eine kleine Warnmeldung hinzugefügt haben, die dir sagt, dass wir stattdessen Charlie empfehlen. + +##### Einfacher zu fertigen + +Ein weiterer Grund um sich für Charlie statt für Theo zu entscheiden: Charlie ist einfacher zu fertigen. Der Schnitt hat eine unkompliziertere Konstruktionsmethode für den Hosenstall und -bund, und die vorderen Taschen wurden so clever designt, dass sie in den Seitennähten und dadurch viel einfacher zu nähen sind, aber dennoch den klassischen Look von schräg angesetzten Taschen haben. + +Theo wird mit 4 Sternen auf unserer Schwierigkeitsskala eingestuft, und ich habe Charlie 3 Sterne gegeben. Wenn du Angst davor hattest, Hosen zu machen, könnte dies das Schnittmuster sein, auf das du gewartet hast. + +##### Echte Taschen + +Charlie ist ein Unisex-Schnitt und die Taschen sind echt. Das hast hinten Paspeltaschen, und schräge Taschen vorne. In beiden Fällen hast du die Kontrolle darüber, wie groß und tief die Taschen sind. + +Die vorderen Taschen verdienen eine gesonderte Erwähnung. Sie sehen zwar aus wie traditionelle, schräg angesetzte Taschen, liegen aber in der Seitennaht. Damit das möglich ist, erstreckt sich ein Teil des hinteren Stoffstückes nach vorne, dem Winkel der Hosentasche folgend. + +## Andere Neuigkeiten zu 2.15 + +Charlie ist der Hauptakt, aber in dieser 2.15 Version steckt eine ganze Menge Arbeit. + +Wie immer finden sich [im Changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md) alle Details, ich möchte aber ein paar erwähnenswerte Änderungen besonders hervorheben: + + - Wir haben [ein neues Plugin für Riegel](https://freesewing.dev/reference/plugins/bartack/) + - Das [Knopf-Plugin](https://freesewing.dev/reference/plugins/buttons/) bietet neue [Knopfloch-Beginn](https://freesewing.dev/reference/snippets/buttonhole-start) und [Knopfloch-Ende](https://freesewing.dev/reference/snippets/buttonhole-end) Snippets + - Das [Dimensions-Plugin](https://freesewing.dev/reference/plugins/dimension/) stellt ein neues [rmad Makro](https://freesewing.dev/reference/macros/rmad/) zur Verfügung + - Das [Logo-Plugin](https://freesewing.dev/reference/plugins/logo/) unterstützt nun den dunklen Modus + - Titan und Paco haben eine neue `waistbandHeight`-Option + - Punktkoordinaten werden nicht mehr vom Core gerundet, um zu vermeiden, dass [path.split](https://freesewing.dev/reference/api/path/split/) nicht trifft + - [Bella](/designs/bella/) hat einen Bug-Fix an der Schulter bekommen, um Puppenkleidung besser zu unterstützen + - [Charlie](/designs/charlie/) ist das erste Schnittmuster, das ein paar absolute Dimensionen während der Konfiguration anzeigt. Wir haben vor, das auf weitere Schnittmuster auszudehnen. Designer, die dieses Feature nutzen wollen, finden die neuen [raise-Methoden](https://freesewing.dev/reference/api/part/raise) in der Dokumentation. + - Wo wir schon bei der Dokumentation sind, die Beispiele in unserer [Dokumentation für Entwickler](https://freesewing.dev/) erlaubt es dir nun, dir die Punkte und Pfade in den Beispielen per Knopfdruck anzeigen zu lassen + - Die [part.getId()](https://freesewing.dev/reference/api/part/getid/)-Methode verwendet nun ein Präfix-Argument + + + diff --git a/markdown/org/blog/announcing-charlie/en.md b/markdown/org/blog/announcing-charlie/en.md new file mode 100644 index 00000000000..f59b8ecd318 --- /dev/null +++ b/markdown/org/blog/announcing-charlie/en.md @@ -0,0 +1,88 @@ +--- +author: "joostdecock" +caption: "Photo by Flo Dahm from Pexels" +date: "2021-04-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9e1cca6b6de79fadbd5201bad3b9b71375a53464-1920x1442.jpg" +intro: "We've just published FreeSewing v2.15 and it comes with a new pattern: The Charlie Chinos trouser pattern ." +title: "Charlie Chinos: who wants some new trousers?" +--- + + +We've just published FreeSewing v2.15 and it comes with a new pattern: +[The Charlie Chinos trouser pattern](/designs/charlie/). + +I have lost track of how long a chino trouser pattern has been on my to-do list, +but it's measured in years. I'm very happy I finally landed where I wanted to be. + +I have a picture of it here, but due to the dark fabric, you can't really make out much: + +![A pair of Charlies by Joost](https://posts.freesewing.org/uploads/joost_b8dee41025.jpg) + + +So instead, let me tell you about why I am so excited about this. + +##### Based on Titan + +First up, Charlie is based on Titan, our unisex trouser block that is also the +foundation for [our Paco pattern](/designs/paco/). So if you're familiar with +any of those, you already know how Charlie will fit you. + +##### More measurements, more options, better fit + +As a token of how much I feel this is an improvement, I've deprecated [Theo](/designs/theo/). +Based on an Aldrich draft, Theo uses very few measurements, +and while that worked fine for a certain set of people, it's a less versatile pattern. + +Charlie will adapt better to differently shaped bodies, and has a hell of a lot more options +that allow you to configure your trousers so you get them just as you like. In case you're +wondering, Theo has 5 options, whereas Charlie has 31. + +That being said, we will keep Theo available. Deprecated merely means that we've added a little +warning message saying that we recommend Charlie instead. + +##### Easier to make + +Another reason to opt for Charlie rather than Theo: Charlie is easier to make. +It has a more straight-forward fly and waistband construction, and the front +pockets have been cleverly designed to give you the ease of construction that +comes with side-seam pockets, yet the classic look of slanted pockets. + +Theo ranks 4 stars on our difficulty scale, and I've given Charlie 3 stars. +If you were afraid of making trousers, this might be the pattern you've been waiting for. + +##### Real pockets + +Charlie is a unisex pattern and the pockets are real. You have welt (aka jetted) pockets at the back, +and slanted pockets at the front. +In both cases, you have control over the size and depth of the pockets. + +The front pockets deserve a special mention. They look like traditional slanted pockets, but are +set in on the side seam. To make that possible, the back panel of the trousers wraps around the front, +following the pocket slant. + +## Other 2.15 news + +Charlie is the main act, but there's a lot of work that went in this 2.15 release. + +As always, [the changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md) has +all the details, but allow me to highlight some of the more noteworthy changes: + + - We have [a new bartack plugin](https://freesewing.dev/reference/plugins/bartack/) + - The [buttons plugin](https://freesewing.dev/reference/plugins/buttons/) provides + new [buttonhole-start](https://freesewing.dev/reference/snippets/buttonhole-start) + and [buttonhole-end](https://freesewing.dev/reference/snippets/buttonhole-end) snippets + - The [dimension plugin](https://freesewing.dev/reference/plugins/dimension/) provides + a new [rmad macro](https://freesewing.dev/reference/macros/rmad/) + - The [logo plugin](https://freesewing.dev/reference/plugins/logo/) now supports dark mode + - Titan and Paco have a new `waistbandHeight` option + - Core no longer rounds point coordinates to avoid misses when using [path.split](https://freesewing.dev/reference/api/path/split/) + - [Bella](/designs/bella/) has a fix to the shoulder to better accommodate doll-sized clothing + - [Charlie](/designs/charlie/) is the first pattern to list some of the absolute dimensions when configuring + a pattern, but we plan to extend this to other designs + We have documented [the new raise methods](https://freesewing.dev/reference/api/part/raise) for designers + who want to utilize this feature. + - Speaking of documentation, the examples in our [documentation for developers](https://freesewing.dev/) now + allows you to toggle a switch to reveal the points and paths in the examples + - The [part.getId()](https://freesewing.dev/reference/api/part/getid/) method now takes a prefix argument + + diff --git a/markdown/org/blog/announcing-charlie/es.md b/markdown/org/blog/announcing-charlie/es.md new file mode 100644 index 00000000000..03c9a7a804e --- /dev/null +++ b/markdown/org/blog/announcing-charlie/es.md @@ -0,0 +1,88 @@ +--- +author: "joostdecock" +caption: "Photo by Flo Dahm from Pexels" +date: "2021-04-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9e1cca6b6de79fadbd5201bad3b9b71375a53464-1920x1442.jpg" +intro: "We've just published FreeSewing v2.15 and it comes with a new pattern: The Charlie Chinos trouser pattern ." +title: "Charlie Chinos: who wants some new trousers? [No traducido]" +--- + + +We've just published FreeSewing v2.15 and it comes with a new pattern: +[The Charlie Chinos trouser pattern](/designs/charlie/). + +I have lost track of how long a chino trouser pattern has been on my to-do list, +but it's measured in years. I'm very happy I finally landed where I wanted to be. + +I have a picture of it here, but due to the dark fabric, you can't really make out much: + +![A pair of Charlies by Joost](https://posts.freesewing.org/uploads/joost_b8dee41025.jpg) + + +So instead, let me tell you about why I am so excited about this. + +##### Based on Titan + +First up, Charlie is based on Titan, our unisex trouser block that is also the +foundation for [our Paco pattern](/designs/paco/). So if you're familiar with +any of those, you already know how Charlie will fit you. + +##### More measurements, more options, better fit + +As a token of how much I feel this is an improvement, I've deprecated [Theo](/designs/theo/). +Based on an Aldrich draft, Theo uses very few measurements, +and while that worked fine for a certain set of people, it's a less versatile pattern. + +Charlie will adapt better to differently shaped bodies, and has a hell of a lot more options +that allow you to configure your trousers so you get them just as you like. In case you're +wondering, Theo has 5 options, whereas Charlie has 31. + +That being said, we will keep Theo available. Deprecated merely means that we've added a little +warning message saying that we recommend Charlie instead. + +##### Easier to make + +Another reason to opt for Charlie rather than Theo: Charlie is easier to make. +It has a more straight-forward fly and waistband construction, and the front +pockets have been cleverly designed to give you the ease of construction that +comes with side-seam pockets, yet the classic look of slanted pockets. + +Theo ranks 4 stars on our difficulty scale, and I've given Charlie 3 stars. +If you were afraid of making trousers, this might be the pattern you've been waiting for. + +##### Real pockets + +Charlie is a unisex pattern and the pockets are real. You have welt (aka jetted) pockets at the back, +and slanted pockets at the front. +In both cases, you have control over the size and depth of the pockets. + +The front pockets deserve a special mention. They look like traditional slanted pockets, but are +set in on the side seam. To make that possible, the back panel of the trousers wraps around the front, +following the pocket slant. + +## Other 2.15 news + +Charlie is the main act, but there's a lot of work that went in this 2.15 release. + +As always, [the changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md) has +all the details, but allow me to highlight some of the more noteworthy changes: + + - We have [a new bartack plugin](https://freesewing.dev/reference/plugins/bartack/) + - The [buttons plugin](https://freesewing.dev/reference/plugins/buttons/) provides + new [buttonhole-start](https://freesewing.dev/reference/snippets/buttonhole-start) + and [buttonhole-end](https://freesewing.dev/reference/snippets/buttonhole-end) snippets + - The [dimension plugin](https://freesewing.dev/reference/plugins/dimension/) provides + a new [rmad macro](https://freesewing.dev/reference/macros/rmad/) + - The [logo plugin](https://freesewing.dev/reference/plugins/logo/) now supports dark mode + - Titan and Paco have a new `waistbandHeight` option + - Core no longer rounds point coordinates to avoid misses when using [path.split](https://freesewing.dev/reference/api/path/split/) + - [Bella](/designs/bella/) has a fix to the shoulder to better accommodate doll-sized clothing + - [Charlie](/designs/charlie/) is the first pattern to list some of the absolute dimensions when configuring + a pattern, but we plan to extend this to other designs + We have documented [the new raise methods](https://freesewing.dev/reference/api/part/raise) for designers + who want to utilize this feature. + - Speaking of documentation, the examples in our [documentation for developers](https://freesewing.dev/) now + allows you to toggle a switch to reveal the points and paths in the examples + - The [part.getId()](https://freesewing.dev/reference/api/part/getid/) method now takes a prefix argument + + diff --git a/markdown/org/blog/announcing-charlie/fr.md b/markdown/org/blog/announcing-charlie/fr.md new file mode 100644 index 00000000000..900a656a71a --- /dev/null +++ b/markdown/org/blog/announcing-charlie/fr.md @@ -0,0 +1,88 @@ +--- +author: "joostdecock" +caption: "Photo by Flo Dahm from Pexels" +date: "2021-04-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9e1cca6b6de79fadbd5201bad3b9b71375a53464-1920x1442.jpg" +intro: "We've just published FreeSewing v2.15 and it comes with a new pattern: The Charlie Chinos trouser pattern ." +title: "Charlie Chinos: who wants some new trousers? [Non traduit]" +--- + + +We've just published FreeSewing v2.15 and it comes with a new pattern: +[The Charlie Chinos trouser pattern](/designs/charlie/). + +I have lost track of how long a chino trouser pattern has been on my to-do list, +but it's measured in years. I'm very happy I finally landed where I wanted to be. + +I have a picture of it here, but due to the dark fabric, you can't really make out much: + +![A pair of Charlies by Joost](https://posts.freesewing.org/uploads/joost_b8dee41025.jpg) + + +So instead, let me tell you about why I am so excited about this. + +##### Based on Titan + +First up, Charlie is based on Titan, our unisex trouser block that is also the +foundation for [our Paco pattern](/designs/paco/). So if you're familiar with +any of those, you already know how Charlie will fit you. + +##### More measurements, more options, better fit + +As a token of how much I feel this is an improvement, I've deprecated [Theo](/designs/theo/). +Based on an Aldrich draft, Theo uses very few measurements, +and while that worked fine for a certain set of people, it's a less versatile pattern. + +Charlie will adapt better to differently shaped bodies, and has a hell of a lot more options +that allow you to configure your trousers so you get them just as you like. In case you're +wondering, Theo has 5 options, whereas Charlie has 31. + +That being said, we will keep Theo available. Deprecated merely means that we've added a little +warning message saying that we recommend Charlie instead. + +##### Easier to make + +Another reason to opt for Charlie rather than Theo: Charlie is easier to make. +It has a more straight-forward fly and waistband construction, and the front +pockets have been cleverly designed to give you the ease of construction that +comes with side-seam pockets, yet the classic look of slanted pockets. + +Theo ranks 4 stars on our difficulty scale, and I've given Charlie 3 stars. +If you were afraid of making trousers, this might be the pattern you've been waiting for. + +##### Real pockets + +Charlie is a unisex pattern and the pockets are real. You have welt (aka jetted) pockets at the back, +and slanted pockets at the front. +In both cases, you have control over the size and depth of the pockets. + +The front pockets deserve a special mention. They look like traditional slanted pockets, but are +set in on the side seam. To make that possible, the back panel of the trousers wraps around the front, +following the pocket slant. + +## Other 2.15 news + +Charlie is the main act, but there's a lot of work that went in this 2.15 release. + +As always, [the changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md) has +all the details, but allow me to highlight some of the more noteworthy changes: + + - We have [a new bartack plugin](https://freesewing.dev/reference/plugins/bartack/) + - The [buttons plugin](https://freesewing.dev/reference/plugins/buttons/) provides + new [buttonhole-start](https://freesewing.dev/reference/snippets/buttonhole-start) + and [buttonhole-end](https://freesewing.dev/reference/snippets/buttonhole-end) snippets + - The [dimension plugin](https://freesewing.dev/reference/plugins/dimension/) provides + a new [rmad macro](https://freesewing.dev/reference/macros/rmad/) + - The [logo plugin](https://freesewing.dev/reference/plugins/logo/) now supports dark mode + - Titan and Paco have a new `waistbandHeight` option + - Core no longer rounds point coordinates to avoid misses when using [path.split](https://freesewing.dev/reference/api/path/split/) + - [Bella](/designs/bella/) has a fix to the shoulder to better accommodate doll-sized clothing + - [Charlie](/designs/charlie/) is the first pattern to list some of the absolute dimensions when configuring + a pattern, but we plan to extend this to other designs + We have documented [the new raise methods](https://freesewing.dev/reference/api/part/raise) for designers + who want to utilize this feature. + - Speaking of documentation, the examples in our [documentation for developers](https://freesewing.dev/) now + allows you to toggle a switch to reveal the points and paths in the examples + - The [part.getId()](https://freesewing.dev/reference/api/part/getid/) method now takes a prefix argument + + diff --git a/markdown/org/blog/announcing-charlie/nl.md b/markdown/org/blog/announcing-charlie/nl.md new file mode 100644 index 00000000000..c6dea263cf9 --- /dev/null +++ b/markdown/org/blog/announcing-charlie/nl.md @@ -0,0 +1,88 @@ +--- +author: "joostdecock" +caption: "Photo by Flo Dahm from Pexels" +date: "2021-04-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9e1cca6b6de79fadbd5201bad3b9b71375a53464-1920x1442.jpg" +intro: "We've just published FreeSewing v2.15 and it comes with a new pattern: The Charlie Chinos trouser pattern ." +title: "Charlie Chinos: who wants some new trousers? [Niet vertaald]" +--- + + +We've just published FreeSewing v2.15 and it comes with a new pattern: +[The Charlie Chinos trouser pattern](/designs/charlie/). + +I have lost track of how long a chino trouser pattern has been on my to-do list, +but it's measured in years. I'm very happy I finally landed where I wanted to be. + +I have a picture of it here, but due to the dark fabric, you can't really make out much: + +![A pair of Charlies by Joost](https://posts.freesewing.org/uploads/joost_b8dee41025.jpg) + + +So instead, let me tell you about why I am so excited about this. + +##### Based on Titan + +First up, Charlie is based on Titan, our unisex trouser block that is also the +foundation for [our Paco pattern](/designs/paco/). So if you're familiar with +any of those, you already know how Charlie will fit you. + +##### More measurements, more options, better fit + +As a token of how much I feel this is an improvement, I've deprecated [Theo](/designs/theo/). +Based on an Aldrich draft, Theo uses very few measurements, +and while that worked fine for a certain set of people, it's a less versatile pattern. + +Charlie will adapt better to differently shaped bodies, and has a hell of a lot more options +that allow you to configure your trousers so you get them just as you like. In case you're +wondering, Theo has 5 options, whereas Charlie has 31. + +That being said, we will keep Theo available. Deprecated merely means that we've added a little +warning message saying that we recommend Charlie instead. + +##### Easier to make + +Another reason to opt for Charlie rather than Theo: Charlie is easier to make. +It has a more straight-forward fly and waistband construction, and the front +pockets have been cleverly designed to give you the ease of construction that +comes with side-seam pockets, yet the classic look of slanted pockets. + +Theo ranks 4 stars on our difficulty scale, and I've given Charlie 3 stars. +If you were afraid of making trousers, this might be the pattern you've been waiting for. + +##### Real pockets + +Charlie is a unisex pattern and the pockets are real. You have welt (aka jetted) pockets at the back, +and slanted pockets at the front. +In both cases, you have control over the size and depth of the pockets. + +The front pockets deserve a special mention. They look like traditional slanted pockets, but are +set in on the side seam. To make that possible, the back panel of the trousers wraps around the front, +following the pocket slant. + +## Other 2.15 news + +Charlie is the main act, but there's a lot of work that went in this 2.15 release. + +As always, [the changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md) has +all the details, but allow me to highlight some of the more noteworthy changes: + + - We have [a new bartack plugin](https://freesewing.dev/reference/plugins/bartack/) + - The [buttons plugin](https://freesewing.dev/reference/plugins/buttons/) provides + new [buttonhole-start](https://freesewing.dev/reference/snippets/buttonhole-start) + and [buttonhole-end](https://freesewing.dev/reference/snippets/buttonhole-end) snippets + - The [dimension plugin](https://freesewing.dev/reference/plugins/dimension/) provides + a new [rmad macro](https://freesewing.dev/reference/macros/rmad/) + - The [logo plugin](https://freesewing.dev/reference/plugins/logo/) now supports dark mode + - Titan and Paco have a new `waistbandHeight` option + - Core no longer rounds point coordinates to avoid misses when using [path.split](https://freesewing.dev/reference/api/path/split/) + - [Bella](/designs/bella/) has a fix to the shoulder to better accommodate doll-sized clothing + - [Charlie](/designs/charlie/) is the first pattern to list some of the absolute dimensions when configuring + a pattern, but we plan to extend this to other designs + We have documented [the new raise methods](https://freesewing.dev/reference/api/part/raise) for designers + who want to utilize this feature. + - Speaking of documentation, the examples in our [documentation for developers](https://freesewing.dev/) now + allows you to toggle a switch to reveal the points and paths in the examples + - The [part.getId()](https://freesewing.dev/reference/api/part/getid/) method now takes a prefix argument + + diff --git a/markdown/org/blog/announcing-freesewing-library/de.md b/markdown/org/blog/announcing-freesewing-library/de.md new file mode 100644 index 00000000000..9ba48e5d2f3 --- /dev/null +++ b/markdown/org/blog/announcing-freesewing-library/de.md @@ -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: + +![Zeilen des Codevergleichs zwischen der neuen Library und dem (dem relevanten Teil des) FreeSewing-Core](corevsfreesewing.svg) + +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. + + diff --git a/markdown/org/blog/announcing-freesewing-library/en.md b/markdown/org/blog/announcing-freesewing-library/en.md new file mode 100644 index 00000000000..e7b95abbff6 --- /dev/null +++ b/markdown/org/blog/announcing-freesewing-library/en.md @@ -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: + +![Lines of code comparison between the new library and (the relevant portion of) freesewing core](https://posts.freesewing.org/uploads/corevsfreesewing_c9327c9fa3.svg) + +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. + diff --git a/markdown/org/blog/announcing-freesewing-library/es.md b/markdown/org/blog/announcing-freesewing-library/es.md new file mode 100644 index 00000000000..6b809a979e7 --- /dev/null +++ b/markdown/org/blog/announcing-freesewing-library/es.md @@ -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: + +![Lines of code comparison between the new library and (the relevant portion of) freesewing core](https://posts.freesewing.org/uploads/corevsfreesewing_c9327c9fa3.svg) + +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. + diff --git a/markdown/org/blog/announcing-freesewing-library/fr.md b/markdown/org/blog/announcing-freesewing-library/fr.md new file mode 100644 index 00000000000..407eb7fc1bd --- /dev/null +++ b/markdown/org/blog/announcing-freesewing-library/fr.md @@ -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: + +![Lines of code comparison between the new library and (the relevant portion of) freesewing core](https://posts.freesewing.org/uploads/corevsfreesewing_c9327c9fa3.svg) + +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. + diff --git a/markdown/org/blog/announcing-freesewing-library/nl.md b/markdown/org/blog/announcing-freesewing-library/nl.md new file mode 100644 index 00000000000..e09066ada85 --- /dev/null +++ b/markdown/org/blog/announcing-freesewing-library/nl.md @@ -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: + +![Vergelijking van de code tussen de nieuwe bibliotheek en (relevante delen van) de FreeSewing-core](corevsfreesewing.svg) + +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. + + diff --git a/markdown/org/blog/announcing-freesewing/de.md b/markdown/org/blog/announcing-freesewing/de.md new file mode 100644 index 00000000000..9f50289c10f --- /dev/null +++ b/markdown/org/blog/announcing-freesewing/de.md @@ -0,0 +1,51 @@ +--- +author: "joostdecock" +caption: "Das FreeSewing-Logo" +date: "2017-03-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4e1f5426ee6578ef31d9c18a1de9b4beef15836b-2000x1125.jpg" +intro: "Stolz darf ich euch die Veröffentlichung von freesewing core v1.0.0 und der zugehörigen Dokumentation , die das FreeSewing Projekt im Detail beschreibt." +title: "Ankündigung von FreeSewing, eine Opensourceplattform für Schnittmuster auf Mass" +--- + + +Stolz darf ich euch die Veröffentlichung von [freesewing core v1.0.0](https://github.com/freesewing/core) und der zugehörigen [Dokumentation](/docs), die das FreeSewing Projekt im Detail beschreibt. + +Aber ich bin auch Realist und weiss, dass Sie nicht die Zeit haben, sich durch Seiten über Seiten an Dokumentation zu wühlen. + +Stattdessen ist hier eine Abriss, um Ihnen den Kern von FreeSewing in aller Kürze zu präsentieren: + +## Die Herkunft von FreeSewing +Nähen ist einfach. Ja wirklich. Was schwierig ist, ist zu erreichen, dass die Kleidung gut sitzt. Das ist der Grund, warum wir Schnittmuster verwenden. Es ist ein Blaupause für das, was Sie kreieren möchten. Ein guter Schnitt gibt Ihnen eine gute Passform. Die meisten Schnittmuster verfehlen dieses Ziel. + +Dies ist — wie bei Kleidung aus dem Laden — weil Schnitte nach Grössentabellen gefertigt werden. Und Grössen sind ein Versuch Menschen in Schubladen zu stecken. Sie sind für hypothetische Menschen gemacht statt für Sie. + +Es gibt einen anderen Weg, nämlich den Schnitt direkt mit Ihren Massen zu konstruieren. Diese maßgeschneiderten Schnittmuster sind den Grössenschnitten weit überlegen, aber sie erfordern viel Arbeit, um sie zu erstellen. + +Ich wollte diesbezüglich Abhilfe schaffen und diese Anstrengungen mündeten in [MakeMyPattern.com](https://makemypattern.com/). Und diese Seite lief für einige Jahre und hatte erstaunlichen Erfolg. Vermutlich half die Tatsache, dass ich alle Schnittmuster kostenlos zur Verfügung stellte. + +Im Umfeld von Hobbynähern braucht es meistens etwas Erläuterung, warum jemand etwas kostenlos zur Verfügung stellt. Die Dinge stehen ganz anders in der Opensource-Welt, wo die Idee Wissen und Arbeit mit anderen zu teilen, zum Nutzen aller, die Grundlage der Communities darstellt. + +Da ich die Opensource-Kultur nicht in die Welt des Nähens bringen kann, kann ich aber auf jeden Fall Schnittmuster in die Opensource-Sphären bringen. + +[FreeSewing.org](https://freesewing.org/) wird weiterhin zur Verfügung stellen, was [Makemypattern.com](https://makemypattern.com/) heute anbieten: Kostenfreie opensource Schnittmuster, die nach Ihren individuellen Massen erstellt werden. Jedoch wird es zusätzlich offen für Ihre Mitgestaltung sein. + +In der Hoffnung, dass die Schnittmenge von Nähen und Geeks nicht nur mich enthält. + +joost + +## Zum Schluss +Freesewing ist ein Projekt von [Joost De Cock](https://github.com/joostdecock) und Beitragenden. + +Ich danke [@jakesgordon](https://github.com/jakesgordon) und [Kevin Lindsey](http://www.kevlindev.com), dass Sie mir gestatten ein Teil ihres Codes zu portieren. + +Die Begeisterung und der Input im Frühstadium von [@diggydev](https://github.com/diggydev), [@cabi](https://github.com/cabi), [@woutervdub](https://github.com/woutervdub), [@cloutiy](https://github.com/cloutiy), [@straytaoist](https://github.com/straytaoist), [@netpraxis](https://github.com/netpraxis), [@Stefan1960](https://github.com/Stefan1960), [@brendare1](https://github.com/brendare1), [@JorisJoppe](https://github.com/JorisJoppe), [@JamJenkins](https://github.com/JamJenkins), und [@fightingrabbit](https://github.com/fightingrabbit) war eine große Bereicherung für dieses Projekt. + +Vielen Dank an [@annekecaramin](https://twitter.com/annekecaramin) für die Gestaltung eines Logos, das cool genug ist, um es auf ein T-Shirt zu drucken. + +Besonderen Dank an [@scorchtorch](https://twitter.com/scorchtorch) dafür, dass du der Beste in dieser Herz-/Salat-/Sondersituation bist. + +Last but not least wäre dieses Projekt ohne die Nutzer, Unterstützer und Spender von [makemypattern.com](https://makemypattern.com/) nicht möglich. + +Danke Leute! + + diff --git a/markdown/org/blog/announcing-freesewing/en.md b/markdown/org/blog/announcing-freesewing/en.md new file mode 100644 index 00000000000..2091d4f312d --- /dev/null +++ b/markdown/org/blog/announcing-freesewing/en.md @@ -0,0 +1,70 @@ +--- +author: "joostdecock" +caption: "The freesewing logo" +date: "2017-03-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4e1f5426ee6578ef31d9c18a1de9b4beef15836b-2000x1125.jpg" +intro: "I am are proud to announce freesewing core v1.0.0 and the accompanying documentation that describes the freesewing project in detail." +title: "Announcing freesewing, an open source platform for made-to-measure sewing patterns" +--- + +I am are proud to announce [freesewing core v1.0.0](https://github.com/freesewing/core) and the accompanying [documentation](/docs) that describes the freesewing project in detail. + +But I'm also realistic, and understand that you don't have time to plow through pages upon pages of documentation. + +So instead, here's a story to give you the essence of freesewing in a nutshell: + +## The freesewing origin story +Sewing is easy. It really is. +What's hard is getting things to fit properly. +That's why you use a sewing pattern. +It's a blueprint for whatever it is you are making. +A good pattern gives you good fit. Most patterns don't. + +That's because — much like clothes in the shop — patterns come in sizes. +And sizes are a crude way to put people in boxes. +They are made for an imaginary average person, rather than for you. + +There's another way, and that is to draft a pattern based on your measurements. +These made-to-measure patterns are vastly superior, but they require a lot of work. + +I wanted to change that, and that effort evolved into [MakeMyPattern.com](https://makemypattern.com/). +I ran that site for a number of years, and it was a remarkable success. +Probably helped by the fact that I gave away all patterns for free. + +In the world of home sewing, it tends to require a bit of explaining why one would choose to give away their work for free. +Things are different in the open source world where the idea of sharing your work with others for the benefit of all is the very thread from which communities are woven. + +While I can't magically bring the culture of open source to sewing patterns, I certainly can bring sewing patterns into the open source world. + +[Freesewing.org](https://freesewing.org/) will continue to offer what [Makemypattern.com](https://makemypattern.com/) does today: free sewing patterns drafted to your measurements. +But additionally, it will be open to your contributions. + +Here's hoping that in the Venn diagram of the somewhat geeky and sewing, it's not just me in the middle. + +joost + +## Shout-outs +Freesewing is a project by [Joost De Cock](https://github.com/joostdecock) and contributors. + +Hat-tip to [@jakesgordon](https://github.com/jakesgordon) and [Kevin Lindsey](http://www.kevlindev.com) for allowing me to port some of their code. + +The early-stage enthusiasm and input of +[@diggydev](https://github.com/diggydev), +[@cabi](https://github.com/cabi), +[@woutervdub](https://github.com/woutervdub), +[@cloutiy](https://github.com/cloutiy), +[@straytaoist](https://github.com/straytaoist), +[@netpraxis](https://github.com/netpraxis), +[@Stefan1960](https://github.com/Stefan1960), +[@brendare1](https://github.com/brendare1), +[@JorisJoppe](https://github.com/JorisJoppe), +[@JamJenkins](https://github.com/JamJenkins), and +[@fightingrabbit](https://github.com/fightingrabbit) has been a great boon to this project. + +Thanks to [@annekecaramin](https://twitter.com/annekecaramin) for designing a logo cool enough to put on a Tshirt. + +Special thanks to [@scorchtorch](https://twitter.com/scorchtorch) for being the best at that heart/salad/antlers thing. + +Last but not least, this project would not exist without the users, supporters, and donors of [makemypattern.com](https://makemypattern.com/). + +Thanks guys! diff --git a/markdown/org/blog/announcing-freesewing/es.md b/markdown/org/blog/announcing-freesewing/es.md new file mode 100644 index 00000000000..c257e00b08a --- /dev/null +++ b/markdown/org/blog/announcing-freesewing/es.md @@ -0,0 +1,70 @@ +--- +author: "joostdecock" +caption: "The freesewing logo" +date: "2017-03-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4e1f5426ee6578ef31d9c18a1de9b4beef15836b-2000x1125.jpg" +intro: "I am are proud to announce freesewing core v1.0.0 and the accompanying documentation that describes the freesewing project in detail." +title: "Announcing freesewing, an open source platform for made-to-measure sewing patterns [No traducido]" +--- + +I am are proud to announce [freesewing core v1.0.0](https://github.com/freesewing/core) and the accompanying [documentation](/docs) that describes the freesewing project in detail. + +But I'm also realistic, and understand that you don't have time to plow through pages upon pages of documentation. + +So instead, here's a story to give you the essence of freesewing in a nutshell: + +## The freesewing origin story +Sewing is easy. It really is. +What's hard is getting things to fit properly. +That's why you use a sewing pattern. +It's a blueprint for whatever it is you are making. +A good pattern gives you good fit. Most patterns don't. + +That's because — much like clothes in the shop — patterns come in sizes. +And sizes are a crude way to put people in boxes. +They are made for an imaginary average person, rather than for you. + +There's another way, and that is to draft a pattern based on your measurements. +These made-to-measure patterns are vastly superior, but they require a lot of work. + +I wanted to change that, and that effort evolved into [MakeMyPattern.com](https://makemypattern.com/). +I ran that site for a number of years, and it was a remarkable success. +Probably helped by the fact that I gave away all patterns for free. + +In the world of home sewing, it tends to require a bit of explaining why one would choose to give away their work for free. +Things are different in the open source world where the idea of sharing your work with others for the benefit of all is the very thread from which communities are woven. + +While I can't magically bring the culture of open source to sewing patterns, I certainly can bring sewing patterns into the open source world. + +[Freesewing.org](https://freesewing.org/) will continue to offer what [Makemypattern.com](https://makemypattern.com/) does today: free sewing patterns drafted to your measurements. +But additionally, it will be open to your contributions. + +Here's hoping that in the Venn diagram of the somewhat geeky and sewing, it's not just me in the middle. + +joost + +## Shout-outs +Freesewing is a project by [Joost De Cock](https://github.com/joostdecock) and contributors. + +Hat-tip to [@jakesgordon](https://github.com/jakesgordon) and [Kevin Lindsey](http://www.kevlindev.com) for allowing me to port some of their code. + +The early-stage enthusiasm and input of +[@diggydev](https://github.com/diggydev), +[@cabi](https://github.com/cabi), +[@woutervdub](https://github.com/woutervdub), +[@cloutiy](https://github.com/cloutiy), +[@straytaoist](https://github.com/straytaoist), +[@netpraxis](https://github.com/netpraxis), +[@Stefan1960](https://github.com/Stefan1960), +[@brendare1](https://github.com/brendare1), +[@JorisJoppe](https://github.com/JorisJoppe), +[@JamJenkins](https://github.com/JamJenkins), and +[@fightingrabbit](https://github.com/fightingrabbit) has been a great boon to this project. + +Thanks to [@annekecaramin](https://twitter.com/annekecaramin) for designing a logo cool enough to put on a Tshirt. + +Special thanks to [@scorchtorch](https://twitter.com/scorchtorch) for being the best at that heart/salad/antlers thing. + +Last but not least, this project would not exist without the users, supporters, and donors of [makemypattern.com](https://makemypattern.com/). + +Thanks guys! diff --git a/markdown/org/blog/announcing-freesewing/fr.md b/markdown/org/blog/announcing-freesewing/fr.md new file mode 100644 index 00000000000..983a7f83dd5 --- /dev/null +++ b/markdown/org/blog/announcing-freesewing/fr.md @@ -0,0 +1,51 @@ +--- +author: "joostdecock" +caption: "Le logo freesewing" +date: "2017-03-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4e1f5426ee6578ef31d9c18a1de9b4beef15836b-2000x1125.jpg" +intro: "Je suis fier de lancer freesewing v1.0.0 et la documentation qui décrit le projet Freesewing en détail." +title: "Freesewing est une plate-forme open source pour des patrons de couture sur mesure" +--- + + +Je suis fier de lancer [freesewing v1.0.0](https://github.com/freesewing/core) et la [documentation](/docs) qui décrit le projet Freesewing en détail. + +Mais je suis aussi réaliste, et je comprends que vous n'ayez pas le temps de lire des pages et des pages. + +Alors voici une histoire résumant l'essentiel de Freesewing : + +## L'origine de Freesewing +Coudre, c'est facile. Vraiment facile. Ce qui est difficile, c'est de le faire bien. C'est pourquoi on utilise un patron de couture. C'est un schéma pour tout ce que vous fabriquez. Un bon patron vous ira bien. Ce n'est pas le cas de la plupart d'entre eux. + +C'est parce que — comme les vêtements dans une boutique — les patrons ont des tailles. Et les tailles sont un moyen rudimentaire de classer les gens. Ils sont faits pour une personne virtuelle moyenne, plutôt que pour vous. + +Il y a un autre moyen, qui est de créer un patron à vos mesures. Ces patrons sur mesure sont bien meilleurs, mais ils nécessitent beaucoup de travail. + +J'ai voulu changer cela, et ça a donné [MakeMyPattern.com](https://makemypattern.com/). J'ai géré ce site pendant plusieurs années, et ce fut un grand succès. Probablement grâce au fait que j'ai diffusé tous les patrons gratuitement. + +Dans le monde de la couture loisir, il semble nécessaire d'expliquer un peu ce qui peut conduire quelqu'un à choisir de diffuser son travail gratuitement. Les choses sont différentes dans le monde de l'open source, où l'idée de partager votre travail avec d'autres pour le bénéfice de tous est le fil conducteur liant les communautés. + +Bien que je ne puisse pas apporter d'un coup de baguette magique la culture de l'open source aux patrons de couture, je peux en tout cas apporter des patrons de couture dans le monde de l'open source. + +[Freesewing.org](https://freesewing.org/) continuera à offrir ce que [Makemypattern.com](https://makemypattern.com/) fait aujourd'hui : des patrons de couture gratuits à vos mesures. Mais de plus, il sera ouvert à vos contributions. + +Pour les geeks : espérons que dans le diagramme de Venn de la couture, il n'y a pas que moi au milieu. + +joost + +## Dédicace spéciale +Freesewing est un projet de [Joost De Cock](https://github.com/joostdecock) et contributeurs. + +Coup de chapeau à [@jakesgordon](https://github.com/jakesgordon) et [Kevin Lindsey](http://www.kevlindev.com) pour m'avoir permis d'utiliser une partie de leur code. + +L'enthousiasme des débuts et les contributions de [@diggydev](https://github.com/diggydev), [@cabi](https://github.com/cabi), [@woutervdub](https://github.com/woutervdub), [@cloutiy](https://github.com/cloutiy), [@straytaoist](https://github.com/straytaoist), [@netpraxis](https://github.com/netpraxis), [@Stefan1960](https://github.com/Stefan1960), [@brendare1](https://github.com/brendare1), [@JorisJoppe](https://github.com/JorisJoppe), [@JamJenkins](https://github.com/JamJenkins), and [@fightingrabbit](https://github.com/fightingrabbit) ont été une bénédiction pour ce projet. + +Merci à [@annekecaramin](https://twitter.com/annekecaramin) d'avoir conçu un logo suffisamment cool pour le mettre sur un Tshirt. + +Remerciements spéciaux à [@scorchtorch](https://twitter.com/scorchtorch) pour être le meilleur en cœur/salade/ramure. + +Et enfin, ce projet n'existerait pas sans les utilisateurs, les supporters et les donateurs de [makemypattern.com](https://makemypattern.com/). + +Merci tout le monde ! + + diff --git a/markdown/org/blog/announcing-freesewing/nl.md b/markdown/org/blog/announcing-freesewing/nl.md new file mode 100644 index 00000000000..8611a06c2ae --- /dev/null +++ b/markdown/org/blog/announcing-freesewing/nl.md @@ -0,0 +1,51 @@ +--- +author: "joostdecock" +caption: "Het FreeSewing-logo" +date: "2017-03-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4e1f5426ee6578ef31d9c18a1de9b4beef15836b-2000x1125.jpg" +intro: "Ik ben heel trots om jullie voor te stellen aan FreeSewing kernversie 1.0.0 en de bijhorende documentatie die het FreeSewing-project in detail beschrijft." +title: "Welkom op FreeSewing, een open-sourceplatform voor naaipatronen op maat" +--- + + +Ik ben heel trots om jullie voor te stellen aan [FreeSewing kernversie 1.0.0](https://github.com/freesewing/core) en de bijhorende [documentatie](/docs) die het FreeSewing-project in detail beschrijft. + +Maar ik ben ook realistisch. Ik snap dat je wellicht geen tijd hebt om door pagina's en pagina's documentatie te waden. + +Dus in plaats daarvan is dit de essentie van FreeSewing in een notendop: + +## Hoe het voor FreeSewing allemaal begonnen is +Naaien is gemakkelijk. Echt. Het moeilijk is om alles zo te krijgen, dat het ook goed past. Daarom gebruik je een naaipatroon. Dat is een blauwdruk van het stuk dat je maakt. Een goed patroon leidt tot een goede pasvorm. De meeste patronen doen dat niet. + +Dat komt doordat naaipatronen — net zoals kleren in de winkel — in verschillende maten worden gemaakt. Een maten zijn een ruwe manier om mensen in hokjes te stoppen. Ze zijn bedacht voor een gemiddelde persoon die niet echt bestaat. Niet voor jou. + +Er is een andere manier om het aan te pakken, en da tis om een patroon uit te tekenen op basis van jouw maten. Zulke patronen op maat zijn veel beter, maar er kruipt veel werk in. + +Dat wilde ik veranderen, en dat plan mondde uit in [MakeMyPattern.com](https://makemypattern.com/). Ik zat een aantal jaar achter die website, en het was een behoorlijk succes. Waarschijnlijk heeft het wel geholpen dat ik alle patronen gratis weggaf. + +In de hobbynaaiwereld vergt het meestal wel wat tekst en uitleg waarom je ervoor zou kiezen om je harde werk gratis weg te geven. In de open-sourcewereld ligt dat anders. Daar zijn hele gemeenschappen gebaseerd op de gedachte dat je jouw werk deelt met anderen zodat het iedereen ten goede komt. + +Ik kan niet magisch de cultuur van open source overzetten naar naaipatronen. Maar ik kan naaipatronen wel introduceren in de open-sourcewereld. + +[FreeSewing.org](https://freesewing.org/) blijft aanbieden wat [MakeMyPattern.com](https://makemypattern.com/) vandaag doet: gratis naaipatronen gebaseerd op jouw maten. Maar daarbovenop zal je er zelf bijdrages aan kunnne leveren. + +En nu maar hopen dat, in het Venn-diagram van nerds en naaien, ik niet de enige ben die pal in het midden zit. + +joost + +## Vermeldenswaardige mensen +FreeSewing is een project van [Joost De Cock](https://github.com/joostdecock) en bijdragers. + +Petje af voor [@jakesgordon](https://github.com/jakesgordon) en [Kevin Lindsey](http://www.kevlindev.com) die me hebben toegestaan om delen van hun code te gebruiken. + +Het vroege enthousiasme en de input van [@diggydev](https://github.com/diggydev), [@cabi](https://github.com/cabi), [@woutervdub](https://github.com/woutervdub), [@cloutiy](https://github.com/cloutiy), [@straytaoist](https://github.com/straytaoist), [@netpraxis](https://github.com/netpraxis), [@Stefan1960](https://github.com/Stefan1960), [@brendare1](https://github.com/brendare1), [@JorisJoppe](https://github.com/JorisJoppe), [@JamJenkins](https://github.com/JamJenkins), and [@fightingrabbit](https://github.com/fightingrabbit) zijn dit project enorm ten goede gekomen. + +Dank aan [@annekecaramin](https://twitter.com/annekecaramin) voor het ontwerp van een logo dat cool genoeg is om op een T-shirt te zetten. + +Bijzondere dank aan [@scorchtorch](https://twitter.com/scorchtorch) om de beste te zijn in dat ding met harten/sla/geweien. + +En ten slotte zou dit project niet bestaan zonder de gebruikers, supporters en schenkers van [MakeMyPattern.com](https://makemypattern.com/). + +Bedankt allemaal! + + diff --git a/markdown/org/blog/announcing-hortensia/de.md b/markdown/org/blog/announcing-hortensia/de.md new file mode 100644 index 00000000000..7685a4e859c --- /dev/null +++ b/markdown/org/blog/announcing-hortensia/de.md @@ -0,0 +1,31 @@ +--- +author: "joostdecock" +caption: "Eine Beispiel-Hortensia, gefertigt vom Designer" +date: "2021-02-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/01f416518b5bf8fb75dcc8ae3ab2691d5532dd65-2000x1500.jpg" +intro: "Ich freue mich, dass ich die unmittelbare Verfügbarkeit unseres neusten FreeSeewing-Schnittmusters vorstellen kann: die Handtasche Hortensia ." +title: "Sagt Hi zu unserem neuesten Schnittmuster: Die Handtasche Hortensia" +--- + + +Ich freue mich, dass ich die unmittelbare Verfügbarkeit unseres neusten FreeSeewing-Schnittmusters vorstellen kann: [die Handtasche Hortensia](/designs/hortensia/). + +Hortensias Ursprung geht zurück auf [@stoffsuchti](https://twitter.com/stoffsuchti). Stoffsuchti wollte ein Schnittmuster für eine Handtasche erstellen, und war auf der Suche nach einer Person, die dieses Design in Code umsetzen kann. + +Es war [Wouter](https://github.com/woutervdub), der den Ruf hörte und das Schnittmuster implementierte, wodurch dies zu einer weiteren Erfolgsgeschichte der FreeSewing-Community wurde. + +## Keine Körpermaße erforderlich + +Dies ist das erste Muster bei FreeSewing, das zum Herstellen gar keine Körpermaße benötigt. Es gibt ein paar Optionen, die du wählen kannst — um beispielsweise die Größe der Handtasche zu kontrollieren —, aber da dies eine Handtasche ist, werden keine Körpermaße gebraucht. + +Das macht Hortensia zu einem tollen Projekt für ein Geschenk, da du dir keine Gedanken über die Passform machen musst. + + + +##### Zeig' uns deine + +Wenn du eine Hortensia herstellst, dann [sende uns gerne Bilder](https://discord.freesewing.org/) davon. + + + + diff --git a/markdown/org/blog/announcing-hortensia/en.md b/markdown/org/blog/announcing-hortensia/en.md new file mode 100644 index 00000000000..ffca2a37cf2 --- /dev/null +++ b/markdown/org/blog/announcing-hortensia/en.md @@ -0,0 +1,34 @@ +--- +author: "joostdecock" +caption: "An example Hortensia made by the designer" +date: "2021-02-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/01f416518b5bf8fb75dcc8ae3ab2691d5532dd65-2000x1500.jpg" +intro: "I'm happy to announce the immeadiate availability of our latest FreeSewing pattern: the Hortensia handbag ." +title: "Say hi to our latest pattern: The Hortensia handbag" +--- + + +I'm happy to announce the immeadiate availability of our latest FreeSewing pattern: [the Hortensia handbag](/designs/hortensia/). + +Hortensia's origin story traces back to [@stoffsuchti](https://twitter.com/stoffsuchti) who wanted +to create a pattern for a handbag, and was looking for somebody who could implement that design in code. + +It was [Wouter](https://github.com/woutervdub) who answered the call and implemented the pattern, +making this another success story from the FreeSewing community. + +## No measurements needed + +This is the first pattern on FreeSewing that does not require any measurements to make. +There's some options you can choose — to control the size of the handbag for one thing — but +since this is a handbag, no measurements are needed. + +This makes Hortensia a great project to make as a gift, since there's no need to worry about fit. + + + +##### Now show us yours + +If you do make a Hortensia, do [send us pictures](https://discord.freesewing.org/). + + + diff --git a/markdown/org/blog/announcing-hortensia/es.md b/markdown/org/blog/announcing-hortensia/es.md new file mode 100644 index 00000000000..97c952bd15f --- /dev/null +++ b/markdown/org/blog/announcing-hortensia/es.md @@ -0,0 +1,34 @@ +--- +author: "joostdecock" +caption: "An example Hortensia made by the designer" +date: "2021-02-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/01f416518b5bf8fb75dcc8ae3ab2691d5532dd65-2000x1500.jpg" +intro: "I'm happy to announce the immeadiate availability of our latest FreeSewing pattern: the Hortensia handbag ." +title: "Say hi to our latest pattern: The Hortensia handbag [No traducido]" +--- + + +I'm happy to announce the immeadiate availability of our latest FreeSewing pattern: [the Hortensia handbag](/designs/hortensia/). + +Hortensia's origin story traces back to [@stoffsuchti](https://twitter.com/stoffsuchti) who wanted +to create a pattern for a handbag, and was looking for somebody who could implement that design in code. + +It was [Wouter](https://github.com/woutervdub) who answered the call and implemented the pattern, +making this another success story from the FreeSewing community. + +## No measurements needed + +This is the first pattern on FreeSewing that does not require any measurements to make. +There's some options you can choose — to control the size of the handbag for one thing — but +since this is a handbag, no measurements are needed. + +This makes Hortensia a great project to make as a gift, since there's no need to worry about fit. + + + +##### Now show us yours + +If you do make a Hortensia, do [send us pictures](https://discord.freesewing.org/). + + + diff --git a/markdown/org/blog/announcing-hortensia/fr.md b/markdown/org/blog/announcing-hortensia/fr.md new file mode 100644 index 00000000000..cb551a11b75 --- /dev/null +++ b/markdown/org/blog/announcing-hortensia/fr.md @@ -0,0 +1,31 @@ +--- +author: "joostdecock" +caption: "Un exemple de Hortensia fait par le designer" +date: "2021-02-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/01f416518b5bf8fb75dcc8ae3ab2691d5532dd65-2000x1500.jpg" +intro: "Je suis heureux d'annoncer la disponibilité immédiate de notre dernier modèle FreeSewing : le sac à main Hortensia ." +title: "Dites bonjour à notre dernier modèle : le sac à main Hortensia" +--- + + +Je suis heureux d'annoncer la disponibilité immédiate de notre dernier modèle FreeSewing : [le sac à main Hortensia](/designs/hortensia/). + +Hortensia's origin story traces back to [@stoffsuchti](https://twitter.com/stoffsuchti) who wanted to create a pattern for a handbag, and was looking for somebody who could implement that design in code. + +C'est [Wouter](https://github.com/woutervdub) qui a répondu à l'appel et développé le patron, ce qui fait de cette histoire le nouveau succès de la communauté FreeSewing. + +## Aucune mesure nécessaire + +C'est le premier modèle sur FreeSewing qui ne nécessite aucune mesure à faire. Il y a quelques options que vous pouvez choisir — dont le fait de contrôler la taille du sac à main — mais puisqu'il s'agit d'un sac à main, aucune mesure n'est nécessaire. + +Cela fait de Hortensia un grand projet à faire en cadeau, car il n'y a pas besoin de s'inquiéter de l'ajustement. + + + +##### Now show us yours + +If you do make a Hortensia, do [send us pictures](https://discord.freesewing.org/). + + + + diff --git a/markdown/org/blog/announcing-hortensia/nl.md b/markdown/org/blog/announcing-hortensia/nl.md new file mode 100644 index 00000000000..7b20d96c10c --- /dev/null +++ b/markdown/org/blog/announcing-hortensia/nl.md @@ -0,0 +1,34 @@ +--- +author: "joostdecock" +caption: "An example Hortensia made by the designer" +date: "2021-02-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/01f416518b5bf8fb75dcc8ae3ab2691d5532dd65-2000x1500.jpg" +intro: "I'm happy to announce the immeadiate availability of our latest FreeSewing pattern: the Hortensia handbag ." +title: "Say hi to our latest pattern: The Hortensia handbag [Niet vertaald]" +--- + + +I'm happy to announce the immeadiate availability of our latest FreeSewing pattern: [the Hortensia handbag](/designs/hortensia/). + +Hortensia's origin story traces back to [@stoffsuchti](https://twitter.com/stoffsuchti) who wanted +to create a pattern for a handbag, and was looking for somebody who could implement that design in code. + +It was [Wouter](https://github.com/woutervdub) who answered the call and implemented the pattern, +making this another success story from the FreeSewing community. + +## No measurements needed + +This is the first pattern on FreeSewing that does not require any measurements to make. +There's some options you can choose — to control the size of the handbag for one thing — but +since this is a handbag, no measurements are needed. + +This makes Hortensia a great project to make as a gift, since there's no need to worry about fit. + + + +##### Now show us yours + +If you do make a Hortensia, do [send us pictures](https://discord.freesewing.org/). + + + diff --git a/markdown/org/blog/announcing-penelope/de.md b/markdown/org/blog/announcing-penelope/de.md new file mode 100644 index 00000000000..fae221c722c --- /dev/null +++ b/markdown/org/blog/announcing-penelope/de.md @@ -0,0 +1,33 @@ +--- +author: "joostdecock" +caption: "Die Schnittmusterdarstellung für Penelope" +date: "2018-06-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/59646d7171bb8b18df952a1c9547cd212451de79-1920x1080.jpg" +intro: "Ich freue mich sehr die sofortige Verfügbarkeit des Bleistiftrock Penelope in der Beta-Version bekanntzugeben." +title: "Ankündigung des Penelope Bleistiftrockes; Und unsere Damenmode-Roadmap" +--- + + +Ich freue mich sehr die sofortige Verfügbarkeit des [Bleistiftrock Penelope](/patterns/penelope)in der Beta-Version bekanntzugeben. + +![Eine Linienzeichnung von Penelope](linedrawing.svg) + +Penelope wurde entworfen von [@woutervdub](/users/woutervdub) der auch für [Benjamin](/patterns/benjamin) verantwortlich zeichnet. + +## Freies Nähen ist nicht (nur) für Herrenmode + +Dieser neue Ausflug in die Damenmode deutet auf unsere Pläne für die zweite Jahreshälfte hin. Das ist richtig, wir werden mehr Schnitte für Damen herausbringen. + +FreeSewing hat einen gewissen Ruf als Herrenmode-Anbieter, weil wir in der Vergangenheit viel mehr Schnittmuster für Männer als für Frauen hatten. Aber das bedeutet nicht, dass Frauen hier Bürger zweiter Klasse sind. Es ist nur ein Nebeneffekt davon, dass dieses Projekt in der Vergangenheit von einem Mann betrieben wurde. Kannst du es einem Bruder verübeln, dass er Schnitte entworfen hat, die er selbst tragen möchte? + +Heute ist das FreeSewing eine gemeinschaftliche Anstrengung, und es sind viele Damen beteiligt. Es macht also nur Sinn, sich bewusst zu bemühen, etwas für unsere Schwestern zu tun. Und genau das werden wir tun. + +Wir haben ein weiteres Modell in der Pipeline, das nicht nur für Frauen, sondern auch für eine Frau gemacht ist. Das von [@AlfaLyr](/users/alfalyr) entworfene Tellerrockschnittmuster wird hier schon bald aufgeschaltet. + +Parallel dazu werde ich mit [@AnnekeCaramin](/users/annekecaramin) an einem weiblichen Äquivalent für [Brian](/patterns/brian) arbeiten, unser Grundschnitt, auf dem viele unserer Muster basieren. Die Idee ist es, einen hochwertigen Oberteilgrundschnitt für Damen herzustellen, der nach Maß gefertigt wird, so können die häufigsten Passformprobleme automatisch gehandhabt werden. Ich spreche da von Fullbustadjustment, Sway-back und ergleichen Dinge. + +Sobald wir diesen Grundschnitt haben, können Sie davon ausgehen, dass wir ihn in einen Haufen Kleider und Oberteile umwandeln. + +Und wie immer, wenn Sie über Fähigkeiten im Bereich Schnittdesign verfügen, sich aber von der Plattform etwas eingeschüchtert fühlen, kontaktieren Sie uns, um zu sehen, ob wir unsere Kräfte bündeln können, um Ihre Ideen zu verwirklichen. + + diff --git a/markdown/org/blog/announcing-penelope/en.md b/markdown/org/blog/announcing-penelope/en.md new file mode 100644 index 00000000000..50c768d7482 --- /dev/null +++ b/markdown/org/blog/announcing-penelope/en.md @@ -0,0 +1,46 @@ +--- +author: "joostdecock" +caption: "The pattern illustration for Penelope" +date: "2018-06-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/59646d7171bb8b18df952a1c9547cd212451de79-1920x1080.jpg" +intro: "I'm very happy to announce the immeadiate availability of the Penelope Pencil Skirt , out in beta today." +title: "Announcing the Penelope Pencil Skirt; And our womenswear roadmap" +--- + +I'm very happy to announce the immeadiate availability of +[the Penelope Pencil Skirt](/patterns/penelope), out in beta today. + +![A linedrawing of Penelope](linedrawing.svg) + +Penelope was designed by +[@woutervdub](/users/woutervdub) who also signed for [benjamin](/patterns/benjamin). + +## Freesewing is not (just) for menswear + +This new foray into womenswear foreshadows our plans for the second half of this year. +That's right, we're going to be making more patterns for ladies. + +Freesewing has a bit of a menswear reputation, +since historically we've had a lot more patterns for men than for ladies. +But that doesn't mean women are second-class citizens here. +It's just a side-effect of how this project was historically run by a man. +Can you blame a brother for designing patterns he'd like to wear himself? + +Today, freesewing is a communal effort, and there's plenty of ladies involved. +So it only make sense to make a conscious effort to do something for our sisters. +And that's exactly what we'll be doing. + +We've got another pattern in the pipeline that is not only for women, but also by a woman. +By [@AlfaLyr](/users/alfalyr) in particular, who has designed a circle skirt pattern that +is going to land here real soon. + +In parallel, I'll be working with [@AnnekeCaramin](/users/annekecaramin) on a female equivalent for +[Brian](/patterns/brian), our basic body block on which many of our patterns are based. +The idea is to make a quality bodice block for ladies that is made-to-measure and +can handle the common fitting issues automatically. I'm talking about full bust adjustment, sway back, these kind of things. + +Once we have that block, expect us to spin it into a bunch of dresses and tops. + +And as always, if you have pattern design skills but are a bit intimidated by the platform, +reach out to us to see if we can join forces to make your ideas a reality. + diff --git a/markdown/org/blog/announcing-penelope/es.md b/markdown/org/blog/announcing-penelope/es.md new file mode 100644 index 00000000000..2a5a02233b8 --- /dev/null +++ b/markdown/org/blog/announcing-penelope/es.md @@ -0,0 +1,46 @@ +--- +author: "joostdecock" +caption: "The pattern illustration for Penelope" +date: "2018-06-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/59646d7171bb8b18df952a1c9547cd212451de79-1920x1080.jpg" +intro: "I'm very happy to announce the immeadiate availability of the Penelope Pencil Skirt , out in beta today." +title: "Announcing the Penelope Pencil Skirt; And our womenswear roadmap [No traducido]" +--- + +I'm very happy to announce the immeadiate availability of +[the Penelope Pencil Skirt](/patterns/penelope), out in beta today. + +![A linedrawing of Penelope](linedrawing.svg) + +Penelope was designed by +[@woutervdub](/users/woutervdub) who also signed for [benjamin](/patterns/benjamin). + +## Freesewing is not (just) for menswear + +This new foray into womenswear foreshadows our plans for the second half of this year. +That's right, we're going to be making more patterns for ladies. + +Freesewing has a bit of a menswear reputation, +since historically we've had a lot more patterns for men than for ladies. +But that doesn't mean women are second-class citizens here. +It's just a side-effect of how this project was historically run by a man. +Can you blame a brother for designing patterns he'd like to wear himself? + +Today, freesewing is a communal effort, and there's plenty of ladies involved. +So it only make sense to make a conscious effort to do something for our sisters. +And that's exactly what we'll be doing. + +We've got another pattern in the pipeline that is not only for women, but also by a woman. +By [@AlfaLyr](/users/alfalyr) in particular, who has designed a circle skirt pattern that +is going to land here real soon. + +In parallel, I'll be working with [@AnnekeCaramin](/users/annekecaramin) on a female equivalent for +[Brian](/patterns/brian), our basic body block on which many of our patterns are based. +The idea is to make a quality bodice block for ladies that is made-to-measure and +can handle the common fitting issues automatically. I'm talking about full bust adjustment, sway back, these kind of things. + +Once we have that block, expect us to spin it into a bunch of dresses and tops. + +And as always, if you have pattern design skills but are a bit intimidated by the platform, +reach out to us to see if we can join forces to make your ideas a reality. + diff --git a/markdown/org/blog/announcing-penelope/fr.md b/markdown/org/blog/announcing-penelope/fr.md new file mode 100644 index 00000000000..ae8e98b1339 --- /dev/null +++ b/markdown/org/blog/announcing-penelope/fr.md @@ -0,0 +1,46 @@ +--- +author: "joostdecock" +caption: "The pattern illustration for Penelope" +date: "2018-06-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/59646d7171bb8b18df952a1c9547cd212451de79-1920x1080.jpg" +intro: "I'm very happy to announce the immeadiate availability of the Penelope Pencil Skirt , out in beta today." +title: "Announcing the Penelope Pencil Skirt; And our womenswear roadmap [Non traduit]" +--- + +I'm very happy to announce the immeadiate availability of +[the Penelope Pencil Skirt](/patterns/penelope), out in beta today. + +![A linedrawing of Penelope](linedrawing.svg) + +Penelope was designed by +[@woutervdub](/users/woutervdub) who also signed for [benjamin](/patterns/benjamin). + +## Freesewing is not (just) for menswear + +This new foray into womenswear foreshadows our plans for the second half of this year. +That's right, we're going to be making more patterns for ladies. + +Freesewing has a bit of a menswear reputation, +since historically we've had a lot more patterns for men than for ladies. +But that doesn't mean women are second-class citizens here. +It's just a side-effect of how this project was historically run by a man. +Can you blame a brother for designing patterns he'd like to wear himself? + +Today, freesewing is a communal effort, and there's plenty of ladies involved. +So it only make sense to make a conscious effort to do something for our sisters. +And that's exactly what we'll be doing. + +We've got another pattern in the pipeline that is not only for women, but also by a woman. +By [@AlfaLyr](/users/alfalyr) in particular, who has designed a circle skirt pattern that +is going to land here real soon. + +In parallel, I'll be working with [@AnnekeCaramin](/users/annekecaramin) on a female equivalent for +[Brian](/patterns/brian), our basic body block on which many of our patterns are based. +The idea is to make a quality bodice block for ladies that is made-to-measure and +can handle the common fitting issues automatically. I'm talking about full bust adjustment, sway back, these kind of things. + +Once we have that block, expect us to spin it into a bunch of dresses and tops. + +And as always, if you have pattern design skills but are a bit intimidated by the platform, +reach out to us to see if we can join forces to make your ideas a reality. + diff --git a/markdown/org/blog/announcing-penelope/nl.md b/markdown/org/blog/announcing-penelope/nl.md new file mode 100644 index 00000000000..a2b733c6f1e --- /dev/null +++ b/markdown/org/blog/announcing-penelope/nl.md @@ -0,0 +1,33 @@ +--- +author: "joostdecock" +caption: "De patroon illustratie voor Penelope" +date: "2018-06-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/59646d7171bb8b18df952a1c9547cd212451de79-1920x1080.jpg" +intro: "Ik ben erg blij om de beschikbaarheid van de Penelope Kokerrok vandaag aan te kondigen (in beta)." +title: "Aankondiging van de Penelope Kokerrok; en onze strategie voor dameskleding" +--- + + +Ik ben erg blij om de beschikbaarheid van [de Penelope Kokerrok](/patterns/penelope) vandaag aan te kondigen (in beta). + +![Een linetekening van Penelope](linedrawing.svg) + +Penelope is ontworpen door [@woutervdub](/users/woutervdub), die ook [benjamin](/patterns/benjamin) heeft gemaakt. + +## Freesewing is niet (alleen) voor mannen + +Dit initiatief is een laat zien wat onze plannen zijn voor de tweede helft van dit jaar. Ja, we gaan meer patronen maken voor de dames. + +Freesewing heeft een reputatie voor mannenkleding, want we hebben altijd meer patronen voor mannen dan voor dames gehad. Maar dat betekent niet dat dames ondergewaardeerd zijn hier. Het is gewoon een reflectie van een project dat door een kerel gemaakt is. Kun je hem kwalijk nemen dat hij patronen maakte die hij zelf graag zou dragen? + +Maar Freesewing is nu een project dat door de gemeenschap gedragen wordt, en er zijn genoeg dames die eraan meewerken. Het is dus een goed idee om gericht iets te doen voor de dames. En dat is wat we gaan doen. + +We hebben een ander patroon in de pijplijn dat niet alleen voor dames is, maar ook door eentje gemaakt is. Met name door [@AlfaLyr](/users/alfalyr), die een cirkelrok patroon heeft ontworpen dat hier binnenkort gelanceerd wordt. + +Tegelijkertijd ga ik met [@AnnekeCaramin](/users/annekecaramin) aan een dames versie van [Brian](/patterns/brian), ons basis blok van vele patronen, werken. Het idee is om een kwaliteits blok voor dames te maken voor hun maten werkt, en automatisch dagelijkse pas problemen verhandeld. Ik heb het over aanpassingen voor een volle buste, een holle rug, dat soort dingen. + +Als we dat blok hebben, verwachten we dat we het in een hele reeks jurken en topjes zullen verwerken. + +En zoals altijd, als je patroon ontwerpvaardigheden hebt maar een beetje geïntimideerd wordt door het platform, reik naar ons uit om te zien of we samen kunnen werken om je ideeën werkelijkheid te maken. + + diff --git a/markdown/org/blog/announcing-sandy/de.md b/markdown/org/blog/announcing-sandy/de.md new file mode 100644 index 00000000000..fd833bb44d5 --- /dev/null +++ b/markdown/org/blog/announcing-sandy/de.md @@ -0,0 +1,23 @@ +--- +author: "joostdecock" +caption: "Wusstest du, dass Sandy nach Olivia Newton-Johns Figur im Film \"Grease\" benannt wurde?" +date: "2018-08-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/dc69133dd70791871c13267e14c24f70dc797693-1920x1280.jpg" +intro: "Meine Damen und Herren --- denn wer sagt, dass Männer keine Röcke tragen können --- Ich freue mich, die sofortige Verfügbarkeit unseres neuesten FreeSewing-Schnittmusters bekannt zu geben: der Tellerrock Sandy ." +title: "Ankündigung von Sandy, einem Tellerrock, der von @AlfyLyr entworfen wurde" +--- + + +Meine Damen und Herren --- denn wer sagt, dass Männer keine Röcke tragen können --- Ich freue mich, die sofortige Verfügbarkeit unseres neuesten FreeSewing-Schnittmusters bekannt zu geben: [der Tellerrock Sandy](/patterns/sandy). + +Sandy wurde von [@AlfaLyr](/users/alfalyr) entworfen, die wirklich einen hervorragenden Job gemacht haben. Das macht es auch zu einem weiteren Schnittmuster aus der Freesewing-Community, wovon ich sehr begeistert bin. + +## Alle die Optionen + +Wie viele Muster hier beim FreeSewing, kommt Sandy mit einer Reihe von Optionen, die es Ihnen ermöglichen, Ihren Rock nach Ihren Wünschen zu gestalten. + +Es gibt Optionen dafür, wie viel vom Kreis Sie haben wollen (halb? voll? Etwas dazwischen?), wie lange Sie ihn haben wollen, die Form und Überlappung des Taillenbundes, ob Sie Falten wollen, wie viel Saum, und so weiter. + +Ich sehe, dass dies mehr und mehr zur Erfolgsgeschichte wird. Also los und [ gönnen Sie sich einen neuen Rock](/draft/sandy), und lassen Sie [@AlfyLyr](/users/alfalyr) wissen, wie es für Sie funktioniert. + + diff --git a/markdown/org/blog/announcing-sandy/en.md b/markdown/org/blog/announcing-sandy/en.md new file mode 100644 index 00000000000..4ed05806c80 --- /dev/null +++ b/markdown/org/blog/announcing-sandy/en.md @@ -0,0 +1,22 @@ +--- +author: "joostdecock" +caption: "Did you know that Sandy was named after Olivia Newton-John's character in the move Grease?" +date: "2018-08-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/dc69133dd70791871c13267e14c24f70dc797693-1920x1280.jpg" +intro: "Ladies and gentlemen --- because who says men can't wear skirts --- I am happy to announce the immeadiate availability of our latest freesewing pattern: the Sandy circle skirt ." +title: "Announcing Sandy, a circle skirt designed by @AlfyLyr" +--- + +Ladies and gentlemen --- because who says men can't wear skirts --- I am happy to announce the immeadiate availability of our latest freesewing pattern: [the Sandy circle skirt](/patterns/sandy). + +Sandy was designed by [@AlfaLyr](/users/alfalyr) who really did a stellar job. This makes it also another pattern from the freesewing community, something that I'm very excited about. + +## All the options + +As many patterns here at freesewing, Sandy comes with a bunch of options to allow you to customize your skirt to your wishes. + +There's options for how much of circle you want (half? full? Something else?), how long you want it, the shape and overlap of the waistband, whether you want pleats, how much hem, and so on. + +I can see this becoming rather the success story. +So go and [treat yourself to a new skirt](/draft/sandy), and let [@AlfyLyr](/users/alfalyr) know how it works out for you. + diff --git a/markdown/org/blog/announcing-sandy/es.md b/markdown/org/blog/announcing-sandy/es.md new file mode 100644 index 00000000000..868f688357d --- /dev/null +++ b/markdown/org/blog/announcing-sandy/es.md @@ -0,0 +1,22 @@ +--- +author: "joostdecock" +caption: "Did you know that Sandy was named after Olivia Newton-John's character in the move Grease?" +date: "2018-08-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/dc69133dd70791871c13267e14c24f70dc797693-1920x1280.jpg" +intro: "Ladies and gentlemen --- because who says men can't wear skirts --- I am happy to announce the immeadiate availability of our latest freesewing pattern: the Sandy circle skirt ." +title: "Announcing Sandy, a circle skirt designed by @AlfyLyr [No traducido]" +--- + +Ladies and gentlemen --- because who says men can't wear skirts --- I am happy to announce the immeadiate availability of our latest freesewing pattern: [the Sandy circle skirt](/patterns/sandy). + +Sandy was designed by [@AlfaLyr](/users/alfalyr) who really did a stellar job. This makes it also another pattern from the freesewing community, something that I'm very excited about. + +## All the options + +As many patterns here at freesewing, Sandy comes with a bunch of options to allow you to customize your skirt to your wishes. + +There's options for how much of circle you want (half? full? Something else?), how long you want it, the shape and overlap of the waistband, whether you want pleats, how much hem, and so on. + +I can see this becoming rather the success story. +So go and [treat yourself to a new skirt](/draft/sandy), and let [@AlfyLyr](/users/alfalyr) know how it works out for you. + diff --git a/markdown/org/blog/announcing-sandy/fr.md b/markdown/org/blog/announcing-sandy/fr.md new file mode 100644 index 00000000000..e48ca742d24 --- /dev/null +++ b/markdown/org/blog/announcing-sandy/fr.md @@ -0,0 +1,22 @@ +--- +author: "joostdecock" +caption: "Did you know that Sandy was named after Olivia Newton-John's character in the move Grease?" +date: "2018-08-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/dc69133dd70791871c13267e14c24f70dc797693-1920x1280.jpg" +intro: "Ladies and gentlemen --- because who says men can't wear skirts --- I am happy to announce the immeadiate availability of our latest freesewing pattern: the Sandy circle skirt ." +title: "Announcing Sandy, a circle skirt designed by @AlfyLyr [Non traduit]" +--- + +Ladies and gentlemen --- because who says men can't wear skirts --- I am happy to announce the immeadiate availability of our latest freesewing pattern: [the Sandy circle skirt](/patterns/sandy). + +Sandy was designed by [@AlfaLyr](/users/alfalyr) who really did a stellar job. This makes it also another pattern from the freesewing community, something that I'm very excited about. + +## All the options + +As many patterns here at freesewing, Sandy comes with a bunch of options to allow you to customize your skirt to your wishes. + +There's options for how much of circle you want (half? full? Something else?), how long you want it, the shape and overlap of the waistband, whether you want pleats, how much hem, and so on. + +I can see this becoming rather the success story. +So go and [treat yourself to a new skirt](/draft/sandy), and let [@AlfyLyr](/users/alfalyr) know how it works out for you. + diff --git a/markdown/org/blog/announcing-sandy/nl.md b/markdown/org/blog/announcing-sandy/nl.md new file mode 100644 index 00000000000..c290f079ba9 --- /dev/null +++ b/markdown/org/blog/announcing-sandy/nl.md @@ -0,0 +1,23 @@ +--- +author: "joostdecock" +caption: "Wist je dat Sandy vernoemd is naar het personage dat Olivia Newton-John speelt in de film Grease?" +date: "2018-08-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/dc69133dd70791871c13267e14c24f70dc797693-1920x1280.jpg" +intro: "Dames en heren – want wie zegt dat heren geen rokken kunnen dragen? – het doet me plezier om jullie te kunnen melden dat ons nieuwste FreeSewing-patroon onmiddellijk beschikbaar is: de Sandy-cirkelrok ." +title: "Verwelkom Sandy, een cirkelrok ontworpen door @AlfyLyr" +--- + + +Dames en heren – want wie zegt dat heren geen rokken kunnen dragen? – het doet me plezier om jullie te kunnen melden dat ons nieuwste FreeSewing-patroon onmiddellijk beschikbaar is: [de Sandy-cirkelrok](/patterns/sandy). + +Sandy is ontworpen door [@AlfaLyr](/users/alfalyr) die er echt een hoogvlieger van heeft gemaakt. Dit betekent ook dat Sandy een patroon is dat uit de FreeSewing-community voortkomt, en dat vind ik echt geweldig. + +## Alle opties + +Zoals wel meer patronen hier bij FreeSewing, krijg je bij Sandy een hele hoop opties om de rok aan te passen aan jouw wensen. + +Er is een optie voor hoe groot je de cirkel wil hebben (een halve? een volle? nog iets anders?), hoe lang je de rok wil, de vorm en overlapping van de tailleband, of je plooien wil, hoe diep je zoom wordt, enzovoort. + +Volgens mij wordt dit echt een succesverhaal. Dus, hup! [Trakteer jezelf op een nieuwe rok](/draft/sandy) en laat aan [@AlfyLyr](/users/alfalyr) weten wat het resultaat is. + + diff --git a/markdown/org/blog/announcing-shin/de.md b/markdown/org/blog/announcing-shin/de.md new file mode 100644 index 00000000000..f7466b3de4b --- /dev/null +++ b/markdown/org/blog/announcing-shin/de.md @@ -0,0 +1,31 @@ +--- +author: "joostdecock" +caption: "Ich schätze, so sieht Augmented Reality aus?" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b471275001689bd4819d6d95aabc8134788dc612-1694x1129.jpg" +intro: "Vor einer Weile stellte ich fest, dass ich Badehosen benötige. Also habe ich ein Schnittmuster gezeichnet und hab mir welche genäht:" +title: "Ankündigung von Shin, einem Badehosenschnitt" +--- + + +Vor einer Weile stellte ich fest, dass ich Badehosen benötige. Also habe ich ein Schnittmuster gezeichnet und hab mir welche genäht: + +![Ein früher Versuch des Shin-Schnitmusters](sample.jpg) + +Ich fragte, ob die Leute an einem solchen Muster interessiert wären, und stellte fest, dass sie es waren. + +Also, nach einigen weiteren Optimierungen, denke ich, dass dies für euch Jungs bereit ist, und inzwischen hat Roy auch schon eine Illustration dafür geliefert. + +![Ich werde der Erste sein, der zugibt, dass dieser Typ es besser trägt als ich](cover.jpg) + +## Optionen und Dokumentation verfügbar + +Shin kommt mit Optionen, und sie sind sehr nahe an den verfügbaren Optionen für [Bruce](/patterns/bruce). + +Alle [Optionen sind dokumentiert](/docs/patterns/shin/options), sowie die [benötigten Maße](/docs/patterns/shin/measurements), und ich habe auch eine [Anleitung geschrieben, wie man das macht](/docs/patterns/shin). + +Ich muss noch die Illustrationen dazu machen, aber es ist wirklich nicht schwer, also werden Sie die Anleitung wahrscheinlich es ohne sie verstehen. Im Grunde genommen können Sie jetzt sofort loslegen und das Ganze durchziehen. + +Viel Spaß! + + diff --git a/markdown/org/blog/announcing-shin/en.md b/markdown/org/blog/announcing-shin/en.md new file mode 100644 index 00000000000..c0102e08965 --- /dev/null +++ b/markdown/org/blog/announcing-shin/en.md @@ -0,0 +1,36 @@ +--- +author: "joostdecock" +caption: "I guess this is what augmented reality looks like?" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b471275001689bd4819d6d95aabc8134788dc612-1694x1129.jpg" +intro: "A while ago I found myself in need of some new swim trunks. So I drafted a pattern and made some:" +title: "Announcing Shin, a swim trunks pattern" +--- + +A while ago I found myself in need of some new swim trunks. So I drafted a pattern and made some: + +![An early tryout of the Shin pattern](https://posts.freesewing.org/uploads/sample_0437fef846.jpg) + +I asked if people would be interested in a pattern like this, and turns out that yes, they were. + +So, after some more tweaking, I think this is ready for you guys, and meanwhile Roy +has already provided an illustration for it too. + +![I'll be the first to admit that this guy wears it better than me](https://posts.freesewing.org/uploads/shin_0dc5fdd06d.jpg) + +## Options and documentation available + +Shin comes with options, and they are very close to the options available for +[Bruce](/designs/bruce). + +All [options are documented](/docs/patterns/shin/options), +as are the [required measurements](/docs/patterns/shin/measurements), +and I've also written [instructions for how to make this](/docs/patterns/shin). + +I still have to do the illustrations, but it's really not hard so you'll probably +figure it out without them. +Essentially, you can go and make this right now. + +Enjoy! + + diff --git a/markdown/org/blog/announcing-shin/es.md b/markdown/org/blog/announcing-shin/es.md new file mode 100644 index 00000000000..cba0c941d7a --- /dev/null +++ b/markdown/org/blog/announcing-shin/es.md @@ -0,0 +1,36 @@ +--- +author: "joostdecock" +caption: "I guess this is what augmented reality looks like?" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b471275001689bd4819d6d95aabc8134788dc612-1694x1129.jpg" +intro: "A while ago I found myself in need of some new swim trunks. So I drafted a pattern and made some:" +title: "Announcing Shin, a swim trunks pattern [No traducido]" +--- + +A while ago I found myself in need of some new swim trunks. So I drafted a pattern and made some: + +![An early tryout of the Shin pattern](https://posts.freesewing.org/uploads/sample_0437fef846.jpg) + +I asked if people would be interested in a pattern like this, and turns out that yes, they were. + +So, after some more tweaking, I think this is ready for you guys, and meanwhile Roy +has already provided an illustration for it too. + +![I'll be the first to admit that this guy wears it better than me](https://posts.freesewing.org/uploads/shin_0dc5fdd06d.jpg) + +## Options and documentation available + +Shin comes with options, and they are very close to the options available for +[Bruce](/designs/bruce). + +All [options are documented](/docs/patterns/shin/options), +as are the [required measurements](/docs/patterns/shin/measurements), +and I've also written [instructions for how to make this](/docs/patterns/shin). + +I still have to do the illustrations, but it's really not hard so you'll probably +figure it out without them. +Essentially, you can go and make this right now. + +Enjoy! + + diff --git a/markdown/org/blog/announcing-shin/fr.md b/markdown/org/blog/announcing-shin/fr.md new file mode 100644 index 00000000000..7424b1882e0 --- /dev/null +++ b/markdown/org/blog/announcing-shin/fr.md @@ -0,0 +1,36 @@ +--- +author: "joostdecock" +caption: "I guess this is what augmented reality looks like?" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b471275001689bd4819d6d95aabc8134788dc612-1694x1129.jpg" +intro: "A while ago I found myself in need of some new swim trunks. So I drafted a pattern and made some:" +title: "Announcing Shin, a swim trunks pattern [Non traduit]" +--- + +A while ago I found myself in need of some new swim trunks. So I drafted a pattern and made some: + +![An early tryout of the Shin pattern](https://posts.freesewing.org/uploads/sample_0437fef846.jpg) + +I asked if people would be interested in a pattern like this, and turns out that yes, they were. + +So, after some more tweaking, I think this is ready for you guys, and meanwhile Roy +has already provided an illustration for it too. + +![I'll be the first to admit that this guy wears it better than me](https://posts.freesewing.org/uploads/shin_0dc5fdd06d.jpg) + +## Options and documentation available + +Shin comes with options, and they are very close to the options available for +[Bruce](/designs/bruce). + +All [options are documented](/docs/patterns/shin/options), +as are the [required measurements](/docs/patterns/shin/measurements), +and I've also written [instructions for how to make this](/docs/patterns/shin). + +I still have to do the illustrations, but it's really not hard so you'll probably +figure it out without them. +Essentially, you can go and make this right now. + +Enjoy! + + diff --git a/markdown/org/blog/announcing-shin/nl.md b/markdown/org/blog/announcing-shin/nl.md new file mode 100644 index 00000000000..8597105288e --- /dev/null +++ b/markdown/org/blog/announcing-shin/nl.md @@ -0,0 +1,31 @@ +--- +author: "joostdecock" +caption: "Dit is hoe augmented reality eruitziet ... denk ik?" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b471275001689bd4819d6d95aabc8134788dc612-1694x1129.jpg" +intro: "Een tijdje geleden stelde ik vast dat ik een nieuwe zwembroek nodig had. Dus heb ik een patroon geschetst en er eentje gemaakt:" +title: "Verwelkom Shin, een zwembroekpatroon" +--- + + +Een tijdje geleden stelde ik vast dat ik een nieuwe zwembroek nodig had. Dus heb ik een patroon geschetst en er eentje gemaakt: + +![Een vroege test van het Shin-patroon](sample.jpg) + +Ik vroeg rond aan mensen of ze geïnteresseerd zouden zijn in dit soort van patroon, en het bleek van wel. + +Dus na een rondje aanpassingen denk ik dat dit klaar is voor jullie. Roy heeft er intussen ook een illustratie voor gemaakt. + +![Laat me de eerste zijn om toe te geven dat deze kerel 'm beter draagt dan ik.](cover.jpg) + +## Beschikbare opties en documentatie + +Je hebt een aantal opties met Shin en die liggen heel dicht bij de beschikbare opties voor [Bruce](/patterns/bruce). + +Alle [opties zijn gedocumenteerd](/docs/patterns/shin/options), net zoals de [afmetingen die je nodig hebt](/docs/patterns/shin/measurements), en ik heb ook [instructies voor Shin](/docs/patterns/shin) geschreven. + +Ik moet nog illustraties maken voor de instructies, maar het is echt niet moeilijk dus volgens mij kan je aan de slag zonder tekeningen. Eigenlijk kan je gewoon meteen aan de slag. + +Veel plezier! + + diff --git a/markdown/org/blog/announcing-sven/de.md b/markdown/org/blog/announcing-sven/de.md new file mode 100644 index 00000000000..aa72beb47d6 --- /dev/null +++ b/markdown/org/blog/announcing-sven/de.md @@ -0,0 +1,21 @@ +--- +author: "joostdecock" +caption: "Ein Sven für das Büro. Wie in, irgendwie langweilig" +date: "2017-07-09" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b0c9b0cb38bce095739109946a99b6cda63e7cd9-1000x667.jpg" +intro: "Winter veranlasste mich, dieses Schnitt zu entwerfen. Mir war kalt und ich brauchte ein paar Pullover, also was macht man da?" +title: "Ankündigung des Pullovers Sven; ein einfacher Pullover, der auf dem Grundschnitt von Brian basiert" +--- + + +Winter veranlasste mich, dieses Schnitt zu entwerfen. Mir war kalt und ich brauchte ein paar Pullover, also was macht man da? + +Sven blieb bisher unter dem Radar, weil ich es auf der (damals unveröffentlichten) Freewing-Plattform entworfen habe, und bis jetzt hatte ich keinen geeigneten Ort, um es den Leuten zu zeigen. + +So sind wir hierher gekommen. Nun zu dem Pullover: Es ist ein einfaches Design, das auf dem Grundschnitt Brian basiert. Ich habe selbst drei verschiedene Versionen gemacht, bei denen ich den Ausschnitt und die Stoffaiswahl variiert habe, und er tut was er soll (hält mich warm). + +## Bilder oder es ist nicht passiert + +Schauen Sie sich die [Sven Gallerie](/showcase/pattern/sven) für einige Beispiele an. + + diff --git a/markdown/org/blog/announcing-sven/en.md b/markdown/org/blog/announcing-sven/en.md new file mode 100644 index 00000000000..f5e7f6a9658 --- /dev/null +++ b/markdown/org/blog/announcing-sven/en.md @@ -0,0 +1,19 @@ +--- +author: "joostdecock" +caption: "A Sven made for the office. As in, kinda boring" +date: "2017-07-09" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b0c9b0cb38bce095739109946a99b6cda63e7cd9-1000x667.jpg" +intro: "Winter caused me to design this pattern. I was cold, and needed some sweaters, so what does one do?" +title: "Announcing the Sven Sweater; A basic sweater based on the Brian body block" +--- + +Winter caused me to design this pattern. I was cold, and needed some sweaters, so what does one do? + +Sven stayed under the radar until now because I designed it on the (then unreleased) freesewing platform, and until now I didn't have a place to show it to people. + +That's how we got here. Now about that sweater: It's a simple design based on the Brian body block. I've made three different version myself, changing the neckline and fabrics, and it really does what it needs to do very well (as in, keep me warm). + +## Pictures or it didn't happen + +Check out the [Sven showcases](/showcase/pattern/sven) for some samples. + diff --git a/markdown/org/blog/announcing-sven/es.md b/markdown/org/blog/announcing-sven/es.md new file mode 100644 index 00000000000..99894fc268d --- /dev/null +++ b/markdown/org/blog/announcing-sven/es.md @@ -0,0 +1,19 @@ +--- +author: "joostdecock" +caption: "A Sven made for the office. As in, kinda boring" +date: "2017-07-09" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b0c9b0cb38bce095739109946a99b6cda63e7cd9-1000x667.jpg" +intro: "Winter caused me to design this pattern. I was cold, and needed some sweaters, so what does one do?" +title: "Announcing the Sven Sweater; A basic sweater based on the Brian body block [No traducido]" +--- + +Winter caused me to design this pattern. I was cold, and needed some sweaters, so what does one do? + +Sven stayed under the radar until now because I designed it on the (then unreleased) freesewing platform, and until now I didn't have a place to show it to people. + +That's how we got here. Now about that sweater: It's a simple design based on the Brian body block. I've made three different version myself, changing the neckline and fabrics, and it really does what it needs to do very well (as in, keep me warm). + +## Pictures or it didn't happen + +Check out the [Sven showcases](/showcase/pattern/sven) for some samples. + diff --git a/markdown/org/blog/announcing-sven/fr.md b/markdown/org/blog/announcing-sven/fr.md new file mode 100644 index 00000000000..ac977b91b98 --- /dev/null +++ b/markdown/org/blog/announcing-sven/fr.md @@ -0,0 +1,19 @@ +--- +author: "joostdecock" +caption: "A Sven made for the office. As in, kinda boring" +date: "2017-07-09" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b0c9b0cb38bce095739109946a99b6cda63e7cd9-1000x667.jpg" +intro: "Winter caused me to design this pattern. I was cold, and needed some sweaters, so what does one do?" +title: "Announcing the Sven Sweater; A basic sweater based on the Brian body block [Non traduit]" +--- + +Winter caused me to design this pattern. I was cold, and needed some sweaters, so what does one do? + +Sven stayed under the radar until now because I designed it on the (then unreleased) freesewing platform, and until now I didn't have a place to show it to people. + +That's how we got here. Now about that sweater: It's a simple design based on the Brian body block. I've made three different version myself, changing the neckline and fabrics, and it really does what it needs to do very well (as in, keep me warm). + +## Pictures or it didn't happen + +Check out the [Sven showcases](/showcase/pattern/sven) for some samples. + diff --git a/markdown/org/blog/announcing-sven/nl.md b/markdown/org/blog/announcing-sven/nl.md new file mode 100644 index 00000000000..7aa60ec58d1 --- /dev/null +++ b/markdown/org/blog/announcing-sven/nl.md @@ -0,0 +1,21 @@ +--- +author: "joostdecock" +caption: "Een Sven voor op kantoor. Dus euh, best wel saai." +date: "2017-07-09" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b0c9b0cb38bce095739109946a99b6cda63e7cd9-1000x667.jpg" +intro: "Ik heb dit patroon gemaakt omdat het winter was. Ik had het koud en ik had truien nodig. Dus wat doet een mens dan?" +title: "Nieuwkomer: de Sven-sweater, een basistrui gebaseerd op het Brian-corsage" +--- + + +Ik heb dit patroon gemaakt omdat het winter was. Ik had het koud en ik had truien nodig. Dus wat doet een mens dan? + +Sven is tot nu toe onder de radar gebleven omdat ik hem ontworpen had op het (toen nog niet gelanceerde) FreeSewing-platform, en tot nu toe had ik geen plek om het patroon aan mensen te laten zien. + +Zo zijn we dus tot hier geraakt. En nu over die trui: het is een eenvoudig ontwerp gebaseerd op de basisvorm Brian. Ik heb drie verschillende versies voor mezelf gemaakt met verschillende halsopeningen en stoffen, en het patroon doet echt heel goed wat het moet doen (mij warm houden). + +## Foto's of het is niet echt gebeurd + +Bekijk de [Sven-showcases](/showcase/pattern/sven) om een paar voorbeelden te zien. + + diff --git a/markdown/org/blog/announcing-teagan/de.md b/markdown/org/blog/announcing-teagan/de.md new file mode 100644 index 00000000000..02d8426e26e --- /dev/null +++ b/markdown/org/blog/announcing-teagan/de.md @@ -0,0 +1,47 @@ +--- +author: "joostdecock" +caption: "Photo by Alex Andrews from Pexels" +date: "2020-09-09" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8bee0b9035162c14da54744b24539e56a8e16e27-2000x1500.jpg" +intro: "A while ago somebody asked whether we had a T-shirt pattern on freesewing.org and it turns out, we didn't." +title: "FreeSewing 2.9 brings our Teagan T-shirt pattern [Nicht übersetzt]" +--- + +A while ago somebody asked whether we had a T-shirt pattern on freesewing.org and it turns out, we didn't. + +There's no good reason for that, we just never got around to that. +So today we're rolling out version 2.9 of FreeSewing with our latest pattern: [the Teagan T-shirt](/designs/teagan/). + +![A man, seated on a purple couch and wearing a speckled grey Teagan T-Shirt.](https://posts.freesewing.org/uploads/teagan1_2904162431.jpg) + +## Who is this for? + +Teagan is fitted T-shirt pattern with options for altering the neckline, length, and sleeves. + +Teagan is based on [our Brian block](/designs/brian/), which does not take breasts into account. +That being said, this will work for people with breasts too. +Since it uses the chest circumference it will simply draft a T-shirt to fit your full chest. + +We've also added an option to draft this to your high bust, which would give you a more fitted T-shirt +with ease & stretch having to accomodate for your breasts. + +![A woman wearing a striped T-shirt stands in front of a weathered fence. This T-shirt is more fitted through the chest.](https://posts.freesewing.org/uploads/teagan3_8ff8115d75.jpg) + +## Community Updates + +If you're thinking about sewing Teagan, but you're new to sewing or working with knits, never fear! +FreeSewing has more support than ever. Chat with us on [Discord](https://discord.freesewing.org/), in a [Facebook Group](https://www.facebook.com/groups/627769821272714), or on [Reddit](https://www.reddit.com/r/freesewing/). +Find us on social as @freesewing_org on [Instagram](https://www.instagram.com/freesewing_org/) and [Twitter](https://twitter.com/freesewing_org). If you're looking for tutorials, there's +a new [YouTube channel](https://www.youtube.com/channel/UCLAyxEL72gHvuKBpa-GmCvQ) for that. It has a whole +series on [sewing up Teagan](https://www.youtube.com/playlist?list=PLY9EmRuXR20Y7FonIHD6mX9yIpFh_emX1), as well as this amazing preview. + + + +If all of this sounds awesome, and you want to get more involved with FreeSewing, you can check out +our repositories and source code on [Github](https://github.com/freesewing/) or connect with other +contributors via [Discord](https://discord.freesewing.org/). You can find announcements about upcoming contributor calls +on Discord, in the announcements channel. + +And if you sew up a Teagan T-shirt, let us know what you think! + + diff --git a/markdown/org/blog/announcing-teagan/en.md b/markdown/org/blog/announcing-teagan/en.md new file mode 100644 index 00000000000..a68eaf1fe5b --- /dev/null +++ b/markdown/org/blog/announcing-teagan/en.md @@ -0,0 +1,46 @@ +--- +author: "joostdecock" +caption: "Photo by Alex Andrews from Pexels" +date: "2020-09-09" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8bee0b9035162c14da54744b24539e56a8e16e27-2000x1500.jpg" +intro: "A while ago somebody asked whether we had a T-shirt pattern on freesewing.org and it turns out, we didn't." +title: "FreeSewing 2.9 brings our Teagan T-shirt pattern" +--- + +A while ago somebody asked whether we had a T-shirt pattern on freesewing.org and it turns out, we didn't. + +There's no good reason for that, we just never got around to that. +So today we're rolling out version 2.9 of FreeSewing with our latest pattern: [the Teagan T-shirt](/designs/teagan/). + +![A man, seated on a purple couch and wearing a speckled grey Teagan T-Shirt.](https://posts.freesewing.org/uploads/teagan1_2904162431.jpg) + +## Who is this for? + +Teagan is fitted T-shirt pattern with options for altering the neckline, length, and sleeves. + +Teagan is based on [our Brian block](/designs/brian/), which does not take breasts into account. +That being said, this will work for people with breasts too. +Since it uses the chest circumference it will simply draft a T-shirt to fit your full chest. + +We've also added an option to draft this to your high bust, which would give you a more fitted T-shirt +with ease & stretch having to accomodate for your breasts. + +![A woman wearing a striped T-shirt stands in front of a weathered fence. This T-shirt is more fitted through the chest.](https://posts.freesewing.org/uploads/teagan3_8ff8115d75.jpg) + +## Community Updates + +If you're thinking about sewing Teagan, but you're new to sewing or working with knits, never fear! +FreeSewing has more support than ever. Chat with us on [Discord](https://discord.freesewing.org/), in a [Facebook Group](https://www.facebook.com/groups/627769821272714), or on [Reddit](https://www.reddit.com/r/freesewing/). +Find us on social as @freesewing_org on [Instagram](https://www.instagram.com/freesewing_org/) and [Twitter](https://twitter.com/freesewing_org). If you're looking for tutorials, there's +a new [YouTube channel](https://www.youtube.com/channel/UCLAyxEL72gHvuKBpa-GmCvQ) for that. It has a whole +series on [sewing up Teagan](https://www.youtube.com/playlist?list=PLY9EmRuXR20Y7FonIHD6mX9yIpFh_emX1), as well as this amazing preview. + + + +If all of this sounds awesome, and you want to get more involved with FreeSewing, you can check out +our repositories and source code on [Github](https://github.com/freesewing/) or connect with other +contributors via [Discord](https://discord.freesewing.org/). You can find announcements about upcoming contributor calls +on Discord, in the announcements channel. + +And if you sew up a Teagan T-shirt, let us know what you think! + diff --git a/markdown/org/blog/announcing-teagan/es.md b/markdown/org/blog/announcing-teagan/es.md new file mode 100644 index 00000000000..d99df3ff1f4 --- /dev/null +++ b/markdown/org/blog/announcing-teagan/es.md @@ -0,0 +1,47 @@ +--- +author: "joostdecock" +caption: "Photo by Alex Andrews from Pexels" +date: "2020-09-09" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8bee0b9035162c14da54744b24539e56a8e16e27-2000x1500.jpg" +intro: "A while ago somebody asked whether we had a T-shirt pattern on freesewing.org and it turns out, we didn't." +title: "FreeSewing 2.9 brings our Teagan T-shirt pattern [No traducido]" +--- + +A while ago somebody asked whether we had a T-shirt pattern on freesewing.org and it turns out, we didn't. + +There's no good reason for that, we just never got around to that. +So today we're rolling out version 2.9 of FreeSewing with our latest pattern: [the Teagan T-shirt](/designs/teagan/). + +![A man, seated on a purple couch and wearing a speckled grey Teagan T-Shirt.](https://posts.freesewing.org/uploads/teagan1_2904162431.jpg) + +## Who is this for? + +Teagan is fitted T-shirt pattern with options for altering the neckline, length, and sleeves. + +Teagan is based on [our Brian block](/designs/brian/), which does not take breasts into account. +That being said, this will work for people with breasts too. +Since it uses the chest circumference it will simply draft a T-shirt to fit your full chest. + +We've also added an option to draft this to your high bust, which would give you a more fitted T-shirt +with ease & stretch having to accomodate for your breasts. + +![A woman wearing a striped T-shirt stands in front of a weathered fence. This T-shirt is more fitted through the chest.](https://posts.freesewing.org/uploads/teagan3_8ff8115d75.jpg) + +## Community Updates + +If you're thinking about sewing Teagan, but you're new to sewing or working with knits, never fear! +FreeSewing has more support than ever. Chat with us on [Discord](https://discord.freesewing.org/), in a [Facebook Group](https://www.facebook.com/groups/627769821272714), or on [Reddit](https://www.reddit.com/r/freesewing/). +Find us on social as @freesewing_org on [Instagram](https://www.instagram.com/freesewing_org/) and [Twitter](https://twitter.com/freesewing_org). If you're looking for tutorials, there's +a new [YouTube channel](https://www.youtube.com/channel/UCLAyxEL72gHvuKBpa-GmCvQ) for that. It has a whole +series on [sewing up Teagan](https://www.youtube.com/playlist?list=PLY9EmRuXR20Y7FonIHD6mX9yIpFh_emX1), as well as this amazing preview. + + + +If all of this sounds awesome, and you want to get more involved with FreeSewing, you can check out +our repositories and source code on [Github](https://github.com/freesewing/) or connect with other +contributors via [Discord](https://discord.freesewing.org/). You can find announcements about upcoming contributor calls +on Discord, in the announcements channel. + +And if you sew up a Teagan T-shirt, let us know what you think! + + diff --git a/markdown/org/blog/announcing-teagan/fr.md b/markdown/org/blog/announcing-teagan/fr.md new file mode 100644 index 00000000000..1a5e85625e5 --- /dev/null +++ b/markdown/org/blog/announcing-teagan/fr.md @@ -0,0 +1,47 @@ +--- +author: "joostdecock" +caption: "Photo d'Alex Andrews de Pexels" +date: "2020-09-09" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8bee0b9035162c14da54744b24539e56a8e16e27-2000x1500.jpg" +intro: "A while ago somebody asked whether we had a T-shirt pattern on freesewing.org and it turns out, we didn't." +title: "FreeSewing 2.9 apporte notre T-shirt Teagan" +--- + +A while ago somebody asked whether we had a T-shirt pattern on freesewing.org and it turns out, we didn't. + +There's no good reason for that, we just never got around to that. +So today we're rolling out version 2.9 of FreeSewing with our latest pattern: [the Teagan T-shirt](/designs/teagan/). + +![A man, seated on a purple couch and wearing a speckled grey Teagan T-Shirt.](https://posts.freesewing.org/uploads/teagan1_2904162431.jpg) + +## Who is this for? + +Teagan is fitted T-shirt pattern with options for altering the neckline, length, and sleeves. + +Teagan is based on [our Brian block](/designs/brian/), which does not take breasts into account. +That being said, this will work for people with breasts too. +Since it uses the chest circumference it will simply draft a T-shirt to fit your full chest. + +We've also added an option to draft this to your high bust, which would give you a more fitted T-shirt +with ease & stretch having to accomodate for your breasts. + +![A woman wearing a striped T-shirt stands in front of a weathered fence. This T-shirt is more fitted through the chest.](https://posts.freesewing.org/uploads/teagan3_8ff8115d75.jpg) + +## Community Updates + +If you're thinking about sewing Teagan, but you're new to sewing or working with knits, never fear! +FreeSewing has more support than ever. Chat with us on [Discord](https://discord.freesewing.org/), in a [Facebook Group](https://www.facebook.com/groups/627769821272714), or on [Reddit](https://www.reddit.com/r/freesewing/). +Find us on social as @freesewing_org on [Instagram](https://www.instagram.com/freesewing_org/) and [Twitter](https://twitter.com/freesewing_org). If you're looking for tutorials, there's +a new [YouTube channel](https://www.youtube.com/channel/UCLAyxEL72gHvuKBpa-GmCvQ) for that. It has a whole +series on [sewing up Teagan](https://www.youtube.com/playlist?list=PLY9EmRuXR20Y7FonIHD6mX9yIpFh_emX1), as well as this amazing preview. + + + +If all of this sounds awesome, and you want to get more involved with FreeSewing, you can check out +our repositories and source code on [Github](https://github.com/freesewing/) or connect with other +contributors via [Discord](https://discord.freesewing.org/). You can find announcements about upcoming contributor calls +on Discord, in the announcements channel. + +And if you sew up a Teagan T-shirt, let us know what you think! + + diff --git a/markdown/org/blog/announcing-teagan/nl.md b/markdown/org/blog/announcing-teagan/nl.md new file mode 100644 index 00000000000..d763ac3ef02 --- /dev/null +++ b/markdown/org/blog/announcing-teagan/nl.md @@ -0,0 +1,36 @@ +--- +author: "joostdecock" +caption: "Foto door Alex Andrews van Pexels" +date: "2020-09-09" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8bee0b9035162c14da54744b24539e56a8e16e27-2000x1500.jpg" +intro: "Een tijdje geleden vroeg iemand of we een t-shirtpatroon hadden op FreeSewing, en toen bleek dat niet zo te zijn." +title: "Samen met FreeSewing 2.9 arriveert ons Teagan t-shirt patroon" +--- + +Een tijdje geleden vroeg iemand of we een t-shirtpatroon hadden op FreeSewing, en toen bleek dat niet zo te zijn. + +Daar is geen goede reden voor, het is er gewoon nooit van gekomen. Dus vandaag lanceren we versie 2.9 van FreeSewing, met ons nieuwste patroon: [het Teagan t-shirt](/designs/teagan/). + +![A man, seated on a purple couch and wearing a speckled grey Teagan T-Shirt.](teagan1.jpg) + +## Voor wie is dit? + +Teagan is fitted T-shirt pattern with options for altering the neckline, length, and sleeves. + +Teagan is based on [our Brian block](/designs/brian/), which does not take breasts into account. That being said, this will work for people with breasts too. Since it uses the chest circumference it will simply draft a T-shirt to fit your full chest. + +We've also added an option to draft this to your high bust, which would give you a more fitted T-shirt with ease & stretch having to accomodate for your breasts. + +![A woman wearing a striped T-shirt stands in front of a weathered fence. This T-shirt is more fitted through the chest.](teagan3.jpg) + +## Community Updates + +If you're thinking about sewing Teagan, but you're new to sewing or working with knits, never fear! FreeSewing has more support than ever. Chat with us on [Discord](https://discord.freesewing.org/), in a [Facebook Group](https://www.facebook.com/groups/627769821272714), or on [Reddit](https://www.reddit.com/r/freesewing/). Find us on social as @freesewing_org on [Instagram](https://www.instagram.com/freesewing_org/) and [Twitter](https://twitter.com/freesewing_org). If you're looking for tutorials, there's a new [YouTube channel](https://www.youtube.com/channel/UCLAyxEL72gHvuKBpa-GmCvQ) for that. It has a whole series on [sewing up Teagan](https://www.youtube.com/playlist?list=PLY9EmRuXR20Y7FonIHD6mX9yIpFh_emX1), as well as this amazing preview. + + + +If all of this sounds awesome, and you want to get more involved with FreeSewing, you can check out our repositories and source code on [Github](https://github.com/freesewing/) or connect with other contributors via [Discord](https://discord.freesewing.org/). You can find announcements about upcoming contributor calls on Discord, in the announcements channel. + +And if you sew up a Teagan T-shirt, let us know what you think! + + diff --git a/markdown/org/blog/announcing-ursula/de.md b/markdown/org/blog/announcing-ursula/de.md new file mode 100644 index 00000000000..45e067af88a --- /dev/null +++ b/markdown/org/blog/announcing-ursula/de.md @@ -0,0 +1,23 @@ +--- +author: "joostdecock" +caption: "Photo by Karolina Grabowska from Pexels" +date: "2021-06-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/13f022fe08c08ba927a13db25c554d730ec8f912-1280x853.jpg" +intro: "Announcing Ursula, a basic, highly-customizable underwear pattern [Nicht übersetzt]" +title: "Announcing Ursula, a basic, highly-customizable underwear pattern [Nicht übersetzt]" +--- + + +FreeSewing 2.17 is out, and it while it comes with many fixes and improvements, +the biggest news is certainly a brand new pattern: [The Ursula Undies](/designs/ursula/) +by US-based designer Natalia Sayang. + +![Example of a default Ursula](https://posts.freesewing.org/uploads/example_aab890ee57.jpg) + +The picture above is from [this showcase post](/showcase/ursula-test-pairs/) +which includes several more examples of the different styles you can accomplish with +this versatile pattern. + +Ursula is a quick make, not to mention the ultimate stash-buster. +We are really excited about it. + diff --git a/markdown/org/blog/announcing-ursula/en.md b/markdown/org/blog/announcing-ursula/en.md new file mode 100644 index 00000000000..24aa45faddc --- /dev/null +++ b/markdown/org/blog/announcing-ursula/en.md @@ -0,0 +1,23 @@ +--- +author: "joostdecock" +caption: "Photo by Karolina Grabowska from Pexels" +date: "2021-06-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/13f022fe08c08ba927a13db25c554d730ec8f912-1280x853.jpg" +intro: "Announcing Ursula, a basic, highly-customizable underwear pattern" +title: "Announcing Ursula, a basic, highly-customizable underwear pattern" +--- + + +FreeSewing 2.17 is out, and it while it comes with many fixes and improvements, +the biggest news is certainly a brand new pattern: [The Ursula Undies](/designs/ursula/) +by US-based designer Natalia Sayang. + +![Example of a default Ursula](https://posts.freesewing.org/uploads/example_aab890ee57.jpg) + +The picture above is from [this showcase post](/showcase/ursula-test-pairs/) +which includes several more examples of the different styles you can accomplish with +this versatile pattern. + +Ursula is a quick make, not to mention the ultimate stash-buster. +We are really excited about it. + diff --git a/markdown/org/blog/announcing-ursula/es.md b/markdown/org/blog/announcing-ursula/es.md new file mode 100644 index 00000000000..80268e484d3 --- /dev/null +++ b/markdown/org/blog/announcing-ursula/es.md @@ -0,0 +1,23 @@ +--- +author: "joostdecock" +caption: "Photo by Karolina Grabowska from Pexels" +date: "2021-06-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/13f022fe08c08ba927a13db25c554d730ec8f912-1280x853.jpg" +intro: "Announcing Ursula, a basic, highly-customizable underwear pattern [No traducido]" +title: "Announcing Ursula, a basic, highly-customizable underwear pattern [No traducido]" +--- + + +FreeSewing 2.17 is out, and it while it comes with many fixes and improvements, +the biggest news is certainly a brand new pattern: [The Ursula Undies](/designs/ursula/) +by US-based designer Natalia Sayang. + +![Example of a default Ursula](https://posts.freesewing.org/uploads/example_aab890ee57.jpg) + +The picture above is from [this showcase post](/showcase/ursula-test-pairs/) +which includes several more examples of the different styles you can accomplish with +this versatile pattern. + +Ursula is a quick make, not to mention the ultimate stash-buster. +We are really excited about it. + diff --git a/markdown/org/blog/announcing-ursula/fr.md b/markdown/org/blog/announcing-ursula/fr.md new file mode 100644 index 00000000000..d9ccf2996ef --- /dev/null +++ b/markdown/org/blog/announcing-ursula/fr.md @@ -0,0 +1,23 @@ +--- +author: "joostdecock" +caption: "Photo by Karolina Grabowska from Pexels" +date: "2021-06-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/13f022fe08c08ba927a13db25c554d730ec8f912-1280x853.jpg" +intro: "Announcing Ursula, a basic, highly-customizable underwear pattern [Non traduit]" +title: "Announcing Ursula, a basic, highly-customizable underwear pattern [Non traduit]" +--- + + +FreeSewing 2.17 is out, and it while it comes with many fixes and improvements, +the biggest news is certainly a brand new pattern: [The Ursula Undies](/designs/ursula/) +by US-based designer Natalia Sayang. + +![Example of a default Ursula](https://posts.freesewing.org/uploads/example_aab890ee57.jpg) + +The picture above is from [this showcase post](/showcase/ursula-test-pairs/) +which includes several more examples of the different styles you can accomplish with +this versatile pattern. + +Ursula is a quick make, not to mention the ultimate stash-buster. +We are really excited about it. + diff --git a/markdown/org/blog/announcing-ursula/nl.md b/markdown/org/blog/announcing-ursula/nl.md new file mode 100644 index 00000000000..048df30e4f2 --- /dev/null +++ b/markdown/org/blog/announcing-ursula/nl.md @@ -0,0 +1,23 @@ +--- +author: "joostdecock" +caption: "Photo by Karolina Grabowska from Pexels" +date: "2021-06-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/13f022fe08c08ba927a13db25c554d730ec8f912-1280x853.jpg" +intro: "Announcing Ursula, a basic, highly-customizable underwear pattern [Niet vertaald]" +title: "Announcing Ursula, a basic, highly-customizable underwear pattern [Niet vertaald]" +--- + + +FreeSewing 2.17 is out, and it while it comes with many fixes and improvements, +the biggest news is certainly a brand new pattern: [The Ursula Undies](/designs/ursula/) +by US-based designer Natalia Sayang. + +![Example of a default Ursula](https://posts.freesewing.org/uploads/example_aab890ee57.jpg) + +The picture above is from [this showcase post](/showcase/ursula-test-pairs/) +which includes several more examples of the different styles you can accomplish with +this versatile pattern. + +Ursula is a quick make, not to mention the ultimate stash-buster. +We are really excited about it. + diff --git a/markdown/org/blog/announcing-v2/de.md b/markdown/org/blog/announcing-v2/de.md new file mode 100644 index 00000000000..79eefa534ba --- /dev/null +++ b/markdown/org/blog/announcing-v2/de.md @@ -0,0 +1,53 @@ +--- +author: "joostdecock" +caption: "Diese Version ist wirklich eine grundlegende Veränderung" +date: "2019-08-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5b31cfbe3a85cee5519e12afe767ca3249588463-2000x1126.jpg" +intro: "Ankündigung von der Version 2 von FreeSewing, der Opensourceplattform für Schnittmuster auf Mass." +title: "Ankündigung von FreeSewing v2.0" +--- + + +# Ankündigung von FreeSewing v2.0 + +Ankündigung von der Version 2 von FreeSewing, der Opensourceplattform für Schnittmuster auf Mass. + +Diese Veröffentlichung gipfelt in mehr als einem Jahr Arbeit und kommt auf den Tag genau zwei Jahre nach dem ersten Produktivstart von FreeSewing. Heute legen wir wieder einmal die Messlatte höher, was Sie von modernen Schnittmustern erwarten können. + +## 🦄 Höher, besser, schneller, stärker [\*](https://www.youtube.com/watch?v=GDpmVUEjagg) + + +Wir sind von dieser Veröffentlichung *extrem* begeistert, die nicht nur eine neue Hauptversion mit einigen grundlegenden Änderungen ist, sondern eine vollständiger Rewrite in JavaScript/Node.js. Wir werden hier nicht ins kleinste Detail gehen. Wenn Sie sich dafür interessieren, dann schauen Sie mal [in der Entwicklerdokumentation](https://freesewing.dev) oder auf [GitHub](https://github.com/freesewing)vorbei. + + +## ✨ Live-Vorschau + +FreeSewing hatte schon immer den Ruf, Schnittmuster mit jeder Menge Optionen und Variationen bereitzustellen. Das ist sehr cool, aber das Resultat war jeweils erst ganz am Ende ersichtlich, weshalb es manchmal die Vorstellungskraft übersteigen konnte. Aber diese Tage sind vorbei. Ab jetzt, egal welche Einstellungen Sie am Schnitt vornehmen, werden Sie immer eine Live-Vorschau des fertigen Schnittmusters haben. + +## 🧂 Rezepte + +Statt dass wir die fertig konfigurierten Schnittmuster für Sie speichern, speichern wir ab jetzt Ihre *Rezepte* zum erstellen der Schnittmuster. Sie können so viele Schnittmuster-Iteration wie Sie wollen erstellen. Und wenn Sie mit dem Ergebnis zufrieden sind, werden wir alle notwendigen Einstellungen speichern, die es benötigt, um dieses genaue Muster nach einem so genannten Rezept zu erstellen. + +Sie können das Rezept jederzeit wieder hervor nehmen um das Schnittmuster erneut zu erstellen oder es als Ausgangspunkt für eine andere Variante verwenden. Sie könne Rezepte auch teilen, erlauben Sie anderen genau den selben Look zu erstellen auf Grundlage ihrer eigenen Maße. + +## 🤝 Sich zu beteiligen war nie einfacher + +Was sich nicht geändert hat, ist, dass wir immer noch 5 Sprachen unterstützen (Danke an alle Übersetzer) und dass FreeSewing immer noch eine 100%ige Gemeinschaftsleistung ist (Danke an alle Mitwirkenden). Hier gibt es nur Freiwillige, und wenn du mithelfen möchtest, war es noch nie so einfach. + +Für diejenigen, die an unserem Code interessiert sind, besuchen Sie unsere neue Entwicklerdokumentation unter [freesewing.dev](https://freesewing.dev), um mehr über die neue Plattform, unsere Core-API, unsere Plugins und vieles mehr zu erfahren. + +Für diejenigen unter Ihnen, die an der Gestaltung von Schnittmustern interessiert sind, haben wir unser [Schnittmuster-Howto](https://freesewing.dev/tutorial) aktualisiert, damit Sie sofort loslegen können. + +Auch für Übersetzer gibt es gute Nachrichten, denn wir verwenden jetzt [Crowdin](https://crowdin.com/), was die Übersetzung zum Kinderspiel macht. Wenn du bei der Übersetzung helfen oder vielleicht sogar eine neue Sprache zu FreeSewing hinzufügen möchtest, [setze dich einfach mit uns in Verbindung](https://discord.freesewing.org/). + +## 💩 Es gelten die üblichen Einschränkungen + +In der Softwareentwicklung ist es üblich, dass die Umgestaltung von Code gut ist, aber das Neuschreiben von Grund auf ist schlecht. Dennoch haben wir es trotzdem getan, weil wir es den Menschen erleichtern wollten, sich am Projekt zu beteiligen und Muster in Echtzeit im Browser zu generieren. + +Abgesehen davon ist dies eine .Null-Version, sodass Sie über das ein oder andere Problem stolpern könnten. When you do, please [let us know](https://discord.freesewing.org/) or submit an issue. + +## 🤞 Verraten Sie uns Ihre Meinung + +Wir würden uns über Ihr Feedback freuen. Wir sind **@freesewing\_org** auf [Twitter](https://twitter.com/freesewing_org) und [Instagram](https://instagram.com/freesewing_org) vertreten, verwenden Sie das **#freesewing** Hashtag oder [schauen Sie sich unsere Share-Seite](/share) an. + + diff --git a/markdown/org/blog/announcing-v2/en.md b/markdown/org/blog/announcing-v2/en.md new file mode 100644 index 00000000000..cdb479299f2 --- /dev/null +++ b/markdown/org/blog/announcing-v2/en.md @@ -0,0 +1,58 @@ +--- +author: "joostdecock" +caption: "This release really is a sea-change" +date: "2019-08-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5b31cfbe3a85cee5519e12afe767ca3249588463-2000x1126.jpg" +intro: "Welcome to version 2 of FreeSewing, the open source platform for made-to-measure sewing patterns." +title: "Announcing FreeSewing v2.0" +--- + + +# Announcing FreeSewing v2.0 + +Welcome to version 2 of FreeSewing, the open source platform for made-to-measure sewing patterns. + +This release culminates more than a year of work, and comes two years to the day since FreeSewing first went live. +Today, we once again raise the bar for what you can expect from modern-day sewing patterns. + +## 🦄 Harder, better, faster, stronger [\*](https://www.youtube.com/watch?v=GDpmVUEjagg) + + +We are *extremely* excited about this release, which is not just merely a new major version with some breaking changes, +but a complete rewrite in JavaScript/Node.js. We won't go into the nitty gritty here, but if you'd like to know how +we've done it, check out [the developer docs](https://freesewing.dev) or [FreeSewing on GitHub](https://github.com/freesewing). + + +## ✨ Live preview + +FreeSewing has always had a reputation for publishing sewing patterns with tons of options for you to tweak. Which is great, but can be a bit overwhelming because you only got to see the result of all those tweaks at the very end. +But those days are gone. Now, no matter what changes you make, you get a live preview of what your pattern will look like, taking the guesswork out of configuring your pattern exactly as you like it. + +## 🧂 Recipes + +Where we used to store your patterns for you, now we'll store your *recipes* instead. You can go through as many pattern iterations as you want. And when you're happy, we'll save all the settings it takes to create that exact pattern in a so-called recipe. + +You can then at any time re-use that recipe to recreate your pattern, or use it as a starting point to make a slightly different pattern. You can also share these recipes, allowing others to generate the same look for their own measurements. + +## 🤝 Getting involved was never easier + +What hasn't changed is that we still support 5 languages (shout-out to all translators) and that FreeSewing is still a 100% communal effort (shout-out to all contributors). There's only volunteers here, and if you'd like to help out, it's never been easier. + +For those who are interested in our code, head over to our new developer documentation at [freesewing.dev](https://freesewing.dev) to learn about the new platform, our core API, our plugins, and more. + +For those of you who are interested in designing patterns, we have updated our [pattern design tutorial](https://freesewing.dev/tutorial) so you can hit the ground running. + +There's good news for translators too, as we now use [Crowdin](https://crowdin.com/) which makes translation a breeze. If you'd like to help out with translation, or maybe even add a new language to FreeSewing, make sure to [get in touch](https://discord.freesewing.org/). + +## 💩 Usual caveats apply + +It's conventional wisdom in software development that refactoring code is good, but rewriting it from scratch is bad. Still, we did it anyway because we wanted to make it easier for people to get involved in the project, and generate patterns in real-time in the browser. + +That being said, this is a .zero release so you may stumble upon an issue left or right. When you do, please [let us know](https://discord.freesewing.org/) or submit an issue. + +## 🤞 Tell us what you think + +We'd love to hear your feedback. We're **@freesewing\_org** on [Twitter](https://twitter.com/freesewing_org) +and [Instagram](https://instagram.com/freesewing_org), +use the **#freesewing** hashtag, or [check our share page](/share). + diff --git a/markdown/org/blog/announcing-v2/es.md b/markdown/org/blog/announcing-v2/es.md new file mode 100644 index 00000000000..3c8e13a0dcf --- /dev/null +++ b/markdown/org/blog/announcing-v2/es.md @@ -0,0 +1,58 @@ +--- +author: "joostdecock" +caption: "This release really is a sea-change" +date: "2019-08-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5b31cfbe3a85cee5519e12afe767ca3249588463-2000x1126.jpg" +intro: "Welcome to version 2 of FreeSewing, the open source platform for made-to-measure sewing patterns." +title: "Announcing FreeSewing v2.0 [No traducido]" +--- + + +# Announcing FreeSewing v2.0 + +Welcome to version 2 of FreeSewing, the open source platform for made-to-measure sewing patterns. + +This release culminates more than a year of work, and comes two years to the day since FreeSewing first went live. +Today, we once again raise the bar for what you can expect from modern-day sewing patterns. + +## 🦄 Harder, better, faster, stronger [\*](https://www.youtube.com/watch?v=GDpmVUEjagg) + + +We are *extremely* excited about this release, which is not just merely a new major version with some breaking changes, +but a complete rewrite in JavaScript/Node.js. We won't go into the nitty gritty here, but if you'd like to know how +we've done it, check out [the developer docs](https://freesewing.dev) or [FreeSewing on GitHub](https://github.com/freesewing). + + +## ✨ Live preview + +FreeSewing has always had a reputation for publishing sewing patterns with tons of options for you to tweak. Which is great, but can be a bit overwhelming because you only got to see the result of all those tweaks at the very end. +But those days are gone. Now, no matter what changes you make, you get a live preview of what your pattern will look like, taking the guesswork out of configuring your pattern exactly as you like it. + +## 🧂 Recipes + +Where we used to store your patterns for you, now we'll store your *recipes* instead. You can go through as many pattern iterations as you want. And when you're happy, we'll save all the settings it takes to create that exact pattern in a so-called recipe. + +You can then at any time re-use that recipe to recreate your pattern, or use it as a starting point to make a slightly different pattern. You can also share these recipes, allowing others to generate the same look for their own measurements. + +## 🤝 Getting involved was never easier + +What hasn't changed is that we still support 5 languages (shout-out to all translators) and that FreeSewing is still a 100% communal effort (shout-out to all contributors). There's only volunteers here, and if you'd like to help out, it's never been easier. + +For those who are interested in our code, head over to our new developer documentation at [freesewing.dev](https://freesewing.dev) to learn about the new platform, our core API, our plugins, and more. + +For those of you who are interested in designing patterns, we have updated our [pattern design tutorial](https://freesewing.dev/tutorial) so you can hit the ground running. + +There's good news for translators too, as we now use [Crowdin](https://crowdin.com/) which makes translation a breeze. If you'd like to help out with translation, or maybe even add a new language to FreeSewing, make sure to [get in touch](https://discord.freesewing.org/). + +## 💩 Usual caveats apply + +It's conventional wisdom in software development that refactoring code is good, but rewriting it from scratch is bad. Still, we did it anyway because we wanted to make it easier for people to get involved in the project, and generate patterns in real-time in the browser. + +That being said, this is a .zero release so you may stumble upon an issue left or right. When you do, please [let us know](https://discord.freesewing.org/) or submit an issue. + +## 🤞 Tell us what you think + +We'd love to hear your feedback. We're **@freesewing\_org** on [Twitter](https://twitter.com/freesewing_org) +and [Instagram](https://instagram.com/freesewing_org), +use the **#freesewing** hashtag, or [check our share page](/share). + diff --git a/markdown/org/blog/announcing-v2/fr.md b/markdown/org/blog/announcing-v2/fr.md new file mode 100644 index 00000000000..0c4ab67706b --- /dev/null +++ b/markdown/org/blog/announcing-v2/fr.md @@ -0,0 +1,53 @@ +--- +author: "joostdecock" +caption: "Cette version est vraiment un changement de vue" +date: "2019-08-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5b31cfbe3a85cee5519e12afe767ca3249588463-2000x1126.jpg" +intro: "Bienvenue sur la version 2 de FreeSewing, la plate-forme open source pour les patrons de couture sur mesure." +title: "Annonce de FreeSewing v2.0" +--- + + +# Annonce de FreeSewing v2.0 + +Bienvenue sur la version 2 de FreeSewing, la plate-forme open source pour les patrons de couture sur mesure. + +Cette version complète plus d'une année de travail, et vient deux ans après la première sortie de FreeSewing. Aujourd'hui, nous mettons une fois de plus le barre haute pour ce que vous pouvez attendre des patrons modernes de couture. + +## 🦄 Plus solide, meilleur, plus rapide, plus fort [\*](https://www.youtube.com/watch?v=GDpmVUEjagg) + + +Nous sommes *extrèmement* excités à propos de cette nouvelle version, qui n'est pas seulement une version améliorée avec quelques changements, mais une complète réécriture en JavaScript/Node.js. Nous n'entrerons pas dans les détails ici, mais si vous voulez savoir comment nous avons fait, vérifiez [les documents de développement](https://freesewing.dev) ou [FreeSewing sur GitHub](https://github.com/freesewing). + + +## ✨ Aperçu en direct + +FreeSewing a toujours eu la réputation de publier des patrons de couture avec des tonnes d'options pour fignoler. Ce qui est génial, mais peut être un peu accablant parce que vous voulez seulement voir le résultat de toutes ces améliorations à la fin. Mais cette époque est révolue. Maintenant, peu importe les changements que vous apportez, vous obtenez un aperçu en direct de ce à quoi ressemblera votre patron, en configurant votre patron exactement comme vous le souhaitez. + +## 🧂 Recettes + +Là où nous avions l'habitude de stocker vos patrons pour vous, maintenant nous allons stocker vos *recettes* à la place. Vous pouvez générer autant d'itérations de patrons que vous le souhaitez. Et lorsque vous êtes satisfait, nous enregistrerons tous les paramètres qui ont été nécessaires pour créer ce patron dans ce qui est appelé une recette. + +Vous pouvez alors à tout moment réutiliser cette recette pour recréer votre patron, ou l'utiliser comme point de départ pour créer un patron légèrement différent. Vous pouvez également partager ces recettes, permettant ainsi aux autres de générer le même aspect à leurs propres mensurations. + +## 🤝 Participer n'a jamais été aussi facile + +Ce qui n'a pas changé, c'est que nous supportons toujours 5 langues (appel à tous les traducteurs) et que FreeSewing reste un effort communautaire à 100% (appel à tous les contributeurs). Il n'y a que des volontaires ici, et si vous voulez aider, ça n'a jamais été aussi facile. + +Pour ceux qui sont intéressés par notre code, rendez-vous sur notre nouvelle documentation développeur sur [freesewing.dev](https://freesewing.dev) pour en savoir plus sur la nouvelle plate-forme, notre API, nos plugins, et plus encore. + +Pour ceux qui sont intéressés dans le design de patrons, nous avons mis à jour notre [tutoriel de design de patron](https://freesewing.dev/tutorial) pour vous mettre le pied à l'étrier. + +Il y a aussi de bonnes nouvelles pour les traducteurs, car nous utilisons maintenant [Crowdin](https://crowdin.com/) qui permet de gérer la traduction un clin d'œil. If you'd like to help out with translation, or maybe even add a new language to FreeSewing, make sure to [get in touch](https://discord.freesewing.org/). + +## 💩 Appliquer les avertissements courants + +La sagesse répandue dans le développement de logiciels est que revoir du code c'est bien, mais la réécriture complète à partir de zéro c'est mal. Néanmoins, nous l'avons fait quand même parce que nous voulions faciliter l'implication des gens dans le projet. et générer des patrons en temps réel dans le navigateur. + +Ceci étant dit, il s'agit d'une version .zéro ; ainsi vous pouvez trébucher sur une problème ou autre. When you do, please [let us know](https://discord.freesewing.org/) or submit an issue. + +## 🤞 Faites-nous part de vos commentaires + +Votre avis nous intéresse. Nous sommes **@freesewing\_org** sur [Twitter](https://twitter.com/freesewing_org) et [Instagram](https://instagram.com/freesewing_org), utilisez le **#freesewing** hashtag, ou [consultez notre page de partage](/share). + + diff --git a/markdown/org/blog/announcing-v2/nl.md b/markdown/org/blog/announcing-v2/nl.md new file mode 100644 index 00000000000..e3d6b1ec3a9 --- /dev/null +++ b/markdown/org/blog/announcing-v2/nl.md @@ -0,0 +1,53 @@ +--- +author: "joostdecock" +caption: "Deze lancering is echt een aardverschuiving." +date: "2019-08-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5b31cfbe3a85cee5519e12afe767ca3249588463-2000x1126.jpg" +intro: "Welkom aan versie 2 van FreeSewing, het open source-platform voor naaipatronen op maat." +title: "We presenteren FreeSewing v2.0" +--- + + +# We presenteren FreeSewing v2.0 + +Welkom aan versie 2 van FreeSewing, het open source-platform voor naaipatronen op maat. + +Deze release is de kroon op meer dan een jaar werk, en komt er precies twee jaar nadat FreeSewing voor het eerst live ging. Vandaag leggen we de lat opnieuw hoger voor wat je van moderne naaipatronen mag verwachten. + +## 🦄 Harder, better, faster, stronger [\*](https://www.youtube.com/watch?v=GDpmVUEjagg) + + +We zijn *enorm* enthousiast over deze release, die niet gewoon een een baanbrekende nieuwe versie is met een aantal grote aanpassingen, maar een complete herwerking in JavaScript/Node.js. We gaan hier niet tot in de fijne puntjes, maar als je graag zou weten hoe we dit gedaan hebben, kan je de [developerdocumenten](https://freesewing.dev) erop nalezen of je verdiepen in [FreeSewing op GitHub](https://github.com/freesewing). + + +## ✨ Live preview + +FreeSewing heeft altijd al een reputatie gehad voor naaipatronen met een massa opties waarmee je kunt sleutelen. Dat was fijn, maar nogal overdonderend, want je zag het resultaat van al die aanpassingen pas helemaal op het einde. Die tijd is voorbij. Voortaan kun je, welke aanpassingen je ook doet, live zien hoe je patroon eruit gaat zien. Dus is er helemaal geen giswerk meer nodig om je patroon precies uit te werken zoals jij het wilt. + +## 🧂 Recepten + +Vroeger sloegen we patronen voor je op. Voortaan doen we dat met *recepten*. Je kunt het patroon zo vaak bewerken als je wilt. En wanneer jij tevreden bent, slaan we alle instellingen voor dat precieze patroon op in een zogenaamd recept. + +Je kunt dat recept op eender welk moment hergebruiken om je patroon opnieuw te genereren, of gebruiken als vertrekpunt voor een patroon dat net een beetje anders is. Je kunt ook recepten delen. Anderen kunnen dan dezelfde versie genereren met hun eigen maten. + +## 🤝 Het is gemakkelijker dan ooit om mee te werken + +Wat niet veranderd is? We ondersteunen nog steeds 5 talen (shout-out aan alle vertalers) en FreeSewing is nog steeds 100% een gezamenlijke inspanning (shout-out aan alle bijdragers). We zijn hier allemaal vrijwilligers, en als je graag wil helpen, is dat gemakkelijker dan ooit. + +Wie geïnteresseerd is in onze code, kan in onze developerdocumentatie duiken op [freesewing.dev](https://freesewing.dev) en er alles leren over het nieuwe platform, onze kern-API, onze plugins en meer. + +Wie graag patronen zou ontwerpen, kan meteen aan het werk aan de hand van onze [ontwerptutorial](https://freesewing.dev/tutorial). + +En er is ook goed nieuws voor vertalers, want we gebruiken voortaan [Crowdin](https://crowdin.com/) zodat je kan vertalen met twee vingers in je neus. If you'd like to help out with translation, or maybe even add a new language to FreeSewing, make sure to [get in touch](https://discord.freesewing.org/). + +## 💩 De gebruikelijke addertjes onder het gras + +In softwaredevelopment is het algemeen geweten dat het een goed idee is om code te refactoren, maar niet om hem van nul te herschrijven. En toch hebben we dat gedaan. We wilden het gemakkelijker maken voor mensen om bij het project betrokken te raken en om patronen in realtime te genereren in de browser. + +Maar wees je er dus van bewust dat dit een .zero-release is. Het kan dus goed zijn dat je hier en daar een probleem opmerkt. When you do, please [let us know](https://discord.freesewing.org/) or submit an issue. + +## 🤞 Laat ons weten wat je ervan denkt + +We zijn benieuwd naar jouw feedback. Je vindt ons als **@freesewing_org** op [Twitter](https://twitter.com/freesewing_org) en [Instagram](https://instagram.com/freesewing_org). Gebruik de hashtag **#freesewing** of check onze [share-pagina](/share). + + diff --git a/markdown/org/blog/bella-bodice-block/de.md b/markdown/org/blog/bella-bodice-block/de.md new file mode 100644 index 00000000000..503b40f61d8 --- /dev/null +++ b/markdown/org/blog/bella-bodice-block/de.md @@ -0,0 +1,39 @@ +--- +author: "joostdecock" +caption: "Remember when we were allowed to go outside?" +date: "2021-01-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0faad5ded9176b4cf9e58cf5b05a939ba7670363-1920x1272.jpg" +intro: "The Bella bodice block for womenswear [Nicht übersetzt]" +title: "The Bella bodice block for womenswear [Nicht übersetzt]" +--- + + +We've just published a new pattern on this website: [Bella, a bodice block for womenswear](/designs/bella/). +It's a block with bust and waist dart, and a waist dart at the back. + +My goal when venturing into womenswear was to make one foundational block from which +we could then spin out a range of different garments. + +Which is why we have [Breanna](/designs/breanna/), which I designed from scratch. +Unfortunately, it hasn't been the end-all be-all that I — perhaps naively — hoped it would be. + +For Bella, I worked with someone from the industry to implement a design that is commonly +used for commercial garment making. As such, I am curious to see how this one will pan out. + +My initial plan was to also make a variation with a shoulder dart at the front, to replace the bust dart, +but in the end I settled for getting it released, rather than work on it longer. + +Which brings me to: + +##### I'm taking a break from womenswear + +I feel like I'm expending a lot of effort here for little result. +It's getting me down, and I need a win. + +I want to work on something that I can not only design, but also make and wear. +Something that gives me joy, and makes me feel like I know what I'm doing. + +So while I'll still help out people who want to design for women themselves, +I am taking a break from womenswear. + + diff --git a/markdown/org/blog/bella-bodice-block/en.md b/markdown/org/blog/bella-bodice-block/en.md new file mode 100644 index 00000000000..c6bafffc94f --- /dev/null +++ b/markdown/org/blog/bella-bodice-block/en.md @@ -0,0 +1,39 @@ +--- +author: "joostdecock" +caption: "Remember when we were allowed to go outside?" +date: "2021-01-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0faad5ded9176b4cf9e58cf5b05a939ba7670363-1920x1272.jpg" +intro: "The Bella bodice block for womenswear" +title: "The Bella bodice block for womenswear" +--- + + +We've just published a new pattern on this website: [Bella, a bodice block for womenswear](/designs/bella/). +It's a block with bust and waist dart, and a waist dart at the back. + +My goal when venturing into womenswear was to make one foundational block from which +we could then spin out a range of different garments. + +Which is why we have [Breanna](/designs/breanna/), which I designed from scratch. +Unfortunately, it hasn't been the end-all be-all that I — perhaps naively — hoped it would be. + +For Bella, I worked with someone from the industry to implement a design that is commonly +used for commercial garment making. As such, I am curious to see how this one will pan out. + +My initial plan was to also make a variation with a shoulder dart at the front, to replace the bust dart, +but in the end I settled for getting it released, rather than work on it longer. + +Which brings me to: + +##### I'm taking a break from womenswear + +I feel like I'm expending a lot of effort here for little result. +It's getting me down, and I need a win. + +I want to work on something that I can not only design, but also make and wear. +Something that gives me joy, and makes me feel like I know what I'm doing. + +So while I'll still help out people who want to design for women themselves, +I am taking a break from womenswear. + + diff --git a/markdown/org/blog/bella-bodice-block/es.md b/markdown/org/blog/bella-bodice-block/es.md new file mode 100644 index 00000000000..a1fb3a5469a --- /dev/null +++ b/markdown/org/blog/bella-bodice-block/es.md @@ -0,0 +1,39 @@ +--- +author: "joostdecock" +caption: "Remember when we were allowed to go outside?" +date: "2021-01-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0faad5ded9176b4cf9e58cf5b05a939ba7670363-1920x1272.jpg" +intro: "The Bella bodice block for womenswear [No traducido]" +title: "The Bella bodice block for womenswear [No traducido]" +--- + + +We've just published a new pattern on this website: [Bella, a bodice block for womenswear](/designs/bella/). +It's a block with bust and waist dart, and a waist dart at the back. + +My goal when venturing into womenswear was to make one foundational block from which +we could then spin out a range of different garments. + +Which is why we have [Breanna](/designs/breanna/), which I designed from scratch. +Unfortunately, it hasn't been the end-all be-all that I — perhaps naively — hoped it would be. + +For Bella, I worked with someone from the industry to implement a design that is commonly +used for commercial garment making. As such, I am curious to see how this one will pan out. + +My initial plan was to also make a variation with a shoulder dart at the front, to replace the bust dart, +but in the end I settled for getting it released, rather than work on it longer. + +Which brings me to: + +##### I'm taking a break from womenswear + +I feel like I'm expending a lot of effort here for little result. +It's getting me down, and I need a win. + +I want to work on something that I can not only design, but also make and wear. +Something that gives me joy, and makes me feel like I know what I'm doing. + +So while I'll still help out people who want to design for women themselves, +I am taking a break from womenswear. + + diff --git a/markdown/org/blog/bella-bodice-block/fr.md b/markdown/org/blog/bella-bodice-block/fr.md new file mode 100644 index 00000000000..258fe57de4e --- /dev/null +++ b/markdown/org/blog/bella-bodice-block/fr.md @@ -0,0 +1,32 @@ +--- +author: "joostdecock" +caption: "Vous vous souvenez de quand nous avions le droit de sortir ?" +date: "2021-01-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0faad5ded9176b4cf9e58cf5b05a939ba7670363-1920x1272.jpg" +intro: "Nous venons de publier un nouveau modèle sur ce site : Bella, un bloc de buste pour vêtements féminins . C'est un bloc avec une pince de poitrine et de taille, ainsi qu'une pince de taille dans le dos." +title: "Le bloc de buste Bella pour vêtements féminins" +--- + + +Nous venons de publier un nouveau modèle sur ce site : [Bella, un bloc de buste pour vêtements féminins](/designs/bella/). C'est un bloc avec une pince de poitrine et de taille, ainsi qu'une pince de taille dans le dos. + +Mon but en m'aventurant dans des vêtements féminins était de faire un bloc de base à partir duquel nous pourrions ensuite décliner une gamme de vêtements différents. + +C'est pourquoi nous avons [Breanna](/designs/breanna/), que j'ai conçu à partir de zéro. Malheureusement, ce modèle n'a pas été la réussite que j'espérais, peut-être naïvement. + +Pour Bella, j'ai travaillé avec quelqu'un de l'industrie pour mettre en œuvre un design qui est communément utilisé pour la fabrication de vêtements du commerce. En tant que tel, je suis curieux de voir comment celui-ci va s'en sortir. + +Mon projet initial était également de faire une variation avec une pince d'épaule à l'avant, pour remplacer la pince poitrine, mais finalement je me suis décidé à le sortir tel quel, plutôt que de le travailler plus longtemps. + +Ce qui m'amène à : + +##### Je prends une pause concernant les vêtements féminins + +J'ai l'impression que je dépense beaucoup d'efforts ici pour peu de résultats. Ça me démoralise et j'ai besoin d'une victoire. + +Je veux travailler sur quelque chose que je peux non seulement concevoir, mais aussi réaliser et porter. Quelque chose qui me procure de la joie, et me fait sentir que je sais ce que je fais. + +Donc bien que je prévois toujours d'aider les personnes qui veulent concevoir pour les femmes, je prends une pause sur les vêtements féminins. + + + diff --git a/markdown/org/blog/bella-bodice-block/nl.md b/markdown/org/blog/bella-bodice-block/nl.md new file mode 100644 index 00000000000..25aef9a8aea --- /dev/null +++ b/markdown/org/blog/bella-bodice-block/nl.md @@ -0,0 +1,32 @@ +--- +author: "joostdecock" +caption: "Remember when we were allowed to go outside?" +date: "2021-01-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0faad5ded9176b4cf9e58cf5b05a939ba7670363-1920x1272.jpg" +intro: "We've just published a new pattern on this website: Bella, a bodice block for womenswear . It's a block with bust and waist dart, and a waist dart at the back." +title: "Het Bella bovenstuk basispatroon voor dameskledij" +--- + + +We've just published a new pattern on this website: [Bella, a bodice block for womenswear](/designs/bella/). It's a block with bust and waist dart, and a waist dart at the back. + +My goal when venturing into womenswear was to make one foundational block from which we could then spin out a range of different garments. + +Which is why we have [Breanna](/designs/breanna/), which I designed from scratch. Unfortunately, it hasn't been the end-all be-all that I — perhaps naively — hoped it would be. + +For Bella, I worked with someone from the industry to implement a design that is commonly used for commercial garment making. As such, I am curious to see how this one will pan out. + +My initial plan was to also make a variation with a shoulder dart at the front, to replace the bust dart, but in the end I settled for getting it released, rather than work on it longer. + +Which brings me to: + +##### I'm taking a break from womenswear + +I feel like I'm expending a lot of effort here for little result. It's getting me down, and I need a win. + +I want to work on something that I can not only design, but also make and wear. Something that gives me joy, and makes me feel like I know what I'm doing. + +So while I'll still help out people who want to design for women themselves, I am taking a break from womenswear. + + + diff --git a/markdown/org/blog/benjamin-bow-tie-beta/de.md b/markdown/org/blog/benjamin-bow-tie-beta/de.md new file mode 100644 index 00000000000..cca4d2855d5 --- /dev/null +++ b/markdown/org/blog/benjamin-bow-tie-beta/de.md @@ -0,0 +1,39 @@ +--- +author: "joostdecock" +caption: "Wenn es Ihnen gefällt, lassen Sie es uns wissen" +date: "2017-11-14" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8b04db622ddf3bff6e2d66a5305903a0e96edd58-2000x1333.jpg" +intro: "Unsere Familie an freien und opensource Schnittmustern ist wieder gewachsen, und das neueste Mitglied der Familie ist... Benjamin ." +title: "Das Schnittmuster für die Fliege Benjamin ist jetzt in der Beta-Version erhältlich. Und ich musste nicht einmal etwas tun." +--- + + +Unsere Familie an freien und opensource Schnittmustern ist wieder gewachsen, und das neueste Mitglied der Familie ist... [Benjamin](/patterns/benjamin). + +Benjamin ist eine Fliege, die mit einer Vielzahl von Optionen ausgestattet ist, um so ziemlich jeden Aspekt deiner Fliege einstellen zu können. + +Du kannst dich für eine maßgeschneiderte Fliege entscheiden oder Benjamin mit einem Einstellband entwerfen, das dir etwas Flexibilität in der Passform ermöglicht. Eine Eigenschaft, die diese Fliege zu einem großartigen handgefertigten Geschenk für die bevorstehende Weihnachtszeit macht. + +## Benjamin ist vielseitiger und ausgefallener, als man denkt + +Hier ist die Geschichte von Benjamin, über die ich mich am meisten freue: Ich habe nichts getan. + +![Eine Kollektion von Fliegen von Wouter, der dieses Muster entworfen und programmiert hat](benjamins.jpg) + +So ist es, Benjamin wurde von [Wouter van Wageningen](/users/xdpug) designed und erstellt, der sich in den letzten Monaten das Arbeiten mit FreeSewing selbst beigebracht hat: + +> Ich hatte einen Riesenspaß bei der Erstellung des Fliegenschnittes. Ich habe es im Grunde genommen benutzt, um das Tutorial mit dem Babylätzchen in etwas zu verwandeln, das originell und nicht zu komplex (und tatsächlich nützlich) ist. Ich wollte den gesamten Prozess verstehen und beherrschen bevor ich mich an größere Projekte wage. +> +> Dass ich mir die Dinge so einfach selbst erarbeiten konnte, liegt vor allem an dem großartigen [Babylätzchen Tutorial](https://freesewing.org/tutorials/pattern-design/) und an der Hilfestellungen, die ich im [Chat](https://discord.freesewing.org)erhalten habe. Jeder darf in dem Chat Fragen stellen. + +## Wer wird als Nächstes ein Schnittmuster beisteuern? + +Als ich Freesewing als Open-Source-Plattform veröffentlichte, hatte ich die Hoffnung, dass sich andere an den Bemühungen beteiligen würden. + +Aber ich hätte nie gedacht, dass weniger als drei Monate nach der öffentlichen Veröffentlichung von FreeSewing wir bereits das erste Schnittmuster, das aus der Community beigesteuert wird, auf FreeSewing veröffentlichen können. + +![Benjamin ist eine große Sache](giphy.gif) + +Also ja, Benjamin ist ein BFD, Wouter ist ein saucooler Typ, und ich bin zuversichtlich, dass dies das erste von vielen Schnittmustern ist, die wir als Gemeinschaft allen zugänglich machen können. + + diff --git a/markdown/org/blog/benjamin-bow-tie-beta/en.md b/markdown/org/blog/benjamin-bow-tie-beta/en.md new file mode 100644 index 00000000000..0de3c6930fe --- /dev/null +++ b/markdown/org/blog/benjamin-bow-tie-beta/en.md @@ -0,0 +1,48 @@ +--- +author: "joostdecock" +caption: "If you like it, put a bow on it" +date: "2017-11-14" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8b04db622ddf3bff6e2d66a5305903a0e96edd58-2000x1333.jpg" +intro: "Our family of freesewing patterns has grown once again, and the benjamin of the family is... Benjamin ." +title: "The Benjamin Bow Tie pattern is now available in beta. And I didn't even have to do anything." +--- + +Our family of freesewing patterns has grown once again, and the benjamin of the family is... [Benjamin](/designs/benjamin). + +Benjamin is a bow tie that comes with a variety of options to control pretty much every aspect of your bow tie. + +You can opt for a made-to-measure bow tie, or draft Benjamin with an adjustment ribbon to allow +some flexibility in the fit. Something that makes this a great handmade gift for the upcoming holiday season. + +## Benjamin is more special than you realize + +Here's the thing about Benjamin that I'm most excited about: I didn't do anything. + +![A collection of bow ties from Wouter, who designed and coded this pattern](https://posts.freesewing.org/uploads/bowties_4f3e05ec53.jpg) + +That's right, Benjamin was designed and coded by +[Wouter Van Wageningen](/users/xdpug) who has over the last couple of months +been teaching himself the ins and outs of the freesewing platform: + +> I had a blast making the Bow Tie pattern. +> I basically used it to move from the BabyBib tutorial into something that was +> original and not too complex (and actually useful). +> I wanted to get the whole process under control before venturing out into the real stuff. +> +> That I was able to pick things up so easily is due mostly to the great +> [BabyBib tutorial](https://freesewing.org/tutorials/pattern-design/) +> and the help you've provided [here](https://discord.freesewing.org). + +## Who will be next to contribute a pattern? + +When I released freesewing as an open source platform, I obviously hoped that others would +join the effort. + +But I never thought that less than 3 months after the public release of freesewing, +we'd have our first pattern from the freesewing community. + +![Benjamin is kind of a big deal](https://posts.freesewing.org/uploads/giphy_7a40f62815.gif) + +So yeah, Benjamin is a BFD, Wouter is a badass, and I am hopeful that this will be the first +of many patterns that we as a community will be able to make available to all. + diff --git a/markdown/org/blog/benjamin-bow-tie-beta/es.md b/markdown/org/blog/benjamin-bow-tie-beta/es.md new file mode 100644 index 00000000000..d015c0b66e3 --- /dev/null +++ b/markdown/org/blog/benjamin-bow-tie-beta/es.md @@ -0,0 +1,48 @@ +--- +author: "joostdecock" +caption: "If you like it, put a bow on it" +date: "2017-11-14" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8b04db622ddf3bff6e2d66a5305903a0e96edd58-2000x1333.jpg" +intro: "Our family of freesewing patterns has grown once again, and the benjamin of the family is... Benjamin ." +title: "The Benjamin Bow Tie pattern is now available in beta. And I didn't even have to do anything. [No traducido]" +--- + +Our family of freesewing patterns has grown once again, and the benjamin of the family is... [Benjamin](/designs/benjamin). + +Benjamin is a bow tie that comes with a variety of options to control pretty much every aspect of your bow tie. + +You can opt for a made-to-measure bow tie, or draft Benjamin with an adjustment ribbon to allow +some flexibility in the fit. Something that makes this a great handmade gift for the upcoming holiday season. + +## Benjamin is more special than you realize + +Here's the thing about Benjamin that I'm most excited about: I didn't do anything. + +![A collection of bow ties from Wouter, who designed and coded this pattern](https://posts.freesewing.org/uploads/bowties_4f3e05ec53.jpg) + +That's right, Benjamin was designed and coded by +[Wouter Van Wageningen](/users/xdpug) who has over the last couple of months +been teaching himself the ins and outs of the freesewing platform: + +> I had a blast making the Bow Tie pattern. +> I basically used it to move from the BabyBib tutorial into something that was +> original and not too complex (and actually useful). +> I wanted to get the whole process under control before venturing out into the real stuff. +> +> That I was able to pick things up so easily is due mostly to the great +> [BabyBib tutorial](https://freesewing.org/tutorials/pattern-design/) +> and the help you've provided [here](https://discord.freesewing.org). + +## Who will be next to contribute a pattern? + +When I released freesewing as an open source platform, I obviously hoped that others would +join the effort. + +But I never thought that less than 3 months after the public release of freesewing, +we'd have our first pattern from the freesewing community. + +![Benjamin is kind of a big deal](https://posts.freesewing.org/uploads/giphy_7a40f62815.gif) + +So yeah, Benjamin is a BFD, Wouter is a badass, and I am hopeful that this will be the first +of many patterns that we as a community will be able to make available to all. + diff --git a/markdown/org/blog/benjamin-bow-tie-beta/fr.md b/markdown/org/blog/benjamin-bow-tie-beta/fr.md new file mode 100644 index 00000000000..fb76447199d --- /dev/null +++ b/markdown/org/blog/benjamin-bow-tie-beta/fr.md @@ -0,0 +1,48 @@ +--- +author: "joostdecock" +caption: "If you like it, put a bow on it" +date: "2017-11-14" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8b04db622ddf3bff6e2d66a5305903a0e96edd58-2000x1333.jpg" +intro: "Our family of freesewing patterns has grown once again, and the benjamin of the family is... Benjamin ." +title: "The Benjamin Bow Tie pattern is now available in beta. And I didn't even have to do anything. [Non traduit]" +--- + +Our family of freesewing patterns has grown once again, and the benjamin of the family is... [Benjamin](/designs/benjamin). + +Benjamin is a bow tie that comes with a variety of options to control pretty much every aspect of your bow tie. + +You can opt for a made-to-measure bow tie, or draft Benjamin with an adjustment ribbon to allow +some flexibility in the fit. Something that makes this a great handmade gift for the upcoming holiday season. + +## Benjamin is more special than you realize + +Here's the thing about Benjamin that I'm most excited about: I didn't do anything. + +![A collection of bow ties from Wouter, who designed and coded this pattern](https://posts.freesewing.org/uploads/bowties_4f3e05ec53.jpg) + +That's right, Benjamin was designed and coded by +[Wouter Van Wageningen](/users/xdpug) who has over the last couple of months +been teaching himself the ins and outs of the freesewing platform: + +> I had a blast making the Bow Tie pattern. +> I basically used it to move from the BabyBib tutorial into something that was +> original and not too complex (and actually useful). +> I wanted to get the whole process under control before venturing out into the real stuff. +> +> That I was able to pick things up so easily is due mostly to the great +> [BabyBib tutorial](https://freesewing.org/tutorials/pattern-design/) +> and the help you've provided [here](https://discord.freesewing.org). + +## Who will be next to contribute a pattern? + +When I released freesewing as an open source platform, I obviously hoped that others would +join the effort. + +But I never thought that less than 3 months after the public release of freesewing, +we'd have our first pattern from the freesewing community. + +![Benjamin is kind of a big deal](https://posts.freesewing.org/uploads/giphy_7a40f62815.gif) + +So yeah, Benjamin is a BFD, Wouter is a badass, and I am hopeful that this will be the first +of many patterns that we as a community will be able to make available to all. + diff --git a/markdown/org/blog/benjamin-bow-tie-beta/nl.md b/markdown/org/blog/benjamin-bow-tie-beta/nl.md new file mode 100644 index 00000000000..592079c5229 --- /dev/null +++ b/markdown/org/blog/benjamin-bow-tie-beta/nl.md @@ -0,0 +1,39 @@ +--- +author: "joostdecock" +caption: "Doe er een strikje rond" +date: "2017-11-14" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8b04db622ddf3bff6e2d66a5305903a0e96edd58-2000x1333.jpg" +intro: "Onze familie van FreeSewing-patronen is opnieuw gegroeid. En de benjamin van de familie is ... Benjamin ." +title: "Het patroon voor de Benjamin-vlinderdas is nu beschikbaar in beta. En ik heb er zelfs niets voor moeten doen." +--- + + +Onze familie van FreeSewing-patronen is opnieuw gegroeid. En de benjamin van de familie is ... [Benjamin](/patterns/benjamin). + +Benjamin is een vlinderdas met een aantal opties om zowat elk aspect van jouw vlinderdas aan te passen. + +Je kan kiezen voor een vlinderdas op maat, of je kan Benjamin schetsen met een aanpasbaar lint voor een meer flexibele pasvorm. Dat maakt trouwens dat dit een heel leuk handgemaakt cadeau is voor de feestdagen. + +## Benjamin is bijzonderder dan je denkt + +Wat ik nog het beste vind aan Benjamin? Ik heb er niks voor moeten doen. + +![Een verzameling vlinderdasjes van Wouter, die dit patroon ontworpen en gecodeerd heeft](benjamins.jpg) + +Echt waar. Benjamin is ontworpen en gecodeerd door [Wouter Van Wageningen](/users/xdpug) die zich de afgelopen maanden heeft beziggehouden met bijleren over de hele werking van het FreeSewing-platform: + +> Ik heb me enorm geamuseerd met dit vlinderdaspatroon te maken. Eigenlijk heb ik dit project gebruikt om van de BabyBib-tutorial over te stappen op iets dat origineel was en niet te ingewikkeld (en nog bruikbaar ook). Ik wou het hele proces onder de knie krijgen voordat ik overging naar het echte werk. +> +> That I was able to pick things up so easily is due mostly to the great [BabyBib tutorial](https://freesewing.org/tutorials/pattern-design/) and the help you've provided [here](https://discord.freesewing.org). + +## Wie is de volgende om een patroon bij te dragen? + +Toen ik FreeSewing lanceerde als een open-sourceplatform, hoopte ik uiteraard dat anderen erin mee zouden stappen. + +Maar ik had nooit gedacht dat op minder dan drie maanden tijd na de officiële lancering van FreeSewing, we ons eerste patroon vanuit de FreeSewing-community zouden hebben. + +![Benjamin is eigenlijk echt baanbrekend](giphy.gif) + +Voilà: Benjamin is fenomenaal, Wouter is een kei, en ik heb er goede hoop op dat dit de eerste is van vele patronen die we als community beschikbaar gaan maken voor iedereen. + + diff --git a/markdown/org/blog/breanna-measurements-sizes-in-2-2/de.md b/markdown/org/blog/breanna-measurements-sizes-in-2-2/de.md new file mode 100644 index 00000000000..42d70b877aa --- /dev/null +++ b/markdown/org/blog/breanna-measurements-sizes-in-2-2/de.md @@ -0,0 +1,99 @@ +--- +author: "joostdecock" +caption: "Dieser Beitrag beschreibt, was in Version 2.2 von FreeSewing neu ist" +date: "2020-02-22" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/356c127b8b37937b9537790d71a949c236027513-1920x1280.jpg" +intro: "Version 2.2 von FreeSewing ist da, und sie hat eine Menge großer und kleiner Änderungen und Verbesserungen. Das Änderungsprotokoll listet alle Änderungen auf, aber hier ist, was Sie wissen müssen:" +title: "Ein Blick auf die Neuerungen in FreeSewing 2.2, darunter Breanna, unser Grundschnittblock für Damenoberbekleidung" +--- + + + +Version 2.2 von FreeSewing ist da, und sie hat eine Menge großer und kleiner Änderungen und Verbesserungen. Das [Änderungsprotokoll](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md) listet alle Änderungen auf, aber hier ist, was Sie wissen müssen: + + - [Neues Schnittmuster: Breanna ist ein Grundschnittblock für Damenoberbekleidung](#new-pattern-breanna-is-a-bodice-block-for-womenswear) + - [Neue/Verschiedene Maße zur besseren Anpassung an Damenbekleidung](#newdifferent-measurements-to-better-suit-womenswear) + - [Erzeugen von Schnittmustern in *Standard*-Größen (kein Konto erforderlich)](#generate-patterns-in-standard-sizes-no-account-required) + +Schauen wir uns an, was das im Einzelnen bedeutet: + +## Neues Schnittmuster: Breanna ist ein Grundschnittblock für Damenoberbekleidung + +![Breanna line drawing](breanna.svg) + +Schauen Sie sich [Breanna](/designs/breanna/), unser Grundschnittblock für Damenoberbekleidung an. + +Ein Grundschnittblock ist vielleicht nicht das aufregendste Schnittmuster, das es gibt, aber er spielt eine wichtige Rolle, da er die Grundform ist, auf der andere Schnittmuster aufgebaut sind. For example, we have a similar block for menswear called [Brian](/designs/brian/) and our [Aaron](/designs/aaron/), [Bent](/designs/bent/), [Carlita](/designs/carlita/), [Carlton](/designs/carlton/), [Huey](/designs/huey/), [Hugo](/designs/hugo/), [Jaeger](/designs/jaeger/), [Simon](/designs/simon/), [Simone](/designs/simone/), [Sven](/designs/sven/), and [Wahid](/designs/wahid/) patterns can all can trace their lineage back to Brain somehow. + +In other words, Breanna is an important building block for us to extend our womenswear collection. But that doesn't mean it's not good news for you too. If you've been sewing for a while, chances are drafting your own block/sloper has perpetually been on your to-do list. Well, good news, because here's your block ready to go. + +Oh, and of course it's got all the bells and whistles you've come to expect from us. Have a look at [the pattern options](/docs/patterns/breanna/options/) and I think you'll be positively impressed. If nothing else, this block can accommodate 1 or 2 bust darts in 15 different places, giving you 120 unique ways to place your bust dart(s). + +Breanna has has been a while in the making, and we'd love to get your feedback on it. Making a muslin from a block like this really isn't much work. So if you've got some time to spare to whip this one up and let us know how it went, that would be great. + + +## Neue/Verschiedene Maße zur besseren Anpassung an Damenbekleidung + +Now that we're making our jouney into womenswear, we realized that the measurements we use on the site are somewhat skewed towards menswear. In addition, we had a lot of people stuggling with the shoulder slope measurement. So we decided to re-visit our measuremets, and we've made the following changes: + +### We have a bunch of new *HPS* measurements + +We've settled on the High-Point Shoulder, the so-called HPS point, as the basis for many of the vertical torso measurements. If you're not certain what/where the HPS point is, [check the HPS documentation](/docs/measurements/hps/). + +### We discontinued the Center Back To Neck measurement + +As we mentioned earlier, we use measurements from the HPS point now for vertical torso measurements. As a result, we've discontinued the old *Center back neck to waist* measurement. + +Given that this measurement is now gone, you may need to add another measurement for certain patterns. + +### We changed the way the shoulder slope is measured + +We noticed that people struggles with the way we asked them to measure [the shoulder slope measurement](/docs/measurements/shoulderslope) so we have changed how to do that. + +Because the new method yields a very different number (that ultimately captures the same thing, how much your shoulder slopes downward) here too we had to go in and reset all the existing data. In other words, you'll have to re-measure your shoulder slope. + +## Generate patterns in *standard* sizes (no account required + +To get great patterns, you need good measurements, and a bunch of them. It's what we do here at FreeSewing, and most of the problems with patterns are because something goes wrong with taking measurements. + +Unfortunately, there is no magic shortcut for this. If you want something made-to-measure, it's always going to start with acurate measurements. + +This does raise the bar for people who are new to the site, and want to kick the tires. + +> *Oooh, free patterns, nice* 😍 *Wait, I have to create an account first?* 🤔 *And take all these measurements?* 😬 *That seems like a lot of work.* + +Fair enough. + +In addition, our regular visitors also asked us whether they could get to see a pattern and play around with it without first having to put in a bunch of measurements. + +So __*drumroll*__ that is no longer required. We now offer all our patterns in *standard sizes*. Not only do you not have to take measurements to try out the patterns, you don't even have to sign up or log in. No account needed, just pick a pattern, a size, and you're good to go. + +Obvously, made-to-measure patterns is *our thing*, and we're not changing that. But we're hoping that by lowering the bar to try out our platform, more people will give FreeSewing a try. + +### What are standard sizes anyway? + +The hardest thing about adding support for standard sizes? Figuring out what the heck standard sizes are supposed to be. We took a stab at it, and if you're curious you can [check out our sizing table here](/docs/various/sizes/). + +For menswear, our size range is 32 to 50, and they are based on a size 38 baseline that we then graded up and down. For womenswear, our size range is 28 to 48, and they are based on a size 34 baseline that we then graded up and down. + + + +If you're not sure what these numbers are, they are the neck circumference in cm. + + + +While we tried to make our size ranges inclusive, and these tables are an honest attempt to come up with something that makes sense, please understand that this is not our core business. We've love to hear your feedback on the sizing tables, and are open to tweaks and suggestions, but at the end of the day, what we want is to give you a pattern drafted to your measurements. These sizes are just a way to lure you in 🤫 + + +## Also: All the other stuff + +Now go and click around, for we've changed a bunch of other stuff too. + +If you bump into any problems or have questions, as always [our chat room is the place to get in touch](https://discord.freesewing.org/). + +And if you happen to like what we do here, perhaps now is a good time to tell your friends about FreeSewing. After all, they can now check it out without needing to sign up. + +PS: We have [a handy share page](/share/) you can use for this. + + + diff --git a/markdown/org/blog/breanna-measurements-sizes-in-2-2/en.md b/markdown/org/blog/breanna-measurements-sizes-in-2-2/en.md new file mode 100644 index 00000000000..7a65e58f30f --- /dev/null +++ b/markdown/org/blog/breanna-measurements-sizes-in-2-2/en.md @@ -0,0 +1,151 @@ +--- +author: "joostdecock" +caption: "This post describes what's new in version 2.2 of FreeSewing" +date: "2020-02-22" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/356c127b8b37937b9537790d71a949c236027513-1920x1280.jpg" +intro: "A look at what's new in FreeSewing 2.2, including Breanna, our bodice block for womenswear" +title: "A look at what's new in FreeSewing 2.2, including Breanna, our bodice block for womenswear" +--- + +Version 2.2 of FreeSewing is here, and it has a bunch of changes and improvements big and small. +The [changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md) lists all the changes, but here's what you need to know: + + - [New pattern: Breanna is a bodice block for womenswear](#new-pattern-breanna-is-a-bodice-block-for-womenswear) + - [New/Different measurements to better suit womenswear](#newdifferent-measurements-to-better-suit-womenswear) + - [Generate patterns in *standard* sizes (no account required)](#generate-patterns-in-standard-sizes-no-account-required) + +Let's have a look at what it all means: + +## New pattern: Breanna is a bodice block for womenswear + + + +Meet [Breanna](/designs/breanna/), our bodice block for womenswear. + +A block (or sloper) may not the most exciting pattern to look at, but it plays an important +role as it is the basic form which other patterns are built on. + +For example, we have a similar block for menswear called [Brian](/designs/brian/) and our +[Aaron](/designs/aaron/), +[Bent](/designs/bent/), +[Carlita](/designs/carlita/), +[Carlton](/designs/carlton/), +[Huey](/designs/huey/), +[Hugo](/designs/hugo/), +[Jaeger](/designs/jaeger/), +[Simon](/designs/simon/), +[Simone](/designs/simone/), +[Sven](/designs/sven/), +and [Wahid](/designs/wahid/) patterns can all can trace their lineage back to Brain somehow. + +In other words, Breanna is an important building block for us to extend our womenswear collection. +But that does not mean it is not good news for you too. If you have been sewing for +a while, chances are drafting your own block/sloper has perpetually been on your +to-do list. Well, good news, because here is your block ready to go. + +Oh, and of course it has all the bells and whistles you can expect from us. +Have a look at [the pattern options](/docs/patterns/breanna/options/) and +I think you'll be positively impressed. If nothing else, this block can accommodate 1 or 2 bust +darts in 15 different places, giving you 120 unique ways to place your bust dart(s). + +Breanna has has been a while in the making, and we'd love to get your feedback on it. +Making a muslin from a block like this really isn't much work. +So if you've got some time to spare to whip this one up and let us know how it went, +that would be great. + + +## New/Different measurements to better suit womenswear + +Now that we're making our jouney into womenswear, we realized that the measurements we +use on the site are somewhat skewed towards menswear. In addition, we had a lot of people +stuggling with the shoulder slope measurement. So we decided to re-visit our measuremets, +and we've made the following changes: + +### We have a bunch of new *HPS* measurements + +We've settled on the High-Point Shoulder, the so-called HPS point, as the basis for many +of the vertical torso measurements. If you're not certain what/where the HPS point is, +[check the HPS documentation](/docs/measurements/hps/). + +### We discontinued the Center Back To Neck measurement + +As we mentioned earlier, we use measurements from the HPS point now for vertical torso +measurements. As a result, we've discontinued the old *Center back neck to waist* measurement. + +Given that this measurement is now gone, you may need to add another measurement for certain patterns. + +### We changed the way the shoulder slope is measured + +We noticed that people struggles with the way we asked them to measure [the +shoulder slope measurement](/docs/measurements/shoulderslope) so we have changed how to do that. + +Because the new method yields a very different number (that ultimately captures the same +thing, how much your shoulder slopes downward) here too we had to go in and reset all +the existing data. In other words, you'll have to re-measure your shoulder slope. + +## Generate patterns in *standard* sizes (no account required + +To get great patterns, you need good measurements, and a bunch of them. +It's what we do here at FreeSewing, and most of the problems with patterns are because +something goes wrong with taking measurements. + +Unfortunately, there is no magic shortcut for this. If you want something made-to-measure, +it's always going to start with acurate measurements. + +This does raise the bar for people who are new to the site, and want to kick the tires. + +> *Oooh, free patterns, nice* 😍 +> *Wait, I have to create an account first?* 🤔 +> *And take all these measurements?* 😬 +> *That seems like a lot of work.* + +Fair enough. + +In addition, our regular visitors also asked us whether they could get to see a pattern and +play around with it without first having to put in a bunch of measurements. + +So __*drumroll*__ that is no longer required. We now offer all our patterns in *standard sizes*. +Not only do you not have to take measurements to try out the patterns, you don't even have to sign up +or log in. No account needed, just pick a pattern, a size, and you're good to go. + +Obvously, made-to-measure patterns is *our thing*, and we're not changing that. But we're hoping +that by lowering the bar to try out our platform, more people will give FreeSewing a try. + +### What are standard sizes anyway? + +The hardest thing about adding support for standard sizes? Figuring out what the heck standard sizes +are supposed to be. We took a stab at it, and if you're curious you can [check out +our sizing table here](/docs/various/sizes/). + +For menswear, our size range is 32 to 50, and they are based on a size 38 baseline that we then graded +up and down. +For womenswear, our size range is 28 to 48, and they are based on a size 34 baseline that we then graded +up and down. + + + +If you're not sure what these numbers are, they are the neck circumference in cm. + + + +While we tried to make our size ranges inclusive, and these tables are an honest attempt to come up with +something that makes sense, please understand that this is not our core business. +We've love to hear your feedback on the sizing tables, and are open to tweaks and suggestions, but at +the end of the day, what we want is to give you a pattern drafted to your measurements. +These sizes are just a way to lure you in 🤫 + + +## Also: All the other stuff + +Now go and click around, for we've changed a bunch of other stuff too. + +If you bump into any problems or have questions, as always [our chat room is the place to get +in touch](https://discord.freesewing.org/). + +And if you happen to like what we do here, perhaps now is a good time to tell your friends about +FreeSewing. After all, they can now check it out without needing to sign up. + +PS: We have [a handy share page](/share/) you can use for this. + + + diff --git a/markdown/org/blog/breanna-measurements-sizes-in-2-2/es.md b/markdown/org/blog/breanna-measurements-sizes-in-2-2/es.md new file mode 100644 index 00000000000..24c3690b4f4 --- /dev/null +++ b/markdown/org/blog/breanna-measurements-sizes-in-2-2/es.md @@ -0,0 +1,151 @@ +--- +author: "joostdecock" +caption: "This post describes what's new in version 2.2 of FreeSewing" +date: "2020-02-22" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/356c127b8b37937b9537790d71a949c236027513-1920x1280.jpg" +intro: "A look at what's new in FreeSewing 2.2, including Breanna, our bodice block for womenswear [No traducido]" +title: "A look at what's new in FreeSewing 2.2, including Breanna, our bodice block for womenswear [No traducido]" +--- + +Version 2.2 of FreeSewing is here, and it has a bunch of changes and improvements big and small. +The [changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md) lists all the changes, but here's what you need to know: + + - [New pattern: Breanna is a bodice block for womenswear](#new-pattern-breanna-is-a-bodice-block-for-womenswear) + - [New/Different measurements to better suit womenswear](#newdifferent-measurements-to-better-suit-womenswear) + - [Generate patterns in *standard* sizes (no account required)](#generate-patterns-in-standard-sizes-no-account-required) + +Let's have a look at what it all means: + +## New pattern: Breanna is a bodice block for womenswear + + + +Meet [Breanna](/designs/breanna/), our bodice block for womenswear. + +A block (or sloper) may not the most exciting pattern to look at, but it plays an important +role as it is the basic form which other patterns are built on. + +For example, we have a similar block for menswear called [Brian](/designs/brian/) and our +[Aaron](/designs/aaron/), +[Bent](/designs/bent/), +[Carlita](/designs/carlita/), +[Carlton](/designs/carlton/), +[Huey](/designs/huey/), +[Hugo](/designs/hugo/), +[Jaeger](/designs/jaeger/), +[Simon](/designs/simon/), +[Simone](/designs/simone/), +[Sven](/designs/sven/), +and [Wahid](/designs/wahid/) patterns can all can trace their lineage back to Brain somehow. + +In other words, Breanna is an important building block for us to extend our womenswear collection. +But that does not mean it is not good news for you too. If you have been sewing for +a while, chances are drafting your own block/sloper has perpetually been on your +to-do list. Well, good news, because here is your block ready to go. + +Oh, and of course it has all the bells and whistles you can expect from us. +Have a look at [the pattern options](/docs/patterns/breanna/options/) and +I think you'll be positively impressed. If nothing else, this block can accommodate 1 or 2 bust +darts in 15 different places, giving you 120 unique ways to place your bust dart(s). + +Breanna has has been a while in the making, and we'd love to get your feedback on it. +Making a muslin from a block like this really isn't much work. +So if you've got some time to spare to whip this one up and let us know how it went, +that would be great. + + +## New/Different measurements to better suit womenswear + +Now that we're making our jouney into womenswear, we realized that the measurements we +use on the site are somewhat skewed towards menswear. In addition, we had a lot of people +stuggling with the shoulder slope measurement. So we decided to re-visit our measuremets, +and we've made the following changes: + +### We have a bunch of new *HPS* measurements + +We've settled on the High-Point Shoulder, the so-called HPS point, as the basis for many +of the vertical torso measurements. If you're not certain what/where the HPS point is, +[check the HPS documentation](/docs/measurements/hps/). + +### We discontinued the Center Back To Neck measurement + +As we mentioned earlier, we use measurements from the HPS point now for vertical torso +measurements. As a result, we've discontinued the old *Center back neck to waist* measurement. + +Given that this measurement is now gone, you may need to add another measurement for certain patterns. + +### We changed the way the shoulder slope is measured + +We noticed that people struggles with the way we asked them to measure [the +shoulder slope measurement](/docs/measurements/shoulderslope) so we have changed how to do that. + +Because the new method yields a very different number (that ultimately captures the same +thing, how much your shoulder slopes downward) here too we had to go in and reset all +the existing data. In other words, you'll have to re-measure your shoulder slope. + +## Generate patterns in *standard* sizes (no account required + +To get great patterns, you need good measurements, and a bunch of them. +It's what we do here at FreeSewing, and most of the problems with patterns are because +something goes wrong with taking measurements. + +Unfortunately, there is no magic shortcut for this. If you want something made-to-measure, +it's always going to start with acurate measurements. + +This does raise the bar for people who are new to the site, and want to kick the tires. + +> *Oooh, free patterns, nice* 😍 +> *Wait, I have to create an account first?* 🤔 +> *And take all these measurements?* 😬 +> *That seems like a lot of work.* + +Fair enough. + +In addition, our regular visitors also asked us whether they could get to see a pattern and +play around with it without first having to put in a bunch of measurements. + +So __*drumroll*__ that is no longer required. We now offer all our patterns in *standard sizes*. +Not only do you not have to take measurements to try out the patterns, you don't even have to sign up +or log in. No account needed, just pick a pattern, a size, and you're good to go. + +Obvously, made-to-measure patterns is *our thing*, and we're not changing that. But we're hoping +that by lowering the bar to try out our platform, more people will give FreeSewing a try. + +### What are standard sizes anyway? + +The hardest thing about adding support for standard sizes? Figuring out what the heck standard sizes +are supposed to be. We took a stab at it, and if you're curious you can [check out +our sizing table here](/docs/various/sizes/). + +For menswear, our size range is 32 to 50, and they are based on a size 38 baseline that we then graded +up and down. +For womenswear, our size range is 28 to 48, and they are based on a size 34 baseline that we then graded +up and down. + + + +If you're not sure what these numbers are, they are the neck circumference in cm. + + + +While we tried to make our size ranges inclusive, and these tables are an honest attempt to come up with +something that makes sense, please understand that this is not our core business. +We've love to hear your feedback on the sizing tables, and are open to tweaks and suggestions, but at +the end of the day, what we want is to give you a pattern drafted to your measurements. +These sizes are just a way to lure you in 🤫 + + +## Also: All the other stuff + +Now go and click around, for we've changed a bunch of other stuff too. + +If you bump into any problems or have questions, as always [our chat room is the place to get +in touch](https://discord.freesewing.org/). + +And if you happen to like what we do here, perhaps now is a good time to tell your friends about +FreeSewing. After all, they can now check it out without needing to sign up. + +PS: We have [a handy share page](/share/) you can use for this. + + + diff --git a/markdown/org/blog/breanna-measurements-sizes-in-2-2/fr.md b/markdown/org/blog/breanna-measurements-sizes-in-2-2/fr.md new file mode 100644 index 00000000000..73e44d80031 --- /dev/null +++ b/markdown/org/blog/breanna-measurements-sizes-in-2-2/fr.md @@ -0,0 +1,151 @@ +--- +author: "joostdecock" +caption: "This post describes what's new in version 2.2 of FreeSewing" +date: "2020-02-22" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/356c127b8b37937b9537790d71a949c236027513-1920x1280.jpg" +intro: "A look at what's new in FreeSewing 2.2, including Breanna, our bodice block for womenswear [Non traduit]" +title: "A look at what's new in FreeSewing 2.2, including Breanna, our bodice block for womenswear [Non traduit]" +--- + +Version 2.2 of FreeSewing is here, and it has a bunch of changes and improvements big and small. +The [changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md) lists all the changes, but here's what you need to know: + + - [New pattern: Breanna is a bodice block for womenswear](#new-pattern-breanna-is-a-bodice-block-for-womenswear) + - [New/Different measurements to better suit womenswear](#newdifferent-measurements-to-better-suit-womenswear) + - [Generate patterns in *standard* sizes (no account required)](#generate-patterns-in-standard-sizes-no-account-required) + +Let's have a look at what it all means: + +## New pattern: Breanna is a bodice block for womenswear + + + +Meet [Breanna](/designs/breanna/), our bodice block for womenswear. + +A block (or sloper) may not the most exciting pattern to look at, but it plays an important +role as it is the basic form which other patterns are built on. + +For example, we have a similar block for menswear called [Brian](/designs/brian/) and our +[Aaron](/designs/aaron/), +[Bent](/designs/bent/), +[Carlita](/designs/carlita/), +[Carlton](/designs/carlton/), +[Huey](/designs/huey/), +[Hugo](/designs/hugo/), +[Jaeger](/designs/jaeger/), +[Simon](/designs/simon/), +[Simone](/designs/simone/), +[Sven](/designs/sven/), +and [Wahid](/designs/wahid/) patterns can all can trace their lineage back to Brain somehow. + +In other words, Breanna is an important building block for us to extend our womenswear collection. +But that does not mean it is not good news for you too. If you have been sewing for +a while, chances are drafting your own block/sloper has perpetually been on your +to-do list. Well, good news, because here is your block ready to go. + +Oh, and of course it has all the bells and whistles you can expect from us. +Have a look at [the pattern options](/docs/patterns/breanna/options/) and +I think you'll be positively impressed. If nothing else, this block can accommodate 1 or 2 bust +darts in 15 different places, giving you 120 unique ways to place your bust dart(s). + +Breanna has has been a while in the making, and we'd love to get your feedback on it. +Making a muslin from a block like this really isn't much work. +So if you've got some time to spare to whip this one up and let us know how it went, +that would be great. + + +## New/Different measurements to better suit womenswear + +Now that we're making our jouney into womenswear, we realized that the measurements we +use on the site are somewhat skewed towards menswear. In addition, we had a lot of people +stuggling with the shoulder slope measurement. So we decided to re-visit our measuremets, +and we've made the following changes: + +### We have a bunch of new *HPS* measurements + +We've settled on the High-Point Shoulder, the so-called HPS point, as the basis for many +of the vertical torso measurements. If you're not certain what/where the HPS point is, +[check the HPS documentation](/docs/measurements/hps/). + +### We discontinued the Center Back To Neck measurement + +As we mentioned earlier, we use measurements from the HPS point now for vertical torso +measurements. As a result, we've discontinued the old *Center back neck to waist* measurement. + +Given that this measurement is now gone, you may need to add another measurement for certain patterns. + +### We changed the way the shoulder slope is measured + +We noticed that people struggles with the way we asked them to measure [the +shoulder slope measurement](/docs/measurements/shoulderslope) so we have changed how to do that. + +Because the new method yields a very different number (that ultimately captures the same +thing, how much your shoulder slopes downward) here too we had to go in and reset all +the existing data. In other words, you'll have to re-measure your shoulder slope. + +## Generate patterns in *standard* sizes (no account required + +To get great patterns, you need good measurements, and a bunch of them. +It's what we do here at FreeSewing, and most of the problems with patterns are because +something goes wrong with taking measurements. + +Unfortunately, there is no magic shortcut for this. If you want something made-to-measure, +it's always going to start with acurate measurements. + +This does raise the bar for people who are new to the site, and want to kick the tires. + +> *Oooh, free patterns, nice* 😍 +> *Wait, I have to create an account first?* 🤔 +> *And take all these measurements?* 😬 +> *That seems like a lot of work.* + +Fair enough. + +In addition, our regular visitors also asked us whether they could get to see a pattern and +play around with it without first having to put in a bunch of measurements. + +So __*drumroll*__ that is no longer required. We now offer all our patterns in *standard sizes*. +Not only do you not have to take measurements to try out the patterns, you don't even have to sign up +or log in. No account needed, just pick a pattern, a size, and you're good to go. + +Obvously, made-to-measure patterns is *our thing*, and we're not changing that. But we're hoping +that by lowering the bar to try out our platform, more people will give FreeSewing a try. + +### What are standard sizes anyway? + +The hardest thing about adding support for standard sizes? Figuring out what the heck standard sizes +are supposed to be. We took a stab at it, and if you're curious you can [check out +our sizing table here](/docs/various/sizes/). + +For menswear, our size range is 32 to 50, and they are based on a size 38 baseline that we then graded +up and down. +For womenswear, our size range is 28 to 48, and they are based on a size 34 baseline that we then graded +up and down. + + + +If you're not sure what these numbers are, they are the neck circumference in cm. + + + +While we tried to make our size ranges inclusive, and these tables are an honest attempt to come up with +something that makes sense, please understand that this is not our core business. +We've love to hear your feedback on the sizing tables, and are open to tweaks and suggestions, but at +the end of the day, what we want is to give you a pattern drafted to your measurements. +These sizes are just a way to lure you in 🤫 + + +## Also: All the other stuff + +Now go and click around, for we've changed a bunch of other stuff too. + +If you bump into any problems or have questions, as always [our chat room is the place to get +in touch](https://discord.freesewing.org/). + +And if you happen to like what we do here, perhaps now is a good time to tell your friends about +FreeSewing. After all, they can now check it out without needing to sign up. + +PS: We have [a handy share page](/share/) you can use for this. + + + diff --git a/markdown/org/blog/breanna-measurements-sizes-in-2-2/nl.md b/markdown/org/blog/breanna-measurements-sizes-in-2-2/nl.md new file mode 100644 index 00000000000..61bb05accc2 --- /dev/null +++ b/markdown/org/blog/breanna-measurements-sizes-in-2-2/nl.md @@ -0,0 +1,99 @@ +--- +author: "joostdecock" +caption: "Deze post geeft weer wat er nieuw is in versie 2.2 van FreeSewing" +date: "2020-02-22" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/356c127b8b37937b9537790d71a949c236027513-1920x1280.jpg" +intro: "Versie 2.2 van FreeSewing is hier, en zit vol met kleine en grote veranderingen en verbeteringen. In ons changelog vind je een overzicht van alle aanpassingen, maar dit is wat je erover moet weten:" +title: "Een blik op de nieuwigheden in FreeSewing 2.2, inclusief Breanna, ons basiscorsage voor dameskleding" +--- + + + +Versie 2.2 van FreeSewing is hier, en zit vol met kleine en grote veranderingen en verbeteringen. In ons [changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md) vind je een overzicht van alle aanpassingen, maar dit is wat je erover moet weten: + + - [Nieuw patroon: Breanna is een basiscorsage voor dameskleding](#nieuw-patroon-breanna-basiscorsage-dames) + - [Nieuwe/andere afmetingen om beter aan te sluiten bij vrouwenkleding](#nieuwe-afmetingen-voor-dameskleding) + - [*Standaardmaten* voor patronen (beschikbaar zonder account)](#standaardmaten-voor-patronen-zonder-account) + +Even kijken wat dat allemaal betekent: + +## Nieuw patroon: Breanna is een basiscorsage voor dameskleding + +![Lijntekening voor Breanna](breanna.svg) + +We stellen je [Breanna](/designs/breanna/) voor, ons basiscorsage voor vrouwenkleding. + +Een basisvorm is misschien niet het spannendste patroon om naar te kijken, maar het speelt een belangrijke rol als vertrekpunt voor andere patronen. We hebben bijvoorbeeld een vergelijkbare basisvorm voor herenkleding genaamd [Brian](/designs/brian/). De patronen [Aaron](/designs/aaron/), [Bent](/designs/bent/), [Carlita](/designs/carlita/), [Carlton](/designs/carlton/), [Huey](/designs/huey/), [Hugo](/designs/hugo/), [Jaeger](/designs/jaeger/), [Simon](/designs/simon/), [Simone](/designs/simone/), [Sven](/designs/sven/) en [Wahid](/designs/wahid/) zijn allemaal op de een of andere manier verwant met Brian. + +Breanna is met andere woorden een belangrijke bouwsteen voor ons om onze collectie voor dameskledij uit te breiden. Maar dat betekent niet dat het ook voor jou geen goed nieuws is. Als je al een tijdje met naaien bezig bent, dan is de kans groot dat een je eigen basiscorsage al een tijd op je to-dolijstje staat. Wel, goed nieuws: hier is je basisvorm, kant en klaar. + +En natuurlijk heeft Brianna alle toeters en bellen die je intussen van ons verwacht. Have a look at [the pattern options](/docs/patterns/breanna/options/) and I think you'll be positively impressed. Dit basiscorsage geeft je bijvoorbeeld de optie van 1 of 2 coupenaden op 15 mogelijke posities. Dat geeft je in totaal 120 unieke manieren om je coupenaad of -naden te plaatsen. + +Breanna is al een tijdje in ontwikkeling. We zijn benieuwd naar je feedback erop. Het is echt niet veel werk om een toile te maken van een basiscorsage zoals dit. Dus als je wat tijd vrij hebt om dit patroon te testen en ons te laten weten wat je ervan vindt, dan zou dat geweldig zijn. + + +## Nieuwe/andere afmetingen om beter aan te sluiten bij vrouwenkleding + +Nu we ons in de dameskleding storten, hebben we beseft dat de afmetingen die we op onze site gebruiken nogal gericht zijn op herenkleding. Bovendien hebben we gemerkt dat veel mensen het moeilijk hebben met de afmeting van de schouderhelling. Dus hebben we beslist om onze afmetingen opnieuw onder de loep te nemen, en hebben we de volgende aanpassingen gemaakt: + +### We hebben een hoop nieuwe schouderpuntafmetingen + +We hebben beslist om te vertrekken van het schouderpunt (*High-Point Shoulder* of *HPS point*) voor een heel aantal van de verticale torso-afmetingen. Als je niet zeker weet wat het schouderpunt is of waar het zich bevindt, kijk dan in de [HPS-documentatie](/docs/measurements/hps/). + +### We gaan niet verder met de afmeting middenrug-tot-nek + +Zoals eerder gezegd, gebruiken we voortaan de afmetingen van het schouderpunt voor verticale torso-afmetingen. Daardoor hebben we de oude maat voor middenrug-tot-nek niet meer nodig. + +Nu die afmeting verdwenen is, moet je mogelijk een andere afmeting toevoegen voor bepaalde patronen. + +### We meten schouderhelling op een nieuwe manier + +We hebben gemerkt dat mensen het moeilijk hadden met de manier waarop we hen vroegen op de [schouderhelling](/docs/measurements/shoulderslope) te meten, dus hebben we dat veranderd. + +De nieuwe methode levert een totaal ander getal op (dat eigenlijk hetzelfde weergeeft, namelijk hoe je schouder naar beneden afloopt) dus ook hier hebben we alle bestaande data moeten resetten. Met andere woorden: je zal je schouderhelling opnieuw moeten meten. + +## *Standaardmaten* voor patronen (beschikbaar zonder account) + +Voor een goed patroon heb je goede afmetingen nodig, en veel. Dat is wat we doen hier bij FreeSewing. En wanneer er iets misgaat met onze patronen, is het vaak omdat er iets misgaat met het opnemen van die maten. + +Jammer genoeg bestaat daar geen magische oplossing voor. Als je iets op maat wilt hebben, dan moet je vertrekken vanuit accurate afmetingen. + +Dat verhoogt de drempel voor mensen die onze site nog niet goed kennen en eens willen rondsnuffelen. + +> *Ooooeeeh, gratis patronen, fijn* 😍 *Wacht, ik moet eerst een account aanmaken?* 🤔 *En al die maten opnemen?* 😬 *Dat ziet eruit als een hoop werk.* + +Begrijpelijk. + +Bovendien hebben onze regelmatige bezoekers gevraagd of het niet mogelijk was om een patroon te bekijken en er wat mee te spelen zonder dat ze daarvoor eerst een hele lijst afmetingen moesten ingeven. + +Dus – __tromgeroffel__ – dat is voortaan niet meer nodig. We bieden al onze patronen voortaan aan in *standaardmaten*. Je hoeft dus geen afmetingen meer op te nemen om de patronen te testen. Je hoeft zelfs geen account meer te maken of in te loggen. Geen account vereist, gewoon een patroon kiezen, een maat aantikken, en je bent er klaar voor. + +Patronen op maat zijn uiteraard *ons ding* en dat blijft ook zo. Maar we hopen dat meer mensen de weg vinden naar FreeSewing nu de drempel om te beginnen wat lager ligt. + +### Wat zijn eigenlijk 'standaard'maten? + +Het lastigste aan de hele oefening met standaardmaten? Uitvissen wat nu eigenlijk 'standaard' is. We took a stab at it, and if you're curious you can [check out our sizing table here](/docs/various/sizes/). + +Voor herenkleding gaat onze maattabel van 32 tot 50. Ze zijn allemaal gebaseerd op een standaardmaat 38 die we dan naar boven en naar beneden gegradeerd hebben. Voor dameskleding gaan onze maten van 28 tot 48. Ze zijn gebaseerd op een standaardmaat 34 en naar boven en naar beneden gegradeerd. + + + +Als je niet zeker bent wat die getallen betekenen: dat is de halsomtrek in centimeter. + + + +We hebben ons best gedaan om een inclusieve maattabel op te stellen, en dit is onze beste poging om een logisch systeem te bedenken. Hou er alsjeblieft rekening mee dat dit niet onze core business is. We horen graag wat jij te zeggen hebt over deze maattabellen en we staan open voor aanpassingen en suggesties. Maar uiteindelijk is het ons doel om jou een patroon te bezorgen dat geschetst is op basis van jouw maten. Deze standaardmaten zijn gewoon het lokaas 🤫 + + +## En ook nog: allerlei andere dingen + +Hup, ga een beetje rondklikken, want we hebben ook nog een heleboel andere dingen veranderd. + +If you bump into any problems or have questions, as always [our chat room is the place to get in touch](https://discord.freesewing.org/). + +En als je het aanstaat wat we hier doen, dan is dit misschien een goed moment om je vrienden te vertellen over FreeSewing. Want nu kunnen ze komen kijken zonder een account te moeten maken. + +P.S.: We hebben een handige [share-pagina](/share/) die je daarvoor kan gebruiken. + + + diff --git a/markdown/org/blog/bye-2020/de.md b/markdown/org/blog/bye-2020/de.md new file mode 100644 index 00000000000..428c72f6edb --- /dev/null +++ b/markdown/org/blog/bye-2020/de.md @@ -0,0 +1,55 @@ +--- +author: "joostdecock" +caption: "A photo by Paulo Silva shows an empty Times Square in New York during the COVID pandemic" +date: "2021-01-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ffacb5c6384f250ad7cd3cb50b5ed4fdeff33ae6-1920x1280.jpg" +intro: "Aren't we all glad 2020 is over?" +title: "The year 2020 was something alright [Nicht übersetzt]" +--- + + + + +Aren't we all glad 2020 is over? + +Realistically, at least some of you, or your loved ones, got caught in the absolute gut-punch that is the COVID-19 pandemic. +Either indirectly through lost income or other practical concerns, or directly by battling the virus itself. + +I can only offer my sympathy, and the belief that things will get better. +So hang in there, and let me briefly take your mind of things by sharing some good news against the bleak backdrop of the annus horribilis that 2020 turned out to be. + +##### The face mask tsunami + +FreeSewing found itself — absolutely unexpected I might add — under the glaring spotlight of international media this year. +A tidal wave of attention rolled over us, and while the peak lasted only a good month, the repercussions and long tail of these events have shaped our entire year. + +It all started in February when COVID-19 was starting to rear its ugly head in Europe and the supplies of personal protective equipment (PPE) started dwindling. It seemed that face masks were going to be a big factor in trying to slow down the spread of this disease, but they were getting harder to come by every day. + +So on February 28th, after some design and experimentation, we [published our face mask pattern on freesewing.org](/blog/florence-face-mask/). Three weeks later, we followed up with [a one-page PDF that people could share and adapt](/blog/facemask-frenzy/). + +We did not really want to be in the center of this, we just wanted to help people make masks. But when [Forbes ran an editorial calling on people to help out with the healthcare workers PPE shortage](https://www.forbes.com/sites/tjmccue/2020/03/20/calling-all-people-who-sew-and-make-you-can-help-solve-2020-n95-type-mask-shortage/), we suddenly found ourselves in the middle of a gigantic spotlight. The article prominently featured FreeSewing, and linked to [our blog post](/blog/facemask-frenzy). + +At that time, there were few patterns available for face masks, and soon enough a long list of other publications started running links to our pattern and website. When I found [the instruction video that I made for the pattern staring back at me on the website of the New York Times](https://www.nytimes.com/2020/03/31/opinion/coronavirus-n95-mask.html), it was a veritable oh-crap moment. Sure enough, in the month following the Forbes publication, a million people descended on freesewing.org. + +The sudden jump in visitors and users (not to mention patrons) made it clear that I am a bottleneck of the project, and so in the latter half of the year we've set out to [try and remedy that with some community building](/blog/a-call-for-help/). On one hand it's slow going, but on the other hand if I look at how vibrant the FreeSewing community is today, it almost beggars belief that we did all of this throughout 2020. We now have regular [contributor calls](/community/calls/), and [our chat rooms are never empty](https://discord.freesewing.org/). + +I hope to continue to fade into the background and let other people carry some of the torches. Not because I don't want to work on this anymore, but because I want to grow FreeSewing beyond what I can do on my own. + +##### Black Lives Matter +Since this is a look at 2020, I also want to pause and acknowledge the **Black Lives Matter** movement and the ongoing problem of systemic racism. It is an area where my background and genetic material makes me ill-equipped to take a leading role, so here too I rely on our community for guidance. + +We are also expanding our efforts to provide patterns that work for all body types, and I am particularly proud of how many of our users come to us because our patterns help them project the gender of their choice. + +##### We helped more people than ever this year +On the practical side of things, I have extended our book year with a couple of weeks so that going forward, we will just follow the calendar years. With a couple of hours left in this year, FreeSewing's revenue for 2020 clocks in at **10.736,82 euro**. That makes 2020 and absolute bumper year, and it's more than all previous years combined (2015: € 256.65, 2016: € 473.50, 2017: € 673.14, 2018: € 3162.14, 2019: € 4109.38). + +As always, all of FreeSewing's revenue -- the entire 10.736,82 euro -- [goes to Doctors Without Borders](/docs/various/pledge/). + +I am truly grateful for your continued support and contributions. I feel like in a very small way, we are able to apply some balm to the hurt that seems at times omnipresent in the world. + +Thank you so much, and stay safe + +love +joost + + diff --git a/markdown/org/blog/bye-2020/en.md b/markdown/org/blog/bye-2020/en.md new file mode 100644 index 00000000000..c4875852977 --- /dev/null +++ b/markdown/org/blog/bye-2020/en.md @@ -0,0 +1,55 @@ +--- +author: "joostdecock" +caption: "A photo by Paulo Silva shows an empty Times Square in New York during the COVID pandemic" +date: "2021-01-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ffacb5c6384f250ad7cd3cb50b5ed4fdeff33ae6-1920x1280.jpg" +intro: "Aren't we all glad 2020 is over?" +title: "The year 2020 was something alright" +--- + + + + +Aren't we all glad 2020 is over? + +Realistically, at least some of you, or your loved ones, got caught in the absolute gut-punch that is the COVID-19 pandemic. +Either indirectly through lost income or other practical concerns, or directly by battling the virus itself. + +I can only offer my sympathy, and the belief that things will get better. +So hang in there, and let me briefly take your mind of things by sharing some good news against the bleak backdrop of the annus horribilis that 2020 turned out to be. + +##### The face mask tsunami + +FreeSewing found itself — absolutely unexpected I might add — under the glaring spotlight of international media this year. +A tidal wave of attention rolled over us, and while the peak lasted only a good month, the repercussions and long tail of these events have shaped our entire year. + +It all started in February when COVID-19 was starting to rear its ugly head in Europe and the supplies of personal protective equipment (PPE) started dwindling. It seemed that face masks were going to be a big factor in trying to slow down the spread of this disease, but they were getting harder to come by every day. + +So on February 28th, after some design and experimentation, we [published our face mask pattern on freesewing.org](/blog/florence-face-mask/). Three weeks later, we followed up with [a one-page PDF that people could share and adapt](/blog/facemask-frenzy/). + +We did not really want to be in the center of this, we just wanted to help people make masks. But when [Forbes ran an editorial calling on people to help out with the healthcare workers PPE shortage](https://www.forbes.com/sites/tjmccue/2020/03/20/calling-all-people-who-sew-and-make-you-can-help-solve-2020-n95-type-mask-shortage/), we suddenly found ourselves in the middle of a gigantic spotlight. The article prominently featured FreeSewing, and linked to [our blog post](/blog/facemask-frenzy). + +At that time, there were few patterns available for face masks, and soon enough a long list of other publications started running links to our pattern and website. When I found [the instruction video that I made for the pattern staring back at me on the website of the New York Times](https://www.nytimes.com/2020/03/31/opinion/coronavirus-n95-mask.html), it was a veritable oh-crap moment. Sure enough, in the month following the Forbes publication, a million people descended on freesewing.org. + +The sudden jump in visitors and users (not to mention patrons) made it clear that I am a bottleneck of the project, and so in the latter half of the year we've set out to [try and remedy that with some community building](/blog/a-call-for-help/). On one hand it's slow going, but on the other hand if I look at how vibrant the FreeSewing community is today, it almost beggars belief that we did all of this throughout 2020. We now have regular [contributor calls](/community/calls/), and [our chat rooms are never empty](https://discord.freesewing.org/). + +I hope to continue to fade into the background and let other people carry some of the torches. Not because I don't want to work on this anymore, but because I want to grow FreeSewing beyond what I can do on my own. + +##### Black Lives Matter +Since this is a look at 2020, I also want to pause and acknowledge the **Black Lives Matter** movement and the ongoing problem of systemic racism. It is an area where my background and genetic material makes me ill-equipped to take a leading role, so here too I rely on our community for guidance. + +We are also expanding our efforts to provide patterns that work for all body types, and I am particularly proud of how many of our users come to us because our patterns help them project the gender of their choice. + +##### We helped more people than ever this year +On the practical side of things, I have extended our book year with a couple of weeks so that going forward, we will just follow the calendar years. With a couple of hours left in this year, FreeSewing's revenue for 2020 clocks in at **10.736,82 euro**. That makes 2020 and absolute bumper year, and it's more than all previous years combined (2015: € 256.65, 2016: € 473.50, 2017: € 673.14, 2018: € 3162.14, 2019: € 4109.38). + +As always, all of FreeSewing's revenue -- the entire 10.736,82 euro -- [goes to Doctors Without Borders](/docs/various/pledge/). + +I am truly grateful for your continued support and contributions. I feel like in a very small way, we are able to apply some balm to the hurt that seems at times omnipresent in the world. + +Thank you so much, and stay safe + +love +joost + + diff --git a/markdown/org/blog/bye-2020/es.md b/markdown/org/blog/bye-2020/es.md new file mode 100644 index 00000000000..dee2320c47b --- /dev/null +++ b/markdown/org/blog/bye-2020/es.md @@ -0,0 +1,55 @@ +--- +author: "joostdecock" +caption: "A photo by Paulo Silva shows an empty Times Square in New York during the COVID pandemic" +date: "2021-01-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ffacb5c6384f250ad7cd3cb50b5ed4fdeff33ae6-1920x1280.jpg" +intro: "Aren't we all glad 2020 is over?" +title: "The year 2020 was something alright [No traducido]" +--- + + + + +Aren't we all glad 2020 is over? + +Realistically, at least some of you, or your loved ones, got caught in the absolute gut-punch that is the COVID-19 pandemic. +Either indirectly through lost income or other practical concerns, or directly by battling the virus itself. + +I can only offer my sympathy, and the belief that things will get better. +So hang in there, and let me briefly take your mind of things by sharing some good news against the bleak backdrop of the annus horribilis that 2020 turned out to be. + +##### The face mask tsunami + +FreeSewing found itself — absolutely unexpected I might add — under the glaring spotlight of international media this year. +A tidal wave of attention rolled over us, and while the peak lasted only a good month, the repercussions and long tail of these events have shaped our entire year. + +It all started in February when COVID-19 was starting to rear its ugly head in Europe and the supplies of personal protective equipment (PPE) started dwindling. It seemed that face masks were going to be a big factor in trying to slow down the spread of this disease, but they were getting harder to come by every day. + +So on February 28th, after some design and experimentation, we [published our face mask pattern on freesewing.org](/blog/florence-face-mask/). Three weeks later, we followed up with [a one-page PDF that people could share and adapt](/blog/facemask-frenzy/). + +We did not really want to be in the center of this, we just wanted to help people make masks. But when [Forbes ran an editorial calling on people to help out with the healthcare workers PPE shortage](https://www.forbes.com/sites/tjmccue/2020/03/20/calling-all-people-who-sew-and-make-you-can-help-solve-2020-n95-type-mask-shortage/), we suddenly found ourselves in the middle of a gigantic spotlight. The article prominently featured FreeSewing, and linked to [our blog post](/blog/facemask-frenzy). + +At that time, there were few patterns available for face masks, and soon enough a long list of other publications started running links to our pattern and website. When I found [the instruction video that I made for the pattern staring back at me on the website of the New York Times](https://www.nytimes.com/2020/03/31/opinion/coronavirus-n95-mask.html), it was a veritable oh-crap moment. Sure enough, in the month following the Forbes publication, a million people descended on freesewing.org. + +The sudden jump in visitors and users (not to mention patrons) made it clear that I am a bottleneck of the project, and so in the latter half of the year we've set out to [try and remedy that with some community building](/blog/a-call-for-help/). On one hand it's slow going, but on the other hand if I look at how vibrant the FreeSewing community is today, it almost beggars belief that we did all of this throughout 2020. We now have regular [contributor calls](/community/calls/), and [our chat rooms are never empty](https://discord.freesewing.org/). + +I hope to continue to fade into the background and let other people carry some of the torches. Not because I don't want to work on this anymore, but because I want to grow FreeSewing beyond what I can do on my own. + +##### Black Lives Matter +Since this is a look at 2020, I also want to pause and acknowledge the **Black Lives Matter** movement and the ongoing problem of systemic racism. It is an area where my background and genetic material makes me ill-equipped to take a leading role, so here too I rely on our community for guidance. + +We are also expanding our efforts to provide patterns that work for all body types, and I am particularly proud of how many of our users come to us because our patterns help them project the gender of their choice. + +##### We helped more people than ever this year +On the practical side of things, I have extended our book year with a couple of weeks so that going forward, we will just follow the calendar years. With a couple of hours left in this year, FreeSewing's revenue for 2020 clocks in at **10.736,82 euro**. That makes 2020 and absolute bumper year, and it's more than all previous years combined (2015: € 256.65, 2016: € 473.50, 2017: € 673.14, 2018: € 3162.14, 2019: € 4109.38). + +As always, all of FreeSewing's revenue -- the entire 10.736,82 euro -- [goes to Doctors Without Borders](/docs/various/pledge/). + +I am truly grateful for your continued support and contributions. I feel like in a very small way, we are able to apply some balm to the hurt that seems at times omnipresent in the world. + +Thank you so much, and stay safe + +love +joost + + diff --git a/markdown/org/blog/bye-2020/fr.md b/markdown/org/blog/bye-2020/fr.md new file mode 100644 index 00000000000..50330b6d3d6 --- /dev/null +++ b/markdown/org/blog/bye-2020/fr.md @@ -0,0 +1,50 @@ +--- +author: "joostdecock" +caption: "Une photo de Paulo Silva montrant un Times Square vide à New York pendant la pandémie COVID" +date: "2021-01-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ffacb5c6384f250ad7cd3cb50b5ed4fdeff33ae6-1920x1280.jpg" +intro: "Ne sommes-nous pas tous heureux que 2020 soit finie ?" +title: "L'année 2020 était quelque chose de tout à fait normal" +--- + +Ne sommes-nous pas tous heureux que 2020 soit finie ? + +D’un point de vue réaliste, au moins certains d’entre vous, ou vos proches, ont été pris au piège absolu de la pandémie COVID-19. Soit indirectement par la perte de revenus ou d'autres préoccupations pratiques, soit directement par la lutte contre le virus lui-même. + +Je ne peux qu'exprimer ma sympathie et la conviction que les choses vont aller vers du mieux. Alors accrochez-vous, et permettez-moi de vous rappeler brièvement les choses en partageant quelques bonnes nouvelles dans le sombre contexte de l'annus horribilis que 2020 s'est avéré être. + +##### Le tsunami du masque + +FreeSewing s’est retrouvé — j’ajouterais de façon absolument inattendue — sous les projecteurs des médias internationaux cette année. Une vague de marée d'attention s'est abattue sur nous, et bien que ce pic n'ait duré qu'un bon mois, les répercussions et la longue queue de ces événements ont façonné notre année entière. + +Tout a commencé en février lorsque la COVID-19 commençait à pointer sa tête hideuse en Europe et que les stocks d’équipement de protection individuelle (EPI) commençaient à diminuer. Il semblait que les masques allaient être un élément important pour essayer de ralentir la propagation de cette maladie, mais ils devenaient de plus en plus difficiles à trouver de jour en jour. + +Donc, le 28 février, après plusieurs essais de conception et expérimentations, nous [avons publié notre modèle de masque sur freesewing.org](/blog/florence-face-mask/). Trois semaines plus tard, nous avons enchaîné avec [un PDF d'une page que les gens pouvaient partager et adapter](/blog/facemask-frenzy/). + +Nous ne voulions pas vraiment être au centre de cela, nous voulions simplement aider les gens à faire des masques. Mais quand [Forbes a rédigé un éditorial appelant les gens à aider avec la pénurie d'EPI pour le personnel de santé](https://www.forbes.com/sites/tjmccue/2020/03/20/calling-all-people-who-sew-and-make-you-can-help-solve-2020-n95-type-mask-shortage/), nous nous sommes soudainement retrouvés au beau milieu d'un gigantesque projecteur. L'article a mis en vedette FreeSewing, et a donné le lien vers [notre article de blog](/blog/facemask-frenzy). + +À cette époque, il y avait peu de modèles disponibles pour les masques, et assez tôt une longue liste d'autres publications ont commencé à donner des liens vers notre modèle et notre site Web. Quand j'ai découvert [la vidéo d'instruction que j'ai faite pour le patron qui me met en lumière sur le site du New York Times](https://www.nytimes.com/2020/03/31/opinion/coronavirus-n95-mask.html), C’était un véritable moment de dingue. Bien sûr, dans le mois qui a suivi la publication de Forbes, un million de personnes sont venues sur freesewing.org. + +L'augmentation soudaine des visiteurs et des utilisateurs (sans parler des clients) a clairement montré que je suis un goulot d'étranglement du projet, et donc dans la seconde moitié de l'année, nous nous sommes mis à [essayer d'y remédier avec un peu de construction de communauté](/blog/a-call-for-help/). D'un côté, c'est lent, mais d'un autre côté, si je regarde à quel point la communauté de FreeSewing est vibrante aujourd'hui, Il est presque dur de croire que nous avons fait tout cela tout durant l'année 2020. We now have regular [contributor calls](/community/calls/), and [our chat rooms are never empty](https://discord.freesewing.org/). + +J'espère continuer à m'éclipser dans le fond et laisser d'autres personnes porter quelques flambeaux. Non pas parce que je ne veux plus travailler là-dessus, mais parce que je veux faire grandir FreeSewing au-delà de ce que je peux faire seul. + +##### Black Lives Matter +Vu que c'est un coup d'œil à 2020, Je veux également mettre en pause et revenir sur le mouvement **Black Lives Matter** et le problème actuel du racisme systémique. C'est un domaine où mes antécédents et le matériel génétique me rendent mal équipé pour jouer un rôle prépondérant, donc ici aussi je compte sur notre communauté pour obtenir des conseils. + +Nous élargissons également nos efforts pour fournir des modèles qui fonctionnent pour tous les types de corps, et je suis particulièrement fier du nombre d'utilisateurs qui nous rejoignent parce que nos pratiques les aident à se projeter sur le genre de leur choix. + +##### Nous avons aidé plus de personnes que jamais cette année +Sur le plan pratique, j'ai prolongé notre revue de l'année de deux semaines pour aller de l'avant. nous allons juste suivre les années calendaires. Avec quelques heures restantes cette année, les revenus de FreeSewing pour 2020 sont à **10.736,82 euros**. Cela fait de 2020 une année de records absolus, et c'est plus que toutes les années précédentes combinées (2015: 256.65€, 2016: 473,50€, 2017 : 673,14€, 2018 : 3162,14€, 2019 : 4109,38€). + +Comme toujours, tous les revenus de FreeSewing -- l'ensemble de 10,736,82 euros -- [vont à Médecins Sans Frontières](/docs/various/pledge/). + +Je vous suis vraiment reconnaissant de votre soutien et de vos contributions continues. J'ai le sentiment, dans une très petite mesure, que nous sommes en mesure d'apporter un peu de soulagement à la souffrance qui semble parfois omniprésente dans le monde. + +Merci beaucoup, et soyez prudent + +love +joost + + + diff --git a/markdown/org/blog/bye-2020/nl.md b/markdown/org/blog/bye-2020/nl.md new file mode 100644 index 00000000000..26a8356e641 --- /dev/null +++ b/markdown/org/blog/bye-2020/nl.md @@ -0,0 +1,55 @@ +--- +author: "joostdecock" +caption: "A photo by Paulo Silva shows an empty Times Square in New York during the COVID pandemic" +date: "2021-01-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ffacb5c6384f250ad7cd3cb50b5ed4fdeff33ae6-1920x1280.jpg" +intro: "Aren't we all glad 2020 is over?" +title: "The year 2020 was something alright [Niet vertaald]" +--- + + + + +Aren't we all glad 2020 is over? + +Realistically, at least some of you, or your loved ones, got caught in the absolute gut-punch that is the COVID-19 pandemic. +Either indirectly through lost income or other practical concerns, or directly by battling the virus itself. + +I can only offer my sympathy, and the belief that things will get better. +So hang in there, and let me briefly take your mind of things by sharing some good news against the bleak backdrop of the annus horribilis that 2020 turned out to be. + +##### The face mask tsunami + +FreeSewing found itself — absolutely unexpected I might add — under the glaring spotlight of international media this year. +A tidal wave of attention rolled over us, and while the peak lasted only a good month, the repercussions and long tail of these events have shaped our entire year. + +It all started in February when COVID-19 was starting to rear its ugly head in Europe and the supplies of personal protective equipment (PPE) started dwindling. It seemed that face masks were going to be a big factor in trying to slow down the spread of this disease, but they were getting harder to come by every day. + +So on February 28th, after some design and experimentation, we [published our face mask pattern on freesewing.org](/blog/florence-face-mask/). Three weeks later, we followed up with [a one-page PDF that people could share and adapt](/blog/facemask-frenzy/). + +We did not really want to be in the center of this, we just wanted to help people make masks. But when [Forbes ran an editorial calling on people to help out with the healthcare workers PPE shortage](https://www.forbes.com/sites/tjmccue/2020/03/20/calling-all-people-who-sew-and-make-you-can-help-solve-2020-n95-type-mask-shortage/), we suddenly found ourselves in the middle of a gigantic spotlight. The article prominently featured FreeSewing, and linked to [our blog post](/blog/facemask-frenzy). + +At that time, there were few patterns available for face masks, and soon enough a long list of other publications started running links to our pattern and website. When I found [the instruction video that I made for the pattern staring back at me on the website of the New York Times](https://www.nytimes.com/2020/03/31/opinion/coronavirus-n95-mask.html), it was a veritable oh-crap moment. Sure enough, in the month following the Forbes publication, a million people descended on freesewing.org. + +The sudden jump in visitors and users (not to mention patrons) made it clear that I am a bottleneck of the project, and so in the latter half of the year we've set out to [try and remedy that with some community building](/blog/a-call-for-help/). On one hand it's slow going, but on the other hand if I look at how vibrant the FreeSewing community is today, it almost beggars belief that we did all of this throughout 2020. We now have regular [contributor calls](/community/calls/), and [our chat rooms are never empty](https://discord.freesewing.org/). + +I hope to continue to fade into the background and let other people carry some of the torches. Not because I don't want to work on this anymore, but because I want to grow FreeSewing beyond what I can do on my own. + +##### Black Lives Matter +Since this is a look at 2020, I also want to pause and acknowledge the **Black Lives Matter** movement and the ongoing problem of systemic racism. It is an area where my background and genetic material makes me ill-equipped to take a leading role, so here too I rely on our community for guidance. + +We are also expanding our efforts to provide patterns that work for all body types, and I am particularly proud of how many of our users come to us because our patterns help them project the gender of their choice. + +##### We helped more people than ever this year +On the practical side of things, I have extended our book year with a couple of weeks so that going forward, we will just follow the calendar years. With a couple of hours left in this year, FreeSewing's revenue for 2020 clocks in at **10.736,82 euro**. That makes 2020 and absolute bumper year, and it's more than all previous years combined (2015: € 256.65, 2016: € 473.50, 2017: € 673.14, 2018: € 3162.14, 2019: € 4109.38). + +As always, all of FreeSewing's revenue -- the entire 10.736,82 euro -- [goes to Doctors Without Borders](/docs/various/pledge/). + +I am truly grateful for your continued support and contributions. I feel like in a very small way, we are able to apply some balm to the hurt that seems at times omnipresent in the world. + +Thank you so much, and stay safe + +love +joost + + diff --git a/markdown/org/blog/calling-all-patrons/de.md b/markdown/org/blog/calling-all-patrons/de.md new file mode 100644 index 00000000000..6e75a0be1c1 --- /dev/null +++ b/markdown/org/blog/calling-all-patrons/de.md @@ -0,0 +1,128 @@ +--- +author: "joostdecock" +caption: "Wir bauen ein Fundament aus treuen Unterstützern, um eine nachhaltige Zukunft für freesewing.org, unseren Code, unsere Schnittmuster und unsere Community zu sichern." +date: "2017-12-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/84e39d762790744f10fe17bcb971f99e98550299-2000x1334.jpg" +intro: "Jedes Jahr, an diesem Tag, schreibe ich über die Ereignisse der letzten 12 Monate, und schaue nach vorne, was Sie im kommenden Jahr erwarten können." +title: "Aufruf an alle Gönner; Schließen Sie sich unserem Fundament treuer Unterstützer an." +--- + + +Jedes Jahr, an diesem Tag, schreibe ich über die Ereignisse der letzten 12 Monate, und schaue nach vorne, was Sie im kommenden Jahr erwarten können. + +Dieses Jahr ist es nicht anders, aber Junge, ich habe viel zu bereden. + +## 2017: Das Jahr in dem FreeSewing geboren wurde + +Während FreeSewing im Jahr 2016 konzipiert wurde - das ist der Zeitpunkt, an dem ich anfing, daran zu arbeiten - war 2017 das Jahr, in dem es das Licht der Welt erblickte. + +Core FreeSewing v1.0.0 [wurde im März dieses Jahres](/blog/announcing-freesewing/) veröffentlicht. Für die meisten Menschen ging dieses Ereignis unter dem Radar durch. Eine Open-Source-Plattform für Nähmuster nach Maß? Was macht dieses Ding eigentlich? + +Viel, wie es sich herausstellt. Etwas, das offensichtlicher geworden ist, seit der [die Veröffentlichung von freesewing.org](/blog/open-for-business/) Ende August. + +![Bild aus dem ursprünglichen Ankündigungs-Blog-Beitrag](open.jpg) + +Am Weihnachtstag werden (erst) vier Monate verstrichen sein, seit dieser Veröffentlichung. Doch in dieser Zeit haben sich **2735 Benutzer** bei uns angemeldet, für die wir **1522 Entwürfe**und **2359 Modelle** speichern. + +Wir starteten mit 11 Schnittmustern und haben inzwischen 4 weitere hinzugefügt, was die aktuelle Summe der verfügbaren Schnittmuster auf 15 erhöht. Die Hälfte dieser neuen Schnitte wurden von der Gemeinschaft beigesteuert, was besonders vielversprechend ist. + +Ja, es ist noch früh. Aber ich denke, es ist sicher zu sagen, dass die Entscheidung, makemypattern.com als Open-Source-Projekt neu zu erfinden, die richtige Entscheidung war. + +Da wir gerade davon sprechen. + +## MakeMyPattern.com gibt es nicht mehr +Kurz vor der Veröffentlichung dieses Blog-Posts habe ich den Stecker gezogen bei [makemypattern.com](https://makemypattern.com/). + +Du kannst versuchen, diesen Link zu besuchen, aber du wirst nur hier hinten landen. + +MakeMyPattern.com sah das Licht des Tages im Jahr 2012. Es hat seitdem eine Reihe von Iterationen durchlaufen, und heute wird es schließlich durch freesewing.org ersetzt. + +![War es ein M? Ein Buch? Ein Vogel? Brüste? Wir wissen vielleicht nie](mmp.png) + +Es lief gut, und ich denke, dass es für jedes Projekt ein guter Weg ist, wenn es von etwas Besserem, zu dem es einen inspiriert hat, kannibalisiert wird. + +## Lass uns über Geld reden +Wie jedes Jahr an diesem Tag, habe ich alle eingegangenen Spenden auf das Konto von [Ärtze ohne Grenzen](http://www.msf.org/) überwiesen. + +In diesem Jahr kamen wir auf **673,14€**, diese Summe habe ich überwiesen. + +> Warum sollten wir Ihnen Geld in geben, wenn Sie es einfach weggeben? + +Ich habe auch verstanden, dass die Leute eine Reihe von Fragen dazu haben. *Warum machen Sie das?* und *Warum sollten wir Ihnen Geld in geben, wenn Sie einfach weiterspenden?* + +Diese Fragen haben in letzter Zeit zu einer gewissen Selbstbeobachtung geführt. Was ich gelernt habe ist, dass es nicht einfach ist, über Geld zu sprechen. Es ist auch nicht einfach, Dinge, von denen man fast instinktiv weiß, dass sie richtig sind, in Worte zu fassen. + +Aber ich wollte völlig transparent sein, was vor sich geht, also habe ich mich bemüht, über diese Dinge auf [unserer Versprechenseite](/about/pledge) zu schreiben. Und ich kopiere sie hierher, wörtlich: + +> ##### Noblesse oblige +> +> Sie gehen wahrscheinlich davon aus, dass wir Geld bitten, um die Server zu betreiben. Aber das stimmt nicht genau. +> +> Ich weiß nicht, ob Sie mit dem Satz *noblesse oblige* vertraut sind, aber es bedeutet im Wesentlichen, dass Privilegien Verantwortung bedeutet. +> +> Ich bin privilegiert, und damit habe ich Verantwortung. Ich habe das große Glück, in Westeuropa geboren zu sein, einen guten Job und ein Dach über dem Kopf zu haben. +> +> Könnte ich das Geld gebrauchen? Ja, ich könnte es. Brauche ich das Geld? Nein ich bin nicht darauf angewiesen. +> +> ##### Der Wert Ihrer Unterstützung +> +> Das Hauptrisiko für Freesewing ist das gleiche wie bei jedem Open-Source-Projekt da draußen: Maintainer-Burnout. +> +> Obwohl ich FreeSewing nicht mehr alleine stemme — und ich kann nicht genug betonen, wie sehr ich die Arbeit aller Mitwirkenden schätze - macht mich das nicht immun gegen Gefühle von der Sorte: *Warum zum Teufel tu ich mir das an?* +> +> Wenn Menschen Gönner werden (oder spenden), geben sie mehr als nur Geld. Für mich ist der Hauptwert die Botschaft, die sie mir und anderen Menschen, die daran arbeiten, vermitteln. Und diese Botschaft ist: *Hey, Ihr machst eine sinnvolle Sache. Macht weiter mit der guten Arbeit*. +> +> ##### Der Wert Ihres Geldes +> +> Es geht nicht nur um das Geld. Aber das bedeutet nicht, dass das Geld nicht wichtig ist. Ganz im Gegenteil. +> +> Geld zu sammeln, indem ich etwas tue, das ich liebe, und es dann an die Wohltätigkeitsorganisation weiterzugeben, erlaubt es mir, nachts zu schlafen. +> +> Ich könnte freiwillig in einer Suppenküche arbeiten oder unterprivilegierten Kindern das Nähen beibringen. Aber stattdessen arbeite ich an FreeSewing. +> +> Darum gehen alle Einnahmen und Spenden, die ich durch FreeSewing erziele an eine gemeinnützige Organisation. So macht dieses Projekt nicht nur Spaß, sondern ist auch sozial verantwortlich. Und ich brauche das, um mich davon zu überzeugen, dass es in Ordnung ist, meine ganze Zeit damit zu verbringen, denn am Ende des Jahres kann ich einen Scheck an Leute schreiben, die ihn viel mehr brauchen als ich. +> +> ##### Gemeinnützigkeit ist nicht sexy +> +> Hier ist der heikle Teil: Die Menschen spenden weniger, wenn sie wissen, dass das Geld an Wohltätigkeitsarbeit geht. Ich wünschte, das wäre nicht der Fall, aber es so. +> +> Deshalb erwähne ich es nicht ausdrücklich auf unserer Gönnerseite, die so aufgemacht ist als würden Sie eine Geschäftsseite sehen. +> +> Ja, alles ist kostenlos, und das Geld geht nicht wirklich zur Bezahlung der Serverrechnungen (weil ich sie aus den oben genannten Gründen aus eigener Tasche bezahle). Aber das bedeutet nicht, dass diese Beiträge nicht entscheidend für das Wohlergehen des Projekts sind, oder zumindest sein Betreuer (das wäre ich). + +Hast du bemerkt, dass ich im obigen Text unsere Gönnerseite erwähnt habe? Das liegt daran, dass ich heute eine Reihe von Änderungen vorgenommen habe. + +Nachdem ich mir die Zeit genommen habe, über die finanzielle Seite der Dinge nachzudenken, habe ich erkannt, dass es ein wichtiger Faktor für das Wohlergehen dieses Projekts ist. Ich glaube auch, dass Spenden - obwohl motivierend und geschätzt - nicht der beste Weg sind, um dies zu erreichen. + +Deshalb nennen wir seit heute alle Gönner. + +## Werde ein Gönner von FreeSewing + +Um eine nachhaltige Zukunft für freesewing.org, unseren Code, unsere Muster und unsere Community zu gewährleisten, müssen wir ein Fundament aus treuen Unterstützern aufbauen. Gönner, die uns in unserer Kernarbeit unterstützen: Entwicklung einer Open-Source-Plattform für maßgeschneiderte Schnittmuster. + +![Wir haben drei Stufen der Gönnerschaft](patron-medals.jpg) + +Wir haben verschiedene Stufen der Gönnerschaft, jede mit ihren eigenen Vergünstigungen. Sie können uns für nur 2€ unterstützen, und es dauert nur eine Minute. + +> Wir ändern nicht die Art der Website. All unsere Schnittmuster und unser Code bleiben frei und opensource. + +Wir ändern nicht die Art der Website. All unsere Schnittmuster und unser Code bleiben frei und opensource. Was wir ändern, ist die Art und Weise, wie wir fundraising betreiben. Von einem System gelegentlicher Spenden in eine Gemeinschaft fürsorglicher Gönner. Wenn Sie jemand sind, der sich darum kümmert, dann schauen Sie sich an, [was wir zu bieten haben](/patrons/join). + +Ich glaube aufrichtig, dass wir hier etwas Gutes tun. Wenn Sie auch so denken, dann bitte ich Sie, die Gönnerschaft auszuwählen, die Sie vermögen, damit wir noch viele weitere Kapitel in diesem Buch schreiben können. + +> ### Werden Sie noch heute ein Gönner +> +> #### Sie sind bereits mit einem Betrag von 2€ dabei, und es dauert nur eine Minute. +> +> [Erfahren Sie mehr](/patrons/join) + +Vielen Dank und ich wünsche Ihnen ein gutes Wahr. + +joost + +PS: Es wäre eine Schande, wenn dort Leute draußen bereit sind, uns zu unterstützen, die aber nicht wissen wie. +Vielleicht könnten Sie also [dieses Bild](patrons-ig.png) auf sozialen Medien teilen? + +![Sharing is Caring!](patrons-ig.png) + + diff --git a/markdown/org/blog/calling-all-patrons/en.md b/markdown/org/blog/calling-all-patrons/en.md new file mode 100644 index 00000000000..71e61294ea3 --- /dev/null +++ b/markdown/org/blog/calling-all-patrons/en.md @@ -0,0 +1,161 @@ +--- +author: "joostdecock" +caption: "We are building a bedrock of loyal supporters to ensure a sustainable future for freesewing.org, our code, our patterns, and our community." +date: "2017-12-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/84e39d762790744f10fe17bcb971f99e98550299-2000x1334.jpg" +intro: "Calling all Patrons; Join our bedrock of loyal supporters." +title: "Calling all Patrons; Join our bedrock of loyal supporters." +--- + +Every year, on this day, I write about what happened in the previous 12 months, +and look ahead at what you can expect in the year ahead. + +This year is no different, but boy do I have a lot to talk about. + +## 2017: the year freesewing was born + +While freesewing was conceived in 2016 -- that's when I started working on it -- +2017 was the year it saw the light of day. + +Freesewing core v1.0.0 [was released in March this year](/blog/announcing-freesewing/). +For most people, that event passed under the radar. An open source platform for +made-to-measure sewing patterns? What does this thing actually do? + +A lot, as it turns out. Something that's become more obvious since +[the release of freesewing.org](/blog/open-for-business/) at the end of August. + +![Image from the original announcement blog post](https://posts.freesewing.org/uploads/open_e799153fa2.jpg) + +On Christmas day, it will (only) have been four months since this release. +Yet in that time, we've signed up **2735 users** +for whom we host **1522 drafts**, and **2359 models**. + +We launched with 11 patterns, and have since added 4, +bringing the current total to 15. Half of those new patterns are a community effort, +which is particularly promising. + +Yes, it's still early days. But I think it's safe to say that the decision to +reinvent makemypattern.com as an open source project was the right call. + +Speaking of which. + +## MakeMyPattern.com is no more +Shortly before publishing this blog post, I've pulled the plug on +[makemypattern.com](https://makemypattern.com/). + +You can try to visit that link, but you'll only end up back here. + +MakeMyPattern.com saw the light of day in 2012. It went through a number +of iterations since, and today is finally superseded by freesewing.org. + +![Was it an M? A book? A bird? Boobs? We may never know](https://posts.freesewing.org/uploads/mmp_27886c8346.png) + +We had a good run, and I feel that for any project, it's a good way to go +when you get cannibalized by something better that you inspired. + +## Let's talk money +Like every year on this day, I've transferred all donations into the +account of +[Médecins Sans Frontières/Doctors Without Borders](http://www.msf.org/). + +This year we came in at **673.14€**, so that's what I've transferred. + +> Why should we give you money in the +> first place if you're just going to give it away? + +I've also come to understand that people have a bunch of questions about this. +Like *Why are you doing this?* and *Why should we give you money in the +first place if you're just going to give it away?* + +These questions have led to some soul-searching recently. +What I've learned is that it's not easy to talk about money. Nor is it +easy to put in words things that you know to be right, almost instinctively. + +But I wanted to be completely transparent about what's going on, so I made +the effort to write about these things on [our pledge page](/about/pledge). +And I'm copying them here verbatim: + +> ##### Noblesse oblige +> +> You probably assume that we ask for money to keep the servers running. But that’s not exactly true. +> +> I don’t know if you’re familiar with the phrase *noblesse oblige* but it essentially means that privilege entails responsibility. +> +> I am privileged, and thus I have responsibilities. I am very fortunate to have been born in Western Europe, have a good job, and a roof over my head. +> +> Could I use the money? Yes I could. +> Do I need the money? No I don’t. +> +> ##### The value of your support +> +> The main risk to Freesewing is the same as any open source project out there: maintainer burnout. +> +> While I no longer carry Freesewing alone — and I can’t stress enough how much I value the work of all contributors — that doesn’t make me immune to feelings of *Why the fuck am I doing this?* +> +> When people become Patrons (or donate), they give more than money. To me, the main value is the message they send to me and other people working on this. And that message is: *Hey, you’re doing a worthwhile thing. Keep up the good work*. +> +> ##### The value of your money +> +> It is not just about the money. But that doesn’t mean the money is not important. Much to the contrary. +> +> Raising money by doing something I love and then passing it on to charity allows me to sleep at night. +> +> I could volunteer at a soup kitchen, or teach underprivileged children how to sew. But instead I’m working on Freesewing. +> +> Which is why all the money raised through freesewing goes to charity. It makes this project not only fun to do, but also socially responsible. And I need that to convince myself that yes, it’s OK to spend all my time doing this, because at the end of the year, I get to write a check to people who need it so much more. +> +> ##### Charity is not sexy +> +> Here’s the tricky part: People donate less once they know the money goes to charity in the end. I wish it wasn’t the case, but it is. +> +> So I’m not explicitly mentioning it on our Patrons page, which is presented like you would see on a business site. +> +> Yes, everything is free, and the money doesn’t actually go to paying the server bills (because I choose to pay them out of my pocket for reasons outlined above). But that doesn’t mean that these contributions are not crucial to the well-being of the project, or at the very least its maintainer (that would be me). + +Did you notice that in the text above I mentioned our Patrons page? That is because I've rolled out a bunch of changes today. + +Having taken the time to reflect on the money side of things, I've realized +that it's an important factor in the well-being of this project. +I also believe that donations -- while motivating and appreciated -- are not the best way to go about this. + +So, as of today, we are calling all Patrons. + +## Become a Patron of Freesewing + +To ensure a sustainable future for freesewing.org, our code, our patterns, and our community, +we need to build a bedrock of loyal supporters. +Patrons who support us in our core work; Developing an open source platform for made-to-measure sewing patterns. + +![We have three tiers of Patronage](https://posts.freesewing.org/uploads/patron_medals_2160e69d77.jpg) + +We have different tiers of Patronage, each with their own perks. You can support us for as +little as 2€, and it only takes a minute. + +> We are not changing the nature of the site. All patterns, and all our code, will remain free. + +We are not changing the nature of the site. +All patterns, and all our code, will remain free. +What we are changing is the way we raise funds. From a system of impulsive donations +to a community of caring Patrons. If you are someone who cares, then +[check out what we have to offer](/patrons/join). + +I sincerely believe we are doing a worthwhile thing here. If you feel that way too, +then I ask you to pledge whatever you can so that we can write many more chapters in this book. + +> ### Become a Patron today +> #### You can sign up for as little as 2€, and it only takes a minute. +>[Find out more](/patrons/join) + +Thank you, and have a great year. + +joost + +PS: It would be a shame if there's people out there willing to support us who don't know about this. +So perhaps you could share [this image](patrons-ig.png) on social media? + +![Sharing is caring!](https://posts.freesewing.org/uploads/patrons_ig_45e11fe270.png) + + + + + diff --git a/markdown/org/blog/calling-all-patrons/es.md b/markdown/org/blog/calling-all-patrons/es.md new file mode 100644 index 00000000000..4b71c4f541c --- /dev/null +++ b/markdown/org/blog/calling-all-patrons/es.md @@ -0,0 +1,161 @@ +--- +author: "joostdecock" +caption: "We are building a bedrock of loyal supporters to ensure a sustainable future for freesewing.org, our code, our patterns, and our community." +date: "2017-12-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/84e39d762790744f10fe17bcb971f99e98550299-2000x1334.jpg" +intro: "Calling all Patrons; Join our bedrock of loyal supporters. [No traducido]" +title: "Calling all Patrons; Join our bedrock of loyal supporters. [No traducido]" +--- + +Every year, on this day, I write about what happened in the previous 12 months, +and look ahead at what you can expect in the year ahead. + +This year is no different, but boy do I have a lot to talk about. + +## 2017: the year freesewing was born + +While freesewing was conceived in 2016 -- that's when I started working on it -- +2017 was the year it saw the light of day. + +Freesewing core v1.0.0 [was released in March this year](/blog/announcing-freesewing/). +For most people, that event passed under the radar. An open source platform for +made-to-measure sewing patterns? What does this thing actually do? + +A lot, as it turns out. Something that's become more obvious since +[the release of freesewing.org](/blog/open-for-business/) at the end of August. + +![Image from the original announcement blog post](https://posts.freesewing.org/uploads/open_e799153fa2.jpg) + +On Christmas day, it will (only) have been four months since this release. +Yet in that time, we've signed up **2735 users** +for whom we host **1522 drafts**, and **2359 models**. + +We launched with 11 patterns, and have since added 4, +bringing the current total to 15. Half of those new patterns are a community effort, +which is particularly promising. + +Yes, it's still early days. But I think it's safe to say that the decision to +reinvent makemypattern.com as an open source project was the right call. + +Speaking of which. + +## MakeMyPattern.com is no more +Shortly before publishing this blog post, I've pulled the plug on +[makemypattern.com](https://makemypattern.com/). + +You can try to visit that link, but you'll only end up back here. + +MakeMyPattern.com saw the light of day in 2012. It went through a number +of iterations since, and today is finally superseded by freesewing.org. + +![Was it an M? A book? A bird? Boobs? We may never know](https://posts.freesewing.org/uploads/mmp_27886c8346.png) + +We had a good run, and I feel that for any project, it's a good way to go +when you get cannibalized by something better that you inspired. + +## Let's talk money +Like every year on this day, I've transferred all donations into the +account of +[Médecins Sans Frontières/Doctors Without Borders](http://www.msf.org/). + +This year we came in at **673.14€**, so that's what I've transferred. + +> Why should we give you money in the +> first place if you're just going to give it away? + +I've also come to understand that people have a bunch of questions about this. +Like *Why are you doing this?* and *Why should we give you money in the +first place if you're just going to give it away?* + +These questions have led to some soul-searching recently. +What I've learned is that it's not easy to talk about money. Nor is it +easy to put in words things that you know to be right, almost instinctively. + +But I wanted to be completely transparent about what's going on, so I made +the effort to write about these things on [our pledge page](/about/pledge). +And I'm copying them here verbatim: + +> ##### Noblesse oblige +> +> You probably assume that we ask for money to keep the servers running. But that’s not exactly true. +> +> I don’t know if you’re familiar with the phrase *noblesse oblige* but it essentially means that privilege entails responsibility. +> +> I am privileged, and thus I have responsibilities. I am very fortunate to have been born in Western Europe, have a good job, and a roof over my head. +> +> Could I use the money? Yes I could. +> Do I need the money? No I don’t. +> +> ##### The value of your support +> +> The main risk to Freesewing is the same as any open source project out there: maintainer burnout. +> +> While I no longer carry Freesewing alone — and I can’t stress enough how much I value the work of all contributors — that doesn’t make me immune to feelings of *Why the fuck am I doing this?* +> +> When people become Patrons (or donate), they give more than money. To me, the main value is the message they send to me and other people working on this. And that message is: *Hey, you’re doing a worthwhile thing. Keep up the good work*. +> +> ##### The value of your money +> +> It is not just about the money. But that doesn’t mean the money is not important. Much to the contrary. +> +> Raising money by doing something I love and then passing it on to charity allows me to sleep at night. +> +> I could volunteer at a soup kitchen, or teach underprivileged children how to sew. But instead I’m working on Freesewing. +> +> Which is why all the money raised through freesewing goes to charity. It makes this project not only fun to do, but also socially responsible. And I need that to convince myself that yes, it’s OK to spend all my time doing this, because at the end of the year, I get to write a check to people who need it so much more. +> +> ##### Charity is not sexy +> +> Here’s the tricky part: People donate less once they know the money goes to charity in the end. I wish it wasn’t the case, but it is. +> +> So I’m not explicitly mentioning it on our Patrons page, which is presented like you would see on a business site. +> +> Yes, everything is free, and the money doesn’t actually go to paying the server bills (because I choose to pay them out of my pocket for reasons outlined above). But that doesn’t mean that these contributions are not crucial to the well-being of the project, or at the very least its maintainer (that would be me). + +Did you notice that in the text above I mentioned our Patrons page? That is because I've rolled out a bunch of changes today. + +Having taken the time to reflect on the money side of things, I've realized +that it's an important factor in the well-being of this project. +I also believe that donations -- while motivating and appreciated -- are not the best way to go about this. + +So, as of today, we are calling all Patrons. + +## Become a Patron of Freesewing + +To ensure a sustainable future for freesewing.org, our code, our patterns, and our community, +we need to build a bedrock of loyal supporters. +Patrons who support us in our core work; Developing an open source platform for made-to-measure sewing patterns. + +![We have three tiers of Patronage](https://posts.freesewing.org/uploads/patron_medals_2160e69d77.jpg) + +We have different tiers of Patronage, each with their own perks. You can support us for as +little as 2€, and it only takes a minute. + +> We are not changing the nature of the site. All patterns, and all our code, will remain free. + +We are not changing the nature of the site. +All patterns, and all our code, will remain free. +What we are changing is the way we raise funds. From a system of impulsive donations +to a community of caring Patrons. If you are someone who cares, then +[check out what we have to offer](/patrons/join). + +I sincerely believe we are doing a worthwhile thing here. If you feel that way too, +then I ask you to pledge whatever you can so that we can write many more chapters in this book. + +> ### Become a Patron today +> #### You can sign up for as little as 2€, and it only takes a minute. +>[Find out more](/patrons/join) + +Thank you, and have a great year. + +joost + +PS: It would be a shame if there's people out there willing to support us who don't know about this. +So perhaps you could share [this image](patrons-ig.png) on social media? + +![Sharing is caring!](https://posts.freesewing.org/uploads/patrons_ig_45e11fe270.png) + + + + + diff --git a/markdown/org/blog/calling-all-patrons/fr.md b/markdown/org/blog/calling-all-patrons/fr.md new file mode 100644 index 00000000000..57b12c293c1 --- /dev/null +++ b/markdown/org/blog/calling-all-patrons/fr.md @@ -0,0 +1,128 @@ +--- +author: "joostdecock" +caption: "Nous construisons un cercle de soutiens fidèles pour assurer un avenir durable à freesewing.org, à notre code, à nos modèles et à notre communauté." +date: "2017-12-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/84e39d762790744f10fe17bcb971f99e98550299-2000x1334.jpg" +intro: "Chaque année, à ce jour, j'écris sur ce qui s'est passé au cours des 12 mois précédents, et annonce ce à quoi vous pouvez vous attendre pour l'année à venir." +title: "Appel aux mécènes ; rejoignez notre socle de soutiens fidèles." +--- + + +Chaque année, à ce jour, j'écris sur ce qui s'est passé au cours des 12 mois précédents, et annonce ce à quoi vous pouvez vous attendre pour l'année à venir. + +Cette année n'est pas différente, mais purée, que j'ai beaucoup à dire. + +## 2017: année de naissance de freesewing. org + +Bien que le freesewing ait été conçu en 2016 -- c'est là que j'ai commencé à travailler dessus -- 2017 a été l'année où il a vu le jour. + +La version 1.0.0 de freesewing [a été publiée en mars de cette année](/blog/announcing-freesewing/). Pour la plupart des gens, cet événement est passé sous le radar. Une plateforme open source pour les patrons de couture sur mesure ? Que fait-elle réellement ? + +Beaucoup de choses en l’occurrence. Quelque chose devient plus évident depuis [la sortie de freesewing.org](/blog/open-for-business/) à la fin du mois d'août. + +![Image du blog de l'annonce originale](open.jpg) + +Le jour de Noël, il se sera écoulé (seulement) quatre mois depuis cette sortie. Pourtant dans ce délai, nous avons accueillis **2735 utilisateurs** pour qui nous hébergeons **1522 brouillons** et **2359 modèles**. + +Nous avons démarré avec 11 patrons et en avons depuis ajouté 4, portant le total actuel à 15. La moitié de ces nouveaux patrons proviennent d'un effort communautaire, qui est particulièrement prometteur. + +Oui, nous n'en sommes qu'aux débuts. Mais je pense qu'il est sage de dire que la décision de réinventer makemypattern.com en tant que projet open source était le bon choix. + +A ce propos. + +## MakeMyPattern.com n'est plus +Peu de temps avant de publier cet article de blog, j'ai débranché [makemypattern.com](https://makemypattern.com/). + +Vous pouvez essayer de visiter ce lien, mais vous finirez par revenir ici. + +MakeMyPattern.com a vu le jour en 2012. Il est passé par un certain nombre d'itérations depuis, et aujourd'hui est finalement remplacé par freesewing.org. + +![Était-ce un M ? Un livre ? Un oiseau ? Des seins ? Nous ne le saurons peut-être jamais](mmp.png) + +Nous en avons terminé, et je pense que pour n'importe quel projet, c'est une bonne façon de faire quand vous vous faites cannibaliser par quelque chose qui vous inspire davantage. + +## Parlons d'argent +Comme chaque année jusqu'à ce jour, j'ai transféré tous les dons sur le compte de [Médecins Sans Frontières](http://www.msf.org/). + +Cette année, nous sommes arrivés à **673.14€**, donc c'est ce que j'ai reversé. + +> Pourquoi devrions-nous vous donner de l'argent si c'est pour que vous le donniez ensuite ? + +J'ai compris que les gens ont un tas de questions à ce sujet. Telles que *Pouquoi faites-vous cela ?* et *Pourquoi devrions-nous vous donner de l'argent pour que vous le donniez ensuite ?* + +Ces questions ont récemment fait l'objet d'un examen de conscience. Ce que j'ai appris, c'est qu'il n'est pas facile de parler d'argent. Il n'est pas non plus facile de mettre des mots sur ce que vous estimez être juste, instinctivement. + +Mais je voulais être complètement transparent sur ce qui se passe, alors j'ai fait l'effort d'écrire à ce sujet sur [la page de nos engagement](/about/pledge). Et je les copie ici mot pour mot : + +> ##### Noblesse oblige +> +> Vous supposez probablement que nous demandons de l'argent pour faire tourner les serveurs. Mais ce n'est pas tout à fait vrai. +> +> Je ne sais pas si vous êtes familier avec l'expression *noblesse oblige* mais cela signifie essentiellement que le privilège implique une responsabilité. +> +> Je suis privilégié, et j'ai donc des responsabilités. J'ai la chance d'être né en Europe occidentale, d'avoir un bon travail et un toit au-dessus de ma tête. +> +> Pourrais-je utiliser cet argent ? Oui. Ai-je besoin de cet argent ? Non. +> +> ##### La valeur de votre soutien +> +> Le risque principal pour FreeSewing est le même que n'importe quel projet open source : le burnout du responsable. +> +> Bien que je ne supporte plus FreeSewing seul — et je ne saurais trop insister sur la valeur du travail de tous les contributeurs — cela ne m'immunise pas contre le sentiments de *Pourquoi donc est-ce que je fais tout ça ?* +> +> Quand les gens deviennent des mécènes (ou font des dons), ils donnent plus que de l'argent. Pour moi, la principale valeur est le message qu'ils m'envoient, ainsi qu'aux autres personnes qui travaillent sur ce projet. Et ce message est: *Hey, vous faites quelque chose qui en vaut la peine. Continuez à bien travailler*. +> +> ##### La valeur de votre argent +> +> Il ne s'agit pas seulement d'argent. Mais cela ne signifie pas que l'argent n'est pas important. Bien au contraire. +> +> Gagner de l'argent en faisant quelque chose que j'aime et ensuite le transmettre aux œuvres caritatives me permet de dormir la nuit. +> +> Je pourrais faire du bénévolat aux resto du cœur ou apprendre aux enfants défavorisés à coudre. Mais à la place, je travaille sur FreeSewing. +> +> C'est pourquoi tout l'argent récolté par FreeSewing va aux bonnes œuvres. Il rend ce projet non seulement amusant à faire, mais aussi socialement responsable. Et j'ai besoin de ça pour me convaincre que oui, il est bon de passer tout mon temps à le faire, parce qu'à la fin de l'année, cela me permet d'envoyer un chèque à des gens qui en ont vraiment besoin. +> +> ##### La charité n'est pas sexy +> +> Voici la partie délicate : les gens donnent moins une fois qu'ils savent que l'argent est finalement reversé aux bonnes œuvres. Je voudrais que ce ne soit pas le cas, mais ça l'est. +> +> Je ne le mentionne donc pas explicitement sur notre page de Mécènes, qui est présentée comme vous pourrez le voir, comme un site marchand. +> +> Oui, tout est gratuit et l'argent ne va pas vraiment payer les factures des serveurs (parce que je choisis de les payer de ma poche pour les raisons décrites ci-dessus). Mais cela ne signifie pas que ces contributions ne sont pas cruciales pour le bien-être du projet, ou du moins son responsable (c'est-à-dire moi). + +Avez-vous remarqué que dans le texte ci-dessus, j'ai mentionné notre page de Mécènes ? C'est parce que j'ai déployé un tas de changements aujourd'hui. + +Avoir pris le temps de me pencher sur l'aspect monétaire des choses m'a permis de réaliser que c'est un facteur important dans le bien-être de ce projet. Je crois aussi que les dons – bien que motivants et les appréciés – ne sont pas la meilleure façon d’y parvenir. + +Donc, dès aujourd'hui, nous en appelons à tous les Mécènes. + +## Devenez un Mécène de Freesewing + +Pour assurer un avenir durable à freesewing.org, à notre code, à nos patrons et à notre communauté, nous avons besoin de construire un socle de soutiens fidèles. Les mécènes qui nous soutiennent sont au cœur de notre travail, en développant une plateforme open source pour les patrons de couture sur-mesure. + +![Nous avons trois niveaux de Mécénat](patron-medals.jpg) + +Nous avons différents niveaux de Mécénat, chacun avec ses propres avantages. Vous pouvez nous soutenir à partir de 2€, et cela ne prend qu'une minute. + +> Nous ne changeons pas la nature du site. Tous les patrons, et tout notre code, resteront gratuits. + +Nous ne changeons pas la nature du site. Tous les patrons, et tout notre code, resteront gratuits. Ce que nous changeons, c'est la manière dont nous collectons des fonds. D'un système de dons spontanés à une communauté de mécènes attentionnés. Si vous êtes quelqu'un d'intéressé, alors [regardez ce que nous avons à offrir](/patrons/join). + +Je crois sincèrement que nous faisons une chose qui vaut la peine ici. Si vous vous avez le même sentiment vous aussi, alors je vous demande d'engager tout ce que vous pouvez pour que nous puissions écrire beaucoup plus de chapitres dans ce livre. + +> ### Devenez mécène aujourd'hui +> +> #### Vous pouvez nous soutenir à partir de 2€, et cela ne prend qu'une minute. +> +> [En savoir plus](/patrons/join) + +Merci et bonne année. + +joost + +PS: Il serait dommage qu'il y ait des gens prêts à nous soutenir qui ne soient pas au courant. +Alors, peut-être pourriez-vous partager [cette image](patrons-ig.png) sur les réseaux sociaux ? + +![Partager, c'est soutenir !](patrons-ig.png) + + diff --git a/markdown/org/blog/calling-all-patrons/nl.md b/markdown/org/blog/calling-all-patrons/nl.md new file mode 100644 index 00000000000..d93d774274d --- /dev/null +++ b/markdown/org/blog/calling-all-patrons/nl.md @@ -0,0 +1,128 @@ +--- +author: "joostdecock" +caption: "We bouwen een trouwe supportersgroep om mee te werken aan een duurzame toekomst voor FreeSewing.org, onze code, onze patronen en onze community." +date: "2017-12-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/84e39d762790744f10fe17bcb971f99e98550299-2000x1334.jpg" +intro: "Elk jaar schrijf ik op deze dag neer wat er gebeurd is in de afgelopen twaalf maanden en kijk ik vooruit naar wat je in het komende jaar kan verwachten." +title: "Oproep aan alle Patrons: sluit je aan bij onze trouwe supportersgroep" +--- + + +Elk jaar schrijf ik op deze dag neer wat er gebeurd is in de afgelopen twaalf maanden en kijk ik vooruit naar wat je in het komende jaar kan verwachten. + +Dit jaar is niet anders, maar wauw, wat heb ik veel te vertellen! + +## 2017: het geboortejaar van FreeSewing + +FreeSewing werd verwekt in 2016 – dat is het jaar waarin ik eraan begon te werken – maar in 2017 kwam het echt ter wereld. + +In maart van dit jaar [werd de FreeSewing core v1.0.0 gelanceerd](/blog/announcing-freesewing/). Voor de meeste mensen bleef dat onopgemerkt. Een open-sourceplatform voor naaipatronen op maat? Wat doet dat ding eigenlijk? + +Veel, zo blijkt. Dat is steeds duidelijker geworden sinds [de lancering van FreeSewing.org](/blog/open-for-business/) eind augustus. + +![Afbeelding van de oorspronkelijke blogpost met de aankondiging](open.jpg) + +Op kerstdag is het (nog maar) vier maanden geleden sinds die lancering. Maar in die tijd hebben we **2735 gebruikers** geregistreerd voor wie we **1522 patroonversies** en **2359 modellen** hosten. + +Bij de lancering hadden we elf patronen. Sindsdien hebben we er nog vier toegevoegd, zodat het totaal nu op vijftien staat. De helft van die nieuwe patronen komen uit onze community, wat ik bijzonder veelbelovend vind. + +Ja, het is nog vroeg. Maar ik durf gerust te zeggen dat het een goede beslissing was om MakeMyPattern.com heruit te vinden als een open-sourceproject. + +En nu we het er toch over hebben. + +## MakeMyPattern.com bestaat niet meer +Kort voor de publicatie van deze blogpost heb ik de stekker uit [makemypattern.com](https://makemypattern.com/) getrokken. + +Probeer gerust om op de link te klikken, maar je komt toch terug hier terecht. + +MakeMyPattern.com zag het levenslicht in 2012. Daarna heeft het een paar transformaties meegemaakt. En nu is het dus vervangen en verbeterd met FreeSewing.org. + +![Was het een M? Een boek? Een vogel? Een stel borsten? We zullen het nooit weten](mmp.png) + +We hebben het goed gehad samen. En naar mijn gevoel is het voor elk project een mooi einde als je opgevreten wordt door iets dat beter is dan jij, en waar je zelf de inspiratie voor bent geweest. + +## En nu over geld +Net zoals elk jaar op deze dag, heb ik alle schenkingen doorgestort naar de rekening van [Artsen zonder grenzen](http://www.msf.org/). + +Dit jaar hebben we **673,14 euro** binnengekregen en dat is dus ook wat ik heb overgeschreven. + +> Waarom zouden we jou eigenlijk geld geven als je het toch maar weggeeft? + +Ik heb intussen begrepen dat mensen hier veel vragen bij hebben. Zoals *'waarom doe je dit?'* en *'waarom zouden we jou geld geven als je het toch maar weggeeft?'* + +Omwille van die vragen heb ik de laatste tijd diep nagedacht. Ik heb ontdekt dat het niet gemakkelijk is om over geld te praten. En het is al helemaal niet gemakkelijk om onder woorden te brengen wat je zelf, bijna instinctief, aanvoelt als juist. + +Maar ik wil volkomen transparant zijn over wat er hier gebeurt, dus ik heb mijn best gedaan om over dit onderwerp te schrijven op onze [Pledge-pagina](/about/pledge). En ik kopieer het hier letterlijk: + +> ##### Noblesse oblige +> +> Je veronderstelt waarschijnlijk dat we om geld vragen om de servers te laten draaien. Maar dat klopt niet helemaal. +> +> Ik weet niet of je al gehoord hebt van de uitdrukking *'noblesse oblige'*. Het komt erop neer dat privilege ook verantwoordelijkheid met zich meebrengt. +> +> Ik ben bevoorrecht, en dus heb ik verantwoordelijkheden. Ik heb het enorme geluk dat ik geboren ben in West-Europa, een goede job heb en een dak boven mijn hoofd. +> +> Zou ik het geld kunnen gebruiken? Ja, zeker. Heb ik het geld nodig? Nee, dat niet. +> +> ##### De waarde van jullie steun +> +> Het grootste risico van FreeSewing is hetzelfde als voor elk open-sourceproject: dat we opgebrand raken door het te onderhouden. +> +> Ik draag FreeSewing niet meer alleen – en ik kan niet genoeg benadrukken hoe waardevol het werk van onze bijdragers is – maar dat betekent niet dat ik immuun ben voor gevoelens zoals *'waarom houd ik me hier in godsnaam mee bezig?'* +> +> Wanneer mensen Patrons worden (of doneren), geven ze meer dan geld. Voor mij is de belangrijkste waarde de boodschap die ze geven aan mij en de andere mensen die hieraan meewerken. En die boodschap is: *'Hé, het is de moeite waard wat je hier doet. Blijf vooral doorgaan.'* +> +> ##### De waarde van jullie geld +> +> Het gaat niet alleen over het geld. Maar dat betekent niet dat geld niet belangrijk is. Integendeel. +> +> Geld inzamelen door iets te doen wat ik graag doe, en het dan doorgeven aan een goed doel, is wat mij op twee oren doet slapen. +> +> Ik zou als vrijwilliger kunnen werken in de voedselbedeling, of kinderen uit minder gegoede gezinnen leren naaien. Maar in plaats daarvan werk ik aan FreeSewing. +> +> En daarom gaat dus al het geld dat FreeSewing opbrengt, naar een goed doel. Het maakt dit project niet alleen leuk, maar ook maatschappelijk verantwoord. En dat heb ik nodig om mezelf te overtuigen dat het oké is dat ik hier al mijn tijd in stop. Want aan het einde van het jaar mag ik een bedrag doorgeven aan mensen die het zoveel harder nodig hebben. +> +> ##### Goede doelen zijn niet sexy +> +> Hier wringt het schoentje: mensen doneren minder als ze weten dat het geld uiteindelijk naar een goed doel gaat. Ik wou dat het niet zo was, maar ja. +> +> Daarom vermeld ik het niet expliciet op onze Patrons-pagina, die eruitziet zoals je zou verwachten op een zakelijke site. +> +> Ja, alles is gratis, en het geld gaat niet echt naar de rekeningen voor de server (omdat ik ervoor kies om die zelf te betalen, om de redenen die ik hierboven uitleg). Maar dat betekent niet dat deze bijdrages geen cruciaal deel uitmaken van het welzijn van dit project, of minstens degene die het onderhoudt (mij dus). + +Heb je gemerkt dat ik hierboven verwijs naar onze Patrons-pagina? Dat komt omdat ik vandaag een hoop veranderingen heb uitgerold. + +Nadat ik de tijd had genomen om na te denken over de financiële kant van de zaak, heb ik beseft dat het een belangrijke factor is in de goede werking van dit project. Ik geloof ook dat schenkingen – hoewel ze motiverend zijn en ze erg op prijs worden gesteld – niet de beste manier zijn om hiermee om te gaan. + +Dus doen we vanaf vandaag een oproep voor Patrons. + +## Word een FreeSewing-Patron + +Om een duurzame toekomst te verzekeren voor FreeSewing.org, onze code, onze patronen en onze gemeenschap, moeten we bouwen aan een stevige basis van trouwe supporters. Patrons die onze kerntaak ondersteunen: een open-sourceplatform ontwikkelen voor naaipatronen op maat. + +![Er bestaan drie niveaus voor Patrons](patron-medals.jpg) + +We hebben verschillende niveaus voor Patrons, elk met zijn eigen voordelen. Je kan ons al ondersteunen vanaf 2 euro, en het duurt maar een minuutje. + +> We veranderen niets aan de aard van de site. Alle patronen en al onze code blijven gratis. + +We veranderen niets aan de aard van de site. Alle patronen en al onze code blijven gratis. Wat we veranderen is de manier waarop we fondsen inzamelen. We gaan van een systeem van impulsieve schenkingen naar een community van Patrons die met het project begaan zijn. Als jij zo iemand bent, [ga dan zeker kijken wat we je te bieden hebben](/patrons/join). + +Ik geloof echt dat we hier iets waardevols aan het doen zijn. Als jij er ook zo over denkt, wil ik je vragen om te geven wat je kan zodat we nog veel meer hoofdstukken in dit boek kunnen schrijven. + +> ### Word vandaag een Patron +> +> #### Je kan al intekenen vanaf 2 euro en het is maar een minuutje werk. +> +> [Ontdek meer](/patrons/join) + +Bedankt, en maak er een topjaar van. + +joost + +PS Het zou jammer zijn als er mensen zijn die ons wel zouden willen steunen, maar dit project niet kennen. +Dus misschien kan je [deze afbeelding](patrons-ig.png) delen op je sociale media? + +![Sharing is caring!](patrons-ig.png) + + diff --git a/markdown/org/blog/core-1-8-jaeger-across-back/de.md b/markdown/org/blog/core-1-8-jaeger-across-back/de.md new file mode 100644 index 00000000000..e2e6c50e1a7 --- /dev/null +++ b/markdown/org/blog/core-1-8-jaeger-across-back/de.md @@ -0,0 +1,64 @@ +--- +author: "joostdecock" +caption: "Diese Version übermitteln wir Ihnen aus Bangkok" +date: "2018-03-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/34ed654dcda9004e7c249b90256ad197469cc87e-1920x1277.webp" +intro: "Wir haben gerade den Button auf Core 1.8.0 gedrückt. Diesmal ist es eher ein kleineres Update, weil wir ein neues Schnittmuster haben, aber in diesem Fall gibt es zwei Gründe:" +title: "FreeSewing Core 1.8: Jeager-Sakko ist drin, die Rückenbreite ist raus" +--- + + +Wir haben gerade den *Release* Button auf Core 1.8.0 gedrückt. Diesmal ist es eher ein kleineres Update, weil wir ein neues Schnittmuster haben, aber in diesem Fall gibt es zwei Gründe: + + - Das[Jaeger-Sakko](/designs/jaeger) ist jetzt verfügbar + - Und wir haben uns von der *Rückenbreite* verabschiedet + +Lesen Sie weiter für die Details. + +## Ankündigung des Jäger-Sakko + +Für [meine Refasioner Einreichung im letzten Jahr](/blog/the-refashioners-2017/) habe ich ein Sakko-Muster entworfen, das ich ich eigentlich parallel zur Produktion des Sakkos publizieren wollt. Es lief jedoch nicht nach Plan, deshalb habe ich mir für die Publikation etwas mehr Zeit genommen. + +Wie sich herausstellt, bedeutet es, wenn ich sage * dass ein bisschen mehr Zeit brauchte* es am Ende 6,5 Monate sind, also verzeihen Sie mir bitte die Verzögerung, aber hier ist es, [das Jaeger-Sakko](/designs/jaeger). + +![Beachten Sie, dass ich damals in meinem Beitrag über den Blake Blazer gesprochen habe, aber ich habe ihn seitdem umbenannt, weil Jaeger-Sakko einfach cooler ist](jaeger.jpg) + +### Das Jaeger-Sport-Sakko ist keine Alliteration + +Jaeger ist ein Sakko im sportlichen Look. In der Form eines einreihigen Sakko mit zwei Knöpfen und aufgesetzten Taschen. + +Mit anderen Worten, es ist ein Kleidungsstück, das üblicherweise auf Jeans oder anderen Hosen getragen wird und nicht als Teil eines Anzuges. + +### Optionen in Hülle und Fülle + +Jaeger verfügt über 38 Optionen, so dass Sie *viel* an diesem Schnittmuster ändern können. + +Aber keine Sorge, es gibt auch vernünftige Standardwerte, so dass Sie genauso gut alle diese Einstellungsmöglichkeiten ignorieren können. + +## Das Mass Rückenbreite gibt es nicht + +Apropos vernünftige Vorgaben: Jaeger ist nicht das Einzige, was an Freewing Core 1.8.0, das heute erhältlich ist, neu ist. + +Wir haben auch das Mass *Rückenbreite * abgeschafft. + +Die Rückenbreite hat bei unseren Anwendern für große Verwirrung gesorgt. Meistens, wenn jemand mit uns Kontakt aufnahm, weil sein Muster unrealistisch aussah, war eine unmögliches Rückenbreitenmass schuld. + +Die Wurzeln des Rückenbreitenmass gehen auf eine Zeit zurück, in der wir anstelle des *Schulter-zu-Schulter-*Mass, das wir jetzt verwenden, das *Schulterlänge-*Mass verwendet hatten. Dieses war auch Quelle einiger Verwirrung, also haben wir es zugunsten des *Schulter-zu-Schulter-* Mass eingestellt. + +Die Sache ist die, dass, wenn wir das *Schulter-zu-Schulter*Mass kennen, wir mit angemessener Genauigkeit das *Rückenbreitenmass*mit ausreichender Genauigkeit extrapolieren können. Also, anstatt Sie im die Angabe zu bitten, errechnen wir diese jetzt einfach. + +### Aber Sie vereinfachen das Muster zu sehr + +Dies ist nicht der Fall *dieses Schnittmuster kommt mit 38 Optionen*. Als ob dies nicht schon genug Einstellungsmöglichkeiten wären, setzen wir hier bei FreeSewing alles daran Ihnen möglich alle Regler zur Optimierung des Schnittes an die an die Hand zu geben. + +Das Ersetzen einer Messung durch einen errechneten Wert, der auf der Grundlage einer anderen Messung generiert wird, mag dem entgegengesetzt erscheinen, aber es besteht kein Grund zur Sorge. Wir haben dafür gesorgt, dass Sie sich immer noch und die Passform am Rücken kümmern können. + +Muster, die früher die die Rückenbreite als Mass erforderten, haben nun eine neue erweiterte Option: den *Rückenfaktor*. Es erlaubt Ihnen, die Berechnung Ihrer Rückenbreite zu optimieren, stellt aber sicher, dass diese innerhalb sinnvoller Parameter bleibt. + +![Der Rückenbreitenfaktor](acrossback.png) + +Wir tun dies in der Überzeugung, dass wir Fehler für den gelegentlichen Benutzer vermeiden, ohne Ihnen, den Schnittmuster-Optionsguru, in Ihren Möglichkeiten einzuschränken. + +Oder anders ausgedrückt, Sie können immer noch mit der Rückenbreite herumalbern, aber standardmäßig müssen Sie sich keine Gedanken mehr darüber machen. + + diff --git a/markdown/org/blog/core-1-8-jaeger-across-back/en.md b/markdown/org/blog/core-1-8-jaeger-across-back/en.md new file mode 100644 index 00000000000..e2647cb2607 --- /dev/null +++ b/markdown/org/blog/core-1-8-jaeger-across-back/en.md @@ -0,0 +1,68 @@ +--- +author: "joostdecock" +caption: "This release brought to you from Bangkok" +date: "2018-03-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/34ed654dcda9004e7c249b90256ad197469cc87e-1920x1277.webp" +intro: "We've just pushed the button on core 1.8.0. That bump in minor number is typically because we have a new pattern, but in this case, there's two reasons:" +title: "Freesewing core 1.8: Jaeger Jacket is in, across back measurement is out" +--- + + +We've just pushed the *release* button on core 1.8.0. That bump in minor number is typically because we have a new pattern, but in this case, there's two reasons: + + - The [Jaeger Jacket](/patterns/jaeger) is now available + - We've gotten rid of the *across back* measurement + +Read on for the details. + +## Announcing the Jaeger Jacket + +For [my refasioners entry last year](/blog/the-refashioners-2017/) I designed a jacket pattern that I intially wanted to release alongside my make. It didn't work out that way, and I asked for a bit more time to get the pattern out the door. + +Turns out that when I say *a bit more time* it means 6 and a half months, so please forgive me for the delay, but here it is, [the Jaeger Jacket](/designs/jaeger). + +![Note that in my post back then, I was talking about the Blake Blazer, but I've since renamed it because Jaeger Jacket is just cooler](https://posts.freesewing.org/uploads/jaeger_1cb91a3cd3.jpg) + + + +### Jaeger Sport Coat is not an alliteration + +Jaeger is a sport coat style of jacket. As in, a single-breasted jacket with a 2-button closure, and patch pockets. + +In other words, this is a garment that's typically worn on jeans or other trousers, and not as part of a suit. + +### Options galore + +Jaeger comes with 38 options, so you can change *a lot* about this pattern. + +No need to worry though, it also comes with sensible defaults, so you can just as well ignore all those choices. + +## The across back measurement is no more + +Speaking of sensible defaults, Jaeger is not the only new thing in freesewing core 1.8.0, which is out today. + +We've also gotten rid of the *across back* measurement. + +The across back measurement was cause of a great deal of confusion among our users. +More often than not, when someone contacted us because their pattern looked wonky, an unrealistic across back measurement was to blame. + +The roots of the across back measurement go back to a time when, instead of the *shoulder to shoulder* measurement we use now, we had the *shoulder length* measurement. +That one was also source of some confusion, so we phased it out in favour of the *shoulder to shoulder* measurement. + +The thing is that if we know the *shoulder to shoulder* measurement, we can guestimate with reasonable accuracy what the *across back* measurement will be. So, instead of asking you for it, we simply assume now. + +### But you're dumbing down the pattern + +In case the *this pattern comes with 38 options* bit above wasn't enough of a giveaway, we're pretty committed here at freesewing to give you all the knobs to tweak your drafts. + +Replacing a measurement with a value calculated based on another measurement may seem to go against that, but there's no need to worry. We've made sure you can still muck about with your across back. + +Patterns that used to require the *across back* measurement now have a new advanced option: the *across back factor*. It allows you to tweak how we calculate your across back measurement, but does make sure to keep it within boundaries that are sensible. + +![The across back factor option](https://posts.freesewing.org/uploads/acrossback_60791a4392.png) + + +As such, we feel we're preventing mistakes for the casual user, without taking away power from you, the pattern option guru. + +Or to put it differently, you can still muck about with your across back, but by default, you don't have to worry about it anymore. + diff --git a/markdown/org/blog/core-1-8-jaeger-across-back/es.md b/markdown/org/blog/core-1-8-jaeger-across-back/es.md new file mode 100644 index 00000000000..1d717dee24a --- /dev/null +++ b/markdown/org/blog/core-1-8-jaeger-across-back/es.md @@ -0,0 +1,68 @@ +--- +author: "joostdecock" +caption: "This release brought to you from Bangkok" +date: "2018-03-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/34ed654dcda9004e7c249b90256ad197469cc87e-1920x1277.webp" +intro: "We've just pushed the button on core 1.8.0. That bump in minor number is typically because we have a new pattern, but in this case, there's two reasons:" +title: "Freesewing core 1.8: Jaeger Jacket is in, across back measurement is out [No traducido]" +--- + + +We've just pushed the *release* button on core 1.8.0. That bump in minor number is typically because we have a new pattern, but in this case, there's two reasons: + + - The [Jaeger Jacket](/patterns/jaeger) is now available + - We've gotten rid of the *across back* measurement + +Read on for the details. + +## Announcing the Jaeger Jacket + +For [my refasioners entry last year](/blog/the-refashioners-2017/) I designed a jacket pattern that I intially wanted to release alongside my make. It didn't work out that way, and I asked for a bit more time to get the pattern out the door. + +Turns out that when I say *a bit more time* it means 6 and a half months, so please forgive me for the delay, but here it is, [the Jaeger Jacket](/designs/jaeger). + +![Note that in my post back then, I was talking about the Blake Blazer, but I've since renamed it because Jaeger Jacket is just cooler](https://posts.freesewing.org/uploads/jaeger_1cb91a3cd3.jpg) + + + +### Jaeger Sport Coat is not an alliteration + +Jaeger is a sport coat style of jacket. As in, a single-breasted jacket with a 2-button closure, and patch pockets. + +In other words, this is a garment that's typically worn on jeans or other trousers, and not as part of a suit. + +### Options galore + +Jaeger comes with 38 options, so you can change *a lot* about this pattern. + +No need to worry though, it also comes with sensible defaults, so you can just as well ignore all those choices. + +## The across back measurement is no more + +Speaking of sensible defaults, Jaeger is not the only new thing in freesewing core 1.8.0, which is out today. + +We've also gotten rid of the *across back* measurement. + +The across back measurement was cause of a great deal of confusion among our users. +More often than not, when someone contacted us because their pattern looked wonky, an unrealistic across back measurement was to blame. + +The roots of the across back measurement go back to a time when, instead of the *shoulder to shoulder* measurement we use now, we had the *shoulder length* measurement. +That one was also source of some confusion, so we phased it out in favour of the *shoulder to shoulder* measurement. + +The thing is that if we know the *shoulder to shoulder* measurement, we can guestimate with reasonable accuracy what the *across back* measurement will be. So, instead of asking you for it, we simply assume now. + +### But you're dumbing down the pattern + +In case the *this pattern comes with 38 options* bit above wasn't enough of a giveaway, we're pretty committed here at freesewing to give you all the knobs to tweak your drafts. + +Replacing a measurement with a value calculated based on another measurement may seem to go against that, but there's no need to worry. We've made sure you can still muck about with your across back. + +Patterns that used to require the *across back* measurement now have a new advanced option: the *across back factor*. It allows you to tweak how we calculate your across back measurement, but does make sure to keep it within boundaries that are sensible. + +![The across back factor option](https://posts.freesewing.org/uploads/acrossback_60791a4392.png) + + +As such, we feel we're preventing mistakes for the casual user, without taking away power from you, the pattern option guru. + +Or to put it differently, you can still muck about with your across back, but by default, you don't have to worry about it anymore. + diff --git a/markdown/org/blog/core-1-8-jaeger-across-back/fr.md b/markdown/org/blog/core-1-8-jaeger-across-back/fr.md new file mode 100644 index 00000000000..f6c93d6b6f2 --- /dev/null +++ b/markdown/org/blog/core-1-8-jaeger-across-back/fr.md @@ -0,0 +1,68 @@ +--- +author: "joostdecock" +caption: "This release brought to you from Bangkok" +date: "2018-03-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/34ed654dcda9004e7c249b90256ad197469cc87e-1920x1277.webp" +intro: "We've just pushed the button on core 1.8.0. That bump in minor number is typically because we have a new pattern, but in this case, there's two reasons:" +title: "Freesewing core 1.8: Jaeger Jacket is in, across back measurement is out [Non traduit]" +--- + + +We've just pushed the *release* button on core 1.8.0. That bump in minor number is typically because we have a new pattern, but in this case, there's two reasons: + + - The [Jaeger Jacket](/patterns/jaeger) is now available + - We've gotten rid of the *across back* measurement + +Read on for the details. + +## Announcing the Jaeger Jacket + +For [my refasioners entry last year](/blog/the-refashioners-2017/) I designed a jacket pattern that I intially wanted to release alongside my make. It didn't work out that way, and I asked for a bit more time to get the pattern out the door. + +Turns out that when I say *a bit more time* it means 6 and a half months, so please forgive me for the delay, but here it is, [the Jaeger Jacket](/designs/jaeger). + +![Note that in my post back then, I was talking about the Blake Blazer, but I've since renamed it because Jaeger Jacket is just cooler](https://posts.freesewing.org/uploads/jaeger_1cb91a3cd3.jpg) + + + +### Jaeger Sport Coat is not an alliteration + +Jaeger is a sport coat style of jacket. As in, a single-breasted jacket with a 2-button closure, and patch pockets. + +In other words, this is a garment that's typically worn on jeans or other trousers, and not as part of a suit. + +### Options galore + +Jaeger comes with 38 options, so you can change *a lot* about this pattern. + +No need to worry though, it also comes with sensible defaults, so you can just as well ignore all those choices. + +## The across back measurement is no more + +Speaking of sensible defaults, Jaeger is not the only new thing in freesewing core 1.8.0, which is out today. + +We've also gotten rid of the *across back* measurement. + +The across back measurement was cause of a great deal of confusion among our users. +More often than not, when someone contacted us because their pattern looked wonky, an unrealistic across back measurement was to blame. + +The roots of the across back measurement go back to a time when, instead of the *shoulder to shoulder* measurement we use now, we had the *shoulder length* measurement. +That one was also source of some confusion, so we phased it out in favour of the *shoulder to shoulder* measurement. + +The thing is that if we know the *shoulder to shoulder* measurement, we can guestimate with reasonable accuracy what the *across back* measurement will be. So, instead of asking you for it, we simply assume now. + +### But you're dumbing down the pattern + +In case the *this pattern comes with 38 options* bit above wasn't enough of a giveaway, we're pretty committed here at freesewing to give you all the knobs to tweak your drafts. + +Replacing a measurement with a value calculated based on another measurement may seem to go against that, but there's no need to worry. We've made sure you can still muck about with your across back. + +Patterns that used to require the *across back* measurement now have a new advanced option: the *across back factor*. It allows you to tweak how we calculate your across back measurement, but does make sure to keep it within boundaries that are sensible. + +![The across back factor option](https://posts.freesewing.org/uploads/acrossback_60791a4392.png) + + +As such, we feel we're preventing mistakes for the casual user, without taking away power from you, the pattern option guru. + +Or to put it differently, you can still muck about with your across back, but by default, you don't have to worry about it anymore. + diff --git a/markdown/org/blog/core-1-8-jaeger-across-back/nl.md b/markdown/org/blog/core-1-8-jaeger-across-back/nl.md new file mode 100644 index 00000000000..a5481baae1d --- /dev/null +++ b/markdown/org/blog/core-1-8-jaeger-across-back/nl.md @@ -0,0 +1,64 @@ +--- +author: "joostdecock" +caption: "Deze update bereikt je vanuit Bangkok" +date: "2018-03-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/34ed654dcda9004e7c249b90256ad197469cc87e-1920x1277.webp" +intro: "We hebben net onze core 1.8.0 gelanceerd. Zo'n nieuw getal na de komma doen we meestal wanneer we een nieuw patroon toevoegen, maar in dit geval zijn er twee redenen:" +title: "FreeSewing core 1.8: het Jaeger-jasje komt erbij en de 'across back'-afmeting verdwijnt" +--- + + +We hebben net onze core 1.8.0 gelanceerd. Zo'n nieuw getal na de komma doen we meestal wanneer we een nieuw patroon toevoegen, maar in dit geval zijn er twee redenen: + + - Het [Jaeger-jasje](/patterns/jaeger) is nu beschikbaar + - We hebben de afmeting *across back* verwijderd + +Lees verder voor meer details. + +## Het nieuwe Jaeger-jasje + +Voor mijn deelname aan [The Refashioners](/blog/the-refashioners-2017/) vorig jaar heb ik een patroon voor een jasje ontworpen dat ik oorspronkelijk wilde lanceren samen met mijn eerste uitvoering ervan. Het is een beetje anders gegaan en ik heb wat meer tijd gevraagd om het patroon op punt te stellen. + +*Wat meer tijd* bleek uiteindelijk iets meer dan zes maanden te zijn. Dus vergeef me voor de vertraging, maar hier is hij: het [Jaeger-jasje](/patterns/jaeger). + +![In mijn oorspronkelijke post had ik het over de Blake-blazer, maar ik heb het patroon een nieuwe naam gegeven omdat Jaeger-jasje gewoon cooler is](jaeger.jpg) + +### 'Jaeger-sportjasje' is geen alliteratie + +Jaeger is een jasje met een sportieve stijl. Een jasje met een enkele knopenrij van twee knopen en opgenaaide zakken. + +Het is met andere woorden een jasje dat je eerder zou dragen met een jeans of broek, en niet als deel van een kostuum. + +### Opties overal + +Jaeger telt zomaar even 38 opties, dus je kan *véél* aanpassen aan dit patroon. + +Maar maak je geen zorgen; de standaarduitvoering is heel goed doordacht, dus je kan al die opties ook gewoon naast je neerleggen. + +## Weg met de 'across back'-afmeting + +Van goed doordacht gesproken, Jaeger is niet de enige nieuwigheid in de FreeSewing core 1.8.0 die we vandaag lanceren. + +We hebben ook de 'across back'-afmeting afgeschaft. + +De 'across back'-afmeting leverde bij veel gebruikers verwarring op. We merkten vaak dat wanneer gebruikers ons lieten weten dat hun patroon er raar uitzag, de 'across back'-afmeting de boosdoener was. + +Oorspronkelijk gebruikten we de 'across back'-afmeting samen met de schouderlengte die we gebruikten in plaats van de lengte van schouder tot schouder die we nu gebruiken. Die schouderlengte veroorzaakte ook verwarring, dus hebben we die vervangen door de lengte van schouder tot schouder. + +Maar als we dan toch weten wat de lengte van schouder tot schouder is, dan kunnen we met vrij grote zekerheid gokken wat de rugbreedte is. Dus in plaats van jou te vragen om de 'across back' of rugbreedte te meten, berekenen we die nu gewoon vanzelf. + +### Maar je maakt het patroon dommer + +Als je het nog niet doorhad op basis van de 38 opties bij het Jaeger-jasje, zeggen we het nog eens: we vinden het hier bij FreeSewing belangrijk dat je zelf aan alle knopjes kan draaien om je patroonschetsen bij te sturen. + +Een afmeting vervangen door een waarde die berekend wordt op basis van een andere afmeting, lijkt daarmee tegenstrijdig. Maar je hoeft je geen zogen te maken. We hebben ervoor gezorgd dat je wel nog kan spelen met de rugbreedte. + +Patronen waarvoor je vroeger een 'across back'-afmeting nodig had, hebben nu een geavanceerde optie: de *rugbreedtefactor*. Dat laat je toe om aan te passen hoe de rugbreedte berekend wordt, maar dan wel binnen realistische proporties voor je patroon. + +![De rugbreedtefactor-optie](acrossback.png) + +Op die manier denken we dat we frustraties voorkomen bij onze nonchalante gebruikers terwijl we jou, de patroonoptiegoeroe, toch alle vrijheid geven. + +Of anders gezegd, je kan nog altijd prutsen met je 'across back', maar standaard hoef je er zelfs niet meer bij stil te staan. + + diff --git a/markdown/org/blog/core-v1-3-0-is-out/de.md b/markdown/org/blog/core-v1-3-0-is-out/de.md new file mode 100644 index 00000000000..b54cc701bdd --- /dev/null +++ b/markdown/org/blog/core-v1-3-0-is-out/de.md @@ -0,0 +1,104 @@ +--- +author: "joostdecock" +caption: "Scales, how do they work?" +date: "2018-01-04" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d09252be53d33ab5b743c22f523a9ea8cbd70708-2000x1328.jpg" +intro: "Freesewing core v1.3.0 is out; Comes with fixes so good that we back-ported them to all your drafts [Nicht übersetzt]" +title: "Freesewing core v1.3.0 is out; Comes with fixes so good that we back-ported them to all your drafts [Nicht übersetzt]" +--- + +On the last day of 2017, in our +[monthly roundup of all the freesewing news](/blog/roundup-2017-12/) +, we wrote about +the looming issue with incorrectly scaled drafts, aka +[Core issue #204 - The Inkscape default units quandary](https://github.com/freesewing/core/issues/204). + +I won't go over [all that](/blog/roundup-2017-12/) again, but it boils down to the fact that the +[Inkscape](http://inkscape.org/) maintainers have +changed Inkscape's internal DPI (dots per inch) from 90 to 96. A change that goes in effect from version +0.92 onwards. + +Left unchecked, this change would cause all freesewing patterns to be incorrectly scaled. +That's because we assume 90DPI in our SVG output, and scale accordingly. + +![That 'oh-shit' moment when we realized the full impact of the DPI change](https://posts.freesewing.org/uploads/oh_shit_90b4969a5d.gif) + +When the switch to 96DPI goes into effect, all patterns would be off by 6.66%. Which is really +the kind of difference that is too small to notice when eyeballing a pattern, yet large enough +to completely mess up your garment. + +The issue is also more troublesome than it would seem at the surface. +First of all because we can't just switch to 96DPI as there are now two versions out there +that use a different default DPI under the hood. We need a solution that works for both. + +![Screenshot of a freesewing pattern that is incorrectly scaled in the latest Inkscape release](https://posts.freesewing.org/uploads/inkscape_b96e2bb510.png) + +Furthermore, while any fix we implement would apply to new drafts, +all existing drafts generated before the fix would still be impacted. + +In other words, if you drafted a pattern last week, or a month ago, that pattern would not +scale correctly in a recent version of Inkscape. +And since we use Inkscape in our SVG-to-PDF tool-chain, it would also be incorrectly scaled +if you came here and downloaded a PDF. + +Clearly, something needed to be done. And fast. + +## The fix for new drafts + +From today's release of core v1.3.0 onwards, our SVG files no longer depend on any DPI setting. + +Rather than use the internal units and apply an SVG transform to scale the entire +pattern, we've bolted down the units to mm and updated the SVG viewBox to apply the scaling. + +Obviously, this is how we should have done it from the start. Everyday is a school day. + +If you're worried about the use of mm in your draft (because you're used to imperial +units), rest assured that those mm will stay under the hood. You won't be able to tell the difference. + +## The fix for pre-existing drafts + +To avoid problems with pre-existing drafts, we needed to come up with a solution for those too. + +We essentially have two options: + + - Re-draft all those drafts + - Patch them in-place without changing the draft itself + +Re-drafting fixes the issue as every new draft will be handled by the latest core version +that does include the fix. + +However, core also ships with regular updates, tweaks, and fixes in the patterns themselves. +So by re-drafting a draft generated on a previous version of core, there's no guarantee the +draft won't change. + +In principle that change would always be an improvement. But one person's bug is another person's +feature, and we do prefer not to [move your cheese](https://en.wikipedia.org/wiki/Who_Moved_My_Cheese%3F). + +![Don't touch my stuff](https://posts.freesewing.org/uploads/who_moved_my_cheese_0cd51a25d6.jpg) + +So, instead we decided to patch all drafts we have on file in-place with the new scaling code, +without touching any other aspect of the draft. + +As you're reading this, this has already been done, and all freesewing drafts should now scale correctly. +Everywhere. + +## Also: version awareness + +We've also made changes to our backend systems to store the version of freesewing core that +generated your draft. + +If since you generated your draft we've rolled out new features or fixes, you'll be notified +that an update is available: + +![If you draft is generated with an old version of freesewing core, we'll tell you about it](https://posts.freesewing.org/uploads/upgrade_dee342e3fb.png) + +Whether you update your draft or not is up to you. +If you don't want to loose the info in your *old* draft, rather than update it in-place, you can fork it. + + + + + + + + diff --git a/markdown/org/blog/core-v1-3-0-is-out/en.md b/markdown/org/blog/core-v1-3-0-is-out/en.md new file mode 100644 index 00000000000..4e8be464fef --- /dev/null +++ b/markdown/org/blog/core-v1-3-0-is-out/en.md @@ -0,0 +1,104 @@ +--- +author: "joostdecock" +caption: "Scales, how do they work?" +date: "2018-01-04" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d09252be53d33ab5b743c22f523a9ea8cbd70708-2000x1328.jpg" +intro: "Freesewing core v1.3.0 is out; Comes with fixes so good that we back-ported them to all your drafts" +title: "Freesewing core v1.3.0 is out; Comes with fixes so good that we back-ported them to all your drafts" +--- + +On the last day of 2017, in our +[monthly roundup of all the freesewing news](/blog/roundup-2017-12/) +, we wrote about +the looming issue with incorrectly scaled drafts, aka +[Core issue #204 - The Inkscape default units quandary](https://github.com/freesewing/core/issues/204). + +I won't go over [all that](/blog/roundup-2017-12/) again, but it boils down to the fact that the +[Inkscape](http://inkscape.org/) maintainers have +changed Inkscape's internal DPI (dots per inch) from 90 to 96. A change that goes in effect from version +0.92 onwards. + +Left unchecked, this change would cause all freesewing patterns to be incorrectly scaled. +That's because we assume 90DPI in our SVG output, and scale accordingly. + +![That 'oh-shit' moment when we realized the full impact of the DPI change](https://posts.freesewing.org/uploads/oh_shit_90b4969a5d.gif) + +When the switch to 96DPI goes into effect, all patterns would be off by 6.66%. Which is really +the kind of difference that is too small to notice when eyeballing a pattern, yet large enough +to completely mess up your garment. + +The issue is also more troublesome than it would seem at the surface. +First of all because we can't just switch to 96DPI as there are now two versions out there +that use a different default DPI under the hood. We need a solution that works for both. + +![Screenshot of a freesewing pattern that is incorrectly scaled in the latest Inkscape release](https://posts.freesewing.org/uploads/inkscape_b96e2bb510.png) + +Furthermore, while any fix we implement would apply to new drafts, +all existing drafts generated before the fix would still be impacted. + +In other words, if you drafted a pattern last week, or a month ago, that pattern would not +scale correctly in a recent version of Inkscape. +And since we use Inkscape in our SVG-to-PDF tool-chain, it would also be incorrectly scaled +if you came here and downloaded a PDF. + +Clearly, something needed to be done. And fast. + +## The fix for new drafts + +From today's release of core v1.3.0 onwards, our SVG files no longer depend on any DPI setting. + +Rather than use the internal units and apply an SVG transform to scale the entire +pattern, we've bolted down the units to mm and updated the SVG viewBox to apply the scaling. + +Obviously, this is how we should have done it from the start. Everyday is a school day. + +If you're worried about the use of mm in your draft (because you're used to imperial +units), rest assured that those mm will stay under the hood. You won't be able to tell the difference. + +## The fix for pre-existing drafts + +To avoid problems with pre-existing drafts, we needed to come up with a solution for those too. + +We essentially have two options: + + - Re-draft all those drafts + - Patch them in-place without changing the draft itself + +Re-drafting fixes the issue as every new draft will be handled by the latest core version +that does include the fix. + +However, core also ships with regular updates, tweaks, and fixes in the patterns themselves. +So by re-drafting a draft generated on a previous version of core, there's no guarantee the +draft won't change. + +In principle that change would always be an improvement. But one person's bug is another person's +feature, and we do prefer not to [move your cheese](https://en.wikipedia.org/wiki/Who_Moved_My_Cheese%3F). + +![Don't touch my stuff](https://posts.freesewing.org/uploads/who_moved_my_cheese_0cd51a25d6.jpg) + +So, instead we decided to patch all drafts we have on file in-place with the new scaling code, +without touching any other aspect of the draft. + +As you're reading this, this has already been done, and all freesewing drafts should now scale correctly. +Everywhere. + +## Also: version awareness + +We've also made changes to our backend systems to store the version of freesewing core that +generated your draft. + +If since you generated your draft we've rolled out new features or fixes, you'll be notified +that an update is available: + +![If you draft is generated with an old version of freesewing core, we'll tell you about it](https://posts.freesewing.org/uploads/upgrade_dee342e3fb.png) + +Whether you update your draft or not is up to you. +If you don't want to loose the info in your *old* draft, rather than update it in-place, you can fork it. + + + + + + + + diff --git a/markdown/org/blog/core-v1-3-0-is-out/es.md b/markdown/org/blog/core-v1-3-0-is-out/es.md new file mode 100644 index 00000000000..6710810296f --- /dev/null +++ b/markdown/org/blog/core-v1-3-0-is-out/es.md @@ -0,0 +1,104 @@ +--- +author: "joostdecock" +caption: "Scales, how do they work?" +date: "2018-01-04" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d09252be53d33ab5b743c22f523a9ea8cbd70708-2000x1328.jpg" +intro: "Freesewing core v1.3.0 is out; Comes with fixes so good that we back-ported them to all your drafts [No traducido]" +title: "Freesewing core v1.3.0 is out; Comes with fixes so good that we back-ported them to all your drafts [No traducido]" +--- + +On the last day of 2017, in our +[monthly roundup of all the freesewing news](/blog/roundup-2017-12/) +, we wrote about +the looming issue with incorrectly scaled drafts, aka +[Core issue #204 - The Inkscape default units quandary](https://github.com/freesewing/core/issues/204). + +I won't go over [all that](/blog/roundup-2017-12/) again, but it boils down to the fact that the +[Inkscape](http://inkscape.org/) maintainers have +changed Inkscape's internal DPI (dots per inch) from 90 to 96. A change that goes in effect from version +0.92 onwards. + +Left unchecked, this change would cause all freesewing patterns to be incorrectly scaled. +That's because we assume 90DPI in our SVG output, and scale accordingly. + +![That 'oh-shit' moment when we realized the full impact of the DPI change](https://posts.freesewing.org/uploads/oh_shit_90b4969a5d.gif) + +When the switch to 96DPI goes into effect, all patterns would be off by 6.66%. Which is really +the kind of difference that is too small to notice when eyeballing a pattern, yet large enough +to completely mess up your garment. + +The issue is also more troublesome than it would seem at the surface. +First of all because we can't just switch to 96DPI as there are now two versions out there +that use a different default DPI under the hood. We need a solution that works for both. + +![Screenshot of a freesewing pattern that is incorrectly scaled in the latest Inkscape release](https://posts.freesewing.org/uploads/inkscape_b96e2bb510.png) + +Furthermore, while any fix we implement would apply to new drafts, +all existing drafts generated before the fix would still be impacted. + +In other words, if you drafted a pattern last week, or a month ago, that pattern would not +scale correctly in a recent version of Inkscape. +And since we use Inkscape in our SVG-to-PDF tool-chain, it would also be incorrectly scaled +if you came here and downloaded a PDF. + +Clearly, something needed to be done. And fast. + +## The fix for new drafts + +From today's release of core v1.3.0 onwards, our SVG files no longer depend on any DPI setting. + +Rather than use the internal units and apply an SVG transform to scale the entire +pattern, we've bolted down the units to mm and updated the SVG viewBox to apply the scaling. + +Obviously, this is how we should have done it from the start. Everyday is a school day. + +If you're worried about the use of mm in your draft (because you're used to imperial +units), rest assured that those mm will stay under the hood. You won't be able to tell the difference. + +## The fix for pre-existing drafts + +To avoid problems with pre-existing drafts, we needed to come up with a solution for those too. + +We essentially have two options: + + - Re-draft all those drafts + - Patch them in-place without changing the draft itself + +Re-drafting fixes the issue as every new draft will be handled by the latest core version +that does include the fix. + +However, core also ships with regular updates, tweaks, and fixes in the patterns themselves. +So by re-drafting a draft generated on a previous version of core, there's no guarantee the +draft won't change. + +In principle that change would always be an improvement. But one person's bug is another person's +feature, and we do prefer not to [move your cheese](https://en.wikipedia.org/wiki/Who_Moved_My_Cheese%3F). + +![Don't touch my stuff](https://posts.freesewing.org/uploads/who_moved_my_cheese_0cd51a25d6.jpg) + +So, instead we decided to patch all drafts we have on file in-place with the new scaling code, +without touching any other aspect of the draft. + +As you're reading this, this has already been done, and all freesewing drafts should now scale correctly. +Everywhere. + +## Also: version awareness + +We've also made changes to our backend systems to store the version of freesewing core that +generated your draft. + +If since you generated your draft we've rolled out new features or fixes, you'll be notified +that an update is available: + +![If you draft is generated with an old version of freesewing core, we'll tell you about it](https://posts.freesewing.org/uploads/upgrade_dee342e3fb.png) + +Whether you update your draft or not is up to you. +If you don't want to loose the info in your *old* draft, rather than update it in-place, you can fork it. + + + + + + + + diff --git a/markdown/org/blog/core-v1-3-0-is-out/fr.md b/markdown/org/blog/core-v1-3-0-is-out/fr.md new file mode 100644 index 00000000000..4bde204c7b7 --- /dev/null +++ b/markdown/org/blog/core-v1-3-0-is-out/fr.md @@ -0,0 +1,104 @@ +--- +author: "joostdecock" +caption: "Scales, how do they work?" +date: "2018-01-04" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d09252be53d33ab5b743c22f523a9ea8cbd70708-2000x1328.jpg" +intro: "Freesewing core v1.3.0 is out; Comes with fixes so good that we back-ported them to all your drafts [Non traduit]" +title: "Freesewing core v1.3.0 is out; Comes with fixes so good that we back-ported them to all your drafts [Non traduit]" +--- + +On the last day of 2017, in our +[monthly roundup of all the freesewing news](/blog/roundup-2017-12/) +, we wrote about +the looming issue with incorrectly scaled drafts, aka +[Core issue #204 - The Inkscape default units quandary](https://github.com/freesewing/core/issues/204). + +I won't go over [all that](/blog/roundup-2017-12/) again, but it boils down to the fact that the +[Inkscape](http://inkscape.org/) maintainers have +changed Inkscape's internal DPI (dots per inch) from 90 to 96. A change that goes in effect from version +0.92 onwards. + +Left unchecked, this change would cause all freesewing patterns to be incorrectly scaled. +That's because we assume 90DPI in our SVG output, and scale accordingly. + +![That 'oh-shit' moment when we realized the full impact of the DPI change](https://posts.freesewing.org/uploads/oh_shit_90b4969a5d.gif) + +When the switch to 96DPI goes into effect, all patterns would be off by 6.66%. Which is really +the kind of difference that is too small to notice when eyeballing a pattern, yet large enough +to completely mess up your garment. + +The issue is also more troublesome than it would seem at the surface. +First of all because we can't just switch to 96DPI as there are now two versions out there +that use a different default DPI under the hood. We need a solution that works for both. + +![Screenshot of a freesewing pattern that is incorrectly scaled in the latest Inkscape release](https://posts.freesewing.org/uploads/inkscape_b96e2bb510.png) + +Furthermore, while any fix we implement would apply to new drafts, +all existing drafts generated before the fix would still be impacted. + +In other words, if you drafted a pattern last week, or a month ago, that pattern would not +scale correctly in a recent version of Inkscape. +And since we use Inkscape in our SVG-to-PDF tool-chain, it would also be incorrectly scaled +if you came here and downloaded a PDF. + +Clearly, something needed to be done. And fast. + +## The fix for new drafts + +From today's release of core v1.3.0 onwards, our SVG files no longer depend on any DPI setting. + +Rather than use the internal units and apply an SVG transform to scale the entire +pattern, we've bolted down the units to mm and updated the SVG viewBox to apply the scaling. + +Obviously, this is how we should have done it from the start. Everyday is a school day. + +If you're worried about the use of mm in your draft (because you're used to imperial +units), rest assured that those mm will stay under the hood. You won't be able to tell the difference. + +## The fix for pre-existing drafts + +To avoid problems with pre-existing drafts, we needed to come up with a solution for those too. + +We essentially have two options: + + - Re-draft all those drafts + - Patch them in-place without changing the draft itself + +Re-drafting fixes the issue as every new draft will be handled by the latest core version +that does include the fix. + +However, core also ships with regular updates, tweaks, and fixes in the patterns themselves. +So by re-drafting a draft generated on a previous version of core, there's no guarantee the +draft won't change. + +In principle that change would always be an improvement. But one person's bug is another person's +feature, and we do prefer not to [move your cheese](https://en.wikipedia.org/wiki/Who_Moved_My_Cheese%3F). + +![Don't touch my stuff](https://posts.freesewing.org/uploads/who_moved_my_cheese_0cd51a25d6.jpg) + +So, instead we decided to patch all drafts we have on file in-place with the new scaling code, +without touching any other aspect of the draft. + +As you're reading this, this has already been done, and all freesewing drafts should now scale correctly. +Everywhere. + +## Also: version awareness + +We've also made changes to our backend systems to store the version of freesewing core that +generated your draft. + +If since you generated your draft we've rolled out new features or fixes, you'll be notified +that an update is available: + +![If you draft is generated with an old version of freesewing core, we'll tell you about it](https://posts.freesewing.org/uploads/upgrade_dee342e3fb.png) + +Whether you update your draft or not is up to you. +If you don't want to loose the info in your *old* draft, rather than update it in-place, you can fork it. + + + + + + + + diff --git a/markdown/org/blog/core-v1-3-0-is-out/nl.md b/markdown/org/blog/core-v1-3-0-is-out/nl.md new file mode 100644 index 00000000000..cb83e530a5d --- /dev/null +++ b/markdown/org/blog/core-v1-3-0-is-out/nl.md @@ -0,0 +1,104 @@ +--- +author: "joostdecock" +caption: "Scales, how do they work?" +date: "2018-01-04" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d09252be53d33ab5b743c22f523a9ea8cbd70708-2000x1328.jpg" +intro: "Freesewing core v1.3.0 is out; Comes with fixes so good that we back-ported them to all your drafts [Niet vertaald]" +title: "Freesewing core v1.3.0 is out; Comes with fixes so good that we back-ported them to all your drafts [Niet vertaald]" +--- + +On the last day of 2017, in our +[monthly roundup of all the freesewing news](/blog/roundup-2017-12/) +, we wrote about +the looming issue with incorrectly scaled drafts, aka +[Core issue #204 - The Inkscape default units quandary](https://github.com/freesewing/core/issues/204). + +I won't go over [all that](/blog/roundup-2017-12/) again, but it boils down to the fact that the +[Inkscape](http://inkscape.org/) maintainers have +changed Inkscape's internal DPI (dots per inch) from 90 to 96. A change that goes in effect from version +0.92 onwards. + +Left unchecked, this change would cause all freesewing patterns to be incorrectly scaled. +That's because we assume 90DPI in our SVG output, and scale accordingly. + +![That 'oh-shit' moment when we realized the full impact of the DPI change](https://posts.freesewing.org/uploads/oh_shit_90b4969a5d.gif) + +When the switch to 96DPI goes into effect, all patterns would be off by 6.66%. Which is really +the kind of difference that is too small to notice when eyeballing a pattern, yet large enough +to completely mess up your garment. + +The issue is also more troublesome than it would seem at the surface. +First of all because we can't just switch to 96DPI as there are now two versions out there +that use a different default DPI under the hood. We need a solution that works for both. + +![Screenshot of a freesewing pattern that is incorrectly scaled in the latest Inkscape release](https://posts.freesewing.org/uploads/inkscape_b96e2bb510.png) + +Furthermore, while any fix we implement would apply to new drafts, +all existing drafts generated before the fix would still be impacted. + +In other words, if you drafted a pattern last week, or a month ago, that pattern would not +scale correctly in a recent version of Inkscape. +And since we use Inkscape in our SVG-to-PDF tool-chain, it would also be incorrectly scaled +if you came here and downloaded a PDF. + +Clearly, something needed to be done. And fast. + +## The fix for new drafts + +From today's release of core v1.3.0 onwards, our SVG files no longer depend on any DPI setting. + +Rather than use the internal units and apply an SVG transform to scale the entire +pattern, we've bolted down the units to mm and updated the SVG viewBox to apply the scaling. + +Obviously, this is how we should have done it from the start. Everyday is a school day. + +If you're worried about the use of mm in your draft (because you're used to imperial +units), rest assured that those mm will stay under the hood. You won't be able to tell the difference. + +## The fix for pre-existing drafts + +To avoid problems with pre-existing drafts, we needed to come up with a solution for those too. + +We essentially have two options: + + - Re-draft all those drafts + - Patch them in-place without changing the draft itself + +Re-drafting fixes the issue as every new draft will be handled by the latest core version +that does include the fix. + +However, core also ships with regular updates, tweaks, and fixes in the patterns themselves. +So by re-drafting a draft generated on a previous version of core, there's no guarantee the +draft won't change. + +In principle that change would always be an improvement. But one person's bug is another person's +feature, and we do prefer not to [move your cheese](https://en.wikipedia.org/wiki/Who_Moved_My_Cheese%3F). + +![Don't touch my stuff](https://posts.freesewing.org/uploads/who_moved_my_cheese_0cd51a25d6.jpg) + +So, instead we decided to patch all drafts we have on file in-place with the new scaling code, +without touching any other aspect of the draft. + +As you're reading this, this has already been done, and all freesewing drafts should now scale correctly. +Everywhere. + +## Also: version awareness + +We've also made changes to our backend systems to store the version of freesewing core that +generated your draft. + +If since you generated your draft we've rolled out new features or fixes, you'll be notified +that an update is available: + +![If you draft is generated with an old version of freesewing core, we'll tell you about it](https://posts.freesewing.org/uploads/upgrade_dee342e3fb.png) + +Whether you update your draft or not is up to you. +If you don't want to loose the info in your *old* draft, rather than update it in-place, you can fork it. + + + + + + + + diff --git a/markdown/org/blog/cornelius-cycling-breeches/de.md b/markdown/org/blog/cornelius-cycling-breeches/de.md new file mode 100644 index 00000000000..7e83482eced --- /dev/null +++ b/markdown/org/blog/cornelius-cycling-breeches/de.md @@ -0,0 +1,29 @@ +--- +author: "joostdecock" +caption: "Radfahren wie ein wahrer Gentleman" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/15c72486b0c48905f9f4a916a32caa058f1b0f8a-997x857.jpg" +intro: "Wouter ist wieder einmal dabei, diesmal verwöhnt er uns mit klassischen Kniebundhosen zum Radfahren." +title: "Diese Radfahr-Kniehosen Cornelius sind Wouters neuestes Geschenk an uns alle" +--- + + +[Wouter](https://www.instagram.com/wouter.vdub/) ist wieder einmal dabei, diesmal verwöhnt er uns mit klassischen Kniebundhosen zum Radfahren. + +Er schreibt: + +> Als ich ein Kind war, erzählte mir mein Vater Geschichten über Wanderungen in den Bergen, etwas Magisches für ein Kind in den Niederlanden. Er hatte einen Koffer mit seinen Dingen zum Bergsteigen, und Teil davon waren ein paar "Knickerbocker", beutelige Hosen, die bis zu den Waden reichten. +> +> Als ich in meinen Dreißigern in die USA zog und selber mit dem Wandern begann, habe ich häufig an diese Unterhaltungen zurückgedacht und es als schade empfunden, dass ich diese Knickerbocker nicht geerbt habe. Als ich dann das Nähen entdeckte, beschloss ich, mir selber welche zu machen, aber es ließen sich keine guten Muster finden. +> +> Dieser Jahr postete jemand im Freesewing Discord-Server einen Link zu den "Keystone"-Systemen, praktische Methoden des Schneiderns aus der Zeit der Jahrhundertwende. Diese enthielten ein Entwurfssystem für "Radfahr-Kniehosen", die nah an dem waren, was mein Vater früher trug, und die sich in ein Freesewing-Schnittmuster übertragen ließen. Ein Projekt war geboren, und ich freue mich darüber, euch nun das Ergebnis präsentieren zu können. + +Wie Wouter erwähnt: dises Schnittmuster basiert auf [der Entwurfsmethode nach Keystone](https://archive.org/details/keystonesystemsc00heck/page/n5/mode/2up). Das spielt aber natürlich keine Rolle, weil du es wie immer für dich maßgeschneidert bekommst, [direkt hier auf FreeSewing.org](/designs/cornelius/). + +![Hier ist der Herr höchstpersönlich](wouter.jpg) + +Beachte, dass du nicht Fahrrad fahren musst, um diese zu tragen. Du musst nur dazu bereit sein, deine Socken (oder Waden) zur Schau zu stellen. + +Cornelius ist verfügbar unter [/designs/cornelius/](/designs/cornelius/). + + diff --git a/markdown/org/blog/cornelius-cycling-breeches/en.md b/markdown/org/blog/cornelius-cycling-breeches/en.md new file mode 100644 index 00000000000..8f1f4e67bbb --- /dev/null +++ b/markdown/org/blog/cornelius-cycling-breeches/en.md @@ -0,0 +1,36 @@ +--- +author: "joostdecock" +caption: "Cycling like a true gentlemen" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/15c72486b0c48905f9f4a916a32caa058f1b0f8a-997x857.jpg" +intro: "Wouter is at it again, this time around he's treating us to classic cycling breeches." +title: "These Cornelius cycling breeches are Wouter's latest gift to us all" +--- + + +[Wouter](https://www.instagram.com/wouter.vdub/) is at it again, this time around he's treating us to classic cycling breeches. + +He writes: + +> When I was a child my dad would tell me stories about hiking in the mountains, something magical for a kid living in The Netherlands. +> He had a suitcase with his mountaineering things in it, and part of that were some 'knickerbockers', baggy trousers that reached down to your calves. +> +> When I moved to the USA in my thirties and started hiking myself, I would often reflect on those talks and felt sad that I didn't inherit those knickerbockers. +> Then when I discovered sewing, I decided I would make myself a pair, but no good patterns presented themselves. +> +> This year someone on the Freesewing discord server posted a link to The 'Keystone' Systems, Practical methods of cutting, from around the turn of the century. +> This contained a drafting system for 'Cycling Breeches', which seemed to be close to what my father used to wear, and could be translated into a Freesewing pattern. +> A project was born, and I'm happy to be able to present the results to you. + +As Wouter mentioned; This pattern is based on [the Keystone drafting method](https://archive.org/details/keystonesystemsc00heck/page/n5/mode/2up). +Not that it matters because as always you get it made-to-measure for +you [right here on FreeSewing.org](/designs/cornelius/). + +![Here's the man himself](https://posts.freesewing.org/uploads/wouter_9fbc821146.jpg) + +Note that you don't have to cycle to wear these. +All that's required is a willingness to show of those socks (or calfs). + +Cornelius is available at [/designs/cornelius/](/designs/cornelius/). + + diff --git a/markdown/org/blog/cornelius-cycling-breeches/es.md b/markdown/org/blog/cornelius-cycling-breeches/es.md new file mode 100644 index 00000000000..2a68741918d --- /dev/null +++ b/markdown/org/blog/cornelius-cycling-breeches/es.md @@ -0,0 +1,36 @@ +--- +author: "joostdecock" +caption: "Cycling like a true gentlemen" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/15c72486b0c48905f9f4a916a32caa058f1b0f8a-997x857.jpg" +intro: "Wouter is at it again, this time around he's treating us to classic cycling breeches." +title: "These Cornelius cycling breeches are Wouter's latest gift to us all [No traducido]" +--- + + +[Wouter](https://www.instagram.com/wouter.vdub/) is at it again, this time around he's treating us to classic cycling breeches. + +He writes: + +> When I was a child my dad would tell me stories about hiking in the mountains, something magical for a kid living in The Netherlands. +> He had a suitcase with his mountaineering things in it, and part of that were some 'knickerbockers', baggy trousers that reached down to your calves. +> +> When I moved to the USA in my thirties and started hiking myself, I would often reflect on those talks and felt sad that I didn't inherit those knickerbockers. +> Then when I discovered sewing, I decided I would make myself a pair, but no good patterns presented themselves. +> +> This year someone on the Freesewing discord server posted a link to The 'Keystone' Systems, Practical methods of cutting, from around the turn of the century. +> This contained a drafting system for 'Cycling Breeches', which seemed to be close to what my father used to wear, and could be translated into a Freesewing pattern. +> A project was born, and I'm happy to be able to present the results to you. + +As Wouter mentioned; This pattern is based on [the Keystone drafting method](https://archive.org/details/keystonesystemsc00heck/page/n5/mode/2up). +Not that it matters because as always you get it made-to-measure for +you [right here on FreeSewing.org](/designs/cornelius/). + +![Here's the man himself](https://posts.freesewing.org/uploads/wouter_9fbc821146.jpg) + +Note that you don't have to cycle to wear these. +All that's required is a willingness to show of those socks (or calfs). + +Cornelius is available at [/designs/cornelius/](/designs/cornelius/). + + diff --git a/markdown/org/blog/cornelius-cycling-breeches/fr.md b/markdown/org/blog/cornelius-cycling-breeches/fr.md new file mode 100644 index 00000000000..3daaa320e00 --- /dev/null +++ b/markdown/org/blog/cornelius-cycling-breeches/fr.md @@ -0,0 +1,29 @@ +--- +author: "joostdecock" +caption: "Faire du vélo comme un vrai gentilhomme" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/15c72486b0c48905f9f4a916a32caa058f1b0f8a-997x857.jpg" +intro: "Wouter s'y est remis, cette fois-ci il nous a préparé une culotte de cyclisme classique." +title: "Cette culotte de cyclisme Cornelius est le dernier cadeau de Woutter pour nous tous" +--- + + +[Wouter](https://www.instagram.com/wouter.vdub/) s'y est remis, cette fois-ci il nous a préparé une culotte de cyclisme classique. + +Il a écrit : + +> Quand j’étais enfant, mon père me racontait des histoires sur la randonnée dans les montagnes, quelque chose de magique pour un enfant vivant aux Pays-Bas. Il avait une valise avec ses affaires d'alpinisme dedans, et une partie était des "culottes", pantalon baggy qui descendait jusqu'aux mollets. +> +> Quand j'ai déménagé aux États-Unis dans ma trentaine et j'ai commencé à faire de la randonnée. Je pensais souvent à ces discussions et je me sentais triste de ne pas avoir hérité de ces culottes. Puis quand j'ai découvert la couture, j'ai décidé de m'en faire, mais aucun bon patron ne s'est présenté. +> +> Cette année, quelqu'un sur le serveur discord de Freesewing a posté un lien vers les systèmes de la "Keystone", méthodes pratiques de coupe, du début du siècle dernier. Celui-ci contenait un système de patronage pour les "culottes de cyclisme", qui semblait être proche de ce que mon père avait l'habitude de porter, et pouvait être traduit en un patron Freesewing. Un projet est né et je suis heureux de pouvoir vous présenter les résultats. + +Comme Wouter l'a mentionné; Ce modèle est basé sur [la méthode de patronage de Keystone](https://archive.org/details/keystonesystemsc00heck/page/n5/mode/2up). Cela n'a pas d'importance parce que, comme toujours, vous le faites sur mesure pour vous [ici sur FreeSewing.org](/designs/cornelius/). + +![Voici l'homme lui-même](wouter.jpg) + +Notez que vous n'avez pas à faire de vélo pour les porter. Tout ce qu'il faut c'est une volonté de montrer vos chaussettes (ou mollets). + +Cornelius est disponible à [/designs/cornelius/](/designs/cornelius/). + + diff --git a/markdown/org/blog/cornelius-cycling-breeches/nl.md b/markdown/org/blog/cornelius-cycling-breeches/nl.md new file mode 100644 index 00000000000..f43fee2128c --- /dev/null +++ b/markdown/org/blog/cornelius-cycling-breeches/nl.md @@ -0,0 +1,36 @@ +--- +author: "joostdecock" +caption: "Cycling like a true gentlemen" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/15c72486b0c48905f9f4a916a32caa058f1b0f8a-997x857.jpg" +intro: "Wouter is at it again, this time around he's treating us to classic cycling breeches." +title: "These Cornelius cycling breeches are Wouter's latest gift to us all [Niet vertaald]" +--- + + +[Wouter](https://www.instagram.com/wouter.vdub/) is at it again, this time around he's treating us to classic cycling breeches. + +He writes: + +> When I was a child my dad would tell me stories about hiking in the mountains, something magical for a kid living in The Netherlands. +> He had a suitcase with his mountaineering things in it, and part of that were some 'knickerbockers', baggy trousers that reached down to your calves. +> +> When I moved to the USA in my thirties and started hiking myself, I would often reflect on those talks and felt sad that I didn't inherit those knickerbockers. +> Then when I discovered sewing, I decided I would make myself a pair, but no good patterns presented themselves. +> +> This year someone on the Freesewing discord server posted a link to The 'Keystone' Systems, Practical methods of cutting, from around the turn of the century. +> This contained a drafting system for 'Cycling Breeches', which seemed to be close to what my father used to wear, and could be translated into a Freesewing pattern. +> A project was born, and I'm happy to be able to present the results to you. + +As Wouter mentioned; This pattern is based on [the Keystone drafting method](https://archive.org/details/keystonesystemsc00heck/page/n5/mode/2up). +Not that it matters because as always you get it made-to-measure for +you [right here on FreeSewing.org](/designs/cornelius/). + +![Here's the man himself](https://posts.freesewing.org/uploads/wouter_9fbc821146.jpg) + +Note that you don't have to cycle to wear these. +All that's required is a willingness to show of those socks (or calfs). + +Cornelius is available at [/designs/cornelius/](/designs/cornelius/). + + diff --git a/markdown/org/blog/email-spam-problems/de.md b/markdown/org/blog/email-spam-problems/de.md new file mode 100644 index 00000000000..772e061d190 --- /dev/null +++ b/markdown/org/blog/email-spam-problems/de.md @@ -0,0 +1,117 @@ +--- +author: "joostdecock" +caption: "Würden Sie eine Spur schließen, weil ein Fahrer seine Musik zu laut spielte?" +date: "2017-09-07" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/923cd5587c873d2662df4a804f75f8f32b5673ca-1920x1281.jpg" +intro: "Menschen mit einer E-Mail-Adresse von Microsoft --- denken Sie an Hotmail, MSN, live.com, outlook.com und ihre zahlreichen Varianten --- melden sich, statistisch gesehen, deutlich weniger für diese Website an." +title: "Danke für nichts Microsoft; E-Mail sollte nicht so schwierig sein" +--- + + +Menschen mit einer E-Mail-Adresse von Microsoft --- denken Sie an Hotmail, MSN, live.com, outlook.com und ihre zahlreichen Varianten --- melden sich, statistisch gesehen, deutlich weniger für diese Website an. + +Der Grund dafür ist, dass mehr als 4 mal von 10, sie nie ihre Kontoaktivierungs-E-Mail erhalten. + +## Was ist hier los? + +Schauen wir uns zunächst an, was passiert. Hier ist ein relevantes Snippet aus den Logs: + +```` +Failed: postmaster@mg.freesewing.org -> ********@hotmail.co.uk 'Confirm your freesewing account' +Server response: 550 5.7.1 Unfortunately, messages from [104.130.122.15] weren't sent. +Please contact your Internet service provider since part of their network is on our block list. +```` + +Das bedeutet, dass ein Teil des MailGun Netzwerks auf ihrer Blockliste steht. Im Endeffekt liefer Die (wer die sind mehr dazu später) die ausgehenden Nachrichten nicht aus an die Empfänger. + +[MailGun](https://www.mailgun.com/) ist ein beliebter E-Mail-Dienst für Entwickler. Es wird von dieser Seite verwendet, um E-Mails zu verschicken, wie zum Beispiel die Aktivierungs-E-Mails. + +Auch andere Leute nutzen diesen Dienst auch, und vielleicht haben einige von ihnen irgendwann Spam per Mailgun versendet. Oder es war vielleicht nur ein Mann mit einem Nachnamen, der dazu neigt, Spamfilter auszulösen. + +![Einige andere MailGun Kunden. Nicht gerade ein zwielichtiger Dienst, oder?](mailgun.png) + +Der Punkt ist, diese IP-Adresse oder einer ihrer Nachbarn hat *eine schlechte Reputation*. Das passiert. Aber sich zu weigern, Nachrichten von diesem Host (oder einem ganzen Netzwerk von Hosts) anzunehmen, ist gleichbedeutend mit dem Abschalten einer Autobahnspur (oder einer ganzen Autobahn), weil ein Auto in dieser Spur seine Musik einmal unangenehm laut wiedergab. + +Was uns zu der nächsten Frage bringt: + +## Wer würde so etwas tun? + +Gute Frage. Hier sind ein paar Beispiele: + +![Ein Graph der Zustellung von E-Mails seit dem Start dieser Seite](emailgraph.png) + +Der obige Graph stellt E-Mails dar, die seit dem Start dieser Website verschickt wurden. Der kleine Abschnitt des roten Graphen sind E-Mails, die nicht ausgeliefert werden. + +Diese Website versendet verschiedene Arten von E-Mails: + + - Benutzerkonto-Bestätigungs-E-Mail + - Die *Ich habe mein Passwort vergessen* E-Mails + - Kommentarantwort-Benachrichtigungen + +Der Graph steht für alle E-Mails, aber ich konzentriere mich nur auf das Konto-Bestätigungs-E-Mails. Sie sind schließlich die Wichtigsten. + +> Außer dem 1 Auslöser wurde jede blockierte Nachricht von Microsoft blockiert + +Hier ist eine Liste aller Domains, die legitime Aktivierungs-E-Mails an ihre Benutzer blockiert haben: + + - btinternet.com + - hotmail.com + - hotmail.co.uk + - live.ca + - live.com + - live.com.au + - live.nl + - msn.com + - outlook.com + +Abgesehen von diesem ersten Eintrag in der Liste (bei dem nur eine Nachricht blockiert wurde) handelt es sich um Microsoft-Domains. + +Lassen Sie mich das noch einmal klar sagen: Abgesehen von dem 1 Auslöser wurde jede Meldung, die blockiert wurde, von Microsoft blockiert. + +## Was sind die Auswirkungen? + +Welche Auswirkungen hat das auf die Menschen? + +Nun, zu dem Zeitpunkt, zu dem ich dies schreibe, gibt es 817 registrierte Benutzer, und ca. 80% (661) haben auch ihr Konto aktiviert. + +![Eine unverhältnismäßige Anzahl an ausstehenden Aktivierungen ist von Benutzern mit einer von Microsoft verwalteten E-Mail-Adresse](activations.svg) + +Von diesen Personen, die in der Lage waren, ihr Konto zu aktivieren, haben weniger als 1% (6) eine E-Mail-Adresse, die von Microsoft verwaltet wird. In der Gruppe von Personen, die ihr Konto nicht aktiviert haben oder nicht in der Lage waren, ihr Konto zu aktivieren, haben mehr als die Hälfte eine solche Adresse. + +Mehr als 40% der E-Mail-Nachrichten zur Kontobestätigung werden einfach von Microsoft blockiert, und je nach Anzahl der Aktivierungen scheint es wahrscheinlich, dass sie, selbst wenn sie nicht am SMTP-Relay blockiert werden, irgendwo weiter hinten gefiltert werden. + +So wie die Dinge liegen, scheint es fast unmöglich für die durchschnittliche Hotmail/outlook/live/MSN/... Benutzer, um sich für diese Seite zu registrieren. + +## Was können wir dagegen tun? + +Ich habe mailgun aus einer Reihe von Gründen gewählt. Das Fehlen von SMTP-Outselves vereinfacht den Code. Nicht abhängig von einem lokalen SMTP-Deamon zu sein macht den Code portabler, und MailGun hat eine Reihe cooler Funktionen, die es einem erlauben auf Kommentare per E-Mail zu antworten. + +Microsofts grobe Methoden der Spam-Filterung entkräften keinen dieser Gründe. + +MailGun zu benutzen bedeutet, ihre SMTP-Relais zu benutzen und dem Reputation dieses Relais ausgeliefert zu sein. Der einzige Weg, das zu umgehen, ist, ein dediziertes Relais in MailGun so zu konfigurieren, dass der FreeSewing.org-Traffic abgeschirmt ist vom Rest, und wir die Kontrolle über die Reputation unseres Smtp-Relais haben. + +![$59 monatlich? Vielleicht nicht](pricing.png) + +Für dieses Privileg berechnet MailGun 59 Dollar pro Monat, was sich auf 708 Dollar jährlich beläuft. Wenn Sie einen Blick in die [Spendenhistory](/about/pledge#donations-history) werfen, werden Sie feststellen, dass dies nicht drin liegt. + +Ich könnte die Blockliste herausfordern und versuchen, das Relais entsperrt zu bekommen. Aber das ist so ziemlicher Kampf gegen Windmühlen, wenn der Host nicht unter meiner Kontrolle ist. Ganz zu schweigen davon, dass MailGun nicht nur diesen einen Host hat. + +Es scheint, dass ich kaum Optionen mehr habe, und ganz ehrlich, mir reisst auch der Geduldsfaden. + +## Was ich dagegen tun werde + +Microsoft ist ein Moloch, und ich bin nur ein Kerl. Ich kann sie hier nicht bekämpfen. Ausser ich „titanfalle“ ihre Ärsche. + +![Blockiere dies, Schlampe](titanfall.gif) + +Glauben Sie, dass Gmail niemals missbraucht wird, um Spam zu versenden? Sie wissen, dass es das wird. Glauben Sie, dass sie jemals alle E-Mails von Google Mail blockieren würden? Sie wissen, dass das nicht der Fall ist. + +Also habe ich gestern Abend einige Änderungen vorgenommen, um das Thema zu umgehen. Wenn Sie eine *problematische* E-Mail-Adresse haben, zusätzlich zu der regulären E-Mail, verschickt Ihnen diese Seite eine zweite E-Mail über Gmail. + +Ich möchte sehen, dass sie das blockieren. + +> ##### Registrierungsprobleme? Hilfe ist verfügbar +> +> Wenn Sie (noch immer) Probleme mit der Registrierung haben, zögern Sie nicht, [Kontakt aufzunehmen](/contact). + + diff --git a/markdown/org/blog/email-spam-problems/en.md b/markdown/org/blog/email-spam-problems/en.md new file mode 100644 index 00000000000..9870460185a --- /dev/null +++ b/markdown/org/blog/email-spam-problems/en.md @@ -0,0 +1,138 @@ +--- +author: "joostdecock" +caption: "Would you close a lane because one driver was playing their music too loud?" +date: "2017-09-07" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/923cd5587c873d2662df4a804f75f8f32b5673ca-1920x1281.jpg" +intro: "Thanks for nothing Microsoft; Email shouldn't be this hard" +title: "Thanks for nothing Microsoft; Email shouldn't be this hard" +--- + +People with an email address from Microsoft --- think Hotmail, MSN, live.com, outlook.com and their numerous variants --- +are significantly less likely to sign up for this website. + +That's because more than 4 times out of 10, they never receive their account activation email. + +## What's going on? + +Let's first look at what's happening. Here's a relevant snippet from the logs: + +```` +Failed: postmaster@mg.freesewing.org -> ********@hotmail.co.uk 'Confirm your freesewing account' +Server response: 550 5.7.1 Unfortunately, messages from [104.130.122.15] weren't sent. +Please contact your Internet service provider since part of their network is on our block list. +```` + +What this means is that part of the MailGun network is on their block list. +As a result, they (more on who they are later) are not delivering any messages that go out. + +[MailGun](https://www.mailgun.com/) is a popular email service for developers. +It's used by this site to send out emails, like the account activation emails. + +Other people use this service too, and perhaps some of them, at some point, +delivered some spam messages through mailgun. Or it may just have been some guy with +a last name that tends to trigger spam filters. + +![Some other MailGun customers. Not exactly a dodgy service is it?](https://posts.freesewing.org/uploads/mailgun_19f315d4d6.png) + +Point is, this IP address or one of its neighbours got *a bad rep*. It happens. +But to flat-out refuse to accept any messages from this host (or an entire network of hosts) +is the equivalent of shutting down a highway lane (or entire highway) +because one car in that lane played its music obnoxiously loud that one time. + +Which brings me to our next question: + +## Who would do something like that? + +Good question. Here are some numbers: + +![A graph of mail delivery since the launch of this site](https://posts.freesewing.org/uploads/emailgraph_d14d476efa.png) + +The graph above represents emails that were sent out since the launch of this site. +The small subsection of the graph that is red are emails that are dropped. + +This website sends out different kinds of email: + + - The account confirmation email + - The *I forgot my password* emails + - Comment reply notifications + +The graph represents all email, but I'm focussing on the account confirmation emails only. +They are the most important after all. + +> Apart from the 1 outlier, every message that was blocked, was blocked by Microsoft + +Here's a list of all domains that blocked legitimate activation emails to their users: + + - btinternet.com + - hotmail.com + - hotmail.co.uk + - live.ca + - live.com + - live.com.au + - live.nl + - msn.com + - outlook.com + +Apart from that very first entry in the list (on which only 1 message was blocked) all of these are Microsoft domains. + +Let me restate that: Apart from the 1 outlier, every message that was blocked, was blocked by Microsoft. + +## What's the impact? + +So what sort of impact does that have on people? + +Well, at the time I'm writing this, there are 817 registered users, and about 80% (661) have also activated their account. + +![A disproportionate amount of pending activations is from users with an email address managed by Microsoft](https://posts.freesewing.org/uploads/activations_06987b6065.svg) + +From those people who were able to activate their account, less than 1% (6) have an email address managed by Microsoft. +In the group of people who did not, or were not able to, activate their account, more than half have such an address. + +More than 40% of account confirmation emails are simply blocked by Microsoft and, based on the number of activations, +it seems likely that even when they aren't block at the SMTP relay, they get filtered somewhere further down the line. + +As things stand, it seems almost impossible for the average hotmail/outlook/live/MSN/... user to sign up for this site. + +## What can we do about it? + +I chose mailgun for a number of reasons. Not having to handle SMTP outselves simplifies the code. +Not depending on a local SMTP deamon makes the code more portable, and MailGun has a bunch of cool features +that allow you to do things like replying to comments via email. + +Microsoft's crude methods of spam filtering don't invalidate any of those reasons. + +Using MailGun means using their SMTP relays, and being at the mercy of the reputation of that relay. +The only way around that is to configure a dedicated relay in MailGun so that freesewing.org traffic is shielded from +others, and we become masters of our own reputation. + +![$59 per month? Perhaps not](https://posts.freesewing.org/uploads/pricing_52f0e817cb.png) + +For that priviledge, MailGun charges 59 dollar per month, which amounts to 708 dollar yearly. +I invite you to take a look at [the donations history](/about/pledge#donations-history), +and you'll understand that's not going to happen either. + +I could challenge the block list, and try to get the relay unblocked. +But that's pretty much tilting at windmills when the host is not under my control. +Not to mention that MailGun doesn't just have that one host. + +It seems that I'm running low on options and quiet frankly, I'm also running out of patience. + +## What I'm going to do about it + +Microsoft is a behemoth, and I'm just a guy. I can't fight them on this. +Unless I Titanfall their ass. + +![Block this, bitch](https://posts.freesewing.org/uploads/titanfall_cb5a210468.gif) + +Do you think Gmail is ever abused to send out spam? You know it is. +Do you think they would ever block all email coming from Gmail? You know they won't. + +So last night, I rolled out some changes to work around the issue. +If you have a *problemtic* email address, in addition to the regular email, this site will send out +a second email through Gmail. + +I'd like to see them block that. + +> ##### Signup trouble? Help is available +> If you are (still) having problems signing up, don't hesitate to [get in touch](/contact). + diff --git a/markdown/org/blog/email-spam-problems/es.md b/markdown/org/blog/email-spam-problems/es.md new file mode 100644 index 00000000000..6445a282615 --- /dev/null +++ b/markdown/org/blog/email-spam-problems/es.md @@ -0,0 +1,138 @@ +--- +author: "joostdecock" +caption: "Would you close a lane because one driver was playing their music too loud?" +date: "2017-09-07" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/923cd5587c873d2662df4a804f75f8f32b5673ca-1920x1281.jpg" +intro: "Thanks for nothing Microsoft; Email shouldn't be this hard [No traducido]" +title: "Thanks for nothing Microsoft; Email shouldn't be this hard [No traducido]" +--- + +People with an email address from Microsoft --- think Hotmail, MSN, live.com, outlook.com and their numerous variants --- +are significantly less likely to sign up for this website. + +That's because more than 4 times out of 10, they never receive their account activation email. + +## What's going on? + +Let's first look at what's happening. Here's a relevant snippet from the logs: + +```` +Failed: postmaster@mg.freesewing.org -> ********@hotmail.co.uk 'Confirm your freesewing account' +Server response: 550 5.7.1 Unfortunately, messages from [104.130.122.15] weren't sent. +Please contact your Internet service provider since part of their network is on our block list. +```` + +What this means is that part of the MailGun network is on their block list. +As a result, they (more on who they are later) are not delivering any messages that go out. + +[MailGun](https://www.mailgun.com/) is a popular email service for developers. +It's used by this site to send out emails, like the account activation emails. + +Other people use this service too, and perhaps some of them, at some point, +delivered some spam messages through mailgun. Or it may just have been some guy with +a last name that tends to trigger spam filters. + +![Some other MailGun customers. Not exactly a dodgy service is it?](https://posts.freesewing.org/uploads/mailgun_19f315d4d6.png) + +Point is, this IP address or one of its neighbours got *a bad rep*. It happens. +But to flat-out refuse to accept any messages from this host (or an entire network of hosts) +is the equivalent of shutting down a highway lane (or entire highway) +because one car in that lane played its music obnoxiously loud that one time. + +Which brings me to our next question: + +## Who would do something like that? + +Good question. Here are some numbers: + +![A graph of mail delivery since the launch of this site](https://posts.freesewing.org/uploads/emailgraph_d14d476efa.png) + +The graph above represents emails that were sent out since the launch of this site. +The small subsection of the graph that is red are emails that are dropped. + +This website sends out different kinds of email: + + - The account confirmation email + - The *I forgot my password* emails + - Comment reply notifications + +The graph represents all email, but I'm focussing on the account confirmation emails only. +They are the most important after all. + +> Apart from the 1 outlier, every message that was blocked, was blocked by Microsoft + +Here's a list of all domains that blocked legitimate activation emails to their users: + + - btinternet.com + - hotmail.com + - hotmail.co.uk + - live.ca + - live.com + - live.com.au + - live.nl + - msn.com + - outlook.com + +Apart from that very first entry in the list (on which only 1 message was blocked) all of these are Microsoft domains. + +Let me restate that: Apart from the 1 outlier, every message that was blocked, was blocked by Microsoft. + +## What's the impact? + +So what sort of impact does that have on people? + +Well, at the time I'm writing this, there are 817 registered users, and about 80% (661) have also activated their account. + +![A disproportionate amount of pending activations is from users with an email address managed by Microsoft](https://posts.freesewing.org/uploads/activations_06987b6065.svg) + +From those people who were able to activate their account, less than 1% (6) have an email address managed by Microsoft. +In the group of people who did not, or were not able to, activate their account, more than half have such an address. + +More than 40% of account confirmation emails are simply blocked by Microsoft and, based on the number of activations, +it seems likely that even when they aren't block at the SMTP relay, they get filtered somewhere further down the line. + +As things stand, it seems almost impossible for the average hotmail/outlook/live/MSN/... user to sign up for this site. + +## What can we do about it? + +I chose mailgun for a number of reasons. Not having to handle SMTP outselves simplifies the code. +Not depending on a local SMTP deamon makes the code more portable, and MailGun has a bunch of cool features +that allow you to do things like replying to comments via email. + +Microsoft's crude methods of spam filtering don't invalidate any of those reasons. + +Using MailGun means using their SMTP relays, and being at the mercy of the reputation of that relay. +The only way around that is to configure a dedicated relay in MailGun so that freesewing.org traffic is shielded from +others, and we become masters of our own reputation. + +![$59 per month? Perhaps not](https://posts.freesewing.org/uploads/pricing_52f0e817cb.png) + +For that priviledge, MailGun charges 59 dollar per month, which amounts to 708 dollar yearly. +I invite you to take a look at [the donations history](/about/pledge#donations-history), +and you'll understand that's not going to happen either. + +I could challenge the block list, and try to get the relay unblocked. +But that's pretty much tilting at windmills when the host is not under my control. +Not to mention that MailGun doesn't just have that one host. + +It seems that I'm running low on options and quiet frankly, I'm also running out of patience. + +## What I'm going to do about it + +Microsoft is a behemoth, and I'm just a guy. I can't fight them on this. +Unless I Titanfall their ass. + +![Block this, bitch](https://posts.freesewing.org/uploads/titanfall_cb5a210468.gif) + +Do you think Gmail is ever abused to send out spam? You know it is. +Do you think they would ever block all email coming from Gmail? You know they won't. + +So last night, I rolled out some changes to work around the issue. +If you have a *problemtic* email address, in addition to the regular email, this site will send out +a second email through Gmail. + +I'd like to see them block that. + +> ##### Signup trouble? Help is available +> If you are (still) having problems signing up, don't hesitate to [get in touch](/contact). + diff --git a/markdown/org/blog/email-spam-problems/fr.md b/markdown/org/blog/email-spam-problems/fr.md new file mode 100644 index 00000000000..1d2b78fff67 --- /dev/null +++ b/markdown/org/blog/email-spam-problems/fr.md @@ -0,0 +1,138 @@ +--- +author: "joostdecock" +caption: "Would you close a lane because one driver was playing their music too loud?" +date: "2017-09-07" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/923cd5587c873d2662df4a804f75f8f32b5673ca-1920x1281.jpg" +intro: "Thanks for nothing Microsoft; Email shouldn't be this hard [Non traduit]" +title: "Thanks for nothing Microsoft; Email shouldn't be this hard [Non traduit]" +--- + +People with an email address from Microsoft --- think Hotmail, MSN, live.com, outlook.com and their numerous variants --- +are significantly less likely to sign up for this website. + +That's because more than 4 times out of 10, they never receive their account activation email. + +## What's going on? + +Let's first look at what's happening. Here's a relevant snippet from the logs: + +```` +Failed: postmaster@mg.freesewing.org -> ********@hotmail.co.uk 'Confirm your freesewing account' +Server response: 550 5.7.1 Unfortunately, messages from [104.130.122.15] weren't sent. +Please contact your Internet service provider since part of their network is on our block list. +```` + +What this means is that part of the MailGun network is on their block list. +As a result, they (more on who they are later) are not delivering any messages that go out. + +[MailGun](https://www.mailgun.com/) is a popular email service for developers. +It's used by this site to send out emails, like the account activation emails. + +Other people use this service too, and perhaps some of them, at some point, +delivered some spam messages through mailgun. Or it may just have been some guy with +a last name that tends to trigger spam filters. + +![Some other MailGun customers. Not exactly a dodgy service is it?](https://posts.freesewing.org/uploads/mailgun_19f315d4d6.png) + +Point is, this IP address or one of its neighbours got *a bad rep*. It happens. +But to flat-out refuse to accept any messages from this host (or an entire network of hosts) +is the equivalent of shutting down a highway lane (or entire highway) +because one car in that lane played its music obnoxiously loud that one time. + +Which brings me to our next question: + +## Who would do something like that? + +Good question. Here are some numbers: + +![A graph of mail delivery since the launch of this site](https://posts.freesewing.org/uploads/emailgraph_d14d476efa.png) + +The graph above represents emails that were sent out since the launch of this site. +The small subsection of the graph that is red are emails that are dropped. + +This website sends out different kinds of email: + + - The account confirmation email + - The *I forgot my password* emails + - Comment reply notifications + +The graph represents all email, but I'm focussing on the account confirmation emails only. +They are the most important after all. + +> Apart from the 1 outlier, every message that was blocked, was blocked by Microsoft + +Here's a list of all domains that blocked legitimate activation emails to their users: + + - btinternet.com + - hotmail.com + - hotmail.co.uk + - live.ca + - live.com + - live.com.au + - live.nl + - msn.com + - outlook.com + +Apart from that very first entry in the list (on which only 1 message was blocked) all of these are Microsoft domains. + +Let me restate that: Apart from the 1 outlier, every message that was blocked, was blocked by Microsoft. + +## What's the impact? + +So what sort of impact does that have on people? + +Well, at the time I'm writing this, there are 817 registered users, and about 80% (661) have also activated their account. + +![A disproportionate amount of pending activations is from users with an email address managed by Microsoft](https://posts.freesewing.org/uploads/activations_06987b6065.svg) + +From those people who were able to activate their account, less than 1% (6) have an email address managed by Microsoft. +In the group of people who did not, or were not able to, activate their account, more than half have such an address. + +More than 40% of account confirmation emails are simply blocked by Microsoft and, based on the number of activations, +it seems likely that even when they aren't block at the SMTP relay, they get filtered somewhere further down the line. + +As things stand, it seems almost impossible for the average hotmail/outlook/live/MSN/... user to sign up for this site. + +## What can we do about it? + +I chose mailgun for a number of reasons. Not having to handle SMTP outselves simplifies the code. +Not depending on a local SMTP deamon makes the code more portable, and MailGun has a bunch of cool features +that allow you to do things like replying to comments via email. + +Microsoft's crude methods of spam filtering don't invalidate any of those reasons. + +Using MailGun means using their SMTP relays, and being at the mercy of the reputation of that relay. +The only way around that is to configure a dedicated relay in MailGun so that freesewing.org traffic is shielded from +others, and we become masters of our own reputation. + +![$59 per month? Perhaps not](https://posts.freesewing.org/uploads/pricing_52f0e817cb.png) + +For that priviledge, MailGun charges 59 dollar per month, which amounts to 708 dollar yearly. +I invite you to take a look at [the donations history](/about/pledge#donations-history), +and you'll understand that's not going to happen either. + +I could challenge the block list, and try to get the relay unblocked. +But that's pretty much tilting at windmills when the host is not under my control. +Not to mention that MailGun doesn't just have that one host. + +It seems that I'm running low on options and quiet frankly, I'm also running out of patience. + +## What I'm going to do about it + +Microsoft is a behemoth, and I'm just a guy. I can't fight them on this. +Unless I Titanfall their ass. + +![Block this, bitch](https://posts.freesewing.org/uploads/titanfall_cb5a210468.gif) + +Do you think Gmail is ever abused to send out spam? You know it is. +Do you think they would ever block all email coming from Gmail? You know they won't. + +So last night, I rolled out some changes to work around the issue. +If you have a *problemtic* email address, in addition to the regular email, this site will send out +a second email through Gmail. + +I'd like to see them block that. + +> ##### Signup trouble? Help is available +> If you are (still) having problems signing up, don't hesitate to [get in touch](/contact). + diff --git a/markdown/org/blog/email-spam-problems/nl.md b/markdown/org/blog/email-spam-problems/nl.md new file mode 100644 index 00000000000..23078c9b8be --- /dev/null +++ b/markdown/org/blog/email-spam-problems/nl.md @@ -0,0 +1,138 @@ +--- +author: "joostdecock" +caption: "Would you close a lane because one driver was playing their music too loud?" +date: "2017-09-07" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/923cd5587c873d2662df4a804f75f8f32b5673ca-1920x1281.jpg" +intro: "Thanks for nothing Microsoft; Email shouldn't be this hard [Niet vertaald]" +title: "Thanks for nothing Microsoft; Email shouldn't be this hard [Niet vertaald]" +--- + +People with an email address from Microsoft --- think Hotmail, MSN, live.com, outlook.com and their numerous variants --- +are significantly less likely to sign up for this website. + +That's because more than 4 times out of 10, they never receive their account activation email. + +## What's going on? + +Let's first look at what's happening. Here's a relevant snippet from the logs: + +```` +Failed: postmaster@mg.freesewing.org -> ********@hotmail.co.uk 'Confirm your freesewing account' +Server response: 550 5.7.1 Unfortunately, messages from [104.130.122.15] weren't sent. +Please contact your Internet service provider since part of their network is on our block list. +```` + +What this means is that part of the MailGun network is on their block list. +As a result, they (more on who they are later) are not delivering any messages that go out. + +[MailGun](https://www.mailgun.com/) is a popular email service for developers. +It's used by this site to send out emails, like the account activation emails. + +Other people use this service too, and perhaps some of them, at some point, +delivered some spam messages through mailgun. Or it may just have been some guy with +a last name that tends to trigger spam filters. + +![Some other MailGun customers. Not exactly a dodgy service is it?](https://posts.freesewing.org/uploads/mailgun_19f315d4d6.png) + +Point is, this IP address or one of its neighbours got *a bad rep*. It happens. +But to flat-out refuse to accept any messages from this host (or an entire network of hosts) +is the equivalent of shutting down a highway lane (or entire highway) +because one car in that lane played its music obnoxiously loud that one time. + +Which brings me to our next question: + +## Who would do something like that? + +Good question. Here are some numbers: + +![A graph of mail delivery since the launch of this site](https://posts.freesewing.org/uploads/emailgraph_d14d476efa.png) + +The graph above represents emails that were sent out since the launch of this site. +The small subsection of the graph that is red are emails that are dropped. + +This website sends out different kinds of email: + + - The account confirmation email + - The *I forgot my password* emails + - Comment reply notifications + +The graph represents all email, but I'm focussing on the account confirmation emails only. +They are the most important after all. + +> Apart from the 1 outlier, every message that was blocked, was blocked by Microsoft + +Here's a list of all domains that blocked legitimate activation emails to their users: + + - btinternet.com + - hotmail.com + - hotmail.co.uk + - live.ca + - live.com + - live.com.au + - live.nl + - msn.com + - outlook.com + +Apart from that very first entry in the list (on which only 1 message was blocked) all of these are Microsoft domains. + +Let me restate that: Apart from the 1 outlier, every message that was blocked, was blocked by Microsoft. + +## What's the impact? + +So what sort of impact does that have on people? + +Well, at the time I'm writing this, there are 817 registered users, and about 80% (661) have also activated their account. + +![A disproportionate amount of pending activations is from users with an email address managed by Microsoft](https://posts.freesewing.org/uploads/activations_06987b6065.svg) + +From those people who were able to activate their account, less than 1% (6) have an email address managed by Microsoft. +In the group of people who did not, or were not able to, activate their account, more than half have such an address. + +More than 40% of account confirmation emails are simply blocked by Microsoft and, based on the number of activations, +it seems likely that even when they aren't block at the SMTP relay, they get filtered somewhere further down the line. + +As things stand, it seems almost impossible for the average hotmail/outlook/live/MSN/... user to sign up for this site. + +## What can we do about it? + +I chose mailgun for a number of reasons. Not having to handle SMTP outselves simplifies the code. +Not depending on a local SMTP deamon makes the code more portable, and MailGun has a bunch of cool features +that allow you to do things like replying to comments via email. + +Microsoft's crude methods of spam filtering don't invalidate any of those reasons. + +Using MailGun means using their SMTP relays, and being at the mercy of the reputation of that relay. +The only way around that is to configure a dedicated relay in MailGun so that freesewing.org traffic is shielded from +others, and we become masters of our own reputation. + +![$59 per month? Perhaps not](https://posts.freesewing.org/uploads/pricing_52f0e817cb.png) + +For that priviledge, MailGun charges 59 dollar per month, which amounts to 708 dollar yearly. +I invite you to take a look at [the donations history](/about/pledge#donations-history), +and you'll understand that's not going to happen either. + +I could challenge the block list, and try to get the relay unblocked. +But that's pretty much tilting at windmills when the host is not under my control. +Not to mention that MailGun doesn't just have that one host. + +It seems that I'm running low on options and quiet frankly, I'm also running out of patience. + +## What I'm going to do about it + +Microsoft is a behemoth, and I'm just a guy. I can't fight them on this. +Unless I Titanfall their ass. + +![Block this, bitch](https://posts.freesewing.org/uploads/titanfall_cb5a210468.gif) + +Do you think Gmail is ever abused to send out spam? You know it is. +Do you think they would ever block all email coming from Gmail? You know they won't. + +So last night, I rolled out some changes to work around the issue. +If you have a *problemtic* email address, in addition to the regular email, this site will send out +a second email through Gmail. + +I'd like to see them block that. + +> ##### Signup trouble? Help is available +> If you are (still) having problems signing up, don't hesitate to [get in touch](/contact). + diff --git a/markdown/org/blog/facemask-frenzy/de.md b/markdown/org/blog/facemask-frenzy/de.md new file mode 100644 index 00000000000..bfebadc5e72 --- /dev/null +++ b/markdown/org/blog/facemask-frenzy/de.md @@ -0,0 +1,42 @@ +--- +author: "joostdecock" +caption: "Dr. Dragnea from Antwerp University hospital wearing a Florence facemask" +date: "2020-03-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b811b79114f15aa192a1962b95083e6c55d79402-1532x1123.jpg" +intro: "Calling all makers: Here's a 1-page PDF facemask pattern; Now go make some and help beat this thing [Nicht übersetzt]" +title: "Calling all makers: Here's a 1-page PDF facemask pattern; Now go make some and help beat this thing [Nicht übersetzt]" +--- + + + + +**TL;DR: Please make facemasks for healthcare workers** + + + - PDF pattern for our Florence face mask: + - [A4 facemask pattern](/florence-facemask-freesewing.org.a4.pdf) + - [Letter facemask pattern](/florence-facemask-freesewing.org.letter.pdf) + - [Instructions for the facemask pattern](/docs/patterns/florence/instructions/) + + + + + +Well that escalated quickly. +We published [our Florence Face Mask pattern](/designs/florence/) at the end of last month, hoping it would be helpful. +Now, [hospitals are actively reaching out to people to beg them to make fabric face masks for their staff](https://www.uza.be/mondmaskers). + +So obviously, we want to help: + + - PDF pattern for our Florence face mask: + - [A4 facemask pattern](/florence-facemask-freesewing.org.a4.pdf) + - [Letter facemask pattern](/florence-facemask-freesewing.org.letter.pdf) + - [Instructions for the facemask pattern](/docs/patterns/florence/instructions/) + +No go and make a bunch. Our healthcare workers are counting on you! + + + +PS: You can support us by [becoming a patron](/patrons/join/) ❤️ + + diff --git a/markdown/org/blog/facemask-frenzy/en.md b/markdown/org/blog/facemask-frenzy/en.md new file mode 100644 index 00000000000..78f74d3b694 --- /dev/null +++ b/markdown/org/blog/facemask-frenzy/en.md @@ -0,0 +1,42 @@ +--- +author: "joostdecock" +caption: "Dr. Dragnea from Antwerp University hospital wearing a Florence facemask" +date: "2020-03-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b811b79114f15aa192a1962b95083e6c55d79402-1532x1123.jpg" +intro: "Calling all makers: Here's a 1-page PDF facemask pattern; Now go make some and help beat this thing" +title: "Calling all makers: Here's a 1-page PDF facemask pattern; Now go make some and help beat this thing" +--- + + + + +**TL;DR: Please make facemasks for healthcare workers** + + + - PDF pattern for our Florence face mask: + - [A4 facemask pattern](/florence-facemask-freesewing.org.a4.pdf) + - [Letter facemask pattern](/florence-facemask-freesewing.org.letter.pdf) + - [Instructions for the facemask pattern](/docs/patterns/florence/instructions/) + + + + + +Well that escalated quickly. +We published [our Florence Face Mask pattern](/designs/florence/) at the end of last month, hoping it would be helpful. +Now, [hospitals are actively reaching out to people to beg them to make fabric face masks for their staff](https://www.uza.be/mondmaskers). + +So obviously, we want to help: + + - PDF pattern for our Florence face mask: + - [A4 facemask pattern](/florence-facemask-freesewing.org.a4.pdf) + - [Letter facemask pattern](/florence-facemask-freesewing.org.letter.pdf) + - [Instructions for the facemask pattern](/docs/patterns/florence/instructions/) + +No go and make a bunch. Our healthcare workers are counting on you! + + + +PS: You can support us by [becoming a patron](/patrons/join/) ❤️ + + diff --git a/markdown/org/blog/facemask-frenzy/es.md b/markdown/org/blog/facemask-frenzy/es.md new file mode 100644 index 00000000000..35b56e9cf42 --- /dev/null +++ b/markdown/org/blog/facemask-frenzy/es.md @@ -0,0 +1,42 @@ +--- +author: "joostdecock" +caption: "Dr. Dragnea from Antwerp University hospital wearing a Florence facemask" +date: "2020-03-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b811b79114f15aa192a1962b95083e6c55d79402-1532x1123.jpg" +intro: "Llamando a todos los creadores: Aquí hay un patrón de mascarilla en un PDF de una página, ve a hacer algunas y ayuda a vencer este bicho" +title: "Llamando a todos los creadores: Aquí hay un patrón de mascarilla en un PDF de una página, ve a hacer algunas y ayuda a vencer este bicho" +--- + + + + +**TL;DR: Please make facemasks for healthcare workers** + + + - PDF pattern for our Florence face mask: + - [A4 facemask pattern](/florence-facemask-freesewing.org.a4.pdf) + - [Letter facemask pattern](/florence-facemask-freesewing.org.letter.pdf) + - [Instructions for the facemask pattern](/docs/patterns/florence/instructions/) + + + + + +Bueno, eso se intensificó rápidamente. We published [our Florence Face Mask pattern](/designs/florence/) at the end of last month, hoping it would be helpful. Ahora, [algunos hospitales están pidiendo activamente a la gente que hagan máscaras de tela para su personal](https://www.uza.be/mondmaskers). + +Por lo tanto, obviamente, queremos ayudar: + + - PDF pattern for our Florence face mask: + - [Patrón de mascarilla A4](/florence-facemask-freesewing.org.a4.pdf) + - [Patrón de mascarilla letter](/florence-facemask-freesewing.org.letter.pdf) + - [Instrucciones para el patrón de la mascarilla](/docs/patterns/florence/instructions/) + +Ahora ve a hacer un montón. ¡Nuestros profesionales de la salud cuentan contigo! + + + +PD: Puedes apoyarnos [convirtiéndote en patrocinador](/patrons/join/) ❤ + + + + diff --git a/markdown/org/blog/facemask-frenzy/fr.md b/markdown/org/blog/facemask-frenzy/fr.md new file mode 100644 index 00000000000..6fedcc90f42 --- /dev/null +++ b/markdown/org/blog/facemask-frenzy/fr.md @@ -0,0 +1,42 @@ +--- +author: "joostdecock" +caption: "Dr. Dragnea, de l'hôpital universitaire d'Anvers, portant le masque facial Florence" +date: "2020-03-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b811b79114f15aa192a1962b95083e6c55d79402-1532x1123.jpg" +intro: "Appel à tous : voici un patron de masque facial PDF en 1 page ; fabriquez-en quelques uns et aidez à vaincre cette chose" +title: "Appel à tous : voici un patron de masque facial PDF en 1 page ; fabriquez-en quelques uns et aidez à vaincre cette chose" +--- + + + + +**TL;DR: S'il vous plait, faites des masques pour les personnels de la santé** + + + - Patron PDF de notre masque Florence : + - [patron format A4](/florence-facemask-freesewing.org.a4.fr.pdf) + - [patron format Lettre](/florence-facemask-freesewing.org.letter.fr.pdf) + - [Instructions pour la réalisation du masque](/docs/patterns/florence/instructions/) + + + + + +Les choses s'accélèrent. Nous avons publié [notre masque Florence](/designs/florence/) à la fin du mois dernier, en espérant qu'il serait utile. Maintenant, [les hôpitaux contactent activement le public et le sollicite pour la fabrication de masques en tissu pour leur personnel](https://www.uza.be/mondmaskers). + +Alors, évidemment, nous voulons aider : + + - Patron PDF pour notre masque Florence : + - [Patron du masque en format A4](/florence-facemask-freesewing.org.a4.fr.pdf) + - [Patron du masque en format Lettre](/florence-facemask-freesewing.org.letter.fr.pdf) + - [Instructions pour la réalisation du masque facial](/docs/patterns/florence/instructions/) + +Maintenant, lancez-vous et faites-en une série. Nos professionnels de la santé comptent sur vous ! + + + +PS: Vous pouvez nous soutenir en [devenant un mécène](/patrons/join/) ❤ + + + + diff --git a/markdown/org/blog/facemask-frenzy/nl.md b/markdown/org/blog/facemask-frenzy/nl.md new file mode 100644 index 00000000000..ba4f93d2d6a --- /dev/null +++ b/markdown/org/blog/facemask-frenzy/nl.md @@ -0,0 +1,41 @@ +--- +author: "joostdecock" +caption: "Dr. Dragnea van het Universitair Ziekenhuis Antwerpen met een Florence mondmasker" +date: "2020-03-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b811b79114f15aa192a1962b95083e6c55d79402-1532x1123.jpg" +intro: "Oproep aan alle makers: Hier is een PDF patroon voor een mondmasker; Laten we samen aan de slag gaan" +title: "Oproep aan alle makers: Hier is een PDF patroon voor een mondmasker; Laten we samen aan de slag gaan" +--- + + + + +**TL;DR: Maak alsjeblieft mondmaskers voor werkers in de gezondheidszorg** + +- PDF-patroon voor ons Florence mondmasker: +- [A4 mondmasker patroon](/florence-facemask-freesewing.org.a4.pdf) +- [US Letter mondmasker patroon](/florence-facemask-freesewing.org.letter.pdf) +- [Instructies voor het mondmasker](/docs/patterns/florence/instructions/) + + + + + +Wel dat ging snel. We hebben ons [Florence mondmasker patroon](/designs/florence/) eind maart gepubliceerd, in de hoop dat het nuttig zou zijn. Nu [roepen ziekenhuizen op](https://www.uza.be/mondmaskers) om massaal mond maskers te maken voor hun personeel. + +Dus uiteraard willen we daarbij helpen: + + - PDF-patroon voor ons Florence mondmasker: + - [A4 mondmasker patroon](/florence-facemask-freesewing.org.a4.pdf) + - [US Letter mondmasker patroon](/florence-facemask-freesewing.org.letter.pdf) + - [Instructies voor het patroon](/docs/patterns/florence/instructions/) + +Tijd om er een stapel te maken. Onze gezondheidszorg werkers rekenen op je! + + + +PS: You can support us by [becoming a patron](/patrons/join/) ❤️ + + + + diff --git a/markdown/org/blog/florence-face-mask/de.md b/markdown/org/blog/florence-face-mask/de.md new file mode 100644 index 00000000000..a6d31b554c8 --- /dev/null +++ b/markdown/org/blog/florence-face-mask/de.md @@ -0,0 +1,28 @@ +--- +author: "joostdecock" +caption: "Halten Sie diese mit Viren infizierten Tröpfchen mit unserer Florence-Gesichtsmaske in Schach" +date: "2020-02-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d2235dcc38012e87ac402d43e7ae7084a7d7e9b4-1920x1272.jpg" +intro: "Die Ausbreitung des Coronavirus Covid-19 scheint unerbittlich zu sein, und trotz der besten Versuche weltweit wird die Möglichkeit einer globalen Pandemie von Tag zu Tag realer. Das wirft die Frage auf, was wir tun können?" +title: "Wir haben gerade ein Gesichtsmaskenmuster wegen des Coronavirus veröffentlicht" +--- + + + +Die Ausbreitung des Coronavirus Covid-19 scheint unerbittlich zu sein, und trotz der besten Versuche weltweit wird die Möglichkeit einer globalen Pandemie von Tag zu Tag realer. Das wirft die Frage auf, was wir tun können? + +Vielleicht nicht viel, aber wir können Schnittmuster entwerfen. Sagen Sie also hallo zur [Gesichtsmaske "Florence"](/designs/florence/), ein einfaches Schnittmuster, mit dem Sie Ihre eigenen Gesichtsmasken anfertigen können. Eine, die man den ganzen Tag tragen kann, denn diese medizinischen Geräte sind nicht gerade bequem. + +Ob eine Gesichtsmaske tatsächlich hilft, ist Gegenstand einer Diskussion. Ich habe ein bisschen hin und her über die Frage nachgedacht, ob ich ein Schnittmuster für eine Gesichtsmaske veröffentlichen soll. Dann - heute früh - las ich einen [Guardian](https://www.theguardian.com/) Artikel namens [Ja, es ist schlimmer als die Grippe: die Auflösung der Coronavirus-Mythen](https://www.theguardian.com/world/2020/feb/28/coronavirus-truth-myths-flu-covid-19-face-masks). Sie enthielt die folgende Passage unter dem Mythos *Gesichtsmasken funktionieren nicht*: + +> ###### Behauptung: 'Gesichtsmasken funktionieren nicht' +> +> *Das Tragen einer Gesichtsmaske ist keine sichere Garantie dafür, dass man nicht krank wird - Viren können auch durch die Augen übertragen werden, und winzige Viruspartikel, so genannte Aerosol-Partikel, können dennoch in Masken eindringen. Masken sind jedoch wirksam beim Auffangen von Tröpfchen, dem Hauptübertragungsweg des Coronavirus, und einige Studien haben einen etwa fünffachen Schutz gegenüber keiner Barriere geschätzt. Wenn Sie wahrscheinlich in engem Kontakt mit einer infizierten Person stehen, verringert eine Maske die Wahrscheinlichkeit, dass die Krankheit weitergegeben wird.* + +Damit soll lediglich verhindert werden, dass Sie das Coronavirus bekommen. Es gibt auch die Tatsache, dass die Maske (ein bisschen) helfen kann, die Verbreitung von Corona zu verhindern. Denn so wie die Dinge im Moment laufen, sollten wir wohl jede Kleinigkeit tun, um die Sache zu verlangsamen. + +Als ich nach Hause kam, machte ich mich also auf den Weg, um ein Schnittmuster für eine Gesichtsmaske zu erstellen. Der gesunde Menschenverstand sagt, dass es nicht schaden kann, und anscheinend steckt auch mehr dahinter. Nicht zuletzt möchte ich eine süße Gesichtsmaske, nicht eine der hässlichen, die man in den Nachrichten sieht. + +Bleiben Sie sicher da draußen. + + diff --git a/markdown/org/blog/florence-face-mask/en.md b/markdown/org/blog/florence-face-mask/en.md new file mode 100644 index 00000000000..1b820e1afe2 --- /dev/null +++ b/markdown/org/blog/florence-face-mask/en.md @@ -0,0 +1,37 @@ +--- +author: "joostdecock" +caption: "Keep those virus-infesed droplets at bay with our Florence face mask" +date: "2020-02-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d2235dcc38012e87ac402d43e7ae7084a7d7e9b4-1920x1272.jpg" +intro: "We just published a face mask pattern, because coronavirus" +title: "We just published a face mask pattern, because coronavirus" +--- + + + +The spread of the Covid-19 coronavirus seems relentless and despite the world's best attempts, +the possibility of a global pandemic is getting more real every day. Which begs the question, what can we do? + +Perhaps not much, but we can design patterns. So say hi to the [Florence face mask](/designs/florence/), +a simple pattern that allows you make your own face masks. One that you can wear all day, +because those medical ones aren't exactly comfortable. + +Whether or not a face mask actually helps is subject of debate. +I've been to-ing and fro-ing a bit about whether to publish a pattern for a face mask. +Then — earlier today — I read a [Guardian](https://www.theguardian.com/) article +called [Yes, it is worse than the flu: busting the coronavirus myths](https://www.theguardian.com/world/2020/feb/28/coronavirus-truth-myths-flu-covid-19-face-masks). +It included the following passage under the *Face masks don’t work* myth: + +> ###### Claim: ‘Face masks don’t work’ +> +> *Wearing a face mask is not an iron clad guarantee that you won’t get sick – viruses can also transmit through the eyes and tiny viral particles, known as aerosols, can still penetrate masks. However, masks are effective at capturing droplets, which is the main transmission route of coronavirus, and some studies have estimated a roughly five-fold protection versus no barrier. If you are likely to be in close contact with someone infected, a mask cuts the chance of the disease being passed on.* + +This only focusses on preventing you from getting coronavirus. +There's also the fact that the mask can help (a bit) in keeping you from spreading it further. +Because the way things are going right now, it looks like we should do every little thing we can to try to slow this thing down. + +So when I got home, I set out to rush out a face mask pattern. Common sense says it can't hurt, and apparently there's more to it too. +If nothing else, I want a cute face mask, not one of the ugly ones you see on the news. + +Stay safe out there. + diff --git a/markdown/org/blog/florence-face-mask/es.md b/markdown/org/blog/florence-face-mask/es.md new file mode 100644 index 00000000000..faf638e17a9 --- /dev/null +++ b/markdown/org/blog/florence-face-mask/es.md @@ -0,0 +1,37 @@ +--- +author: "joostdecock" +caption: "Keep those virus-infesed droplets at bay with our Florence face mask" +date: "2020-02-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d2235dcc38012e87ac402d43e7ae7084a7d7e9b4-1920x1272.jpg" +intro: "We just published a face mask pattern, because coronavirus [No traducido]" +title: "We just published a face mask pattern, because coronavirus [No traducido]" +--- + + + +The spread of the Covid-19 coronavirus seems relentless and despite the world's best attempts, +the possibility of a global pandemic is getting more real every day. Which begs the question, what can we do? + +Perhaps not much, but we can design patterns. So say hi to the [Florence face mask](/designs/florence/), +a simple pattern that allows you make your own face masks. One that you can wear all day, +because those medical ones aren't exactly comfortable. + +Whether or not a face mask actually helps is subject of debate. +I've been to-ing and fro-ing a bit about whether to publish a pattern for a face mask. +Then — earlier today — I read a [Guardian](https://www.theguardian.com/) article +called [Yes, it is worse than the flu: busting the coronavirus myths](https://www.theguardian.com/world/2020/feb/28/coronavirus-truth-myths-flu-covid-19-face-masks). +It included the following passage under the *Face masks don’t work* myth: + +> ###### Claim: ‘Face masks don’t work’ +> +> *Wearing a face mask is not an iron clad guarantee that you won’t get sick – viruses can also transmit through the eyes and tiny viral particles, known as aerosols, can still penetrate masks. However, masks are effective at capturing droplets, which is the main transmission route of coronavirus, and some studies have estimated a roughly five-fold protection versus no barrier. If you are likely to be in close contact with someone infected, a mask cuts the chance of the disease being passed on.* + +This only focusses on preventing you from getting coronavirus. +There's also the fact that the mask can help (a bit) in keeping you from spreading it further. +Because the way things are going right now, it looks like we should do every little thing we can to try to slow this thing down. + +So when I got home, I set out to rush out a face mask pattern. Common sense says it can't hurt, and apparently there's more to it too. +If nothing else, I want a cute face mask, not one of the ugly ones you see on the news. + +Stay safe out there. + diff --git a/markdown/org/blog/florence-face-mask/fr.md b/markdown/org/blog/florence-face-mask/fr.md new file mode 100644 index 00000000000..67f815c57c7 --- /dev/null +++ b/markdown/org/blog/florence-face-mask/fr.md @@ -0,0 +1,28 @@ +--- +author: "joostdecock" +caption: "Retenez les gouttelettes infestées de virus avec notre masque Florence" +date: "2020-02-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d2235dcc38012e87ac402d43e7ae7084a7d7e9b4-1920x1272.jpg" +intro: "La propagation du coronavirus Covid-19 semble inéluctable et malgré les meilleures tentatives du monde, la possibilité d'une pandémie mondiale devient de plus en plus réelle chaque jour. D'où la question : que peut-on faire ?" +title: "Nous venons de publier un patron de masque facial, en raison du coronavirus" +--- + + + +La propagation du coronavirus Covid-19 semble inéluctable et malgré les meilleures tentatives du monde, la possibilité d'une pandémie mondiale devient de plus en plus réelle chaque jour. D'où la question : que peut-on faire ? + +Même si c'est peu, nous pouvons concevoir des patrons. Alors dites bonjour au [masque facial Florence](/designs/florence/), un patron simple qui vous permet de créer vos propres masques. Un masque que vous pouvez porter toute la journée, parce que les masques médicaux ne sont pas vraiment confortables. + +La question de savoir si un masque protège réellement est débattue. J'ai un peu tergiversé avant de publier un patron de masque facial. Puis — un peu plus tôt aujourd'hui — j'ai lu un article [du Guardian](https://www.theguardian.com/) appelé [Oui, c'est pire que la grippe: bousculer les mythes coronavirus](https://www.theguardian.com/world/2020/feb/28/coronavirus-truth-myths-flu-covid-19-face-masks). Il incluait le passage suivant "*les masques de visage ne fonctionnent pas* ": + +> ###### Affirmation : «Les masques de visage ne fonctionnent pas» +> +> *Porter un masque facial ne garantit pas que vous ne serez pas malade - les virus peuvent également se transmettre à travers les yeux, et les minuscules particules virales, connues sous le nom d'aérosols, peuvent pénétrer à travers les masques. Cependant, les masques capturent efficacement les gouttelettes, principale voie de transmission du coronavirus, et certaines études ont estimé que les masques protégeaient environ cinq fois plus que s'il n' existait aucune barrière. Si vous êtes susceptible d'être en contact étroit avec une personne infectée, un masque réduit le risque de transmission de la maladie.* + +Cela ne concerne que les modalités permettant d'empêcher de se contaminer par le coronavirus. D'autre part, le masque peut aider (un peu) à empêcher une personne infectée de disséminer le virus. Dans le contexte actuel, il semble utile de faire toutes les petites actions possibles pour essayer de ralentir ce phénomène. + +Alors quand je suis rentré chez moi, je me suis précipité pour travailler sur un patron de masque facial. Le bon sens dit que ça ne peut pas faire de mal, et peut être est ce utile. Faute de mieux, je veux un joli masque, pas une de ces horreurs qu'on voit aux informations. + +Prenez soin de vous. + + diff --git a/markdown/org/blog/florence-face-mask/nl.md b/markdown/org/blog/florence-face-mask/nl.md new file mode 100644 index 00000000000..dff1192591d --- /dev/null +++ b/markdown/org/blog/florence-face-mask/nl.md @@ -0,0 +1,37 @@ +--- +author: "joostdecock" +caption: "Keep those virus-infesed droplets at bay with our Florence face mask" +date: "2020-02-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d2235dcc38012e87ac402d43e7ae7084a7d7e9b4-1920x1272.jpg" +intro: "We just published a face mask pattern, because coronavirus [Niet vertaald]" +title: "We just published a face mask pattern, because coronavirus [Niet vertaald]" +--- + + + +The spread of the Covid-19 coronavirus seems relentless and despite the world's best attempts, +the possibility of a global pandemic is getting more real every day. Which begs the question, what can we do? + +Perhaps not much, but we can design patterns. So say hi to the [Florence face mask](/designs/florence/), +a simple pattern that allows you make your own face masks. One that you can wear all day, +because those medical ones aren't exactly comfortable. + +Whether or not a face mask actually helps is subject of debate. +I've been to-ing and fro-ing a bit about whether to publish a pattern for a face mask. +Then — earlier today — I read a [Guardian](https://www.theguardian.com/) article +called [Yes, it is worse than the flu: busting the coronavirus myths](https://www.theguardian.com/world/2020/feb/28/coronavirus-truth-myths-flu-covid-19-face-masks). +It included the following passage under the *Face masks don’t work* myth: + +> ###### Claim: ‘Face masks don’t work’ +> +> *Wearing a face mask is not an iron clad guarantee that you won’t get sick – viruses can also transmit through the eyes and tiny viral particles, known as aerosols, can still penetrate masks. However, masks are effective at capturing droplets, which is the main transmission route of coronavirus, and some studies have estimated a roughly five-fold protection versus no barrier. If you are likely to be in close contact with someone infected, a mask cuts the chance of the disease being passed on.* + +This only focusses on preventing you from getting coronavirus. +There's also the fact that the mask can help (a bit) in keeping you from spreading it further. +Because the way things are going right now, it looks like we should do every little thing we can to try to slow this thing down. + +So when I got home, I set out to rush out a face mask pattern. Common sense says it can't hurt, and apparently there's more to it too. +If nothing else, I want a cute face mask, not one of the ugly ones you see on the news. + +Stay safe out there. + diff --git a/markdown/org/blog/florent-flat-cap-beta/de.md b/markdown/org/blog/florent-flat-cap-beta/de.md new file mode 100644 index 00000000000..2d04d1b8407 --- /dev/null +++ b/markdown/org/blog/florent-flat-cap-beta/de.md @@ -0,0 +1,35 @@ +--- +author: "joostdecock" +caption: "Quentin umgeben von unseren zukünftigen Roboter-Overlords." +date: "2017-12-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ee5c11e3b29fe788dae470ab0e20396d806c4d1b-2000x1333.jpg" +intro: "Nach der Veröffentlichung von Benjamin im letzten Monat, gibt es hier eine weitere Schnittmuster-Freigabe, um den schlanken Gentleman zu kanalisieren: die Florent Flat Cap ." +title: "Das Schnittmuster der Schiebermütze Florent ist jetzt in der Beta-Version erhältlich. Da ist ein weiteres Geschenk erschienen." +--- + + +Nach der Veröffentlichung von [Benjamin](/patterns/benjamin) im letzten Monat, gibt es hier eine weitere Schnittmuster-Freigabe, um den schlanken Gentleman zu kanalisieren: die [Florent Flat Cap](/patterns/florent). + +Wie Benjamin wurde auch dieses Muster von der FreeSewing-Community und nicht von mir selbst erstellt. In diesem Fall war es [Quentin Felix](/users/ptzcb) der für das Design verantwortlich zeichnet. + +Ich fragte Quentin, ob er diesen Ankündigungsblogpost selbst schreiben wollte, aber er argumentierte, dass es an der Zeit sei, dass ich auch was tue. Es hat jedoch hier den Platz, aus welchen Gründen er das Schnittmuster überhaupt entworfen hat: + +> ##### Quentin zu seinen Gründen, warum er Florent entworfen hat +> +> Ich trage gerne selbst Schiebermützen. Das habe ich früher nicht, aber ich habe einen Freund Florent, der mich inspiriert hat, sie zu tragen (jetzt wißen Sie, woher der Name kommt). +> +> Als ich das erste Mal eine Schiebermütze herstellte, dauerte es ewig, bis ich das Muster passgenau skaliert hatte, wobei ich viel mit Transparentpapier herumbastelte. Es gibt eine Reihe von Schnittmuster für Schiebermützen, die online erhältlich sind. Aber sie sind alle nur in einer Größe erhältlich. +> +> Ich wollte das den Menschen zugänglicher machen. Und während ich dabei war, habe ich auch meine Erfahrung genutzt, um einige Optimierungen für eine bessere Passform vorzunehmen. +> +> Dieses Design erstreckt sich beispielsweise tiefer an der Rückseite des Kopfes, was ihm einen besseren Halt gibt. + +Dieses *warum sollten wir das Rad immer wieder neu erfinden müssen?* könnte so ziemlich der Slogan von FreeSewing sein. + +## Es ist die Zeit des Schenkens + +Florent benötigt nur eine Messung: den Kopfumfang. Somit ist diese Veröffentlichung genau zum richtigen Zeitpunkt erfolgt. Mit der bevorstehenden Weihnachtszeit, hier ist ein weiteres Geschenk, das Sie selbst machen können. + +Danke Quentin! + + diff --git a/markdown/org/blog/florent-flat-cap-beta/en.md b/markdown/org/blog/florent-flat-cap-beta/en.md new file mode 100644 index 00000000000..a01d61d7d5c --- /dev/null +++ b/markdown/org/blog/florent-flat-cap-beta/en.md @@ -0,0 +1,47 @@ +--- +author: "joostdecock" +caption: "Quentin surrounded by our future robot overlords." +date: "2017-12-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ee5c11e3b29fe788dae470ab0e20396d806c4d1b-2000x1333.jpg" +intro: "The Florent Flat Cap pattern is now available in beta. That's another gift sorted." +title: "The Florent Flat Cap pattern is now available in beta. That's another gift sorted." +--- + +After last month's release of [Benjamin](/patterns/benjamin), here's another pattern release +to channel the dapper gentleman within: the [Florent Flat Cap](/patterns/florent). + +Like Benjamin, this pattern was contributed by the freesewing community, rather than +yours truly. In this case, it was [Quentin Felix](/users/ptzcb) who signed for the design. + +I asked Quentin if he wanted to write this announcement blog post himself, +but he argued that it was time I did something too. He did have this to share +though, on his reasons for designing this pattern in the first place: + +> ##### Quentin on his reasons for designing Florent +> +> I like wearing flat caps myself. I didn't use to, but I have +> a friend Florent who inspired me to wear them (now you know where the name comes from). +> +> +> The first time I made a flat cap, it took me ages to scale the +> pattern to an exact fit, involving a lot of messing about with tracing paper. +> There's a number of patterns available online for flat caps. +> But they all come in one size only. +> +> I wanted to make this more accessible to people. And, while I was at it, +> I also drew on my experience to add some tweaks for a better fit. +> +> For example, this design extends lower at the back of the head, which +> gives it better hold. + +This *why should we always have to re-invent the wheel?* could +pretty much be freesewing's slogan. + +## It's the season for giving + +Florent requires only one measurement: the head circumference. As such, +this release is perfectly timed. With the holiday season coming up, +here's another gift you can make yourself. + +Thanks Quentin! + diff --git a/markdown/org/blog/florent-flat-cap-beta/es.md b/markdown/org/blog/florent-flat-cap-beta/es.md new file mode 100644 index 00000000000..388e5ad381c --- /dev/null +++ b/markdown/org/blog/florent-flat-cap-beta/es.md @@ -0,0 +1,47 @@ +--- +author: "joostdecock" +caption: "Quentin surrounded by our future robot overlords." +date: "2017-12-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ee5c11e3b29fe788dae470ab0e20396d806c4d1b-2000x1333.jpg" +intro: "The Florent Flat Cap pattern is now available in beta. That's another gift sorted. [No traducido]" +title: "The Florent Flat Cap pattern is now available in beta. That's another gift sorted. [No traducido]" +--- + +After last month's release of [Benjamin](/patterns/benjamin), here's another pattern release +to channel the dapper gentleman within: the [Florent Flat Cap](/patterns/florent). + +Like Benjamin, this pattern was contributed by the freesewing community, rather than +yours truly. In this case, it was [Quentin Felix](/users/ptzcb) who signed for the design. + +I asked Quentin if he wanted to write this announcement blog post himself, +but he argued that it was time I did something too. He did have this to share +though, on his reasons for designing this pattern in the first place: + +> ##### Quentin on his reasons for designing Florent +> +> I like wearing flat caps myself. I didn't use to, but I have +> a friend Florent who inspired me to wear them (now you know where the name comes from). +> +> +> The first time I made a flat cap, it took me ages to scale the +> pattern to an exact fit, involving a lot of messing about with tracing paper. +> There's a number of patterns available online for flat caps. +> But they all come in one size only. +> +> I wanted to make this more accessible to people. And, while I was at it, +> I also drew on my experience to add some tweaks for a better fit. +> +> For example, this design extends lower at the back of the head, which +> gives it better hold. + +This *why should we always have to re-invent the wheel?* could +pretty much be freesewing's slogan. + +## It's the season for giving + +Florent requires only one measurement: the head circumference. As such, +this release is perfectly timed. With the holiday season coming up, +here's another gift you can make yourself. + +Thanks Quentin! + diff --git a/markdown/org/blog/florent-flat-cap-beta/fr.md b/markdown/org/blog/florent-flat-cap-beta/fr.md new file mode 100644 index 00000000000..4a81b0421e8 --- /dev/null +++ b/markdown/org/blog/florent-flat-cap-beta/fr.md @@ -0,0 +1,47 @@ +--- +author: "joostdecock" +caption: "Quentin surrounded by our future robot overlords." +date: "2017-12-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ee5c11e3b29fe788dae470ab0e20396d806c4d1b-2000x1333.jpg" +intro: "The Florent Flat Cap pattern is now available in beta. That's another gift sorted. [Non traduit]" +title: "The Florent Flat Cap pattern is now available in beta. That's another gift sorted. [Non traduit]" +--- + +After last month's release of [Benjamin](/patterns/benjamin), here's another pattern release +to channel the dapper gentleman within: the [Florent Flat Cap](/patterns/florent). + +Like Benjamin, this pattern was contributed by the freesewing community, rather than +yours truly. In this case, it was [Quentin Felix](/users/ptzcb) who signed for the design. + +I asked Quentin if he wanted to write this announcement blog post himself, +but he argued that it was time I did something too. He did have this to share +though, on his reasons for designing this pattern in the first place: + +> ##### Quentin on his reasons for designing Florent +> +> I like wearing flat caps myself. I didn't use to, but I have +> a friend Florent who inspired me to wear them (now you know where the name comes from). +> +> +> The first time I made a flat cap, it took me ages to scale the +> pattern to an exact fit, involving a lot of messing about with tracing paper. +> There's a number of patterns available online for flat caps. +> But they all come in one size only. +> +> I wanted to make this more accessible to people. And, while I was at it, +> I also drew on my experience to add some tweaks for a better fit. +> +> For example, this design extends lower at the back of the head, which +> gives it better hold. + +This *why should we always have to re-invent the wheel?* could +pretty much be freesewing's slogan. + +## It's the season for giving + +Florent requires only one measurement: the head circumference. As such, +this release is perfectly timed. With the holiday season coming up, +here's another gift you can make yourself. + +Thanks Quentin! + diff --git a/markdown/org/blog/florent-flat-cap-beta/nl.md b/markdown/org/blog/florent-flat-cap-beta/nl.md new file mode 100644 index 00000000000..cd6d139c42b --- /dev/null +++ b/markdown/org/blog/florent-flat-cap-beta/nl.md @@ -0,0 +1,47 @@ +--- +author: "joostdecock" +caption: "Quentin surrounded by our future robot overlords." +date: "2017-12-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ee5c11e3b29fe788dae470ab0e20396d806c4d1b-2000x1333.jpg" +intro: "The Florent Flat Cap pattern is now available in beta. That's another gift sorted. [Niet vertaald]" +title: "The Florent Flat Cap pattern is now available in beta. That's another gift sorted. [Niet vertaald]" +--- + +After last month's release of [Benjamin](/patterns/benjamin), here's another pattern release +to channel the dapper gentleman within: the [Florent Flat Cap](/patterns/florent). + +Like Benjamin, this pattern was contributed by the freesewing community, rather than +yours truly. In this case, it was [Quentin Felix](/users/ptzcb) who signed for the design. + +I asked Quentin if he wanted to write this announcement blog post himself, +but he argued that it was time I did something too. He did have this to share +though, on his reasons for designing this pattern in the first place: + +> ##### Quentin on his reasons for designing Florent +> +> I like wearing flat caps myself. I didn't use to, but I have +> a friend Florent who inspired me to wear them (now you know where the name comes from). +> +> +> The first time I made a flat cap, it took me ages to scale the +> pattern to an exact fit, involving a lot of messing about with tracing paper. +> There's a number of patterns available online for flat caps. +> But they all come in one size only. +> +> I wanted to make this more accessible to people. And, while I was at it, +> I also drew on my experience to add some tweaks for a better fit. +> +> For example, this design extends lower at the back of the head, which +> gives it better hold. + +This *why should we always have to re-invent the wheel?* could +pretty much be freesewing's slogan. + +## It's the season for giving + +Florent requires only one measurement: the head circumference. As such, +this release is perfectly timed. With the holiday season coming up, +here's another gift you can make yourself. + +Thanks Quentin! + diff --git a/markdown/org/blog/freesewing-2-19/de.md b/markdown/org/blog/freesewing-2-19/de.md new file mode 100644 index 00000000000..4fb05c504ab --- /dev/null +++ b/markdown/org/blog/freesewing-2-19/de.md @@ -0,0 +1,40 @@ +--- +author: "joostdecock" +caption: "Like history? Then this release is going to be right up your alley." +date: "2021-10-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/af326b5b6326911272ed989947e8cafe22966019-1920x1280.jpg" +intro: "I've just pulled the release lever on version 2.19 of FreeSewing and there's a lot that went into this release. For full details, you can check out the changelog , here I'll stick to the highlights:" +title: "FreeSewing 2.19 brings Bee, Lunetius, Tiberius, Walburga, a new plugin, and a bunch of improvements and fixes [Nicht übersetzt]" +--- + +I've just pulled the release lever on version 2.19 of FreeSewing and there's a lot that went into this release. For full details, you can [check out the changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md#2190-2021-10-17), here I'll stick to the highlights: + +## Lunetius, Tiberius, and Walburga + +[Lunetius](/designs/lunetius), [Tiberius](/designs/tiberius/), and [Walburga](/designs/walburga/) are three new patters from **Rika Tamaike** who is the latest addition to our growing team of designers. These are all historical pattern: + + - Lunetius is a lacerna, a historical Roman cloak + - Tiberius is a historical Roman tunic + - Walburga is a tabard/surcoat, a historical garment from medieval Europe + +I'm not much of a history buff myself, so I'm looking forward to see what these will look like when people are going to start making them. What I can say for sure is that all of these are pretty straight-forward, so they should be fun to make. + +## The Bee bikini + +Also new in this release is [Bee](/designs/bee/), a bikini pattern that you can pair with the [Ursula Undies pattern](/designs/ursula/). **Bobgeorgethe3rd** signed for the code, the design of the bikini was a collaboration with **PrudenceRabbit**. + +I'm hoping for some people in the Southern hemisphere to make this one because I suspect it might be a while before bikini weather returns to those of use living above the equator. + +This too is a fast and simple make, so go and check it out. + +## The versionfree-svg plugin + +This is a bit more under-the-hood stuff, but we've also published [plugin-versinofree-svg](https://www.npmjs.com/package/@freesewing/plugin-versionfree-svg), a new plugin that will strip the version information from FreeSewing's SVG output. + +This is handy because it allows diffing between different versions. By not including the version information, you can see what (if anything) has changed between different versions of a pattern, something we use ourselved in our QA pipeline. + +## Backported snap options from the v3 roadmap + +Speaking of under-the-hood, the [snap proposal](https://github.com/freesewing/freesewing/discussions/1331) on [our v3 roadmap](https://github.com/freesewing/freesewing/discussions/1278) was something we liked so much that we promptly backported it to v2, and it's already being used in different patterns. + +Have fun with the new patterns, and for feedback, questions, or suggestions, [come hang out with us on Discord](https://discord.freesewing.org). diff --git a/markdown/org/blog/freesewing-2-19/en.md b/markdown/org/blog/freesewing-2-19/en.md new file mode 100644 index 00000000000..7b8046e5154 --- /dev/null +++ b/markdown/org/blog/freesewing-2-19/en.md @@ -0,0 +1,40 @@ +--- +author: "joostdecock" +caption: "Like history? Then this release is going to be right up your alley." +date: "2021-10-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/af326b5b6326911272ed989947e8cafe22966019-1920x1280.jpg" +intro: "I've just pulled the release lever on version 2.19 of FreeSewing and there's a lot that went into this release. For full details, you can check out the changelog , here I'll stick to the highlights:" +title: "FreeSewing 2.19 brings Bee, Lunetius, Tiberius, Walburga, a new plugin, and a bunch of improvements and fixes" +--- + +I've just pulled the release lever on version 2.19 of FreeSewing and there's a lot that went into this release. For full details, you can [check out the changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md#2190-2021-10-17), here I'll stick to the highlights: + +## Lunetius, Tiberius, and Walburga + +[Lunetius](/designs/lunetius), [Tiberius](/designs/tiberius/), and [Walburga](/designs/walburga/) are three new patters from **Rika Tamaike** who is the latest addition to our growing team of designers. These are all historical pattern: + + - Lunetius is a lacerna, a historical Roman cloak + - Tiberius is a historical Roman tunic + - Walburga is a tabard/surcoat, a historical garment from medieval Europe + +I'm not much of a history buff myself, so I'm looking forward to see what these will look like when people are going to start making them. What I can say for sure is that all of these are pretty straight-forward, so they should be fun to make. + +## The Bee bikini + +Also new in this release is [Bee](/designs/bee/), a bikini pattern that you can pair with the [Ursula Undies pattern](/designs/ursula/). **Bobgeorgethe3rd** signed for the code, the design of the bikini was a collaboration with **PrudenceRabbit**. + +I'm hoping for some people in the Southern hemisphere to make this one because I suspect it might be a while before bikini weather returns to those of use living above the equator. + +This too is a fast and simple make, so go and check it out. + +## The versionfree-svg plugin + +This is a bit more under-the-hood stuff, but we've also published [plugin-versinofree-svg](https://www.npmjs.com/package/@freesewing/plugin-versionfree-svg), a new plugin that will strip the version information from FreeSewing's SVG output. + +This is handy because it allows diffing between different versions. By not including the version information, you can see what (if anything) has changed between different versions of a pattern, something we use ourselved in our QA pipeline. + +## Backported snap options from the v3 roadmap + +Speaking of under-the-hood, the [snap proposal](https://github.com/freesewing/freesewing/discussions/1331) on [our v3 roadmap](https://github.com/freesewing/freesewing/discussions/1278) was something we liked so much that we promptly backported it to v2, and it's already being used in different patterns. + +Have fun with the new patterns, and for feedback, questions, or suggestions, [come hang out with us on Discord](https://discord.freesewing.org). diff --git a/markdown/org/blog/freesewing-2-19/es.md b/markdown/org/blog/freesewing-2-19/es.md new file mode 100644 index 00000000000..7350f7a2f5f --- /dev/null +++ b/markdown/org/blog/freesewing-2-19/es.md @@ -0,0 +1,40 @@ +--- +author: "joostdecock" +caption: "Like history? Then this release is going to be right up your alley." +date: "2021-10-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/af326b5b6326911272ed989947e8cafe22966019-1920x1280.jpg" +intro: "I've just pulled the release lever on version 2.19 of FreeSewing and there's a lot that went into this release. For full details, you can check out the changelog , here I'll stick to the highlights:" +title: "FreeSewing 2.19 brings Bee, Lunetius, Tiberius, Walburga, a new plugin, and a bunch of improvements and fixes [No traducido]" +--- + +I've just pulled the release lever on version 2.19 of FreeSewing and there's a lot that went into this release. For full details, you can [check out the changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md#2190-2021-10-17), here I'll stick to the highlights: + +## Lunetius, Tiberius, and Walburga + +[Lunetius](/designs/lunetius), [Tiberius](/designs/tiberius/), and [Walburga](/designs/walburga/) are three new patters from **Rika Tamaike** who is the latest addition to our growing team of designers. These are all historical pattern: + + - Lunetius is a lacerna, a historical Roman cloak + - Tiberius is a historical Roman tunic + - Walburga is a tabard/surcoat, a historical garment from medieval Europe + +I'm not much of a history buff myself, so I'm looking forward to see what these will look like when people are going to start making them. What I can say for sure is that all of these are pretty straight-forward, so they should be fun to make. + +## The Bee bikini + +Also new in this release is [Bee](/designs/bee/), a bikini pattern that you can pair with the [Ursula Undies pattern](/designs/ursula/). **Bobgeorgethe3rd** signed for the code, the design of the bikini was a collaboration with **PrudenceRabbit**. + +I'm hoping for some people in the Southern hemisphere to make this one because I suspect it might be a while before bikini weather returns to those of use living above the equator. + +This too is a fast and simple make, so go and check it out. + +## The versionfree-svg plugin + +This is a bit more under-the-hood stuff, but we've also published [plugin-versinofree-svg](https://www.npmjs.com/package/@freesewing/plugin-versionfree-svg), a new plugin that will strip the version information from FreeSewing's SVG output. + +This is handy because it allows diffing between different versions. By not including the version information, you can see what (if anything) has changed between different versions of a pattern, something we use ourselved in our QA pipeline. + +## Backported snap options from the v3 roadmap + +Speaking of under-the-hood, the [snap proposal](https://github.com/freesewing/freesewing/discussions/1331) on [our v3 roadmap](https://github.com/freesewing/freesewing/discussions/1278) was something we liked so much that we promptly backported it to v2, and it's already being used in different patterns. + +Have fun with the new patterns, and for feedback, questions, or suggestions, [come hang out with us on Discord](https://discord.freesewing.org). diff --git a/markdown/org/blog/freesewing-2-19/fr.md b/markdown/org/blog/freesewing-2-19/fr.md new file mode 100644 index 00000000000..56d54fd4545 --- /dev/null +++ b/markdown/org/blog/freesewing-2-19/fr.md @@ -0,0 +1,40 @@ +--- +author: "joostdecock" +caption: "Like history? Then this release is going to be right up your alley." +date: "2021-10-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/af326b5b6326911272ed989947e8cafe22966019-1920x1280.jpg" +intro: "I've just pulled the release lever on version 2.19 of FreeSewing and there's a lot that went into this release. For full details, you can check out the changelog , here I'll stick to the highlights:" +title: "FreeSewing 2.19 brings Bee, Lunetius, Tiberius, Walburga, a new plugin, and a bunch of improvements and fixes [Non traduit]" +--- + +I've just pulled the release lever on version 2.19 of FreeSewing and there's a lot that went into this release. For full details, you can [check out the changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md#2190-2021-10-17), here I'll stick to the highlights: + +## Lunetius, Tiberius, and Walburga + +[Lunetius](/designs/lunetius), [Tiberius](/designs/tiberius/), and [Walburga](/designs/walburga/) are three new patters from **Rika Tamaike** who is the latest addition to our growing team of designers. These are all historical pattern: + + - Lunetius is a lacerna, a historical Roman cloak + - Tiberius is a historical Roman tunic + - Walburga is a tabard/surcoat, a historical garment from medieval Europe + +I'm not much of a history buff myself, so I'm looking forward to see what these will look like when people are going to start making them. What I can say for sure is that all of these are pretty straight-forward, so they should be fun to make. + +## The Bee bikini + +Also new in this release is [Bee](/designs/bee/), a bikini pattern that you can pair with the [Ursula Undies pattern](/designs/ursula/). **Bobgeorgethe3rd** signed for the code, the design of the bikini was a collaboration with **PrudenceRabbit**. + +I'm hoping for some people in the Southern hemisphere to make this one because I suspect it might be a while before bikini weather returns to those of use living above the equator. + +This too is a fast and simple make, so go and check it out. + +## The versionfree-svg plugin + +This is a bit more under-the-hood stuff, but we've also published [plugin-versinofree-svg](https://www.npmjs.com/package/@freesewing/plugin-versionfree-svg), a new plugin that will strip the version information from FreeSewing's SVG output. + +This is handy because it allows diffing between different versions. By not including the version information, you can see what (if anything) has changed between different versions of a pattern, something we use ourselved in our QA pipeline. + +## Backported snap options from the v3 roadmap + +Speaking of under-the-hood, the [snap proposal](https://github.com/freesewing/freesewing/discussions/1331) on [our v3 roadmap](https://github.com/freesewing/freesewing/discussions/1278) was something we liked so much that we promptly backported it to v2, and it's already being used in different patterns. + +Have fun with the new patterns, and for feedback, questions, or suggestions, [come hang out with us on Discord](https://discord.freesewing.org). diff --git a/markdown/org/blog/freesewing-2-19/nl.md b/markdown/org/blog/freesewing-2-19/nl.md new file mode 100644 index 00000000000..c40e2fd9847 --- /dev/null +++ b/markdown/org/blog/freesewing-2-19/nl.md @@ -0,0 +1,40 @@ +--- +author: "joostdecock" +caption: "Like history? Then this release is going to be right up your alley." +date: "2021-10-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/af326b5b6326911272ed989947e8cafe22966019-1920x1280.jpg" +intro: "I've just pulled the release lever on version 2.19 of FreeSewing and there's a lot that went into this release. For full details, you can check out the changelog , here I'll stick to the highlights:" +title: "FreeSewing 2.19 brings Bee, Lunetius, Tiberius, Walburga, a new plugin, and a bunch of improvements and fixes [Niet vertaald]" +--- + +I've just pulled the release lever on version 2.19 of FreeSewing and there's a lot that went into this release. For full details, you can [check out the changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md#2190-2021-10-17), here I'll stick to the highlights: + +## Lunetius, Tiberius, and Walburga + +[Lunetius](/designs/lunetius), [Tiberius](/designs/tiberius/), and [Walburga](/designs/walburga/) are three new patters from **Rika Tamaike** who is the latest addition to our growing team of designers. These are all historical pattern: + + - Lunetius is a lacerna, a historical Roman cloak + - Tiberius is a historical Roman tunic + - Walburga is a tabard/surcoat, a historical garment from medieval Europe + +I'm not much of a history buff myself, so I'm looking forward to see what these will look like when people are going to start making them. What I can say for sure is that all of these are pretty straight-forward, so they should be fun to make. + +## The Bee bikini + +Also new in this release is [Bee](/designs/bee/), a bikini pattern that you can pair with the [Ursula Undies pattern](/designs/ursula/). **Bobgeorgethe3rd** signed for the code, the design of the bikini was a collaboration with **PrudenceRabbit**. + +I'm hoping for some people in the Southern hemisphere to make this one because I suspect it might be a while before bikini weather returns to those of use living above the equator. + +This too is a fast and simple make, so go and check it out. + +## The versionfree-svg plugin + +This is a bit more under-the-hood stuff, but we've also published [plugin-versinofree-svg](https://www.npmjs.com/package/@freesewing/plugin-versionfree-svg), a new plugin that will strip the version information from FreeSewing's SVG output. + +This is handy because it allows diffing between different versions. By not including the version information, you can see what (if anything) has changed between different versions of a pattern, something we use ourselved in our QA pipeline. + +## Backported snap options from the v3 roadmap + +Speaking of under-the-hood, the [snap proposal](https://github.com/freesewing/freesewing/discussions/1331) on [our v3 roadmap](https://github.com/freesewing/freesewing/discussions/1278) was something we liked so much that we promptly backported it to v2, and it's already being used in different patterns. + +Have fun with the new patterns, and for feedback, questions, or suggestions, [come hang out with us on Discord](https://discord.freesewing.org). diff --git a/markdown/org/blog/freesewing-2-21/en.md b/markdown/org/blog/freesewing-2-21/en.md new file mode 100644 index 00000000000..96c7ff61eab --- /dev/null +++ b/markdown/org/blog/freesewing-2-21/en.md @@ -0,0 +1,48 @@ +--- +author: "joostdecock" +caption: "A pink Hi and its BLÅHAJ ancestor" +date: "2022-06-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5b5d9171aca75dd339bf8b7359b257769aa61936-4032x3024.jpg" +intro: "FreeSewing 2.21 adds Bob, Hi, Lucy, Noble and Unice designs" +title: "FreeSewing 2.21 adds Bob, Hi, Lucy, Noble and Unice designs" +--- + +We've rolled out FreeSewing v2.21 today, and it's a massive update with tons of changes, improvements, and behind the scenes work. +Check the CHANGELOG if you'd like get all the nitty-gritty detail. For this blog post, I'll focus on what you are probably going to be most interested in: New designs. + +This release brings 5 new designs to our catalog, so let's dive right in: + +## Bob is a bib + +We've been using the construction of a Bib pattern in our [pattern design tutorial](https://freesewing.dev/tutorials/pattern-design) for years. +Yet we never added the pattern to our catalog. An oversight that's been corrected now, and we now carry [Bob the bib](/designs/bob) in our collection. + +Perfect for babies and grown-ups who are messy eaters alike, since you can make Bob in any size. + +## Hi is a shark + +It's been kinda hard to contain our excitement about this, but hear me out: A while ago rumours started swirling that IKEA would discontinue it's [BLÅHAJ](https://www.ikea.com/us/en/p/blahaj-soft-toy-shark-90373590/) stuffed shark, which is a universally beloved toy. + +The FreeSewing community wasn't just going to idly stand by while the worlds friendliest shark ran the risk of becoming extinct. +A conservation effort gained momentum, and ultimately Wouter matter-of-factively dropped the first **Hi** pictures in our Discord. + +Oh, and you should know that [Hi](/designs/hi) can be made big or small. The patterns scales up to a 5m shark. What are you waiting for? + +## Lucy is a tie-on pocket + +We've seen a number of historical designs recently, specifically from Starf. This time around, it's SeaZeeZee who added [Lucy](/designs/lucy) which is a pattern for a tie-on pocket. + +It's a quick make for cosplay, historical re-enactment, or for all those dresses that don't come with pockets. + +## Noble is a body block with prince(ss) seams + +Wouter (of Hi fame) has another contribution in this release: Noble is a princess seam body block. +Blocks tend to be undervalued but they are the foundation that other designs are built on, so having a new body block with prince(ss) seams is very exciting. + +## Unice is for undies + +[Unice](/designs/unice) is a variant of [Ursula](/desgns/ursula), another undies pattern. It was designed by Anna who describes it as *the undies for those with significant rear estate*. + +It has a few changes and tweaks in comparison to Ursula, and is specifically intended to fit *any* body. So if you're rear estate mogul, try these out. + + diff --git a/markdown/org/blog/freesewing-goes-jamstack/de.md b/markdown/org/blog/freesewing-goes-jamstack/de.md new file mode 100644 index 00000000000..493891b466f --- /dev/null +++ b/markdown/org/blog/freesewing-goes-jamstack/de.md @@ -0,0 +1,103 @@ +--- +author: "joostdecock" +caption: "Bild von" +date: "2017-06-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/952f714d11203d03a449895053c63963b0c02dbd-2000x1126.jpg" +intro: "Als wir Ende März den FreeSewing Core veröffentlichten, verlagerte sich mein Fokus sofort auf den Aufbau unseres Frontends, sodass freesewing.org makemypattern.com vollständig ersetzen konnte." +title: "Wir sind JAMstack, wir sind JAMstack, wir sind JAMstack, wir sind JAMstack, wir sind JAMstack, wir sind JAMstack, wir sind JAMstack, wir sind JAMstack, und ich hoffe, dass du auch JAMstack magst" +--- + + +Als wir Ende März den FreeSewing Core veröffentlichten, verlagerte sich mein Fokus sofort auf den Aufbau unseres Frontends, sodass [freesewing.org](/) [makemypattern.com](https://makemypattern.com/) vollständig ersetzen konnte. + +Ich glaube, dass der Wert von FreeSewing bei dem Core der Plattform und unseren Schnittmustern liegt. Aber ohne eine benutzerfreundliche Möglichkeit, diese Werte zu präsentieren, werden sie weitgehend ignoriert werden. + +Deshalb brauchten wir eine Website, die es den Leuten ermöglicht, Schnittmuster zu generieren. Makemypattern.com — wohl der beste Vergleich von etwas Ähnlichem — läuft auf Drupal 7, und meine erste Idee war es, die neue Seite auf Drupal 8 zu betreiben. Ich ging diesen Weg weit genug, um sicher zu sein, dass ich ihn zum Laufen bringen und an unser Backend anschließen konnte. An diesem Punkt habe ich das Ruder herumgerissen und mich dem FreeSewing Core zugewendet. + +Der Bau des Cores dauerte etwa 7 Monate, und seitdem hat sich viel verändert. Oder vielleicht habe ich mich verändert, ich habe auf jeden Fall viel gelernt. So oder so, ich habe mich entschieden, die Dinge anders zu machen. + +## Das Problem mit einem CMS + +Ich habe kein Problem mit Drupal, aber die Idee, die FreeSewing-Website über ein Content Management System (CMS) zu verwalten, gefällt mir nicht. + +Einer der Hauptgründe ist, dass so viele Informationen unter einer undurchsichtigen Datenbankschicht gespeichert sind, was die Verwaltung erschwert. Das gilt für Inhalte, bei denen Beiträge, Metadaten, Bilder usw. über Tabellen, Speicherorte und Ordner verteilt sind. Aber es gibt auch das Theme, das einen Haufen Zeug enthält, es gibt die benutzerdefinierten Drupal-Module, um sich mit dem Backend zu verbinden, und so weiter und so fort. + +> Ich wollte den gleichen Ansatz in einer Website. Außer, dass sie nicht statisch sein kann, weil sie, Sie wissen schon, Dinge tun muss. + +Als wir den Kern fertiggestellt haben, habe ich eine Dokumentationsseite dafür erstellt, die auf [Jekyll](https://jekyllrb.com/) basiert. Im Vergleich zu Drupal fühlte es sich wie ein Hauch von frischer Luft an. Nur ein Haufen Markdown-Dateien, mit einigen SASS, Bildern und etwas JavaScript, die in den Mixxer geworfen wurden, und alles wird zu einer ordentlichen statischen Website zusammengefügt. + +Es ist einfach zu verwalten und lässt sich gut in einen GitHub-zentrierten Workflow integrieren, der potenziellen Mitwirkenden vertraut sein dürfte. + +Ich wollte den gleichen Ansatz in einer Website. Außer, dass sie nicht statisch sein kann, weil sie, Sie wissen schon, Dinge tun muss. + + +## Ein alternativer Ansatz: JAMstack + +Ich habe zum ersten Mal von JAMstack erfahren, als ich anfing, mich mit dem Hosting für diese zentrale Dokumentationsseite zu befassen. Es wurde ursprünglich auf GitHub-Seiten gehostet, die kostenloses Hosting anbieten. Sie haben auch SSL oder einen benutzerdefinierten Domänennamen, aber Sie können nicht beides haben. Was eine Art Deal-Breaker war. + +Auf der Suche nach Alternativen stolperte ich über [Netlify](https://www.netlify.com/), die sowohl SSL- als auch kundenspezifische Domains betreiben und ein kostenloses Angebot für Open-Source-Projekte haben (danke Jungs). Außerdem hat mich dieses Video von Netlify CEO Mathias Biilmann sehr begeistert für JAMstack. + +Sofern Sie nicht mit JAMstack vertraut sind, schlage ich vor, dass Sie sich das Video ansehen, aber es läuft darauf hinaus: + + - **J** = JavaScript + - **A** = APIs + - **J** = Markup + +Die Idee ist, dass Sie Ihre statische Website (Markup) erstellen, die Sie dann mit JavaScript interaktiv machen, das an eine oder mehrere APIs angeschlossen ist. + +Anstatt also in unserem Fall eine einfache Dokumentationsseite mit einfach zu bearbeitendem Markdown und einem komplexen CMS zur Handhabung des dymanischen Materials zu haben, lassen Sie uns einfach eine einfache Seite erstellen, die statisch generiert wird, aber JavaScript und APIs verwendet, um das interaktive Material bereitzustellen. + + + +## Laufen, bevor Sie gehen können + +Ich muss zugeben, dass ich in meiner Begeisterung, diesen neuen Ansatz anzunehmen, ein wenig über mich selbst hinausgewachsen bin. Plötzlich baute ich keine einfache Website mehr, aber ich war bis zum Anschlag in isomorphem Rendering, client-seitigem Routing, React and Redux, Node.js und ES6 Transpiling verwickelt. + + + +> Wenn Sie nicht wissen, was das alles bedeutet, werden Sie vielleicht einen Eindruck von der Frustration bekommen, die ich empfand, als ich versuchte, all diese neuen Bestien zu zähmen. +> +> Wenn Sie wissen, was das alles bedeutet, wo waren Sie dann im April, als ich durch das Tal des Todes ging? + +Der Punkt ist, ich bin kein Entwickler und ich war weit über meinem Level. Während ich jeden Tag neue Dinge lernte, machte ich bei der eigentlichen Aufgabe nicht viel Fortschritte und war frustriert über meine Unfähigkeit, selbst die alltäglichsten Dinge zu tun. + +Nach einem Monat der Frustration, vielen Versuchen und scheinbar noch mehr Fehlern warf ich das Handtuch. Ich lass diesen neumodischen Kram namens JavaScript, den alle Kiddies heutzutage nutzen, und bleibe bei dem, was ich kenne. + +Was im Wesentlichen die Grundlagen von jQuery ist. Mit anderen Worten, Sachen, die vor 10 Jahren ziemlich cool waren. + + + +## 10 Jahre alte Marmelade ist immer noch Marmelade, oder? + +Hier sind wir also, freesewing.org ist eine Seite, die vom JAMstack betrieben wird. Und wissen Sie was, es scheint zu tun, was es tun soll. + +Wir lassen Jekyll eine statische Website erstellen, und wenn wir etwas in unserem Masterbranch pushen, wird es automatisch auf Netlify bereitgestellt. + + + +> Effektiv dieses neumodisch glänzende JavaScript, das alle kleinen Kiddies benutzen + +Wir haben [eine brandneue Daten-API](https://github.com/freesewing/data), die auf [dem Slim Framework](https://www.slimframework.com/) basiert. Es verwaltet alle Benutzerdaten. Dinge wie Benutzerkonten, Maße, Modelle und Entwürfe, aber auch Kommentare zu dieser Website und so weiter. + +Es spricht auch für uns, und jedes Mal, wenn Sie ein Muster entwerfen, geben wir Ihnen nicht nur das Muster, sondern führen auch einen Vergleich Ihres Musters mit einer Reihe von Standardgrößen durch, was irgendwie cool ist. + +Und wir haben noch andere coole Dinge, wie die Möglichkeit, einen bestehenden Entwurf zu duplizieren oder neu zu entwerfen. + + + +## Das ist ein Ausgangspunkt + +Ich hoffe, dass die Benutzererfahrung/Benutzeroberfläche kein Hindernis für Menschen sein wird. Ich habe große Anstrengungen unternommen, um den Entwurfvorgang so intuitiv wie möglich zu machen und ich denke, dass es im Vergleich zu unserer Demo (oder der Makemypattern-Schnittstelle für diese Angelegenheit) eine enorme Verbesserung ist. + +Andererseits bin ich sicher, dass die Dinge nach links oder rechts brechen werden, oder dass einige von euch die Farben nicht mögen oder was auch immer. + +Der Punkt ist, dass ich mich daran gemacht habe, etwas zu bauen, das makemypattern.com ersetzen kann, damit ich euch allen sagen kann _Hey, kommt vorbei und spielt mit diesem neuen Ding_. + +Ich denke, das kann ich das jetzt tun. Und wenn Sie Verbesserungspotenzial sehen, nehmen Sie bitte [an der Anstrengung teil](/contribute), wir fangen gerade erst an. + +PS: Für diejenigen von euch, die sich über den Titel dieses Beitrags Gedanken machen: + + + + + diff --git a/markdown/org/blog/freesewing-goes-jamstack/en.md b/markdown/org/blog/freesewing-goes-jamstack/en.md new file mode 100644 index 00000000000..05ec8c4524d --- /dev/null +++ b/markdown/org/blog/freesewing-goes-jamstack/en.md @@ -0,0 +1,106 @@ +--- +author: "joostdecock" +caption: "Picture by Jennifer" +date: "2017-06-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/952f714d11203d03a449895053c63963b0c02dbd-2000x1126.jpg" +intro: "When we released freesewing core at the end of March, my focus immeadiatly shifted to building our front-end so that freesewing.org could fully replace makemypattern.com ." +title: "We're JAMstack, we're JAMstack, we're JAMstack, we're JAMstack, we're JAMstack, we're JAMstack, we're JAMstack, and I hope you like JAMstack too" +--- + +When we released freesewing core at the end of March, my focus immeadiatly shifted to building our front-end so that [freesewing.org](/) could fully replace [makemypattern.com](https://makemypattern.com/). + +I believe that the value of freesewing lies with the core platform and our patterns. +But without a user friendly way to expose that value, it will largely go ignored. + +So we needed a website that lets people generate patterns. Makemypattern.com — arguably the best comparison of something similar — runs on Drupal 7, and my initial idea was to run the new site on Drupal 8. +I went down that path far enought to be confident I could get it to work, and hook it up to our backend. At which point I switched gears and turned my attention to what is now known as freesewing core. + +Core took about 7 months to build, and a lot has changed since then. Or perhaps I have changed, I certainly learned a lot along the way. Either way, I've decided to do things different. + +## The problem with a CMS + +I have no beef with Drupal but the idea of managing the freesewing website through any Content Management System (CMS) does not appeal to me. + +One of the main reason is that so much information is stored under an opaque database layer which makes it difficult to manage. +That goes for content where posts, metadata, images, and so on is all spread across tables, locations, and folders. +But there's also the theme that has a bunch of stuff in it, there's the custom Drupal modules to connect to the backend, and so on and so forth. + +> I wanted that same approach in a website. Except, it can't be static because it has to, you know, do stuff. + +When we were finalizing core, I built a documentation site for it based on [Jekyll](https://jekyllrb.com/). It felt like a breath of fresh air in comparison. +Just a bunch of markdown files, with some SASS, images, and some JavaScript thrown in the mix, and it all compiles into a neat static website. + +It's easy to manage, and it integrates nicely with a GitHub-centered workflow that is going to be famliar to potential contributors. + +I wanted that same approach in a website. Except, it can't be static because it has to, you know, do stuff. + + +## An alternative approach: JAMstack + +I first learned about JAMstack when I started looking into hosting for said core documentation site. +It was initially hosted on GitHub pages which provides free hosting. +They also have SSL or a custom domain name, but you can't have both. Which was kind of a deal breaker. + +Looking for alternatives, I stumbled onto [Netlify](https://www.netlify.com/), who do both SSL and custom domains and have a free-tier for open source projects (thanks guys). +Furthermore, [this video by Netlify CEO Mathias Biilmann](https://vimeo.com/163522126) got me really excited about JAMstack. + +Unless you're familiar with JAMstack, I suggest you check out the video, but it boils down to this: + + - **J** = JavaScript + - **A** = APIs + - **M** = Markup + +The idea is that you build your static site (markup) that you then make interactive with JavaScript that hooks up to one or more APIs. + +So in our case, rather than having a straight-forward documentation site with easy-to-edit markdown and a complex CMS to handle the dymanic stuff, let's just build one simple site that is statically generated, yet uses JavaScript and APIs to do the smart stuff. + +## Running before you can walk + +I must admit that in my enthousiasm to embrace this new approach I got a little ahead of myself. +Suddenly, I was no longer building a simple site, but I was up to my eyeballs in isomorphic rendering, client-side routing, React and Redux, Node.js and ES6 transpiling. + +> If you don't know what any of that means, you might get a hint of the frustration I felt as I was trying to tame all these new beasts. +> +> If you do know what it all means, where were you back in April when I walked through the valley of the React of death? + +Point is, I'm not a developer and I was in way over my head. +While I was learning new things every day, I wasn't making much progress on the actual task at hand, and felt frustrated with my inability to do even the most mundane things. + +After a month of frustration, loads of trial and seemingly even more error, I threw in the towel. +Eff this newfangled shiny JavaScript all the young kids are using, I'll stick to what I know. + +Which is essentially the basics of jQuery. In other words, stuff that was pretty cool 10 years ago. + +## 10 year old jam is still jam right? + +So here we are, freesewing.org is a site powered by the JAMstack. And you know what, it seems to do what it needs to do. + +We have Jekyll build out static site, and when we push to our master branch, it gets autmatically deployed to Netlify. + +> Eff this newfangled shiny JavaScript all the young kids are using + +We have [a brand new data API](https://github.com/freesewing/data) build on [the Slim framework](https://www.slimframework.com/). +It handles all user data. Things like accounts, measurements, models, and drafts, but also comments on this website and so on. + +It also talks to core for us, and every time you draft a pattern, we don't just give you the pattern, but we also run a comparison of your pattern to a range of standard sizes, which is kinda cool. + +And we have other cool stuff, like the ability to fork or redraft an existing draft. + +## This is a starting point + +I hope the user experience/interface is not going to be a roadblock for people. +I've made a great deal of effort to make the drafting process as intuitive as possible and I think that in comparison to our demo (or the makemypattern interface for that matter) it's a vast improvement. + +Then again, I'm sure things will break left or right, or that some of you don't like the colours or whatnot. + +The point is that I set out to build something that can replace makemypattern.com so that I could tell all of you _Hey, come over and play with this new thing_. + +I think if nothing else, I can do that now. And if you see room for improvement, please [join the effort](/contribute), we're only getting started. + + + +PS: For those of you wondering about the title of this post: + + + + diff --git a/markdown/org/blog/freesewing-goes-jamstack/es.md b/markdown/org/blog/freesewing-goes-jamstack/es.md new file mode 100644 index 00000000000..d7a0b733d13 --- /dev/null +++ b/markdown/org/blog/freesewing-goes-jamstack/es.md @@ -0,0 +1,106 @@ +--- +author: "joostdecock" +caption: "Picture by Jennifer" +date: "2017-06-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/952f714d11203d03a449895053c63963b0c02dbd-2000x1126.jpg" +intro: "When we released freesewing core at the end of March, my focus immeadiatly shifted to building our front-end so that freesewing.org could fully replace makemypattern.com ." +title: "We're JAMstack, we're JAMstack, we're JAMstack, we're JAMstack, we're JAMstack, we're JAMstack, we're JAMstack, and I hope you like JAMstack too [No traducido]" +--- + +When we released freesewing core at the end of March, my focus immeadiatly shifted to building our front-end so that [freesewing.org](/) could fully replace [makemypattern.com](https://makemypattern.com/). + +I believe that the value of freesewing lies with the core platform and our patterns. +But without a user friendly way to expose that value, it will largely go ignored. + +So we needed a website that lets people generate patterns. Makemypattern.com — arguably the best comparison of something similar — runs on Drupal 7, and my initial idea was to run the new site on Drupal 8. +I went down that path far enought to be confident I could get it to work, and hook it up to our backend. At which point I switched gears and turned my attention to what is now known as freesewing core. + +Core took about 7 months to build, and a lot has changed since then. Or perhaps I have changed, I certainly learned a lot along the way. Either way, I've decided to do things different. + +## The problem with a CMS + +I have no beef with Drupal but the idea of managing the freesewing website through any Content Management System (CMS) does not appeal to me. + +One of the main reason is that so much information is stored under an opaque database layer which makes it difficult to manage. +That goes for content where posts, metadata, images, and so on is all spread across tables, locations, and folders. +But there's also the theme that has a bunch of stuff in it, there's the custom Drupal modules to connect to the backend, and so on and so forth. + +> I wanted that same approach in a website. Except, it can't be static because it has to, you know, do stuff. + +When we were finalizing core, I built a documentation site for it based on [Jekyll](https://jekyllrb.com/). It felt like a breath of fresh air in comparison. +Just a bunch of markdown files, with some SASS, images, and some JavaScript thrown in the mix, and it all compiles into a neat static website. + +It's easy to manage, and it integrates nicely with a GitHub-centered workflow that is going to be famliar to potential contributors. + +I wanted that same approach in a website. Except, it can't be static because it has to, you know, do stuff. + + +## An alternative approach: JAMstack + +I first learned about JAMstack when I started looking into hosting for said core documentation site. +It was initially hosted on GitHub pages which provides free hosting. +They also have SSL or a custom domain name, but you can't have both. Which was kind of a deal breaker. + +Looking for alternatives, I stumbled onto [Netlify](https://www.netlify.com/), who do both SSL and custom domains and have a free-tier for open source projects (thanks guys). +Furthermore, [this video by Netlify CEO Mathias Biilmann](https://vimeo.com/163522126) got me really excited about JAMstack. + +Unless you're familiar with JAMstack, I suggest you check out the video, but it boils down to this: + + - **J** = JavaScript + - **A** = APIs + - **M** = Markup + +The idea is that you build your static site (markup) that you then make interactive with JavaScript that hooks up to one or more APIs. + +So in our case, rather than having a straight-forward documentation site with easy-to-edit markdown and a complex CMS to handle the dymanic stuff, let's just build one simple site that is statically generated, yet uses JavaScript and APIs to do the smart stuff. + +## Running before you can walk + +I must admit that in my enthousiasm to embrace this new approach I got a little ahead of myself. +Suddenly, I was no longer building a simple site, but I was up to my eyeballs in isomorphic rendering, client-side routing, React and Redux, Node.js and ES6 transpiling. + +> If you don't know what any of that means, you might get a hint of the frustration I felt as I was trying to tame all these new beasts. +> +> If you do know what it all means, where were you back in April when I walked through the valley of the React of death? + +Point is, I'm not a developer and I was in way over my head. +While I was learning new things every day, I wasn't making much progress on the actual task at hand, and felt frustrated with my inability to do even the most mundane things. + +After a month of frustration, loads of trial and seemingly even more error, I threw in the towel. +Eff this newfangled shiny JavaScript all the young kids are using, I'll stick to what I know. + +Which is essentially the basics of jQuery. In other words, stuff that was pretty cool 10 years ago. + +## 10 year old jam is still jam right? + +So here we are, freesewing.org is a site powered by the JAMstack. And you know what, it seems to do what it needs to do. + +We have Jekyll build out static site, and when we push to our master branch, it gets autmatically deployed to Netlify. + +> Eff this newfangled shiny JavaScript all the young kids are using + +We have [a brand new data API](https://github.com/freesewing/data) build on [the Slim framework](https://www.slimframework.com/). +It handles all user data. Things like accounts, measurements, models, and drafts, but also comments on this website and so on. + +It also talks to core for us, and every time you draft a pattern, we don't just give you the pattern, but we also run a comparison of your pattern to a range of standard sizes, which is kinda cool. + +And we have other cool stuff, like the ability to fork or redraft an existing draft. + +## This is a starting point + +I hope the user experience/interface is not going to be a roadblock for people. +I've made a great deal of effort to make the drafting process as intuitive as possible and I think that in comparison to our demo (or the makemypattern interface for that matter) it's a vast improvement. + +Then again, I'm sure things will break left or right, or that some of you don't like the colours or whatnot. + +The point is that I set out to build something that can replace makemypattern.com so that I could tell all of you _Hey, come over and play with this new thing_. + +I think if nothing else, I can do that now. And if you see room for improvement, please [join the effort](/contribute), we're only getting started. + + + +PS: For those of you wondering about the title of this post: + + + + diff --git a/markdown/org/blog/freesewing-goes-jamstack/fr.md b/markdown/org/blog/freesewing-goes-jamstack/fr.md new file mode 100644 index 00000000000..a14993bf8a9 --- /dev/null +++ b/markdown/org/blog/freesewing-goes-jamstack/fr.md @@ -0,0 +1,106 @@ +--- +author: "joostdecock" +caption: "Picture by Jennifer" +date: "2017-06-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/952f714d11203d03a449895053c63963b0c02dbd-2000x1126.jpg" +intro: "When we released freesewing core at the end of March, my focus immeadiatly shifted to building our front-end so that freesewing.org could fully replace makemypattern.com ." +title: "We're JAMstack, we're JAMstack, we're JAMstack, we're JAMstack, we're JAMstack, we're JAMstack, we're JAMstack, and I hope you like JAMstack too [Non traduit]" +--- + +When we released freesewing core at the end of March, my focus immeadiatly shifted to building our front-end so that [freesewing.org](/) could fully replace [makemypattern.com](https://makemypattern.com/). + +I believe that the value of freesewing lies with the core platform and our patterns. +But without a user friendly way to expose that value, it will largely go ignored. + +So we needed a website that lets people generate patterns. Makemypattern.com — arguably the best comparison of something similar — runs on Drupal 7, and my initial idea was to run the new site on Drupal 8. +I went down that path far enought to be confident I could get it to work, and hook it up to our backend. At which point I switched gears and turned my attention to what is now known as freesewing core. + +Core took about 7 months to build, and a lot has changed since then. Or perhaps I have changed, I certainly learned a lot along the way. Either way, I've decided to do things different. + +## The problem with a CMS + +I have no beef with Drupal but the idea of managing the freesewing website through any Content Management System (CMS) does not appeal to me. + +One of the main reason is that so much information is stored under an opaque database layer which makes it difficult to manage. +That goes for content where posts, metadata, images, and so on is all spread across tables, locations, and folders. +But there's also the theme that has a bunch of stuff in it, there's the custom Drupal modules to connect to the backend, and so on and so forth. + +> I wanted that same approach in a website. Except, it can't be static because it has to, you know, do stuff. + +When we were finalizing core, I built a documentation site for it based on [Jekyll](https://jekyllrb.com/). It felt like a breath of fresh air in comparison. +Just a bunch of markdown files, with some SASS, images, and some JavaScript thrown in the mix, and it all compiles into a neat static website. + +It's easy to manage, and it integrates nicely with a GitHub-centered workflow that is going to be famliar to potential contributors. + +I wanted that same approach in a website. Except, it can't be static because it has to, you know, do stuff. + + +## An alternative approach: JAMstack + +I first learned about JAMstack when I started looking into hosting for said core documentation site. +It was initially hosted on GitHub pages which provides free hosting. +They also have SSL or a custom domain name, but you can't have both. Which was kind of a deal breaker. + +Looking for alternatives, I stumbled onto [Netlify](https://www.netlify.com/), who do both SSL and custom domains and have a free-tier for open source projects (thanks guys). +Furthermore, [this video by Netlify CEO Mathias Biilmann](https://vimeo.com/163522126) got me really excited about JAMstack. + +Unless you're familiar with JAMstack, I suggest you check out the video, but it boils down to this: + + - **J** = JavaScript + - **A** = APIs + - **M** = Markup + +The idea is that you build your static site (markup) that you then make interactive with JavaScript that hooks up to one or more APIs. + +So in our case, rather than having a straight-forward documentation site with easy-to-edit markdown and a complex CMS to handle the dymanic stuff, let's just build one simple site that is statically generated, yet uses JavaScript and APIs to do the smart stuff. + +## Running before you can walk + +I must admit that in my enthousiasm to embrace this new approach I got a little ahead of myself. +Suddenly, I was no longer building a simple site, but I was up to my eyeballs in isomorphic rendering, client-side routing, React and Redux, Node.js and ES6 transpiling. + +> If you don't know what any of that means, you might get a hint of the frustration I felt as I was trying to tame all these new beasts. +> +> If you do know what it all means, where were you back in April when I walked through the valley of the React of death? + +Point is, I'm not a developer and I was in way over my head. +While I was learning new things every day, I wasn't making much progress on the actual task at hand, and felt frustrated with my inability to do even the most mundane things. + +After a month of frustration, loads of trial and seemingly even more error, I threw in the towel. +Eff this newfangled shiny JavaScript all the young kids are using, I'll stick to what I know. + +Which is essentially the basics of jQuery. In other words, stuff that was pretty cool 10 years ago. + +## 10 year old jam is still jam right? + +So here we are, freesewing.org is a site powered by the JAMstack. And you know what, it seems to do what it needs to do. + +We have Jekyll build out static site, and when we push to our master branch, it gets autmatically deployed to Netlify. + +> Eff this newfangled shiny JavaScript all the young kids are using + +We have [a brand new data API](https://github.com/freesewing/data) build on [the Slim framework](https://www.slimframework.com/). +It handles all user data. Things like accounts, measurements, models, and drafts, but also comments on this website and so on. + +It also talks to core for us, and every time you draft a pattern, we don't just give you the pattern, but we also run a comparison of your pattern to a range of standard sizes, which is kinda cool. + +And we have other cool stuff, like the ability to fork or redraft an existing draft. + +## This is a starting point + +I hope the user experience/interface is not going to be a roadblock for people. +I've made a great deal of effort to make the drafting process as intuitive as possible and I think that in comparison to our demo (or the makemypattern interface for that matter) it's a vast improvement. + +Then again, I'm sure things will break left or right, or that some of you don't like the colours or whatnot. + +The point is that I set out to build something that can replace makemypattern.com so that I could tell all of you _Hey, come over and play with this new thing_. + +I think if nothing else, I can do that now. And if you see room for improvement, please [join the effort](/contribute), we're only getting started. + + + +PS: For those of you wondering about the title of this post: + + + + diff --git a/markdown/org/blog/freesewing-goes-jamstack/nl.md b/markdown/org/blog/freesewing-goes-jamstack/nl.md new file mode 100644 index 00000000000..68ea1006649 --- /dev/null +++ b/markdown/org/blog/freesewing-goes-jamstack/nl.md @@ -0,0 +1,106 @@ +--- +author: "joostdecock" +caption: "Picture by Jennifer" +date: "2017-06-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/952f714d11203d03a449895053c63963b0c02dbd-2000x1126.jpg" +intro: "When we released freesewing core at the end of March, my focus immeadiatly shifted to building our front-end so that freesewing.org could fully replace makemypattern.com ." +title: "We're JAMstack, we're JAMstack, we're JAMstack, we're JAMstack, we're JAMstack, we're JAMstack, we're JAMstack, and I hope you like JAMstack too [Niet vertaald]" +--- + +When we released freesewing core at the end of March, my focus immeadiatly shifted to building our front-end so that [freesewing.org](/) could fully replace [makemypattern.com](https://makemypattern.com/). + +I believe that the value of freesewing lies with the core platform and our patterns. +But without a user friendly way to expose that value, it will largely go ignored. + +So we needed a website that lets people generate patterns. Makemypattern.com — arguably the best comparison of something similar — runs on Drupal 7, and my initial idea was to run the new site on Drupal 8. +I went down that path far enought to be confident I could get it to work, and hook it up to our backend. At which point I switched gears and turned my attention to what is now known as freesewing core. + +Core took about 7 months to build, and a lot has changed since then. Or perhaps I have changed, I certainly learned a lot along the way. Either way, I've decided to do things different. + +## The problem with a CMS + +I have no beef with Drupal but the idea of managing the freesewing website through any Content Management System (CMS) does not appeal to me. + +One of the main reason is that so much information is stored under an opaque database layer which makes it difficult to manage. +That goes for content where posts, metadata, images, and so on is all spread across tables, locations, and folders. +But there's also the theme that has a bunch of stuff in it, there's the custom Drupal modules to connect to the backend, and so on and so forth. + +> I wanted that same approach in a website. Except, it can't be static because it has to, you know, do stuff. + +When we were finalizing core, I built a documentation site for it based on [Jekyll](https://jekyllrb.com/). It felt like a breath of fresh air in comparison. +Just a bunch of markdown files, with some SASS, images, and some JavaScript thrown in the mix, and it all compiles into a neat static website. + +It's easy to manage, and it integrates nicely with a GitHub-centered workflow that is going to be famliar to potential contributors. + +I wanted that same approach in a website. Except, it can't be static because it has to, you know, do stuff. + + +## An alternative approach: JAMstack + +I first learned about JAMstack when I started looking into hosting for said core documentation site. +It was initially hosted on GitHub pages which provides free hosting. +They also have SSL or a custom domain name, but you can't have both. Which was kind of a deal breaker. + +Looking for alternatives, I stumbled onto [Netlify](https://www.netlify.com/), who do both SSL and custom domains and have a free-tier for open source projects (thanks guys). +Furthermore, [this video by Netlify CEO Mathias Biilmann](https://vimeo.com/163522126) got me really excited about JAMstack. + +Unless you're familiar with JAMstack, I suggest you check out the video, but it boils down to this: + + - **J** = JavaScript + - **A** = APIs + - **M** = Markup + +The idea is that you build your static site (markup) that you then make interactive with JavaScript that hooks up to one or more APIs. + +So in our case, rather than having a straight-forward documentation site with easy-to-edit markdown and a complex CMS to handle the dymanic stuff, let's just build one simple site that is statically generated, yet uses JavaScript and APIs to do the smart stuff. + +## Running before you can walk + +I must admit that in my enthousiasm to embrace this new approach I got a little ahead of myself. +Suddenly, I was no longer building a simple site, but I was up to my eyeballs in isomorphic rendering, client-side routing, React and Redux, Node.js and ES6 transpiling. + +> If you don't know what any of that means, you might get a hint of the frustration I felt as I was trying to tame all these new beasts. +> +> If you do know what it all means, where were you back in April when I walked through the valley of the React of death? + +Point is, I'm not a developer and I was in way over my head. +While I was learning new things every day, I wasn't making much progress on the actual task at hand, and felt frustrated with my inability to do even the most mundane things. + +After a month of frustration, loads of trial and seemingly even more error, I threw in the towel. +Eff this newfangled shiny JavaScript all the young kids are using, I'll stick to what I know. + +Which is essentially the basics of jQuery. In other words, stuff that was pretty cool 10 years ago. + +## 10 year old jam is still jam right? + +So here we are, freesewing.org is a site powered by the JAMstack. And you know what, it seems to do what it needs to do. + +We have Jekyll build out static site, and when we push to our master branch, it gets autmatically deployed to Netlify. + +> Eff this newfangled shiny JavaScript all the young kids are using + +We have [a brand new data API](https://github.com/freesewing/data) build on [the Slim framework](https://www.slimframework.com/). +It handles all user data. Things like accounts, measurements, models, and drafts, but also comments on this website and so on. + +It also talks to core for us, and every time you draft a pattern, we don't just give you the pattern, but we also run a comparison of your pattern to a range of standard sizes, which is kinda cool. + +And we have other cool stuff, like the ability to fork or redraft an existing draft. + +## This is a starting point + +I hope the user experience/interface is not going to be a roadblock for people. +I've made a great deal of effort to make the drafting process as intuitive as possible and I think that in comparison to our demo (or the makemypattern interface for that matter) it's a vast improvement. + +Then again, I'm sure things will break left or right, or that some of you don't like the colours or whatnot. + +The point is that I set out to build something that can replace makemypattern.com so that I could tell all of you _Hey, come over and play with this new thing_. + +I think if nothing else, I can do that now. And if you see room for improvement, please [join the effort](/contribute), we're only getting started. + + + +PS: For those of you wondering about the title of this post: + + + + diff --git a/markdown/org/blog/freesewing-v2-1/de.md b/markdown/org/blog/freesewing-v2-1/de.md new file mode 100644 index 00000000000..9a83cca8110 --- /dev/null +++ b/markdown/org/blog/freesewing-v2-1/de.md @@ -0,0 +1,86 @@ +--- +author: "joostdecock" +caption: "In diesem Beitrag geht es hauptsächlich um unsere Arbeit an der progressiven Offenlegung. Außerdem: Drei neue Schnittmuster!" +date: "2019-10-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/52db6852590a15208dace4a16a6a1c824037e400-2000x1500.jpg" +intro: "Wir haben gerade FreeSewing v2.1 veröffentlicht 🎉" +title: "FreeSewing v2.1: Drei neue Muster, Expertenmodus und Hilfe beim Massnehmen" +--- + + +Wir haben gerade FreeSewing v2.1 veröffentlicht 🎉 + +## Treffen Sie Penelope, Waralee und Simone + +Es gibt 3 neue Schnittmuster in dieser Version: + + - [Penelope](/patterns/penelope) ist ein Bleistiftrock von [Wouter Van Wageningen](/users/wouter.vdub) + - [Waralee](/patterns/waralee) sind Wickelhosen, auch von [Wouter](/users/wouter.vdub) + - [Simone](/patterns/simone) ist Simon (unser vielseitiges Button-Down-Muster) für Brüste angepasst durch [Joost De Cock](/users/joost) + +Alle diese Muster sind entweder Damenmode oder - im Falle von Waralee - Unisex-Kleidung. Was ein Zeichen für unser Engagement ist, mehr Damenmode auf die Website zu bringen. + +Neben der Entwicklung neuer Muster sind viele Anstrengungen unternommen worden, um die Dinge einfacher zu machen, ohne sie dümmer zu machen. Lassen Sie mich das erklären: + +## Unsere Arbeit an der progressiven Offenlegung + +Eine Balance zu finden, die es unseren Nutzern ermöglicht, die gesamte Leistungsfähigkeit der Plattform zu nutzen und gleichzeitig den Einstieg für Neueinsteiger zu erleichtern, ist eine ständige Herausforderung. Wir haben begonnen, dieses Problem mit der sogenannten *progressiven Offenlegung der Komplexität* anzugehen. + +Die Idee - die wir nicht erfunden haben, aber ein Konzept im UX-Design ist - ist es, die Erfahrung für die meisten Menschen zu vereinfachen, ohne die Fähigkeiten fortgeschrittenerer Benutzer einzuschränken. + +Wir konzentrieren unsere Aufmerksamkeit für eine schrittweise Offenlegung auf zwei Bereiche, die diejenigen sind, mit denen unsere Benutzer am häufigsten zu kämpfen haben: + + - **Schnittmusteroptionen**: Unsere Schnittmuster haben oft Dutzende von Optionen. Das ist großartig für diejenigen, die gerne jedes Detail ihres Musters abstimmen, aber für Neulinge kann ein wenig überwältigend sein + - **Masse**: Genaues Massnehmen ist entscheidend für gute Ergebnisse mit unseren Schnittmustern, aber nicht so trivial, wie Sie denken würden. + +Obwohl wir noch nicht da sind wo wir hin wollen, haben wir bei beidem Fortschritte gemacht. Schauen wir uns an, worum es geht: + +### Schnittmusteroptionen: Hier haben wir jetzt einen Expertenmodus, und der ist standardmäßig ausgeschaltet + +(einige von) unseren Schnitten haben seit einiger Zeit *erweiterte Optionen*, aber die sind nun standardmäßig ausgeblendet. Das heißt, bis Sie den **Expertenmodus** in den Einstellungen (unterhalb der Schnittmusteroptionen) einschalten. + +Neben den erweiterten Musteroptionen zeigt der Exportmodus auch die weniger verwendeten Entwurfseinstellungen wie die Möglichkeit, Sprache, Einheiten, Details, Nahtzugabe und Inhalt Ihres Entwurfs zu ändern. + +![Erweiterter Modus](recreate.png) + + + +######## Auch angezeigt: Muster vs. Rezeptvorgaben + +Wenn Sie Ihren Entwurf konfigurieren, verfügt jede Option über eine kleine Schaltfläche, um den Standardwert für diese Option wiederherzustellen. +Die Dinge werden komplizierter, wenn Sie ein Rezept erneut erstellen. Wenn Sie nun den Standardwert wiederherstellen, ist es dann der Musterstandard oder der Standard des Rezepts? + +Die Antwort war bisher: der Schnittmusterstandardwert, aber mit dieser Version werden Sie feststellen, dass Optionen, bei denen der Rezeptstandard vom Musterstandard abweicht, zwei Schaltflächen haben. Das eine stellt die Schnittmusterstandardwerte wieder her, das an die Standardwerte des Rezepts. + +Sie können dies im Screenshot oben sehen. + + + +### Masse: Helfen Ihnen die Fehler in Ihren gemessenen Massen zu entdecken + +Wir haben ein paar Indikatoren hinzugefügt, die Ihnen helfen sollen, Fehler oder Probleme beim Massnehmen. Ihre Modelle zeigen nun eine grafische Darstellung Ihrer Körpermaße, mit der Sie Ausreißer erkennen können. + +![Eine grafische Darstellung der Maße Ihres Modells](model.png) + +Zusätzlich zeigen wir Ihnen neben dem Istwert eine Schätzung Ihrer verschiedenen Maße (bezogen auf Ihren Halsumfang). Wenn der Unterschied größer wird, werden wir Sie darauf aufmerksam machen. + +Dies ist ein schwieriges Arbeitsfeld für uns. Wir möchten Ihnen helfen, die besten Ergebnisse zu erzielen, und dazu gehört auch, dass wir Ihnen helfen, Probleme beim Massnehmen zu erkennen. Auf der anderen Seite wollen wir keinesfalls annehmen, dass die Maße von einem Menschen *falsch* irgendwie falsch sein könnten. + +Wir sind eine extrem size-inklusive Plattform für Schnittmuster, und ein sehr hoher Anteil unserer Nutzer sind Menschen, die Schwierigkeiten haben, Kleidung oder Schnittmuster bei anderen Anbietern zu finden. Auf der einen Seite könnte es also so aussehen, als ob wir uns auf Fehler einstellen würden, indem wir Messungen mit einem Satz von mehr oder weniger *Standard*Massen vergleichen. Aber du kennst deinen Körper. Sie wissen, welche Ihrer Körpermasse vom Durchschnitt abweichen. Und dass wir darauf hinweisen, dass sie es tun, ist in gewisser Weise nur eine Bestätigung dafür, dass Sie richtig gemessen haben. Wenn andererseits etwas hervorsticht, wo Sie ziemlich durchschnittliche Masse habem, wissen Sie, dass Sie diese Messung vermutlich überprüfen sollten. + +Last but not least, während wir versuchen, eine Anleitung für Messungen zu geben, um Fehler zu erkennen, schließen wir niemanden aus egal in welcher Größe oder Abmessung. Egal, was Sie uns an den Kopf werfen, wir werden ein Muster entwerfen, das für Sie funktioniert, oder (unsere Software wird) bei dem Versuch sterben. + +## Weitere Änderungen + + - Für unsere Vergleichsansichten haben wir unsere Größenbereiche erweitert. Die Größen für Herrenmode werden jetzt von Größe 32 bis 48 gesampelt, während für Damenmode von Größe 28 bis 46. + - Wir haben einige Änderungen an den Standardeinstellungen im Simon-Muster vorgenommen, basierend auf unseren Tests mit Simone + - Wir haben unsere Entwicklungsumgebung für Schnittmusterdesigner um die Möglichkeit erweitert, Modelle mit Brüsten als Preload einzustellen + - Wir haben Korrekturen und Verbesserungen an unseren Scnittmustern Jaeger, Bruce, Benajamin, Simon, Carlton und Carlita vorgenommen + - Wir haben der Dokumentation eine Reihe fehlender Bilder hinzugefügt und [bemüht, sicherzustellen, dass alle Optionen mit einem Bild versehen sind, um ihren Verwendungszweck zu veranschaulichen](https://github.com/freesewing/freesewing.org/issues/190). + +Weitere Informationen finden Sie [im Changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md). + +We hope you enjoy this release, and please [stop by our chat room](https://discord.freesewing.org/) to share your thoughts, feedback, suggestions, or ideas. Wir freuen uns, von Ihnen zu hören + + + diff --git a/markdown/org/blog/freesewing-v2-1/en.md b/markdown/org/blog/freesewing-v2-1/en.md new file mode 100644 index 00000000000..cad40833fbf --- /dev/null +++ b/markdown/org/blog/freesewing-v2-1/en.md @@ -0,0 +1,92 @@ +--- +author: "joostdecock" +caption: "This post is mostly about our work on progressive disclosure. Also: Three new patterns!" +date: "2019-10-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/52db6852590a15208dace4a16a6a1c824037e400-2000x1500.jpg" +intro: "We've just release FreeSewing v2.1 🎉" +title: "FreeSewing v2.1: Three new patterns, expert mode, and help with measurements" +--- + + +We've just release FreeSewing v2.1 🎉 + +## Meet Penelope, Waralee, and Simone + +There are 3 new patterns in this release: + + - [Penelope](/patterns/penelope) is a pencil skirt by [Wouter Van Wageningen](/users/wouter.vdub) + - [Waralee](/patterns/waralee) are wrap pants, also by [Wouter](/users/wouter.vdub) + - [Simone](/patterns/simone) is Simon (our versatile button-down pattern) adapted for breasts by [Joost De Cock](/users/joost) + +All of these patterns are either womenswear or -- in the case of Waralee -- unisex clothing. Which in an indication of our commitment to bring more womenswear patterns to the site. + +Apart from creating new patterns, a lot of efforts have gone into making things simpler, without making them dumber. Let me explain: + +## Our work on progressive disclosure + +Striking a balance between giving our users all the power of the platform, yet making it easy for newcomers to get started, is an ongoing challenge. We have started making inroads into addressing that issue with so-called *progressive disclosure of complexity*. + +The idea -- which we didn't make up, but is a concept in UX design -- is to simplify the experience for most people without limiting the abilities of more advanced users. + +We are focusing our attention for progressive disclosure on two areas that are the ones that our users most often struggle with: + + - **Pattern options**: Our patterns often come with dozens of options. That is great for those who like to fine-tune every detail of their pattern, but can be a bit overwhelming for newcomers + - **Measurements**: Taking accurate measurements is crucial for good results with our patterns, yet not as trivial as you would think. + +While we're certainly not there yet, we've made progress on both of these. Let's look at what we've been up to: + +### Pattern options: We now have an expert mode, and it's off by default + +(some of) Our patterns have had *advanced options* for a while, but they are now hidden by default. That is until you turn on the **Expert mode** in the settings (below the pattern options). + +Apart from advanced pattern options, export mode also reveals the lesser-used draft settings such as the ability to change the language, units, details, margin, and contents of your draft. + +![Advanced mode](https://posts.freesewing.org/uploads/recreate_a6e2f9c4d6.png) + + + +###### Also shown: Pattern vs Recipe defaults + +When configuring your draft, every option has a little button to restore the default value for that option. +Things get more complicated when you're re-creating a recipe. Now when you restore the default, is it the pattern default, or the recipe's default? + +The answer used to be the pattern default, but with this release, you'll find that options where the recipe default is different from the pattern +default will have two buttons. Once to restore the pattern default, and another to restore the recipe default. + +You can see this in the screenshot above. + + + + +### Measurements: Helping you spot mistakes in your measurements + +We've added a few indicators to help you spot mistakes or problems in your measurements. Your models will now show a graphical representation of your body measurements, which will allow you to spot any outliers. + +![A graphical representation of your model's measurements](https://posts.freesewing.org/uploads/model_c3fa8fc50c.png) + +In addition, we are showing you an estimate of your different measurements (based on your neck circumference) next to the actual value. If the difference gets larger, we'll draw your attention to that. + +This is a difficult area for us to work in. We want to help you get the best results, and that includes helping you spot issues with your measurements. On the other hand, we in no way want to imply that someone's measurements are *wrong* somehow. + +We are an extremely size-inclusive pattern outlet, and a disproportionate amount of our users are people who struggle to find clothes or patterns from other outlets. So on one hand, it might seem like we're setting ourselves up for failure by comparing measurements to a set of more or less *standard* measurements. +But you know your body. You know which of your measurements deviate from the average. And us pointing out that they do is in a way only confirmation that you've been measuring correctly. +On the other hand, if something jumps out where you are fairly average sized, you know to double-check those measurements. + +Last but not least, while we try to provide guidance about measurements to help spot mistakes, we never exclude anyone based on size or measurement. No matter what you throw at us, we will draft a pattern that works for you, or (our software will) die trying. + +## Other changes + + - We have extended our size ranges for our comparison views. Menswear sizes are now sampled from size 32 up to 48, while womenswear is sampled from size 28 up to 46. + - We've made some changes to the defaults in the Simon pattern, based on our tests with Simone + - We've added support for preloading models with breasts to our development environment for pattern designers + - We've implemented fixes and improvements in our Jaeger, Bruce, Benajamin, Simon, Carlton, and Carlita patterns + - We've added a bunch of missing images in the documentation, and [started an effort to make sure all options have an image to illustrate their purpose](https://github.com/freesewing/freesewing.org/issues/190). + +More information is available [in the changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md). + +We hope you enjoy this release, and please [stop by our chat room](https://discord.freesewing.org/) to share your thoughts, feedback, suggestions, or ideas. We'd love to hear from you + + + + + diff --git a/markdown/org/blog/freesewing-v2-1/es.md b/markdown/org/blog/freesewing-v2-1/es.md new file mode 100644 index 00000000000..96911e522e0 --- /dev/null +++ b/markdown/org/blog/freesewing-v2-1/es.md @@ -0,0 +1,92 @@ +--- +author: "joostdecock" +caption: "This post is mostly about our work on progressive disclosure. Also: Three new patterns!" +date: "2019-10-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/52db6852590a15208dace4a16a6a1c824037e400-2000x1500.jpg" +intro: "We've just release FreeSewing v2.1 🎉" +title: "FreeSewing v2.1: Three new patterns, expert mode, and help with measurements [No traducido]" +--- + + +We've just release FreeSewing v2.1 🎉 + +## Meet Penelope, Waralee, and Simone + +There are 3 new patterns in this release: + + - [Penelope](/patterns/penelope) is a pencil skirt by [Wouter Van Wageningen](/users/wouter.vdub) + - [Waralee](/patterns/waralee) are wrap pants, also by [Wouter](/users/wouter.vdub) + - [Simone](/patterns/simone) is Simon (our versatile button-down pattern) adapted for breasts by [Joost De Cock](/users/joost) + +All of these patterns are either womenswear or -- in the case of Waralee -- unisex clothing. Which in an indication of our commitment to bring more womenswear patterns to the site. + +Apart from creating new patterns, a lot of efforts have gone into making things simpler, without making them dumber. Let me explain: + +## Our work on progressive disclosure + +Striking a balance between giving our users all the power of the platform, yet making it easy for newcomers to get started, is an ongoing challenge. We have started making inroads into addressing that issue with so-called *progressive disclosure of complexity*. + +The idea -- which we didn't make up, but is a concept in UX design -- is to simplify the experience for most people without limiting the abilities of more advanced users. + +We are focusing our attention for progressive disclosure on two areas that are the ones that our users most often struggle with: + + - **Pattern options**: Our patterns often come with dozens of options. That is great for those who like to fine-tune every detail of their pattern, but can be a bit overwhelming for newcomers + - **Measurements**: Taking accurate measurements is crucial for good results with our patterns, yet not as trivial as you would think. + +While we're certainly not there yet, we've made progress on both of these. Let's look at what we've been up to: + +### Pattern options: We now have an expert mode, and it's off by default + +(some of) Our patterns have had *advanced options* for a while, but they are now hidden by default. That is until you turn on the **Expert mode** in the settings (below the pattern options). + +Apart from advanced pattern options, export mode also reveals the lesser-used draft settings such as the ability to change the language, units, details, margin, and contents of your draft. + +![Advanced mode](https://posts.freesewing.org/uploads/recreate_a6e2f9c4d6.png) + + + +###### Also shown: Pattern vs Recipe defaults + +When configuring your draft, every option has a little button to restore the default value for that option. +Things get more complicated when you're re-creating a recipe. Now when you restore the default, is it the pattern default, or the recipe's default? + +The answer used to be the pattern default, but with this release, you'll find that options where the recipe default is different from the pattern +default will have two buttons. Once to restore the pattern default, and another to restore the recipe default. + +You can see this in the screenshot above. + + + + +### Measurements: Helping you spot mistakes in your measurements + +We've added a few indicators to help you spot mistakes or problems in your measurements. Your models will now show a graphical representation of your body measurements, which will allow you to spot any outliers. + +![A graphical representation of your model's measurements](https://posts.freesewing.org/uploads/model_c3fa8fc50c.png) + +In addition, we are showing you an estimate of your different measurements (based on your neck circumference) next to the actual value. If the difference gets larger, we'll draw your attention to that. + +This is a difficult area for us to work in. We want to help you get the best results, and that includes helping you spot issues with your measurements. On the other hand, we in no way want to imply that someone's measurements are *wrong* somehow. + +We are an extremely size-inclusive pattern outlet, and a disproportionate amount of our users are people who struggle to find clothes or patterns from other outlets. So on one hand, it might seem like we're setting ourselves up for failure by comparing measurements to a set of more or less *standard* measurements. +But you know your body. You know which of your measurements deviate from the average. And us pointing out that they do is in a way only confirmation that you've been measuring correctly. +On the other hand, if something jumps out where you are fairly average sized, you know to double-check those measurements. + +Last but not least, while we try to provide guidance about measurements to help spot mistakes, we never exclude anyone based on size or measurement. No matter what you throw at us, we will draft a pattern that works for you, or (our software will) die trying. + +## Other changes + + - We have extended our size ranges for our comparison views. Menswear sizes are now sampled from size 32 up to 48, while womenswear is sampled from size 28 up to 46. + - We've made some changes to the defaults in the Simon pattern, based on our tests with Simone + - We've added support for preloading models with breasts to our development environment for pattern designers + - We've implemented fixes and improvements in our Jaeger, Bruce, Benajamin, Simon, Carlton, and Carlita patterns + - We've added a bunch of missing images in the documentation, and [started an effort to make sure all options have an image to illustrate their purpose](https://github.com/freesewing/freesewing.org/issues/190). + +More information is available [in the changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md). + +We hope you enjoy this release, and please [stop by our chat room](https://discord.freesewing.org/) to share your thoughts, feedback, suggestions, or ideas. We'd love to hear from you + + + + + diff --git a/markdown/org/blog/freesewing-v2-1/fr.md b/markdown/org/blog/freesewing-v2-1/fr.md new file mode 100644 index 00000000000..09477f96e49 --- /dev/null +++ b/markdown/org/blog/freesewing-v2-1/fr.md @@ -0,0 +1,87 @@ +--- +author: "joostdecock" +caption: "Ce message traite principalement de notre travail sur la révélation progressive. De plus : trois nouveaux modèles !" +date: "2019-10-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/52db6852590a15208dace4a16a6a1c824037e400-2000x1500.jpg" +intro: "Nous venons juste de publier FreeSewing v2.1 🎉" +title: "FreeSewing v2.1 : Trois nouveaux modèles, un mode expert et l'aide aux mesures" +--- + + +Nous venons juste de publier FreeSewing v2.1 🎉 + +## Rencontrez Pénelope, Waralee et Simone + +Il y a 3 nouveaux modèles dans cette nouvelle version : + + - [Penelope](/patterns/penelope) est une jupe crayon de [Wouter Van Wageningen](/users/wouter.vdub) + - [Waralee](/patterns/waralee) est un pantalon "pareo" (aussi dit thaïlandais), aussi de [Wouter](/users/wouter.vdub) + - [Simone](/patterns/simone) est Simon (notre versatile patron boutonné) adapté pour les seins, de [Joost De Cock](/users/joost) + +Tous ces patrons sont des vêtements féminins ou -- dans le cas de Waralee -- unisexes. Ceci est donc une démonstration de notre engagement à apporter plus de modèles de vêtements féminins sur le site. + +En plus de créer de nouveaux modèles, de nombreux efforts ont été réalisés pour simplifier les choses, sans les rendre plus limitées. Je m’explique : + +## Notre travail sur la révélation progressive + +Trouver un équilibre entre donner à nos utilisateurs toute la puissance de la plate-forme, tout en facilitant le démarrage des nouveaux arrivants, est un défi permanent. Nous avons commencé à faire des progrès dans la résolution de ce problème avec ce que l'on appelle *révélation progressive de la complexité*. + +L'idée -- que nous n'avons pas inventée, mais c'est un concept dans la conception d'UX (= expérience utilisateur) -- est de simplifier l'expérience pour la majorité des gens sans limiter les capacités des utilisateurs plus avancés. + +Nous concentrons notre attention pour la révélation progressive sur deux sujets pour lesquels nos utilisateurs débattent le plus souvent : + + - **Options des patrons** : Nos patrons offrent souvent une douzaine d'options. C'est génial pour ceux qui aiment affiner chaque détail de leur modèle, mais peut-être un peu accablant pour les nouveaux arrivants + - **Mesures** : Il est essentiel de prendre des mesures précises pour obtenir de bons résultats avec nos modèles ; ce n'est pas aussi futile que vous le pensez. + +Bien que nous n'en soyons certainement pas encore là, nous avons fait des progrès sur ces deux points. Voyons ce que nous avons déjà réussi : + +### Options de patron : Nous avons maintenant un mode expert, et il est désactivé par défaut + +(certains de) Nos patrons ont des *options avancées* depuis un certain temps, mais ils sont maintenant cachés par défaut. Ceci jusqu'à ce que vous activiez le **Mode Expert** dans les paramètres (ci-dessous les options de patron). + +Hormis les options avancées de patron, le mode export révèle également les paramètres de brouillon moins utilisés comme la possibilité de changer la langue, l'unité, les détails, les marges et le contenu de votre brouillon. + +![Mode avancé](recreate.png) + + + +###### Également affiché : Patron vs Recette par défaut + +Lors de la configuration de votre brouillon, chaque option a un petit bouton pour restaurer la valeur par défaut de cette option. +Les choses deviennent plus compliquées lorsque vous recréez une recette. Maintenant, lorsque vous restaurez la valeur par défaut, est-ce le patron par défaut ou la recette par défaut ? + +La réponse était le modèle par défaut, mais avec cette nouvelle version, vous verrez que les options où la valeur par défaut de la recette est différente du patron +auront deux boutons. Un pour restaurer le patron par défaut, et un autre pour restaurer la recette par défaut. + +Vous pouvez le voir dans la capture d'écran ci-dessus. + + + +### Mesures : Vous aider à détecter les erreurs dans vos mensurations + +Nous avons ajouté quelques indicateurs pour vous aider à repérer des erreurs ou des problèmes dans vos mesures. Vos modèles afficheront maintenant une représentation graphique de vos mensurations, ce qui vous permettra de repérer les erreurs potentielles. + +![Une représentation graphique des mensurations de votre modèle](model.png) + +De plus, nous vous présentons une estimation de vos différentes mensurations (basées sur votre circonférence du cou) comparées à la valeur réelle. Si la différence s'accentue, nous attirerons votre attention sur ce point. + +C'est un travail difficile pour nous. Nous voulons vous aider à obtenir les meilleurs résultats, notamment en vous aidant à repérer les problèmes liés à vos mesures. D'un autre côté, nous ne voulons en aucun cas impliquer que les mesures de quelqu'un sont *erronées* d'une manière ou d'une autre. + +Nous sommes une boutique de patrons qui se veut destiné pour toutes les tailles, et une grande quantité de nos utilisateurs sont des personnes qui luttent pour trouver des vêtements ou des patrons. Donc d'une part. il peut sembler que nous nous mettons en échecs en comparant les mesures à un ensemble de mesures plus ou moins *standards*. Mais vous connaissez votre corps. Vous savez laquelle de vos mesures s'écarte de la moyenne. Et nous signalons que ce n'est d'une certaine manière que la confirmation que vous avez mesuré correctement. D'un autre côté, si une mesure s'éloigne là où vous êtes plutôt dans la moyenne, alors vous savez que vous devez vérifier cette mesure. + +Enfin et surtout, alors que nous essayons de fournir des conseils sur les mesures pour aider à détecter les erreurs, nous n'excluons jamais quiconque en fonction de sa taille ou de ses mensurations. Peu importe ce que vous nous envoyez, nous élaborerons un modèle qui fonctionne pour vous, ou on (ou plutôt notre logiciel) se tuera à essayer. + +## Autres modifications + + - Nous avons étendu notre gamme de tailles pour nos vues de comparaison. Les tailles de vêtements pour hommes sont maintenant échantillonnées de la taille 32 à 48, tandis que les vêtements pour femmes sont échantillonnés de la taille 28 à 46. + - Nous avons modifié les paramètres par défaut dans le modèle Simon, basé sur nos tests avec Simone + - Nous avons ajouté la prise en charge des modèles prédéfinis avec seins dans notre environnement de développement pour les concepteurs de patrons + - Nous avons implémenté des corrections et des améliorations dans nos patrons Jaeger, Bruce, Benajamin, Simon, Carlton et Carlita + - Nous avons ajouté un tas d'images manquantes dans la documentation, et [ débuté un travail pour s'assurer que toutes les options ont une image pour illustrer leur objectif](https://github.com/freesewing/freesewing.org/issues/190). + +Plus d'informations sont disponibles [dans le suivi des modifications](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md). + +We hope you enjoy this release, and please [stop by our chat room](https://discord.freesewing.org/) to share your thoughts, feedback, suggestions, or ideas. Nous aimerions connaître votre avis. + + + diff --git a/markdown/org/blog/freesewing-v2-1/nl.md b/markdown/org/blog/freesewing-v2-1/nl.md new file mode 100644 index 00000000000..6b97501d012 --- /dev/null +++ b/markdown/org/blog/freesewing-v2-1/nl.md @@ -0,0 +1,92 @@ +--- +author: "joostdecock" +caption: "This post is mostly about our work on progressive disclosure. Also: Three new patterns!" +date: "2019-10-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/52db6852590a15208dace4a16a6a1c824037e400-2000x1500.jpg" +intro: "We've just release FreeSewing v2.1 🎉" +title: "FreeSewing v2.1: Three new patterns, expert mode, and help with measurements [Niet vertaald]" +--- + + +We've just release FreeSewing v2.1 🎉 + +## Meet Penelope, Waralee, and Simone + +There are 3 new patterns in this release: + + - [Penelope](/patterns/penelope) is a pencil skirt by [Wouter Van Wageningen](/users/wouter.vdub) + - [Waralee](/patterns/waralee) are wrap pants, also by [Wouter](/users/wouter.vdub) + - [Simone](/patterns/simone) is Simon (our versatile button-down pattern) adapted for breasts by [Joost De Cock](/users/joost) + +All of these patterns are either womenswear or -- in the case of Waralee -- unisex clothing. Which in an indication of our commitment to bring more womenswear patterns to the site. + +Apart from creating new patterns, a lot of efforts have gone into making things simpler, without making them dumber. Let me explain: + +## Our work on progressive disclosure + +Striking a balance between giving our users all the power of the platform, yet making it easy for newcomers to get started, is an ongoing challenge. We have started making inroads into addressing that issue with so-called *progressive disclosure of complexity*. + +The idea -- which we didn't make up, but is a concept in UX design -- is to simplify the experience for most people without limiting the abilities of more advanced users. + +We are focusing our attention for progressive disclosure on two areas that are the ones that our users most often struggle with: + + - **Pattern options**: Our patterns often come with dozens of options. That is great for those who like to fine-tune every detail of their pattern, but can be a bit overwhelming for newcomers + - **Measurements**: Taking accurate measurements is crucial for good results with our patterns, yet not as trivial as you would think. + +While we're certainly not there yet, we've made progress on both of these. Let's look at what we've been up to: + +### Pattern options: We now have an expert mode, and it's off by default + +(some of) Our patterns have had *advanced options* for a while, but they are now hidden by default. That is until you turn on the **Expert mode** in the settings (below the pattern options). + +Apart from advanced pattern options, export mode also reveals the lesser-used draft settings such as the ability to change the language, units, details, margin, and contents of your draft. + +![Advanced mode](https://posts.freesewing.org/uploads/recreate_a6e2f9c4d6.png) + + + +###### Also shown: Pattern vs Recipe defaults + +When configuring your draft, every option has a little button to restore the default value for that option. +Things get more complicated when you're re-creating a recipe. Now when you restore the default, is it the pattern default, or the recipe's default? + +The answer used to be the pattern default, but with this release, you'll find that options where the recipe default is different from the pattern +default will have two buttons. Once to restore the pattern default, and another to restore the recipe default. + +You can see this in the screenshot above. + + + + +### Measurements: Helping you spot mistakes in your measurements + +We've added a few indicators to help you spot mistakes or problems in your measurements. Your models will now show a graphical representation of your body measurements, which will allow you to spot any outliers. + +![A graphical representation of your model's measurements](https://posts.freesewing.org/uploads/model_c3fa8fc50c.png) + +In addition, we are showing you an estimate of your different measurements (based on your neck circumference) next to the actual value. If the difference gets larger, we'll draw your attention to that. + +This is a difficult area for us to work in. We want to help you get the best results, and that includes helping you spot issues with your measurements. On the other hand, we in no way want to imply that someone's measurements are *wrong* somehow. + +We are an extremely size-inclusive pattern outlet, and a disproportionate amount of our users are people who struggle to find clothes or patterns from other outlets. So on one hand, it might seem like we're setting ourselves up for failure by comparing measurements to a set of more or less *standard* measurements. +But you know your body. You know which of your measurements deviate from the average. And us pointing out that they do is in a way only confirmation that you've been measuring correctly. +On the other hand, if something jumps out where you are fairly average sized, you know to double-check those measurements. + +Last but not least, while we try to provide guidance about measurements to help spot mistakes, we never exclude anyone based on size or measurement. No matter what you throw at us, we will draft a pattern that works for you, or (our software will) die trying. + +## Other changes + + - We have extended our size ranges for our comparison views. Menswear sizes are now sampled from size 32 up to 48, while womenswear is sampled from size 28 up to 46. + - We've made some changes to the defaults in the Simon pattern, based on our tests with Simone + - We've added support for preloading models with breasts to our development environment for pattern designers + - We've implemented fixes and improvements in our Jaeger, Bruce, Benajamin, Simon, Carlton, and Carlita patterns + - We've added a bunch of missing images in the documentation, and [started an effort to make sure all options have an image to illustrate their purpose](https://github.com/freesewing/freesewing.org/issues/190). + +More information is available [in the changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md). + +We hope you enjoy this release, and please [stop by our chat room](https://discord.freesewing.org/) to share your thoughts, feedback, suggestions, or ideas. We'd love to hear from you + + + + + diff --git a/markdown/org/blog/freesewing-v2-7/de.md b/markdown/org/blog/freesewing-v2-7/de.md new file mode 100644 index 00000000000..a93646ced42 --- /dev/null +++ b/markdown/org/blog/freesewing-v2-7/de.md @@ -0,0 +1,75 @@ +--- +author: "joostdecock" +caption: "Photo by Deeana Creates from Pexels" +date: "2020-07-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f04cc6c50a8e5f08f3ebd6c3d4903fb3055c9a01-1920x1280.jpg" +intro: "We've just release FreeSewing v2.7 🎉" +title: "FreeSewing v2.7: Titan, changes to measurements, and a long list of improvements [Nicht übersetzt]" +--- + + +We've just release FreeSewing v2.7 🎉 + +There's a lot of work that went into this release, and unfortunately it also will cause some breaking changes to your existing patterns and people, but it's all for the better. + +Let's have a look at what's new: + +## Titan trouser block + +I have lost count of the number of times I have started working on a trouser block over the last couple of years. It's something that's been on my to-do list for a long time, yet despite several attempts at making it happen, I hadn't come up with something that I was happy with. + +That's because designing trouser patterns is hard. Making sure things fit, while also guaranteeing that inseam, outseam, and cross seam are all the same length is no walk in the park. Especially if you want a pattern that will seamlessly adapt to different sizes and models. + +It would have probably lingered on my to-do list a while longer, but in February, Debra reached out to me and proposed we would come up with a pants sloper together. I love teaming up with people because it a great way to stay motivated, so over the next 4 months or so, we worked on what Debra has named [Titan](/designs/titan/), a dart-free unisex trouser block. I'd like to thank her for her patience and contributions to make Titan a success + + + +###### Help us out: Make a Titan muslin + +A block is just that, a block or sloper. Our next steps are obviously this spin this into a number of different trouser patterns. Before we get to that though, we'd like to see how Titan performs on a variety of bodies. + +So if you could whip up a muslin of a made-to-measure Titan and let us know how it went, that would be wonderful. + + + +## Shoulder slope — again — and other changes to measurements + +We've made changes to the different measurements on the site. The roughly fall into 3 categories: + + - We've made *waist* the basis for vertical measurements + - We've changed the shoulder slope measurement + - We've simplified the language and terms + +As a result, some vertical measurements that were not based on the waist are not gone (hips to upper leg for example). Other measurements have been renamed under the hood to make things simpler, but unless you're a developer, you don't need to worry about that. + +An important change is the one we made to the shoulder slope measurement. It's historically been a measurement that is hard to measure, and the changes we've made before to try to address that were in retrospect a bad idea. + +We've changed it again, but this time around, shoulder slope is measured as you would expect a slope to be measured: in degrees. + +This required some changes as up until now all measurements used the same units, but things should be ok now. + +As a result of all these changes and measurements, there's two things you should know: + + - The people you have in your account will have their measurements updated (when the names changed) or removed (where the measurement is no longer used, or we changed how to measure it) + - Patterns that you have saved in your account that use some of the changed measurements will no longer work. However, we've kept them in your account so that if you want, you can extract the data, and re-draft them for the new measurements. Feel free to reach out if you need assistance with that. + + + +We've migrated our backend to these new measurements, but you are likely to still have some of the old stuff cached in your profile. +To get around this, you should probably [reload your account](/account/reload/). + + + +## Frontend changes + +We've made a few changes to the website too. + + - We've added a [pattern notation guide](/docs/various/notation/) to take the guesswork out of what those markings on your pattern mean. + - We've added a [reload account](/account/actions/reload/) page to help you avoid issues due to cached account data + - We've changed the styling of the different sizes when you compare a pattern, as well as included a legend showing which outline corresponds to which size. + + +## And many more changes under the hood + +As I said, a lot of work went into this release. See our [monorepo changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md) for all the details. + diff --git a/markdown/org/blog/freesewing-v2-7/en.md b/markdown/org/blog/freesewing-v2-7/en.md new file mode 100644 index 00000000000..52faca99808 --- /dev/null +++ b/markdown/org/blog/freesewing-v2-7/en.md @@ -0,0 +1,75 @@ +--- +author: "joostdecock" +caption: "Photo by Deeana Creates from Pexels" +date: "2020-07-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f04cc6c50a8e5f08f3ebd6c3d4903fb3055c9a01-1920x1280.jpg" +intro: "We've just release FreeSewing v2.7 🎉" +title: "FreeSewing v2.7: Titan, changes to measurements, and a long list of improvements" +--- + + +We've just release FreeSewing v2.7 🎉 + +There's a lot of work that went into this release, and unfortunately it also will cause some breaking changes to your existing patterns and people, but it's all for the better. + +Let's have a look at what's new: + +## Titan trouser block + +I have lost count of the number of times I have started working on a trouser block over the last couple of years. It's something that's been on my to-do list for a long time, yet despite several attempts at making it happen, I hadn't come up with something that I was happy with. + +That's because designing trouser patterns is hard. Making sure things fit, while also guaranteeing that inseam, outseam, and cross seam are all the same length is no walk in the park. Especially if you want a pattern that will seamlessly adapt to different sizes and models. + +It would have probably lingered on my to-do list a while longer, but in February, Debra reached out to me and proposed we would come up with a pants sloper together. I love teaming up with people because it a great way to stay motivated, so over the next 4 months or so, we worked on what Debra has named [Titan](/designs/titan/), a dart-free unisex trouser block. I'd like to thank her for her patience and contributions to make Titan a success + + + +###### Help us out: Make a Titan muslin + +A block is just that, a block or sloper. Our next steps are obviously this spin this into a number of different trouser patterns. Before we get to that though, we'd like to see how Titan performs on a variety of bodies. + +So if you could whip up a muslin of a made-to-measure Titan and let us know how it went, that would be wonderful. + + + +## Shoulder slope — again — and other changes to measurements + +We've made changes to the different measurements on the site. The roughly fall into 3 categories: + + - We've made *waist* the basis for vertical measurements + - We've changed the shoulder slope measurement + - We've simplified the language and terms + +As a result, some vertical measurements that were not based on the waist are not gone (hips to upper leg for example). Other measurements have been renamed under the hood to make things simpler, but unless you're a developer, you don't need to worry about that. + +An important change is the one we made to the shoulder slope measurement. It's historically been a measurement that is hard to measure, and the changes we've made before to try to address that were in retrospect a bad idea. + +We've changed it again, but this time around, shoulder slope is measured as you would expect a slope to be measured: in degrees. + +This required some changes as up until now all measurements used the same units, but things should be ok now. + +As a result of all these changes and measurements, there's two things you should know: + + - The people you have in your account will have their measurements updated (when the names changed) or removed (where the measurement is no longer used, or we changed how to measure it) + - Patterns that you have saved in your account that use some of the changed measurements will no longer work. However, we've kept them in your account so that if you want, you can extract the data, and re-draft them for the new measurements. Feel free to reach out if you need assistance with that. + + + +We've migrated our backend to these new measurements, but you are likely to still have some of the old stuff cached in your profile. +To get around this, you should probably [reload your account](/account/reload/). + + + +## Frontend changes + +We've made a few changes to the website too. + + - We've added a [pattern notation guide](/docs/various/notation/) to take the guesswork out of what those markings on your pattern mean. + - We've added a [reload account](/account/actions/reload/) page to help you avoid issues due to cached account data + - We've changed the styling of the different sizes when you compare a pattern, as well as included a legend showing which outline corresponds to which size. + + +## And many more changes under the hood + +As I said, a lot of work went into this release. See our [monorepo changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md) for all the details. + diff --git a/markdown/org/blog/freesewing-v2-7/es.md b/markdown/org/blog/freesewing-v2-7/es.md new file mode 100644 index 00000000000..6ebea838e1f --- /dev/null +++ b/markdown/org/blog/freesewing-v2-7/es.md @@ -0,0 +1,75 @@ +--- +author: "joostdecock" +caption: "Photo by Deeana Creates from Pexels" +date: "2020-07-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f04cc6c50a8e5f08f3ebd6c3d4903fb3055c9a01-1920x1280.jpg" +intro: "We've just release FreeSewing v2.7 🎉" +title: "FreeSewing v2.7: Titan, changes to measurements, and a long list of improvements [No traducido]" +--- + + +We've just release FreeSewing v2.7 🎉 + +There's a lot of work that went into this release, and unfortunately it also will cause some breaking changes to your existing patterns and people, but it's all for the better. + +Let's have a look at what's new: + +## Titan trouser block + +I have lost count of the number of times I have started working on a trouser block over the last couple of years. It's something that's been on my to-do list for a long time, yet despite several attempts at making it happen, I hadn't come up with something that I was happy with. + +That's because designing trouser patterns is hard. Making sure things fit, while also guaranteeing that inseam, outseam, and cross seam are all the same length is no walk in the park. Especially if you want a pattern that will seamlessly adapt to different sizes and models. + +It would have probably lingered on my to-do list a while longer, but in February, Debra reached out to me and proposed we would come up with a pants sloper together. I love teaming up with people because it a great way to stay motivated, so over the next 4 months or so, we worked on what Debra has named [Titan](/designs/titan/), a dart-free unisex trouser block. I'd like to thank her for her patience and contributions to make Titan a success + + + +###### Help us out: Make a Titan muslin + +A block is just that, a block or sloper. Our next steps are obviously this spin this into a number of different trouser patterns. Before we get to that though, we'd like to see how Titan performs on a variety of bodies. + +So if you could whip up a muslin of a made-to-measure Titan and let us know how it went, that would be wonderful. + + + +## Shoulder slope — again — and other changes to measurements + +We've made changes to the different measurements on the site. The roughly fall into 3 categories: + + - We've made *waist* the basis for vertical measurements + - We've changed the shoulder slope measurement + - We've simplified the language and terms + +As a result, some vertical measurements that were not based on the waist are not gone (hips to upper leg for example). Other measurements have been renamed under the hood to make things simpler, but unless you're a developer, you don't need to worry about that. + +An important change is the one we made to the shoulder slope measurement. It's historically been a measurement that is hard to measure, and the changes we've made before to try to address that were in retrospect a bad idea. + +We've changed it again, but this time around, shoulder slope is measured as you would expect a slope to be measured: in degrees. + +This required some changes as up until now all measurements used the same units, but things should be ok now. + +As a result of all these changes and measurements, there's two things you should know: + + - The people you have in your account will have their measurements updated (when the names changed) or removed (where the measurement is no longer used, or we changed how to measure it) + - Patterns that you have saved in your account that use some of the changed measurements will no longer work. However, we've kept them in your account so that if you want, you can extract the data, and re-draft them for the new measurements. Feel free to reach out if you need assistance with that. + + + +We've migrated our backend to these new measurements, but you are likely to still have some of the old stuff cached in your profile. +To get around this, you should probably [reload your account](/account/reload/). + + + +## Frontend changes + +We've made a few changes to the website too. + + - We've added a [pattern notation guide](/docs/various/notation/) to take the guesswork out of what those markings on your pattern mean. + - We've added a [reload account](/account/actions/reload/) page to help you avoid issues due to cached account data + - We've changed the styling of the different sizes when you compare a pattern, as well as included a legend showing which outline corresponds to which size. + + +## And many more changes under the hood + +As I said, a lot of work went into this release. See our [monorepo changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md) for all the details. + diff --git a/markdown/org/blog/freesewing-v2-7/fr.md b/markdown/org/blog/freesewing-v2-7/fr.md new file mode 100644 index 00000000000..7a59fc0044a --- /dev/null +++ b/markdown/org/blog/freesewing-v2-7/fr.md @@ -0,0 +1,76 @@ +--- +author: "joostdecock" +caption: "Photo par Deeana crée à partir de Pexels" +date: "2020-07-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f04cc6c50a8e5f08f3ebd6c3d4903fb3055c9a01-1920x1280.jpg" +intro: "Nous venons de publier FreeSewing v2.7 🎉" +title: "FreeSewing v2.7 : Titan, modifications des mesures et une longue liste d'améliorations" +--- + + +Nous venons de publier FreeSewing v2.7 🎉 + +Il y a beaucoup de travail dans cette version, et, malheureusement, cela causera aussi quelques erreurs à vos modèles et à vos personnes existantes, mais c'est pour la bonne cause. + +Regardons ce qui est nouveau : + +## Bloc de pantalon Titan + +J'ai perdu le nombre de fois où j'ai commencé à travailler sur un pantalon au cours des dernières années. C'est quelque chose qui est resté sur ma liste de tâches pendant longtemps, mais malgré plusieurs tentatives de m'y mettre, je n'avais pas réussi à parvenir à quelque chose dont j'étais satisfait. + +C'est parce que la conception de patrons de pantalon est difficile. S'assurer que tout tombe bien, tout en garantissant également que les coutures d'intérieur, d'extérieur et la couture de fourche soient toutes les mêmes longueurs n'est pas une mince affaire. Surtout si vous voulez un patron qui s'adapte parfaitement aux différentes tailles et modèles. + +Il serait probablement resté sur ma liste de tâches un peu plus longtemps, mais en février, Debra m'a tendu la main et nous avons réussi à sortir un pantalon ensemble. J'aime faire équipe avec des gens parce que c'est un excellent moyen de rester motivé, donc au cours des 4 prochains mois ou plus, nous avons travaillé sur ce que Debra a nommé [Titan](/designs/titan/), un bloc de pantalon unisexe sans pinces. Je tiens à la remercier pour sa patience et ses contributions à faire de Titan un succès + + + +###### Aidez-nous : Fabriquer une toile de Titan + +Un bloc est juste cela, un bloc ou un patron de base. Nos prochaines étapes sont évidemment de l'utiliser pour servir de base pour un certain nombre de patron de pantalon différents. Avant d'y arriver, nous aimerions voir comment Titan s'adapte sur une variété de corps. + +Donc, si vous pouviez réaliser une toile d'un Titan sur mesure et nous faire savoir comment il tombe, ce serait merveilleux. + + + +## La pente de l'épaule — encore — et d'autres modifications aux mensurations + +Nous avons modifié les différentes mesures du site. Cela se présente en 3 principales catégories : + + - Nous avons fait de la *taille * la base des mesures verticales + - Nous avons changé la mesure de la pente des épaules + - Nous avons simplifié la langue et les termes + +En conséquence, certaines mesures verticales qui n'étaient pas basées sur la taille ne sont pas parties (les hanches au haut de la jambe par exemple). D'autres mesures ont été renommées pour simplifier les choses, mais à moins que vous ne soyez un développeur, vous n'avez pas à vous en soucier. + +Un changement important est celui que nous avons fait pour la mesure de la pente des épaules. C'est historiquement une mesure difficile à mesurer, et les changements que nous avons faits précédemment pour essayer de résoudre ce problème étaient rétrospectivement une mauvaise idée. + +Nous l'avons à nouveau changé, mais cette fois-ci, la pente des épaules est mesurée comme on s'attendrait à ce qu'une pente soit mesurée : en degrés. + +Cela nécessitait quelques changements car jusqu'à présent, toutes les mesures utilisaient les mêmes unités, mais les choses devraient être ok maintenant. + +À la suite de toutes ces modifications et mesures, il y a deux choses que vous devez savoir : + + - Les personnes que vous avez dans votre compte verront leurs mesures mises à jour (lorsque juste les noms ont changé) ou supprimées (lorsque la mesure n'est plus utilisée, ou nous avons changé la façon de le mesurer) + - Les patrons que vous avez enregistrés dans votre compte qui utilisent certaines des mesures modifiées ne fonctionneront plus. Cependant, nous les avons conservées dans votre compte afin que, si vous le souhaitez, vous puissiez extraire les données et les retracer avec les nouvelles mesures. N'hésitez pas à nous contacter si vous avez besoin d'aide pour cela. + + + +Nous avons migré notre code (backend) vers ces nouvelles mesures, mais il est probable que vous ayez encore en cache certaines choses anciennes dans votre profil. +Pour contourner ce problème, vous devriez probablement [recharger votre compte](/account/reload/). + + + +## Changements du frontend + +Nous avons également apporté quelques modifications au site Web. + + - Nous avons ajouté un [guide de notation des patrons](/docs/various/notation/) pour aider à la compréhension de la signification de ces marquages sur votre patron. + - Nous avons ajouté une page [recharger le compte](/account/actions/reload/) pour vous aider à éviter des problèmes liés aux données du compte mises en cache + - Nous avons changé le style des différentes tailles lorsque vous comparez un patron, et nous avons aussi inclus une légende montrant quel trait correspond à quelle taille. + + +## Et bien d'autres changements sous le capot + +Comme je l'ai dit, beaucoup de travail a été effectué dans cette version. Consultez notre [journal des modifications Monorepo](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md) pour tous les détails. + + diff --git a/markdown/org/blog/freesewing-v2-7/nl.md b/markdown/org/blog/freesewing-v2-7/nl.md new file mode 100644 index 00000000000..c6f9abade06 --- /dev/null +++ b/markdown/org/blog/freesewing-v2-7/nl.md @@ -0,0 +1,75 @@ +--- +author: "joostdecock" +caption: "Photo by Deeana Creates from Pexels" +date: "2020-07-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f04cc6c50a8e5f08f3ebd6c3d4903fb3055c9a01-1920x1280.jpg" +intro: "We've just release FreeSewing v2.7 🎉" +title: "FreeSewing v2.7: Titan, changes to measurements, and a long list of improvements [Niet vertaald]" +--- + + +We've just release FreeSewing v2.7 🎉 + +There's a lot of work that went into this release, and unfortunately it also will cause some breaking changes to your existing patterns and people, but it's all for the better. + +Let's have a look at what's new: + +## Titan trouser block + +I have lost count of the number of times I have started working on a trouser block over the last couple of years. It's something that's been on my to-do list for a long time, yet despite several attempts at making it happen, I hadn't come up with something that I was happy with. + +That's because designing trouser patterns is hard. Making sure things fit, while also guaranteeing that inseam, outseam, and cross seam are all the same length is no walk in the park. Especially if you want a pattern that will seamlessly adapt to different sizes and models. + +It would have probably lingered on my to-do list a while longer, but in February, Debra reached out to me and proposed we would come up with a pants sloper together. I love teaming up with people because it a great way to stay motivated, so over the next 4 months or so, we worked on what Debra has named [Titan](/designs/titan/), a dart-free unisex trouser block. I'd like to thank her for her patience and contributions to make Titan a success + + + +###### Help us out: Make a Titan muslin + +A block is just that, a block or sloper. Our next steps are obviously this spin this into a number of different trouser patterns. Before we get to that though, we'd like to see how Titan performs on a variety of bodies. + +So if you could whip up a muslin of a made-to-measure Titan and let us know how it went, that would be wonderful. + + + +## Shoulder slope — again — and other changes to measurements + +We've made changes to the different measurements on the site. The roughly fall into 3 categories: + + - We've made *waist* the basis for vertical measurements + - We've changed the shoulder slope measurement + - We've simplified the language and terms + +As a result, some vertical measurements that were not based on the waist are not gone (hips to upper leg for example). Other measurements have been renamed under the hood to make things simpler, but unless you're a developer, you don't need to worry about that. + +An important change is the one we made to the shoulder slope measurement. It's historically been a measurement that is hard to measure, and the changes we've made before to try to address that were in retrospect a bad idea. + +We've changed it again, but this time around, shoulder slope is measured as you would expect a slope to be measured: in degrees. + +This required some changes as up until now all measurements used the same units, but things should be ok now. + +As a result of all these changes and measurements, there's two things you should know: + + - The people you have in your account will have their measurements updated (when the names changed) or removed (where the measurement is no longer used, or we changed how to measure it) + - Patterns that you have saved in your account that use some of the changed measurements will no longer work. However, we've kept them in your account so that if you want, you can extract the data, and re-draft them for the new measurements. Feel free to reach out if you need assistance with that. + + + +We've migrated our backend to these new measurements, but you are likely to still have some of the old stuff cached in your profile. +To get around this, you should probably [reload your account](/account/reload/). + + + +## Frontend changes + +We've made a few changes to the website too. + + - We've added a [pattern notation guide](/docs/various/notation/) to take the guesswork out of what those markings on your pattern mean. + - We've added a [reload account](/account/actions/reload/) page to help you avoid issues due to cached account data + - We've changed the styling of the different sizes when you compare a pattern, as well as included a legend showing which outline corresponds to which size. + + +## And many more changes under the hood + +As I said, a lot of work went into this release. See our [monorepo changelog](https://github.com/freesewing/freesewing/blob/develop/CHANGELOG.md) for all the details. + diff --git a/markdown/org/blog/gdpr-plan/de.md b/markdown/org/blog/gdpr-plan/de.md new file mode 100644 index 00000000000..e9dde4b202b --- /dev/null +++ b/markdown/org/blog/gdpr-plan/de.md @@ -0,0 +1,320 @@ +--- +author: "joostdecock" +caption: "Dieses Bild ist wahrscheinlich das Einzige in der Post, was Sie diagonal überfliegen können" +date: "2018-02-14" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/39f3d1e7320510b2dd12cc1bc2e58008263889f3-1920x1280.webp" +intro: "Dieser Blogpost handelt von der Datenschutzgrundverordnung (DSGVO) der Europäischen Union (EU). Während ich auf die Grundlagen der DSGVO eingehe, konzentriert sich der Schwerpunkt auf deren Auswirkungen auf FreeSewing.org, und was wir in den 100 Tagen tun wollen, die bleiben, bevor die DSGVO in Kraft tritt." +title: "Die Datenschutzgrundverordnung der Europäischen Union: Unser Schlachtplan." +--- + + +Dieser Blogpost handelt von der Datenschutzgrundverordnung (DSGVO) der Europäischen Union (EU). Während ich auf die Grundlagen der DSGVO eingehe, konzentriert sich der Schwerpunkt auf deren Auswirkungen auf FreeSewing.org, und was wir in den 100 Tagen tun wollen, die bleiben, bevor die DSGVO in Kraft tritt. + +Dies ist eine etwas lange Lektüre, deshalb hier ein Inhaltsverzeichnis: + +## Gedanken zur DSGVO der EU + +Ich habe eine Hassliebe mit der Europäischen Union. Ich liebe, was sie tun und wofür sie stehen, ich hasse, wie sie es tun. + +![Ich verstehe diesen Typen total](rage-quit.gif) + +Mit der DSGVO ist es nicht anders. Es handelt sich um einen wichtiges Stück Gesetzgebung, das die Messlatte für den Online-Datenschutz höher legt, was großartig ist. Aber als ich über das Thema las, verspürte ich den Drang, aus Wut aufzuhören, diese ewigen Bürokraten. + +Erlauben Sie mir, das zu erklären. + +### Privatsphäre braucht Schutz +Auf Gedeih und Verderb (ich glaube eher auf Verderben) hat sich das Internet in einen Modus Operandi eingependelt wobei Sie *freie Sachen* mit Ihren persönlichen Daten bezahlen. Einige Leute nennen es [People-Farming](https://ar.al/notes/we-didnt-lose-control-it-was-stolen/), und ich denke, das ist ein toller Begriff. + +Die [furchterregenden Fünf](https://www.nytimes.com/2017/05/10/technology/techs-frightful-five-theyve-got-us.html) saugen immer mehr unseres persönlichen Lebens ab. Abgesehen davon, dass wir nie online gehen werden, können wir anscheinend nur sehr wenig dagegen tun. + +### Warum die EU die beste ist +Dieses Problem ist zu groß, um von einem von uns alleine angegangen zu werden. Wer könnte der geballten Macht der Technologieriesen die Stirn bieten? + +Nun, wie ist das für einen Lebenslauf: + + - Habe Facebook zu 110 Millionen Euro Strafe wegen irreführender Aussagen über den Kauf von WhatsApp verurteilt + - Befahl Amazon die Nachzahlung von 250 Millionen Euro zusätzlicher Steuern in Luxemburg + - Verhängte gegen Google eine Geldbuße in Höhe von 2,4 Milliarden Euro wegen Missbrauchs seiner dominanten Position bei der Suche + - Habe Apple zur Zahlung von 13 Milliarden Euro zusätzlicher Steuern in Irland verurteilt + +![Wir sind die EU, Bitch](titanfall.gif) + +Wenn es um die Giganten der Technik geht, ist die Europäische Union nur eine Peitsche, kein Zuckerbrot. + +Die Datenschutzgrundverordnung setzt Datenschutzrichtlinien durch, die die Rechte der Nutzer respektieren. Sie gilt für alle EU-Bürger, jederzeit und überall. + +Es spielt keine Rolle, ob Sie ein "Silicon Valley Juggernaut" sind, die Rechte der EU-Bürger respektieren oder sich dem Zorn der Eurokratie stellen: + +> Organisationen, die gegen GDPR verstoßen, können mit einer Geldstrafe von bis zu 4% des weltweiten Jahresumsatzes oder 20 Millionen Euro (je nachdem, welcher Betrag höher ist) belegt werden + +Vier Prozent des weltweiten Umsatzes ist *eine sehr lange Peitsche*. + +### Warum die EU die schlechteste ist + +![So stelle ich mir eine Artikel-29-Datenschutzgruppe vor](complicated.gif) + +Da die EU die EU ist, ist die Verordnung ein Mischmasch aus hochgesteckten Zielen und Idealen, die durch Lobbygruppen verwässert und durch den Kompromiss, der erforderlich ist, um 28 Mitgliedstaaten ins Boot zu holen, noch komplizierter wird. + +Die Absichten sind großartig, es ist eine großartige Idee, aber sie machen einen schrecklichen Job, sie zu vermarkten --- wie immer. + +Die praktische Umsetzung liegt in den Händen der so genannten *Artikel-29-Arbeitsgruppe* die sich derzeit mit der Gestaltung von Symbolen beschäftigt (das kann man sich [nicht ausdenken](https://www.google.be/search?q=standardised+icons+gdpr)) Sie wird ihren Namen in *Europäischen Datenschutzrat* am 25. Mai ändern weil Sie mit diesem ganzen Jargon jetzt nicht zu zufrieden sein werden, oder? + +## Die DSGVO in der praktischen Umsetzung + +Wenn Sie Expertenrat zur DSGVO-Konformität suchen, ist dies nicht der richtige Ort für Sie. + + +Aber wenn Sie neugierig sind auf die DSGVO und was es für eine Website wie FreeSewing.org braucht um der Verordnung gerecht zu werden, lesen Sie weiter. + +> ##### Weiterführende Literatur +> +> Wenn Sie wirklich wissen wollen, was DSGVO ist, ist das Beste, was Sie tun können [Lesen Sie das verdammte Ding einfach durch](http://eur-lex.europa.eu/legal-content/en/TXT/?uri=CELEX%3A32016R0679). Es ist keine Raketenwissenschaft. +> +> Wenn Gesetzestexte Sie dazu bringen, die Wände hoch zu gehen, hat die ICO des Vereinigten Königreichs [einfach einer der besten Leitfäden zu DSGVO](https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/). + +### Gut zu wissen + +A few things you should know before we dive into GDPR: + +#### There's 100 days left + +The GDPR was adopted back in 2016, but it won't grow its teeth until May 25th 2018. + +Until that day, you get a pass. After that day, it's for real. Which means we have 100 days left to get our house in order. + +#### There's exemptions for SMEs + +Organizations employing fewer than 250 people are exempt from some of the more bureaucratic aspects of the GDPR, such as a bunch of documenting requirements. + +Essentially, while you still have to do the right thing, there's a lot less paperwork to fill out. + +Freesewing employs zero people, so we're off the hook. + +#### There's extra provisions for sensitive data + +> Body measurements alone are not sensitive data + +The GDPR has extra provisions for *sensitive data* such as biometric data, profiling, and a bunch of other stuff. + +This was cause for concern because we collect body measurements, and one of our questions was whether that qualifies as biometric data. + +Turns out it doesn't. Biometric data is what you can use to identify a person, like a fingerprint or iris scan. Body measurements alone are not sensitive data. + + +### Collecting data through consent + +To collect data, you need a so-called *lawful basis for data processing*. There are different types, but the one that applies to us (and to most online services) is **consent**. + +In this scenario, your legal basis for processing the data is that you've asked the person to get their data and they've freely given it to you. + +That is straight-forward, and makes sense. But the GDPR is really serious about making sure this consent is freely given, and not wrestled from you grudgingly. + +To prevent companies from throwing up a big wall of legalese that people have to agree to, the GDPR outlines a number of principles this consent should adhere to. Here's a non-exhaustive list: + + - people should have real choice and control + - consent requires a positive opt-in, pre-ticked boxes or anything like that are not allowed + - there should be a very clear statement explaining what people are agreeing to + - these requests for consent must be separate from any terms & conditions + - consent needs to be granular, you need individual consent for different things, and can't ask for blanket consent + - it must be easy for people to redraw consent + - consent of data processing should not be a precondition for a service + +Looking at that list, I can't help but feel that legislation would be a lot simpler if lawmakers could just write *don't be a dick* and call it a day. + +#### Consent granularity + +Remember, we can't just get blanket consent. We need to get consent for every type of data processing we do. + +For freesewing.org, we have identified three different types of data processing: + + - Profile data + - Model data + - Patron data + +For each of these, we'll need to get consent from the user, making sure it's *real consent* as intended in the GDPR. + +Below is a mockup for what this could look like for each data type: + +> ##### These mockups are no longer available +> +> Please note that the mockups originally included in this post are no longer available. Instead, this functionality has been implemented in the website. + +#### Consent timing + +The GDPR states that you should ask for consent when the data is collected. + +With our three types of data processing, that means that consent must be asked at different times: + + - **Profile data**: When signing up on the site + - **Model data**: When creating the first model + - **Patron data**: When becoming a patron + +This will (also) require some extra work to integrate this in the site. + +### Respecting basic rights when processing data + +The EU enshrines basic rights for its citizens that should be respected when processing data. + +Let's look at each of these rights and their impact on freesewing.org. + +#### The right to be informed + +> You need to be transparent about how you use personal data. Why you collect it, how you use it, and so on. + +Informing users is something we are still working on. If anything, this blog post is part of that effort. + +We will need to design the individual privacy notices, but also a more overall privacy policy as well as making certain that users are informed of all their rights. + +While this will require some work, I don't expect any problems here. + +#### The right of access + +> People have the right to know their data is processed, and to access that data. + +We are already compliant, as all data users enter on the site can also be accessed by them. + +#### The right to rectification + +> People have the right to correct their data if it's not correct. + +We are already compliant, as all data users enter on the site can also be edited by them. + +#### The right to erasure + +> People have the right to have their data removed/erased. + +We are already compliant, as users can remove their models, or entire account at any time. + +#### The right to restrict processing + +This right means that users must be able to put a *freeze* on all data processing, without going as far as to delete their data. + +We do not currently offer this possibility, and will need to add this functionality to the site. + +#### The right to data portability + +> People not only have a right to export all their data, that export should also be in a format that makes it easy for them to take their data elsewhere. + +We are already compliant, as we allow users to export all of their data, and make it available in different standard formats (YAML and JSON). + +#### The right to object + +> The right to object applies specifically to: +> +> - processing for public interests or by official authorities +> - processing for direct marketing +> - processing for science/historic research/statistics +> +> In these cases, people can object to this specific processing. + +This is going to apply to us when we start publishing anonymized model data, something that's on our roadmap. + +The reason for publishing this data is that we want to make a dataset available of *real* body measurements, rather than the *standard* measurements that are typically used in the industry. + +This is something we'll write about more at a later date, but essentially this falls under the *scientific research/statistics* category. And even though the data is anonimized, we still need to respect the right of users to object to this processing. + +As such, we should add the possibility to object to this specific use of the data. + +#### Rights in relation to automated decision making and profiling + +> People have extra rights when it comes to profiling or decisions made by AI or algorithms without human involvement. + +This is not relevant in our situation. + +### Privacy by design + +The EU isn't content with throwing up a couple of consent questions and respecting people's rights when processing data. It also wants to make certain that your privacy is (better) protected when things go wrong. + +That's why it advocates for *privacy by design*. While it's a concept that's hard to pin down in legislation, the purpose is clear: They want everyone to consider privacy from the very start of their project/product/business, and not as an afterthought. + +Things such as encryption (both in transit and for data at-rest), pseudonyms, and data expiry are suggested as things to keep in mind while designing. + +Obviously, the EU is not going to come check your code to see whether you've taken privacy by design to heart. But it can (and probably will) have an influence when things to wrong. + +Imagine two companies who have a data leak, one of them hasn't done much to safeguard the privacy of their users, whereas the other has taken *privacy by design* measures to mitigate the damage. + +It seems obvious that the EU is going to come down harder on the company who didn't even try. + +#### What we're already doing + +We already do a number of things that are driven by a *privacy by design* approach. For example: + + - We use pseudonyms for user accounts + - We don't share any data with any third party + - We don't include any tracking code, or analytics + - We don't use cookies + - We don't have any social logins, like buttons, or other such things + - We don't run/show any ads + - We don't run any third-party JavaScript code + - We use encryption on all transport + +There's some more info on this in this blog post: [The choices I've made to protect your privacy. Or why you won't be getting any cookies](/blog/privacy-choices/). + +These already form a very good basis for a privacy conscious website. But since we'll need to make changes for GDPR anyway, we're considering other options to further raise the privacy bar. Specifically, what can we do to limit the damage to our users in case there is a data leak. + +#### Restriction of data storage + +Some of the most sensitive data we store today is the address and birthday of our higher-tier patrons. + +However, the site does not need this information to function. We only need it for administrative purposes; Sending out gifts and birthday cards to our patrons. + +As such, there's no real need to keep this data in the freesewing database. We could just as well write this information down in a notebook we keep on our coffee table. + +So, as part of our GDPR-related changes, we will remove this information from the database, and store it offline. + +#### Encryption of data at rest + +We already encrypt all data in transit. But, we are currently considering to add encryption of data at rest. + +The idea is to encrypt all data that could potentially identify a user. Such as: + + - Email address + - User name + - Model names + - Model notes + +This would add an extra layer of defense for our users' privacy in case somehow our database gets dumped. + +While this change will be non-trivial to implement and come with a performance penalty, I feel it's worth looking in to. + +## Fazit + +While we still have some work to do, we are already compliant with large parts of the GDPR, especially when it comes to respecting users rights: + + - The right to be informed + - The right of access + - The right to rectification + - The right to erasure + - The right to restrict processing + - The right to data portability + - The right to object + - Rights in relation to automated decision making and profiling + +We are currently working on *the right to be informed* and have a plan for the changes required to respect *the right to restrict processing* and *the right to object*. + +On the data collection site, we need to hammer out the details for our privacy notices. We'll also write a detailed privacy policy that bundles all the info from the different notices. + +We'll need to add changes to the user on-boarding to make sure notices are presented at the correct time. Not to mention that we'll need to keep track of who gave their consent for what. + +### Action points + + - Draft privacy notices for profile/model/patron data + - Integrate consent in user on-boarding, model creation, and patron sign-up + - Make site functionality depend on consent + - Provide a centralized privacy dashboard where people can review their privacy settings/consent + - Add email notifications every time consent is changed + - Provide a way for people to *freeze* their account + - Provide a way for people to object to their model data being used for research and statistics + - Write and publish an overall privacy policy + - Encrypt sensitive data in the database + +Seems like we've got a lot of work ahead of us. + +### Feedback + +It is my personal opinion that the GDPR is a good thing. But I want to hear from you about the changes outlined in this blog post. + +So please reach out with your feedback and comments. It is after all your data we're talking about. + + + diff --git a/markdown/org/blog/gdpr-plan/en.md b/markdown/org/blog/gdpr-plan/en.md new file mode 100644 index 00000000000..1f0e9a467c2 --- /dev/null +++ b/markdown/org/blog/gdpr-plan/en.md @@ -0,0 +1,367 @@ +--- +author: "joostdecock" +caption: "This image is probably the only thing in the post you can skim diagonally" +date: "2018-02-14" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/39f3d1e7320510b2dd12cc1bc2e58008263889f3-1920x1280.webp" +intro: "The General Data Protection Regulation of the European Union: Our battle plan." +title: "The General Data Protection Regulation of the European Union: Our battle plan." +--- + +This blog post is about the General Data Protection Regulation (GDPR) of the European Union (EU). +While I cover the basics of GDPR, the main focus is on how it impacts freesewing.org, and what we plan to do to in the 100 days that remain +before GDPR goes into force. + +This is a bit of a long read, so here's a table of contents: + +## Thoughts on the EU's GDPR + +I have a love/hate relationship with the European Union. +I love what they do and what they stand for, I hate how they do it. + +![I totally get this dude](https://posts.freesewing.org/uploads/rage_quit_fff821e695.gif) + +The GDPR is no different. +It's an important piece of legislation that raises the bar for online privacy, which is great. +But as I was reading up on the subject, I felt the urge to rage-quit because OMG bureaucrats. + +Allow me to explain. + +### Privacy needs protection +For better or for worse (I believe for worse) the internet has settled into a modus operandi +where you pay for *free stuff* with your personal data. +Some people call it [people farming](https://ar.al/notes/we-didnt-lose-control-it-was-stolen/), and I think that's a great term. + +The [frightful five](https://www.nytimes.com/2017/05/10/technology/techs-frightful-five-theyve-got-us.html) +are vacuuming up ever more of our personal lives. +Short of never going online, there seems to be precious little we can do about it. + +### Why the EU is the best +This problem is too big to tackle by any of us. +Who could possibly stand up to the combined power of the tech giants? + +Well, how's this for a CV: + + - Fined Facebook 110 million euro for misleading statements about their WhatsApp purchase + - Ordered Amazon to pay 250 million euro extra taxes in Luxembourg + - Fined Google 2.4 billion euro for abusing its dominant position in search + - Ordered Apple to pay 13 billion euro extra taxes in Ireland + +![We're the EU, bitch](titanfall.gif) + +When it comes to tech giants, the European Union is all stick/ no carrot. + +The General Data Protection Regulation enforces privacy policies that respect users' rights. +It applies to all EU citizens, all the time, everywhere. + +Doesn't matter if you're a silicon valley juggernaut, respect the rights of the EU citizens or face the wrath of the eurocracy: + +> Organizations in breach of GDPR can be fined up to 4% of annual global turnover or 20 million euro (whichever is greater) + +Four percent of global turnover is *a very big stick*. + +### Why the EU is the worst + +![What I imagine a Article 29 Working Party looks like](complicated.gif) + +The EU being the EU, the regulation is a mixed bag of lofty goals and ideals, watered down by lobbying groups, and further complicated by the compromise required to get 28 member states on board. + +The intentions are great, it's a great idea, but they are doing a terrible job at selling it --- as usual. + +The practical implementation is in the hands of the so-called *Article 29 Working Party* +which is currently keeping busy designing icons +(I am [not making this up](https://www.google.be/search?q=standardised+icons+gdpr)) +It will change its name to the +*European Data Protection Board* come May 25th, because you wouldn't want to get too comfortable with all this jargon now, would you? + +## The GDPR in practice + +If you're looking for expert advice on GDPR compliance, this is not the place for you. + + +But if you are curious about the GDPR and what it takes for a website like freesewing.org +to be compliant, read on. + +> ##### Further reading +> If you really want to know what GDPR is, the best thing you can do is +> [read the damn thing](http://eur-lex.europa.eu/legal-content/en/TXT/?uri=CELEX%3A32016R0679). It ain't no rocket science. +> +> If legislative texts make you run for the hills, the UKs ICO has +> [easily one of the best guides on GDPR](https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/). + +### Good to know + +A few things you should know before we dive into GDPR: + +#### There's 100 days left + +The GDPR was adopted back in 2016, but it won't grow its teeth until May 25th 2018. + +Until that day, you get a pass. After that day, it's for real. +Which means we have 100 days left to get our house in order. + +#### There's exemptions for SMEs + +Organizations employing fewer than 250 people are exempt from some of the more bureaucratic aspects of the GDPR, such as a bunch of documenting requirements. + +Essentially, while you still have to do the right thing, there's a lot less paperwork to fill out. + +Freesewing employs zero people, so we're off the hook. + +#### There's extra provisions for sensitive data + +> Body measurements alone are not sensitive data + +The GDPR has extra provisions for *sensitive data* +such as biometric data, profiling, and a bunch of other stuff. + +This was cause for concern because we collect body measurements, and one of our questions was whether that qualifies as biometric data. + +Turns out it doesn't. Biometric data is what you can use to identify a person, like a fingerprint or iris scan. Body measurements alone are not sensitive data. + + +### Collecting data through consent + +To collect data, you need a so-called *lawful basis for data processing*. +There are different types, but the one that applies to us (and to most online services) is **consent**. + +In this scenario, your legal basis for processing the data is that you've asked the person to get their data +and they've freely given it to you. + +That is straight-forward, and makes sense. But the GDPR is really serious about making sure this consent is +freely given, and not wrestled from you grudgingly. + +To prevent companies from throwing up a big wall of legalese that people have to agree to, the GDPR outlines a number +of principles this consent should adhere to. Here's a non-exhaustive list: + + - people should have real choice and control + - consent requires a positive opt-in, pre-ticked boxes or anything like that are not allowed + - there should be a very clear statement explaining what people are agreeing to + - these requests for consent must be separate from any terms & conditions + - consent needs to be granular, you need individual consent for different things, and can't ask for blanket consent + - it must be easy for people to redraw consent + - consent of data processing should not be a precondition for a service + +Looking at that list, I can't help but feel that legislation would be a lot simpler if lawmakers could just write +*don't be a dick* and call it a day. + +#### Consent granularity + +Remember, we can't just get blanket consent. +We need to get consent for every type of data processing we do. + +For freesewing.org, we have identified three different types of data processing: + + - Profile data + - Model data + - Patron data + +For each of these, we'll need to get consent from the user, making sure it's *real consent* as intended in the GDPR. + +Below is a mockup for what this could look like for each data type: + +> ##### These mockups are no longer available +> +> Please note that the mockups originally included in this post are no longer +> available. Instead, this functionality has been implemented in the website. + +#### Consent timing + +The GDPR states that you should ask for consent when the data is collected. + +With our three types of data processing, that means that consent must be asked at different times: + + - **Profile data**: When signing up on the site + - **Model data**: When creating the first model + - **Patron data**: When becoming a patron + +This will (also) require some extra work to integrate this in the site. + +### Respecting basic rights when processing data + +The EU enshrines basic rights for its citizens that should be respected when processing data. + +Let's look at each of these rights and their impact on freesewing.org. + +#### The right to be informed + +> You need to be transparent about how you use personal data. Why you collect it, how you use it, and so on. + +Informing users is something we are still working on. If anything, this blog post is part of that effort. + +We will need to design the individual privacy notices, but also a more overall privacy policy as well as +making certain that users are informed of all their rights. + +While this will require some work, I don't expect any problems here. + +#### The right of access + +> People have the right to know their data is processed, and to access that data. + +We are already compliant, as all data users enter on the site can also be accessed by them. + +#### The right to rectification + +> People have the right to correct their data if it's not correct. + +We are already compliant, as all data users enter on the site can also be edited by them. + +#### The right to erasure + +> People have the right to have their data removed/erased. + +We are already compliant, as users can remove their models, or entire account at any time. + +#### The right to restrict processing + +This right means that users must be able to put a *freeze* on all data processing, without going as far as to delete their data. + +We do not currently offer this possibility, and will need to add this functionality to the site. + +#### The right to data portability + +> People not only have a right to export all their data, that export should also be in a format that makes it easy for them to take their data elsewhere. + +We are already compliant, as we allow users to export all of their data, and make it available in different standard formats (YAML and JSON). + +#### The right to object + +> The right to object applies specifically to: +> +> - processing for public interests or by official authorities +> - processing for direct marketing +> - processing for science/historic research/statistics +> +> In these cases, people can object to this specific processing. + +This is going to apply to us when we start publishing anonymized model data, something that's on our roadmap. + +The reason for publishing this data is that we want to make a dataset available of *real* body measurements, rather than the +*standard* measurements that are typically used in the industry. + +This is something we'll write about more at a later date, but essentially this falls under the *scientific research/statistics* category. +And even though the data is anonimized, we still need to respect the right of users to object to this processing. + +As such, we should add the possibility to object to this specific use of the data. + +#### Rights in relation to automated decision making and profiling + +> People have extra rights when it comes to profiling or decisions made by AI or algorithms without human involvement. + +This is not relevant in our situation. + +### Privacy by design + +The EU isn't content with throwing up a couple of consent questions and respecting people's rights when processing data. +It also wants to make certain that your privacy is (better) protected when things go wrong. + +That's why it advocates for *privacy by design*. While it's a concept that's hard to pin down in legislation, the +purpose is clear: They want everyone to consider privacy from the very start of their project/product/business, and +not as an afterthought. + +Things such as encryption (both in transit and for data at-rest), pseudonyms, and data expiry are suggested as +things to keep in mind while designing. + +Obviously, the EU is not going to come check your code to see whether you've taken privacy by design to heart. +But it can (and probably will) have an influence when things to wrong. + +Imagine two companies who have a data leak, one of them hasn't done much to safeguard the privacy of their users, +whereas the other has taken *privacy by design* measures to mitigate the damage. + +It seems obvious that the EU is going to come down harder on the company who didn't even try. + +#### What we're already doing + +We already do a number of things that are driven by a *privacy by design* approach. For example: + + - We use pseudonyms for user accounts + - We don't share any data with any third party + - We don't include any tracking code, or analytics + - We don't use cookies + - We don't have any social logins, like buttons, or other such things + - We don't run/show any ads + - We don't run any third-party JavaScript code + - We use encryption on all transport + +There's some more info on this in this blog post: +[The choices I've made to protect your privacy. Or why you won't be getting any cookies](/blog/privacy-choices/). + +These already form a very good basis for a privacy conscious website. But since we'll need to make changes +for GDPR anyway, we're considering other options to further raise the privacy bar. +Specifically, what can we do to limit the damage to our users in case there is a data leak. + +#### Restriction of data storage + +Some of the most sensitive data we store today is the address and birthday of our higher-tier patrons. + +However, the site does not need this information to function. We only need it for administrative purposes; +Sending out gifts and birthday cards to our patrons. + +As such, there's no real need to keep this data in the freesewing database. +We could just as well write this information down in a notebook we keep on our coffee table. + +So, as part of our GDPR-related changes, we will remove this information from the database, and store it +offline. + +#### Encryption of data at rest + +We already encrypt all data in transit. But, we are currently considering to add encryption of data at rest. + +The idea is to encrypt all data that could potentially identify a user. +Such as: + + - Email address + - User name + - Model names + - Model notes + +This would add an extra layer of defense for our users' privacy in case somehow our database gets dumped. + +While this change will be non-trivial to implement and come with a performance penalty, I feel it's +worth looking in to. + +## Conclusion + +While we still have some work to do, we are already compliant with large parts of the GDPR, especially when +it comes to respecting users rights: + + - The right to be informed + - The right of access + - The right to rectification + - The right to erasure + - The right to restrict processing + - The right to data portability + - The right to object + - Rights in relation to automated decision making and profiling + +We are currently working on *the right to be informed* and have a plan +for the changes required to respect *the right to restrict processing* and *the right to object*. + +On the data collection site, we need to hammer out the details for our privacy notices. +We'll also write a detailed privacy policy that bundles all the info from the different notices. + +We'll need to add changes to the user on-boarding to make sure notices are presented at the correct time. +Not to mention that we'll need to keep track of who gave their consent for what. + +### Action points + + - Draft privacy notices for profile/model/patron data + - Integrate consent in user on-boarding, model creation, and patron sign-up + - Make site functionality depend on consent + - Provide a centralized privacy dashboard where people can review their privacy settings/consent + - Add email notifications every time consent is changed + - Provide a way for people to *freeze* their account + - Provide a way for people to object to their model data being used for research and statistics + - Write and publish an overall privacy policy + - Encrypt sensitive data in the database + +Seems like we've got a lot of work ahead of us. + +### Feedback + +It is my personal opinion that the GDPR is a good thing. +But I want to hear from you about the changes outlined in this blog post. + +So please reach out with your feedback and comments. +It is after all your data we're talking about. + + diff --git a/markdown/org/blog/gdpr-plan/es.md b/markdown/org/blog/gdpr-plan/es.md new file mode 100644 index 00000000000..5daf544a303 --- /dev/null +++ b/markdown/org/blog/gdpr-plan/es.md @@ -0,0 +1,367 @@ +--- +author: "joostdecock" +caption: "This image is probably the only thing in the post you can skim diagonally" +date: "2018-02-14" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/39f3d1e7320510b2dd12cc1bc2e58008263889f3-1920x1280.webp" +intro: "The General Data Protection Regulation of the European Union: Our battle plan. [No traducido]" +title: "The General Data Protection Regulation of the European Union: Our battle plan. [No traducido]" +--- + +This blog post is about the General Data Protection Regulation (GDPR) of the European Union (EU). +While I cover the basics of GDPR, the main focus is on how it impacts freesewing.org, and what we plan to do to in the 100 days that remain +before GDPR goes into force. + +This is a bit of a long read, so here's a table of contents: + +## Thoughts on the EU's GDPR + +I have a love/hate relationship with the European Union. +I love what they do and what they stand for, I hate how they do it. + +![I totally get this dude](https://posts.freesewing.org/uploads/rage_quit_fff821e695.gif) + +The GDPR is no different. +It's an important piece of legislation that raises the bar for online privacy, which is great. +But as I was reading up on the subject, I felt the urge to rage-quit because OMG bureaucrats. + +Allow me to explain. + +### Privacy needs protection +For better or for worse (I believe for worse) the internet has settled into a modus operandi +where you pay for *free stuff* with your personal data. +Some people call it [people farming](https://ar.al/notes/we-didnt-lose-control-it-was-stolen/), and I think that's a great term. + +The [frightful five](https://www.nytimes.com/2017/05/10/technology/techs-frightful-five-theyve-got-us.html) +are vacuuming up ever more of our personal lives. +Short of never going online, there seems to be precious little we can do about it. + +### Why the EU is the best +This problem is too big to tackle by any of us. +Who could possibly stand up to the combined power of the tech giants? + +Well, how's this for a CV: + + - Fined Facebook 110 million euro for misleading statements about their WhatsApp purchase + - Ordered Amazon to pay 250 million euro extra taxes in Luxembourg + - Fined Google 2.4 billion euro for abusing its dominant position in search + - Ordered Apple to pay 13 billion euro extra taxes in Ireland + +![We're the EU, bitch](titanfall.gif) + +When it comes to tech giants, the European Union is all stick/ no carrot. + +The General Data Protection Regulation enforces privacy policies that respect users' rights. +It applies to all EU citizens, all the time, everywhere. + +Doesn't matter if you're a silicon valley juggernaut, respect the rights of the EU citizens or face the wrath of the eurocracy: + +> Organizations in breach of GDPR can be fined up to 4% of annual global turnover or 20 million euro (whichever is greater) + +Four percent of global turnover is *a very big stick*. + +### Why the EU is the worst + +![What I imagine a Article 29 Working Party looks like](complicated.gif) + +The EU being the EU, the regulation is a mixed bag of lofty goals and ideals, watered down by lobbying groups, and further complicated by the compromise required to get 28 member states on board. + +The intentions are great, it's a great idea, but they are doing a terrible job at selling it --- as usual. + +The practical implementation is in the hands of the so-called *Article 29 Working Party* +which is currently keeping busy designing icons +(I am [not making this up](https://www.google.be/search?q=standardised+icons+gdpr)) +It will change its name to the +*European Data Protection Board* come May 25th, because you wouldn't want to get too comfortable with all this jargon now, would you? + +## The GDPR in practice + +If you're looking for expert advice on GDPR compliance, this is not the place for you. + + +But if you are curious about the GDPR and what it takes for a website like freesewing.org +to be compliant, read on. + +> ##### Further reading +> If you really want to know what GDPR is, the best thing you can do is +> [read the damn thing](http://eur-lex.europa.eu/legal-content/en/TXT/?uri=CELEX%3A32016R0679). It ain't no rocket science. +> +> If legislative texts make you run for the hills, the UKs ICO has +> [easily one of the best guides on GDPR](https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/). + +### Good to know + +A few things you should know before we dive into GDPR: + +#### There's 100 days left + +The GDPR was adopted back in 2016, but it won't grow its teeth until May 25th 2018. + +Until that day, you get a pass. After that day, it's for real. +Which means we have 100 days left to get our house in order. + +#### There's exemptions for SMEs + +Organizations employing fewer than 250 people are exempt from some of the more bureaucratic aspects of the GDPR, such as a bunch of documenting requirements. + +Essentially, while you still have to do the right thing, there's a lot less paperwork to fill out. + +Freesewing employs zero people, so we're off the hook. + +#### There's extra provisions for sensitive data + +> Body measurements alone are not sensitive data + +The GDPR has extra provisions for *sensitive data* +such as biometric data, profiling, and a bunch of other stuff. + +This was cause for concern because we collect body measurements, and one of our questions was whether that qualifies as biometric data. + +Turns out it doesn't. Biometric data is what you can use to identify a person, like a fingerprint or iris scan. Body measurements alone are not sensitive data. + + +### Collecting data through consent + +To collect data, you need a so-called *lawful basis for data processing*. +There are different types, but the one that applies to us (and to most online services) is **consent**. + +In this scenario, your legal basis for processing the data is that you've asked the person to get their data +and they've freely given it to you. + +That is straight-forward, and makes sense. But the GDPR is really serious about making sure this consent is +freely given, and not wrestled from you grudgingly. + +To prevent companies from throwing up a big wall of legalese that people have to agree to, the GDPR outlines a number +of principles this consent should adhere to. Here's a non-exhaustive list: + + - people should have real choice and control + - consent requires a positive opt-in, pre-ticked boxes or anything like that are not allowed + - there should be a very clear statement explaining what people are agreeing to + - these requests for consent must be separate from any terms & conditions + - consent needs to be granular, you need individual consent for different things, and can't ask for blanket consent + - it must be easy for people to redraw consent + - consent of data processing should not be a precondition for a service + +Looking at that list, I can't help but feel that legislation would be a lot simpler if lawmakers could just write +*don't be a dick* and call it a day. + +#### Consent granularity + +Remember, we can't just get blanket consent. +We need to get consent for every type of data processing we do. + +For freesewing.org, we have identified three different types of data processing: + + - Profile data + - Model data + - Patron data + +For each of these, we'll need to get consent from the user, making sure it's *real consent* as intended in the GDPR. + +Below is a mockup for what this could look like for each data type: + +> ##### These mockups are no longer available +> +> Please note that the mockups originally included in this post are no longer +> available. Instead, this functionality has been implemented in the website. + +#### Consent timing + +The GDPR states that you should ask for consent when the data is collected. + +With our three types of data processing, that means that consent must be asked at different times: + + - **Profile data**: When signing up on the site + - **Model data**: When creating the first model + - **Patron data**: When becoming a patron + +This will (also) require some extra work to integrate this in the site. + +### Respecting basic rights when processing data + +The EU enshrines basic rights for its citizens that should be respected when processing data. + +Let's look at each of these rights and their impact on freesewing.org. + +#### The right to be informed + +> You need to be transparent about how you use personal data. Why you collect it, how you use it, and so on. + +Informing users is something we are still working on. If anything, this blog post is part of that effort. + +We will need to design the individual privacy notices, but also a more overall privacy policy as well as +making certain that users are informed of all their rights. + +While this will require some work, I don't expect any problems here. + +#### The right of access + +> People have the right to know their data is processed, and to access that data. + +We are already compliant, as all data users enter on the site can also be accessed by them. + +#### The right to rectification + +> People have the right to correct their data if it's not correct. + +We are already compliant, as all data users enter on the site can also be edited by them. + +#### The right to erasure + +> People have the right to have their data removed/erased. + +We are already compliant, as users can remove their models, or entire account at any time. + +#### The right to restrict processing + +This right means that users must be able to put a *freeze* on all data processing, without going as far as to delete their data. + +We do not currently offer this possibility, and will need to add this functionality to the site. + +#### The right to data portability + +> People not only have a right to export all their data, that export should also be in a format that makes it easy for them to take their data elsewhere. + +We are already compliant, as we allow users to export all of their data, and make it available in different standard formats (YAML and JSON). + +#### The right to object + +> The right to object applies specifically to: +> +> - processing for public interests or by official authorities +> - processing for direct marketing +> - processing for science/historic research/statistics +> +> In these cases, people can object to this specific processing. + +This is going to apply to us when we start publishing anonymized model data, something that's on our roadmap. + +The reason for publishing this data is that we want to make a dataset available of *real* body measurements, rather than the +*standard* measurements that are typically used in the industry. + +This is something we'll write about more at a later date, but essentially this falls under the *scientific research/statistics* category. +And even though the data is anonimized, we still need to respect the right of users to object to this processing. + +As such, we should add the possibility to object to this specific use of the data. + +#### Rights in relation to automated decision making and profiling + +> People have extra rights when it comes to profiling or decisions made by AI or algorithms without human involvement. + +This is not relevant in our situation. + +### Privacy by design + +The EU isn't content with throwing up a couple of consent questions and respecting people's rights when processing data. +It also wants to make certain that your privacy is (better) protected when things go wrong. + +That's why it advocates for *privacy by design*. While it's a concept that's hard to pin down in legislation, the +purpose is clear: They want everyone to consider privacy from the very start of their project/product/business, and +not as an afterthought. + +Things such as encryption (both in transit and for data at-rest), pseudonyms, and data expiry are suggested as +things to keep in mind while designing. + +Obviously, the EU is not going to come check your code to see whether you've taken privacy by design to heart. +But it can (and probably will) have an influence when things to wrong. + +Imagine two companies who have a data leak, one of them hasn't done much to safeguard the privacy of their users, +whereas the other has taken *privacy by design* measures to mitigate the damage. + +It seems obvious that the EU is going to come down harder on the company who didn't even try. + +#### What we're already doing + +We already do a number of things that are driven by a *privacy by design* approach. For example: + + - We use pseudonyms for user accounts + - We don't share any data with any third party + - We don't include any tracking code, or analytics + - We don't use cookies + - We don't have any social logins, like buttons, or other such things + - We don't run/show any ads + - We don't run any third-party JavaScript code + - We use encryption on all transport + +There's some more info on this in this blog post: +[The choices I've made to protect your privacy. Or why you won't be getting any cookies](/blog/privacy-choices/). + +These already form a very good basis for a privacy conscious website. But since we'll need to make changes +for GDPR anyway, we're considering other options to further raise the privacy bar. +Specifically, what can we do to limit the damage to our users in case there is a data leak. + +#### Restriction of data storage + +Some of the most sensitive data we store today is the address and birthday of our higher-tier patrons. + +However, the site does not need this information to function. We only need it for administrative purposes; +Sending out gifts and birthday cards to our patrons. + +As such, there's no real need to keep this data in the freesewing database. +We could just as well write this information down in a notebook we keep on our coffee table. + +So, as part of our GDPR-related changes, we will remove this information from the database, and store it +offline. + +#### Encryption of data at rest + +We already encrypt all data in transit. But, we are currently considering to add encryption of data at rest. + +The idea is to encrypt all data that could potentially identify a user. +Such as: + + - Email address + - User name + - Model names + - Model notes + +This would add an extra layer of defense for our users' privacy in case somehow our database gets dumped. + +While this change will be non-trivial to implement and come with a performance penalty, I feel it's +worth looking in to. + +## Conclusion + +While we still have some work to do, we are already compliant with large parts of the GDPR, especially when +it comes to respecting users rights: + + - The right to be informed + - The right of access + - The right to rectification + - The right to erasure + - The right to restrict processing + - The right to data portability + - The right to object + - Rights in relation to automated decision making and profiling + +We are currently working on *the right to be informed* and have a plan +for the changes required to respect *the right to restrict processing* and *the right to object*. + +On the data collection site, we need to hammer out the details for our privacy notices. +We'll also write a detailed privacy policy that bundles all the info from the different notices. + +We'll need to add changes to the user on-boarding to make sure notices are presented at the correct time. +Not to mention that we'll need to keep track of who gave their consent for what. + +### Action points + + - Draft privacy notices for profile/model/patron data + - Integrate consent in user on-boarding, model creation, and patron sign-up + - Make site functionality depend on consent + - Provide a centralized privacy dashboard where people can review their privacy settings/consent + - Add email notifications every time consent is changed + - Provide a way for people to *freeze* their account + - Provide a way for people to object to their model data being used for research and statistics + - Write and publish an overall privacy policy + - Encrypt sensitive data in the database + +Seems like we've got a lot of work ahead of us. + +### Feedback + +It is my personal opinion that the GDPR is a good thing. +But I want to hear from you about the changes outlined in this blog post. + +So please reach out with your feedback and comments. +It is after all your data we're talking about. + + diff --git a/markdown/org/blog/gdpr-plan/fr.md b/markdown/org/blog/gdpr-plan/fr.md new file mode 100644 index 00000000000..0c6d56d25e6 --- /dev/null +++ b/markdown/org/blog/gdpr-plan/fr.md @@ -0,0 +1,320 @@ +--- +author: "joostdecock" +caption: "Cette image est probablement la seule chose dans le article que vous pourrez parcourir en diagonale" +date: "2018-02-14" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/39f3d1e7320510b2dd12cc1bc2e58008263889f3-1920x1280.webp" +intro: "Cet article de blog traite du Règlement Général sur la Protection de Données (RGPD) de l'Union Européenne (EU). Bien que je couvre les bases du RGPD, l'accent est mis sur la façon dont il impacte freesewing.org et ce que nous prévoyons de faire dans les 100 jours qui viennent avant l'entrée en vigueur du RGPD." +title: "Le Règlement Général sur la Protection des Données de l'Union Européenne: Notre plan de bataille." +--- + + +Cet article de blog traite du Règlement Général sur la Protection de Données (RGPD) de l'Union Européenne (EU). Bien que je couvre les bases du RGPD, l'accent est mis sur la façon dont il impacte freesewing.org et ce que nous prévoyons de faire dans les 100 jours qui viennent avant l'entrée en vigueur du RGPD. + +Tout cela représente une sacré lecture, donc voici donc une table des matières : + +## Pensées sur le RGPD de l'UE + +J'ai une relation d'amour/haine avec l'Union européenne. J'adore ce qu'ils font et ce qu'ils défendent, je déteste la façon dont ils le font. + +![Je comprends totalement ce gars](rage-quit.gif) + +Le RGPD ne fait pas exception. C'est un acte législatif important qui met la barre faute en matière de confidentialité en ligne ; ce qui est formidable. Mais alors qu'avançais dans la lecture à ce sujet, j'ai failli tout laisser tomber de rage car c'est un sacré boulot de bureaucrate ! + +Permettez-moi de m'expliquer. + +### La vie privée a besoin d'être protégée +Pour le meilleur ou pour le pire (je pense pour le pire) Internet s'est installé dans un mode opératoire où vous payez pour des *choses gratuites* avec vos données personnelles. Certains appellent ça [la culture des personnes](https://ar.al/notes/we-didnt-lose-control-it-was-stolen/), et je pense que c'est un bon terme. + +Les [GAFAM](https://www.nytimes.com/2017/05/10/technology/techs-frightful-five-theyve-got-us.html) (Google/Apple/Facebook/Microsoft/Amazon) aspirent de plus en plus d'informations de nos vies personnelles. A part ne jamais se connecter sur Internet, il semble que nous ne puissions pas faire grand-chose à ce sujet. + +### Pourquoi l'Union Européenne est la meilleure +Ce problème est trop important pour que chacun d'entre nous s'y colle. Qui pourrait résister à la puissance combinée des géants technologiques ? + +Eh bien, voici un quelques chiffres : + + - Facebook a reçu une amende de 110 millions d'euros pour des déclarations trompeuses à propos de leur achats WhatsApp + - Amazon a été condamné à payer 250 millions d'euros de taxes supplémentaires au Luxembourg + - Google a reçu une amende de 2,4 milliards d'euros pour avoir abusé de sa position dominante dans les moteurs de recherche + - Apple a été condamné à payer 13 milliards d'euros de taxes supplémentaires en Irlande + +![Nous sommes l'UE, garce](titanfall.gif) + +En ce qui concerne les géants du numérique, l'Union Européenne n'utilise que le bâton ; pas la carotte. + +Le Règlement Général sur la Protection des Données applique des politiques de confidentialité qui respectent les droits des utilisateurs. Elle s'applique à tous les citoyens de l'UE, à tout moment, partout. + +Peu importe que vous soyez une poids lourd de la "silicon valley", que vous respectiez les droits des citoyens de l'UE ou que vous soyez confronté à la colère de l'eurocratie : + +> Les organisations qui violent le RGPD peuvent être condamnées à une amende allant jusqu'à 4 % de leur chiffre d'affaires mondial annuel ou 20 millions d'euros (selon le plus élevé des deux) + +Quatre pour cent du chiffre d'affaires global est *un très gros bâton*. + +### Pourquoi l'UE est la pire + +![Ce que j'imagine à quoi ressemble un groupe de travail sur l'article 29](complicated.gif) + +L'UE étant l'UE, le règlement est un mélange d'objectifs et d'idéaux élevés, avec une pression des lobbies, est en plus complexifié par le compromis nécessaire pour rallier 28 États membres. + +Les intentions sont nobles, c'est une super idée, mais ils le vendent très mal --- comme d'habitude. + +La mise en œuvre pratique est entre les mains du fameux *Groupe de travail de l'Article 29* qui est actuellement occupé à concevoir des icônes (je [n'invente rien](https://www.google.be/search?q=standardised+icons+gdpr)) Elle changera son nom en *Bureau Européen de Protection des Données* le 25 mai prochain, car qui ne voudrait pas être bien plus à l'aise avec tout ce jargon maintenant, n'est-ce- pas ? + +## Le RGPD en pratique + +Si vous cherchez des conseils d'experts sur la conformité au RGPD, ce n'est pas l'endroit idéal pour vous. + + +Mais si vous êtes curieux à propos du RGPD et de ce qu'il faut pour qu'un site comme freesewing.org soit conforme, vous pouvez lire ce qui suit. + +> ##### Lectures additionnelles +> +> Si vous voulez vraiment savoir ce qu'est le RGPD, la meilleure chose que vous pouvez faire est de [lire ce sacré morceau](http://eur-lex.europa.eu/legal-content/en/TXT/?uri=CELEX%3A32016R0679). Ce n'est pas sorcier. +> +> Si des textes législatifs vous font prendre vos jambes à votre cou, l'ICO du Royaume-Uni a [clairement l'un des meilleurs guides sur le RGPD](https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/). + +### Bon à savoir + +Quelques petites choses que vous devriez savoir avant de plonger dans le RGPD : + +#### Il reste 100 jours + +Le GDPR a été adopté en 2016, mais ses dents n'auront pas poussées avant le 25 mai 2018. + +Jusqu’à ce jour, vous obtenez un laissez-passer. Après ce jour, ce sera réel. Ce qui signifie qu'il nous reste 100 jours pour remettre de l'ordre dans notre maison. + +#### Il y a des exemptions pour les PME + +Les organisations employant moins de 250 personnes sont exemptées de certains des aspects les plus bureaucratiques du RGPD, comme notamment tout un tas d'exigences documentaires. + +Dans l'essentiel, même si vous devez quand même faire les choses bien, il y a beaucoup moins de paperasse à remplir. + +Freesewing emploie zéro personnes, nous sommes donc tirés d'affaire. + +#### Il y a des dispositions supplémentaires pour les données sensibles + +> Les mensurations seules ne sont pas des données sensibles en soi + +Le RGPD a des dispositions supplémentaires pour *données sensibles* telles que les données biométriques, le profilage, et un tas d'autres choses. + +C'est ce qui est à l'origine de nos préoccupations car nous collectons des mensurations, et une de nos questions était de savoir si celles-ci sont qualifiées de données biométriques. + +Il s'avère que ce n'est pas le cas. Les données biométriques sont celles que vous pouvez utiliser pour identifier une personne, comme une empreinte digitale ou un scan d'iris. Les mensurations seules ne sont pas des données sensibles en soi. + + +### Collecte de données par consentement + +Pour collecter des données, vous avez besoin d'une fameuse *base légale pour le traitement des données*. Il existe différents types, mais celui qui s'applique à nous (et à la plupart des services en ligne) est **le consentement**. + +Dans ce scénario, votre base légale pour le traitement des données est que vous avez demandé à la personne de récupérer ses données et qu'elle vous les a données librement. + +C'est direct et cela a du sens. Mais le RGPD est très sérieux pour s'assurer que ce consentement est donné librement et qu'il n'est pas obtenu à contre cœur. + +Pour empêcher les entreprises de dresser un grand mur juridique contre lequel les gens se heurteraient, le RGPD décrit un certain nombre de de principes auxquels ce consentement devrait adhérer. Voici une liste non exhaustive : + + - les gens devraient avoir un vrai choix et un vrai contrôle + - le consentement requiert une action positive en ce sens, des cases pré-cochées ou quoique ce soit dans ce genre, ce n'est pas autorisé + - il devrait y avoir une déclaration très claire expliquant ce que les gens acceptent + - ces demandes de consentement doivent être distinctes de tout autres termes & conditions + - le consentement doit être granulaire, vous avez besoin d'un consentement individuel pour différentes choses, et ne pouvez pas demander un consentement général + - il doit être facile pour les gens de retracer leur consentement + - le consentement au traitement des données ne doit pas être une condition préalable à un service + +En regardant cette liste, Je ne peux m'empêcher de penser que la législation serait beaucoup plus simple si les législateurs pouvaient juste écrire *ne faites pas le con* et s'en tenir à ça. + +#### Granularité du consentement + +Rappelez-vous que nous ne pouvons pas seulement obtenir un consentement global. Nous devons obtenir le consentement de chaque type de traitement de données que nous faisons. + +Pour freesewing.org, nous avons identifié trois types différents de traitement de données: + + - Données de profil + - Données de modèle + - Données de mécène + +Pour chacun d'entre eux, nous devrons obtenir le consentement de l'utilisateur, en s'assurant que c'est un *consentement réel* comme prévu dans le RGPD. + +Voici une maquette de ce à quoi cela pourrait ressembler à chaque type de données : + +> ##### Ces maquettes ne sont plus disponibles +> +> Veuillez noter que les maquettes initialement incluses dans ce message ne sont plus disponibles. A la place, cette fonctionnalité a été directement implémentée dans le site Web. + +#### Temps du consentement + +Le RGPD indique que vous devez demander votre consentement lors de la collecte des données. + +Avec nos trois types de traitement des données, cela signifie que le consentement doit être demandé à des moments différents : + + - **Données de profil**: lors de l'inscription sur le site + - **Données de modèle**: lors de la création du premier modèle + - **Données de mécène**: En devenant un mécène + +Cela nécessitera (également) un travail supplémentaire pour intégrer ceci dans le site. + +### Respecter des droits fondamentaux lors du traitement des données + +L'UE garantit à ses citoyens des droits fondamentaux qui doivent être respectés lors du traitement des données. + +Examinons chacun de ces droits et leur impact sur freesewing.org. + +#### Le droit d’être informé + +> Vous devez être transparent quant à la façon dont vous utilisez les données personnelles. Pourquoi vous le collectez, comment vous les utilisez, etc. + +nous travaillons encore sur l'information des utilisateurs. En tout cas, cet article de blog participe à cet effort. + +Nous devrons concevoir la Politique de Confidentialité individuelle, mais aussi une politique de confidentialité plus générale tout en veillant à ce que les utilisateurs soient informés de tous leurs droits. + +Bien que cela demande un peu de travail, je ne m'attends pas à ce qu'il y ait des problèmes ici. + +#### Le droit d’accès + +> Les personnes ont le droit de savoir si leurs données sont traitées, et de pouvoir y accéder. + +Nous sommes déjà conformes, puisque toutes les données que les utilisateurs saisissent sur le site sont également accessibles par eux. + +#### Le droit de rectification + +> Les personnes ont le droit de corriger leurs données si elles ne sont pas correctes. + +Nous sommes déjà conformes, car toutes les données que les utilisateurs saisissent sur le site peuvent également être modifiées par eux. + +#### Le droit à l’effacement + +> Les personnes ont le droit de supprimer/effacer leurs données. + +Nous sommes déjà conformes, car les utilisateurs peuvent supprimer leurs modèles, ou tout le compte à tout moment. + +#### Le droit à la limitation du traitement + +Ce droit signifie que les utilisateurs doivent être en mesure de mettre une *limitation* sur tout traitement de données, sans aller jusqu'à supprimer leurs données. + +Pour le moment, nous n'offrons pas cette possibilité, et nous devrons ajouter cette fonctionnalité au site. + +#### Le droit à la portabilité des données + +> Les personnes n'ont pas seulement le droit d'exporter toutes leurs données, mais cette exportation doit également être dans un format qui leur permet de les utiliser ailleurs. + +Nous sommes déjà conformes, car nous permettons aux utilisateurs d'exporter toutes leurs données, et de les rendre disponibles dans différents formats standards (YAML et JSON). + +#### Le droit d’opposition + +> Le droit d'opposition s'applique spécifiquement à : +> +> - traitement pour des intérêts publics ou par les autorités officielles +> - traitement du marketing direct +> - traitement des statistiques/recherches scientifiques/historiques +> +> Dans ces cas, les personnes peuvent s'opposer à ce traitement spécifique. + +Cela s'appliquera à nous lorsque nous commencerons à publier des données de modèles anonymisés ; chose qui est sur notre feuille de route. + +La raison pour laquelle nous publions ces données est que nous voulons mettre à disposition un jeu de données de mensurations *réelles*, plutôt que des mensurations *standards* qui sont généralement utilisées dans l'industrie. + +C'est quelque chose que sur quoi écrirons davantage à une date ultérieure, mais globalement ça tombe dans la catégorie *recherche/statistiques scientifique*. Et même si les données sont anonymisées, nous devons toujours respecter le droit des utilisateurs de s'opposer à ce traitement. + +À ce titre, nous devrions ajouter la possibilité de nous opposer à cette utilisation spécifique des données. + +#### Droits relatifs à l'automatisation de prise de décision et de profilage + +> Les gens ont des droits supplémentaires en matière de profilage ou de décisions prises par des IA ou des algorithmes sans implication humaine. + +Cela n'est pas pertinent dans notre situation. + +### Respect de la vie privée dès la conception + +L'UE ne se contente pas de poser quelques questions de consentement et de respect les droits des personnes sur le traitement des données. Elle veut aussi s'assurer que votre vie privée est (mieux) protégée lorsque les choses tournent mal. + +C'est pourquoi il préconise le *respect de la vie privée dès la conception*. Bien que ce concept soit difficile à mettre en place dans la législation, le but est clair : ils veulent que tout le monde prenne en considération le respect de la vie privée dès le début de leur projet/produit/entreprise, et pas comme une réflexion a posteriori. + +Des choses telles que le chiffrement (tant en transit que pour les données en sommeil), les pseudonymes, et l'expiration des données, sont suggérées comme à garder à l'esprit dès la conception. + +Évidemment, l'UE ne va pas venir vérifier votre code pour voir si vous avez pris à cœur le respect de la vie privée dès la conception. Mais elle peut (et elle aura sûrement) avoir une influence si les choses tournent mal. + +Imaginez deux entreprises qui ont une fuite de données, l'une d'entre elles n'a pas fait grand chose pour protéger la vie privée de leurs utilisateurs, alors que l'autre a pris des mesures pour *le respect de la vie privée dès la conception* afin d'atténuer les dégâts. + +Il semble évident que l'UE va se montrer plus sévère à l'égard de la société qui n'a pas fait d'effort. + +#### Ce que nous faisons déjà + +Nous faisons déjà un certain nombre de choses qui sont animées par une approche de *respect de la vie privée dès la conception*. Par exemple : + + - Nous utilisons des pseudonymes pour les comptes utilisateurs + - Nous ne partageons aucune donnée avec un tiers + - Nous n'incluons pas de code de suivi, ou d'analyse + - Nous n'utilisons pas de cookies + - Nous n'avons pas de connexions sociales, comme des boutons de "j'aime", ou autres choses de ce genre + - Nous ne diffusons pas de publicités + - Nous n'exécutons aucun code JavaScript tiers + - Nous utilisons le chiffrement pour tous les tranferts + +Il y a plus d'informations à ce sujet dans cet article du blog : [Les choix que j'ai faits pour protéger votre vie privée. Ou pourquoi vous n'aurez pas de cookies](/blog/privacy-choices/). + +Ceci forme déjà une très bonne base pour un site web soucieux de la protection de la vie privée. Mais comme nous aurons besoin de faire des changements pour le RGPD de toute façon, nous envisageons d'autres options pour élever davantage le niveau de confidentialité. Plus précisément, ce que nous pouvons faire pour limiter les dégâts causés à nos utilisateurs en cas de fuite de données. + +#### Limiter la conservation des données + +Parmi les des données les plus sensibles que nous enregistrons aujourd'hui il y a l'adresse et l'anniversaire de nos plus mécènes de niveau supérieur. + +Toutefois, le site n'a pas besoin de ces informations pour fonctionner. Nous n'en avons besoin qu'à des fins administratives ; envoi de cadeaux et de cartes d'anniversaire à nos mécènes. + +Il n'y a donc aucun besoin réel de conserver ces données dans la base de données freesewing. Nous pourrions aussi bien écrire ces informations dans un carnet que nous garderions sur notre table basse. + +Donc, dans le cadre de nos changements pour le RGPD, nous supprimerons ces informations de la base de données et les stockerons hors ligne. + +#### Chiffrement des données stockées + +Nous cryptons déjà toutes les données en transit. Mais nous envisageons actuellement d'ajouter le chiffrement des données stockées. + +L'idée est de chiffrer toutes les données qui pourraient potentiellement identifier un utilisateur. Telles que : + + - Adresse E-mail + - Nom d’utilisateur + - Noms de modèle + - Notes de modèle + +Cela ajouterait une couche supplémentaire de défense de la vie privée de nos utilisateurs au cas où notre base de données serait détruite. + +Bien que ce changement risque d'être difficile à mettre en œuvre et assorti d'une perte de performance, je pense que ça vaut la peine d'y travailler. + +## Conclusion + +Bien que nous ayons encore du pain sur la planche, nous sommes déjà en conformité avec une grande partie du RGPD, en particulier quand il s'agit de respecter les droits des utilisateurs : + + - Le droit d’être informé + - Le droit d’accès + - Le droit de rectification + - Le droit à l’effacement + - Le droit à la limitation du traitement + - Le droit à la portabilité des données + - Le droit d’opposition + - Droits relatifs à l'automatisation de prise de décision et de profilage + +Nous travaillons actuellement sur *le droit à l'information* et avons un plan pour les changements requis afin de respecter *le droit de restreindre le traitement* et *le droit de contester*. + +Sur le site de collecte de données, nous devons préciser les détails de nos avis de confidentialité. Nous allons également écrire une politique de confidentialité détaillée qui inclut toutes les informations des différentes avis. + +Nous devrons ajouter des modifications lors de la prise en main de l'utilisateur pour nous assurer que les avis sont présentés au bon moment. Sans oublier que nous devrons garder trace de qui a donné son consentement et pour quoi. + +### Points d'action + + - Brouillon des avis de confidentialité pour les données du profil/modèle/patron + - Intégrer le consentement au démarrage, à la création de modèles et à l'inscription des mécènes + - Rendre la fonctionnalité du site dépendante du consentement + - Fournir un rapport de confidentialité centralisé où les personnes peuvent consulter leurs paramètres de confidentialité / consentement + - Ajouter des notifications par email chaque fois que le consentement est modifié + - Permettre aux personnes de *geler* leur compte + - Permettre aux personnes de s'opposer à l'utilisation de leurs données de modèle pour la recherche et les statistiques + - Écrire et publier une politique de confidentialité globale + - Chiffrer les données sensibles dans la base de données + +Il semble que nous ayons beaucoup de travail devant nous. + +### Avis + +Je pense personnellement que le RGPD est une bonne chose. Mais je veux entendre vos avis à propos des changements décrits dans ce billet de blog. + +Donc s'il vous plaît faites-nous part de vos commentaires et avis. Après tout, ce sont vos données dont nous parlons. + + + diff --git a/markdown/org/blog/gdpr-plan/nl.md b/markdown/org/blog/gdpr-plan/nl.md new file mode 100644 index 00000000000..8143274bfe8 --- /dev/null +++ b/markdown/org/blog/gdpr-plan/nl.md @@ -0,0 +1,367 @@ +--- +author: "joostdecock" +caption: "This image is probably the only thing in the post you can skim diagonally" +date: "2018-02-14" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/39f3d1e7320510b2dd12cc1bc2e58008263889f3-1920x1280.webp" +intro: "The General Data Protection Regulation of the European Union: Our battle plan. [Niet vertaald]" +title: "The General Data Protection Regulation of the European Union: Our battle plan. [Niet vertaald]" +--- + +This blog post is about the General Data Protection Regulation (GDPR) of the European Union (EU). +While I cover the basics of GDPR, the main focus is on how it impacts freesewing.org, and what we plan to do to in the 100 days that remain +before GDPR goes into force. + +This is a bit of a long read, so here's a table of contents: + +## Thoughts on the EU's GDPR + +I have a love/hate relationship with the European Union. +I love what they do and what they stand for, I hate how they do it. + +![I totally get this dude](https://posts.freesewing.org/uploads/rage_quit_fff821e695.gif) + +The GDPR is no different. +It's an important piece of legislation that raises the bar for online privacy, which is great. +But as I was reading up on the subject, I felt the urge to rage-quit because OMG bureaucrats. + +Allow me to explain. + +### Privacy needs protection +For better or for worse (I believe for worse) the internet has settled into a modus operandi +where you pay for *free stuff* with your personal data. +Some people call it [people farming](https://ar.al/notes/we-didnt-lose-control-it-was-stolen/), and I think that's a great term. + +The [frightful five](https://www.nytimes.com/2017/05/10/technology/techs-frightful-five-theyve-got-us.html) +are vacuuming up ever more of our personal lives. +Short of never going online, there seems to be precious little we can do about it. + +### Why the EU is the best +This problem is too big to tackle by any of us. +Who could possibly stand up to the combined power of the tech giants? + +Well, how's this for a CV: + + - Fined Facebook 110 million euro for misleading statements about their WhatsApp purchase + - Ordered Amazon to pay 250 million euro extra taxes in Luxembourg + - Fined Google 2.4 billion euro for abusing its dominant position in search + - Ordered Apple to pay 13 billion euro extra taxes in Ireland + +![We're the EU, bitch](titanfall.gif) + +When it comes to tech giants, the European Union is all stick/ no carrot. + +The General Data Protection Regulation enforces privacy policies that respect users' rights. +It applies to all EU citizens, all the time, everywhere. + +Doesn't matter if you're a silicon valley juggernaut, respect the rights of the EU citizens or face the wrath of the eurocracy: + +> Organizations in breach of GDPR can be fined up to 4% of annual global turnover or 20 million euro (whichever is greater) + +Four percent of global turnover is *a very big stick*. + +### Why the EU is the worst + +![What I imagine a Article 29 Working Party looks like](complicated.gif) + +The EU being the EU, the regulation is a mixed bag of lofty goals and ideals, watered down by lobbying groups, and further complicated by the compromise required to get 28 member states on board. + +The intentions are great, it's a great idea, but they are doing a terrible job at selling it --- as usual. + +The practical implementation is in the hands of the so-called *Article 29 Working Party* +which is currently keeping busy designing icons +(I am [not making this up](https://www.google.be/search?q=standardised+icons+gdpr)) +It will change its name to the +*European Data Protection Board* come May 25th, because you wouldn't want to get too comfortable with all this jargon now, would you? + +## The GDPR in practice + +If you're looking for expert advice on GDPR compliance, this is not the place for you. + + +But if you are curious about the GDPR and what it takes for a website like freesewing.org +to be compliant, read on. + +> ##### Further reading +> If you really want to know what GDPR is, the best thing you can do is +> [read the damn thing](http://eur-lex.europa.eu/legal-content/en/TXT/?uri=CELEX%3A32016R0679). It ain't no rocket science. +> +> If legislative texts make you run for the hills, the UKs ICO has +> [easily one of the best guides on GDPR](https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/). + +### Good to know + +A few things you should know before we dive into GDPR: + +#### There's 100 days left + +The GDPR was adopted back in 2016, but it won't grow its teeth until May 25th 2018. + +Until that day, you get a pass. After that day, it's for real. +Which means we have 100 days left to get our house in order. + +#### There's exemptions for SMEs + +Organizations employing fewer than 250 people are exempt from some of the more bureaucratic aspects of the GDPR, such as a bunch of documenting requirements. + +Essentially, while you still have to do the right thing, there's a lot less paperwork to fill out. + +Freesewing employs zero people, so we're off the hook. + +#### There's extra provisions for sensitive data + +> Body measurements alone are not sensitive data + +The GDPR has extra provisions for *sensitive data* +such as biometric data, profiling, and a bunch of other stuff. + +This was cause for concern because we collect body measurements, and one of our questions was whether that qualifies as biometric data. + +Turns out it doesn't. Biometric data is what you can use to identify a person, like a fingerprint or iris scan. Body measurements alone are not sensitive data. + + +### Collecting data through consent + +To collect data, you need a so-called *lawful basis for data processing*. +There are different types, but the one that applies to us (and to most online services) is **consent**. + +In this scenario, your legal basis for processing the data is that you've asked the person to get their data +and they've freely given it to you. + +That is straight-forward, and makes sense. But the GDPR is really serious about making sure this consent is +freely given, and not wrestled from you grudgingly. + +To prevent companies from throwing up a big wall of legalese that people have to agree to, the GDPR outlines a number +of principles this consent should adhere to. Here's a non-exhaustive list: + + - people should have real choice and control + - consent requires a positive opt-in, pre-ticked boxes or anything like that are not allowed + - there should be a very clear statement explaining what people are agreeing to + - these requests for consent must be separate from any terms & conditions + - consent needs to be granular, you need individual consent for different things, and can't ask for blanket consent + - it must be easy for people to redraw consent + - consent of data processing should not be a precondition for a service + +Looking at that list, I can't help but feel that legislation would be a lot simpler if lawmakers could just write +*don't be a dick* and call it a day. + +#### Consent granularity + +Remember, we can't just get blanket consent. +We need to get consent for every type of data processing we do. + +For freesewing.org, we have identified three different types of data processing: + + - Profile data + - Model data + - Patron data + +For each of these, we'll need to get consent from the user, making sure it's *real consent* as intended in the GDPR. + +Below is a mockup for what this could look like for each data type: + +> ##### These mockups are no longer available +> +> Please note that the mockups originally included in this post are no longer +> available. Instead, this functionality has been implemented in the website. + +#### Consent timing + +The GDPR states that you should ask for consent when the data is collected. + +With our three types of data processing, that means that consent must be asked at different times: + + - **Profile data**: When signing up on the site + - **Model data**: When creating the first model + - **Patron data**: When becoming a patron + +This will (also) require some extra work to integrate this in the site. + +### Respecting basic rights when processing data + +The EU enshrines basic rights for its citizens that should be respected when processing data. + +Let's look at each of these rights and their impact on freesewing.org. + +#### The right to be informed + +> You need to be transparent about how you use personal data. Why you collect it, how you use it, and so on. + +Informing users is something we are still working on. If anything, this blog post is part of that effort. + +We will need to design the individual privacy notices, but also a more overall privacy policy as well as +making certain that users are informed of all their rights. + +While this will require some work, I don't expect any problems here. + +#### The right of access + +> People have the right to know their data is processed, and to access that data. + +We are already compliant, as all data users enter on the site can also be accessed by them. + +#### The right to rectification + +> People have the right to correct their data if it's not correct. + +We are already compliant, as all data users enter on the site can also be edited by them. + +#### The right to erasure + +> People have the right to have their data removed/erased. + +We are already compliant, as users can remove their models, or entire account at any time. + +#### The right to restrict processing + +This right means that users must be able to put a *freeze* on all data processing, without going as far as to delete their data. + +We do not currently offer this possibility, and will need to add this functionality to the site. + +#### The right to data portability + +> People not only have a right to export all their data, that export should also be in a format that makes it easy for them to take their data elsewhere. + +We are already compliant, as we allow users to export all of their data, and make it available in different standard formats (YAML and JSON). + +#### The right to object + +> The right to object applies specifically to: +> +> - processing for public interests or by official authorities +> - processing for direct marketing +> - processing for science/historic research/statistics +> +> In these cases, people can object to this specific processing. + +This is going to apply to us when we start publishing anonymized model data, something that's on our roadmap. + +The reason for publishing this data is that we want to make a dataset available of *real* body measurements, rather than the +*standard* measurements that are typically used in the industry. + +This is something we'll write about more at a later date, but essentially this falls under the *scientific research/statistics* category. +And even though the data is anonimized, we still need to respect the right of users to object to this processing. + +As such, we should add the possibility to object to this specific use of the data. + +#### Rights in relation to automated decision making and profiling + +> People have extra rights when it comes to profiling or decisions made by AI or algorithms without human involvement. + +This is not relevant in our situation. + +### Privacy by design + +The EU isn't content with throwing up a couple of consent questions and respecting people's rights when processing data. +It also wants to make certain that your privacy is (better) protected when things go wrong. + +That's why it advocates for *privacy by design*. While it's a concept that's hard to pin down in legislation, the +purpose is clear: They want everyone to consider privacy from the very start of their project/product/business, and +not as an afterthought. + +Things such as encryption (both in transit and for data at-rest), pseudonyms, and data expiry are suggested as +things to keep in mind while designing. + +Obviously, the EU is not going to come check your code to see whether you've taken privacy by design to heart. +But it can (and probably will) have an influence when things to wrong. + +Imagine two companies who have a data leak, one of them hasn't done much to safeguard the privacy of their users, +whereas the other has taken *privacy by design* measures to mitigate the damage. + +It seems obvious that the EU is going to come down harder on the company who didn't even try. + +#### What we're already doing + +We already do a number of things that are driven by a *privacy by design* approach. For example: + + - We use pseudonyms for user accounts + - We don't share any data with any third party + - We don't include any tracking code, or analytics + - We don't use cookies + - We don't have any social logins, like buttons, or other such things + - We don't run/show any ads + - We don't run any third-party JavaScript code + - We use encryption on all transport + +There's some more info on this in this blog post: +[The choices I've made to protect your privacy. Or why you won't be getting any cookies](/blog/privacy-choices/). + +These already form a very good basis for a privacy conscious website. But since we'll need to make changes +for GDPR anyway, we're considering other options to further raise the privacy bar. +Specifically, what can we do to limit the damage to our users in case there is a data leak. + +#### Restriction of data storage + +Some of the most sensitive data we store today is the address and birthday of our higher-tier patrons. + +However, the site does not need this information to function. We only need it for administrative purposes; +Sending out gifts and birthday cards to our patrons. + +As such, there's no real need to keep this data in the freesewing database. +We could just as well write this information down in a notebook we keep on our coffee table. + +So, as part of our GDPR-related changes, we will remove this information from the database, and store it +offline. + +#### Encryption of data at rest + +We already encrypt all data in transit. But, we are currently considering to add encryption of data at rest. + +The idea is to encrypt all data that could potentially identify a user. +Such as: + + - Email address + - User name + - Model names + - Model notes + +This would add an extra layer of defense for our users' privacy in case somehow our database gets dumped. + +While this change will be non-trivial to implement and come with a performance penalty, I feel it's +worth looking in to. + +## Conclusion + +While we still have some work to do, we are already compliant with large parts of the GDPR, especially when +it comes to respecting users rights: + + - The right to be informed + - The right of access + - The right to rectification + - The right to erasure + - The right to restrict processing + - The right to data portability + - The right to object + - Rights in relation to automated decision making and profiling + +We are currently working on *the right to be informed* and have a plan +for the changes required to respect *the right to restrict processing* and *the right to object*. + +On the data collection site, we need to hammer out the details for our privacy notices. +We'll also write a detailed privacy policy that bundles all the info from the different notices. + +We'll need to add changes to the user on-boarding to make sure notices are presented at the correct time. +Not to mention that we'll need to keep track of who gave their consent for what. + +### Action points + + - Draft privacy notices for profile/model/patron data + - Integrate consent in user on-boarding, model creation, and patron sign-up + - Make site functionality depend on consent + - Provide a centralized privacy dashboard where people can review their privacy settings/consent + - Add email notifications every time consent is changed + - Provide a way for people to *freeze* their account + - Provide a way for people to object to their model data being used for research and statistics + - Write and publish an overall privacy policy + - Encrypt sensitive data in the database + +Seems like we've got a lot of work ahead of us. + +### Feedback + +It is my personal opinion that the GDPR is a good thing. +But I want to hear from you about the changes outlined in this blog post. + +So please reach out with your feedback and comments. +It is after all your data we're talking about. + + diff --git a/markdown/org/blog/gdpr-ready/de.md b/markdown/org/blog/gdpr-ready/de.md new file mode 100644 index 00000000000..7ec74852ae6 --- /dev/null +++ b/markdown/org/blog/gdpr-ready/de.md @@ -0,0 +1,111 @@ +--- +author: "joostdecock" +caption: "The most important change is obviously that we moved from purple to black as our signature color" +date: "2018-05-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e67a17e37a70154b3bb250ea1cb60eff2baddb55-1920x1285.jpg" +intro: "Welcome to our new website. It's GDPR compliant, speaks 3 languages, and smells of wet paint [Nicht übersetzt]" +title: "Welcome to our new website. It's GDPR compliant, speaks 3 languages, and smells of wet paint [Nicht übersetzt]" +--- + + +Tomorrow, May 25th, the General Data Protection Regulation (GDPR) of the European Union (EU) comes into force. +From that day onward, businesses that don't respect the privacy of EU citizens +expose themselves to fines of up to 4% of their global annual turnover. + +The date marks nothing short of a watershed moment for online privacy, +as the world's most stringent data protection laws suddenly apply to half a billion people. + +## Your consent is now required + +For freesewing, the roll-out of GDPR doesn't pose a problem as such. +Not only did we have a solid plan, the only thing we absolutely had to add to the site was *consent*. +We are no longer allowed to process your data without your permission. +Permission that we should ask for both explicitly and granularly. + +So, we have two types of questions to ask you: + + - Do you give your consent to process your profile data? + - Do you give your consent to process your model data? + +We make the distinction because they are different things. +A profile/account is required to login to the site, post comments, and so on. +Model data is required to generate made-to-measure sewing patterns. + +You will be greeted by these questions when they are relevant +(as in, when we do need to access that specific data), +and you can revisit them at any time [in your account settings](/account). + +## It is our duty to inform you + +Under GDPR, we must inform you about how we handle privacy issues. +We have written about [our approach to privacy](/blog/privacy-choices) before, +but this requires something (a bit) more formal. + +So, we've drafted a [privacy notice](/privacy) that outlines all of these things. + +In addition to our privacy notice, we've setup [a page that lists all of your rights](/rights), +and explains how you can exercise them. + +With these changes, we've covered your right to be informed. + +## Privacy by design + +One of the more vague yet impactful requirements of GDPR is so-called *privacy-by-design*. +We took the advice to heart and have made two changes inspired by this: + + - Encryption of data at rest + - Termination of dormant accounts + +We now encrypt your profile data at rest. +In other words, our database holds your info, but it's encrypted. +We only decrypt it when we need it. + +We'll also terminate accounts that have been dormant for 12 months. +In other words, if you don't login on the website for 1 year, your account and all your data will be removed. + +However, for that last matter, there will be a bit of a grace period as we haven't fully implemented all the required changes yet. +Which brings me to my next point: + +## Also new: everything else + +These GDPR-related changes seemed like a good opportunity to re-vist some of the choices we've made, and see if there was room for improvement. +That was the initial idea anyway. In the end, we complete re-wrote the website from scratch. + +Our previous website used [Jekyll](https://jekyllrb.com/) as a static site generator, +with a pile of javascript code to make add the dynamic elements to the site. +While that did do the trick, there were two important downsides: + + - Jekyll uses the Ruby programming language. That's another programming language, another package manager, and another ecosystem that potential contributors have to wrap their heads around. We wanted to avoid that. + - That *pile* of JavaScript code was rather literal. Maintainability was starting to become an issue, not to mention that it would be difficult for new developers to jump in and understand what's going on. + +So, to kill two birds with one stone, we rewrote the entire site using [Vue.js](https://vuejs.org/) and [Nuxt](https://nuxtjs.org/). +Our entire frontend is written in JavaScript now — no more Ruby required — and due to Vue's modular nature and component-based approach, +it should be a lot easier to maintain. + +## Internationalization, aka i18n + +Obviously, as we were rewriting things, we've thrown in a couple of new features. +The most obvious being that we fully support i18n (internationalization) now. + +While translation is an ongoing endeavor, we've got everything in place to support it. +Starting today, freesewing is no longer exclusively available in English, but also in Dutch and Spanish. + +I'd like to thank [@AnnekeCaramin](/users/annekecaramin) +and [@AlfaLyr](/users/alfalyr), our language coordinators for Dutch and Spanish respectively, +but also all other people who have helped out with translating. + +An overview of the status of the different languages is available [here](/i18n), +and I'm hopeful that soon we'll be able to enable more languages. + +## Beware the wet paint + +Arguably, this release is a bit premature. +We've still have [a couple of open issue to fix](https://github.com/freesewing/site/issues), +and we're missing a bunch of documentation. + +However, since our deadline is externally imposed, we don't exactly have much choice in this. +That is, if we want to be fully compliant with GDPR, and we do. + +So, please bear with us as we continue to build this website, and our platform. +And don't hesitate to let us know when something goes wrong. + diff --git a/markdown/org/blog/gdpr-ready/en.md b/markdown/org/blog/gdpr-ready/en.md new file mode 100644 index 00000000000..8e83df8bcbb --- /dev/null +++ b/markdown/org/blog/gdpr-ready/en.md @@ -0,0 +1,111 @@ +--- +author: "joostdecock" +caption: "The most important change is obviously that we moved from purple to black as our signature color" +date: "2018-05-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e67a17e37a70154b3bb250ea1cb60eff2baddb55-1920x1285.jpg" +intro: "Welcome to our new website. It's GDPR compliant, speaks 3 languages, and smells of wet paint" +title: "Welcome to our new website. It's GDPR compliant, speaks 3 languages, and smells of wet paint" +--- + + +Tomorrow, May 25th, the General Data Protection Regulation (GDPR) of the European Union (EU) comes into force. +From that day onward, businesses that don't respect the privacy of EU citizens +expose themselves to fines of up to 4% of their global annual turnover. + +The date marks nothing short of a watershed moment for online privacy, +as the world's most stringent data protection laws suddenly apply to half a billion people. + +## Your consent is now required + +For freesewing, the roll-out of GDPR doesn't pose a problem as such. +Not only did we have a solid plan, the only thing we absolutely had to add to the site was *consent*. +We are no longer allowed to process your data without your permission. +Permission that we should ask for both explicitly and granularly. + +So, we have two types of questions to ask you: + + - Do you give your consent to process your profile data? + - Do you give your consent to process your model data? + +We make the distinction because they are different things. +A profile/account is required to login to the site, post comments, and so on. +Model data is required to generate made-to-measure sewing patterns. + +You will be greeted by these questions when they are relevant +(as in, when we do need to access that specific data), +and you can revisit them at any time [in your account settings](/account). + +## It is our duty to inform you + +Under GDPR, we must inform you about how we handle privacy issues. +We have written about [our approach to privacy](/blog/privacy-choices) before, +but this requires something (a bit) more formal. + +So, we've drafted a [privacy notice](/privacy) that outlines all of these things. + +In addition to our privacy notice, we've setup [a page that lists all of your rights](/rights), +and explains how you can exercise them. + +With these changes, we've covered your right to be informed. + +## Privacy by design + +One of the more vague yet impactful requirements of GDPR is so-called *privacy-by-design*. +We took the advice to heart and have made two changes inspired by this: + + - Encryption of data at rest + - Termination of dormant accounts + +We now encrypt your profile data at rest. +In other words, our database holds your info, but it's encrypted. +We only decrypt it when we need it. + +We'll also terminate accounts that have been dormant for 12 months. +In other words, if you don't login on the website for 1 year, your account and all your data will be removed. + +However, for that last matter, there will be a bit of a grace period as we haven't fully implemented all the required changes yet. +Which brings me to my next point: + +## Also new: everything else + +These GDPR-related changes seemed like a good opportunity to re-vist some of the choices we've made, and see if there was room for improvement. +That was the initial idea anyway. In the end, we complete re-wrote the website from scratch. + +Our previous website used [Jekyll](https://jekyllrb.com/) as a static site generator, +with a pile of javascript code to make add the dynamic elements to the site. +While that did do the trick, there were two important downsides: + + - Jekyll uses the Ruby programming language. That's another programming language, another package manager, and another ecosystem that potential contributors have to wrap their heads around. We wanted to avoid that. + - That *pile* of JavaScript code was rather literal. Maintainability was starting to become an issue, not to mention that it would be difficult for new developers to jump in and understand what's going on. + +So, to kill two birds with one stone, we rewrote the entire site using [Vue.js](https://vuejs.org/) and [Nuxt](https://nuxtjs.org/). +Our entire frontend is written in JavaScript now — no more Ruby required — and due to Vue's modular nature and component-based approach, +it should be a lot easier to maintain. + +## Internationalization, aka i18n + +Obviously, as we were rewriting things, we've thrown in a couple of new features. +The most obvious being that we fully support i18n (internationalization) now. + +While translation is an ongoing endeavor, we've got everything in place to support it. +Starting today, freesewing is no longer exclusively available in English, but also in Dutch and Spanish. + +I'd like to thank [@AnnekeCaramin](/users/annekecaramin) +and [@AlfaLyr](/users/alfalyr), our language coordinators for Dutch and Spanish respectively, +but also all other people who have helped out with translating. + +An overview of the status of the different languages is available [here](/i18n), +and I'm hopeful that soon we'll be able to enable more languages. + +## Beware the wet paint + +Arguably, this release is a bit premature. +We've still have [a couple of open issue to fix](https://github.com/freesewing/site/issues), +and we're missing a bunch of documentation. + +However, since our deadline is externally imposed, we don't exactly have much choice in this. +That is, if we want to be fully compliant with GDPR, and we do. + +So, please bear with us as we continue to build this website, and our platform. +And don't hesitate to let us know when something goes wrong. + diff --git a/markdown/org/blog/gdpr-ready/es.md b/markdown/org/blog/gdpr-ready/es.md new file mode 100644 index 00000000000..565c5fb5c6c --- /dev/null +++ b/markdown/org/blog/gdpr-ready/es.md @@ -0,0 +1,111 @@ +--- +author: "joostdecock" +caption: "The most important change is obviously that we moved from purple to black as our signature color" +date: "2018-05-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e67a17e37a70154b3bb250ea1cb60eff2baddb55-1920x1285.jpg" +intro: "Welcome to our new website. It's GDPR compliant, speaks 3 languages, and smells of wet paint [No traducido]" +title: "Welcome to our new website. It's GDPR compliant, speaks 3 languages, and smells of wet paint [No traducido]" +--- + + +Tomorrow, May 25th, the General Data Protection Regulation (GDPR) of the European Union (EU) comes into force. +From that day onward, businesses that don't respect the privacy of EU citizens +expose themselves to fines of up to 4% of their global annual turnover. + +The date marks nothing short of a watershed moment for online privacy, +as the world's most stringent data protection laws suddenly apply to half a billion people. + +## Your consent is now required + +For freesewing, the roll-out of GDPR doesn't pose a problem as such. +Not only did we have a solid plan, the only thing we absolutely had to add to the site was *consent*. +We are no longer allowed to process your data without your permission. +Permission that we should ask for both explicitly and granularly. + +So, we have two types of questions to ask you: + + - Do you give your consent to process your profile data? + - Do you give your consent to process your model data? + +We make the distinction because they are different things. +A profile/account is required to login to the site, post comments, and so on. +Model data is required to generate made-to-measure sewing patterns. + +You will be greeted by these questions when they are relevant +(as in, when we do need to access that specific data), +and you can revisit them at any time [in your account settings](/account). + +## It is our duty to inform you + +Under GDPR, we must inform you about how we handle privacy issues. +We have written about [our approach to privacy](/blog/privacy-choices) before, +but this requires something (a bit) more formal. + +So, we've drafted a [privacy notice](/privacy) that outlines all of these things. + +In addition to our privacy notice, we've setup [a page that lists all of your rights](/rights), +and explains how you can exercise them. + +With these changes, we've covered your right to be informed. + +## Privacy by design + +One of the more vague yet impactful requirements of GDPR is so-called *privacy-by-design*. +We took the advice to heart and have made two changes inspired by this: + + - Encryption of data at rest + - Termination of dormant accounts + +We now encrypt your profile data at rest. +In other words, our database holds your info, but it's encrypted. +We only decrypt it when we need it. + +We'll also terminate accounts that have been dormant for 12 months. +In other words, if you don't login on the website for 1 year, your account and all your data will be removed. + +However, for that last matter, there will be a bit of a grace period as we haven't fully implemented all the required changes yet. +Which brings me to my next point: + +## Also new: everything else + +These GDPR-related changes seemed like a good opportunity to re-vist some of the choices we've made, and see if there was room for improvement. +That was the initial idea anyway. In the end, we complete re-wrote the website from scratch. + +Our previous website used [Jekyll](https://jekyllrb.com/) as a static site generator, +with a pile of javascript code to make add the dynamic elements to the site. +While that did do the trick, there were two important downsides: + + - Jekyll uses the Ruby programming language. That's another programming language, another package manager, and another ecosystem that potential contributors have to wrap their heads around. We wanted to avoid that. + - That *pile* of JavaScript code was rather literal. Maintainability was starting to become an issue, not to mention that it would be difficult for new developers to jump in and understand what's going on. + +So, to kill two birds with one stone, we rewrote the entire site using [Vue.js](https://vuejs.org/) and [Nuxt](https://nuxtjs.org/). +Our entire frontend is written in JavaScript now — no more Ruby required — and due to Vue's modular nature and component-based approach, +it should be a lot easier to maintain. + +## Internationalization, aka i18n + +Obviously, as we were rewriting things, we've thrown in a couple of new features. +The most obvious being that we fully support i18n (internationalization) now. + +While translation is an ongoing endeavor, we've got everything in place to support it. +Starting today, freesewing is no longer exclusively available in English, but also in Dutch and Spanish. + +I'd like to thank [@AnnekeCaramin](/users/annekecaramin) +and [@AlfaLyr](/users/alfalyr), our language coordinators for Dutch and Spanish respectively, +but also all other people who have helped out with translating. + +An overview of the status of the different languages is available [here](/i18n), +and I'm hopeful that soon we'll be able to enable more languages. + +## Beware the wet paint + +Arguably, this release is a bit premature. +We've still have [a couple of open issue to fix](https://github.com/freesewing/site/issues), +and we're missing a bunch of documentation. + +However, since our deadline is externally imposed, we don't exactly have much choice in this. +That is, if we want to be fully compliant with GDPR, and we do. + +So, please bear with us as we continue to build this website, and our platform. +And don't hesitate to let us know when something goes wrong. + diff --git a/markdown/org/blog/gdpr-ready/fr.md b/markdown/org/blog/gdpr-ready/fr.md new file mode 100644 index 00000000000..d46cb53b1f4 --- /dev/null +++ b/markdown/org/blog/gdpr-ready/fr.md @@ -0,0 +1,111 @@ +--- +author: "joostdecock" +caption: "The most important change is obviously that we moved from purple to black as our signature color" +date: "2018-05-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e67a17e37a70154b3bb250ea1cb60eff2baddb55-1920x1285.jpg" +intro: "Welcome to our new website. It's GDPR compliant, speaks 3 languages, and smells of wet paint [Non traduit]" +title: "Welcome to our new website. It's GDPR compliant, speaks 3 languages, and smells of wet paint [Non traduit]" +--- + + +Tomorrow, May 25th, the General Data Protection Regulation (GDPR) of the European Union (EU) comes into force. +From that day onward, businesses that don't respect the privacy of EU citizens +expose themselves to fines of up to 4% of their global annual turnover. + +The date marks nothing short of a watershed moment for online privacy, +as the world's most stringent data protection laws suddenly apply to half a billion people. + +## Your consent is now required + +For freesewing, the roll-out of GDPR doesn't pose a problem as such. +Not only did we have a solid plan, the only thing we absolutely had to add to the site was *consent*. +We are no longer allowed to process your data without your permission. +Permission that we should ask for both explicitly and granularly. + +So, we have two types of questions to ask you: + + - Do you give your consent to process your profile data? + - Do you give your consent to process your model data? + +We make the distinction because they are different things. +A profile/account is required to login to the site, post comments, and so on. +Model data is required to generate made-to-measure sewing patterns. + +You will be greeted by these questions when they are relevant +(as in, when we do need to access that specific data), +and you can revisit them at any time [in your account settings](/account). + +## It is our duty to inform you + +Under GDPR, we must inform you about how we handle privacy issues. +We have written about [our approach to privacy](/blog/privacy-choices) before, +but this requires something (a bit) more formal. + +So, we've drafted a [privacy notice](/privacy) that outlines all of these things. + +In addition to our privacy notice, we've setup [a page that lists all of your rights](/rights), +and explains how you can exercise them. + +With these changes, we've covered your right to be informed. + +## Privacy by design + +One of the more vague yet impactful requirements of GDPR is so-called *privacy-by-design*. +We took the advice to heart and have made two changes inspired by this: + + - Encryption of data at rest + - Termination of dormant accounts + +We now encrypt your profile data at rest. +In other words, our database holds your info, but it's encrypted. +We only decrypt it when we need it. + +We'll also terminate accounts that have been dormant for 12 months. +In other words, if you don't login on the website for 1 year, your account and all your data will be removed. + +However, for that last matter, there will be a bit of a grace period as we haven't fully implemented all the required changes yet. +Which brings me to my next point: + +## Also new: everything else + +These GDPR-related changes seemed like a good opportunity to re-vist some of the choices we've made, and see if there was room for improvement. +That was the initial idea anyway. In the end, we complete re-wrote the website from scratch. + +Our previous website used [Jekyll](https://jekyllrb.com/) as a static site generator, +with a pile of javascript code to make add the dynamic elements to the site. +While that did do the trick, there were two important downsides: + + - Jekyll uses the Ruby programming language. That's another programming language, another package manager, and another ecosystem that potential contributors have to wrap their heads around. We wanted to avoid that. + - That *pile* of JavaScript code was rather literal. Maintainability was starting to become an issue, not to mention that it would be difficult for new developers to jump in and understand what's going on. + +So, to kill two birds with one stone, we rewrote the entire site using [Vue.js](https://vuejs.org/) and [Nuxt](https://nuxtjs.org/). +Our entire frontend is written in JavaScript now — no more Ruby required — and due to Vue's modular nature and component-based approach, +it should be a lot easier to maintain. + +## Internationalization, aka i18n + +Obviously, as we were rewriting things, we've thrown in a couple of new features. +The most obvious being that we fully support i18n (internationalization) now. + +While translation is an ongoing endeavor, we've got everything in place to support it. +Starting today, freesewing is no longer exclusively available in English, but also in Dutch and Spanish. + +I'd like to thank [@AnnekeCaramin](/users/annekecaramin) +and [@AlfaLyr](/users/alfalyr), our language coordinators for Dutch and Spanish respectively, +but also all other people who have helped out with translating. + +An overview of the status of the different languages is available [here](/i18n), +and I'm hopeful that soon we'll be able to enable more languages. + +## Beware the wet paint + +Arguably, this release is a bit premature. +We've still have [a couple of open issue to fix](https://github.com/freesewing/site/issues), +and we're missing a bunch of documentation. + +However, since our deadline is externally imposed, we don't exactly have much choice in this. +That is, if we want to be fully compliant with GDPR, and we do. + +So, please bear with us as we continue to build this website, and our platform. +And don't hesitate to let us know when something goes wrong. + diff --git a/markdown/org/blog/gdpr-ready/nl.md b/markdown/org/blog/gdpr-ready/nl.md new file mode 100644 index 00000000000..97277a51832 --- /dev/null +++ b/markdown/org/blog/gdpr-ready/nl.md @@ -0,0 +1,111 @@ +--- +author: "joostdecock" +caption: "The most important change is obviously that we moved from purple to black as our signature color" +date: "2018-05-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e67a17e37a70154b3bb250ea1cb60eff2baddb55-1920x1285.jpg" +intro: "Welcome to our new website. It's GDPR compliant, speaks 3 languages, and smells of wet paint [Niet vertaald]" +title: "Welcome to our new website. It's GDPR compliant, speaks 3 languages, and smells of wet paint [Niet vertaald]" +--- + + +Tomorrow, May 25th, the General Data Protection Regulation (GDPR) of the European Union (EU) comes into force. +From that day onward, businesses that don't respect the privacy of EU citizens +expose themselves to fines of up to 4% of their global annual turnover. + +The date marks nothing short of a watershed moment for online privacy, +as the world's most stringent data protection laws suddenly apply to half a billion people. + +## Your consent is now required + +For freesewing, the roll-out of GDPR doesn't pose a problem as such. +Not only did we have a solid plan, the only thing we absolutely had to add to the site was *consent*. +We are no longer allowed to process your data without your permission. +Permission that we should ask for both explicitly and granularly. + +So, we have two types of questions to ask you: + + - Do you give your consent to process your profile data? + - Do you give your consent to process your model data? + +We make the distinction because they are different things. +A profile/account is required to login to the site, post comments, and so on. +Model data is required to generate made-to-measure sewing patterns. + +You will be greeted by these questions when they are relevant +(as in, when we do need to access that specific data), +and you can revisit them at any time [in your account settings](/account). + +## It is our duty to inform you + +Under GDPR, we must inform you about how we handle privacy issues. +We have written about [our approach to privacy](/blog/privacy-choices) before, +but this requires something (a bit) more formal. + +So, we've drafted a [privacy notice](/privacy) that outlines all of these things. + +In addition to our privacy notice, we've setup [a page that lists all of your rights](/rights), +and explains how you can exercise them. + +With these changes, we've covered your right to be informed. + +## Privacy by design + +One of the more vague yet impactful requirements of GDPR is so-called *privacy-by-design*. +We took the advice to heart and have made two changes inspired by this: + + - Encryption of data at rest + - Termination of dormant accounts + +We now encrypt your profile data at rest. +In other words, our database holds your info, but it's encrypted. +We only decrypt it when we need it. + +We'll also terminate accounts that have been dormant for 12 months. +In other words, if you don't login on the website for 1 year, your account and all your data will be removed. + +However, for that last matter, there will be a bit of a grace period as we haven't fully implemented all the required changes yet. +Which brings me to my next point: + +## Also new: everything else + +These GDPR-related changes seemed like a good opportunity to re-vist some of the choices we've made, and see if there was room for improvement. +That was the initial idea anyway. In the end, we complete re-wrote the website from scratch. + +Our previous website used [Jekyll](https://jekyllrb.com/) as a static site generator, +with a pile of javascript code to make add the dynamic elements to the site. +While that did do the trick, there were two important downsides: + + - Jekyll uses the Ruby programming language. That's another programming language, another package manager, and another ecosystem that potential contributors have to wrap their heads around. We wanted to avoid that. + - That *pile* of JavaScript code was rather literal. Maintainability was starting to become an issue, not to mention that it would be difficult for new developers to jump in and understand what's going on. + +So, to kill two birds with one stone, we rewrote the entire site using [Vue.js](https://vuejs.org/) and [Nuxt](https://nuxtjs.org/). +Our entire frontend is written in JavaScript now — no more Ruby required — and due to Vue's modular nature and component-based approach, +it should be a lot easier to maintain. + +## Internationalization, aka i18n + +Obviously, as we were rewriting things, we've thrown in a couple of new features. +The most obvious being that we fully support i18n (internationalization) now. + +While translation is an ongoing endeavor, we've got everything in place to support it. +Starting today, freesewing is no longer exclusively available in English, but also in Dutch and Spanish. + +I'd like to thank [@AnnekeCaramin](/users/annekecaramin) +and [@AlfaLyr](/users/alfalyr), our language coordinators for Dutch and Spanish respectively, +but also all other people who have helped out with translating. + +An overview of the status of the different languages is available [here](/i18n), +and I'm hopeful that soon we'll be able to enable more languages. + +## Beware the wet paint + +Arguably, this release is a bit premature. +We've still have [a couple of open issue to fix](https://github.com/freesewing/site/issues), +and we're missing a bunch of documentation. + +However, since our deadline is externally imposed, we don't exactly have much choice in this. +That is, if we want to be fully compliant with GDPR, and we do. + +So, please bear with us as we continue to build this website, and our platform. +And don't hesitate to let us know when something goes wrong. + diff --git a/markdown/org/blog/halloween-cosplays-2021/de.md b/markdown/org/blog/halloween-cosplays-2021/de.md new file mode 100644 index 00000000000..9691b9a502e --- /dev/null +++ b/markdown/org/blog/halloween-cosplays-2021/de.md @@ -0,0 +1,147 @@ +--- +author: "joostdecock" +caption: "A bit cold perhaps, but swimtrunks: we've got'em" +date: "2021-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3a69586735a24a674d4e65971643b3b55c676fc3-1000x667.png" +intro: "Embodying your favourite character can make for a really fun Halloween experience! Here are some iconic characters to get you inspired." +title: "10 cosplays you can make from FreeSewing patterns to get you in the Halloween mood [Nicht übersetzt]" +--- + +Embodying your favourite character can make for a really fun Halloween experience! Here are some iconic characters to get you inspired. + +### Spongebob +Perhaps the most iconic character of them all, who doesn't know this yellow sponge? And his outfit is surprisingly stylish too! + +He wears a white dress shirt and brown pants, which can be created by [Simon](/designs/simon/) and a shortened [Charlie](/designs/charlie/) respectively, but you may already have this in your closet (saves time!). +A bright red [Trayvon](/designs/trayvon/) and a black belt would top it all off, or you can go even further by wearing shiny black shoes and white socks. + +![SpongeBob_stock_art.webp](https://posts.freesewing.org/uploads/Sponge_Bob_stock_art_ada2f4fd18.webp) + +![FreeSewing's Trayvon tie in a bright red](https://posts.freesewing.org/uploads/medium_spongebob_trayvon_e9729ec7ef.png) +![FreeSewing's Simon with shortened sleeves in white](https://posts.freesewing.org/uploads/medium_spongebob_simon_2327811c53.png) +![FreeSewing's Charlie, shortened and in brown](https://posts.freesewing.org/uploads/spongebob_charlie_fd09ebd233.png) + + +### Patrick +Where there is Spongebob, there is Patrick. Recreate his look with a pink [Teagan](/designs/teagan/) (or a pink shirt from your closet) and green [Shin swim trunks](/designs/shin/). +If you want to go even further, try to find fabric that resembles the pattern of his shorts, or paint the purple flowers on a pair of green shorts yourself! + +![A picture of Patrick Star](https://posts.freesewing.org/uploads/large_patrick_star_f206a40931.webp) + +![FreeSewing's Teagan tee in pink](https://posts.freesewing.org/uploads/medium_patrick_teagan_d32ebc17a2.png) +![FreeSewing's Shin swimtrunks in green and with purple blobs](https://posts.freesewing.org/uploads/small_patrick_shin_42e16e2342.png) + + +### Phineas and Ferb +Another iconic duo! Recreate Phineas' outfit with an orange striped [Teagan](/designs/teagan/) and pair it with short, blue cargo-like pants (or just dark jeans). +Bonus points if you have blue sneakers and maybe even (temporary) red hair dye. + +Ferb seems to be wearing a pastel yellow [Simon](/designs/simon/) with a white collar and buttons. He also wears very high-waisted purple pants, easy to recreate with an altered [Charlie](/designs/charlie/). +Aside from that, he wears black sneakers and... green hair. This is your time to go wild. + +![Phineas, Ferb and Perry surfing](https://posts.freesewing.org/uploads/phineas_ferb_45e5afda28.webp) + +![FreeSewing's Charlie chino's in a deep purple](https://posts.freesewing.org/uploads/medium_ferb_charlie_51ced3ff7e.png) +![FreeSewing's Simon shirt in pastel yellow with short sleeves and a white collar and buttons.](https://posts.freesewing.org/uploads/medium_ferb_simon_d87b96bc1d.png) +![FreeSewing's Teagan tee in yellow with orange stripes](https://posts.freesewing.org/uploads/medium_phineas_teagan_62d98938ee.png) + + +### Ash from Pokémon +The main character from the beloved Pokémon series! Although his look has changed many times over the last 20 years, there are still ways to embody him. + +He generally wears light denim jeans and his iconic red hat. We currently do not have patterns for either of these, but we do have patterns for the jackets he wears! + +To create his original outfit, wear a blue [Simon](/designs/simon/) with short white sleeves and a white collar, with yellow top buttons. +This jacket seems to have yellow pockets, but sewing yellow stripes on it will also do the trick. +(P.S. This jacket is not really a Simon, but it's the closest we have.) +If you really want to go all the way, the bottom of his jacket has a yellow line and he wears green fingerless gloves. He wears a dark green or black shirt under this, or use [Teagan](/designs/teagan/) if you don't have one. + +If that's a bit much, any bright blue jacket will recreate his vibe. + Add yellow accessories to get more into it. If that's too simple, he also wears a t-shirt ([Teagan](/designs/teagan/) would be great here, too!) in the Sun and Moon series. Forget the jeans for this one; he pairs this with shortened [Pacos](/designs/paco/) that have red ribbing. + +![Character Ash from the Pokémon series](https://posts.freesewing.org/uploads/medium_ash_8f9cbfb8f2.jpg) + +![FreeSewing's Simon shirt altered to mirror the shirt from the character Ash](https://posts.freesewing.org/uploads/medium_ash_simon_74ef670561.png) + +(Hint: in our other Halloween blogpost, we have ideas for turning Huey and Hugo into Pokémon hoodies!) + + +### The PowerPuff girls +This is a perfect cosplay for a group of three! Choose your favourite body block and pair it with a [Sandy](/designs/sandy/). +Find a large black belt or simply sew a black stripe on the block. You can turn this into a dress, but that's not mandatory. +The three also wear white tights and black shoes. For Blossom (the pink one), you can use [Benjamin](/designs/benjamin/) to create her bow. +Bonus points if you get their hairstyles right too. + +![The three PowerPuff girls flying](https://posts.freesewing.org/uploads/powerpuff_girls_3231f9ec09.webp) + +### Dora +Dora! Iconic and quite easy to replicate. +She wears a cropped pink shirt (cropped Teagan!) and short orange pants, which can be created by making shortened [Pacos](/designs/pacos/) or a [Charlie](/designs/charlie/). +She wears yellow socks, a yellow beaded bracelet, with white or pink shoes. Her purple bag may perhaps be the hardest thing to find. + +![The character Dora](https://posts.freesewing.org/uploads/medium_Dora_0eeb97b52f.webp) + +![FreeSewing's Teagan tee in pink](https://posts.freesewing.org/uploads/medium_dora_teagan_e6e26c630c.png) +![FreeSewing's Charlie chinos but orange and shortened](https://posts.freesewing.org/uploads/dora_charlie_6241e9dd2b.png) + +Now, you may have been wondering if this whole list is going to be children's characters. Don't panic! It's time for more mature characters. + +### Soldier: 76's summer skin +The stoic soldier from the game Overwatch, and his outfits are more fun than you'd think. +His summer skin makes for an awesome casual outfit too. + +The blue apron is arguably the most important part of this, and also the hardest part to get right. +His apron has a lot of pockets. You can start with [Albert](/designs/albert/) and just add a bunch of pockets. +If you make it from cotton, you can write the text on it with fabric dye. + +He also wears a red Hawaiian shirt, which can be replicated with a [Simon](/designs/simon/) with short sleeves, from a red flowery pattern. +He wears brown pants underneath it, which can be replicated with a shortened [Charlie](/designs/charlie/). + +This person even made the apron from leather! The owner commissioned it from [Knotted Bone Leather Works](https://www.knottedboneleatherworks.com/). + +![The character Soldier: 76 in his summer skin](https://posts.freesewing.org/uploads/medium_soldier76summer_7a8260726d.jpg) + +![The Soldier:76 Summer skin's apron from leather](https://posts.freesewing.org/uploads/small_soldier76cosplay_06df3b891c.webp) + + +### Sherlock Holmes +Well, it would almost be a crime if we didn't include this character, as we have patterns inspired by his show! +Wear a dark navy or black [Carlton](/designs/carlton/)/[Carlita](/designs/carlita/) (shocker, I know) and under that wear all-black clothes, or a white dress shirt instead of something black. +To really get the look, wear a desaturated blue scarf and make our [Holmes hat](/designs/holmes/) from a gray fabric ("herringbone") and with a dark brown ribbon. + +![Sherlock Holmes from the TV series](https://posts.freesewing.org/uploads/medium_sherlock_holmes_hat_de80125cd1.webp) +![bc.jpg](https://posts.freesewing.org/uploads/medium_bc_f20e01a16d.jpg) + + +### Janet from The Good Place +Janet, our favourite non-human (slightly human) assistant. +This entry wouldn't be here if not for [Natalia](https://freesewing.org/makers/nataliasayang/)! +She cosplayed this character last year and it looks awesome. +If you'd want to create Janet's look with FreeSewing patterns: make a [Wahid](/designs/wahid/) and [Sandy](/designs/sandy/), both from a deep purple fabric, and pair it with a long-sleeved shirt made from an (optionally translucent) blue flowered fabric. +Janet's shirt has a lot of flair that we don't have features for, but you can manually add these things. + +![Janet from The Good Place](https://posts.freesewing.org/uploads/medium_janet_7985d4b2af.jpg) +![Janet cosplay by Natalia Sayang](https://posts.freesewing.org/uploads/medium_janet_costume_2114092e9a.jpg) + + +### Hatsune Miku +Yes.... She counts as a mature character, although her looks may give the impression that she's popular with children. +But, this vocaloid (the product of a voice synthesizer software) has many fans and has even had real-life concerts! (Crazy for a fictional character!) + +Anyways, to create her look, you'll need a gray [Wahid](/designs/wahid/), optionally with blue lines, and a blue [Trayvon](/designs/trayvon/) tie. +She also wears a black pleated knife skirt, with a blue line, but erm... This pattern does not *yet* exist. +She wears black tights (again with a blue stripe!) with black shoes. + +She wears huge sleeves that aren't attached to her top; you can simply grab Sven and only take the sleeves, cut a bit off the top of the sleeve and add an elastic band there, and make the rest of the sleeve get wider and wider. Again there's the option to add a blue line. + +Bonus points if you can find a wig for her iconic blue pigtails, but if you have long hair you can also get the vibe by recreating her hairstyle with your own hair. + +![The vocaloid Hatsune Miku](https://posts.freesewing.org/uploads/medium_hatsune_miku_43ccad726b.jpg) + +![FreeSewing's Wahid waistcoat in gray](https://posts.freesewing.org/uploads/medium_miku_wahid_2dce7835cc.png) +![FreeSewing's Trayvon tie in blue](https://posts.freesewing.org/uploads/medium_miku_trayvon_a204b6499f.png) + + +Hopefully we inspired you and happy halloween! 🎃 + +> *This was a collaboration between bobgeorgethethird and lucibytes!* diff --git a/markdown/org/blog/halloween-cosplays-2021/en.md b/markdown/org/blog/halloween-cosplays-2021/en.md new file mode 100644 index 00000000000..ea3a5896f0d --- /dev/null +++ b/markdown/org/blog/halloween-cosplays-2021/en.md @@ -0,0 +1,147 @@ +--- +author: "joostdecock" +caption: "A bit cold perhaps, but swimtrunks: we've got'em" +date: "2021-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3a69586735a24a674d4e65971643b3b55c676fc3-1000x667.png" +intro: "Embodying your favourite character can make for a really fun Halloween experience! Here are some iconic characters to get you inspired." +title: "10 cosplays you can make from FreeSewing patterns to get you in the Halloween mood" +--- + +Embodying your favourite character can make for a really fun Halloween experience! Here are some iconic characters to get you inspired. + +### Spongebob +Perhaps the most iconic character of them all, who doesn't know this yellow sponge? And his outfit is surprisingly stylish too! + +He wears a white dress shirt and brown pants, which can be created by [Simon](/designs/simon/) and a shortened [Charlie](/designs/charlie/) respectively, but you may already have this in your closet (saves time!). +A bright red [Trayvon](/designs/trayvon/) and a black belt would top it all off, or you can go even further by wearing shiny black shoes and white socks. + +![SpongeBob_stock_art.webp](https://posts.freesewing.org/uploads/Sponge_Bob_stock_art_ada2f4fd18.webp) + +![FreeSewing's Trayvon tie in a bright red](https://posts.freesewing.org/uploads/medium_spongebob_trayvon_e9729ec7ef.png) +![FreeSewing's Simon with shortened sleeves in white](https://posts.freesewing.org/uploads/medium_spongebob_simon_2327811c53.png) +![FreeSewing's Charlie, shortened and in brown](https://posts.freesewing.org/uploads/spongebob_charlie_fd09ebd233.png) + + +### Patrick +Where there is Spongebob, there is Patrick. Recreate his look with a pink [Teagan](/designs/teagan/) (or a pink shirt from your closet) and green [Shin swim trunks](/designs/shin/). +If you want to go even further, try to find fabric that resembles the pattern of his shorts, or paint the purple flowers on a pair of green shorts yourself! + +![A picture of Patrick Star](https://posts.freesewing.org/uploads/large_patrick_star_f206a40931.webp) + +![FreeSewing's Teagan tee in pink](https://posts.freesewing.org/uploads/medium_patrick_teagan_d32ebc17a2.png) +![FreeSewing's Shin swimtrunks in green and with purple blobs](https://posts.freesewing.org/uploads/small_patrick_shin_42e16e2342.png) + + +### Phineas and Ferb +Another iconic duo! Recreate Phineas' outfit with an orange striped [Teagan](/designs/teagan/) and pair it with short, blue cargo-like pants (or just dark jeans). +Bonus points if you have blue sneakers and maybe even (temporary) red hair dye. + +Ferb seems to be wearing a pastel yellow [Simon](/designs/simon/) with a white collar and buttons. He also wears very high-waisted purple pants, easy to recreate with an altered [Charlie](/designs/charlie/). +Aside from that, he wears black sneakers and... green hair. This is your time to go wild. + +![Phineas, Ferb and Perry surfing](https://posts.freesewing.org/uploads/phineas_ferb_45e5afda28.webp) + +![FreeSewing's Charlie chino's in a deep purple](https://posts.freesewing.org/uploads/medium_ferb_charlie_51ced3ff7e.png) +![FreeSewing's Simon shirt in pastel yellow with short sleeves and a white collar and buttons.](https://posts.freesewing.org/uploads/medium_ferb_simon_d87b96bc1d.png) +![FreeSewing's Teagan tee in yellow with orange stripes](https://posts.freesewing.org/uploads/medium_phineas_teagan_62d98938ee.png) + + +### Ash from Pokémon +The main character from the beloved Pokémon series! Although his look has changed many times over the last 20 years, there are still ways to embody him. + +He generally wears light denim jeans and his iconic red hat. We currently do not have patterns for either of these, but we do have patterns for the jackets he wears! + +To create his original outfit, wear a blue [Simon](/designs/simon/) with short white sleeves and a white collar, with yellow top buttons. +This jacket seems to have yellow pockets, but sewing yellow stripes on it will also do the trick. +(P.S. This jacket is not really a Simon, but it's the closest we have.) +If you really want to go all the way, the bottom of his jacket has a yellow line and he wears green fingerless gloves. He wears a dark green or black shirt under this, or use [Teagan](/designs/teagan/) if you don't have one. + +If that's a bit much, any bright blue jacket will recreate his vibe. + Add yellow accessories to get more into it. If that's too simple, he also wears a t-shirt ([Teagan](/designs/teagan/) would be great here, too!) in the Sun and Moon series. Forget the jeans for this one; he pairs this with shortened [Pacos](/designs/paco/) that have red ribbing. + +![Character Ash from the Pokémon series](https://posts.freesewing.org/uploads/medium_ash_8f9cbfb8f2.jpg) + +![FreeSewing's Simon shirt altered to mirror the shirt from the character Ash](https://posts.freesewing.org/uploads/medium_ash_simon_74ef670561.png) + +(Hint: in our other Halloween blogpost, we have ideas for turning Huey and Hugo into Pokémon hoodies!) + + +### The PowerPuff girls +This is a perfect cosplay for a group of three! Choose your favourite body block and pair it with a [Sandy](/designs/sandy/). +Find a large black belt or simply sew a black stripe on the block. You can turn this into a dress, but that's not mandatory. +The three also wear white tights and black shoes. For Blossom (the pink one), you can use [Benjamin](/designs/benjamin/) to create her bow. +Bonus points if you get their hairstyles right too. + +![The three PowerPuff girls flying](https://posts.freesewing.org/uploads/powerpuff_girls_3231f9ec09.webp) + +### Dora +Dora! Iconic and quite easy to replicate. +She wears a cropped pink shirt (cropped Teagan!) and short orange pants, which can be created by making shortened [Pacos](/designs/pacos/) or a [Charlie](/designs/charlie/). +She wears yellow socks, a yellow beaded bracelet, with white or pink shoes. Her purple bag may perhaps be the hardest thing to find. + +![The character Dora](https://posts.freesewing.org/uploads/medium_Dora_0eeb97b52f.webp) + +![FreeSewing's Teagan tee in pink](https://posts.freesewing.org/uploads/medium_dora_teagan_e6e26c630c.png) +![FreeSewing's Charlie chinos but orange and shortened](https://posts.freesewing.org/uploads/dora_charlie_6241e9dd2b.png) + +Now, you may have been wondering if this whole list is going to be children's characters. Don't panic! It's time for more mature characters. + +### Soldier: 76's summer skin +The stoic soldier from the game Overwatch, and his outfits are more fun than you'd think. +His summer skin makes for an awesome casual outfit too. + +The blue apron is arguably the most important part of this, and also the hardest part to get right. +His apron has a lot of pockets. You can start with [Albert](/designs/albert/) and just add a bunch of pockets. +If you make it from cotton, you can write the text on it with fabric dye. + +He also wears a red Hawaiian shirt, which can be replicated with a [Simon](/designs/simon/) with short sleeves, from a red flowery pattern. +He wears brown pants underneath it, which can be replicated with a shortened [Charlie](/designs/charlie/). + +This person even made the apron from leather! The owner commissioned it from [Knotted Bone Leather Works](https://www.knottedboneleatherworks.com/). + +![The character Soldier: 76 in his summer skin](https://posts.freesewing.org/uploads/medium_soldier76summer_7a8260726d.jpg) + +![The Soldier:76 Summer skin's apron from leather](https://posts.freesewing.org/uploads/small_soldier76cosplay_06df3b891c.webp) + + +### Sherlock Holmes +Well, it would almost be a crime if we didn't include this character, as we have patterns inspired by his show! +Wear a dark navy or black [Carlton](/designs/carlton/)/[Carlita](/designs/carlita/) (shocker, I know) and under that wear all-black clothes, or a white dress shirt instead of something black. +To really get the look, wear a desaturated blue scarf and make our [Holmes hat](/designs/holmes/) from a gray fabric ("herringbone") and with a dark brown ribbon. + +![Sherlock Holmes from the TV series](https://posts.freesewing.org/uploads/medium_sherlock_holmes_hat_de80125cd1.webp) +![bc.jpg](https://posts.freesewing.org/uploads/medium_bc_f20e01a16d.jpg) + + +### Janet from The Good Place +Janet, our favourite non-human (slightly human) assistant. +This entry wouldn't be here if not for [Natalia](https://freesewing.org/makers/nataliasayang/)! +She cosplayed this character last year and it looks awesome. +If you'd want to create Janet's look with FreeSewing patterns: make a [Wahid](/designs/wahid/) and [Sandy](/designs/sandy/), both from a deep purple fabric, and pair it with a long-sleeved shirt made from an (optionally translucent) blue flowered fabric. +Janet's shirt has a lot of flair that we don't have features for, but you can manually add these things. + +![Janet from The Good Place](https://posts.freesewing.org/uploads/medium_janet_7985d4b2af.jpg) +![Janet cosplay by Natalia Sayang](https://posts.freesewing.org/uploads/medium_janet_costume_2114092e9a.jpg) + + +### Hatsune Miku +Yes.... She counts as a mature character, although her looks may give the impression that she's popular with children. +But, this vocaloid (the product of a voice synthesizer software) has many fans and has even had real-life concerts! (Crazy for a fictional character!) + +Anyways, to create her look, you'll need a gray [Wahid](/designs/wahid/), optionally with blue lines, and a blue [Trayvon](/designs/trayvon/) tie. +She also wears a black pleated knife skirt, with a blue line, but erm... This pattern does not *yet* exist. +She wears black tights (again with a blue stripe!) with black shoes. + +She wears huge sleeves that aren't attached to her top; you can simply grab Sven and only take the sleeves, cut a bit off the top of the sleeve and add an elastic band there, and make the rest of the sleeve get wider and wider. Again there's the option to add a blue line. + +Bonus points if you can find a wig for her iconic blue pigtails, but if you have long hair you can also get the vibe by recreating her hairstyle with your own hair. + +![The vocaloid Hatsune Miku](https://posts.freesewing.org/uploads/medium_hatsune_miku_43ccad726b.jpg) + +![FreeSewing's Wahid waistcoat in gray](https://posts.freesewing.org/uploads/medium_miku_wahid_2dce7835cc.png) +![FreeSewing's Trayvon tie in blue](https://posts.freesewing.org/uploads/medium_miku_trayvon_a204b6499f.png) + + +Hopefully we inspired you and happy halloween! 🎃 + +> *This was a collaboration between bobgeorgethethird and lucibytes!* diff --git a/markdown/org/blog/halloween-cosplays-2021/es.md b/markdown/org/blog/halloween-cosplays-2021/es.md new file mode 100644 index 00000000000..29af22d9907 --- /dev/null +++ b/markdown/org/blog/halloween-cosplays-2021/es.md @@ -0,0 +1,147 @@ +--- +author: "joostdecock" +caption: "A bit cold perhaps, but swimtrunks: we've got'em" +date: "2021-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3a69586735a24a674d4e65971643b3b55c676fc3-1000x667.png" +intro: "Embodying your favourite character can make for a really fun Halloween experience! Here are some iconic characters to get you inspired." +title: "10 cosplays you can make from FreeSewing patterns to get you in the Halloween mood [No traducido]" +--- + +Embodying your favourite character can make for a really fun Halloween experience! Here are some iconic characters to get you inspired. + +### Spongebob +Perhaps the most iconic character of them all, who doesn't know this yellow sponge? And his outfit is surprisingly stylish too! + +He wears a white dress shirt and brown pants, which can be created by [Simon](/designs/simon/) and a shortened [Charlie](/designs/charlie/) respectively, but you may already have this in your closet (saves time!). +A bright red [Trayvon](/designs/trayvon/) and a black belt would top it all off, or you can go even further by wearing shiny black shoes and white socks. + +![SpongeBob_stock_art.webp](https://posts.freesewing.org/uploads/Sponge_Bob_stock_art_ada2f4fd18.webp) + +![FreeSewing's Trayvon tie in a bright red](https://posts.freesewing.org/uploads/medium_spongebob_trayvon_e9729ec7ef.png) +![FreeSewing's Simon with shortened sleeves in white](https://posts.freesewing.org/uploads/medium_spongebob_simon_2327811c53.png) +![FreeSewing's Charlie, shortened and in brown](https://posts.freesewing.org/uploads/spongebob_charlie_fd09ebd233.png) + + +### Patrick +Where there is Spongebob, there is Patrick. Recreate his look with a pink [Teagan](/designs/teagan/) (or a pink shirt from your closet) and green [Shin swim trunks](/designs/shin/). +If you want to go even further, try to find fabric that resembles the pattern of his shorts, or paint the purple flowers on a pair of green shorts yourself! + +![A picture of Patrick Star](https://posts.freesewing.org/uploads/large_patrick_star_f206a40931.webp) + +![FreeSewing's Teagan tee in pink](https://posts.freesewing.org/uploads/medium_patrick_teagan_d32ebc17a2.png) +![FreeSewing's Shin swimtrunks in green and with purple blobs](https://posts.freesewing.org/uploads/small_patrick_shin_42e16e2342.png) + + +### Phineas and Ferb +Another iconic duo! Recreate Phineas' outfit with an orange striped [Teagan](/designs/teagan/) and pair it with short, blue cargo-like pants (or just dark jeans). +Bonus points if you have blue sneakers and maybe even (temporary) red hair dye. + +Ferb seems to be wearing a pastel yellow [Simon](/designs/simon/) with a white collar and buttons. He also wears very high-waisted purple pants, easy to recreate with an altered [Charlie](/designs/charlie/). +Aside from that, he wears black sneakers and... green hair. This is your time to go wild. + +![Phineas, Ferb and Perry surfing](https://posts.freesewing.org/uploads/phineas_ferb_45e5afda28.webp) + +![FreeSewing's Charlie chino's in a deep purple](https://posts.freesewing.org/uploads/medium_ferb_charlie_51ced3ff7e.png) +![FreeSewing's Simon shirt in pastel yellow with short sleeves and a white collar and buttons.](https://posts.freesewing.org/uploads/medium_ferb_simon_d87b96bc1d.png) +![FreeSewing's Teagan tee in yellow with orange stripes](https://posts.freesewing.org/uploads/medium_phineas_teagan_62d98938ee.png) + + +### Ash from Pokémon +The main character from the beloved Pokémon series! Although his look has changed many times over the last 20 years, there are still ways to embody him. + +He generally wears light denim jeans and his iconic red hat. We currently do not have patterns for either of these, but we do have patterns for the jackets he wears! + +To create his original outfit, wear a blue [Simon](/designs/simon/) with short white sleeves and a white collar, with yellow top buttons. +This jacket seems to have yellow pockets, but sewing yellow stripes on it will also do the trick. +(P.S. This jacket is not really a Simon, but it's the closest we have.) +If you really want to go all the way, the bottom of his jacket has a yellow line and he wears green fingerless gloves. He wears a dark green or black shirt under this, or use [Teagan](/designs/teagan/) if you don't have one. + +If that's a bit much, any bright blue jacket will recreate his vibe. + Add yellow accessories to get more into it. If that's too simple, he also wears a t-shirt ([Teagan](/designs/teagan/) would be great here, too!) in the Sun and Moon series. Forget the jeans for this one; he pairs this with shortened [Pacos](/designs/paco/) that have red ribbing. + +![Character Ash from the Pokémon series](https://posts.freesewing.org/uploads/medium_ash_8f9cbfb8f2.jpg) + +![FreeSewing's Simon shirt altered to mirror the shirt from the character Ash](https://posts.freesewing.org/uploads/medium_ash_simon_74ef670561.png) + +(Hint: in our other Halloween blogpost, we have ideas for turning Huey and Hugo into Pokémon hoodies!) + + +### The PowerPuff girls +This is a perfect cosplay for a group of three! Choose your favourite body block and pair it with a [Sandy](/designs/sandy/). +Find a large black belt or simply sew a black stripe on the block. You can turn this into a dress, but that's not mandatory. +The three also wear white tights and black shoes. For Blossom (the pink one), you can use [Benjamin](/designs/benjamin/) to create her bow. +Bonus points if you get their hairstyles right too. + +![The three PowerPuff girls flying](https://posts.freesewing.org/uploads/powerpuff_girls_3231f9ec09.webp) + +### Dora +Dora! Iconic and quite easy to replicate. +She wears a cropped pink shirt (cropped Teagan!) and short orange pants, which can be created by making shortened [Pacos](/designs/pacos/) or a [Charlie](/designs/charlie/). +She wears yellow socks, a yellow beaded bracelet, with white or pink shoes. Her purple bag may perhaps be the hardest thing to find. + +![The character Dora](https://posts.freesewing.org/uploads/medium_Dora_0eeb97b52f.webp) + +![FreeSewing's Teagan tee in pink](https://posts.freesewing.org/uploads/medium_dora_teagan_e6e26c630c.png) +![FreeSewing's Charlie chinos but orange and shortened](https://posts.freesewing.org/uploads/dora_charlie_6241e9dd2b.png) + +Now, you may have been wondering if this whole list is going to be children's characters. Don't panic! It's time for more mature characters. + +### Soldier: 76's summer skin +The stoic soldier from the game Overwatch, and his outfits are more fun than you'd think. +His summer skin makes for an awesome casual outfit too. + +The blue apron is arguably the most important part of this, and also the hardest part to get right. +His apron has a lot of pockets. You can start with [Albert](/designs/albert/) and just add a bunch of pockets. +If you make it from cotton, you can write the text on it with fabric dye. + +He also wears a red Hawaiian shirt, which can be replicated with a [Simon](/designs/simon/) with short sleeves, from a red flowery pattern. +He wears brown pants underneath it, which can be replicated with a shortened [Charlie](/designs/charlie/). + +This person even made the apron from leather! The owner commissioned it from [Knotted Bone Leather Works](https://www.knottedboneleatherworks.com/). + +![The character Soldier: 76 in his summer skin](https://posts.freesewing.org/uploads/medium_soldier76summer_7a8260726d.jpg) + +![The Soldier:76 Summer skin's apron from leather](https://posts.freesewing.org/uploads/small_soldier76cosplay_06df3b891c.webp) + + +### Sherlock Holmes +Well, it would almost be a crime if we didn't include this character, as we have patterns inspired by his show! +Wear a dark navy or black [Carlton](/designs/carlton/)/[Carlita](/designs/carlita/) (shocker, I know) and under that wear all-black clothes, or a white dress shirt instead of something black. +To really get the look, wear a desaturated blue scarf and make our [Holmes hat](/designs/holmes/) from a gray fabric ("herringbone") and with a dark brown ribbon. + +![Sherlock Holmes from the TV series](https://posts.freesewing.org/uploads/medium_sherlock_holmes_hat_de80125cd1.webp) +![bc.jpg](https://posts.freesewing.org/uploads/medium_bc_f20e01a16d.jpg) + + +### Janet from The Good Place +Janet, our favourite non-human (slightly human) assistant. +This entry wouldn't be here if not for [Natalia](https://freesewing.org/makers/nataliasayang/)! +She cosplayed this character last year and it looks awesome. +If you'd want to create Janet's look with FreeSewing patterns: make a [Wahid](/designs/wahid/) and [Sandy](/designs/sandy/), both from a deep purple fabric, and pair it with a long-sleeved shirt made from an (optionally translucent) blue flowered fabric. +Janet's shirt has a lot of flair that we don't have features for, but you can manually add these things. + +![Janet from The Good Place](https://posts.freesewing.org/uploads/medium_janet_7985d4b2af.jpg) +![Janet cosplay by Natalia Sayang](https://posts.freesewing.org/uploads/medium_janet_costume_2114092e9a.jpg) + + +### Hatsune Miku +Yes.... She counts as a mature character, although her looks may give the impression that she's popular with children. +But, this vocaloid (the product of a voice synthesizer software) has many fans and has even had real-life concerts! (Crazy for a fictional character!) + +Anyways, to create her look, you'll need a gray [Wahid](/designs/wahid/), optionally with blue lines, and a blue [Trayvon](/designs/trayvon/) tie. +She also wears a black pleated knife skirt, with a blue line, but erm... This pattern does not *yet* exist. +She wears black tights (again with a blue stripe!) with black shoes. + +She wears huge sleeves that aren't attached to her top; you can simply grab Sven and only take the sleeves, cut a bit off the top of the sleeve and add an elastic band there, and make the rest of the sleeve get wider and wider. Again there's the option to add a blue line. + +Bonus points if you can find a wig for her iconic blue pigtails, but if you have long hair you can also get the vibe by recreating her hairstyle with your own hair. + +![The vocaloid Hatsune Miku](https://posts.freesewing.org/uploads/medium_hatsune_miku_43ccad726b.jpg) + +![FreeSewing's Wahid waistcoat in gray](https://posts.freesewing.org/uploads/medium_miku_wahid_2dce7835cc.png) +![FreeSewing's Trayvon tie in blue](https://posts.freesewing.org/uploads/medium_miku_trayvon_a204b6499f.png) + + +Hopefully we inspired you and happy halloween! 🎃 + +> *This was a collaboration between bobgeorgethethird and lucibytes!* diff --git a/markdown/org/blog/halloween-cosplays-2021/fr.md b/markdown/org/blog/halloween-cosplays-2021/fr.md new file mode 100644 index 00000000000..450ef33e7d3 --- /dev/null +++ b/markdown/org/blog/halloween-cosplays-2021/fr.md @@ -0,0 +1,147 @@ +--- +author: "joostdecock" +caption: "A bit cold perhaps, but swimtrunks: we've got'em" +date: "2021-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3a69586735a24a674d4e65971643b3b55c676fc3-1000x667.png" +intro: "Embodying your favourite character can make for a really fun Halloween experience! Here are some iconic characters to get you inspired." +title: "10 cosplays you can make from FreeSewing patterns to get you in the Halloween mood [Non traduit]" +--- + +Embodying your favourite character can make for a really fun Halloween experience! Here are some iconic characters to get you inspired. + +### Spongebob +Perhaps the most iconic character of them all, who doesn't know this yellow sponge? And his outfit is surprisingly stylish too! + +He wears a white dress shirt and brown pants, which can be created by [Simon](/designs/simon/) and a shortened [Charlie](/designs/charlie/) respectively, but you may already have this in your closet (saves time!). +A bright red [Trayvon](/designs/trayvon/) and a black belt would top it all off, or you can go even further by wearing shiny black shoes and white socks. + +![SpongeBob_stock_art.webp](https://posts.freesewing.org/uploads/Sponge_Bob_stock_art_ada2f4fd18.webp) + +![FreeSewing's Trayvon tie in a bright red](https://posts.freesewing.org/uploads/medium_spongebob_trayvon_e9729ec7ef.png) +![FreeSewing's Simon with shortened sleeves in white](https://posts.freesewing.org/uploads/medium_spongebob_simon_2327811c53.png) +![FreeSewing's Charlie, shortened and in brown](https://posts.freesewing.org/uploads/spongebob_charlie_fd09ebd233.png) + + +### Patrick +Where there is Spongebob, there is Patrick. Recreate his look with a pink [Teagan](/designs/teagan/) (or a pink shirt from your closet) and green [Shin swim trunks](/designs/shin/). +If you want to go even further, try to find fabric that resembles the pattern of his shorts, or paint the purple flowers on a pair of green shorts yourself! + +![A picture of Patrick Star](https://posts.freesewing.org/uploads/large_patrick_star_f206a40931.webp) + +![FreeSewing's Teagan tee in pink](https://posts.freesewing.org/uploads/medium_patrick_teagan_d32ebc17a2.png) +![FreeSewing's Shin swimtrunks in green and with purple blobs](https://posts.freesewing.org/uploads/small_patrick_shin_42e16e2342.png) + + +### Phineas and Ferb +Another iconic duo! Recreate Phineas' outfit with an orange striped [Teagan](/designs/teagan/) and pair it with short, blue cargo-like pants (or just dark jeans). +Bonus points if you have blue sneakers and maybe even (temporary) red hair dye. + +Ferb seems to be wearing a pastel yellow [Simon](/designs/simon/) with a white collar and buttons. He also wears very high-waisted purple pants, easy to recreate with an altered [Charlie](/designs/charlie/). +Aside from that, he wears black sneakers and... green hair. This is your time to go wild. + +![Phineas, Ferb and Perry surfing](https://posts.freesewing.org/uploads/phineas_ferb_45e5afda28.webp) + +![FreeSewing's Charlie chino's in a deep purple](https://posts.freesewing.org/uploads/medium_ferb_charlie_51ced3ff7e.png) +![FreeSewing's Simon shirt in pastel yellow with short sleeves and a white collar and buttons.](https://posts.freesewing.org/uploads/medium_ferb_simon_d87b96bc1d.png) +![FreeSewing's Teagan tee in yellow with orange stripes](https://posts.freesewing.org/uploads/medium_phineas_teagan_62d98938ee.png) + + +### Ash from Pokémon +The main character from the beloved Pokémon series! Although his look has changed many times over the last 20 years, there are still ways to embody him. + +He generally wears light denim jeans and his iconic red hat. We currently do not have patterns for either of these, but we do have patterns for the jackets he wears! + +To create his original outfit, wear a blue [Simon](/designs/simon/) with short white sleeves and a white collar, with yellow top buttons. +This jacket seems to have yellow pockets, but sewing yellow stripes on it will also do the trick. +(P.S. This jacket is not really a Simon, but it's the closest we have.) +If you really want to go all the way, the bottom of his jacket has a yellow line and he wears green fingerless gloves. He wears a dark green or black shirt under this, or use [Teagan](/designs/teagan/) if you don't have one. + +If that's a bit much, any bright blue jacket will recreate his vibe. + Add yellow accessories to get more into it. If that's too simple, he also wears a t-shirt ([Teagan](/designs/teagan/) would be great here, too!) in the Sun and Moon series. Forget the jeans for this one; he pairs this with shortened [Pacos](/designs/paco/) that have red ribbing. + +![Character Ash from the Pokémon series](https://posts.freesewing.org/uploads/medium_ash_8f9cbfb8f2.jpg) + +![FreeSewing's Simon shirt altered to mirror the shirt from the character Ash](https://posts.freesewing.org/uploads/medium_ash_simon_74ef670561.png) + +(Hint: in our other Halloween blogpost, we have ideas for turning Huey and Hugo into Pokémon hoodies!) + + +### The PowerPuff girls +This is a perfect cosplay for a group of three! Choose your favourite body block and pair it with a [Sandy](/designs/sandy/). +Find a large black belt or simply sew a black stripe on the block. You can turn this into a dress, but that's not mandatory. +The three also wear white tights and black shoes. For Blossom (the pink one), you can use [Benjamin](/designs/benjamin/) to create her bow. +Bonus points if you get their hairstyles right too. + +![The three PowerPuff girls flying](https://posts.freesewing.org/uploads/powerpuff_girls_3231f9ec09.webp) + +### Dora +Dora! Iconic and quite easy to replicate. +She wears a cropped pink shirt (cropped Teagan!) and short orange pants, which can be created by making shortened [Pacos](/designs/pacos/) or a [Charlie](/designs/charlie/). +She wears yellow socks, a yellow beaded bracelet, with white or pink shoes. Her purple bag may perhaps be the hardest thing to find. + +![The character Dora](https://posts.freesewing.org/uploads/medium_Dora_0eeb97b52f.webp) + +![FreeSewing's Teagan tee in pink](https://posts.freesewing.org/uploads/medium_dora_teagan_e6e26c630c.png) +![FreeSewing's Charlie chinos but orange and shortened](https://posts.freesewing.org/uploads/dora_charlie_6241e9dd2b.png) + +Now, you may have been wondering if this whole list is going to be children's characters. Don't panic! It's time for more mature characters. + +### Soldier: 76's summer skin +The stoic soldier from the game Overwatch, and his outfits are more fun than you'd think. +His summer skin makes for an awesome casual outfit too. + +The blue apron is arguably the most important part of this, and also the hardest part to get right. +His apron has a lot of pockets. You can start with [Albert](/designs/albert/) and just add a bunch of pockets. +If you make it from cotton, you can write the text on it with fabric dye. + +He also wears a red Hawaiian shirt, which can be replicated with a [Simon](/designs/simon/) with short sleeves, from a red flowery pattern. +He wears brown pants underneath it, which can be replicated with a shortened [Charlie](/designs/charlie/). + +This person even made the apron from leather! The owner commissioned it from [Knotted Bone Leather Works](https://www.knottedboneleatherworks.com/). + +![The character Soldier: 76 in his summer skin](https://posts.freesewing.org/uploads/medium_soldier76summer_7a8260726d.jpg) + +![The Soldier:76 Summer skin's apron from leather](https://posts.freesewing.org/uploads/small_soldier76cosplay_06df3b891c.webp) + + +### Sherlock Holmes +Well, it would almost be a crime if we didn't include this character, as we have patterns inspired by his show! +Wear a dark navy or black [Carlton](/designs/carlton/)/[Carlita](/designs/carlita/) (shocker, I know) and under that wear all-black clothes, or a white dress shirt instead of something black. +To really get the look, wear a desaturated blue scarf and make our [Holmes hat](/designs/holmes/) from a gray fabric ("herringbone") and with a dark brown ribbon. + +![Sherlock Holmes from the TV series](https://posts.freesewing.org/uploads/medium_sherlock_holmes_hat_de80125cd1.webp) +![bc.jpg](https://posts.freesewing.org/uploads/medium_bc_f20e01a16d.jpg) + + +### Janet from The Good Place +Janet, our favourite non-human (slightly human) assistant. +This entry wouldn't be here if not for [Natalia](https://freesewing.org/makers/nataliasayang/)! +She cosplayed this character last year and it looks awesome. +If you'd want to create Janet's look with FreeSewing patterns: make a [Wahid](/designs/wahid/) and [Sandy](/designs/sandy/), both from a deep purple fabric, and pair it with a long-sleeved shirt made from an (optionally translucent) blue flowered fabric. +Janet's shirt has a lot of flair that we don't have features for, but you can manually add these things. + +![Janet from The Good Place](https://posts.freesewing.org/uploads/medium_janet_7985d4b2af.jpg) +![Janet cosplay by Natalia Sayang](https://posts.freesewing.org/uploads/medium_janet_costume_2114092e9a.jpg) + + +### Hatsune Miku +Yes.... She counts as a mature character, although her looks may give the impression that she's popular with children. +But, this vocaloid (the product of a voice synthesizer software) has many fans and has even had real-life concerts! (Crazy for a fictional character!) + +Anyways, to create her look, you'll need a gray [Wahid](/designs/wahid/), optionally with blue lines, and a blue [Trayvon](/designs/trayvon/) tie. +She also wears a black pleated knife skirt, with a blue line, but erm... This pattern does not *yet* exist. +She wears black tights (again with a blue stripe!) with black shoes. + +She wears huge sleeves that aren't attached to her top; you can simply grab Sven and only take the sleeves, cut a bit off the top of the sleeve and add an elastic band there, and make the rest of the sleeve get wider and wider. Again there's the option to add a blue line. + +Bonus points if you can find a wig for her iconic blue pigtails, but if you have long hair you can also get the vibe by recreating her hairstyle with your own hair. + +![The vocaloid Hatsune Miku](https://posts.freesewing.org/uploads/medium_hatsune_miku_43ccad726b.jpg) + +![FreeSewing's Wahid waistcoat in gray](https://posts.freesewing.org/uploads/medium_miku_wahid_2dce7835cc.png) +![FreeSewing's Trayvon tie in blue](https://posts.freesewing.org/uploads/medium_miku_trayvon_a204b6499f.png) + + +Hopefully we inspired you and happy halloween! 🎃 + +> *This was a collaboration between bobgeorgethethird and lucibytes!* diff --git a/markdown/org/blog/halloween-cosplays-2021/nl.md b/markdown/org/blog/halloween-cosplays-2021/nl.md new file mode 100644 index 00000000000..186b5bea283 --- /dev/null +++ b/markdown/org/blog/halloween-cosplays-2021/nl.md @@ -0,0 +1,147 @@ +--- +author: "joostdecock" +caption: "A bit cold perhaps, but swimtrunks: we've got'em" +date: "2021-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3a69586735a24a674d4e65971643b3b55c676fc3-1000x667.png" +intro: "Embodying your favourite character can make for a really fun Halloween experience! Here are some iconic characters to get you inspired." +title: "10 cosplays you can make from FreeSewing patterns to get you in the Halloween mood [Niet vertaald]" +--- + +Embodying your favourite character can make for a really fun Halloween experience! Here are some iconic characters to get you inspired. + +### Spongebob +Perhaps the most iconic character of them all, who doesn't know this yellow sponge? And his outfit is surprisingly stylish too! + +He wears a white dress shirt and brown pants, which can be created by [Simon](/designs/simon/) and a shortened [Charlie](/designs/charlie/) respectively, but you may already have this in your closet (saves time!). +A bright red [Trayvon](/designs/trayvon/) and a black belt would top it all off, or you can go even further by wearing shiny black shoes and white socks. + +![SpongeBob_stock_art.webp](https://posts.freesewing.org/uploads/Sponge_Bob_stock_art_ada2f4fd18.webp) + +![FreeSewing's Trayvon tie in a bright red](https://posts.freesewing.org/uploads/medium_spongebob_trayvon_e9729ec7ef.png) +![FreeSewing's Simon with shortened sleeves in white](https://posts.freesewing.org/uploads/medium_spongebob_simon_2327811c53.png) +![FreeSewing's Charlie, shortened and in brown](https://posts.freesewing.org/uploads/spongebob_charlie_fd09ebd233.png) + + +### Patrick +Where there is Spongebob, there is Patrick. Recreate his look with a pink [Teagan](/designs/teagan/) (or a pink shirt from your closet) and green [Shin swim trunks](/designs/shin/). +If you want to go even further, try to find fabric that resembles the pattern of his shorts, or paint the purple flowers on a pair of green shorts yourself! + +![A picture of Patrick Star](https://posts.freesewing.org/uploads/large_patrick_star_f206a40931.webp) + +![FreeSewing's Teagan tee in pink](https://posts.freesewing.org/uploads/medium_patrick_teagan_d32ebc17a2.png) +![FreeSewing's Shin swimtrunks in green and with purple blobs](https://posts.freesewing.org/uploads/small_patrick_shin_42e16e2342.png) + + +### Phineas and Ferb +Another iconic duo! Recreate Phineas' outfit with an orange striped [Teagan](/designs/teagan/) and pair it with short, blue cargo-like pants (or just dark jeans). +Bonus points if you have blue sneakers and maybe even (temporary) red hair dye. + +Ferb seems to be wearing a pastel yellow [Simon](/designs/simon/) with a white collar and buttons. He also wears very high-waisted purple pants, easy to recreate with an altered [Charlie](/designs/charlie/). +Aside from that, he wears black sneakers and... green hair. This is your time to go wild. + +![Phineas, Ferb and Perry surfing](https://posts.freesewing.org/uploads/phineas_ferb_45e5afda28.webp) + +![FreeSewing's Charlie chino's in a deep purple](https://posts.freesewing.org/uploads/medium_ferb_charlie_51ced3ff7e.png) +![FreeSewing's Simon shirt in pastel yellow with short sleeves and a white collar and buttons.](https://posts.freesewing.org/uploads/medium_ferb_simon_d87b96bc1d.png) +![FreeSewing's Teagan tee in yellow with orange stripes](https://posts.freesewing.org/uploads/medium_phineas_teagan_62d98938ee.png) + + +### Ash from Pokémon +The main character from the beloved Pokémon series! Although his look has changed many times over the last 20 years, there are still ways to embody him. + +He generally wears light denim jeans and his iconic red hat. We currently do not have patterns for either of these, but we do have patterns for the jackets he wears! + +To create his original outfit, wear a blue [Simon](/designs/simon/) with short white sleeves and a white collar, with yellow top buttons. +This jacket seems to have yellow pockets, but sewing yellow stripes on it will also do the trick. +(P.S. This jacket is not really a Simon, but it's the closest we have.) +If you really want to go all the way, the bottom of his jacket has a yellow line and he wears green fingerless gloves. He wears a dark green or black shirt under this, or use [Teagan](/designs/teagan/) if you don't have one. + +If that's a bit much, any bright blue jacket will recreate his vibe. + Add yellow accessories to get more into it. If that's too simple, he also wears a t-shirt ([Teagan](/designs/teagan/) would be great here, too!) in the Sun and Moon series. Forget the jeans for this one; he pairs this with shortened [Pacos](/designs/paco/) that have red ribbing. + +![Character Ash from the Pokémon series](https://posts.freesewing.org/uploads/medium_ash_8f9cbfb8f2.jpg) + +![FreeSewing's Simon shirt altered to mirror the shirt from the character Ash](https://posts.freesewing.org/uploads/medium_ash_simon_74ef670561.png) + +(Hint: in our other Halloween blogpost, we have ideas for turning Huey and Hugo into Pokémon hoodies!) + + +### The PowerPuff girls +This is a perfect cosplay for a group of three! Choose your favourite body block and pair it with a [Sandy](/designs/sandy/). +Find a large black belt or simply sew a black stripe on the block. You can turn this into a dress, but that's not mandatory. +The three also wear white tights and black shoes. For Blossom (the pink one), you can use [Benjamin](/designs/benjamin/) to create her bow. +Bonus points if you get their hairstyles right too. + +![The three PowerPuff girls flying](https://posts.freesewing.org/uploads/powerpuff_girls_3231f9ec09.webp) + +### Dora +Dora! Iconic and quite easy to replicate. +She wears a cropped pink shirt (cropped Teagan!) and short orange pants, which can be created by making shortened [Pacos](/designs/pacos/) or a [Charlie](/designs/charlie/). +She wears yellow socks, a yellow beaded bracelet, with white or pink shoes. Her purple bag may perhaps be the hardest thing to find. + +![The character Dora](https://posts.freesewing.org/uploads/medium_Dora_0eeb97b52f.webp) + +![FreeSewing's Teagan tee in pink](https://posts.freesewing.org/uploads/medium_dora_teagan_e6e26c630c.png) +![FreeSewing's Charlie chinos but orange and shortened](https://posts.freesewing.org/uploads/dora_charlie_6241e9dd2b.png) + +Now, you may have been wondering if this whole list is going to be children's characters. Don't panic! It's time for more mature characters. + +### Soldier: 76's summer skin +The stoic soldier from the game Overwatch, and his outfits are more fun than you'd think. +His summer skin makes for an awesome casual outfit too. + +The blue apron is arguably the most important part of this, and also the hardest part to get right. +His apron has a lot of pockets. You can start with [Albert](/designs/albert/) and just add a bunch of pockets. +If you make it from cotton, you can write the text on it with fabric dye. + +He also wears a red Hawaiian shirt, which can be replicated with a [Simon](/designs/simon/) with short sleeves, from a red flowery pattern. +He wears brown pants underneath it, which can be replicated with a shortened [Charlie](/designs/charlie/). + +This person even made the apron from leather! The owner commissioned it from [Knotted Bone Leather Works](https://www.knottedboneleatherworks.com/). + +![The character Soldier: 76 in his summer skin](https://posts.freesewing.org/uploads/medium_soldier76summer_7a8260726d.jpg) + +![The Soldier:76 Summer skin's apron from leather](https://posts.freesewing.org/uploads/small_soldier76cosplay_06df3b891c.webp) + + +### Sherlock Holmes +Well, it would almost be a crime if we didn't include this character, as we have patterns inspired by his show! +Wear a dark navy or black [Carlton](/designs/carlton/)/[Carlita](/designs/carlita/) (shocker, I know) and under that wear all-black clothes, or a white dress shirt instead of something black. +To really get the look, wear a desaturated blue scarf and make our [Holmes hat](/designs/holmes/) from a gray fabric ("herringbone") and with a dark brown ribbon. + +![Sherlock Holmes from the TV series](https://posts.freesewing.org/uploads/medium_sherlock_holmes_hat_de80125cd1.webp) +![bc.jpg](https://posts.freesewing.org/uploads/medium_bc_f20e01a16d.jpg) + + +### Janet from The Good Place +Janet, our favourite non-human (slightly human) assistant. +This entry wouldn't be here if not for [Natalia](https://freesewing.org/makers/nataliasayang/)! +She cosplayed this character last year and it looks awesome. +If you'd want to create Janet's look with FreeSewing patterns: make a [Wahid](/designs/wahid/) and [Sandy](/designs/sandy/), both from a deep purple fabric, and pair it with a long-sleeved shirt made from an (optionally translucent) blue flowered fabric. +Janet's shirt has a lot of flair that we don't have features for, but you can manually add these things. + +![Janet from The Good Place](https://posts.freesewing.org/uploads/medium_janet_7985d4b2af.jpg) +![Janet cosplay by Natalia Sayang](https://posts.freesewing.org/uploads/medium_janet_costume_2114092e9a.jpg) + + +### Hatsune Miku +Yes.... She counts as a mature character, although her looks may give the impression that she's popular with children. +But, this vocaloid (the product of a voice synthesizer software) has many fans and has even had real-life concerts! (Crazy for a fictional character!) + +Anyways, to create her look, you'll need a gray [Wahid](/designs/wahid/), optionally with blue lines, and a blue [Trayvon](/designs/trayvon/) tie. +She also wears a black pleated knife skirt, with a blue line, but erm... This pattern does not *yet* exist. +She wears black tights (again with a blue stripe!) with black shoes. + +She wears huge sleeves that aren't attached to her top; you can simply grab Sven and only take the sleeves, cut a bit off the top of the sleeve and add an elastic band there, and make the rest of the sleeve get wider and wider. Again there's the option to add a blue line. + +Bonus points if you can find a wig for her iconic blue pigtails, but if you have long hair you can also get the vibe by recreating her hairstyle with your own hair. + +![The vocaloid Hatsune Miku](https://posts.freesewing.org/uploads/medium_hatsune_miku_43ccad726b.jpg) + +![FreeSewing's Wahid waistcoat in gray](https://posts.freesewing.org/uploads/medium_miku_wahid_2dce7835cc.png) +![FreeSewing's Trayvon tie in blue](https://posts.freesewing.org/uploads/medium_miku_trayvon_a204b6499f.png) + + +Hopefully we inspired you and happy halloween! 🎃 + +> *This was a collaboration between bobgeorgethethird and lucibytes!* diff --git a/markdown/org/blog/halloween-ideas-2021/de.md b/markdown/org/blog/halloween-ideas-2021/de.md new file mode 100644 index 00000000000..ff6ce134203 --- /dev/null +++ b/markdown/org/blog/halloween-ideas-2021/de.md @@ -0,0 +1,66 @@ +--- +author: "joostdecock" +caption: "Drawing by @racerxmachina, Sandy!" +date: "2021-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/37c6f1c78ac0bfb539ea2b11ff32f104c34a0d6d-1666x1111.jpg" +intro: "You may already have an idea for what you want to make for Halloween. Or maybe you have no clue. Either way, here is some inspiration to get you going." +title: "Get your Halloween going with these inspirational costume ideas [Nicht übersetzt]" +--- + + You may already have an idea for what you want to make for Halloween. Or maybe you have no clue. Either way, here is some inspiration to get you going. + +### Want to go for a vintage look? +Many of our patterns can give you a vintage-esque look without actually having to be vintage. +Working outwards from the bases of [Charlie](/designs/charlie) and [Simon](/designs/simon/)/[Simone](/designs/simone/), you can then use combination of [Wahid](/designs/wahid/), [Jaeger](/designs/jeager), [Carlton](/designs/carlton/)/[Carlita](/designs/carlita) for the outerwear. To complete the look, don a [Florent](/designs/florent) and a [Trayvon](/designs/trayvon) or [Benjamin](/designs/benjamin). If [Charlie](/designs/charlie/) isn’t doing it for you, maybe switch it out for a [Cornelius](/designs/cornelius/) or a floor -length quarter-circle or half-circle [Sandy Skirt](/designs/sandy/). + +### Want to have more of Gothic look? +First, let’s make more Romantic version of [Simon](/designs/simon/)/[Simone](/designs/simone/). You can do this by slashing and spreading the sleeve piece. There are many ways to do this and many variations, but we recommend a bishop sleeve which you can find [on SewingJulie's YouTube channel]( https://www.youtube.com/watch?v=GkEZtATYZ2g&ab_channel=SewingJulie). Just remember that [Simon](/designs/simon/)([e](/designs/simone/)) has already been drafted for a cuff and has a placket. From there you can throw on a pair of [Charlies](/designs/charlie/). + +For outerwear, you can either go for a [Wahid](/designs/wahid/) or [Cathrin](/designs/cathrin/) and to finish the look we recommend the square variant of [Benjamin](/designs/benjamin/). Again if [Charlie](/designs/charlie/) is not your thing you can try [Penelope](/designs/penelope/) or [Sandy](/designs/sandy/). +![A drawing of a vampire-like man, wearing a poofy Simon shirt and a purple Wahid waistcoat](https://posts.freesewing.org/uploads/wahidsimonvamp_345e8bb3b0.jpg) + *Drawing by @racerxmachina, Sandy* + +### Or are you more of a secret agent? +Get the suave look by making a [Jaeger](/designs/jaeger/), [Trayvon](/designs/trayvon/), and [Charlie](/designs/charlie/) and pair it with your favourite sunglasses. If the [Jaeger](/designs/jaeger/) isn’t your style, try switching it out for a [Wahid](/designs/wahid/). And if trousers don’t take your fancy, try [Penelope](/designs/penelope/) or a quarter-circle [Sandy](/designs/sandy/). + +Or maybe you want to be in your combat garb. Try combining [Sven](/designs/sven/) and [Paco](/designs/paco/). Pair them with some combat boots and a belt of your choosing. + +### Maybe you are more of fantasy dweller? +Whilst we don’t have many patterns that emulate fantasy, the [Cathrin Corset](/designs/cathrin/) is a great place to start. Combine it with a Puff-Sleeve variant of [Teagan](/designs/teagan/) and a floor-length quarter- or half-circle [Sandy](/designs/sandy/), and you are well on your way to emulating [the Cathrin cover art](/designs/cathrin/). For those of you who are feeling a little more adventurous, a little challenge for you: try combining [Cornelius](/designs/cornelius/) and [Paco](/designs/paco/) together to create satyr legs, then perhaps pair it with [Wahid](/designs/wahid/) and [Simon](/designs/simon/)/[Simone](/designs/simone/). + +### Become "that suit person." +This is a goofy outfit that can be worn to any informal party. The formal aspects of [Jaeger](/designs/jaeger/) and [Charlie](/designs/charlie/) clash beautifully with crazy patterned fabrics, which makes for a super fun Halloween outfit, which can also be worn to other parties in the future. Making a [Jaeger](/designs/jaeger/) is hard, but at least the idea is simple: find your favourite crazy fabric and use it for both pieces. You can wear a white dress shirt (or a white [Simon](/designs/simon/)) underneath. There's an option to add a [Trayvon](/designs/trayvon/) or [Benjamin](/designs/benjamin/) in a bright color as well. The possibilities are endless! + +### Or maybe you only want to make one or two garments for an easy-to-wear costume? +[Huey](/designs/huey/), [Hugo](/designs/hugo/), and [Paco](/designs/paco/) are perfect bases to create simple animal hoodies and trousers that will also be comfortable to wear. There are many animals you can try so here are a few basic alterations and ideas to get your creative brain flowing. + +#### Creating a back seam for Hugo and Huey +For simple things like back spikes for dinosaurs, you may find it useful to create a back seam in [Hugo](/designs/hugo/) or [Huey](/designs/huey/). This is simply done by cutting two back pieces instead of one on the fold. Don't forget to add seam allowance along the center back! From there you would construct your additions, such as spikes, and then baste them to one of the back pieces with right sides together. Then pin the other back piece over the top, right sides together and sew. This will now count as your single back piece in the Huey and [Hugo instructions](https://freesewing.org/docs/patterns/hugo/instructions/). + +The same can be done with the hood center piece for [Hugo](/designs/hugo/), and [Huey](/designs/huey/)'s hood already has a center back seam so no changes are required for Huey's hood. Another thing you can do is split the hood patterns in half ear to ear if you are adding stuff like ears but you may find it easier just to hand sew these elements on. + +For these particular costumes we recommend using fabrics that do not fray such as polar fleece for the body and larger additions, with felt being an option for the smaller add-ons. + +With these alterations in mind, let’s talk some ideas. + +#### Wings +This might sound odd at first, but hear me out. You can add wings by making a quarter- or half-circle and inserting them into the side seams of [Huey](/designs/huey/) and [Hugo](/designs/hugo/). If you make want to make your wings more spiky, cut-out semi-circles from the curved edge of your pattern, a plate will make this a lot quicker. Experiment! There are many types of wings and many shapes for them! +#### Bear +Who doesn’t want a ferocious bear running around a party? Create round ears for the hood and an oval shape to go on front for the underbelly. You can make a simple small tail for the back of the hoodie. +#### Cat +Everybody wants to be a cat! Well not everybody, but if you want to go as one of the Halloween staples and be comfortable, this is the way to do. Add pointed triangle ears to the hood and possibly whiskers with pipe cleaners and add a long sausage tail to the back. +#### Dinosaurs +Add horns! Add teeth! Add spikes! The possibilities are endless! If you want to keep it simple, make the center back seam adjustment and add some spikes, then add some felt triangles to represent teeth around the brim of the hood. If you are feeling more daring, why not try to emulate a triceratops head with its horns. You can also add spots to represent dinosaur skin and even a tail if you're up for it. +![A drawing of a child and an adult walking hand in hand, one wearing a bat costume, the other a dragon costume](https://posts.freesewing.org/uploads/huey_paco_costumes_8a199c7572.jpg) +*Drawing by @racerxmachina, Sandy* + +#### Dog +Add triangle ears and a wagging tail, or if that’s not to your liking you can try floppy ears. For more variation you can add spots to denote color. Possibly, be a Cruella and make it look like a Dalmatian. +#### Rabbit +Go for pink, white, yellow, brown, grey, black or any other color a bunny can be! Add oval-shaped ears and a small nose. For a tail, simply gather up a circle of fur fabric around a ball of stuffing and hand sew to your hoodie. +#### Pokemon +Now I know what you are thinking. Why is this in the regulars? Well we thought it was best to keep all the [Hugo](/designs/hugo/) and [Huey](/designs/huey/) adaptations together. So why not be inspired by [Frankie’s Bulbasaur Huey](/showcase/bulbasaur-huey/) they made for the child and make a [Huey](/designs/huey/) or [Hugo](/designs/hugo/) inspired favourite Pokemon. You can be as elaborate as you like and make ears, bulbs, and other appendages, or you can simply use the color scheme of your favourite Pokemon and add their eyes, mouth and nose on the hood. +#### Detective Pikachu +A detective that might even rival Sherlock Holmes would also be amiss without their hat. Use a [Holmes](/designs/holmes/) with a beige brown herringbone fabric and dark brown ribbon. Now what about the ears? The ears?! Why yes, Pikachu’s ears! Make a two-layered oval shape with a straight bottom. You can either cut and sew the black tops on as a seam or sew them on after you've turned the yellow parts right-side-out. Sew the two yellow layers together good sides together leaving the bottom open, trim and clip the seam allowances, then turn right-side-out. Once turned, stuff and hand sew to the ear flaps of the deerstalker before they are attached to the crown. You can sew these on after final construction if easier, just remember to close the bottom as a seam with hand-sewing before attaching to ear flaps. If you’re not aiming the exact look experiment with different colors and patterns and make a unique Detective Pikachu hat just for you! + +> *This was a collaboration between bobgeorgethethird and lucibytes!* diff --git a/markdown/org/blog/halloween-ideas-2021/en.md b/markdown/org/blog/halloween-ideas-2021/en.md new file mode 100644 index 00000000000..3874a298787 --- /dev/null +++ b/markdown/org/blog/halloween-ideas-2021/en.md @@ -0,0 +1,66 @@ +--- +author: "joostdecock" +caption: "Drawing by @racerxmachina, Sandy!" +date: "2021-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/37c6f1c78ac0bfb539ea2b11ff32f104c34a0d6d-1666x1111.jpg" +intro: "You may already have an idea for what you want to make for Halloween. Or maybe you have no clue. Either way, here is some inspiration to get you going." +title: "Get your Halloween going with these inspirational costume ideas" +--- + + You may already have an idea for what you want to make for Halloween. Or maybe you have no clue. Either way, here is some inspiration to get you going. + +### Want to go for a vintage look? +Many of our patterns can give you a vintage-esque look without actually having to be vintage. +Working outwards from the bases of [Charlie](/designs/charlie) and [Simon](/designs/simon/)/[Simone](/designs/simone/), you can then use combination of [Wahid](/designs/wahid/), [Jaeger](/designs/jeager), [Carlton](/designs/carlton/)/[Carlita](/designs/carlita) for the outerwear. To complete the look, don a [Florent](/designs/florent) and a [Trayvon](/designs/trayvon) or [Benjamin](/designs/benjamin). If [Charlie](/designs/charlie/) isn’t doing it for you, maybe switch it out for a [Cornelius](/designs/cornelius/) or a floor -length quarter-circle or half-circle [Sandy Skirt](/designs/sandy/). + +### Want to have more of Gothic look? +First, let’s make more Romantic version of [Simon](/designs/simon/)/[Simone](/designs/simone/). You can do this by slashing and spreading the sleeve piece. There are many ways to do this and many variations, but we recommend a bishop sleeve which you can find [on SewingJulie's YouTube channel]( https://www.youtube.com/watch?v=GkEZtATYZ2g&ab_channel=SewingJulie). Just remember that [Simon](/designs/simon/)([e](/designs/simone/)) has already been drafted for a cuff and has a placket. From there you can throw on a pair of [Charlies](/designs/charlie/). + +For outerwear, you can either go for a [Wahid](/designs/wahid/) or [Cathrin](/designs/cathrin/) and to finish the look we recommend the square variant of [Benjamin](/designs/benjamin/). Again if [Charlie](/designs/charlie/) is not your thing you can try [Penelope](/designs/penelope/) or [Sandy](/designs/sandy/). +![A drawing of a vampire-like man, wearing a poofy Simon shirt and a purple Wahid waistcoat](https://posts.freesewing.org/uploads/wahidsimonvamp_345e8bb3b0.jpg) + *Drawing by @racerxmachina, Sandy* + +### Or are you more of a secret agent? +Get the suave look by making a [Jaeger](/designs/jaeger/), [Trayvon](/designs/trayvon/), and [Charlie](/designs/charlie/) and pair it with your favourite sunglasses. If the [Jaeger](/designs/jaeger/) isn’t your style, try switching it out for a [Wahid](/designs/wahid/). And if trousers don’t take your fancy, try [Penelope](/designs/penelope/) or a quarter-circle [Sandy](/designs/sandy/). + +Or maybe you want to be in your combat garb. Try combining [Sven](/designs/sven/) and [Paco](/designs/paco/). Pair them with some combat boots and a belt of your choosing. + +### Maybe you are more of fantasy dweller? +Whilst we don’t have many patterns that emulate fantasy, the [Cathrin Corset](/designs/cathrin/) is a great place to start. Combine it with a Puff-Sleeve variant of [Teagan](/designs/teagan/) and a floor-length quarter- or half-circle [Sandy](/designs/sandy/), and you are well on your way to emulating [the Cathrin cover art](/designs/cathrin/). For those of you who are feeling a little more adventurous, a little challenge for you: try combining [Cornelius](/designs/cornelius/) and [Paco](/designs/paco/) together to create satyr legs, then perhaps pair it with [Wahid](/designs/wahid/) and [Simon](/designs/simon/)/[Simone](/designs/simone/). + +### Become "that suit person." +This is a goofy outfit that can be worn to any informal party. The formal aspects of [Jaeger](/designs/jaeger/) and [Charlie](/designs/charlie/) clash beautifully with crazy patterned fabrics, which makes for a super fun Halloween outfit, which can also be worn to other parties in the future. Making a [Jaeger](/designs/jaeger/) is hard, but at least the idea is simple: find your favourite crazy fabric and use it for both pieces. You can wear a white dress shirt (or a white [Simon](/designs/simon/)) underneath. There's an option to add a [Trayvon](/designs/trayvon/) or [Benjamin](/designs/benjamin/) in a bright color as well. The possibilities are endless! + +### Or maybe you only want to make one or two garments for an easy-to-wear costume? +[Huey](/designs/huey/), [Hugo](/designs/hugo/), and [Paco](/designs/paco/) are perfect bases to create simple animal hoodies and trousers that will also be comfortable to wear. There are many animals you can try so here are a few basic alterations and ideas to get your creative brain flowing. + +#### Creating a back seam for Hugo and Huey +For simple things like back spikes for dinosaurs, you may find it useful to create a back seam in [Hugo](/designs/hugo/) or [Huey](/designs/huey/). This is simply done by cutting two back pieces instead of one on the fold. Don't forget to add seam allowance along the center back! From there you would construct your additions, such as spikes, and then baste them to one of the back pieces with right sides together. Then pin the other back piece over the top, right sides together and sew. This will now count as your single back piece in the Huey and [Hugo instructions](https://freesewing.org/docs/patterns/hugo/instructions/). + +The same can be done with the hood center piece for [Hugo](/designs/hugo/), and [Huey](/designs/huey/)'s hood already has a center back seam so no changes are required for Huey's hood. Another thing you can do is split the hood patterns in half ear to ear if you are adding stuff like ears but you may find it easier just to hand sew these elements on. + +For these particular costumes we recommend using fabrics that do not fray such as polar fleece for the body and larger additions, with felt being an option for the smaller add-ons. + +With these alterations in mind, let’s talk some ideas. + +#### Wings +This might sound odd at first, but hear me out. You can add wings by making a quarter- or half-circle and inserting them into the side seams of [Huey](/designs/huey/) and [Hugo](/designs/hugo/). If you make want to make your wings more spiky, cut-out semi-circles from the curved edge of your pattern, a plate will make this a lot quicker. Experiment! There are many types of wings and many shapes for them! +#### Bear +Who doesn’t want a ferocious bear running around a party? Create round ears for the hood and an oval shape to go on front for the underbelly. You can make a simple small tail for the back of the hoodie. +#### Cat +Everybody wants to be a cat! Well not everybody, but if you want to go as one of the Halloween staples and be comfortable, this is the way to do. Add pointed triangle ears to the hood and possibly whiskers with pipe cleaners and add a long sausage tail to the back. +#### Dinosaurs +Add horns! Add teeth! Add spikes! The possibilities are endless! If you want to keep it simple, make the center back seam adjustment and add some spikes, then add some felt triangles to represent teeth around the brim of the hood. If you are feeling more daring, why not try to emulate a triceratops head with its horns. You can also add spots to represent dinosaur skin and even a tail if you're up for it. +![A drawing of a child and an adult walking hand in hand, one wearing a bat costume, the other a dragon costume](https://posts.freesewing.org/uploads/huey_paco_costumes_8a199c7572.jpg) +*Drawing by @racerxmachina, Sandy* + +#### Dog +Add triangle ears and a wagging tail, or if that’s not to your liking you can try floppy ears. For more variation you can add spots to denote color. Possibly, be a Cruella and make it look like a Dalmatian. +#### Rabbit +Go for pink, white, yellow, brown, grey, black or any other color a bunny can be! Add oval-shaped ears and a small nose. For a tail, simply gather up a circle of fur fabric around a ball of stuffing and hand sew to your hoodie. +#### Pokemon +Now I know what you are thinking. Why is this in the regulars? Well we thought it was best to keep all the [Hugo](/designs/hugo/) and [Huey](/designs/huey/) adaptations together. So why not be inspired by [Frankie’s Bulbasaur Huey](/showcase/bulbasaur-huey/) they made for the child and make a [Huey](/designs/huey/) or [Hugo](/designs/hugo/) inspired favourite Pokemon. You can be as elaborate as you like and make ears, bulbs, and other appendages, or you can simply use the color scheme of your favourite Pokemon and add their eyes, mouth and nose on the hood. +#### Detective Pikachu +A detective that might even rival Sherlock Holmes would also be amiss without their hat. Use a [Holmes](/designs/holmes/) with a beige brown herringbone fabric and dark brown ribbon. Now what about the ears? The ears?! Why yes, Pikachu’s ears! Make a two-layered oval shape with a straight bottom. You can either cut and sew the black tops on as a seam or sew them on after you've turned the yellow parts right-side-out. Sew the two yellow layers together good sides together leaving the bottom open, trim and clip the seam allowances, then turn right-side-out. Once turned, stuff and hand sew to the ear flaps of the deerstalker before they are attached to the crown. You can sew these on after final construction if easier, just remember to close the bottom as a seam with hand-sewing before attaching to ear flaps. If you’re not aiming the exact look experiment with different colors and patterns and make a unique Detective Pikachu hat just for you! + +> *This was a collaboration between bobgeorgethethird and lucibytes!* diff --git a/markdown/org/blog/halloween-ideas-2021/es.md b/markdown/org/blog/halloween-ideas-2021/es.md new file mode 100644 index 00000000000..3cc7d3875a3 --- /dev/null +++ b/markdown/org/blog/halloween-ideas-2021/es.md @@ -0,0 +1,66 @@ +--- +author: "joostdecock" +caption: "Drawing by @racerxmachina, Sandy!" +date: "2021-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/37c6f1c78ac0bfb539ea2b11ff32f104c34a0d6d-1666x1111.jpg" +intro: "You may already have an idea for what you want to make for Halloween. Or maybe you have no clue. Either way, here is some inspiration to get you going." +title: "Get your Halloween going with these inspirational costume ideas [No traducido]" +--- + + You may already have an idea for what you want to make for Halloween. Or maybe you have no clue. Either way, here is some inspiration to get you going. + +### Want to go for a vintage look? +Many of our patterns can give you a vintage-esque look without actually having to be vintage. +Working outwards from the bases of [Charlie](/designs/charlie) and [Simon](/designs/simon/)/[Simone](/designs/simone/), you can then use combination of [Wahid](/designs/wahid/), [Jaeger](/designs/jeager), [Carlton](/designs/carlton/)/[Carlita](/designs/carlita) for the outerwear. To complete the look, don a [Florent](/designs/florent) and a [Trayvon](/designs/trayvon) or [Benjamin](/designs/benjamin). If [Charlie](/designs/charlie/) isn’t doing it for you, maybe switch it out for a [Cornelius](/designs/cornelius/) or a floor -length quarter-circle or half-circle [Sandy Skirt](/designs/sandy/). + +### Want to have more of Gothic look? +First, let’s make more Romantic version of [Simon](/designs/simon/)/[Simone](/designs/simone/). You can do this by slashing and spreading the sleeve piece. There are many ways to do this and many variations, but we recommend a bishop sleeve which you can find [on SewingJulie's YouTube channel]( https://www.youtube.com/watch?v=GkEZtATYZ2g&ab_channel=SewingJulie). Just remember that [Simon](/designs/simon/)([e](/designs/simone/)) has already been drafted for a cuff and has a placket. From there you can throw on a pair of [Charlies](/designs/charlie/). + +For outerwear, you can either go for a [Wahid](/designs/wahid/) or [Cathrin](/designs/cathrin/) and to finish the look we recommend the square variant of [Benjamin](/designs/benjamin/). Again if [Charlie](/designs/charlie/) is not your thing you can try [Penelope](/designs/penelope/) or [Sandy](/designs/sandy/). +![A drawing of a vampire-like man, wearing a poofy Simon shirt and a purple Wahid waistcoat](https://posts.freesewing.org/uploads/wahidsimonvamp_345e8bb3b0.jpg) + *Drawing by @racerxmachina, Sandy* + +### Or are you more of a secret agent? +Get the suave look by making a [Jaeger](/designs/jaeger/), [Trayvon](/designs/trayvon/), and [Charlie](/designs/charlie/) and pair it with your favourite sunglasses. If the [Jaeger](/designs/jaeger/) isn’t your style, try switching it out for a [Wahid](/designs/wahid/). And if trousers don’t take your fancy, try [Penelope](/designs/penelope/) or a quarter-circle [Sandy](/designs/sandy/). + +Or maybe you want to be in your combat garb. Try combining [Sven](/designs/sven/) and [Paco](/designs/paco/). Pair them with some combat boots and a belt of your choosing. + +### Maybe you are more of fantasy dweller? +Whilst we don’t have many patterns that emulate fantasy, the [Cathrin Corset](/designs/cathrin/) is a great place to start. Combine it with a Puff-Sleeve variant of [Teagan](/designs/teagan/) and a floor-length quarter- or half-circle [Sandy](/designs/sandy/), and you are well on your way to emulating [the Cathrin cover art](/designs/cathrin/). For those of you who are feeling a little more adventurous, a little challenge for you: try combining [Cornelius](/designs/cornelius/) and [Paco](/designs/paco/) together to create satyr legs, then perhaps pair it with [Wahid](/designs/wahid/) and [Simon](/designs/simon/)/[Simone](/designs/simone/). + +### Become "that suit person." +This is a goofy outfit that can be worn to any informal party. The formal aspects of [Jaeger](/designs/jaeger/) and [Charlie](/designs/charlie/) clash beautifully with crazy patterned fabrics, which makes for a super fun Halloween outfit, which can also be worn to other parties in the future. Making a [Jaeger](/designs/jaeger/) is hard, but at least the idea is simple: find your favourite crazy fabric and use it for both pieces. You can wear a white dress shirt (or a white [Simon](/designs/simon/)) underneath. There's an option to add a [Trayvon](/designs/trayvon/) or [Benjamin](/designs/benjamin/) in a bright color as well. The possibilities are endless! + +### Or maybe you only want to make one or two garments for an easy-to-wear costume? +[Huey](/designs/huey/), [Hugo](/designs/hugo/), and [Paco](/designs/paco/) are perfect bases to create simple animal hoodies and trousers that will also be comfortable to wear. There are many animals you can try so here are a few basic alterations and ideas to get your creative brain flowing. + +#### Creating a back seam for Hugo and Huey +For simple things like back spikes for dinosaurs, you may find it useful to create a back seam in [Hugo](/designs/hugo/) or [Huey](/designs/huey/). This is simply done by cutting two back pieces instead of one on the fold. Don't forget to add seam allowance along the center back! From there you would construct your additions, such as spikes, and then baste them to one of the back pieces with right sides together. Then pin the other back piece over the top, right sides together and sew. This will now count as your single back piece in the Huey and [Hugo instructions](https://freesewing.org/docs/patterns/hugo/instructions/). + +The same can be done with the hood center piece for [Hugo](/designs/hugo/), and [Huey](/designs/huey/)'s hood already has a center back seam so no changes are required for Huey's hood. Another thing you can do is split the hood patterns in half ear to ear if you are adding stuff like ears but you may find it easier just to hand sew these elements on. + +For these particular costumes we recommend using fabrics that do not fray such as polar fleece for the body and larger additions, with felt being an option for the smaller add-ons. + +With these alterations in mind, let’s talk some ideas. + +#### Wings +This might sound odd at first, but hear me out. You can add wings by making a quarter- or half-circle and inserting them into the side seams of [Huey](/designs/huey/) and [Hugo](/designs/hugo/). If you make want to make your wings more spiky, cut-out semi-circles from the curved edge of your pattern, a plate will make this a lot quicker. Experiment! There are many types of wings and many shapes for them! +#### Bear +Who doesn’t want a ferocious bear running around a party? Create round ears for the hood and an oval shape to go on front for the underbelly. You can make a simple small tail for the back of the hoodie. +#### Cat +Everybody wants to be a cat! Well not everybody, but if you want to go as one of the Halloween staples and be comfortable, this is the way to do. Add pointed triangle ears to the hood and possibly whiskers with pipe cleaners and add a long sausage tail to the back. +#### Dinosaurs +Add horns! Add teeth! Add spikes! The possibilities are endless! If you want to keep it simple, make the center back seam adjustment and add some spikes, then add some felt triangles to represent teeth around the brim of the hood. If you are feeling more daring, why not try to emulate a triceratops head with its horns. You can also add spots to represent dinosaur skin and even a tail if you're up for it. +![A drawing of a child and an adult walking hand in hand, one wearing a bat costume, the other a dragon costume](https://posts.freesewing.org/uploads/huey_paco_costumes_8a199c7572.jpg) +*Drawing by @racerxmachina, Sandy* + +#### Dog +Add triangle ears and a wagging tail, or if that’s not to your liking you can try floppy ears. For more variation you can add spots to denote color. Possibly, be a Cruella and make it look like a Dalmatian. +#### Rabbit +Go for pink, white, yellow, brown, grey, black or any other color a bunny can be! Add oval-shaped ears and a small nose. For a tail, simply gather up a circle of fur fabric around a ball of stuffing and hand sew to your hoodie. +#### Pokemon +Now I know what you are thinking. Why is this in the regulars? Well we thought it was best to keep all the [Hugo](/designs/hugo/) and [Huey](/designs/huey/) adaptations together. So why not be inspired by [Frankie’s Bulbasaur Huey](/showcase/bulbasaur-huey/) they made for the child and make a [Huey](/designs/huey/) or [Hugo](/designs/hugo/) inspired favourite Pokemon. You can be as elaborate as you like and make ears, bulbs, and other appendages, or you can simply use the color scheme of your favourite Pokemon and add their eyes, mouth and nose on the hood. +#### Detective Pikachu +A detective that might even rival Sherlock Holmes would also be amiss without their hat. Use a [Holmes](/designs/holmes/) with a beige brown herringbone fabric and dark brown ribbon. Now what about the ears? The ears?! Why yes, Pikachu’s ears! Make a two-layered oval shape with a straight bottom. You can either cut and sew the black tops on as a seam or sew them on after you've turned the yellow parts right-side-out. Sew the two yellow layers together good sides together leaving the bottom open, trim and clip the seam allowances, then turn right-side-out. Once turned, stuff and hand sew to the ear flaps of the deerstalker before they are attached to the crown. You can sew these on after final construction if easier, just remember to close the bottom as a seam with hand-sewing before attaching to ear flaps. If you’re not aiming the exact look experiment with different colors and patterns and make a unique Detective Pikachu hat just for you! + +> *This was a collaboration between bobgeorgethethird and lucibytes!* diff --git a/markdown/org/blog/halloween-ideas-2021/fr.md b/markdown/org/blog/halloween-ideas-2021/fr.md new file mode 100644 index 00000000000..e39dbf7c430 --- /dev/null +++ b/markdown/org/blog/halloween-ideas-2021/fr.md @@ -0,0 +1,66 @@ +--- +author: "joostdecock" +caption: "Drawing by @racerxmachina, Sandy!" +date: "2021-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/37c6f1c78ac0bfb539ea2b11ff32f104c34a0d6d-1666x1111.jpg" +intro: "You may already have an idea for what you want to make for Halloween. Or maybe you have no clue. Either way, here is some inspiration to get you going." +title: "Get your Halloween going with these inspirational costume ideas [Non traduit]" +--- + + You may already have an idea for what you want to make for Halloween. Or maybe you have no clue. Either way, here is some inspiration to get you going. + +### Want to go for a vintage look? +Many of our patterns can give you a vintage-esque look without actually having to be vintage. +Working outwards from the bases of [Charlie](/designs/charlie) and [Simon](/designs/simon/)/[Simone](/designs/simone/), you can then use combination of [Wahid](/designs/wahid/), [Jaeger](/designs/jeager), [Carlton](/designs/carlton/)/[Carlita](/designs/carlita) for the outerwear. To complete the look, don a [Florent](/designs/florent) and a [Trayvon](/designs/trayvon) or [Benjamin](/designs/benjamin). If [Charlie](/designs/charlie/) isn’t doing it for you, maybe switch it out for a [Cornelius](/designs/cornelius/) or a floor -length quarter-circle or half-circle [Sandy Skirt](/designs/sandy/). + +### Want to have more of Gothic look? +First, let’s make more Romantic version of [Simon](/designs/simon/)/[Simone](/designs/simone/). You can do this by slashing and spreading the sleeve piece. There are many ways to do this and many variations, but we recommend a bishop sleeve which you can find [on SewingJulie's YouTube channel]( https://www.youtube.com/watch?v=GkEZtATYZ2g&ab_channel=SewingJulie). Just remember that [Simon](/designs/simon/)([e](/designs/simone/)) has already been drafted for a cuff and has a placket. From there you can throw on a pair of [Charlies](/designs/charlie/). + +For outerwear, you can either go for a [Wahid](/designs/wahid/) or [Cathrin](/designs/cathrin/) and to finish the look we recommend the square variant of [Benjamin](/designs/benjamin/). Again if [Charlie](/designs/charlie/) is not your thing you can try [Penelope](/designs/penelope/) or [Sandy](/designs/sandy/). +![A drawing of a vampire-like man, wearing a poofy Simon shirt and a purple Wahid waistcoat](https://posts.freesewing.org/uploads/wahidsimonvamp_345e8bb3b0.jpg) + *Drawing by @racerxmachina, Sandy* + +### Or are you more of a secret agent? +Get the suave look by making a [Jaeger](/designs/jaeger/), [Trayvon](/designs/trayvon/), and [Charlie](/designs/charlie/) and pair it with your favourite sunglasses. If the [Jaeger](/designs/jaeger/) isn’t your style, try switching it out for a [Wahid](/designs/wahid/). And if trousers don’t take your fancy, try [Penelope](/designs/penelope/) or a quarter-circle [Sandy](/designs/sandy/). + +Or maybe you want to be in your combat garb. Try combining [Sven](/designs/sven/) and [Paco](/designs/paco/). Pair them with some combat boots and a belt of your choosing. + +### Maybe you are more of fantasy dweller? +Whilst we don’t have many patterns that emulate fantasy, the [Cathrin Corset](/designs/cathrin/) is a great place to start. Combine it with a Puff-Sleeve variant of [Teagan](/designs/teagan/) and a floor-length quarter- or half-circle [Sandy](/designs/sandy/), and you are well on your way to emulating [the Cathrin cover art](/designs/cathrin/). For those of you who are feeling a little more adventurous, a little challenge for you: try combining [Cornelius](/designs/cornelius/) and [Paco](/designs/paco/) together to create satyr legs, then perhaps pair it with [Wahid](/designs/wahid/) and [Simon](/designs/simon/)/[Simone](/designs/simone/). + +### Become "that suit person." +This is a goofy outfit that can be worn to any informal party. The formal aspects of [Jaeger](/designs/jaeger/) and [Charlie](/designs/charlie/) clash beautifully with crazy patterned fabrics, which makes for a super fun Halloween outfit, which can also be worn to other parties in the future. Making a [Jaeger](/designs/jaeger/) is hard, but at least the idea is simple: find your favourite crazy fabric and use it for both pieces. You can wear a white dress shirt (or a white [Simon](/designs/simon/)) underneath. There's an option to add a [Trayvon](/designs/trayvon/) or [Benjamin](/designs/benjamin/) in a bright color as well. The possibilities are endless! + +### Or maybe you only want to make one or two garments for an easy-to-wear costume? +[Huey](/designs/huey/), [Hugo](/designs/hugo/), and [Paco](/designs/paco/) are perfect bases to create simple animal hoodies and trousers that will also be comfortable to wear. There are many animals you can try so here are a few basic alterations and ideas to get your creative brain flowing. + +#### Creating a back seam for Hugo and Huey +For simple things like back spikes for dinosaurs, you may find it useful to create a back seam in [Hugo](/designs/hugo/) or [Huey](/designs/huey/). This is simply done by cutting two back pieces instead of one on the fold. Don't forget to add seam allowance along the center back! From there you would construct your additions, such as spikes, and then baste them to one of the back pieces with right sides together. Then pin the other back piece over the top, right sides together and sew. This will now count as your single back piece in the Huey and [Hugo instructions](https://freesewing.org/docs/patterns/hugo/instructions/). + +The same can be done with the hood center piece for [Hugo](/designs/hugo/), and [Huey](/designs/huey/)'s hood already has a center back seam so no changes are required for Huey's hood. Another thing you can do is split the hood patterns in half ear to ear if you are adding stuff like ears but you may find it easier just to hand sew these elements on. + +For these particular costumes we recommend using fabrics that do not fray such as polar fleece for the body and larger additions, with felt being an option for the smaller add-ons. + +With these alterations in mind, let’s talk some ideas. + +#### Wings +This might sound odd at first, but hear me out. You can add wings by making a quarter- or half-circle and inserting them into the side seams of [Huey](/designs/huey/) and [Hugo](/designs/hugo/). If you make want to make your wings more spiky, cut-out semi-circles from the curved edge of your pattern, a plate will make this a lot quicker. Experiment! There are many types of wings and many shapes for them! +#### Bear +Who doesn’t want a ferocious bear running around a party? Create round ears for the hood and an oval shape to go on front for the underbelly. You can make a simple small tail for the back of the hoodie. +#### Cat +Everybody wants to be a cat! Well not everybody, but if you want to go as one of the Halloween staples and be comfortable, this is the way to do. Add pointed triangle ears to the hood and possibly whiskers with pipe cleaners and add a long sausage tail to the back. +#### Dinosaurs +Add horns! Add teeth! Add spikes! The possibilities are endless! If you want to keep it simple, make the center back seam adjustment and add some spikes, then add some felt triangles to represent teeth around the brim of the hood. If you are feeling more daring, why not try to emulate a triceratops head with its horns. You can also add spots to represent dinosaur skin and even a tail if you're up for it. +![A drawing of a child and an adult walking hand in hand, one wearing a bat costume, the other a dragon costume](https://posts.freesewing.org/uploads/huey_paco_costumes_8a199c7572.jpg) +*Drawing by @racerxmachina, Sandy* + +#### Dog +Add triangle ears and a wagging tail, or if that’s not to your liking you can try floppy ears. For more variation you can add spots to denote color. Possibly, be a Cruella and make it look like a Dalmatian. +#### Rabbit +Go for pink, white, yellow, brown, grey, black or any other color a bunny can be! Add oval-shaped ears and a small nose. For a tail, simply gather up a circle of fur fabric around a ball of stuffing and hand sew to your hoodie. +#### Pokemon +Now I know what you are thinking. Why is this in the regulars? Well we thought it was best to keep all the [Hugo](/designs/hugo/) and [Huey](/designs/huey/) adaptations together. So why not be inspired by [Frankie’s Bulbasaur Huey](/showcase/bulbasaur-huey/) they made for the child and make a [Huey](/designs/huey/) or [Hugo](/designs/hugo/) inspired favourite Pokemon. You can be as elaborate as you like and make ears, bulbs, and other appendages, or you can simply use the color scheme of your favourite Pokemon and add their eyes, mouth and nose on the hood. +#### Detective Pikachu +A detective that might even rival Sherlock Holmes would also be amiss without their hat. Use a [Holmes](/designs/holmes/) with a beige brown herringbone fabric and dark brown ribbon. Now what about the ears? The ears?! Why yes, Pikachu’s ears! Make a two-layered oval shape with a straight bottom. You can either cut and sew the black tops on as a seam or sew them on after you've turned the yellow parts right-side-out. Sew the two yellow layers together good sides together leaving the bottom open, trim and clip the seam allowances, then turn right-side-out. Once turned, stuff and hand sew to the ear flaps of the deerstalker before they are attached to the crown. You can sew these on after final construction if easier, just remember to close the bottom as a seam with hand-sewing before attaching to ear flaps. If you’re not aiming the exact look experiment with different colors and patterns and make a unique Detective Pikachu hat just for you! + +> *This was a collaboration between bobgeorgethethird and lucibytes!* diff --git a/markdown/org/blog/halloween-ideas-2021/nl.md b/markdown/org/blog/halloween-ideas-2021/nl.md new file mode 100644 index 00000000000..6a61712075f --- /dev/null +++ b/markdown/org/blog/halloween-ideas-2021/nl.md @@ -0,0 +1,66 @@ +--- +author: "joostdecock" +caption: "Drawing by @racerxmachina, Sandy!" +date: "2021-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/37c6f1c78ac0bfb539ea2b11ff32f104c34a0d6d-1666x1111.jpg" +intro: "You may already have an idea for what you want to make for Halloween. Or maybe you have no clue. Either way, here is some inspiration to get you going." +title: "Get your Halloween going with these inspirational costume ideas [Niet vertaald]" +--- + + You may already have an idea for what you want to make for Halloween. Or maybe you have no clue. Either way, here is some inspiration to get you going. + +### Want to go for a vintage look? +Many of our patterns can give you a vintage-esque look without actually having to be vintage. +Working outwards from the bases of [Charlie](/designs/charlie) and [Simon](/designs/simon/)/[Simone](/designs/simone/), you can then use combination of [Wahid](/designs/wahid/), [Jaeger](/designs/jeager), [Carlton](/designs/carlton/)/[Carlita](/designs/carlita) for the outerwear. To complete the look, don a [Florent](/designs/florent) and a [Trayvon](/designs/trayvon) or [Benjamin](/designs/benjamin). If [Charlie](/designs/charlie/) isn’t doing it for you, maybe switch it out for a [Cornelius](/designs/cornelius/) or a floor -length quarter-circle or half-circle [Sandy Skirt](/designs/sandy/). + +### Want to have more of Gothic look? +First, let’s make more Romantic version of [Simon](/designs/simon/)/[Simone](/designs/simone/). You can do this by slashing and spreading the sleeve piece. There are many ways to do this and many variations, but we recommend a bishop sleeve which you can find [on SewingJulie's YouTube channel]( https://www.youtube.com/watch?v=GkEZtATYZ2g&ab_channel=SewingJulie). Just remember that [Simon](/designs/simon/)([e](/designs/simone/)) has already been drafted for a cuff and has a placket. From there you can throw on a pair of [Charlies](/designs/charlie/). + +For outerwear, you can either go for a [Wahid](/designs/wahid/) or [Cathrin](/designs/cathrin/) and to finish the look we recommend the square variant of [Benjamin](/designs/benjamin/). Again if [Charlie](/designs/charlie/) is not your thing you can try [Penelope](/designs/penelope/) or [Sandy](/designs/sandy/). +![A drawing of a vampire-like man, wearing a poofy Simon shirt and a purple Wahid waistcoat](https://posts.freesewing.org/uploads/wahidsimonvamp_345e8bb3b0.jpg) + *Drawing by @racerxmachina, Sandy* + +### Or are you more of a secret agent? +Get the suave look by making a [Jaeger](/designs/jaeger/), [Trayvon](/designs/trayvon/), and [Charlie](/designs/charlie/) and pair it with your favourite sunglasses. If the [Jaeger](/designs/jaeger/) isn’t your style, try switching it out for a [Wahid](/designs/wahid/). And if trousers don’t take your fancy, try [Penelope](/designs/penelope/) or a quarter-circle [Sandy](/designs/sandy/). + +Or maybe you want to be in your combat garb. Try combining [Sven](/designs/sven/) and [Paco](/designs/paco/). Pair them with some combat boots and a belt of your choosing. + +### Maybe you are more of fantasy dweller? +Whilst we don’t have many patterns that emulate fantasy, the [Cathrin Corset](/designs/cathrin/) is a great place to start. Combine it with a Puff-Sleeve variant of [Teagan](/designs/teagan/) and a floor-length quarter- or half-circle [Sandy](/designs/sandy/), and you are well on your way to emulating [the Cathrin cover art](/designs/cathrin/). For those of you who are feeling a little more adventurous, a little challenge for you: try combining [Cornelius](/designs/cornelius/) and [Paco](/designs/paco/) together to create satyr legs, then perhaps pair it with [Wahid](/designs/wahid/) and [Simon](/designs/simon/)/[Simone](/designs/simone/). + +### Become "that suit person." +This is a goofy outfit that can be worn to any informal party. The formal aspects of [Jaeger](/designs/jaeger/) and [Charlie](/designs/charlie/) clash beautifully with crazy patterned fabrics, which makes for a super fun Halloween outfit, which can also be worn to other parties in the future. Making a [Jaeger](/designs/jaeger/) is hard, but at least the idea is simple: find your favourite crazy fabric and use it for both pieces. You can wear a white dress shirt (or a white [Simon](/designs/simon/)) underneath. There's an option to add a [Trayvon](/designs/trayvon/) or [Benjamin](/designs/benjamin/) in a bright color as well. The possibilities are endless! + +### Or maybe you only want to make one or two garments for an easy-to-wear costume? +[Huey](/designs/huey/), [Hugo](/designs/hugo/), and [Paco](/designs/paco/) are perfect bases to create simple animal hoodies and trousers that will also be comfortable to wear. There are many animals you can try so here are a few basic alterations and ideas to get your creative brain flowing. + +#### Creating a back seam for Hugo and Huey +For simple things like back spikes for dinosaurs, you may find it useful to create a back seam in [Hugo](/designs/hugo/) or [Huey](/designs/huey/). This is simply done by cutting two back pieces instead of one on the fold. Don't forget to add seam allowance along the center back! From there you would construct your additions, such as spikes, and then baste them to one of the back pieces with right sides together. Then pin the other back piece over the top, right sides together and sew. This will now count as your single back piece in the Huey and [Hugo instructions](https://freesewing.org/docs/patterns/hugo/instructions/). + +The same can be done with the hood center piece for [Hugo](/designs/hugo/), and [Huey](/designs/huey/)'s hood already has a center back seam so no changes are required for Huey's hood. Another thing you can do is split the hood patterns in half ear to ear if you are adding stuff like ears but you may find it easier just to hand sew these elements on. + +For these particular costumes we recommend using fabrics that do not fray such as polar fleece for the body and larger additions, with felt being an option for the smaller add-ons. + +With these alterations in mind, let’s talk some ideas. + +#### Wings +This might sound odd at first, but hear me out. You can add wings by making a quarter- or half-circle and inserting them into the side seams of [Huey](/designs/huey/) and [Hugo](/designs/hugo/). If you make want to make your wings more spiky, cut-out semi-circles from the curved edge of your pattern, a plate will make this a lot quicker. Experiment! There are many types of wings and many shapes for them! +#### Bear +Who doesn’t want a ferocious bear running around a party? Create round ears for the hood and an oval shape to go on front for the underbelly. You can make a simple small tail for the back of the hoodie. +#### Cat +Everybody wants to be a cat! Well not everybody, but if you want to go as one of the Halloween staples and be comfortable, this is the way to do. Add pointed triangle ears to the hood and possibly whiskers with pipe cleaners and add a long sausage tail to the back. +#### Dinosaurs +Add horns! Add teeth! Add spikes! The possibilities are endless! If you want to keep it simple, make the center back seam adjustment and add some spikes, then add some felt triangles to represent teeth around the brim of the hood. If you are feeling more daring, why not try to emulate a triceratops head with its horns. You can also add spots to represent dinosaur skin and even a tail if you're up for it. +![A drawing of a child and an adult walking hand in hand, one wearing a bat costume, the other a dragon costume](https://posts.freesewing.org/uploads/huey_paco_costumes_8a199c7572.jpg) +*Drawing by @racerxmachina, Sandy* + +#### Dog +Add triangle ears and a wagging tail, or if that’s not to your liking you can try floppy ears. For more variation you can add spots to denote color. Possibly, be a Cruella and make it look like a Dalmatian. +#### Rabbit +Go for pink, white, yellow, brown, grey, black or any other color a bunny can be! Add oval-shaped ears and a small nose. For a tail, simply gather up a circle of fur fabric around a ball of stuffing and hand sew to your hoodie. +#### Pokemon +Now I know what you are thinking. Why is this in the regulars? Well we thought it was best to keep all the [Hugo](/designs/hugo/) and [Huey](/designs/huey/) adaptations together. So why not be inspired by [Frankie’s Bulbasaur Huey](/showcase/bulbasaur-huey/) they made for the child and make a [Huey](/designs/huey/) or [Hugo](/designs/hugo/) inspired favourite Pokemon. You can be as elaborate as you like and make ears, bulbs, and other appendages, or you can simply use the color scheme of your favourite Pokemon and add their eyes, mouth and nose on the hood. +#### Detective Pikachu +A detective that might even rival Sherlock Holmes would also be amiss without their hat. Use a [Holmes](/designs/holmes/) with a beige brown herringbone fabric and dark brown ribbon. Now what about the ears? The ears?! Why yes, Pikachu’s ears! Make a two-layered oval shape with a straight bottom. You can either cut and sew the black tops on as a seam or sew them on after you've turned the yellow parts right-side-out. Sew the two yellow layers together good sides together leaving the bottom open, trim and clip the seam allowances, then turn right-side-out. Once turned, stuff and hand sew to the ear flaps of the deerstalker before they are attached to the crown. You can sew these on after final construction if easier, just remember to close the bottom as a seam with hand-sewing before attaching to ear flaps. If you’re not aiming the exact look experiment with different colors and patterns and make a unique Detective Pikachu hat just for you! + +> *This was a collaboration between bobgeorgethethird and lucibytes!* diff --git a/markdown/org/blog/holmes-deerstalker-hat/de.md b/markdown/org/blog/holmes-deerstalker-hat/de.md new file mode 100644 index 00000000000..92b675241c4 --- /dev/null +++ b/markdown/org/blog/holmes-deerstalker-hat/de.md @@ -0,0 +1,27 @@ +--- +author: "joostdecock" +caption: "Screengrab from Bernadette Banner's YouTube tutorial for this hat" +date: "2020-02-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/02a03dd39c9e5317e89681482735e8e5929d7c2d-2748x1546.jpg" +intro: "New pattern: The Holmes Deerstalker Hat [Nicht übersetzt]" +title: "New pattern: The Holmes Deerstalker Hat [Nicht übersetzt]" +--- + + +Earlier this week, [AlfaLyr](/users/alfalyr) wrote to us to say that she had made a pattern +for the iconic Sherlock Holmes Deerstalker hat, based on this YouTube tutorial +by [Bernadette Banner](https://www.youtube.com/channel/UCSHtaUm-FjUps090S7crO4Q): + + + +Unfortunately, we were just rounding +up [the rollout of v2.2 of FreeSewing](/blog/breanna-measurements-sizes-in-2-2/), and it was +too late to squeeze in this extra pattern. + +But obviously we love this hat, not to mention that it is the perfect accessory for +our [Carlton](/designs/carlton/) and [Carlita](/designs/carlita/) patterns. So here it +is, [FreeSewing 2.3](https://github.com/freesewing/freesewing/releases/tag/v2.2.0) +with [the new Holmes pattern](/designs/holmes/). + +Enjoy! + diff --git a/markdown/org/blog/holmes-deerstalker-hat/en.md b/markdown/org/blog/holmes-deerstalker-hat/en.md new file mode 100644 index 00000000000..fc00e6b6140 --- /dev/null +++ b/markdown/org/blog/holmes-deerstalker-hat/en.md @@ -0,0 +1,27 @@ +--- +author: "joostdecock" +caption: "Screengrab from Bernadette Banner's YouTube tutorial for this hat" +date: "2020-02-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/02a03dd39c9e5317e89681482735e8e5929d7c2d-2748x1546.jpg" +intro: "New pattern: The Holmes Deerstalker Hat" +title: "New pattern: The Holmes Deerstalker Hat" +--- + + +Earlier this week, [AlfaLyr](/users/alfalyr) wrote to us to say that she had made a pattern +for the iconic Sherlock Holmes Deerstalker hat, based on this YouTube tutorial +by [Bernadette Banner](https://www.youtube.com/channel/UCSHtaUm-FjUps090S7crO4Q): + + + +Unfortunately, we were just rounding +up [the rollout of v2.2 of FreeSewing](/blog/breanna-measurements-sizes-in-2-2/), and it was +too late to squeeze in this extra pattern. + +But obviously we love this hat, not to mention that it is the perfect accessory for +our [Carlton](/designs/carlton/) and [Carlita](/designs/carlita/) patterns. So here it +is, [FreeSewing 2.3](https://github.com/freesewing/freesewing/releases/tag/v2.2.0) +with [the new Holmes pattern](/designs/holmes/). + +Enjoy! + diff --git a/markdown/org/blog/holmes-deerstalker-hat/es.md b/markdown/org/blog/holmes-deerstalker-hat/es.md new file mode 100644 index 00000000000..6c80acfee95 --- /dev/null +++ b/markdown/org/blog/holmes-deerstalker-hat/es.md @@ -0,0 +1,27 @@ +--- +author: "joostdecock" +caption: "Screengrab from Bernadette Banner's YouTube tutorial for this hat" +date: "2020-02-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/02a03dd39c9e5317e89681482735e8e5929d7c2d-2748x1546.jpg" +intro: "New pattern: The Holmes Deerstalker Hat [No traducido]" +title: "New pattern: The Holmes Deerstalker Hat [No traducido]" +--- + + +Earlier this week, [AlfaLyr](/users/alfalyr) wrote to us to say that she had made a pattern +for the iconic Sherlock Holmes Deerstalker hat, based on this YouTube tutorial +by [Bernadette Banner](https://www.youtube.com/channel/UCSHtaUm-FjUps090S7crO4Q): + + + +Unfortunately, we were just rounding +up [the rollout of v2.2 of FreeSewing](/blog/breanna-measurements-sizes-in-2-2/), and it was +too late to squeeze in this extra pattern. + +But obviously we love this hat, not to mention that it is the perfect accessory for +our [Carlton](/designs/carlton/) and [Carlita](/designs/carlita/) patterns. So here it +is, [FreeSewing 2.3](https://github.com/freesewing/freesewing/releases/tag/v2.2.0) +with [the new Holmes pattern](/designs/holmes/). + +Enjoy! + diff --git a/markdown/org/blog/holmes-deerstalker-hat/fr.md b/markdown/org/blog/holmes-deerstalker-hat/fr.md new file mode 100644 index 00000000000..99f3809ab15 --- /dev/null +++ b/markdown/org/blog/holmes-deerstalker-hat/fr.md @@ -0,0 +1,21 @@ +--- +author: "joostdecock" +caption: "Aperçu issu du tutoriel YouTube de Bernadette Banner pour ce chapeau" +date: "2020-02-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/02a03dd39c9e5317e89681482735e8e5929d7c2d-2748x1546.jpg" +intro: "Plus tôt cette semaine, AlfaLyr nous a écrit pour dire qu'elle avait fait un patron pour le chapeau emblématique Deerstalker de Sherlock Holmes, basé sur ce tutoriel YouTube de Banner Bernadette :" +title: "Nouveau patron : Chapeau Deerstalker de Sherlock Holmes" +--- + + +Plus tôt cette semaine, [AlfaLyr](/users/alfalyr) nous a écrit pour dire qu'elle avait fait un patron pour le chapeau emblématique Deerstalker de Sherlock Holmes, basé sur ce tutoriel YouTube de [Banner Bernadette](https://www.youtube.com/channel/UCSHtaUm-FjUps090S7crO4Q): + + + +Malheureusement, nous avions déjà fait le récap sur [le déploiement de la v2.2 de FreeSewing](/blog/breanna-measurements-sizes-in-2-2/), et il était trop tard pour intégrer ce nouveau modèle. + +Mais bien sûr nous aimons ce chapeau, sans mentionner que c'est l'accessoire parfait pour nos patrons [Carlton](/designs/carlton/) et [Carlita](/designs/carlita/). Donc voici la mise à jour [FreeSewing 2.3](https://github.com/freesewing/freesewing/releases/tag/v2.2.0) avec [le nouveau patron Holmes](/designs/holmes/). + +Profitez bien ! + + diff --git a/markdown/org/blog/holmes-deerstalker-hat/nl.md b/markdown/org/blog/holmes-deerstalker-hat/nl.md new file mode 100644 index 00000000000..402add381f9 --- /dev/null +++ b/markdown/org/blog/holmes-deerstalker-hat/nl.md @@ -0,0 +1,27 @@ +--- +author: "joostdecock" +caption: "Screengrab from Bernadette Banner's YouTube tutorial for this hat" +date: "2020-02-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/02a03dd39c9e5317e89681482735e8e5929d7c2d-2748x1546.jpg" +intro: "New pattern: The Holmes Deerstalker Hat [Niet vertaald]" +title: "New pattern: The Holmes Deerstalker Hat [Niet vertaald]" +--- + + +Earlier this week, [AlfaLyr](/users/alfalyr) wrote to us to say that she had made a pattern +for the iconic Sherlock Holmes Deerstalker hat, based on this YouTube tutorial +by [Bernadette Banner](https://www.youtube.com/channel/UCSHtaUm-FjUps090S7crO4Q): + + + +Unfortunately, we were just rounding +up [the rollout of v2.2 of FreeSewing](/blog/breanna-measurements-sizes-in-2-2/), and it was +too late to squeeze in this extra pattern. + +But obviously we love this hat, not to mention that it is the perfect accessory for +our [Carlton](/designs/carlton/) and [Carlita](/designs/carlita/) patterns. So here it +is, [FreeSewing 2.3](https://github.com/freesewing/freesewing/releases/tag/v2.2.0) +with [the new Holmes pattern](/designs/holmes/). + +Enjoy! + diff --git a/markdown/org/blog/huey-hoodie-beta/de.md b/markdown/org/blog/huey-hoodie-beta/de.md new file mode 100644 index 00000000000..2f4d8cfe816 --- /dev/null +++ b/markdown/org/blog/huey-hoodie-beta/de.md @@ -0,0 +1,46 @@ +--- +author: "joostdecock" +caption: "Dieser lila Huey Hoodie ist der erste seiner Art. Nun sind Sie an der Reihe" +date: "2017-10-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3be185a211486823b678af97710274804fe86dcf-2048x2048.jpg" +intro: "Willkommen bei Huey , dem jüngsten Mitglied in unserer Schnittmusterfamilie. Huey ist ein Hoodie mit Reißverschluss und mit optionalen Taschen auf der Vorderseite. Ich habe mir selbst einen gemacht -- den da auf dem Bild da oben -- und hab ihn seither nicht mehr ausgezogen." +title: "Der Hoodie \"Huey\" ist jetzt als Beta-Version erhältlich. Was die Frage aufwirft, was es bedeutet, wenn ein Schnittmuster in der Beta-Phase ist?" +--- + + +Willkommen bei [Huey](/patterns/huey), dem jüngsten Mitglied in unserer Schnittmusterfamilie. Huey ist ein Hoodie mit Reißverschluss und mit optionalen Taschen auf der Vorderseite. Ich habe mir selbst einen gemacht -- den da auf dem Bild da oben -- und hab ihn seither nicht mehr ausgezogen. + +In der Zwischenzeit habe ich mich gefragt, warum zum Teufel ich dieses Schnittmuster nicht schon früher entworfen habe. Es ist so angenehm zu tragen. + +## Ab sofort verfügbar, in Beta-Version + +Das Schnittmuster ist [gleich hier](/patterns/huey) verfügbar, für den Moment aber es ist im Beta-Stadium. + +Um herauszufinden, was das bedeutet - und warum ich das tue - lesen Sie einfach weiter. Aber wenn es Sie danach juckt, das zu machen, müssen Sie Folgendes über den Betastatus wissen: + + - Beta-Schnittmustern fehlt die Dokumentation + - Beta-Schnittmuster wurden (bisher) nur von wenigen Personen genutzt + +Im Laufe der Zeit und wenn diese Probleme gelöst sind, wird Huey von der Beta- zur Core-Version übergeben werden. + +## Warum also diese Beta-Versions-Geschichte + +Wie ich in [meinem Round-up-Post des letzten Monats](/blog/roundup-2017-09/) erklärt habe, ist das Testen von Schnittmustern für mich ein echter Engpass. + +Eine Reihe von Leuten hat sich gemeldet und angeboten, bei den Tests zu helfen (vielen Dank dafür), was mich dazu veranlasst hat, darüber nachzudenken, wie dies in der Praxis funktionieren würde. + +Zum Beispiel habe ich Huey bis zum Punkt *es funktioniert für mich* gebracht und ich bin etwas zuversichtlich, dass es auch für andere funktioniert. Dennoch ersetzt nichts einen Test in der realen Welt, daher wäre es schön, wenn ein paar Leute es schaffen könnten. + +Anstatt die Gelegenheit zu geben, Huey mit einer Handvoll Leute zu testen, die sich gemeldet haben, dachte ich mir, ich könnte ihn auch für alle anderen, die sich dazu berufen fühlen, öffnen. + +Und um darauf hinzuweisen, dass dieses Schnittmuster nicht so straßenerprobt ist wie die anderen, behalte ich es im Beta-Namensraum, wo es tatsächlich entwickelt wird, und das wird auch auf der Schnittmuster-Seite auftauchen. Keine Änderungen erforderlich. + +## Frühzeitig veröffentlichen, oft veröffentlichen + +In Zukunft werde ich so bald wie möglich Schnittmuster veröffentlichen und an der Fertigstellung der Dokumentation arbeiten, solange sie noch in der Beta-Phase sind. + +Ich halte das für einen guten Weg und halte mich an das Mantra *früh veröffentlichen, oft veröffentlichen* von Open-Source-Software. + +Wenn Sie der Meinung sind, dass das eine schlechte (oder sehr gute) Idee ist, teilen Sie mir das bitte in den Kommentaren unten mit. + + diff --git a/markdown/org/blog/huey-hoodie-beta/en.md b/markdown/org/blog/huey-hoodie-beta/en.md new file mode 100644 index 00000000000..a890775bbfd --- /dev/null +++ b/markdown/org/blog/huey-hoodie-beta/en.md @@ -0,0 +1,52 @@ +--- +author: "joostdecock" +caption: "This purple Huey hoodie is the first of its kind. Now it's your turn" +date: "2017-10-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3be185a211486823b678af97710274804fe86dcf-2048x2048.jpg" +intro: "The Huey Hoodie is now available in beta. Which begs the question, what does it mean for a pattern to be in Beta?" +title: "The Huey Hoodie is now available in beta. Which begs the question, what does it mean for a pattern to be in Beta?" +--- + +Welcome to [Huey](/patterns/huey), the youngest member in our pattern family. +Huey is a zip-up hoodie with an (optional) front pouch. I've made one for myself -- the one in the picture above -- +and I have yet to take it off since. + +Meanwhile, I've been wondering why the hell I didn't design this pattern sooner. +It's just that nice to wear. + +## Available as of now, in beta + +The pattern is available [right here](/patterns/huey), right now, but it's in beta. + +To find out what that means -- and why I'm doing this -- just continue reading. +But if you're itching to make this, here's is what you need to know about beta status: + + - Beta patterns lack documentation + - Beta patterns are made by few people (so far) + +As time goes by and these issues are resolved, Huey will move from beta to core. + +## So why this beta business + +As I explained in [my round-up post of last month](/blog/roundup-2017-09/), pattern testing is a real bottleneck for me. + +A number of people came forward, offering to help out with testing (thank you very much for that) +which lead me to consider how this would work in practice. + +Like, I've got Huey to point of *it works for me* and I am somewhat confident that it will work for others too. +Stil, nothing replaces a real-world test so it would be nice if a couple of people could make it. + +Rather than given the opportunity to test Huey to a handful of people who came forward, I figured I might as well +open it up to everyone who feels so inclined. + +And to indicate that this pattern isn't as road-tested as the others, I'm keeping it in the beta namespace, where it actually is developed +and this will also show up on the pattern page. No changes required. + +## Release early, release often + +Going forward, I will release patterns as soon as I can, and work on completing the documentation while they remain in beta. + +I think it's a good way to go, and adheres to the *release early, release often* mantra of open source software. + +If you think that's a bad idea (or a very good idea), make sure to tell me about it in the comments below. + diff --git a/markdown/org/blog/huey-hoodie-beta/es.md b/markdown/org/blog/huey-hoodie-beta/es.md new file mode 100644 index 00000000000..8d4157c8a4d --- /dev/null +++ b/markdown/org/blog/huey-hoodie-beta/es.md @@ -0,0 +1,52 @@ +--- +author: "joostdecock" +caption: "This purple Huey hoodie is the first of its kind. Now it's your turn" +date: "2017-10-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3be185a211486823b678af97710274804fe86dcf-2048x2048.jpg" +intro: "The Huey Hoodie is now available in beta. Which begs the question, what does it mean for a pattern to be in Beta? [No traducido]" +title: "The Huey Hoodie is now available in beta. Which begs the question, what does it mean for a pattern to be in Beta? [No traducido]" +--- + +Welcome to [Huey](/patterns/huey), the youngest member in our pattern family. +Huey is a zip-up hoodie with an (optional) front pouch. I've made one for myself -- the one in the picture above -- +and I have yet to take it off since. + +Meanwhile, I've been wondering why the hell I didn't design this pattern sooner. +It's just that nice to wear. + +## Available as of now, in beta + +The pattern is available [right here](/patterns/huey), right now, but it's in beta. + +To find out what that means -- and why I'm doing this -- just continue reading. +But if you're itching to make this, here's is what you need to know about beta status: + + - Beta patterns lack documentation + - Beta patterns are made by few people (so far) + +As time goes by and these issues are resolved, Huey will move from beta to core. + +## So why this beta business + +As I explained in [my round-up post of last month](/blog/roundup-2017-09/), pattern testing is a real bottleneck for me. + +A number of people came forward, offering to help out with testing (thank you very much for that) +which lead me to consider how this would work in practice. + +Like, I've got Huey to point of *it works for me* and I am somewhat confident that it will work for others too. +Stil, nothing replaces a real-world test so it would be nice if a couple of people could make it. + +Rather than given the opportunity to test Huey to a handful of people who came forward, I figured I might as well +open it up to everyone who feels so inclined. + +And to indicate that this pattern isn't as road-tested as the others, I'm keeping it in the beta namespace, where it actually is developed +and this will also show up on the pattern page. No changes required. + +## Release early, release often + +Going forward, I will release patterns as soon as I can, and work on completing the documentation while they remain in beta. + +I think it's a good way to go, and adheres to the *release early, release often* mantra of open source software. + +If you think that's a bad idea (or a very good idea), make sure to tell me about it in the comments below. + diff --git a/markdown/org/blog/huey-hoodie-beta/fr.md b/markdown/org/blog/huey-hoodie-beta/fr.md new file mode 100644 index 00000000000..a47012a8831 --- /dev/null +++ b/markdown/org/blog/huey-hoodie-beta/fr.md @@ -0,0 +1,52 @@ +--- +author: "joostdecock" +caption: "This purple Huey hoodie is the first of its kind. Now it's your turn" +date: "2017-10-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3be185a211486823b678af97710274804fe86dcf-2048x2048.jpg" +intro: "The Huey Hoodie is now available in beta. Which begs the question, what does it mean for a pattern to be in Beta? [Non traduit]" +title: "The Huey Hoodie is now available in beta. Which begs the question, what does it mean for a pattern to be in Beta? [Non traduit]" +--- + +Welcome to [Huey](/patterns/huey), the youngest member in our pattern family. +Huey is a zip-up hoodie with an (optional) front pouch. I've made one for myself -- the one in the picture above -- +and I have yet to take it off since. + +Meanwhile, I've been wondering why the hell I didn't design this pattern sooner. +It's just that nice to wear. + +## Available as of now, in beta + +The pattern is available [right here](/patterns/huey), right now, but it's in beta. + +To find out what that means -- and why I'm doing this -- just continue reading. +But if you're itching to make this, here's is what you need to know about beta status: + + - Beta patterns lack documentation + - Beta patterns are made by few people (so far) + +As time goes by and these issues are resolved, Huey will move from beta to core. + +## So why this beta business + +As I explained in [my round-up post of last month](/blog/roundup-2017-09/), pattern testing is a real bottleneck for me. + +A number of people came forward, offering to help out with testing (thank you very much for that) +which lead me to consider how this would work in practice. + +Like, I've got Huey to point of *it works for me* and I am somewhat confident that it will work for others too. +Stil, nothing replaces a real-world test so it would be nice if a couple of people could make it. + +Rather than given the opportunity to test Huey to a handful of people who came forward, I figured I might as well +open it up to everyone who feels so inclined. + +And to indicate that this pattern isn't as road-tested as the others, I'm keeping it in the beta namespace, where it actually is developed +and this will also show up on the pattern page. No changes required. + +## Release early, release often + +Going forward, I will release patterns as soon as I can, and work on completing the documentation while they remain in beta. + +I think it's a good way to go, and adheres to the *release early, release often* mantra of open source software. + +If you think that's a bad idea (or a very good idea), make sure to tell me about it in the comments below. + diff --git a/markdown/org/blog/huey-hoodie-beta/nl.md b/markdown/org/blog/huey-hoodie-beta/nl.md new file mode 100644 index 00000000000..1252747336b --- /dev/null +++ b/markdown/org/blog/huey-hoodie-beta/nl.md @@ -0,0 +1,52 @@ +--- +author: "joostdecock" +caption: "This purple Huey hoodie is the first of its kind. Now it's your turn" +date: "2017-10-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3be185a211486823b678af97710274804fe86dcf-2048x2048.jpg" +intro: "The Huey Hoodie is now available in beta. Which begs the question, what does it mean for a pattern to be in Beta? [Niet vertaald]" +title: "The Huey Hoodie is now available in beta. Which begs the question, what does it mean for a pattern to be in Beta? [Niet vertaald]" +--- + +Welcome to [Huey](/patterns/huey), the youngest member in our pattern family. +Huey is a zip-up hoodie with an (optional) front pouch. I've made one for myself -- the one in the picture above -- +and I have yet to take it off since. + +Meanwhile, I've been wondering why the hell I didn't design this pattern sooner. +It's just that nice to wear. + +## Available as of now, in beta + +The pattern is available [right here](/patterns/huey), right now, but it's in beta. + +To find out what that means -- and why I'm doing this -- just continue reading. +But if you're itching to make this, here's is what you need to know about beta status: + + - Beta patterns lack documentation + - Beta patterns are made by few people (so far) + +As time goes by and these issues are resolved, Huey will move from beta to core. + +## So why this beta business + +As I explained in [my round-up post of last month](/blog/roundup-2017-09/), pattern testing is a real bottleneck for me. + +A number of people came forward, offering to help out with testing (thank you very much for that) +which lead me to consider how this would work in practice. + +Like, I've got Huey to point of *it works for me* and I am somewhat confident that it will work for others too. +Stil, nothing replaces a real-world test so it would be nice if a couple of people could make it. + +Rather than given the opportunity to test Huey to a handful of people who came forward, I figured I might as well +open it up to everyone who feels so inclined. + +And to indicate that this pattern isn't as road-tested as the others, I'm keeping it in the beta namespace, where it actually is developed +and this will also show up on the pattern page. No changes required. + +## Release early, release often + +Going forward, I will release patterns as soon as I can, and work on completing the documentation while they remain in beta. + +I think it's a good way to go, and adheres to the *release early, release often* mantra of open source software. + +If you think that's a bad idea (or a very good idea), make sure to tell me about it in the comments below. + diff --git a/markdown/org/blog/lets-meet-up-in-2019/de.md b/markdown/org/blog/lets-meet-up-in-2019/de.md new file mode 100644 index 00000000000..d8dddbccb22 --- /dev/null +++ b/markdown/org/blog/lets-meet-up-in-2019/de.md @@ -0,0 +1,61 @@ +--- +author: "joostdecock" +caption: "Als introvertierter Mensch sage ich das nicht oft, aber ich würde Sie eigentlich gerne kennenlernen." +date: "2018-12-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8b5fdb232675b32c7c08b59ffc57e9b9da31f02f-1920x1078.jpg" +intro: "Da niemand einen Stichtag am Silvesterabend mag, schließt Freewing traditionell am 10. Dezember sein Jahr ab. Das bedeutet, dass es jetzt an der Zeit ist, über die Vergangenheit nachzudenken und sich auf das zu freuen, was vor uns liegt." +title: "Wir treffen uns im 2019! Und andere Jahresendbetrachtungen" +--- + + +Da niemand einen Stichtag am Silvesterabend mag, schließt Freewing traditionell am 10. Dezember sein Jahr ab. Das bedeutet, dass es jetzt an der Zeit ist, über die Vergangenheit nachzudenken und sich auf das zu freuen, was vor uns liegt. + +## Was halten Sie von einem Treffen? + +Ich springe gleich rein: Im Jahr 2019 möchte ich ein Treffen mit den FreeSewing Unterstützern und Mitwirkenden organisieren, um die Zukunft des Projekts zu diskutieren, Ideen und Erfahrungen austauschen. Die Einladung steht allen offen, also zögern Sie nicht, diesen Beitrag mit anderen zu teilen. + +Ich kann Ihnen noch keine Einzelheiten nennen. Nicht, weil ich faul bin (was ich bin, aber das ist eine andere Geschichte), sondern weil ich von Ihnen hören möchte, was Sie tun/hören/reden möchten über. + +Wenn es sich also nach etwas anhört, an dem Sie gerne teilnehmen möchten, teilen Sie uns bitte Ihre Gedanken, Ideen und Vorschläge mit. Ich habe [ein GitHub-Issue für diese Angelegenheit erstellt.](https://github.com/freesewing/meetup/issues/1) Das ist also ein guter Ort, um Ihre Beiträge zu hinterlassen. Aber auch soziale Medien sind ein guter Ort. + +Input zu was, fragen Sie sich? Nun, hier sind einige Fragen, die beantwortet werden müssen: + + - Wann werden wir das tun? Nächste Woche? August? Der letzte Blutmond vor der Abrechnung? + - Wo werden wir das tun? Im Keller deiner Mutter? Der Pfarrsaal von Oostrozebeke? London? Paris? Montreal? Mar-a-Lago? + - Wird dies eine 2-Stunden-Sache, ein Donnerstagnachmittag oder ein ganzes Wochenende sein? + - Worüber werden wir reden. Was wollen wir tun? Was möchten Sie sehen oder hören? + + +Nochmals, nichts ist in Stein gemeiselt, und ich freue mich von Ihnen zu hören, wie wir dies zu einem erinnernswerten Event gestalten. + +Seien Sie also nicht schüchtern, sondern teilen Sie sich uns mit. + +## FreeSewing 2.0 + +We have done a lot of work since freesewing.org was launched (only) 16 months ago. We've added new patterns, built a new website, and we've translated freesewing.org into 4 additional languages in order to remove knowledge of English as a barrier to using the site. + +But we actually did much more this year. For the last 6 months or so, I've been working like crazy on [freesewing 2.0.](https://github.com/freesewing/freesewing). It's a complete rewrite of pretty much every aspect of the project. My reasons for doing so are simple: With the project growing as it does, the fact that I only have two hands and 24 hours in a day is quickly becoming a bottleneck. For freesewing to thrive we must make it simpler for other people to [dive in](https://developer.freesewing.org), and get involved. + +As such, I have embarked on a journey to tackle technical debt, and simplify our technology stack. The first big hurdle was [rounded in August](/blog/announcing-freesewing-library) when the JavaScript port of our core platform reached feature parity. Since then, I have ported [several patterns](https://github.com/freesewing/patterns), and currently I am working on [a new backend](https://github.com/freesewing/backend) and [website](https://github.com/freesewing/website). + +The new setup will be faster, more modular, and easier to extend and wrap your head around. Which is crucial for our long-term growth. + +Unfortunately, this is one of those scenarios where nothing works until everything works. So while you can go to [beta.freesewing.org](https://beta.freesewing.org) now and kick the tires, it's probably going to be a bit of a downer as so much is still broken, or unfinished. + +So please bear with me as we continue this important behind-the-scenes work. Because while I can't tell you when it will be ready, I really feel it's something worth looking forward to. + +## Oh, and one more thing + +I'm more of a looking-forward than a looking-back kinda guy, but as I reflect on the year, it is clear to me that the most important thing we did with freesewing, was to team up with [our patrons](/community/who/patrons). + +Twelve months ago , [we launched our patron project](/blog/calling-all-patrons). Since then, 65 patrons — spread roughly equally among our 3 tiers of patronage — have [stepped forward to support freesewing](/patrons/join). The knock-on effects of these people making a commitment to support our work have surpassed even my most optimistic hopes. + +You may or may not know that I have [made a pledge](/docs/various/pledge) to donate all income from freesewing to charity. So this morning I transferred our entire revenue for the year (**3162.14 euros**) to [Médecins Sans Frontières](https://www.msf.org/) (Doctors Without Borders). Money that will go towards bringing relief to some of the most vulnerable people on this planet. + +You made that happen, and if it brings a fraction of the joy to your heart as it does to mine, you'll understand how much your patronage means to me. + +I have, for several years now, put a lot of time and effort into freesewing. And I can honestly say that I've never worked harder on this than I am doing now. But at the same time, it has been easier than ever for me to find the motivation to do so. Every contribution, no matter how small, is like a small patch in a warm blanket of support under which freesewing can thrive. + +So thank you for all this. And let's try to do (even) better next year. + + diff --git a/markdown/org/blog/lets-meet-up-in-2019/en.md b/markdown/org/blog/lets-meet-up-in-2019/en.md new file mode 100644 index 00000000000..bbf93b68a46 --- /dev/null +++ b/markdown/org/blog/lets-meet-up-in-2019/en.md @@ -0,0 +1,109 @@ +--- +author: "joostdecock" +caption: "As an introvert I don't say this often, but I'd actually like to meet you guys." +date: "2018-12-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8b5fdb232675b32c7c08b59ffc57e9b9da31f02f-1920x1078.jpg" +intro: "Let's meet up in 2019! And other end-of-year musings" +title: "Let's meet up in 2019! And other end-of-year musings" +--- + + +Because nobody likes a deadline on New Year's Eve, freesewing traditionally +wraps up its year on December 10th. Which means that now is the time to +reflect on the past, and look forward to what lies ahead. + +## How do you feel about meeting up? + +I'll jump right in: In 2019 I would like to organize a get-together +of freesewing supporters and contributors to discuss the future of the project, +exchange ideas and experiences. The invitation is open to everyone, so feel free +to share this post with others. + +I can't give you any details yet. Not because I'm lazy (which I am, but that's a +different story) but because I want to hear from you what you'd like to do/hear/talk +about. + +So if this sounds like something you'd like to attend, +please share your thoughts, ideas, and suggestions. I've created +[a GitHub issue for the matter](https://github.com/freesewing/meetup/issues/1) +so that's a good place to leave your input. But social media is a good place too. + +Input on what, you ask? Well, here's some questions that need answers: + + - When are we going to do this? Next week? August? The last blood moon before the reckoning? + - Where are we going to do this? Your mom's basement? The parish hall of Oostrozebeke? London? Paris? Montreal? Mar-a-Lago? + - Is this going to be a 2-hour thing, a Thursday afternoon, or a full weekend? + - What are we going to talk about. What are we going to do? What would you like to see or hear? + + +Once again, nothing is set in stone, and I'm looking forward to hearing from you guys how +we could make this memorable. + +So don't be shy, just share. + +## freesewing 2.0 + +We have done a lot of work since freesewing.org was launched (only) +16 months ago. We've added new patterns, built a new website, and we've +translated freesewing.org into 4 additional languages in order to remove +knowledge of English as a barrier to using the site. + +But we actually did much more this year. For the last 6 months or so, I've been +working like crazy +on [freesewing 2.0.](https://github.com/freesewing/freesewing). +It's a complete rewrite of pretty much +every aspect of the project. My reasons for doing so are simple: With the project +growing as it does, the fact that I only have two hands and 24 hours in a day is +quickly becoming a bottleneck. For freesewing to thrive we must make it simpler +for other people to [dive in](https://developer.freesewing.org), and get involved. + +As such, I have embarked on a journey to tackle technical debt, and simplify our +technology stack. The first big hurdle +was [rounded in August](/blog/announcing-freesewing-library) when the JavaScript +port of our core platform reached feature parity. Since then, I have +ported [several patterns](https://github.com/freesewing/patterns), +and currently I am working +on [a new backend](https://github.com/freesewing/backend) and [website](https://github.com/freesewing/website). + +The new setup will be faster, more modular, and easier to extend and wrap your +head around. Which is crucial for our long-term growth. + +Unfortunately, this is one of those scenarios where nothing works until everything works. +So while you can go +to [beta.freesewing.org](https://beta.freesewing.org) now and kick the tires, +it's probably going to be a bit of a downer as so much is still broken, or unfinished. + +So please bear with me as we continue this important behind-the-scenes work. +Because while I can't tell you when it will be ready, +I really feel it's something worth looking forward to. + +## Oh, and one more thing + +I'm more of a looking-forward than a looking-back kinda guy, but as I reflect on the year, +it is clear to me that the most important thing we did with freesewing, was to team up +with [our patrons](/community/who/patrons). + +Twelve months ago +, [we launched our patron project](/blog/calling-all-patrons). Since then, 65 patrons +— spread roughly equally among our 3 tiers of patronage — +have [stepped forward to support freesewing](/patrons/join). +The knock-on effects of these people making a commitment to support our work have surpassed +even my most optimistic hopes. + +You may or may not know that I +have [made a pledge](/docs/various/pledge) to donate all income from freesewing to charity. +So this morning I transferred our entire revenue for the year (**3162.14 euros**) +to [Médecins Sans Frontières](https://www.msf.org/) (Doctors Without Borders). +Money that will go towards bringing relief to some of the most vulnerable people on this planet. + +You made that happen, and if it brings a fraction of the joy to your heart as it does to mine, +you'll understand how much your patronage means to me. + +I have, for several years now, put a lot of time and effort into freesewing. +And I can honestly say that I've never worked harder on this than I am doing now. +But at the same time, it has been easier than ever for me to find the motivation to do so. +Every contribution, no matter how small, is like a small patch in a warm blanket of support +under which freesewing can thrive. + +So thank you for all this. And let's try to do (even) better next year. + diff --git a/markdown/org/blog/lets-meet-up-in-2019/es.md b/markdown/org/blog/lets-meet-up-in-2019/es.md new file mode 100644 index 00000000000..5af4f2ff421 --- /dev/null +++ b/markdown/org/blog/lets-meet-up-in-2019/es.md @@ -0,0 +1,109 @@ +--- +author: "joostdecock" +caption: "As an introvert I don't say this often, but I'd actually like to meet you guys." +date: "2018-12-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8b5fdb232675b32c7c08b59ffc57e9b9da31f02f-1920x1078.jpg" +intro: "Let's meet up in 2019! And other end-of-year musings [No traducido]" +title: "Let's meet up in 2019! And other end-of-year musings [No traducido]" +--- + + +Because nobody likes a deadline on New Year's Eve, freesewing traditionally +wraps up its year on December 10th. Which means that now is the time to +reflect on the past, and look forward to what lies ahead. + +## How do you feel about meeting up? + +I'll jump right in: In 2019 I would like to organize a get-together +of freesewing supporters and contributors to discuss the future of the project, +exchange ideas and experiences. The invitation is open to everyone, so feel free +to share this post with others. + +I can't give you any details yet. Not because I'm lazy (which I am, but that's a +different story) but because I want to hear from you what you'd like to do/hear/talk +about. + +So if this sounds like something you'd like to attend, +please share your thoughts, ideas, and suggestions. I've created +[a GitHub issue for the matter](https://github.com/freesewing/meetup/issues/1) +so that's a good place to leave your input. But social media is a good place too. + +Input on what, you ask? Well, here's some questions that need answers: + + - When are we going to do this? Next week? August? The last blood moon before the reckoning? + - Where are we going to do this? Your mom's basement? The parish hall of Oostrozebeke? London? Paris? Montreal? Mar-a-Lago? + - Is this going to be a 2-hour thing, a Thursday afternoon, or a full weekend? + - What are we going to talk about. What are we going to do? What would you like to see or hear? + + +Once again, nothing is set in stone, and I'm looking forward to hearing from you guys how +we could make this memorable. + +So don't be shy, just share. + +## freesewing 2.0 + +We have done a lot of work since freesewing.org was launched (only) +16 months ago. We've added new patterns, built a new website, and we've +translated freesewing.org into 4 additional languages in order to remove +knowledge of English as a barrier to using the site. + +But we actually did much more this year. For the last 6 months or so, I've been +working like crazy +on [freesewing 2.0.](https://github.com/freesewing/freesewing). +It's a complete rewrite of pretty much +every aspect of the project. My reasons for doing so are simple: With the project +growing as it does, the fact that I only have two hands and 24 hours in a day is +quickly becoming a bottleneck. For freesewing to thrive we must make it simpler +for other people to [dive in](https://developer.freesewing.org), and get involved. + +As such, I have embarked on a journey to tackle technical debt, and simplify our +technology stack. The first big hurdle +was [rounded in August](/blog/announcing-freesewing-library) when the JavaScript +port of our core platform reached feature parity. Since then, I have +ported [several patterns](https://github.com/freesewing/patterns), +and currently I am working +on [a new backend](https://github.com/freesewing/backend) and [website](https://github.com/freesewing/website). + +The new setup will be faster, more modular, and easier to extend and wrap your +head around. Which is crucial for our long-term growth. + +Unfortunately, this is one of those scenarios where nothing works until everything works. +So while you can go +to [beta.freesewing.org](https://beta.freesewing.org) now and kick the tires, +it's probably going to be a bit of a downer as so much is still broken, or unfinished. + +So please bear with me as we continue this important behind-the-scenes work. +Because while I can't tell you when it will be ready, +I really feel it's something worth looking forward to. + +## Oh, and one more thing + +I'm more of a looking-forward than a looking-back kinda guy, but as I reflect on the year, +it is clear to me that the most important thing we did with freesewing, was to team up +with [our patrons](/community/who/patrons). + +Twelve months ago +, [we launched our patron project](/blog/calling-all-patrons). Since then, 65 patrons +— spread roughly equally among our 3 tiers of patronage — +have [stepped forward to support freesewing](/patrons/join). +The knock-on effects of these people making a commitment to support our work have surpassed +even my most optimistic hopes. + +You may or may not know that I +have [made a pledge](/docs/various/pledge) to donate all income from freesewing to charity. +So this morning I transferred our entire revenue for the year (**3162.14 euros**) +to [Médecins Sans Frontières](https://www.msf.org/) (Doctors Without Borders). +Money that will go towards bringing relief to some of the most vulnerable people on this planet. + +You made that happen, and if it brings a fraction of the joy to your heart as it does to mine, +you'll understand how much your patronage means to me. + +I have, for several years now, put a lot of time and effort into freesewing. +And I can honestly say that I've never worked harder on this than I am doing now. +But at the same time, it has been easier than ever for me to find the motivation to do so. +Every contribution, no matter how small, is like a small patch in a warm blanket of support +under which freesewing can thrive. + +So thank you for all this. And let's try to do (even) better next year. + diff --git a/markdown/org/blog/lets-meet-up-in-2019/fr.md b/markdown/org/blog/lets-meet-up-in-2019/fr.md new file mode 100644 index 00000000000..20685128f87 --- /dev/null +++ b/markdown/org/blog/lets-meet-up-in-2019/fr.md @@ -0,0 +1,109 @@ +--- +author: "joostdecock" +caption: "As an introvert I don't say this often, but I'd actually like to meet you guys." +date: "2018-12-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8b5fdb232675b32c7c08b59ffc57e9b9da31f02f-1920x1078.jpg" +intro: "Let's meet up in 2019! And other end-of-year musings [Non traduit]" +title: "Let's meet up in 2019! And other end-of-year musings [Non traduit]" +--- + + +Because nobody likes a deadline on New Year's Eve, freesewing traditionally +wraps up its year on December 10th. Which means that now is the time to +reflect on the past, and look forward to what lies ahead. + +## How do you feel about meeting up? + +I'll jump right in: In 2019 I would like to organize a get-together +of freesewing supporters and contributors to discuss the future of the project, +exchange ideas and experiences. The invitation is open to everyone, so feel free +to share this post with others. + +I can't give you any details yet. Not because I'm lazy (which I am, but that's a +different story) but because I want to hear from you what you'd like to do/hear/talk +about. + +So if this sounds like something you'd like to attend, +please share your thoughts, ideas, and suggestions. I've created +[a GitHub issue for the matter](https://github.com/freesewing/meetup/issues/1) +so that's a good place to leave your input. But social media is a good place too. + +Input on what, you ask? Well, here's some questions that need answers: + + - When are we going to do this? Next week? August? The last blood moon before the reckoning? + - Where are we going to do this? Your mom's basement? The parish hall of Oostrozebeke? London? Paris? Montreal? Mar-a-Lago? + - Is this going to be a 2-hour thing, a Thursday afternoon, or a full weekend? + - What are we going to talk about. What are we going to do? What would you like to see or hear? + + +Once again, nothing is set in stone, and I'm looking forward to hearing from you guys how +we could make this memorable. + +So don't be shy, just share. + +## freesewing 2.0 + +We have done a lot of work since freesewing.org was launched (only) +16 months ago. We've added new patterns, built a new website, and we've +translated freesewing.org into 4 additional languages in order to remove +knowledge of English as a barrier to using the site. + +But we actually did much more this year. For the last 6 months or so, I've been +working like crazy +on [freesewing 2.0.](https://github.com/freesewing/freesewing). +It's a complete rewrite of pretty much +every aspect of the project. My reasons for doing so are simple: With the project +growing as it does, the fact that I only have two hands and 24 hours in a day is +quickly becoming a bottleneck. For freesewing to thrive we must make it simpler +for other people to [dive in](https://developer.freesewing.org), and get involved. + +As such, I have embarked on a journey to tackle technical debt, and simplify our +technology stack. The first big hurdle +was [rounded in August](/blog/announcing-freesewing-library) when the JavaScript +port of our core platform reached feature parity. Since then, I have +ported [several patterns](https://github.com/freesewing/patterns), +and currently I am working +on [a new backend](https://github.com/freesewing/backend) and [website](https://github.com/freesewing/website). + +The new setup will be faster, more modular, and easier to extend and wrap your +head around. Which is crucial for our long-term growth. + +Unfortunately, this is one of those scenarios where nothing works until everything works. +So while you can go +to [beta.freesewing.org](https://beta.freesewing.org) now and kick the tires, +it's probably going to be a bit of a downer as so much is still broken, or unfinished. + +So please bear with me as we continue this important behind-the-scenes work. +Because while I can't tell you when it will be ready, +I really feel it's something worth looking forward to. + +## Oh, and one more thing + +I'm more of a looking-forward than a looking-back kinda guy, but as I reflect on the year, +it is clear to me that the most important thing we did with freesewing, was to team up +with [our patrons](/community/who/patrons). + +Twelve months ago +, [we launched our patron project](/blog/calling-all-patrons). Since then, 65 patrons +— spread roughly equally among our 3 tiers of patronage — +have [stepped forward to support freesewing](/patrons/join). +The knock-on effects of these people making a commitment to support our work have surpassed +even my most optimistic hopes. + +You may or may not know that I +have [made a pledge](/docs/various/pledge) to donate all income from freesewing to charity. +So this morning I transferred our entire revenue for the year (**3162.14 euros**) +to [Médecins Sans Frontières](https://www.msf.org/) (Doctors Without Borders). +Money that will go towards bringing relief to some of the most vulnerable people on this planet. + +You made that happen, and if it brings a fraction of the joy to your heart as it does to mine, +you'll understand how much your patronage means to me. + +I have, for several years now, put a lot of time and effort into freesewing. +And I can honestly say that I've never worked harder on this than I am doing now. +But at the same time, it has been easier than ever for me to find the motivation to do so. +Every contribution, no matter how small, is like a small patch in a warm blanket of support +under which freesewing can thrive. + +So thank you for all this. And let's try to do (even) better next year. + diff --git a/markdown/org/blog/lets-meet-up-in-2019/nl.md b/markdown/org/blog/lets-meet-up-in-2019/nl.md new file mode 100644 index 00000000000..5fa09868eb1 --- /dev/null +++ b/markdown/org/blog/lets-meet-up-in-2019/nl.md @@ -0,0 +1,109 @@ +--- +author: "joostdecock" +caption: "As an introvert I don't say this often, but I'd actually like to meet you guys." +date: "2018-12-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8b5fdb232675b32c7c08b59ffc57e9b9da31f02f-1920x1078.jpg" +intro: "Let's meet up in 2019! And other end-of-year musings [Niet vertaald]" +title: "Let's meet up in 2019! And other end-of-year musings [Niet vertaald]" +--- + + +Because nobody likes a deadline on New Year's Eve, freesewing traditionally +wraps up its year on December 10th. Which means that now is the time to +reflect on the past, and look forward to what lies ahead. + +## How do you feel about meeting up? + +I'll jump right in: In 2019 I would like to organize a get-together +of freesewing supporters and contributors to discuss the future of the project, +exchange ideas and experiences. The invitation is open to everyone, so feel free +to share this post with others. + +I can't give you any details yet. Not because I'm lazy (which I am, but that's a +different story) but because I want to hear from you what you'd like to do/hear/talk +about. + +So if this sounds like something you'd like to attend, +please share your thoughts, ideas, and suggestions. I've created +[a GitHub issue for the matter](https://github.com/freesewing/meetup/issues/1) +so that's a good place to leave your input. But social media is a good place too. + +Input on what, you ask? Well, here's some questions that need answers: + + - When are we going to do this? Next week? August? The last blood moon before the reckoning? + - Where are we going to do this? Your mom's basement? The parish hall of Oostrozebeke? London? Paris? Montreal? Mar-a-Lago? + - Is this going to be a 2-hour thing, a Thursday afternoon, or a full weekend? + - What are we going to talk about. What are we going to do? What would you like to see or hear? + + +Once again, nothing is set in stone, and I'm looking forward to hearing from you guys how +we could make this memorable. + +So don't be shy, just share. + +## freesewing 2.0 + +We have done a lot of work since freesewing.org was launched (only) +16 months ago. We've added new patterns, built a new website, and we've +translated freesewing.org into 4 additional languages in order to remove +knowledge of English as a barrier to using the site. + +But we actually did much more this year. For the last 6 months or so, I've been +working like crazy +on [freesewing 2.0.](https://github.com/freesewing/freesewing). +It's a complete rewrite of pretty much +every aspect of the project. My reasons for doing so are simple: With the project +growing as it does, the fact that I only have two hands and 24 hours in a day is +quickly becoming a bottleneck. For freesewing to thrive we must make it simpler +for other people to [dive in](https://developer.freesewing.org), and get involved. + +As such, I have embarked on a journey to tackle technical debt, and simplify our +technology stack. The first big hurdle +was [rounded in August](/blog/announcing-freesewing-library) when the JavaScript +port of our core platform reached feature parity. Since then, I have +ported [several patterns](https://github.com/freesewing/patterns), +and currently I am working +on [a new backend](https://github.com/freesewing/backend) and [website](https://github.com/freesewing/website). + +The new setup will be faster, more modular, and easier to extend and wrap your +head around. Which is crucial for our long-term growth. + +Unfortunately, this is one of those scenarios where nothing works until everything works. +So while you can go +to [beta.freesewing.org](https://beta.freesewing.org) now and kick the tires, +it's probably going to be a bit of a downer as so much is still broken, or unfinished. + +So please bear with me as we continue this important behind-the-scenes work. +Because while I can't tell you when it will be ready, +I really feel it's something worth looking forward to. + +## Oh, and one more thing + +I'm more of a looking-forward than a looking-back kinda guy, but as I reflect on the year, +it is clear to me that the most important thing we did with freesewing, was to team up +with [our patrons](/community/who/patrons). + +Twelve months ago +, [we launched our patron project](/blog/calling-all-patrons). Since then, 65 patrons +— spread roughly equally among our 3 tiers of patronage — +have [stepped forward to support freesewing](/patrons/join). +The knock-on effects of these people making a commitment to support our work have surpassed +even my most optimistic hopes. + +You may or may not know that I +have [made a pledge](/docs/various/pledge) to donate all income from freesewing to charity. +So this morning I transferred our entire revenue for the year (**3162.14 euros**) +to [Médecins Sans Frontières](https://www.msf.org/) (Doctors Without Borders). +Money that will go towards bringing relief to some of the most vulnerable people on this planet. + +You made that happen, and if it brings a fraction of the joy to your heart as it does to mine, +you'll understand how much your patronage means to me. + +I have, for several years now, put a lot of time and effort into freesewing. +And I can honestly say that I've never worked harder on this than I am doing now. +But at the same time, it has been easier than ever for me to find the motivation to do so. +Every contribution, no matter how small, is like a small patch in a warm blanket of support +under which freesewing can thrive. + +So thank you for all this. And let's try to do (even) better next year. + diff --git a/markdown/org/blog/meet-paco/de.md b/markdown/org/blog/meet-paco/de.md new file mode 100644 index 00000000000..ce74f11a794 --- /dev/null +++ b/markdown/org/blog/meet-paco/de.md @@ -0,0 +1,37 @@ +--- +author: "joostdecock" +caption: "Paco on yours truly" +date: "2020-08-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1bc82d4abb50ea1b7bda32dd64521e9ecfdd8467-2048x1536.jpg" +intro: "Meet Paco: Our new unisex pattern for stylish summer pants [Nicht übersetzt]" +title: "Meet Paco: Our new unisex pattern for stylish summer pants [Nicht übersetzt]" +--- + +If you pay attention to our releases, you know that 4 weeks ago we put out our new [Titan trouser block](/designs/titan/). +Today, I'm happy to announce our first *real* pattern based on it: The [Paco summer pants](/designs/paco). + +These are decidedly unisex — in a good way — and they're also quick to make, certainly in comparison to a pair of full-blown trousers like [Theo](/designs/theo/). + +Paco comes with an elasticated waist and cuffs, at least by default, for you can also choose to draft these with regular hemmed legs. + +The default options also include front pockets on the side seams. If you want welt pockets in the back, you can chose that as an option. +You can also remove the side seam pockets of you'd like that. + + +## Are these just sweat pants? + +They could be. If you make these in a knit, than your could certainly use them as such. But no, they are not designed to be. + +The ones you see in the picture above (full disclosure: I have not taken these off since I've made them) aren't knit either. +Here's a close-up of the woven fabric: + +![Close-up of a woven fabric](https://posts.freesewing.org/uploads/fabric_46633a6dd2.jpg) + +The difference is in the cut — which is a lot more flattering and stylish that your typical sweat pants — and the pockets. +Yes, the pockets. Because pockets are important. + +Both front pockets and (optional) back pockets are anchored at the waist. Which means that you can put things in your +pockets without them becoming unsightly bump that's just dangling around in your trouser leg. + +Convinced yet? Then go make some, and make sure to share your pictures :) + diff --git a/markdown/org/blog/meet-paco/en.md b/markdown/org/blog/meet-paco/en.md new file mode 100644 index 00000000000..db3c2042b34 --- /dev/null +++ b/markdown/org/blog/meet-paco/en.md @@ -0,0 +1,37 @@ +--- +author: "joostdecock" +caption: "Paco on yours truly" +date: "2020-08-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1bc82d4abb50ea1b7bda32dd64521e9ecfdd8467-2048x1536.jpg" +intro: "Meet Paco: Our new unisex pattern for stylish summer pants" +title: "Meet Paco: Our new unisex pattern for stylish summer pants" +--- + +If you pay attention to our releases, you know that 4 weeks ago we put out our new [Titan trouser block](/designs/titan/). +Today, I'm happy to announce our first *real* pattern based on it: The [Paco summer pants](/designs/paco). + +These are decidedly unisex — in a good way — and they're also quick to make, certainly in comparison to a pair of full-blown trousers like [Theo](/designs/theo/). + +Paco comes with an elasticated waist and cuffs, at least by default, for you can also choose to draft these with regular hemmed legs. + +The default options also include front pockets on the side seams. If you want welt pockets in the back, you can chose that as an option. +You can also remove the side seam pockets of you'd like that. + + +## Are these just sweat pants? + +They could be. If you make these in a knit, than your could certainly use them as such. But no, they are not designed to be. + +The ones you see in the picture above (full disclosure: I have not taken these off since I've made them) aren't knit either. +Here's a close-up of the woven fabric: + +![Close-up of a woven fabric](https://posts.freesewing.org/uploads/fabric_46633a6dd2.jpg) + +The difference is in the cut — which is a lot more flattering and stylish that your typical sweat pants — and the pockets. +Yes, the pockets. Because pockets are important. + +Both front pockets and (optional) back pockets are anchored at the waist. Which means that you can put things in your +pockets without them becoming unsightly bump that's just dangling around in your trouser leg. + +Convinced yet? Then go make some, and make sure to share your pictures :) + diff --git a/markdown/org/blog/meet-paco/es.md b/markdown/org/blog/meet-paco/es.md new file mode 100644 index 00000000000..8ce509a1057 --- /dev/null +++ b/markdown/org/blog/meet-paco/es.md @@ -0,0 +1,37 @@ +--- +author: "joostdecock" +caption: "Paco on yours truly" +date: "2020-08-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1bc82d4abb50ea1b7bda32dd64521e9ecfdd8467-2048x1536.jpg" +intro: "Meet Paco: Our new unisex pattern for stylish summer pants [No traducido]" +title: "Meet Paco: Our new unisex pattern for stylish summer pants [No traducido]" +--- + +If you pay attention to our releases, you know that 4 weeks ago we put out our new [Titan trouser block](/designs/titan/). +Today, I'm happy to announce our first *real* pattern based on it: The [Paco summer pants](/designs/paco). + +These are decidedly unisex — in a good way — and they're also quick to make, certainly in comparison to a pair of full-blown trousers like [Theo](/designs/theo/). + +Paco comes with an elasticated waist and cuffs, at least by default, for you can also choose to draft these with regular hemmed legs. + +The default options also include front pockets on the side seams. If you want welt pockets in the back, you can chose that as an option. +You can also remove the side seam pockets of you'd like that. + + +## Are these just sweat pants? + +They could be. If you make these in a knit, than your could certainly use them as such. But no, they are not designed to be. + +The ones you see in the picture above (full disclosure: I have not taken these off since I've made them) aren't knit either. +Here's a close-up of the woven fabric: + +![Close-up of a woven fabric](https://posts.freesewing.org/uploads/fabric_46633a6dd2.jpg) + +The difference is in the cut — which is a lot more flattering and stylish that your typical sweat pants — and the pockets. +Yes, the pockets. Because pockets are important. + +Both front pockets and (optional) back pockets are anchored at the waist. Which means that you can put things in your +pockets without them becoming unsightly bump that's just dangling around in your trouser leg. + +Convinced yet? Then go make some, and make sure to share your pictures :) + diff --git a/markdown/org/blog/meet-paco/fr.md b/markdown/org/blog/meet-paco/fr.md new file mode 100644 index 00000000000..cefd782a595 --- /dev/null +++ b/markdown/org/blog/meet-paco/fr.md @@ -0,0 +1,34 @@ +--- +author: "joostdecock" +caption: "Paco sur votre obligé" +date: "2020-08-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1bc82d4abb50ea1b7bda32dd64521e9ecfdd8467-2048x1536.jpg" +intro: "Si vous prêtez attention à nos versions, vous savez qu'il y a 4 semaines, nous avons sorti notre nouveau bloc de pantalon Titan . Aujourd'hui, je suis heureux d'annoncer notre premier patron basé sur celui-ci : le pantalon d'été Paco ." +title: "Découvrez Paco : notre nouveau patron unisexe pour un élégant pantalon d'été" +--- + + +Si vous prêtez attention à nos versions, vous savez qu'il y a 4 semaines, nous avons sorti notre nouveau [bloc de pantalon Titan](/designs/titan/). Aujourd'hui, je suis heureux d'annoncer notre premier *vrai* patron basé sur celui-ci : le [pantalon d'été Paco](/designs/paco). + +Celui-ci est décidément unisexe — dans le sens positif — et il est aussi rapide à faire, certainement par rapport à un patalon plus complexe comme [Theo](/designs/theo/). + +Paco est prévu avec une taille et des poignets élastiqués, du moins par défaut, car vous pouvez aussi choisir de les tracer avec des finitions à ourlets classiques. + +Les options par défaut incluent également des poches avant sur les coutures latérales. Si vous voulez des poches de passepoilées dans le dos, vous pouvez les choisir dans les options. Vous pouvez également retirer les poches de la couture latérale si vous le souhaitez. + + +## Est-ce juste un pantalon de jogging ? + +Ça pourrait. Si vous le cousez dans une maille, alors vous pourriez certainement l'utiliser comme tel. Mais non, il n'est pas prévu pour ça. + +Celui que vous voyez dans la photo ci-dessus (disclaimer : je ne l'ai pas quitté depuis que je l'ai fait) n'est pas cousu dans une maille. Voici un aperçu du tissu tissé : + +![Close-up d'un tissu tissé](fabric.jpg) + +La différence réside dans la coupe – qui est beaucoup plus flatteuse et plus élégante que vos pantalons de jogging classiques – et dans les poches. Oui, les poches. Parce que les poches c'est important. + +Les poches avant et les poches arrière (optionnelles) sont ancrées à la taille. Ce qui signifie que vous pouvez mettre des choses dans vos poches sans qu'elles ne créent des vilaines bosses qui ne font que se balader dans votre pantalon. + +Alors convaincu ? Allez donc en coudre et et surtout partagez les photos :) + + diff --git a/markdown/org/blog/meet-paco/nl.md b/markdown/org/blog/meet-paco/nl.md new file mode 100644 index 00000000000..a44e7c20bf5 --- /dev/null +++ b/markdown/org/blog/meet-paco/nl.md @@ -0,0 +1,34 @@ +--- +author: "joostdecock" +caption: "Paco op het brein achter de operatie" +date: "2020-08-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1bc82d4abb50ea1b7bda32dd64521e9ecfdd8467-2048x1536.jpg" +intro: "Als je ons werk wat in de gaten houdt weet je dat we 4 weken geleden ons Titan, ons nieuwe basispatroon voor een broek uitbrachten. Vandaag kan ik vol trots ons eerste patroon met Titan als basis aankondigen: De Paco zomerbroek ." +title: "Hier is Paco: Ons nieuwe unisex patroon voor een stijlvolle zomerbroek" +--- + + +Als je ons werk wat in de gaten houdt weet je dat we 4 weken geleden ons [Titan, ons nieuwe basispatroon voor een broek](/designs/titan/) uitbrachten. Vandaag kan ik vol trots ons eerste *echte* patroon met Titan als basis aankondigen: De [Paco zomerbroek](/designs/paco). + +Deze zijn unisex- op een goede manier- en zitten snel in elkaar, zeker in vergelijking met een broek met alles erop en eraan zoals [Theo](/designs/theo/). + +Paco heeft een elastische tailleband en elastiek aan de enkels, al kan je die laatste ook weglaten en in de plaats een gewone zoom kiezen. + +De standaard opties omvatten ook zakken in de zijnaad. Als je paspelzakken achteraan wil, kan je daar ook voor kiezen. Het is ook mogelijk om de zakken in de zijnaad weg te laten als je dat wil. + + +## Is dit gewoon een joggingbroek? + +Dat kan. Als je deze in een gebreide stof maakt, kan je ze zeker zo gebruiken. Maar nee, zo zijn ze niet ontworpen. + +Het voorbeeld dat je hierboven ziet (in alle eerlijkheid heb ik ze nog niet uitgetrokken sinds ik ze gemaakt heb) zijn ook geen jersey. Hier is een close-up van de geweven stof: + +![Close-up van een geweven stof](fabric.jpg) + +Het verschil is de pasvorm- die een stuk flatterender en stijlvoller is dan de doordeweekse joggingbroek- en de zakken. Ja, de zakken. Omdat zakken belangrijk zijn. + +Zowel de voorzakken en de (optionele) achterzakken zijn verankerd aan de taille. Wat wil zeggen dat je dingen in je zakken kan steken zonder dat ze een rare bult worden die wat in je broekspijp hangt te bengelen. + +Al overtuigd? Ga er dan een paar maken, en deel zeker je foto's :) + + diff --git a/markdown/org/blog/open-for-business/de.md b/markdown/org/blog/open-for-business/de.md new file mode 100644 index 00000000000..d25633488ac --- /dev/null +++ b/markdown/org/blog/open-for-business/de.md @@ -0,0 +1,210 @@ +--- +author: "joostdecock" +caption: "Open 24/7 from now onwards" +date: "2017-08-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/444b63db2120d50eb52004b2017c992624bbb66e-2000x1333.jpg" +intro: "Freesewing.org is open for business. That is, the business of giving away free sewing patterns [Nicht übersetzt]" +title: "Freesewing.org is open for business. That is, the business of giving away free sewing patterns [Nicht übersetzt]" +--- + +When I released freesewing core back in March, +I did not expect it to take another 5 months to finally have a proper front-end for it, +but here we are. + +From today onwards, +[freesewing.org](https://freesewing.org/) +is the place to be for your made-to-measure sewing patterns. + +If you're new to freesewing, +I suggest you start reading [the about page](/about/), +which hopefully does a half-decent attempt at describing what this thing is. + +> As of today mmp will no longer allow new users to sign up and after a grace period of a few months, I will shut it down + +If you do know what I'm doing here, +or you saw *An open-source platform for made-to-measure sewing patterns* +at the top of this page and that was enough for you to figure it out, +this announcement comes after 18 months of work to reinvent my previous site, +[makemypattern.com](https://makemypattern.com/). + +Speaking of which, +makemypattern.com has so far generated more than 6500 sewing patterns, +so I think it's fair to say it's been a good run. + +![Graph of the number of patterns generated on makemypattern.com](https://posts.freesewing.org/uploads/mmp_patterns_82c2056938.png) + +But [every new beginning comes from some other beginning's end](https://www.youtube.com/watch?v=xGytDsqkQY8). +So as of today mmp will no longer allow new users to sign up +and after a grace period of a few months, I will shut it down. + +Update your bookmarks people, +because [freesewing.org](https://freesewing.org/) is where it's at. + +## Everything is new or different, and hopefully better + +The idea of generating made-to-measure sewing patterns based on your measurements is the same. +Apart from that, pretty much everything you see here is different. + +I've written before about the choices I've made when building this frontend. +The [matters of principle and ethics](/en/blog/privacy-choices/) +as wel as [the technical stuff](/en/blog/freesewing-goes-jamstack/). + +Today, I won't go into the details of how things work under the hood. +Instead, I'd like to briefly highlight some of the most significant changes for the users of the site. Hopefully, that includes you. + +### Patterns vs drafts + +I told you earlier that mmp generated over 6500 patterns. +I can also tell you that mmp has 10 patterns available. + +So which one is it, 10 or 6500? +Well, it depends on the context. Which is ambigious and confusing. + +Now, patterns are patterns, and drafts are drafts. +That is, a draft is what you generate from a pattern. It's a pattern drafted to your exact specifications. + +![An example of a draft from freesewing.org](https://posts.freesewing.org/uploads/draft_sample_7e92caf0d6.svg) + +I hope that in using both terms consistently, it will become self-explanatory. + +So, for freesewing that means there are 12 patterns available, +from which a number of drafts have been generated that you can track live on +[the status page](/status). + +### New patterns, and blocks + +Currently, 12 patterns are available on freesewing.org. +All 10 from mmp (note: some have had their name changed) +plus the new [Sven Sweatshirt](/patterns/sven) and the [Brian Body Block](/patterns/brian). + +![An example of the Sven sweatshirt](https://posts.freesewing.org/uploads/sven_b189ad1368.jpg) + +The block also existed in the mmp backend, but it wasn't available to you. +So that's another change, I am making all my blocks (slopers) available. + +And more is coming, I currently have 3 patterns and 1 block that I am working on. +They are not ready yet, and I didn't want to delay the release for them, +but I hope to have them all out before the end of the year. + +What I'm saying is, watch this space. +Or better, check the links at the bottom of this page for social media accounts to follow. + +### Better support for *les autres* + +I [tried](https://makemypattern.com/blog/imperial-units-have-been-spotted-and-they-might-break-things) +and [failed](https://makemypattern.com/blog/imperial-units-not-worth-it) to add support for imperial units to makemypattern.com. + +This time around, both metric and imperial are fully supported. You can set your preferred units in your account settings. +And in each model you can set the units seperately, just in case you happen to sew for people living in different parts of the world. + +Speaking of different parts of the world, freesewing core fully supports different languages. +You can get your pattern in a number of languages, and if yours is not listed you can help with the translation. + +![The yoke of Simon, in French](https://posts.freesewing.org/uploads/yoke_7555f8616c.svg) + +Arguably, that is a bit of a half-measure when this site is only in English, but baby steps, right? + +### Compare to catch issues early + +One of the common pitfalls is that people take measurements the wrong way. + +When they generate a pattern, those incorrect measurements can sometimes really mess up the pattern +in a way that can be hard to spot if you are not familiar with the pattern. + +One way to tackle that is with better measuring instructions, which I have added. +But what I really wanted was a way to make spot issues in an easy way. + +![These two are going to help you to take accurate measurements](https://posts.freesewing.org/uploads/standing_d66bef801a.jpg) + +Comparing yourself to others is the fastest way to be unhappy. +But in this case, there's value to a comparison. + +Putting your pattern side by side with a pattern that is known to be correct +can help you spot any issues that go beyond size differences. + +So, comparison is built-in. Every time you generate a draft, you get two things: + + - Your drafted pattern + - A comparison of your draft to a range of standard sizes + +![An example of a draft compared to standard sizes](https://posts.freesewing.org/uploads/compare_sample_171c3eaecd.svg) + +It's a way to quickly eyeball your draft for any glaring issues before you start working with it. + +### Paperless because trees are precious, and printers not a given + +Something that I am curious to see whether it will catch on are paperless drafts. + +Apart from the obvious upside of saving paper, I hope this will allow people who don't have access to +a printer to use freesewing. + +The idea is that you don't have to print your pattern. +Instead, you can transfer it directly onto fabric or another medium. + +To make that possible, the pattern comes with detailed dimensions and a metric grid (or imperial grid if you're into that) +that helps you transfer all the information. + +![An example of a draft using the paperless theme](https://posts.freesewing.org/uploads/paperless_sample_def717482e.svg) + +As I said, I'm curious to see whether this will be useful to people, but I felt it was worth a try. + +### I've got your back (up) + +Also new is that when you draft a pattern, I will keep that draft for you, and it will remain available. + +![All your drafts are kept and available in your account](https://posts.freesewing.org/uploads/draft_list_7950e1609a.png) + +You can come back at any time to re-download the pattern, or tweak it, redraft it, or fork it. +Yes [fork it](/docs/site/fork), which is kinda cool because you can also fork patterns from other people after they've shared their draft. + +You can also add your own notes to your drafts (and to your models for that matter). + +### Community-driven blog and showcase + +Your makes deserve better than a Flickr album somewhere, so I've added showcases to the site. +The idea is to have a grabbag of examples here on the site of things people have made. + +![Showcase of the Hugo hoodie by uneanneedecouture](https://posts.freesewing.org/uploads/hugo_b331b0c298.jpg) + +Obviously, I can't add your work if I don't know about it, +so either get in touch of make sure to use the #freesewing hashtag when posting about it. + +Speaking of posting, the freesewing blog is also open to your contributions if you feel you have something to share. + +### Badges baby + +This is a bit silly, but you can now unlock [badges](/docs/site/badges) on the site. +I added the feature initially because I wanted to find a way to +thank the people who took part in the early access program. + +A while ago, I opened up an early access version of the site to +those people who were interested, and I would like to thank all of +you who tried out the site, reported issues, or merely gave feedback or encouragements. + +Those of you who took part should all get that coveted early access badge. +If it's missing from [your profile](/profile), [get in touch](/contact). + +Other badges are available, including one for signing up on launch day. [The full list of badges is here](/docs/site/badges). + +## What happens now? + +![Darkness, realistically](https://posts.freesewing.org/uploads/darkness_a9b72d2537.svg) + +Maybe it's just me, but after every major project comes to completion, +I tend to slide into a black hole of *is this it?* disillusionment. + +I might need a few weeks to bounce back from that, but don't let that stop you from giving me +[your feedback and opinions](/contact) on the site. +And if you manage to break something, you can [create an issue](https://github.com/freesewing/site/issues/new). + +## One last thing +I've worked on this for about a year and a half, and especially the last 11 months or so rather intensively. + +Now that it's ready, would you help me spread the news a little? + +If you could tell somebody about this or perhaps tweet or write about it, you'd do me a real favour. + +Thank you + + + diff --git a/markdown/org/blog/open-for-business/en.md b/markdown/org/blog/open-for-business/en.md new file mode 100644 index 00000000000..7c8df9dd68c --- /dev/null +++ b/markdown/org/blog/open-for-business/en.md @@ -0,0 +1,210 @@ +--- +author: "joostdecock" +caption: "Open 24/7 from now onwards" +date: "2017-08-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/444b63db2120d50eb52004b2017c992624bbb66e-2000x1333.jpg" +intro: "Freesewing.org is open for business. That is, the business of giving away free sewing patterns" +title: "Freesewing.org is open for business. That is, the business of giving away free sewing patterns" +--- + +When I released freesewing core back in March, +I did not expect it to take another 5 months to finally have a proper front-end for it, +but here we are. + +From today onwards, +[freesewing.org](https://freesewing.org/) +is the place to be for your made-to-measure sewing patterns. + +If you're new to freesewing, +I suggest you start reading [the about page](/about/), +which hopefully does a half-decent attempt at describing what this thing is. + +> As of today mmp will no longer allow new users to sign up and after a grace period of a few months, I will shut it down + +If you do know what I'm doing here, +or you saw *An open-source platform for made-to-measure sewing patterns* +at the top of this page and that was enough for you to figure it out, +this announcement comes after 18 months of work to reinvent my previous site, +[makemypattern.com](https://makemypattern.com/). + +Speaking of which, +makemypattern.com has so far generated more than 6500 sewing patterns, +so I think it's fair to say it's been a good run. + +![Graph of the number of patterns generated on makemypattern.com](https://posts.freesewing.org/uploads/mmp_patterns_82c2056938.png) + +But [every new beginning comes from some other beginning's end](https://www.youtube.com/watch?v=xGytDsqkQY8). +So as of today mmp will no longer allow new users to sign up +and after a grace period of a few months, I will shut it down. + +Update your bookmarks people, +because [freesewing.org](https://freesewing.org/) is where it's at. + +## Everything is new or different, and hopefully better + +The idea of generating made-to-measure sewing patterns based on your measurements is the same. +Apart from that, pretty much everything you see here is different. + +I've written before about the choices I've made when building this frontend. +The [matters of principle and ethics](/en/blog/privacy-choices/) +as wel as [the technical stuff](/en/blog/freesewing-goes-jamstack/). + +Today, I won't go into the details of how things work under the hood. +Instead, I'd like to briefly highlight some of the most significant changes for the users of the site. Hopefully, that includes you. + +### Patterns vs drafts + +I told you earlier that mmp generated over 6500 patterns. +I can also tell you that mmp has 10 patterns available. + +So which one is it, 10 or 6500? +Well, it depends on the context. Which is ambigious and confusing. + +Now, patterns are patterns, and drafts are drafts. +That is, a draft is what you generate from a pattern. It's a pattern drafted to your exact specifications. + +![An example of a draft from freesewing.org](https://posts.freesewing.org/uploads/draft_sample_7e92caf0d6.svg) + +I hope that in using both terms consistently, it will become self-explanatory. + +So, for freesewing that means there are 12 patterns available, +from which a number of drafts have been generated that you can track live on +[the status page](/status). + +### New patterns, and blocks + +Currently, 12 patterns are available on freesewing.org. +All 10 from mmp (note: some have had their name changed) +plus the new [Sven Sweatshirt](/patterns/sven) and the [Brian Body Block](/patterns/brian). + +![An example of the Sven sweatshirt](https://posts.freesewing.org/uploads/sven_b189ad1368.jpg) + +The block also existed in the mmp backend, but it wasn't available to you. +So that's another change, I am making all my blocks (slopers) available. + +And more is coming, I currently have 3 patterns and 1 block that I am working on. +They are not ready yet, and I didn't want to delay the release for them, +but I hope to have them all out before the end of the year. + +What I'm saying is, watch this space. +Or better, check the links at the bottom of this page for social media accounts to follow. + +### Better support for *les autres* + +I [tried](https://makemypattern.com/blog/imperial-units-have-been-spotted-and-they-might-break-things) +and [failed](https://makemypattern.com/blog/imperial-units-not-worth-it) to add support for imperial units to makemypattern.com. + +This time around, both metric and imperial are fully supported. You can set your preferred units in your account settings. +And in each model you can set the units seperately, just in case you happen to sew for people living in different parts of the world. + +Speaking of different parts of the world, freesewing core fully supports different languages. +You can get your pattern in a number of languages, and if yours is not listed you can help with the translation. + +![The yoke of Simon, in French](https://posts.freesewing.org/uploads/yoke_7555f8616c.svg) + +Arguably, that is a bit of a half-measure when this site is only in English, but baby steps, right? + +### Compare to catch issues early + +One of the common pitfalls is that people take measurements the wrong way. + +When they generate a pattern, those incorrect measurements can sometimes really mess up the pattern +in a way that can be hard to spot if you are not familiar with the pattern. + +One way to tackle that is with better measuring instructions, which I have added. +But what I really wanted was a way to make spot issues in an easy way. + +![These two are going to help you to take accurate measurements](https://posts.freesewing.org/uploads/standing_d66bef801a.jpg) + +Comparing yourself to others is the fastest way to be unhappy. +But in this case, there's value to a comparison. + +Putting your pattern side by side with a pattern that is known to be correct +can help you spot any issues that go beyond size differences. + +So, comparison is built-in. Every time you generate a draft, you get two things: + + - Your drafted pattern + - A comparison of your draft to a range of standard sizes + +![An example of a draft compared to standard sizes](https://posts.freesewing.org/uploads/compare_sample_171c3eaecd.svg) + +It's a way to quickly eyeball your draft for any glaring issues before you start working with it. + +### Paperless because trees are precious, and printers not a given + +Something that I am curious to see whether it will catch on are paperless drafts. + +Apart from the obvious upside of saving paper, I hope this will allow people who don't have access to +a printer to use freesewing. + +The idea is that you don't have to print your pattern. +Instead, you can transfer it directly onto fabric or another medium. + +To make that possible, the pattern comes with detailed dimensions and a metric grid (or imperial grid if you're into that) +that helps you transfer all the information. + +![An example of a draft using the paperless theme](https://posts.freesewing.org/uploads/paperless_sample_def717482e.svg) + +As I said, I'm curious to see whether this will be useful to people, but I felt it was worth a try. + +### I've got your back (up) + +Also new is that when you draft a pattern, I will keep that draft for you, and it will remain available. + +![All your drafts are kept and available in your account](https://posts.freesewing.org/uploads/draft_list_7950e1609a.png) + +You can come back at any time to re-download the pattern, or tweak it, redraft it, or fork it. +Yes [fork it](/docs/site/fork), which is kinda cool because you can also fork patterns from other people after they've shared their draft. + +You can also add your own notes to your drafts (and to your models for that matter). + +### Community-driven blog and showcase + +Your makes deserve better than a Flickr album somewhere, so I've added showcases to the site. +The idea is to have a grabbag of examples here on the site of things people have made. + +![Showcase of the Hugo hoodie by uneanneedecouture](https://posts.freesewing.org/uploads/hugo_b331b0c298.jpg) + +Obviously, I can't add your work if I don't know about it, +so either get in touch of make sure to use the #freesewing hashtag when posting about it. + +Speaking of posting, the freesewing blog is also open to your contributions if you feel you have something to share. + +### Badges baby + +This is a bit silly, but you can now unlock [badges](/docs/site/badges) on the site. +I added the feature initially because I wanted to find a way to +thank the people who took part in the early access program. + +A while ago, I opened up an early access version of the site to +those people who were interested, and I would like to thank all of +you who tried out the site, reported issues, or merely gave feedback or encouragements. + +Those of you who took part should all get that coveted early access badge. +If it's missing from [your profile](/profile), [get in touch](/contact). + +Other badges are available, including one for signing up on launch day. [The full list of badges is here](/docs/site/badges). + +## What happens now? + +![Darkness, realistically](https://posts.freesewing.org/uploads/darkness_a9b72d2537.svg) + +Maybe it's just me, but after every major project comes to completion, +I tend to slide into a black hole of *is this it?* disillusionment. + +I might need a few weeks to bounce back from that, but don't let that stop you from giving me +[your feedback and opinions](/contact) on the site. +And if you manage to break something, you can [create an issue](https://github.com/freesewing/site/issues/new). + +## One last thing +I've worked on this for about a year and a half, and especially the last 11 months or so rather intensively. + +Now that it's ready, would you help me spread the news a little? + +If you could tell somebody about this or perhaps tweet or write about it, you'd do me a real favour. + +Thank you + + + diff --git a/markdown/org/blog/open-for-business/es.md b/markdown/org/blog/open-for-business/es.md new file mode 100644 index 00000000000..0f1f5fd89ce --- /dev/null +++ b/markdown/org/blog/open-for-business/es.md @@ -0,0 +1,210 @@ +--- +author: "joostdecock" +caption: "Open 24/7 from now onwards" +date: "2017-08-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/444b63db2120d50eb52004b2017c992624bbb66e-2000x1333.jpg" +intro: "Freesewing.org is open for business. That is, the business of giving away free sewing patterns [No traducido]" +title: "Freesewing.org is open for business. That is, the business of giving away free sewing patterns [No traducido]" +--- + +When I released freesewing core back in March, +I did not expect it to take another 5 months to finally have a proper front-end for it, +but here we are. + +From today onwards, +[freesewing.org](https://freesewing.org/) +is the place to be for your made-to-measure sewing patterns. + +If you're new to freesewing, +I suggest you start reading [the about page](/about/), +which hopefully does a half-decent attempt at describing what this thing is. + +> As of today mmp will no longer allow new users to sign up and after a grace period of a few months, I will shut it down + +If you do know what I'm doing here, +or you saw *An open-source platform for made-to-measure sewing patterns* +at the top of this page and that was enough for you to figure it out, +this announcement comes after 18 months of work to reinvent my previous site, +[makemypattern.com](https://makemypattern.com/). + +Speaking of which, +makemypattern.com has so far generated more than 6500 sewing patterns, +so I think it's fair to say it's been a good run. + +![Graph of the number of patterns generated on makemypattern.com](https://posts.freesewing.org/uploads/mmp_patterns_82c2056938.png) + +But [every new beginning comes from some other beginning's end](https://www.youtube.com/watch?v=xGytDsqkQY8). +So as of today mmp will no longer allow new users to sign up +and after a grace period of a few months, I will shut it down. + +Update your bookmarks people, +because [freesewing.org](https://freesewing.org/) is where it's at. + +## Everything is new or different, and hopefully better + +The idea of generating made-to-measure sewing patterns based on your measurements is the same. +Apart from that, pretty much everything you see here is different. + +I've written before about the choices I've made when building this frontend. +The [matters of principle and ethics](/en/blog/privacy-choices/) +as wel as [the technical stuff](/en/blog/freesewing-goes-jamstack/). + +Today, I won't go into the details of how things work under the hood. +Instead, I'd like to briefly highlight some of the most significant changes for the users of the site. Hopefully, that includes you. + +### Patterns vs drafts + +I told you earlier that mmp generated over 6500 patterns. +I can also tell you that mmp has 10 patterns available. + +So which one is it, 10 or 6500? +Well, it depends on the context. Which is ambigious and confusing. + +Now, patterns are patterns, and drafts are drafts. +That is, a draft is what you generate from a pattern. It's a pattern drafted to your exact specifications. + +![An example of a draft from freesewing.org](https://posts.freesewing.org/uploads/draft_sample_7e92caf0d6.svg) + +I hope that in using both terms consistently, it will become self-explanatory. + +So, for freesewing that means there are 12 patterns available, +from which a number of drafts have been generated that you can track live on +[the status page](/status). + +### New patterns, and blocks + +Currently, 12 patterns are available on freesewing.org. +All 10 from mmp (note: some have had their name changed) +plus the new [Sven Sweatshirt](/patterns/sven) and the [Brian Body Block](/patterns/brian). + +![An example of the Sven sweatshirt](https://posts.freesewing.org/uploads/sven_b189ad1368.jpg) + +The block also existed in the mmp backend, but it wasn't available to you. +So that's another change, I am making all my blocks (slopers) available. + +And more is coming, I currently have 3 patterns and 1 block that I am working on. +They are not ready yet, and I didn't want to delay the release for them, +but I hope to have them all out before the end of the year. + +What I'm saying is, watch this space. +Or better, check the links at the bottom of this page for social media accounts to follow. + +### Better support for *les autres* + +I [tried](https://makemypattern.com/blog/imperial-units-have-been-spotted-and-they-might-break-things) +and [failed](https://makemypattern.com/blog/imperial-units-not-worth-it) to add support for imperial units to makemypattern.com. + +This time around, both metric and imperial are fully supported. You can set your preferred units in your account settings. +And in each model you can set the units seperately, just in case you happen to sew for people living in different parts of the world. + +Speaking of different parts of the world, freesewing core fully supports different languages. +You can get your pattern in a number of languages, and if yours is not listed you can help with the translation. + +![The yoke of Simon, in French](https://posts.freesewing.org/uploads/yoke_7555f8616c.svg) + +Arguably, that is a bit of a half-measure when this site is only in English, but baby steps, right? + +### Compare to catch issues early + +One of the common pitfalls is that people take measurements the wrong way. + +When they generate a pattern, those incorrect measurements can sometimes really mess up the pattern +in a way that can be hard to spot if you are not familiar with the pattern. + +One way to tackle that is with better measuring instructions, which I have added. +But what I really wanted was a way to make spot issues in an easy way. + +![These two are going to help you to take accurate measurements](https://posts.freesewing.org/uploads/standing_d66bef801a.jpg) + +Comparing yourself to others is the fastest way to be unhappy. +But in this case, there's value to a comparison. + +Putting your pattern side by side with a pattern that is known to be correct +can help you spot any issues that go beyond size differences. + +So, comparison is built-in. Every time you generate a draft, you get two things: + + - Your drafted pattern + - A comparison of your draft to a range of standard sizes + +![An example of a draft compared to standard sizes](https://posts.freesewing.org/uploads/compare_sample_171c3eaecd.svg) + +It's a way to quickly eyeball your draft for any glaring issues before you start working with it. + +### Paperless because trees are precious, and printers not a given + +Something that I am curious to see whether it will catch on are paperless drafts. + +Apart from the obvious upside of saving paper, I hope this will allow people who don't have access to +a printer to use freesewing. + +The idea is that you don't have to print your pattern. +Instead, you can transfer it directly onto fabric or another medium. + +To make that possible, the pattern comes with detailed dimensions and a metric grid (or imperial grid if you're into that) +that helps you transfer all the information. + +![An example of a draft using the paperless theme](https://posts.freesewing.org/uploads/paperless_sample_def717482e.svg) + +As I said, I'm curious to see whether this will be useful to people, but I felt it was worth a try. + +### I've got your back (up) + +Also new is that when you draft a pattern, I will keep that draft for you, and it will remain available. + +![All your drafts are kept and available in your account](https://posts.freesewing.org/uploads/draft_list_7950e1609a.png) + +You can come back at any time to re-download the pattern, or tweak it, redraft it, or fork it. +Yes [fork it](/docs/site/fork), which is kinda cool because you can also fork patterns from other people after they've shared their draft. + +You can also add your own notes to your drafts (and to your models for that matter). + +### Community-driven blog and showcase + +Your makes deserve better than a Flickr album somewhere, so I've added showcases to the site. +The idea is to have a grabbag of examples here on the site of things people have made. + +![Showcase of the Hugo hoodie by uneanneedecouture](https://posts.freesewing.org/uploads/hugo_b331b0c298.jpg) + +Obviously, I can't add your work if I don't know about it, +so either get in touch of make sure to use the #freesewing hashtag when posting about it. + +Speaking of posting, the freesewing blog is also open to your contributions if you feel you have something to share. + +### Badges baby + +This is a bit silly, but you can now unlock [badges](/docs/site/badges) on the site. +I added the feature initially because I wanted to find a way to +thank the people who took part in the early access program. + +A while ago, I opened up an early access version of the site to +those people who were interested, and I would like to thank all of +you who tried out the site, reported issues, or merely gave feedback or encouragements. + +Those of you who took part should all get that coveted early access badge. +If it's missing from [your profile](/profile), [get in touch](/contact). + +Other badges are available, including one for signing up on launch day. [The full list of badges is here](/docs/site/badges). + +## What happens now? + +![Darkness, realistically](https://posts.freesewing.org/uploads/darkness_a9b72d2537.svg) + +Maybe it's just me, but after every major project comes to completion, +I tend to slide into a black hole of *is this it?* disillusionment. + +I might need a few weeks to bounce back from that, but don't let that stop you from giving me +[your feedback and opinions](/contact) on the site. +And if you manage to break something, you can [create an issue](https://github.com/freesewing/site/issues/new). + +## One last thing +I've worked on this for about a year and a half, and especially the last 11 months or so rather intensively. + +Now that it's ready, would you help me spread the news a little? + +If you could tell somebody about this or perhaps tweet or write about it, you'd do me a real favour. + +Thank you + + + diff --git a/markdown/org/blog/open-for-business/fr.md b/markdown/org/blog/open-for-business/fr.md new file mode 100644 index 00000000000..9e029d32064 --- /dev/null +++ b/markdown/org/blog/open-for-business/fr.md @@ -0,0 +1,210 @@ +--- +author: "joostdecock" +caption: "Open 24/7 from now onwards" +date: "2017-08-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/444b63db2120d50eb52004b2017c992624bbb66e-2000x1333.jpg" +intro: "Freesewing.org is open for business. That is, the business of giving away free sewing patterns [Non traduit]" +title: "Freesewing.org is open for business. That is, the business of giving away free sewing patterns [Non traduit]" +--- + +When I released freesewing core back in March, +I did not expect it to take another 5 months to finally have a proper front-end for it, +but here we are. + +From today onwards, +[freesewing.org](https://freesewing.org/) +is the place to be for your made-to-measure sewing patterns. + +If you're new to freesewing, +I suggest you start reading [the about page](/about/), +which hopefully does a half-decent attempt at describing what this thing is. + +> As of today mmp will no longer allow new users to sign up and after a grace period of a few months, I will shut it down + +If you do know what I'm doing here, +or you saw *An open-source platform for made-to-measure sewing patterns* +at the top of this page and that was enough for you to figure it out, +this announcement comes after 18 months of work to reinvent my previous site, +[makemypattern.com](https://makemypattern.com/). + +Speaking of which, +makemypattern.com has so far generated more than 6500 sewing patterns, +so I think it's fair to say it's been a good run. + +![Graph of the number of patterns generated on makemypattern.com](https://posts.freesewing.org/uploads/mmp_patterns_82c2056938.png) + +But [every new beginning comes from some other beginning's end](https://www.youtube.com/watch?v=xGytDsqkQY8). +So as of today mmp will no longer allow new users to sign up +and after a grace period of a few months, I will shut it down. + +Update your bookmarks people, +because [freesewing.org](https://freesewing.org/) is where it's at. + +## Everything is new or different, and hopefully better + +The idea of generating made-to-measure sewing patterns based on your measurements is the same. +Apart from that, pretty much everything you see here is different. + +I've written before about the choices I've made when building this frontend. +The [matters of principle and ethics](/en/blog/privacy-choices/) +as wel as [the technical stuff](/en/blog/freesewing-goes-jamstack/). + +Today, I won't go into the details of how things work under the hood. +Instead, I'd like to briefly highlight some of the most significant changes for the users of the site. Hopefully, that includes you. + +### Patterns vs drafts + +I told you earlier that mmp generated over 6500 patterns. +I can also tell you that mmp has 10 patterns available. + +So which one is it, 10 or 6500? +Well, it depends on the context. Which is ambigious and confusing. + +Now, patterns are patterns, and drafts are drafts. +That is, a draft is what you generate from a pattern. It's a pattern drafted to your exact specifications. + +![An example of a draft from freesewing.org](https://posts.freesewing.org/uploads/draft_sample_7e92caf0d6.svg) + +I hope that in using both terms consistently, it will become self-explanatory. + +So, for freesewing that means there are 12 patterns available, +from which a number of drafts have been generated that you can track live on +[the status page](/status). + +### New patterns, and blocks + +Currently, 12 patterns are available on freesewing.org. +All 10 from mmp (note: some have had their name changed) +plus the new [Sven Sweatshirt](/patterns/sven) and the [Brian Body Block](/patterns/brian). + +![An example of the Sven sweatshirt](https://posts.freesewing.org/uploads/sven_b189ad1368.jpg) + +The block also existed in the mmp backend, but it wasn't available to you. +So that's another change, I am making all my blocks (slopers) available. + +And more is coming, I currently have 3 patterns and 1 block that I am working on. +They are not ready yet, and I didn't want to delay the release for them, +but I hope to have them all out before the end of the year. + +What I'm saying is, watch this space. +Or better, check the links at the bottom of this page for social media accounts to follow. + +### Better support for *les autres* + +I [tried](https://makemypattern.com/blog/imperial-units-have-been-spotted-and-they-might-break-things) +and [failed](https://makemypattern.com/blog/imperial-units-not-worth-it) to add support for imperial units to makemypattern.com. + +This time around, both metric and imperial are fully supported. You can set your preferred units in your account settings. +And in each model you can set the units seperately, just in case you happen to sew for people living in different parts of the world. + +Speaking of different parts of the world, freesewing core fully supports different languages. +You can get your pattern in a number of languages, and if yours is not listed you can help with the translation. + +![The yoke of Simon, in French](https://posts.freesewing.org/uploads/yoke_7555f8616c.svg) + +Arguably, that is a bit of a half-measure when this site is only in English, but baby steps, right? + +### Compare to catch issues early + +One of the common pitfalls is that people take measurements the wrong way. + +When they generate a pattern, those incorrect measurements can sometimes really mess up the pattern +in a way that can be hard to spot if you are not familiar with the pattern. + +One way to tackle that is with better measuring instructions, which I have added. +But what I really wanted was a way to make spot issues in an easy way. + +![These two are going to help you to take accurate measurements](https://posts.freesewing.org/uploads/standing_d66bef801a.jpg) + +Comparing yourself to others is the fastest way to be unhappy. +But in this case, there's value to a comparison. + +Putting your pattern side by side with a pattern that is known to be correct +can help you spot any issues that go beyond size differences. + +So, comparison is built-in. Every time you generate a draft, you get two things: + + - Your drafted pattern + - A comparison of your draft to a range of standard sizes + +![An example of a draft compared to standard sizes](https://posts.freesewing.org/uploads/compare_sample_171c3eaecd.svg) + +It's a way to quickly eyeball your draft for any glaring issues before you start working with it. + +### Paperless because trees are precious, and printers not a given + +Something that I am curious to see whether it will catch on are paperless drafts. + +Apart from the obvious upside of saving paper, I hope this will allow people who don't have access to +a printer to use freesewing. + +The idea is that you don't have to print your pattern. +Instead, you can transfer it directly onto fabric or another medium. + +To make that possible, the pattern comes with detailed dimensions and a metric grid (or imperial grid if you're into that) +that helps you transfer all the information. + +![An example of a draft using the paperless theme](https://posts.freesewing.org/uploads/paperless_sample_def717482e.svg) + +As I said, I'm curious to see whether this will be useful to people, but I felt it was worth a try. + +### I've got your back (up) + +Also new is that when you draft a pattern, I will keep that draft for you, and it will remain available. + +![All your drafts are kept and available in your account](https://posts.freesewing.org/uploads/draft_list_7950e1609a.png) + +You can come back at any time to re-download the pattern, or tweak it, redraft it, or fork it. +Yes [fork it](/docs/site/fork), which is kinda cool because you can also fork patterns from other people after they've shared their draft. + +You can also add your own notes to your drafts (and to your models for that matter). + +### Community-driven blog and showcase + +Your makes deserve better than a Flickr album somewhere, so I've added showcases to the site. +The idea is to have a grabbag of examples here on the site of things people have made. + +![Showcase of the Hugo hoodie by uneanneedecouture](https://posts.freesewing.org/uploads/hugo_b331b0c298.jpg) + +Obviously, I can't add your work if I don't know about it, +so either get in touch of make sure to use the #freesewing hashtag when posting about it. + +Speaking of posting, the freesewing blog is also open to your contributions if you feel you have something to share. + +### Badges baby + +This is a bit silly, but you can now unlock [badges](/docs/site/badges) on the site. +I added the feature initially because I wanted to find a way to +thank the people who took part in the early access program. + +A while ago, I opened up an early access version of the site to +those people who were interested, and I would like to thank all of +you who tried out the site, reported issues, or merely gave feedback or encouragements. + +Those of you who took part should all get that coveted early access badge. +If it's missing from [your profile](/profile), [get in touch](/contact). + +Other badges are available, including one for signing up on launch day. [The full list of badges is here](/docs/site/badges). + +## What happens now? + +![Darkness, realistically](https://posts.freesewing.org/uploads/darkness_a9b72d2537.svg) + +Maybe it's just me, but after every major project comes to completion, +I tend to slide into a black hole of *is this it?* disillusionment. + +I might need a few weeks to bounce back from that, but don't let that stop you from giving me +[your feedback and opinions](/contact) on the site. +And if you manage to break something, you can [create an issue](https://github.com/freesewing/site/issues/new). + +## One last thing +I've worked on this for about a year and a half, and especially the last 11 months or so rather intensively. + +Now that it's ready, would you help me spread the news a little? + +If you could tell somebody about this or perhaps tweet or write about it, you'd do me a real favour. + +Thank you + + + diff --git a/markdown/org/blog/open-for-business/nl.md b/markdown/org/blog/open-for-business/nl.md new file mode 100644 index 00000000000..b9e7bbef340 --- /dev/null +++ b/markdown/org/blog/open-for-business/nl.md @@ -0,0 +1,210 @@ +--- +author: "joostdecock" +caption: "Open 24/7 from now onwards" +date: "2017-08-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/444b63db2120d50eb52004b2017c992624bbb66e-2000x1333.jpg" +intro: "Freesewing.org is open for business. That is, the business of giving away free sewing patterns [Niet vertaald]" +title: "Freesewing.org is open for business. That is, the business of giving away free sewing patterns [Niet vertaald]" +--- + +When I released freesewing core back in March, +I did not expect it to take another 5 months to finally have a proper front-end for it, +but here we are. + +From today onwards, +[freesewing.org](https://freesewing.org/) +is the place to be for your made-to-measure sewing patterns. + +If you're new to freesewing, +I suggest you start reading [the about page](/about/), +which hopefully does a half-decent attempt at describing what this thing is. + +> As of today mmp will no longer allow new users to sign up and after a grace period of a few months, I will shut it down + +If you do know what I'm doing here, +or you saw *An open-source platform for made-to-measure sewing patterns* +at the top of this page and that was enough for you to figure it out, +this announcement comes after 18 months of work to reinvent my previous site, +[makemypattern.com](https://makemypattern.com/). + +Speaking of which, +makemypattern.com has so far generated more than 6500 sewing patterns, +so I think it's fair to say it's been a good run. + +![Graph of the number of patterns generated on makemypattern.com](https://posts.freesewing.org/uploads/mmp_patterns_82c2056938.png) + +But [every new beginning comes from some other beginning's end](https://www.youtube.com/watch?v=xGytDsqkQY8). +So as of today mmp will no longer allow new users to sign up +and after a grace period of a few months, I will shut it down. + +Update your bookmarks people, +because [freesewing.org](https://freesewing.org/) is where it's at. + +## Everything is new or different, and hopefully better + +The idea of generating made-to-measure sewing patterns based on your measurements is the same. +Apart from that, pretty much everything you see here is different. + +I've written before about the choices I've made when building this frontend. +The [matters of principle and ethics](/en/blog/privacy-choices/) +as wel as [the technical stuff](/en/blog/freesewing-goes-jamstack/). + +Today, I won't go into the details of how things work under the hood. +Instead, I'd like to briefly highlight some of the most significant changes for the users of the site. Hopefully, that includes you. + +### Patterns vs drafts + +I told you earlier that mmp generated over 6500 patterns. +I can also tell you that mmp has 10 patterns available. + +So which one is it, 10 or 6500? +Well, it depends on the context. Which is ambigious and confusing. + +Now, patterns are patterns, and drafts are drafts. +That is, a draft is what you generate from a pattern. It's a pattern drafted to your exact specifications. + +![An example of a draft from freesewing.org](https://posts.freesewing.org/uploads/draft_sample_7e92caf0d6.svg) + +I hope that in using both terms consistently, it will become self-explanatory. + +So, for freesewing that means there are 12 patterns available, +from which a number of drafts have been generated that you can track live on +[the status page](/status). + +### New patterns, and blocks + +Currently, 12 patterns are available on freesewing.org. +All 10 from mmp (note: some have had their name changed) +plus the new [Sven Sweatshirt](/patterns/sven) and the [Brian Body Block](/patterns/brian). + +![An example of the Sven sweatshirt](https://posts.freesewing.org/uploads/sven_b189ad1368.jpg) + +The block also existed in the mmp backend, but it wasn't available to you. +So that's another change, I am making all my blocks (slopers) available. + +And more is coming, I currently have 3 patterns and 1 block that I am working on. +They are not ready yet, and I didn't want to delay the release for them, +but I hope to have them all out before the end of the year. + +What I'm saying is, watch this space. +Or better, check the links at the bottom of this page for social media accounts to follow. + +### Better support for *les autres* + +I [tried](https://makemypattern.com/blog/imperial-units-have-been-spotted-and-they-might-break-things) +and [failed](https://makemypattern.com/blog/imperial-units-not-worth-it) to add support for imperial units to makemypattern.com. + +This time around, both metric and imperial are fully supported. You can set your preferred units in your account settings. +And in each model you can set the units seperately, just in case you happen to sew for people living in different parts of the world. + +Speaking of different parts of the world, freesewing core fully supports different languages. +You can get your pattern in a number of languages, and if yours is not listed you can help with the translation. + +![The yoke of Simon, in French](https://posts.freesewing.org/uploads/yoke_7555f8616c.svg) + +Arguably, that is a bit of a half-measure when this site is only in English, but baby steps, right? + +### Compare to catch issues early + +One of the common pitfalls is that people take measurements the wrong way. + +When they generate a pattern, those incorrect measurements can sometimes really mess up the pattern +in a way that can be hard to spot if you are not familiar with the pattern. + +One way to tackle that is with better measuring instructions, which I have added. +But what I really wanted was a way to make spot issues in an easy way. + +![These two are going to help you to take accurate measurements](https://posts.freesewing.org/uploads/standing_d66bef801a.jpg) + +Comparing yourself to others is the fastest way to be unhappy. +But in this case, there's value to a comparison. + +Putting your pattern side by side with a pattern that is known to be correct +can help you spot any issues that go beyond size differences. + +So, comparison is built-in. Every time you generate a draft, you get two things: + + - Your drafted pattern + - A comparison of your draft to a range of standard sizes + +![An example of a draft compared to standard sizes](https://posts.freesewing.org/uploads/compare_sample_171c3eaecd.svg) + +It's a way to quickly eyeball your draft for any glaring issues before you start working with it. + +### Paperless because trees are precious, and printers not a given + +Something that I am curious to see whether it will catch on are paperless drafts. + +Apart from the obvious upside of saving paper, I hope this will allow people who don't have access to +a printer to use freesewing. + +The idea is that you don't have to print your pattern. +Instead, you can transfer it directly onto fabric or another medium. + +To make that possible, the pattern comes with detailed dimensions and a metric grid (or imperial grid if you're into that) +that helps you transfer all the information. + +![An example of a draft using the paperless theme](https://posts.freesewing.org/uploads/paperless_sample_def717482e.svg) + +As I said, I'm curious to see whether this will be useful to people, but I felt it was worth a try. + +### I've got your back (up) + +Also new is that when you draft a pattern, I will keep that draft for you, and it will remain available. + +![All your drafts are kept and available in your account](https://posts.freesewing.org/uploads/draft_list_7950e1609a.png) + +You can come back at any time to re-download the pattern, or tweak it, redraft it, or fork it. +Yes [fork it](/docs/site/fork), which is kinda cool because you can also fork patterns from other people after they've shared their draft. + +You can also add your own notes to your drafts (and to your models for that matter). + +### Community-driven blog and showcase + +Your makes deserve better than a Flickr album somewhere, so I've added showcases to the site. +The idea is to have a grabbag of examples here on the site of things people have made. + +![Showcase of the Hugo hoodie by uneanneedecouture](https://posts.freesewing.org/uploads/hugo_b331b0c298.jpg) + +Obviously, I can't add your work if I don't know about it, +so either get in touch of make sure to use the #freesewing hashtag when posting about it. + +Speaking of posting, the freesewing blog is also open to your contributions if you feel you have something to share. + +### Badges baby + +This is a bit silly, but you can now unlock [badges](/docs/site/badges) on the site. +I added the feature initially because I wanted to find a way to +thank the people who took part in the early access program. + +A while ago, I opened up an early access version of the site to +those people who were interested, and I would like to thank all of +you who tried out the site, reported issues, or merely gave feedback or encouragements. + +Those of you who took part should all get that coveted early access badge. +If it's missing from [your profile](/profile), [get in touch](/contact). + +Other badges are available, including one for signing up on launch day. [The full list of badges is here](/docs/site/badges). + +## What happens now? + +![Darkness, realistically](https://posts.freesewing.org/uploads/darkness_a9b72d2537.svg) + +Maybe it's just me, but after every major project comes to completion, +I tend to slide into a black hole of *is this it?* disillusionment. + +I might need a few weeks to bounce back from that, but don't let that stop you from giving me +[your feedback and opinions](/contact) on the site. +And if you manage to break something, you can [create an issue](https://github.com/freesewing/site/issues/new). + +## One last thing +I've worked on this for about a year and a half, and especially the last 11 months or so rather intensively. + +Now that it's ready, would you help me spread the news a little? + +If you could tell somebody about this or perhaps tweet or write about it, you'd do me a real favour. + +Thank you + + + diff --git a/markdown/org/blog/privacy-choices/de.md b/markdown/org/blog/privacy-choices/de.md new file mode 100644 index 00000000000..03e74f0b563 --- /dev/null +++ b/markdown/org/blog/privacy-choices/de.md @@ -0,0 +1,63 @@ +--- +author: "joostdecock" +caption: "Picture by Herbert" +date: "2017-06-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8ccbb2d5b50eb0917c6bd2befb2b098b6d667ba9-1920x1280.jpg" +intro: "Das World Wide Web untergräbt immer mehr Ihre Privatsphäre. Facebook, Google und eine ganze Armada an Werbenetzwerken haben ihre Browsertabs im Blick. Tracking you on the web, keeping an an eye on the sites your visiting, so that they can gather more info on you, and sell that to advertisers." +title: "Die Entscheidungen, die ich getroffen habe, um Ihre Privatsphäre zu schützen. Oder, warum Sie keine Cookies erhalten werden." +--- + + +Das World Wide Web untergräbt immer mehr Ihre Privatsphäre. Facebook, Google und eine ganze Armada an Werbenetzwerken haben ihre Browsertabs im Blick. Tracking you on the web, keeping an an eye on the sites your visiting, so that they can gather more info on you, and sell that to advertisers. + +Pardon my French, but I hate that shit. + +> Facebook, Google, and an avalanche of ad networks out there are all keeping tabs on your browser tabs + +Building this site from scratch has been a great opportunity to reflect on how to do things. + +To make sure I'm not contributing to the problem, I've made the following choices: + +## Encryption everywhere + +Let's run everything over https. That's just [common sense](https://letsencrypt.org/) in 2017. + +## No ads + +This one is another no-brainer. The number 1 tracking pest online are ad networks, and I want them nowhere near this site. + +Fortunately, that doesn't pose a problem given that we don't play by the _Give something for free, then sell people's data_ rules of the web. + +## No external code + +This site loads no external JavaScript code. None. Which does mean I had to rethink a few things that typically require external code. + +There is no Facebook Like button or Twitter integration. We still have social sharing under our blog posts (hint hint) but it's the plain vanilla HTML variety that prevents tracking. + +In the same category, there's no social logins. Sure a _Login with Facebook_ button is handy, but also kind of a nightmare when you consider what it does to your privacy. + +For a statically generated site like this ([see this post about JAMstack for details](/blog/freesewing-goes-jamstack/)) [Disqus](https://disqus.com/) is pretty much the de facto standard for comments. But Disqus is pretty awful when it comes to tracking, so that was a big no-no to me. + +A similar story for authentication where I considered [Auth0](https://auth0.com/). There too, I was concerned about tracking, so I decided against it. + +I ended up just biting the bullet and implemented authentication and comments myself. Time will tell of that was a good trade-of. + +## No cookies +We don't use any cookies. Obviously no third-party cookies, but not even cookies of our own. + +Instead, we use local storage which is better because unlike cookies, it doesn't send your info on every request. + +## No analytics +I ran [Google Analytics](https://analytics.google.com/) on [makemypattern](https://makemypattern.com/). It's powerful, but obviously a tracking nightmare. So I wasn't going to have that either. + +This issue is further complicated by the fact that this static site is hosted by [Netlify](https://www.netlify.com/). So I don't have server logs and can't run any analytics server-side. + +For the most part, I decided to just go without analytics. I don't need to know how many people are visiting this site. I still know how many user accounts are created, and how many patterns are generated, which should be fine indicators for the site's overall well-being. + +But there's one thing that wanted to keep from analytics: the referral logs. It's one of life's small pleasures to go through that list and discover [somebody](https://www.reddit.com/r/freepatterns/comments/4zh5nr/is_there_software_to_generate_sewing_patterns/) [linked](http://www.makery.uk/2016/08/the-refashioners-2016-joost/) [to](https://closetcasepatterns.com/week-sewing-blogs-vol-98/) [you](https://opensource.com/life/16/11/free-open-sewing-patterns). + +Here too, I've implemented my own bare-bones solution. If you land on this site from an external link, we'll report that referral to our own API. Which means we still get the referral info, but no tracking. + +Perhaps it's just vanity, but when I'm having a bad day, those referral logs make me feel better (when it's not just Russian referral spam). I might be wrong on this one, but I would wager that a lot of people who have their own blog can relate to that. + + diff --git a/markdown/org/blog/privacy-choices/en.md b/markdown/org/blog/privacy-choices/en.md new file mode 100644 index 00000000000..0cfae674ecd --- /dev/null +++ b/markdown/org/blog/privacy-choices/en.md @@ -0,0 +1,65 @@ +--- +author: "joostdecock" +caption: "Picture by Herbert" +date: "2017-06-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8ccbb2d5b50eb0917c6bd2befb2b098b6d667ba9-1920x1280.jpg" +intro: "The world wide web is increasingly eroding your privacy. Facebook, Google, and an avalanche of ad networks out there are all keeping tabs on your browser tabs. Tracking you on the web, keeping an an eye on the sites your visiting, so that they can gather more info on you, and sell that to advertisers." +title: "The choices I've made to protect your privacy. Or why you won't be getting any cookies." +--- + +The world wide web is increasingly eroding your privacy. Facebook, Google, and an avalanche of ad networks out there are all keeping tabs on your browser tabs. Tracking you on the web, keeping an an eye on the sites your visiting, so that they can gather more info on you, and sell that to advertisers. + +Pardon my French, but I hate that shit. + +> Facebook, Google, and an avalanche of ad networks out there are all keeping tabs on your browser tabs + +Building this site from scratch has been a great opportunity to reflect on how to do things. + +To make sure I'm not contributing to the problem, I've made the following choices: + +## Encryption everywhere + +Let's run everything over https. That's just [common sense](https://letsencrypt.org/) in 2017. + +## No ads + +This one is another no-brainer. The number 1 tracking pest online are ad networks, and I want them nowhere near this site. + +Fortunately, that doesn't pose a problem given that we don't play by the _Give something for free, then sell people's data_ rules of the web. + +## No external code + +This site loads no external JavaScript code. None. Which does mean I had to rethink a few things that typically require external code. + +There is no Facebook Like button or Twitter integration. We still have social sharing under our blog posts (hint hint) but it's the plain vanilla HTML variety that prevents tracking. + +In the same category, there's no social logins. Sure a _Login with Facebook_ button is handy, but also kind of a nightmare when you consider what it does to your privacy. + +For a statically generated site like this ([see this post about JAMstack for details](/blog/freesewing-goes-jamstack/)) [Disqus](https://disqus.com/) is pretty much the de facto standard for comments. But Disqus is pretty awful when it comes to tracking, so that was a big no-no to me. + +A similar story for authentication where I considered [Auth0](https://auth0.com/). There too, I was concerned about tracking, so I decided against it. + +I ended up just biting the bullet and implemented authentication and comments myself. Time will tell of that was a good trade-of. + +## No cookies +We don't use any cookies. Obviously no third-party cookies, but not even cookies of our own. + +Instead, we use local storage which is better because unlike cookies, it doesn't send your info on every request. + +## No analytics +I ran [Google Analytics](https://analytics.google.com/) on [makemypattern](https://makemypattern.com/). It's powerful, but obviously a tracking nightmare. So I wasn't going to have that either. + +This issue is further complicated by the fact that this static site is hosted by [Netlify](https://www.netlify.com/). So I don't have server logs and can't run any analytics server-side. + +For the most part, I decided to just go without analytics. I don't need to know how many people are visiting this site. I still know how many user accounts are created, and how many patterns are generated, which should be fine indicators for the site's overall well-being. + +But there's one thing that wanted to keep from analytics: the referral logs. It's one of life's small pleasures to go through that list and discover +[somebody](https://www.reddit.com/r/freepatterns/comments/4zh5nr/is_there_software_to_generate_sewing_patterns/) +[linked](http://www.makery.uk/2016/08/the-refashioners-2016-joost/) +[to](https://closetcasepatterns.com/week-sewing-blogs-vol-98/) +[you](https://opensource.com/life/16/11/free-open-sewing-patterns). + +Here too, I've implemented my own bare-bones solution. If you land on this site from an external link, we'll report that referral to our own API. Which means we still get the referral info, but no tracking. + +Perhaps it's just vanity, but when I'm having a bad day, those referral logs make me feel better (when it's not just Russian referral spam). I might be wrong on this one, but I would wager that a lot of people who have their own blog can relate to that. + diff --git a/markdown/org/blog/privacy-choices/es.md b/markdown/org/blog/privacy-choices/es.md new file mode 100644 index 00000000000..047561de0c4 --- /dev/null +++ b/markdown/org/blog/privacy-choices/es.md @@ -0,0 +1,65 @@ +--- +author: "joostdecock" +caption: "Picture by Herbert" +date: "2017-06-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8ccbb2d5b50eb0917c6bd2befb2b098b6d667ba9-1920x1280.jpg" +intro: "The world wide web is increasingly eroding your privacy. Facebook, Google, and an avalanche of ad networks out there are all keeping tabs on your browser tabs. Tracking you on the web, keeping an an eye on the sites your visiting, so that they can gather more info on you, and sell that to advertisers." +title: "The choices I've made to protect your privacy. Or why you won't be getting any cookies. [No traducido]" +--- + +The world wide web is increasingly eroding your privacy. Facebook, Google, and an avalanche of ad networks out there are all keeping tabs on your browser tabs. Tracking you on the web, keeping an an eye on the sites your visiting, so that they can gather more info on you, and sell that to advertisers. + +Pardon my French, but I hate that shit. + +> Facebook, Google, and an avalanche of ad networks out there are all keeping tabs on your browser tabs + +Building this site from scratch has been a great opportunity to reflect on how to do things. + +To make sure I'm not contributing to the problem, I've made the following choices: + +## Encryption everywhere + +Let's run everything over https. That's just [common sense](https://letsencrypt.org/) in 2017. + +## No ads + +This one is another no-brainer. The number 1 tracking pest online are ad networks, and I want them nowhere near this site. + +Fortunately, that doesn't pose a problem given that we don't play by the _Give something for free, then sell people's data_ rules of the web. + +## No external code + +This site loads no external JavaScript code. None. Which does mean I had to rethink a few things that typically require external code. + +There is no Facebook Like button or Twitter integration. We still have social sharing under our blog posts (hint hint) but it's the plain vanilla HTML variety that prevents tracking. + +In the same category, there's no social logins. Sure a _Login with Facebook_ button is handy, but also kind of a nightmare when you consider what it does to your privacy. + +For a statically generated site like this ([see this post about JAMstack for details](/blog/freesewing-goes-jamstack/)) [Disqus](https://disqus.com/) is pretty much the de facto standard for comments. But Disqus is pretty awful when it comes to tracking, so that was a big no-no to me. + +A similar story for authentication where I considered [Auth0](https://auth0.com/). There too, I was concerned about tracking, so I decided against it. + +I ended up just biting the bullet and implemented authentication and comments myself. Time will tell of that was a good trade-of. + +## No cookies +We don't use any cookies. Obviously no third-party cookies, but not even cookies of our own. + +Instead, we use local storage which is better because unlike cookies, it doesn't send your info on every request. + +## No analytics +I ran [Google Analytics](https://analytics.google.com/) on [makemypattern](https://makemypattern.com/). It's powerful, but obviously a tracking nightmare. So I wasn't going to have that either. + +This issue is further complicated by the fact that this static site is hosted by [Netlify](https://www.netlify.com/). So I don't have server logs and can't run any analytics server-side. + +For the most part, I decided to just go without analytics. I don't need to know how many people are visiting this site. I still know how many user accounts are created, and how many patterns are generated, which should be fine indicators for the site's overall well-being. + +But there's one thing that wanted to keep from analytics: the referral logs. It's one of life's small pleasures to go through that list and discover +[somebody](https://www.reddit.com/r/freepatterns/comments/4zh5nr/is_there_software_to_generate_sewing_patterns/) +[linked](http://www.makery.uk/2016/08/the-refashioners-2016-joost/) +[to](https://closetcasepatterns.com/week-sewing-blogs-vol-98/) +[you](https://opensource.com/life/16/11/free-open-sewing-patterns). + +Here too, I've implemented my own bare-bones solution. If you land on this site from an external link, we'll report that referral to our own API. Which means we still get the referral info, but no tracking. + +Perhaps it's just vanity, but when I'm having a bad day, those referral logs make me feel better (when it's not just Russian referral spam). I might be wrong on this one, but I would wager that a lot of people who have their own blog can relate to that. + diff --git a/markdown/org/blog/privacy-choices/fr.md b/markdown/org/blog/privacy-choices/fr.md new file mode 100644 index 00000000000..e13793db57a --- /dev/null +++ b/markdown/org/blog/privacy-choices/fr.md @@ -0,0 +1,65 @@ +--- +author: "joostdecock" +caption: "Picture by Herbert" +date: "2017-06-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8ccbb2d5b50eb0917c6bd2befb2b098b6d667ba9-1920x1280.jpg" +intro: "The world wide web is increasingly eroding your privacy. Facebook, Google, and an avalanche of ad networks out there are all keeping tabs on your browser tabs. Tracking you on the web, keeping an an eye on the sites your visiting, so that they can gather more info on you, and sell that to advertisers." +title: "The choices I've made to protect your privacy. Or why you won't be getting any cookies. [Non traduit]" +--- + +The world wide web is increasingly eroding your privacy. Facebook, Google, and an avalanche of ad networks out there are all keeping tabs on your browser tabs. Tracking you on the web, keeping an an eye on the sites your visiting, so that they can gather more info on you, and sell that to advertisers. + +Pardon my French, but I hate that shit. + +> Facebook, Google, and an avalanche of ad networks out there are all keeping tabs on your browser tabs + +Building this site from scratch has been a great opportunity to reflect on how to do things. + +To make sure I'm not contributing to the problem, I've made the following choices: + +## Encryption everywhere + +Let's run everything over https. That's just [common sense](https://letsencrypt.org/) in 2017. + +## No ads + +This one is another no-brainer. The number 1 tracking pest online are ad networks, and I want them nowhere near this site. + +Fortunately, that doesn't pose a problem given that we don't play by the _Give something for free, then sell people's data_ rules of the web. + +## No external code + +This site loads no external JavaScript code. None. Which does mean I had to rethink a few things that typically require external code. + +There is no Facebook Like button or Twitter integration. We still have social sharing under our blog posts (hint hint) but it's the plain vanilla HTML variety that prevents tracking. + +In the same category, there's no social logins. Sure a _Login with Facebook_ button is handy, but also kind of a nightmare when you consider what it does to your privacy. + +For a statically generated site like this ([see this post about JAMstack for details](/blog/freesewing-goes-jamstack/)) [Disqus](https://disqus.com/) is pretty much the de facto standard for comments. But Disqus is pretty awful when it comes to tracking, so that was a big no-no to me. + +A similar story for authentication where I considered [Auth0](https://auth0.com/). There too, I was concerned about tracking, so I decided against it. + +I ended up just biting the bullet and implemented authentication and comments myself. Time will tell of that was a good trade-of. + +## No cookies +We don't use any cookies. Obviously no third-party cookies, but not even cookies of our own. + +Instead, we use local storage which is better because unlike cookies, it doesn't send your info on every request. + +## No analytics +I ran [Google Analytics](https://analytics.google.com/) on [makemypattern](https://makemypattern.com/). It's powerful, but obviously a tracking nightmare. So I wasn't going to have that either. + +This issue is further complicated by the fact that this static site is hosted by [Netlify](https://www.netlify.com/). So I don't have server logs and can't run any analytics server-side. + +For the most part, I decided to just go without analytics. I don't need to know how many people are visiting this site. I still know how many user accounts are created, and how many patterns are generated, which should be fine indicators for the site's overall well-being. + +But there's one thing that wanted to keep from analytics: the referral logs. It's one of life's small pleasures to go through that list and discover +[somebody](https://www.reddit.com/r/freepatterns/comments/4zh5nr/is_there_software_to_generate_sewing_patterns/) +[linked](http://www.makery.uk/2016/08/the-refashioners-2016-joost/) +[to](https://closetcasepatterns.com/week-sewing-blogs-vol-98/) +[you](https://opensource.com/life/16/11/free-open-sewing-patterns). + +Here too, I've implemented my own bare-bones solution. If you land on this site from an external link, we'll report that referral to our own API. Which means we still get the referral info, but no tracking. + +Perhaps it's just vanity, but when I'm having a bad day, those referral logs make me feel better (when it's not just Russian referral spam). I might be wrong on this one, but I would wager that a lot of people who have their own blog can relate to that. + diff --git a/markdown/org/blog/privacy-choices/nl.md b/markdown/org/blog/privacy-choices/nl.md new file mode 100644 index 00000000000..56d83f7f293 --- /dev/null +++ b/markdown/org/blog/privacy-choices/nl.md @@ -0,0 +1,65 @@ +--- +author: "joostdecock" +caption: "Picture by Herbert" +date: "2017-06-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8ccbb2d5b50eb0917c6bd2befb2b098b6d667ba9-1920x1280.jpg" +intro: "The world wide web is increasingly eroding your privacy. Facebook, Google, and an avalanche of ad networks out there are all keeping tabs on your browser tabs. Tracking you on the web, keeping an an eye on the sites your visiting, so that they can gather more info on you, and sell that to advertisers." +title: "The choices I've made to protect your privacy. Or why you won't be getting any cookies. [Niet vertaald]" +--- + +The world wide web is increasingly eroding your privacy. Facebook, Google, and an avalanche of ad networks out there are all keeping tabs on your browser tabs. Tracking you on the web, keeping an an eye on the sites your visiting, so that they can gather more info on you, and sell that to advertisers. + +Pardon my French, but I hate that shit. + +> Facebook, Google, and an avalanche of ad networks out there are all keeping tabs on your browser tabs + +Building this site from scratch has been a great opportunity to reflect on how to do things. + +To make sure I'm not contributing to the problem, I've made the following choices: + +## Encryption everywhere + +Let's run everything over https. That's just [common sense](https://letsencrypt.org/) in 2017. + +## No ads + +This one is another no-brainer. The number 1 tracking pest online are ad networks, and I want them nowhere near this site. + +Fortunately, that doesn't pose a problem given that we don't play by the _Give something for free, then sell people's data_ rules of the web. + +## No external code + +This site loads no external JavaScript code. None. Which does mean I had to rethink a few things that typically require external code. + +There is no Facebook Like button or Twitter integration. We still have social sharing under our blog posts (hint hint) but it's the plain vanilla HTML variety that prevents tracking. + +In the same category, there's no social logins. Sure a _Login with Facebook_ button is handy, but also kind of a nightmare when you consider what it does to your privacy. + +For a statically generated site like this ([see this post about JAMstack for details](/blog/freesewing-goes-jamstack/)) [Disqus](https://disqus.com/) is pretty much the de facto standard for comments. But Disqus is pretty awful when it comes to tracking, so that was a big no-no to me. + +A similar story for authentication where I considered [Auth0](https://auth0.com/). There too, I was concerned about tracking, so I decided against it. + +I ended up just biting the bullet and implemented authentication and comments myself. Time will tell of that was a good trade-of. + +## No cookies +We don't use any cookies. Obviously no third-party cookies, but not even cookies of our own. + +Instead, we use local storage which is better because unlike cookies, it doesn't send your info on every request. + +## No analytics +I ran [Google Analytics](https://analytics.google.com/) on [makemypattern](https://makemypattern.com/). It's powerful, but obviously a tracking nightmare. So I wasn't going to have that either. + +This issue is further complicated by the fact that this static site is hosted by [Netlify](https://www.netlify.com/). So I don't have server logs and can't run any analytics server-side. + +For the most part, I decided to just go without analytics. I don't need to know how many people are visiting this site. I still know how many user accounts are created, and how many patterns are generated, which should be fine indicators for the site's overall well-being. + +But there's one thing that wanted to keep from analytics: the referral logs. It's one of life's small pleasures to go through that list and discover +[somebody](https://www.reddit.com/r/freepatterns/comments/4zh5nr/is_there_software_to_generate_sewing_patterns/) +[linked](http://www.makery.uk/2016/08/the-refashioners-2016-joost/) +[to](https://closetcasepatterns.com/week-sewing-blogs-vol-98/) +[you](https://opensource.com/life/16/11/free-open-sewing-patterns). + +Here too, I've implemented my own bare-bones solution. If you land on this site from an external link, we'll report that referral to our own API. Which means we still get the referral info, but no tracking. + +Perhaps it's just vanity, but when I'm having a bad day, those referral logs make me feel better (when it's not just Russian referral spam). I might be wrong on this one, but I would wager that a lot of people who have their own blog can relate to that. + diff --git a/markdown/org/blog/react-17/de.md b/markdown/org/blog/react-17/de.md new file mode 100644 index 00000000000..4a49113c7b8 --- /dev/null +++ b/markdown/org/blog/react-17/de.md @@ -0,0 +1,97 @@ +--- +author: "joostdecock" +caption: "Kurze Anerkennung für nappy.co für das Bild" +date: "2021-05-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0145547c8ba61dde1a6553dc8de318f53e27cbe5-2000x1333.jpg" +intro: "Wir haben heute FreeSewing v2.16 veröffentlicht. Der oberflächliche Beobachter erkennt nicht viele Änderungen. Und für die Nutzer dieser Website ist das sicherlich der Fall." +title: "FreeSewing 2.16 enthält React 17 und Webpack 5" +--- + + +Wir haben heute FreeSewing v2.16 veröffentlicht. Der oberflächliche Beobachter erkennt nicht viele Änderungen. Und für die Nutzer dieser Website ist das sicherlich der Fall. + +Gehe aber nur ein wenig in die Tiefe, und du erkennst, dass eine ganze Menge Arbeit in dieser Version steckt. + +Schauen wir uns doch einmal an, was sich alles geändert hat: + +## create-freesewing-pattern + +Die größte Änderung betrifft [create-freesewing-pattern](https://www.npmjs.com/package/create-freesewing-pattern) und die Entwicklungsumgebung, die es für dich einrichtet. + +Unter der Haube verwenden wir [create-react-app](https://www.npmjs.com/package/create-react-app) (alias CRA), und FreeSewing 2.16 ist die erste Version, die [React](https://reactjs.org/) 17, CRA 4 und [Webpack](https://webpack.js.org/) 5 enthält. + +Die Migration zu CRA 4 (und seinem Begleiter, [react-scripts](https://www.npmjs.com/package/react-scripts) 4) ist signifikant, weil es eine ganz neue Art und Weise für den hot-reload deiner Anwendung enthält, genannt `FAST_REFRESH`. + +Der Nachteil ist, dass das nur für *lokale Komponenten* deiner Anwendung geht. Und da unsere Entwicklungsumgebung deinen Schnittmustercode als (lokale) Dependency lädt, wird es nicht neugeladen, wenn du die Datei deines Schnittmusters änderst. + +Schlimmer noch, Webpack 5 behält die erstellten Dependencies als Cache im Speicher. So werden selbst beim Neustart der Entwicklungsumgebung die Änderungen, die du an deinem Schnittmuster vorgenommen hast, nicht angezeigt. + +Das ist selbstverständlich nicht cool. Und während es durchaus Möglichkeiten gibt, Webpack so zu konfigurieren, dass es sich so verhält wie wir wollen, erlaubt CRA so eine Art von Anpassung nicht. Es ist zwar jederzeit möglich, die CRA Konfiguration abzustoßen (oder react-scripts zu forken), das würde aber zu viel Mehraufwand in der Wartung bedeuten. + +## Die FreeSewing Entwicklungsumgebung: Jetzt mit fast refresh + +Wir wollen, dass die Entwicklungsumgebung alle Änderungen widerspiegelt, die du an deinem Code vornimmst. Und wir würden gerne die neue fast refresh Funktion nutzen, weil sie ziemlich toll ist. + +Im Gegensatz zum vorherigen hot-reload, der einfach nur die Seite neugeladen hat, kann fast refresh eine geänderte React-Komponente dynamisch aktualisieren. + +Das ist eine wichtige Unterscheidung, weil ein Neuladen der Seite die Entwicklungsumgebung in den Zustand zurücksetzt, der im lokalen Speicher gespeichert ist. Das umfasst zwar die allerwichtigsten Dinge wie Körpermaße, aber es beinhaltet nicht, was genau du dir in der Entwicklungsumgebung angeschaut hast, die Konfiguration des Schnittmusters, und so weiter. Also brauchtest du mit jedem Neuladen ein paar Klicks, um wieder dorthin zu kommen, wo du vorher warst, was ein wenig nervig war. + +Fast refresh hat das Potential, das zu beheben, und alles was wir tun müssen, damit es funktionieren kann, ist das Schnittmuster als lokale Komponente zu laden. Leider verwendet CRA das `ModuleScopePlugin` von Webpack, das es uns verbietet, lokalen Code von außerhalb des `example/src`-Ordners zu importieren. + +Um dieses Problem zu umgehen, wird das Ausführen von + +```bash +npx create-freesewing-pattern +``` + +nun einen symbolischen Link von `example/src/pattern` im root-Ordner deines Schnittmusters anlegen. Das bringt den Code in den lokalen Bereich, so dass er korrekt geladen und fast-refreshed werden kann. + +Dieser Ansatz hat einen weiteren Vorteil: Wo zuvor zwei Terminals laufen mussten — eines zum Erstellen/Beobachten des Schnittmustercodes, und eines zum Erstellen/Beobachten der Entwicklungsumgebung —, brauchst du jetzt nur noch eines, weil die Entwicklungsumgebung nun auch den Schnittmustercode erstellen/beobachten kann. + +Entwickler, frohlocket 🎉 + +## Migration von react-markdown 5 zu 6 + +Eine weitere wichtige Änderung ist [react-markdown](https://www.npmjs.com/package/react-markdown). Wir haben es bereits auf unseren Webseiten aktualisiert (Teil der Migration nach Gatsby v3, die wir Anfang dieses Monats abgeschlossen haben), aber wir verwenden es auch in unserer Entwicklungsumgebung. + +Es handelt sich um eine relativ triviale Änderung, bei der der Markdown-Inhalt nicht mehr als expliziter prop übergeben wird: + +```jsx + +``` + +Sondern stattdessen via dem besonderen *children* prop. + +```jsx +Hello, I am **Markdown** +``` + +## Aktualisierte rollup-Plugins + +Die folgenden rollup-Plugins haben ebenfalls einige wesentliche Änderungen erfahren: + +- rollup-plugin-terser 6 => 7 +- @rollup/plugin-commonjs 14 => 19 +- @rollup/plugin-node-resolve 8 => 13 + +Dies sollte keine Probleme verursachen, vielleicht höchstens, wenn du deine freesewing-Schnittmuster selber bündelst. Wenn du auf irgendwelche Probleme stößst, [sag uns Bescheid](https://discord.freesewing.org/). + +## Standardwerte für browserlist + +Wir verwenden nun die empfohlenen `default`-Einstellungen für [browserlist](https://github.com/browserslist/browserslist), was die Browser-Unterstützung von Cross-Compilern wie [Babel](https://babeljs.io/) steuert. + +Früher hatten wir eine Reihe von eigenen Einstellungen, aber es gibt keinen wirklichen Grund für uns, nicht an den Standardeinstellungen festzuhalten. + +Dies könnte möglicherweise Auswirkungen auf die Unterstützung von wirklich alten Browsern haben, aber wahrscheinlich wird auch das größtenteils unbemerkt bleiben. + +## Zusammenfassung + +Im FreeSewing-Code selber hat sich nicht so viel verändert, aber es gibt eine ganze Reihe an Änderungen, die die dependencies und bundler beeinflussen. + +Dies sind typischerweise die schwierigsten und esoterischsten Dinge eines jeden JavaScript-Projekts. + +Wenn du nach dem Upgrade auf FreeSewing v2.16 auf irgendwelche Probleme stößt, komm in [unseren Discord-Server](https://discord.freesewing.org/), damit wir dir weiterhelfen können. + +Nichtsdestotrotz solltest du eigentlich keine Probleme haben, solange du die gleiche Version der verschiedenen FreeSewing-Pakete verwendest. + + diff --git a/markdown/org/blog/react-17/en.md b/markdown/org/blog/react-17/en.md new file mode 100644 index 00000000000..1dfa1220aa9 --- /dev/null +++ b/markdown/org/blog/react-17/en.md @@ -0,0 +1,98 @@ +--- +author: "joostdecock" +caption: "Hat-tip to nappy.co for the picture" +date: "2021-05-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0145547c8ba61dde1a6553dc8de318f53e27cbe5-2000x1333.jpg" +intro: "FreeSewing 2.16 comes with React 17 and Webpack 5" +title: "FreeSewing 2.16 comes with React 17 and Webpack 5" +--- + + +We released FreeSewing v2.16 today. +To the casual observer, there's not that many changes. +And for users of this website, that's certainly the case. + +Scratch the surface however, and you'll find a lot of work went into this release. + +Let's look at what's been changed: + +## create-freesewing-pattern + +The biggest change is related to [create-freesewing-pattern](https://www.npmjs.com/package/create-freesewing-pattern) and the development environment it sets up for you. + +We use [create-react-app](https://www.npmjs.com/package/create-react-app) (aka CRA) under the hood, and FreeSewing 2.16 is our first release to ship with [React](https://reactjs.org/) 17, CRA 4, and [Webpack](https://webpack.js.org/) 5. + +That migration to CRA 4 (and its companion [react-scripts](https://www.npmjs.com/package/react-scripts) 4) is significant be because it has a whole new way of hot-reloading your application, called `FAST_REFRESH`. + +The downside is that it will only work for *local components* in your app. And since our development environment loads your pattern code as a (local) dependency, it does not reload when you change your pattern file. + +To make matters worse, Webpack 5 will keep a cache in memory of the built dependencies. So even restarting the development environment won't show the changes you've made to your pattern. + +Obviously, that ain't cool. And while there's certainly ways to configure Webpack to behave as we want it to, CRA doesn't allow for that sort of customization. You can always eject the CRA configuration (or fork react-scripts) but that would create too much maintenance overhead. + +## The FreeSewing development environment: Now with fast refresh + +We want the development environment to reflect any changes you make to your code. And we'd like to use the new fast refresh feature because it's pretty great. + +Unlike the previous hot-reload that would just reload the page, fast refresh can dynamically update a changed React component. + +That's an important distinction because a page reload will reset the development environment to the state that's stored in local storage. That includes the most important things like measurements, but it does not include what you were looking at in the development environment, pattern configuration, and so on. So each reload you'd need a few clicks to get back to what you were doing, which was a bit of an annoyance. + +Fast refresh has the potential to fix that, and to enable it all we need to do is import the pattern as a local component. Alas, CRA uses Webpack's `ModuleScopePlugin` which forbids importing local code from outside the `example/src` folder. + +To sidestep that issue, running: + +```bash +npx create-freesewing-pattern +``` + +will now symlink `example/src/pattern` to the root folder of your pattern. That brings the code into the local scope, so it can be correctly loaded and fast-refreshed. + +There's another advantage to this approach: Where previously you had to run two terminals — one to build/watch the pattern code and one to build/watch the development environment — you now need to load just one because the development environment will also build/watch the pattern code. + +Developers rejoice 🎉 + +## Migration of react-markdown 5 to 6 + +Another major change is [react-markdown](https://www.npmjs.com/package/react-markdown). We've already upgraded it on our websites (part of the migration to Gatsby v3 that we completed earlier this month), but we're also using it in our development environment. + +It's a relatively trivial change where the markdown content is no longer passed in as an explicit prop: + +```jsx + +``` + +But rather via the special *children* prop. + +```jsx +Hello, I am **Markdown** +``` + +## Upgraded rollup plugins + +The following rollup-plugins also had some major changes: + +- rollup-plugin-terser 6 => 7 +- @rollup/plugin-commonjs 14 => 19 +- @rollup/plugin-node-resolve 8 => 13 + +This should not cause any issues unless perhaps you're bundling your own freesewing patterns. If you hit any snags, [let us know](https://discord.freesewing.org/). + +## Defaults for browserlist + +We now use the recommended `defaults` setting for [browserlist](https://github.com/browserslist/browserslist) which controls browser support for cross-compilers such as [Babel](https://babeljs.io/). + +We used to have a set of custom settings but there is no real reason for us to not stick to the defaults. + +This could potentiality impact browser support for some really old browsers, but chances are this too will pass under the radar. + +## Summary + +Not so much has changed in the FreeSewing code itself, but there's a bunch of changes that impact the dependencies and bundlers. + +These are typically the hardest and most esoteric things about any JavaScript project. + +If you run into any problems after upgrading to FreeSewing v2.16, please [hop onto our Discord server](https://discord.freesewing.org/) so we can help you out. + +That being said, as long as you use the same version of different FreeSewing packages, you should not have any problems. + diff --git a/markdown/org/blog/react-17/es.md b/markdown/org/blog/react-17/es.md new file mode 100644 index 00000000000..52c89ca8946 --- /dev/null +++ b/markdown/org/blog/react-17/es.md @@ -0,0 +1,98 @@ +--- +author: "joostdecock" +caption: "Hat-tip to nappy.co for the picture" +date: "2021-05-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0145547c8ba61dde1a6553dc8de318f53e27cbe5-2000x1333.jpg" +intro: "FreeSewing 2.16 comes with React 17 and Webpack 5 [No traducido]" +title: "FreeSewing 2.16 comes with React 17 and Webpack 5 [No traducido]" +--- + + +We released FreeSewing v2.16 today. +To the casual observer, there's not that many changes. +And for users of this website, that's certainly the case. + +Scratch the surface however, and you'll find a lot of work went into this release. + +Let's look at what's been changed: + +## create-freesewing-pattern + +The biggest change is related to [create-freesewing-pattern](https://www.npmjs.com/package/create-freesewing-pattern) and the development environment it sets up for you. + +We use [create-react-app](https://www.npmjs.com/package/create-react-app) (aka CRA) under the hood, and FreeSewing 2.16 is our first release to ship with [React](https://reactjs.org/) 17, CRA 4, and [Webpack](https://webpack.js.org/) 5. + +That migration to CRA 4 (and its companion [react-scripts](https://www.npmjs.com/package/react-scripts) 4) is significant be because it has a whole new way of hot-reloading your application, called `FAST_REFRESH`. + +The downside is that it will only work for *local components* in your app. And since our development environment loads your pattern code as a (local) dependency, it does not reload when you change your pattern file. + +To make matters worse, Webpack 5 will keep a cache in memory of the built dependencies. So even restarting the development environment won't show the changes you've made to your pattern. + +Obviously, that ain't cool. And while there's certainly ways to configure Webpack to behave as we want it to, CRA doesn't allow for that sort of customization. You can always eject the CRA configuration (or fork react-scripts) but that would create too much maintenance overhead. + +## The FreeSewing development environment: Now with fast refresh + +We want the development environment to reflect any changes you make to your code. And we'd like to use the new fast refresh feature because it's pretty great. + +Unlike the previous hot-reload that would just reload the page, fast refresh can dynamically update a changed React component. + +That's an important distinction because a page reload will reset the development environment to the state that's stored in local storage. That includes the most important things like measurements, but it does not include what you were looking at in the development environment, pattern configuration, and so on. So each reload you'd need a few clicks to get back to what you were doing, which was a bit of an annoyance. + +Fast refresh has the potential to fix that, and to enable it all we need to do is import the pattern as a local component. Alas, CRA uses Webpack's `ModuleScopePlugin` which forbids importing local code from outside the `example/src` folder. + +To sidestep that issue, running: + +```bash +npx create-freesewing-pattern +``` + +will now symlink `example/src/pattern` to the root folder of your pattern. That brings the code into the local scope, so it can be correctly loaded and fast-refreshed. + +There's another advantage to this approach: Where previously you had to run two terminals — one to build/watch the pattern code and one to build/watch the development environment — you now need to load just one because the development environment will also build/watch the pattern code. + +Developers rejoice 🎉 + +## Migration of react-markdown 5 to 6 + +Another major change is [react-markdown](https://www.npmjs.com/package/react-markdown). We've already upgraded it on our websites (part of the migration to Gatsby v3 that we completed earlier this month), but we're also using it in our development environment. + +It's a relatively trivial change where the markdown content is no longer passed in as an explicit prop: + +```jsx + +``` + +But rather via the special *children* prop. + +```jsx +Hello, I am **Markdown** +``` + +## Upgraded rollup plugins + +The following rollup-plugins also had some major changes: + +- rollup-plugin-terser 6 => 7 +- @rollup/plugin-commonjs 14 => 19 +- @rollup/plugin-node-resolve 8 => 13 + +This should not cause any issues unless perhaps you're bundling your own freesewing patterns. If you hit any snags, [let us know](https://discord.freesewing.org/). + +## Defaults for browserlist + +We now use the recommended `defaults` setting for [browserlist](https://github.com/browserslist/browserslist) which controls browser support for cross-compilers such as [Babel](https://babeljs.io/). + +We used to have a set of custom settings but there is no real reason for us to not stick to the defaults. + +This could potentiality impact browser support for some really old browsers, but chances are this too will pass under the radar. + +## Summary + +Not so much has changed in the FreeSewing code itself, but there's a bunch of changes that impact the dependencies and bundlers. + +These are typically the hardest and most esoteric things about any JavaScript project. + +If you run into any problems after upgrading to FreeSewing v2.16, please [hop onto our Discord server](https://discord.freesewing.org/) so we can help you out. + +That being said, as long as you use the same version of different FreeSewing packages, you should not have any problems. + diff --git a/markdown/org/blog/react-17/fr.md b/markdown/org/blog/react-17/fr.md new file mode 100644 index 00000000000..483710da5e0 --- /dev/null +++ b/markdown/org/blog/react-17/fr.md @@ -0,0 +1,98 @@ +--- +author: "joostdecock" +caption: "Hat-tip to nappy.co for the picture" +date: "2021-05-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0145547c8ba61dde1a6553dc8de318f53e27cbe5-2000x1333.jpg" +intro: "FreeSewing 2.16 comes with React 17 and Webpack 5 [Non traduit]" +title: "FreeSewing 2.16 comes with React 17 and Webpack 5 [Non traduit]" +--- + + +We released FreeSewing v2.16 today. +To the casual observer, there's not that many changes. +And for users of this website, that's certainly the case. + +Scratch the surface however, and you'll find a lot of work went into this release. + +Let's look at what's been changed: + +## create-freesewing-pattern + +The biggest change is related to [create-freesewing-pattern](https://www.npmjs.com/package/create-freesewing-pattern) and the development environment it sets up for you. + +We use [create-react-app](https://www.npmjs.com/package/create-react-app) (aka CRA) under the hood, and FreeSewing 2.16 is our first release to ship with [React](https://reactjs.org/) 17, CRA 4, and [Webpack](https://webpack.js.org/) 5. + +That migration to CRA 4 (and its companion [react-scripts](https://www.npmjs.com/package/react-scripts) 4) is significant be because it has a whole new way of hot-reloading your application, called `FAST_REFRESH`. + +The downside is that it will only work for *local components* in your app. And since our development environment loads your pattern code as a (local) dependency, it does not reload when you change your pattern file. + +To make matters worse, Webpack 5 will keep a cache in memory of the built dependencies. So even restarting the development environment won't show the changes you've made to your pattern. + +Obviously, that ain't cool. And while there's certainly ways to configure Webpack to behave as we want it to, CRA doesn't allow for that sort of customization. You can always eject the CRA configuration (or fork react-scripts) but that would create too much maintenance overhead. + +## The FreeSewing development environment: Now with fast refresh + +We want the development environment to reflect any changes you make to your code. And we'd like to use the new fast refresh feature because it's pretty great. + +Unlike the previous hot-reload that would just reload the page, fast refresh can dynamically update a changed React component. + +That's an important distinction because a page reload will reset the development environment to the state that's stored in local storage. That includes the most important things like measurements, but it does not include what you were looking at in the development environment, pattern configuration, and so on. So each reload you'd need a few clicks to get back to what you were doing, which was a bit of an annoyance. + +Fast refresh has the potential to fix that, and to enable it all we need to do is import the pattern as a local component. Alas, CRA uses Webpack's `ModuleScopePlugin` which forbids importing local code from outside the `example/src` folder. + +To sidestep that issue, running: + +```bash +npx create-freesewing-pattern +``` + +will now symlink `example/src/pattern` to the root folder of your pattern. That brings the code into the local scope, so it can be correctly loaded and fast-refreshed. + +There's another advantage to this approach: Where previously you had to run two terminals — one to build/watch the pattern code and one to build/watch the development environment — you now need to load just one because the development environment will also build/watch the pattern code. + +Developers rejoice 🎉 + +## Migration of react-markdown 5 to 6 + +Another major change is [react-markdown](https://www.npmjs.com/package/react-markdown). We've already upgraded it on our websites (part of the migration to Gatsby v3 that we completed earlier this month), but we're also using it in our development environment. + +It's a relatively trivial change where the markdown content is no longer passed in as an explicit prop: + +```jsx + +``` + +But rather via the special *children* prop. + +```jsx +Hello, I am **Markdown** +``` + +## Upgraded rollup plugins + +The following rollup-plugins also had some major changes: + +- rollup-plugin-terser 6 => 7 +- @rollup/plugin-commonjs 14 => 19 +- @rollup/plugin-node-resolve 8 => 13 + +This should not cause any issues unless perhaps you're bundling your own freesewing patterns. If you hit any snags, [let us know](https://discord.freesewing.org/). + +## Defaults for browserlist + +We now use the recommended `defaults` setting for [browserlist](https://github.com/browserslist/browserslist) which controls browser support for cross-compilers such as [Babel](https://babeljs.io/). + +We used to have a set of custom settings but there is no real reason for us to not stick to the defaults. + +This could potentiality impact browser support for some really old browsers, but chances are this too will pass under the radar. + +## Summary + +Not so much has changed in the FreeSewing code itself, but there's a bunch of changes that impact the dependencies and bundlers. + +These are typically the hardest and most esoteric things about any JavaScript project. + +If you run into any problems after upgrading to FreeSewing v2.16, please [hop onto our Discord server](https://discord.freesewing.org/) so we can help you out. + +That being said, as long as you use the same version of different FreeSewing packages, you should not have any problems. + diff --git a/markdown/org/blog/react-17/nl.md b/markdown/org/blog/react-17/nl.md new file mode 100644 index 00000000000..a7dbf52ec26 --- /dev/null +++ b/markdown/org/blog/react-17/nl.md @@ -0,0 +1,98 @@ +--- +author: "joostdecock" +caption: "Hat-tip to nappy.co for the picture" +date: "2021-05-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0145547c8ba61dde1a6553dc8de318f53e27cbe5-2000x1333.jpg" +intro: "FreeSewing 2.16 comes with React 17 and Webpack 5 [Niet vertaald]" +title: "FreeSewing 2.16 comes with React 17 and Webpack 5 [Niet vertaald]" +--- + + +We released FreeSewing v2.16 today. +To the casual observer, there's not that many changes. +And for users of this website, that's certainly the case. + +Scratch the surface however, and you'll find a lot of work went into this release. + +Let's look at what's been changed: + +## create-freesewing-pattern + +The biggest change is related to [create-freesewing-pattern](https://www.npmjs.com/package/create-freesewing-pattern) and the development environment it sets up for you. + +We use [create-react-app](https://www.npmjs.com/package/create-react-app) (aka CRA) under the hood, and FreeSewing 2.16 is our first release to ship with [React](https://reactjs.org/) 17, CRA 4, and [Webpack](https://webpack.js.org/) 5. + +That migration to CRA 4 (and its companion [react-scripts](https://www.npmjs.com/package/react-scripts) 4) is significant be because it has a whole new way of hot-reloading your application, called `FAST_REFRESH`. + +The downside is that it will only work for *local components* in your app. And since our development environment loads your pattern code as a (local) dependency, it does not reload when you change your pattern file. + +To make matters worse, Webpack 5 will keep a cache in memory of the built dependencies. So even restarting the development environment won't show the changes you've made to your pattern. + +Obviously, that ain't cool. And while there's certainly ways to configure Webpack to behave as we want it to, CRA doesn't allow for that sort of customization. You can always eject the CRA configuration (or fork react-scripts) but that would create too much maintenance overhead. + +## The FreeSewing development environment: Now with fast refresh + +We want the development environment to reflect any changes you make to your code. And we'd like to use the new fast refresh feature because it's pretty great. + +Unlike the previous hot-reload that would just reload the page, fast refresh can dynamically update a changed React component. + +That's an important distinction because a page reload will reset the development environment to the state that's stored in local storage. That includes the most important things like measurements, but it does not include what you were looking at in the development environment, pattern configuration, and so on. So each reload you'd need a few clicks to get back to what you were doing, which was a bit of an annoyance. + +Fast refresh has the potential to fix that, and to enable it all we need to do is import the pattern as a local component. Alas, CRA uses Webpack's `ModuleScopePlugin` which forbids importing local code from outside the `example/src` folder. + +To sidestep that issue, running: + +```bash +npx create-freesewing-pattern +``` + +will now symlink `example/src/pattern` to the root folder of your pattern. That brings the code into the local scope, so it can be correctly loaded and fast-refreshed. + +There's another advantage to this approach: Where previously you had to run two terminals — one to build/watch the pattern code and one to build/watch the development environment — you now need to load just one because the development environment will also build/watch the pattern code. + +Developers rejoice 🎉 + +## Migration of react-markdown 5 to 6 + +Another major change is [react-markdown](https://www.npmjs.com/package/react-markdown). We've already upgraded it on our websites (part of the migration to Gatsby v3 that we completed earlier this month), but we're also using it in our development environment. + +It's a relatively trivial change where the markdown content is no longer passed in as an explicit prop: + +```jsx + +``` + +But rather via the special *children* prop. + +```jsx +Hello, I am **Markdown** +``` + +## Upgraded rollup plugins + +The following rollup-plugins also had some major changes: + +- rollup-plugin-terser 6 => 7 +- @rollup/plugin-commonjs 14 => 19 +- @rollup/plugin-node-resolve 8 => 13 + +This should not cause any issues unless perhaps you're bundling your own freesewing patterns. If you hit any snags, [let us know](https://discord.freesewing.org/). + +## Defaults for browserlist + +We now use the recommended `defaults` setting for [browserlist](https://github.com/browserslist/browserslist) which controls browser support for cross-compilers such as [Babel](https://babeljs.io/). + +We used to have a set of custom settings but there is no real reason for us to not stick to the defaults. + +This could potentiality impact browser support for some really old browsers, but chances are this too will pass under the radar. + +## Summary + +Not so much has changed in the FreeSewing code itself, but there's a bunch of changes that impact the dependencies and bundlers. + +These are typically the hardest and most esoteric things about any JavaScript project. + +If you run into any problems after upgrading to FreeSewing v2.16, please [hop onto our Discord server](https://discord.freesewing.org/) so we can help you out. + +That being said, as long as you use the same version of different FreeSewing packages, you should not have any problems. + diff --git a/markdown/org/blog/roundup-2017-09/de.md b/markdown/org/blog/roundup-2017-09/de.md new file mode 100644 index 00000000000..a7b82d9f39f --- /dev/null +++ b/markdown/org/blog/roundup-2017-09/de.md @@ -0,0 +1,115 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of october" +date: "2017-09-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c6418b621228730525d835acff53c4cd6895a865-2000x1250.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - September 2017: Simon complications, email issues, and donations are up this year. [Nicht übersetzt]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at september, and a bit of august +For this first edition, I'm looking back a bit further than one month, because [this site launched at the end of August](/blog/open-for-business/), so I'm including that week in this monthly roundup. + +### My name is Simon, and I'm complicated + +Since the launch, there's been [3 new path releases of freesewing core](https://github.com/freesewing/core/releases) --- you know, the thing that actually generates your sewing patterns --- and all of them were due to issues with [the Simon Shirt pattern](/patterns/simon). + +Full details are available in [the changelog](https://github.com/freesewing/core/blob/develop/CHANGELOG.md), but here's the gist of it: + + + - The seam allowance at the hem was incorrect when the lenthBonus was very low. + - The cut in the sleeve for the placket was too short + - There was a problem with the seam allowance at the buttonhole placket + - The sleeve length bonus was counted double + - The hip measurements/ease was not taken into account; The chest measurement/ease was used instead + - A number option defaults were tweaked + + +Thanks to [Tatyana](/users/yrhdw) and [Stefan](/users/kczrw) for reporting these issues. You get that funky bug badge: + +![I really like this one](https://posts.freesewing.org/uploads/badge_found_bug_d7d0c9055a.svg) + +#### What's your problem Simon? + +That these issues surface in Simon is not a coincidence. The pattern comes with a whopping 41 options that allow you to control pretty much every aspect of your shirt. + +Managing all those different combinations in the code leads to a lot of complexity. And were code complexity rises, bugs appear. + +![If Simon was on facebook, its relationship status would certainly be *It's complicated*](https://posts.freesewing.org/uploads/complicated_d8c872358d.gif) + +#### Is it time for an overhaul? +Simon is a port of the Singular Shirt pattern of MakeMyPattern.com. Back there, making a differently styled shirt would have involved copying the code over, making changes, and then maintaining two slightly different variations for all eternity. + +Things are better here at freesewing, where inheritance is baked in the system. +So I could (and should perhaps) have a basic shirt pattern, and then branch that out into a bunch of differently styled shirt patterns. + + - Brian Body Block + - Basic shirt pattern + - Casual shirt pattern + - Formal shirt pattern + - Some other shirt pattern + +It would not only cut down on code complexity, it would arguably also be more intuitive to see a bunch of differently styled shirt patterns, rather than have only one pattern and then have 41 options to juggle. + +A full Simon overhaul is going to be a bit of work, but it is possible. I'd be interested to hear your thoughts on the matter. + + +## Dealing with email delivery issues +I added a workaround for those of you who had trouble getting the registration emails. Basically, people with an email account managed by Microsoft. + +![If these guys run your inbox, then who knows what other emails you're not getting](msft.gif) + +You can read [my blog post on the matter](/blog/email-spam-problems/) for all the details, but basically if you have one of those addresses, you should get those emails now. The only downside is that you might get them twice. + +## Referrals +When people link to your site, and visitors click that link, that's called a referral. The bloggers among you might be familiar with skimming through your Google Analytics reports to see who's been linking to you. + +This site does not use Google Analytics --- there's [a blog post with details on that](/blog/privacy-choices/) too --- but still captures referrals. The overview of recent referrals is available for all to see on [the status page](/status). + +Linking to freesewing.org is obviously a nice thing to do, so I keep an eye on the referrals, and if a site shows up that belongs to a user, you get the Ambassador badge. + +![Linking to freesewing.org is one way to unlock the ambassasor badge](https://posts.freesewing.org/uploads/badge_ambassador_3dd1e722cc.svg) + +It's a small way to say thank you for spreading the word about freesewing. + +## Donations +During september, we passed last year's donations amount, so it's nice to see I'll be able to [send more money to MSF](/about/pledge#donations-history) this year than in 2016. + +You can always keep track of the donations on [the donations pledge page](/about/pledge#donations-history), but here's the current status: + +![Yay! Better than last year](https://posts.freesewing.org/uploads/donations_68e214d133.svg) + +## More download formats + +I've also added additional formats to the draft download page. You now have a choice of SVG, PDF, letter-PDF, tabloid-PDF, A4-PDF, A3-PDF, A2-PDF, A1-PDF, and A0-PDF. + +## The quality control badge +I've added the quality control badge for things like reporting (or fixing) typos, broken links, grammar, and other small improvements. + +![See a typo? Let me know and you get this](https://posts.freesewing.org/uploads/badge_quality_control_6acb8c10c2.svg) + +These might not seem like an earth-shattering contribution, but they are important nevertheless. + +On the spectrum between endlessly toiling over the perfect content before publishing it, or getting it out fast warts and all, I lean heavily towards the latter. +So I kinda count on you guys to let me know when I messed up. + +## Looking ahead to october + +There are 5 patterns I am currently working on. And all of them are ready to the point where I need to make them to verify that they work as intended. First a muslin, and then the real thing. + +That's a bit of a bottleneck for me because I have a long commute, so my sewing time is typically limited to the weekends. + +The only way I see to speed up the process of getting patterns released is to have people join in with the pattern testing. I don't think it's something I can ask people to do, because this is early stage testing. Not to mention that I have nothing to offer them to sweeten the deal. What am I going to give you, a free pattern? + +Still, on the off chance that some of you want to help out by making a muslin and letting me know how it went, here's what's currently on my drawing board: + + - A trouser block for men that should be better than Theo(dore) + - A block for selvedge jeans for men + - A zip-up hoodie for men + - A wintercoat + - A unisex leggins pattern + +Should any of you want to make one of these as a test, [let me know](/contact), it would really help me out. + diff --git a/markdown/org/blog/roundup-2017-09/en.md b/markdown/org/blog/roundup-2017-09/en.md new file mode 100644 index 00000000000..6b9ba74b709 --- /dev/null +++ b/markdown/org/blog/roundup-2017-09/en.md @@ -0,0 +1,115 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of october" +date: "2017-09-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c6418b621228730525d835acff53c4cd6895a865-2000x1250.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - September 2017: Simon complications, email issues, and donations are up this year." +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at september, and a bit of august +For this first edition, I'm looking back a bit further than one month, because [this site launched at the end of August](/blog/open-for-business/), so I'm including that week in this monthly roundup. + +### My name is Simon, and I'm complicated + +Since the launch, there's been [3 new path releases of freesewing core](https://github.com/freesewing/core/releases) --- you know, the thing that actually generates your sewing patterns --- and all of them were due to issues with [the Simon Shirt pattern](/patterns/simon). + +Full details are available in [the changelog](https://github.com/freesewing/core/blob/develop/CHANGELOG.md), but here's the gist of it: + + + - The seam allowance at the hem was incorrect when the lenthBonus was very low. + - The cut in the sleeve for the placket was too short + - There was a problem with the seam allowance at the buttonhole placket + - The sleeve length bonus was counted double + - The hip measurements/ease was not taken into account; The chest measurement/ease was used instead + - A number option defaults were tweaked + + +Thanks to [Tatyana](/users/yrhdw) and [Stefan](/users/kczrw) for reporting these issues. You get that funky bug badge: + +![I really like this one](https://posts.freesewing.org/uploads/badge_found_bug_d7d0c9055a.svg) + +#### What's your problem Simon? + +That these issues surface in Simon is not a coincidence. The pattern comes with a whopping 41 options that allow you to control pretty much every aspect of your shirt. + +Managing all those different combinations in the code leads to a lot of complexity. And were code complexity rises, bugs appear. + +![If Simon was on facebook, its relationship status would certainly be *It's complicated*](https://posts.freesewing.org/uploads/complicated_d8c872358d.gif) + +#### Is it time for an overhaul? +Simon is a port of the Singular Shirt pattern of MakeMyPattern.com. Back there, making a differently styled shirt would have involved copying the code over, making changes, and then maintaining two slightly different variations for all eternity. + +Things are better here at freesewing, where inheritance is baked in the system. +So I could (and should perhaps) have a basic shirt pattern, and then branch that out into a bunch of differently styled shirt patterns. + + - Brian Body Block + - Basic shirt pattern + - Casual shirt pattern + - Formal shirt pattern + - Some other shirt pattern + +It would not only cut down on code complexity, it would arguably also be more intuitive to see a bunch of differently styled shirt patterns, rather than have only one pattern and then have 41 options to juggle. + +A full Simon overhaul is going to be a bit of work, but it is possible. I'd be interested to hear your thoughts on the matter. + + +## Dealing with email delivery issues +I added a workaround for those of you who had trouble getting the registration emails. Basically, people with an email account managed by Microsoft. + +![If these guys run your inbox, then who knows what other emails you're not getting](msft.gif) + +You can read [my blog post on the matter](/blog/email-spam-problems/) for all the details, but basically if you have one of those addresses, you should get those emails now. The only downside is that you might get them twice. + +## Referrals +When people link to your site, and visitors click that link, that's called a referral. The bloggers among you might be familiar with skimming through your Google Analytics reports to see who's been linking to you. + +This site does not use Google Analytics --- there's [a blog post with details on that](/blog/privacy-choices/) too --- but still captures referrals. The overview of recent referrals is available for all to see on [the status page](/status). + +Linking to freesewing.org is obviously a nice thing to do, so I keep an eye on the referrals, and if a site shows up that belongs to a user, you get the Ambassador badge. + +![Linking to freesewing.org is one way to unlock the ambassasor badge](https://posts.freesewing.org/uploads/badge_ambassador_3dd1e722cc.svg) + +It's a small way to say thank you for spreading the word about freesewing. + +## Donations +During september, we passed last year's donations amount, so it's nice to see I'll be able to [send more money to MSF](/about/pledge#donations-history) this year than in 2016. + +You can always keep track of the donations on [the donations pledge page](/about/pledge#donations-history), but here's the current status: + +![Yay! Better than last year](https://posts.freesewing.org/uploads/donations_68e214d133.svg) + +## More download formats + +I've also added additional formats to the draft download page. You now have a choice of SVG, PDF, letter-PDF, tabloid-PDF, A4-PDF, A3-PDF, A2-PDF, A1-PDF, and A0-PDF. + +## The quality control badge +I've added the quality control badge for things like reporting (or fixing) typos, broken links, grammar, and other small improvements. + +![See a typo? Let me know and you get this](https://posts.freesewing.org/uploads/badge_quality_control_6acb8c10c2.svg) + +These might not seem like an earth-shattering contribution, but they are important nevertheless. + +On the spectrum between endlessly toiling over the perfect content before publishing it, or getting it out fast warts and all, I lean heavily towards the latter. +So I kinda count on you guys to let me know when I messed up. + +## Looking ahead to october + +There are 5 patterns I am currently working on. And all of them are ready to the point where I need to make them to verify that they work as intended. First a muslin, and then the real thing. + +That's a bit of a bottleneck for me because I have a long commute, so my sewing time is typically limited to the weekends. + +The only way I see to speed up the process of getting patterns released is to have people join in with the pattern testing. I don't think it's something I can ask people to do, because this is early stage testing. Not to mention that I have nothing to offer them to sweeten the deal. What am I going to give you, a free pattern? + +Still, on the off chance that some of you want to help out by making a muslin and letting me know how it went, here's what's currently on my drawing board: + + - A trouser block for men that should be better than Theo(dore) + - A block for selvedge jeans for men + - A zip-up hoodie for men + - A wintercoat + - A unisex leggins pattern + +Should any of you want to make one of these as a test, [let me know](/contact), it would really help me out. + diff --git a/markdown/org/blog/roundup-2017-09/es.md b/markdown/org/blog/roundup-2017-09/es.md new file mode 100644 index 00000000000..be8fd913372 --- /dev/null +++ b/markdown/org/blog/roundup-2017-09/es.md @@ -0,0 +1,115 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of october" +date: "2017-09-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c6418b621228730525d835acff53c4cd6895a865-2000x1250.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - September 2017: Simon complications, email issues, and donations are up this year. [No traducido]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at september, and a bit of august +For this first edition, I'm looking back a bit further than one month, because [this site launched at the end of August](/blog/open-for-business/), so I'm including that week in this monthly roundup. + +### My name is Simon, and I'm complicated + +Since the launch, there's been [3 new path releases of freesewing core](https://github.com/freesewing/core/releases) --- you know, the thing that actually generates your sewing patterns --- and all of them were due to issues with [the Simon Shirt pattern](/patterns/simon). + +Full details are available in [the changelog](https://github.com/freesewing/core/blob/develop/CHANGELOG.md), but here's the gist of it: + + + - The seam allowance at the hem was incorrect when the lenthBonus was very low. + - The cut in the sleeve for the placket was too short + - There was a problem with the seam allowance at the buttonhole placket + - The sleeve length bonus was counted double + - The hip measurements/ease was not taken into account; The chest measurement/ease was used instead + - A number option defaults were tweaked + + +Thanks to [Tatyana](/users/yrhdw) and [Stefan](/users/kczrw) for reporting these issues. You get that funky bug badge: + +![I really like this one](https://posts.freesewing.org/uploads/badge_found_bug_d7d0c9055a.svg) + +#### What's your problem Simon? + +That these issues surface in Simon is not a coincidence. The pattern comes with a whopping 41 options that allow you to control pretty much every aspect of your shirt. + +Managing all those different combinations in the code leads to a lot of complexity. And were code complexity rises, bugs appear. + +![If Simon was on facebook, its relationship status would certainly be *It's complicated*](https://posts.freesewing.org/uploads/complicated_d8c872358d.gif) + +#### Is it time for an overhaul? +Simon is a port of the Singular Shirt pattern of MakeMyPattern.com. Back there, making a differently styled shirt would have involved copying the code over, making changes, and then maintaining two slightly different variations for all eternity. + +Things are better here at freesewing, where inheritance is baked in the system. +So I could (and should perhaps) have a basic shirt pattern, and then branch that out into a bunch of differently styled shirt patterns. + + - Brian Body Block + - Basic shirt pattern + - Casual shirt pattern + - Formal shirt pattern + - Some other shirt pattern + +It would not only cut down on code complexity, it would arguably also be more intuitive to see a bunch of differently styled shirt patterns, rather than have only one pattern and then have 41 options to juggle. + +A full Simon overhaul is going to be a bit of work, but it is possible. I'd be interested to hear your thoughts on the matter. + + +## Dealing with email delivery issues +I added a workaround for those of you who had trouble getting the registration emails. Basically, people with an email account managed by Microsoft. + +![If these guys run your inbox, then who knows what other emails you're not getting](msft.gif) + +You can read [my blog post on the matter](/blog/email-spam-problems/) for all the details, but basically if you have one of those addresses, you should get those emails now. The only downside is that you might get them twice. + +## Referrals +When people link to your site, and visitors click that link, that's called a referral. The bloggers among you might be familiar with skimming through your Google Analytics reports to see who's been linking to you. + +This site does not use Google Analytics --- there's [a blog post with details on that](/blog/privacy-choices/) too --- but still captures referrals. The overview of recent referrals is available for all to see on [the status page](/status). + +Linking to freesewing.org is obviously a nice thing to do, so I keep an eye on the referrals, and if a site shows up that belongs to a user, you get the Ambassador badge. + +![Linking to freesewing.org is one way to unlock the ambassasor badge](https://posts.freesewing.org/uploads/badge_ambassador_3dd1e722cc.svg) + +It's a small way to say thank you for spreading the word about freesewing. + +## Donations +During september, we passed last year's donations amount, so it's nice to see I'll be able to [send more money to MSF](/about/pledge#donations-history) this year than in 2016. + +You can always keep track of the donations on [the donations pledge page](/about/pledge#donations-history), but here's the current status: + +![Yay! Better than last year](https://posts.freesewing.org/uploads/donations_68e214d133.svg) + +## More download formats + +I've also added additional formats to the draft download page. You now have a choice of SVG, PDF, letter-PDF, tabloid-PDF, A4-PDF, A3-PDF, A2-PDF, A1-PDF, and A0-PDF. + +## The quality control badge +I've added the quality control badge for things like reporting (or fixing) typos, broken links, grammar, and other small improvements. + +![See a typo? Let me know and you get this](https://posts.freesewing.org/uploads/badge_quality_control_6acb8c10c2.svg) + +These might not seem like an earth-shattering contribution, but they are important nevertheless. + +On the spectrum between endlessly toiling over the perfect content before publishing it, or getting it out fast warts and all, I lean heavily towards the latter. +So I kinda count on you guys to let me know when I messed up. + +## Looking ahead to october + +There are 5 patterns I am currently working on. And all of them are ready to the point where I need to make them to verify that they work as intended. First a muslin, and then the real thing. + +That's a bit of a bottleneck for me because I have a long commute, so my sewing time is typically limited to the weekends. + +The only way I see to speed up the process of getting patterns released is to have people join in with the pattern testing. I don't think it's something I can ask people to do, because this is early stage testing. Not to mention that I have nothing to offer them to sweeten the deal. What am I going to give you, a free pattern? + +Still, on the off chance that some of you want to help out by making a muslin and letting me know how it went, here's what's currently on my drawing board: + + - A trouser block for men that should be better than Theo(dore) + - A block for selvedge jeans for men + - A zip-up hoodie for men + - A wintercoat + - A unisex leggins pattern + +Should any of you want to make one of these as a test, [let me know](/contact), it would really help me out. + diff --git a/markdown/org/blog/roundup-2017-09/fr.md b/markdown/org/blog/roundup-2017-09/fr.md new file mode 100644 index 00000000000..50a40ea67bf --- /dev/null +++ b/markdown/org/blog/roundup-2017-09/fr.md @@ -0,0 +1,115 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of october" +date: "2017-09-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c6418b621228730525d835acff53c4cd6895a865-2000x1250.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - September 2017: Simon complications, email issues, and donations are up this year. [Non traduit]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at september, and a bit of august +For this first edition, I'm looking back a bit further than one month, because [this site launched at the end of August](/blog/open-for-business/), so I'm including that week in this monthly roundup. + +### My name is Simon, and I'm complicated + +Since the launch, there's been [3 new path releases of freesewing core](https://github.com/freesewing/core/releases) --- you know, the thing that actually generates your sewing patterns --- and all of them were due to issues with [the Simon Shirt pattern](/patterns/simon). + +Full details are available in [the changelog](https://github.com/freesewing/core/blob/develop/CHANGELOG.md), but here's the gist of it: + + + - The seam allowance at the hem was incorrect when the lenthBonus was very low. + - The cut in the sleeve for the placket was too short + - There was a problem with the seam allowance at the buttonhole placket + - The sleeve length bonus was counted double + - The hip measurements/ease was not taken into account; The chest measurement/ease was used instead + - A number option defaults were tweaked + + +Thanks to [Tatyana](/users/yrhdw) and [Stefan](/users/kczrw) for reporting these issues. You get that funky bug badge: + +![I really like this one](https://posts.freesewing.org/uploads/badge_found_bug_d7d0c9055a.svg) + +#### What's your problem Simon? + +That these issues surface in Simon is not a coincidence. The pattern comes with a whopping 41 options that allow you to control pretty much every aspect of your shirt. + +Managing all those different combinations in the code leads to a lot of complexity. And were code complexity rises, bugs appear. + +![If Simon was on facebook, its relationship status would certainly be *It's complicated*](https://posts.freesewing.org/uploads/complicated_d8c872358d.gif) + +#### Is it time for an overhaul? +Simon is a port of the Singular Shirt pattern of MakeMyPattern.com. Back there, making a differently styled shirt would have involved copying the code over, making changes, and then maintaining two slightly different variations for all eternity. + +Things are better here at freesewing, where inheritance is baked in the system. +So I could (and should perhaps) have a basic shirt pattern, and then branch that out into a bunch of differently styled shirt patterns. + + - Brian Body Block + - Basic shirt pattern + - Casual shirt pattern + - Formal shirt pattern + - Some other shirt pattern + +It would not only cut down on code complexity, it would arguably also be more intuitive to see a bunch of differently styled shirt patterns, rather than have only one pattern and then have 41 options to juggle. + +A full Simon overhaul is going to be a bit of work, but it is possible. I'd be interested to hear your thoughts on the matter. + + +## Dealing with email delivery issues +I added a workaround for those of you who had trouble getting the registration emails. Basically, people with an email account managed by Microsoft. + +![If these guys run your inbox, then who knows what other emails you're not getting](msft.gif) + +You can read [my blog post on the matter](/blog/email-spam-problems/) for all the details, but basically if you have one of those addresses, you should get those emails now. The only downside is that you might get them twice. + +## Referrals +When people link to your site, and visitors click that link, that's called a referral. The bloggers among you might be familiar with skimming through your Google Analytics reports to see who's been linking to you. + +This site does not use Google Analytics --- there's [a blog post with details on that](/blog/privacy-choices/) too --- but still captures referrals. The overview of recent referrals is available for all to see on [the status page](/status). + +Linking to freesewing.org is obviously a nice thing to do, so I keep an eye on the referrals, and if a site shows up that belongs to a user, you get the Ambassador badge. + +![Linking to freesewing.org is one way to unlock the ambassasor badge](https://posts.freesewing.org/uploads/badge_ambassador_3dd1e722cc.svg) + +It's a small way to say thank you for spreading the word about freesewing. + +## Donations +During september, we passed last year's donations amount, so it's nice to see I'll be able to [send more money to MSF](/about/pledge#donations-history) this year than in 2016. + +You can always keep track of the donations on [the donations pledge page](/about/pledge#donations-history), but here's the current status: + +![Yay! Better than last year](https://posts.freesewing.org/uploads/donations_68e214d133.svg) + +## More download formats + +I've also added additional formats to the draft download page. You now have a choice of SVG, PDF, letter-PDF, tabloid-PDF, A4-PDF, A3-PDF, A2-PDF, A1-PDF, and A0-PDF. + +## The quality control badge +I've added the quality control badge for things like reporting (or fixing) typos, broken links, grammar, and other small improvements. + +![See a typo? Let me know and you get this](https://posts.freesewing.org/uploads/badge_quality_control_6acb8c10c2.svg) + +These might not seem like an earth-shattering contribution, but they are important nevertheless. + +On the spectrum between endlessly toiling over the perfect content before publishing it, or getting it out fast warts and all, I lean heavily towards the latter. +So I kinda count on you guys to let me know when I messed up. + +## Looking ahead to october + +There are 5 patterns I am currently working on. And all of them are ready to the point where I need to make them to verify that they work as intended. First a muslin, and then the real thing. + +That's a bit of a bottleneck for me because I have a long commute, so my sewing time is typically limited to the weekends. + +The only way I see to speed up the process of getting patterns released is to have people join in with the pattern testing. I don't think it's something I can ask people to do, because this is early stage testing. Not to mention that I have nothing to offer them to sweeten the deal. What am I going to give you, a free pattern? + +Still, on the off chance that some of you want to help out by making a muslin and letting me know how it went, here's what's currently on my drawing board: + + - A trouser block for men that should be better than Theo(dore) + - A block for selvedge jeans for men + - A zip-up hoodie for men + - A wintercoat + - A unisex leggins pattern + +Should any of you want to make one of these as a test, [let me know](/contact), it would really help me out. + diff --git a/markdown/org/blog/roundup-2017-09/nl.md b/markdown/org/blog/roundup-2017-09/nl.md new file mode 100644 index 00000000000..53994318b15 --- /dev/null +++ b/markdown/org/blog/roundup-2017-09/nl.md @@ -0,0 +1,115 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of october" +date: "2017-09-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c6418b621228730525d835acff53c4cd6895a865-2000x1250.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - September 2017: Simon complications, email issues, and donations are up this year. [Niet vertaald]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at september, and a bit of august +For this first edition, I'm looking back a bit further than one month, because [this site launched at the end of August](/blog/open-for-business/), so I'm including that week in this monthly roundup. + +### My name is Simon, and I'm complicated + +Since the launch, there's been [3 new path releases of freesewing core](https://github.com/freesewing/core/releases) --- you know, the thing that actually generates your sewing patterns --- and all of them were due to issues with [the Simon Shirt pattern](/patterns/simon). + +Full details are available in [the changelog](https://github.com/freesewing/core/blob/develop/CHANGELOG.md), but here's the gist of it: + + + - The seam allowance at the hem was incorrect when the lenthBonus was very low. + - The cut in the sleeve for the placket was too short + - There was a problem with the seam allowance at the buttonhole placket + - The sleeve length bonus was counted double + - The hip measurements/ease was not taken into account; The chest measurement/ease was used instead + - A number option defaults were tweaked + + +Thanks to [Tatyana](/users/yrhdw) and [Stefan](/users/kczrw) for reporting these issues. You get that funky bug badge: + +![I really like this one](https://posts.freesewing.org/uploads/badge_found_bug_d7d0c9055a.svg) + +#### What's your problem Simon? + +That these issues surface in Simon is not a coincidence. The pattern comes with a whopping 41 options that allow you to control pretty much every aspect of your shirt. + +Managing all those different combinations in the code leads to a lot of complexity. And were code complexity rises, bugs appear. + +![If Simon was on facebook, its relationship status would certainly be *It's complicated*](https://posts.freesewing.org/uploads/complicated_d8c872358d.gif) + +#### Is it time for an overhaul? +Simon is a port of the Singular Shirt pattern of MakeMyPattern.com. Back there, making a differently styled shirt would have involved copying the code over, making changes, and then maintaining two slightly different variations for all eternity. + +Things are better here at freesewing, where inheritance is baked in the system. +So I could (and should perhaps) have a basic shirt pattern, and then branch that out into a bunch of differently styled shirt patterns. + + - Brian Body Block + - Basic shirt pattern + - Casual shirt pattern + - Formal shirt pattern + - Some other shirt pattern + +It would not only cut down on code complexity, it would arguably also be more intuitive to see a bunch of differently styled shirt patterns, rather than have only one pattern and then have 41 options to juggle. + +A full Simon overhaul is going to be a bit of work, but it is possible. I'd be interested to hear your thoughts on the matter. + + +## Dealing with email delivery issues +I added a workaround for those of you who had trouble getting the registration emails. Basically, people with an email account managed by Microsoft. + +![If these guys run your inbox, then who knows what other emails you're not getting](msft.gif) + +You can read [my blog post on the matter](/blog/email-spam-problems/) for all the details, but basically if you have one of those addresses, you should get those emails now. The only downside is that you might get them twice. + +## Referrals +When people link to your site, and visitors click that link, that's called a referral. The bloggers among you might be familiar with skimming through your Google Analytics reports to see who's been linking to you. + +This site does not use Google Analytics --- there's [a blog post with details on that](/blog/privacy-choices/) too --- but still captures referrals. The overview of recent referrals is available for all to see on [the status page](/status). + +Linking to freesewing.org is obviously a nice thing to do, so I keep an eye on the referrals, and if a site shows up that belongs to a user, you get the Ambassador badge. + +![Linking to freesewing.org is one way to unlock the ambassasor badge](https://posts.freesewing.org/uploads/badge_ambassador_3dd1e722cc.svg) + +It's a small way to say thank you for spreading the word about freesewing. + +## Donations +During september, we passed last year's donations amount, so it's nice to see I'll be able to [send more money to MSF](/about/pledge#donations-history) this year than in 2016. + +You can always keep track of the donations on [the donations pledge page](/about/pledge#donations-history), but here's the current status: + +![Yay! Better than last year](https://posts.freesewing.org/uploads/donations_68e214d133.svg) + +## More download formats + +I've also added additional formats to the draft download page. You now have a choice of SVG, PDF, letter-PDF, tabloid-PDF, A4-PDF, A3-PDF, A2-PDF, A1-PDF, and A0-PDF. + +## The quality control badge +I've added the quality control badge for things like reporting (or fixing) typos, broken links, grammar, and other small improvements. + +![See a typo? Let me know and you get this](https://posts.freesewing.org/uploads/badge_quality_control_6acb8c10c2.svg) + +These might not seem like an earth-shattering contribution, but they are important nevertheless. + +On the spectrum between endlessly toiling over the perfect content before publishing it, or getting it out fast warts and all, I lean heavily towards the latter. +So I kinda count on you guys to let me know when I messed up. + +## Looking ahead to october + +There are 5 patterns I am currently working on. And all of them are ready to the point where I need to make them to verify that they work as intended. First a muslin, and then the real thing. + +That's a bit of a bottleneck for me because I have a long commute, so my sewing time is typically limited to the weekends. + +The only way I see to speed up the process of getting patterns released is to have people join in with the pattern testing. I don't think it's something I can ask people to do, because this is early stage testing. Not to mention that I have nothing to offer them to sweeten the deal. What am I going to give you, a free pattern? + +Still, on the off chance that some of you want to help out by making a muslin and letting me know how it went, here's what's currently on my drawing board: + + - A trouser block for men that should be better than Theo(dore) + - A block for selvedge jeans for men + - A zip-up hoodie for men + - A wintercoat + - A unisex leggins pattern + +Should any of you want to make one of these as a test, [let me know](/contact), it would really help me out. + diff --git a/markdown/org/blog/roundup-2017-10/de.md b/markdown/org/blog/roundup-2017-10/de.md new file mode 100644 index 00000000000..5e641c1d5f7 --- /dev/null +++ b/markdown/org/blog/roundup-2017-10/de.md @@ -0,0 +1,96 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of november" +date: "2017-10-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c9242975400bf885feef0b6ddc3b2bc0ce901638-2000x1500.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - October 2017: Huey, Roy, community building and pattern cover pages [Nicht übersetzt]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at october +In retrospect, I should have made the october background image haloween themed. +I guess I'll try to remember that for next year. + +### Meet Huey + +First up: a new pattern. The Huey Hoodie is [now available](/patterns/huey) in beta. + +![Hi everyone, I am Huey](https://posts.freesewing.org/uploads/huey_b410125cba.jpg) + +Huey is a zip-up hoodie, have a look at [the Huey showcase page](/showcase/pattern/huey) for examples. +[The announcement blog post](/blog/huey-hoodie-beta/) also explains what it means for a pattern to be in beta. + +### Community building + +Freesewing is slowly evolving into a communal effort. The +[freesewing chat room](https://chat.freesewing.org/) is turning +into a rather chatty place, which is really wonderful to see. + +Furthermore, a number of people are taking a stab at designing their own patterns with +freesewing. I think that's very exciting and I'm looking forward to the day we'll all +be able to enjoy the fruits of that labour. + +Meanwhile, people are also helping out with the site, suggesting fixes and improvements +left and right, and [Wouter](/users/xdpug) even added an entire page on +[Git basics](/docs/git-basics) which should be a great stepping stone for people who like +him want to get involved, but lack prior experience with Git (and GitHub). + +Needless to say, I am very appreciative of all contributions big and small. +If you'd like to get involved, [come say hi](https://chat.freesewing.org/). + +### Cover pages for patterns + +This is something I'm +[kind of excited about](https://www.instagram.com/p/Ba6qVTFDZv_/): +but I've made +[some changes](https://github.com/freesewing/tile/commit/9d2b11e7a9f0d08b890a04eced989f0b432d2c53) +to [freesewing tile](https://github.com/freesewing/tile) to add a cover page to patterns. + +The tile repository holds software that turns your pattern into multiple pages you can +print on your printer (so called tiling, hence the name). + +You need to sticky-tape those pages together, and even though there are markings on the pages +to help you with that, it would be nice to have an overview page that shows the entire pattern +and how it's layed out over the different pages. + +Problem is, because freesewing patterns are drafted on the fly, based on your measurements, +there's no way to know how big or small your pattern will be. In addition, you can pick a variety +of paper sizes which will also influence how the pattern gets tiled. + +![Turns out, you can add a coverpage if you wrestle long enough with PostScript](https://posts.freesewing.org/uploads/tile_6dccb4de24.jpg) + +So for the longest time, I felt it was simply not possible to add an coverpage with an +overview of how everything needs to be stuck together. But everyday is a school day, and +I'm glad to announce that starting of today, when you download a tiled PDF, it will come +with a cover page detailing the layout. + +This is obviously very new code, so if for some reason you run into trouble with the tiler, +make sure to [let me know about it](https://github.com/freesewing/tile/issues/new). + +### Roy will design cover images for patterns + +I've made some changes to [the patterns page](/patterns/) because I felt that the previous +layout wasn't doing the patterns justice. + +While the layout is a bit better now (I think) the pictures are still a bit *meh* and they +don't really say *freesewing*. + +So, I've talked to Dutch illustrator [Roy Van der Hel](https://royvdhel-art.deviantart.com/) +(who also signed for our measurements illustrations) +and I'm glad to be able to share with you that he's agreed to do illustrations for the +different freesewing patterns. + +Roy will be working on these on and off, but I hope you'll start to see more of his work +here relatively soon. + +## Looking ahead to november + +Last month I said I was working on 5 patterns. One of those (Huey) has been released now +and these days I'm occupied making a test garment for another pattern on that list: a wintercoat. + +I don't want to give away too much about this yet, because it's kind of exciting, but +I hope to be able to show more of this during the month of november. If for no other +reason that it's getting cold and I could really do with a warm coat. + diff --git a/markdown/org/blog/roundup-2017-10/en.md b/markdown/org/blog/roundup-2017-10/en.md new file mode 100644 index 00000000000..3dda1deab59 --- /dev/null +++ b/markdown/org/blog/roundup-2017-10/en.md @@ -0,0 +1,96 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of november" +date: "2017-10-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c9242975400bf885feef0b6ddc3b2bc0ce901638-2000x1500.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - October 2017: Huey, Roy, community building and pattern cover pages" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at october +In retrospect, I should have made the october background image haloween themed. +I guess I'll try to remember that for next year. + +### Meet Huey + +First up: a new pattern. The Huey Hoodie is [now available](/patterns/huey) in beta. + +![Hi everyone, I am Huey](https://posts.freesewing.org/uploads/huey_b410125cba.jpg) + +Huey is a zip-up hoodie, have a look at [the Huey showcase page](/showcase/pattern/huey) for examples. +[The announcement blog post](/blog/huey-hoodie-beta/) also explains what it means for a pattern to be in beta. + +### Community building + +Freesewing is slowly evolving into a communal effort. The +[freesewing chat room](https://chat.freesewing.org/) is turning +into a rather chatty place, which is really wonderful to see. + +Furthermore, a number of people are taking a stab at designing their own patterns with +freesewing. I think that's very exciting and I'm looking forward to the day we'll all +be able to enjoy the fruits of that labour. + +Meanwhile, people are also helping out with the site, suggesting fixes and improvements +left and right, and [Wouter](/users/xdpug) even added an entire page on +[Git basics](/docs/git-basics) which should be a great stepping stone for people who like +him want to get involved, but lack prior experience with Git (and GitHub). + +Needless to say, I am very appreciative of all contributions big and small. +If you'd like to get involved, [come say hi](https://chat.freesewing.org/). + +### Cover pages for patterns + +This is something I'm +[kind of excited about](https://www.instagram.com/p/Ba6qVTFDZv_/): +but I've made +[some changes](https://github.com/freesewing/tile/commit/9d2b11e7a9f0d08b890a04eced989f0b432d2c53) +to [freesewing tile](https://github.com/freesewing/tile) to add a cover page to patterns. + +The tile repository holds software that turns your pattern into multiple pages you can +print on your printer (so called tiling, hence the name). + +You need to sticky-tape those pages together, and even though there are markings on the pages +to help you with that, it would be nice to have an overview page that shows the entire pattern +and how it's layed out over the different pages. + +Problem is, because freesewing patterns are drafted on the fly, based on your measurements, +there's no way to know how big or small your pattern will be. In addition, you can pick a variety +of paper sizes which will also influence how the pattern gets tiled. + +![Turns out, you can add a coverpage if you wrestle long enough with PostScript](https://posts.freesewing.org/uploads/tile_6dccb4de24.jpg) + +So for the longest time, I felt it was simply not possible to add an coverpage with an +overview of how everything needs to be stuck together. But everyday is a school day, and +I'm glad to announce that starting of today, when you download a tiled PDF, it will come +with a cover page detailing the layout. + +This is obviously very new code, so if for some reason you run into trouble with the tiler, +make sure to [let me know about it](https://github.com/freesewing/tile/issues/new). + +### Roy will design cover images for patterns + +I've made some changes to [the patterns page](/patterns/) because I felt that the previous +layout wasn't doing the patterns justice. + +While the layout is a bit better now (I think) the pictures are still a bit *meh* and they +don't really say *freesewing*. + +So, I've talked to Dutch illustrator [Roy Van der Hel](https://royvdhel-art.deviantart.com/) +(who also signed for our measurements illustrations) +and I'm glad to be able to share with you that he's agreed to do illustrations for the +different freesewing patterns. + +Roy will be working on these on and off, but I hope you'll start to see more of his work +here relatively soon. + +## Looking ahead to november + +Last month I said I was working on 5 patterns. One of those (Huey) has been released now +and these days I'm occupied making a test garment for another pattern on that list: a wintercoat. + +I don't want to give away too much about this yet, because it's kind of exciting, but +I hope to be able to show more of this during the month of november. If for no other +reason that it's getting cold and I could really do with a warm coat. + diff --git a/markdown/org/blog/roundup-2017-10/es.md b/markdown/org/blog/roundup-2017-10/es.md new file mode 100644 index 00000000000..8adeadd6752 --- /dev/null +++ b/markdown/org/blog/roundup-2017-10/es.md @@ -0,0 +1,96 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of november" +date: "2017-10-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c9242975400bf885feef0b6ddc3b2bc0ce901638-2000x1500.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - October 2017: Huey, Roy, community building and pattern cover pages [No traducido]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at october +In retrospect, I should have made the october background image haloween themed. +I guess I'll try to remember that for next year. + +### Meet Huey + +First up: a new pattern. The Huey Hoodie is [now available](/patterns/huey) in beta. + +![Hi everyone, I am Huey](https://posts.freesewing.org/uploads/huey_b410125cba.jpg) + +Huey is a zip-up hoodie, have a look at [the Huey showcase page](/showcase/pattern/huey) for examples. +[The announcement blog post](/blog/huey-hoodie-beta/) also explains what it means for a pattern to be in beta. + +### Community building + +Freesewing is slowly evolving into a communal effort. The +[freesewing chat room](https://chat.freesewing.org/) is turning +into a rather chatty place, which is really wonderful to see. + +Furthermore, a number of people are taking a stab at designing their own patterns with +freesewing. I think that's very exciting and I'm looking forward to the day we'll all +be able to enjoy the fruits of that labour. + +Meanwhile, people are also helping out with the site, suggesting fixes and improvements +left and right, and [Wouter](/users/xdpug) even added an entire page on +[Git basics](/docs/git-basics) which should be a great stepping stone for people who like +him want to get involved, but lack prior experience with Git (and GitHub). + +Needless to say, I am very appreciative of all contributions big and small. +If you'd like to get involved, [come say hi](https://chat.freesewing.org/). + +### Cover pages for patterns + +This is something I'm +[kind of excited about](https://www.instagram.com/p/Ba6qVTFDZv_/): +but I've made +[some changes](https://github.com/freesewing/tile/commit/9d2b11e7a9f0d08b890a04eced989f0b432d2c53) +to [freesewing tile](https://github.com/freesewing/tile) to add a cover page to patterns. + +The tile repository holds software that turns your pattern into multiple pages you can +print on your printer (so called tiling, hence the name). + +You need to sticky-tape those pages together, and even though there are markings on the pages +to help you with that, it would be nice to have an overview page that shows the entire pattern +and how it's layed out over the different pages. + +Problem is, because freesewing patterns are drafted on the fly, based on your measurements, +there's no way to know how big or small your pattern will be. In addition, you can pick a variety +of paper sizes which will also influence how the pattern gets tiled. + +![Turns out, you can add a coverpage if you wrestle long enough with PostScript](https://posts.freesewing.org/uploads/tile_6dccb4de24.jpg) + +So for the longest time, I felt it was simply not possible to add an coverpage with an +overview of how everything needs to be stuck together. But everyday is a school day, and +I'm glad to announce that starting of today, when you download a tiled PDF, it will come +with a cover page detailing the layout. + +This is obviously very new code, so if for some reason you run into trouble with the tiler, +make sure to [let me know about it](https://github.com/freesewing/tile/issues/new). + +### Roy will design cover images for patterns + +I've made some changes to [the patterns page](/patterns/) because I felt that the previous +layout wasn't doing the patterns justice. + +While the layout is a bit better now (I think) the pictures are still a bit *meh* and they +don't really say *freesewing*. + +So, I've talked to Dutch illustrator [Roy Van der Hel](https://royvdhel-art.deviantart.com/) +(who also signed for our measurements illustrations) +and I'm glad to be able to share with you that he's agreed to do illustrations for the +different freesewing patterns. + +Roy will be working on these on and off, but I hope you'll start to see more of his work +here relatively soon. + +## Looking ahead to november + +Last month I said I was working on 5 patterns. One of those (Huey) has been released now +and these days I'm occupied making a test garment for another pattern on that list: a wintercoat. + +I don't want to give away too much about this yet, because it's kind of exciting, but +I hope to be able to show more of this during the month of november. If for no other +reason that it's getting cold and I could really do with a warm coat. + diff --git a/markdown/org/blog/roundup-2017-10/fr.md b/markdown/org/blog/roundup-2017-10/fr.md new file mode 100644 index 00000000000..77414b64945 --- /dev/null +++ b/markdown/org/blog/roundup-2017-10/fr.md @@ -0,0 +1,96 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of november" +date: "2017-10-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c9242975400bf885feef0b6ddc3b2bc0ce901638-2000x1500.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - October 2017: Huey, Roy, community building and pattern cover pages [Non traduit]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at october +In retrospect, I should have made the october background image haloween themed. +I guess I'll try to remember that for next year. + +### Meet Huey + +First up: a new pattern. The Huey Hoodie is [now available](/patterns/huey) in beta. + +![Hi everyone, I am Huey](https://posts.freesewing.org/uploads/huey_b410125cba.jpg) + +Huey is a zip-up hoodie, have a look at [the Huey showcase page](/showcase/pattern/huey) for examples. +[The announcement blog post](/blog/huey-hoodie-beta/) also explains what it means for a pattern to be in beta. + +### Community building + +Freesewing is slowly evolving into a communal effort. The +[freesewing chat room](https://chat.freesewing.org/) is turning +into a rather chatty place, which is really wonderful to see. + +Furthermore, a number of people are taking a stab at designing their own patterns with +freesewing. I think that's very exciting and I'm looking forward to the day we'll all +be able to enjoy the fruits of that labour. + +Meanwhile, people are also helping out with the site, suggesting fixes and improvements +left and right, and [Wouter](/users/xdpug) even added an entire page on +[Git basics](/docs/git-basics) which should be a great stepping stone for people who like +him want to get involved, but lack prior experience with Git (and GitHub). + +Needless to say, I am very appreciative of all contributions big and small. +If you'd like to get involved, [come say hi](https://chat.freesewing.org/). + +### Cover pages for patterns + +This is something I'm +[kind of excited about](https://www.instagram.com/p/Ba6qVTFDZv_/): +but I've made +[some changes](https://github.com/freesewing/tile/commit/9d2b11e7a9f0d08b890a04eced989f0b432d2c53) +to [freesewing tile](https://github.com/freesewing/tile) to add a cover page to patterns. + +The tile repository holds software that turns your pattern into multiple pages you can +print on your printer (so called tiling, hence the name). + +You need to sticky-tape those pages together, and even though there are markings on the pages +to help you with that, it would be nice to have an overview page that shows the entire pattern +and how it's layed out over the different pages. + +Problem is, because freesewing patterns are drafted on the fly, based on your measurements, +there's no way to know how big or small your pattern will be. In addition, you can pick a variety +of paper sizes which will also influence how the pattern gets tiled. + +![Turns out, you can add a coverpage if you wrestle long enough with PostScript](https://posts.freesewing.org/uploads/tile_6dccb4de24.jpg) + +So for the longest time, I felt it was simply not possible to add an coverpage with an +overview of how everything needs to be stuck together. But everyday is a school day, and +I'm glad to announce that starting of today, when you download a tiled PDF, it will come +with a cover page detailing the layout. + +This is obviously very new code, so if for some reason you run into trouble with the tiler, +make sure to [let me know about it](https://github.com/freesewing/tile/issues/new). + +### Roy will design cover images for patterns + +I've made some changes to [the patterns page](/patterns/) because I felt that the previous +layout wasn't doing the patterns justice. + +While the layout is a bit better now (I think) the pictures are still a bit *meh* and they +don't really say *freesewing*. + +So, I've talked to Dutch illustrator [Roy Van der Hel](https://royvdhel-art.deviantart.com/) +(who also signed for our measurements illustrations) +and I'm glad to be able to share with you that he's agreed to do illustrations for the +different freesewing patterns. + +Roy will be working on these on and off, but I hope you'll start to see more of his work +here relatively soon. + +## Looking ahead to november + +Last month I said I was working on 5 patterns. One of those (Huey) has been released now +and these days I'm occupied making a test garment for another pattern on that list: a wintercoat. + +I don't want to give away too much about this yet, because it's kind of exciting, but +I hope to be able to show more of this during the month of november. If for no other +reason that it's getting cold and I could really do with a warm coat. + diff --git a/markdown/org/blog/roundup-2017-10/nl.md b/markdown/org/blog/roundup-2017-10/nl.md new file mode 100644 index 00000000000..95a789d3470 --- /dev/null +++ b/markdown/org/blog/roundup-2017-10/nl.md @@ -0,0 +1,96 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of november" +date: "2017-10-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c9242975400bf885feef0b6ddc3b2bc0ce901638-2000x1500.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - October 2017: Huey, Roy, community building and pattern cover pages [Niet vertaald]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at october +In retrospect, I should have made the october background image haloween themed. +I guess I'll try to remember that for next year. + +### Meet Huey + +First up: a new pattern. The Huey Hoodie is [now available](/patterns/huey) in beta. + +![Hi everyone, I am Huey](https://posts.freesewing.org/uploads/huey_b410125cba.jpg) + +Huey is a zip-up hoodie, have a look at [the Huey showcase page](/showcase/pattern/huey) for examples. +[The announcement blog post](/blog/huey-hoodie-beta/) also explains what it means for a pattern to be in beta. + +### Community building + +Freesewing is slowly evolving into a communal effort. The +[freesewing chat room](https://chat.freesewing.org/) is turning +into a rather chatty place, which is really wonderful to see. + +Furthermore, a number of people are taking a stab at designing their own patterns with +freesewing. I think that's very exciting and I'm looking forward to the day we'll all +be able to enjoy the fruits of that labour. + +Meanwhile, people are also helping out with the site, suggesting fixes and improvements +left and right, and [Wouter](/users/xdpug) even added an entire page on +[Git basics](/docs/git-basics) which should be a great stepping stone for people who like +him want to get involved, but lack prior experience with Git (and GitHub). + +Needless to say, I am very appreciative of all contributions big and small. +If you'd like to get involved, [come say hi](https://chat.freesewing.org/). + +### Cover pages for patterns + +This is something I'm +[kind of excited about](https://www.instagram.com/p/Ba6qVTFDZv_/): +but I've made +[some changes](https://github.com/freesewing/tile/commit/9d2b11e7a9f0d08b890a04eced989f0b432d2c53) +to [freesewing tile](https://github.com/freesewing/tile) to add a cover page to patterns. + +The tile repository holds software that turns your pattern into multiple pages you can +print on your printer (so called tiling, hence the name). + +You need to sticky-tape those pages together, and even though there are markings on the pages +to help you with that, it would be nice to have an overview page that shows the entire pattern +and how it's layed out over the different pages. + +Problem is, because freesewing patterns are drafted on the fly, based on your measurements, +there's no way to know how big or small your pattern will be. In addition, you can pick a variety +of paper sizes which will also influence how the pattern gets tiled. + +![Turns out, you can add a coverpage if you wrestle long enough with PostScript](https://posts.freesewing.org/uploads/tile_6dccb4de24.jpg) + +So for the longest time, I felt it was simply not possible to add an coverpage with an +overview of how everything needs to be stuck together. But everyday is a school day, and +I'm glad to announce that starting of today, when you download a tiled PDF, it will come +with a cover page detailing the layout. + +This is obviously very new code, so if for some reason you run into trouble with the tiler, +make sure to [let me know about it](https://github.com/freesewing/tile/issues/new). + +### Roy will design cover images for patterns + +I've made some changes to [the patterns page](/patterns/) because I felt that the previous +layout wasn't doing the patterns justice. + +While the layout is a bit better now (I think) the pictures are still a bit *meh* and they +don't really say *freesewing*. + +So, I've talked to Dutch illustrator [Roy Van der Hel](https://royvdhel-art.deviantart.com/) +(who also signed for our measurements illustrations) +and I'm glad to be able to share with you that he's agreed to do illustrations for the +different freesewing patterns. + +Roy will be working on these on and off, but I hope you'll start to see more of his work +here relatively soon. + +## Looking ahead to november + +Last month I said I was working on 5 patterns. One of those (Huey) has been released now +and these days I'm occupied making a test garment for another pattern on that list: a wintercoat. + +I don't want to give away too much about this yet, because it's kind of exciting, but +I hope to be able to show more of this during the month of november. If for no other +reason that it's getting cold and I could really do with a warm coat. + diff --git a/markdown/org/blog/roundup-2017-11/de.md b/markdown/org/blog/roundup-2017-11/de.md new file mode 100644 index 00000000000..db5a7f46c86 --- /dev/null +++ b/markdown/org/blog/roundup-2017-11/de.md @@ -0,0 +1,164 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of December" +date: "2017-11-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c9c5c5e10d2ed6e9f2935b047afa76c1ddd7c834-2000x1333.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - November 2017: Benjamin, on-boarding, showcases, and our on-demand tiler [Nicht übersetzt]" +--- + + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at November +November has been busy around here. While lot of the work has been happening behind the scenes +-- more on that in December -- there's also a list of things that are already rolled out. + +Here's the most important changes: + +### Meet Benjamin +![Wouter showing off Benjamin](https://posts.freesewing.org/uploads/benjamin_fc9844f4bd.jpg) +First up: a new pattern. The Benjamin Bow tie is [now available](/patterns/benjamin) in beta. + +![More bow ties from Wouter's personal stash](https://posts.freesewing.org/uploads/bowties_4f3e05ec53.jpg) + +Benjamin is a bow tie, and as I explained in [the announcement blog post](/en/blog/benjamin-bow-tie-beta/) +this release is kind of a big deal. + +That's because it's the first ever pattern to have been contributed by the community. +More specifically, it was [Wouter](/users/xdpug) who designed and programmed the pattern. + +So shout-out to him for being the first person to contribute a pattern. And if you +[hang around in the freesewing chat room](https://discord.freesewing.org/), +you know that he's already started working on his next pattern. + + +### Better user on-boarding + +I've changed the sign-up flow a bit to help people discover all the options they can set in their account. + +![The welcome page guides you through your account setup](https://posts.freesewing.org/uploads/welcome_e02a39ca3b.png) + +The change is two-fold. First you are now auto-magically logged in +when you click the email confirmation link for your account. + +Second, we send you to the welcome page and guide you +through a few steps to finalize your account setup. Specifically: + + - Configure your units + - Configure your username + - Configure your profile picture + - Configure your social media accounts + +(More on that last one later in this post) + +All of these settings are available in [your account](/account), but people +frequently don't realize that. +With the new sign-up flow, that should no longer be the case. + +> ##### Hey, I never got a handy welcome page like that +> At any time, you can go to [the welcome page](/welcome) +> to check or update your account settings. + +### Mixed units warning + +One of the issues that drove the changes to the on-boarding of new users was the +issue of mixed units. + +Mixed units is when your account is configured in metric, but your model is set +to imperial (or vice-versa). + +![An example warning when units are mixed between your account and your model](https://posts.freesewing.org/uploads/units_mismatch_warning_058d7de9b4.png) + +This is supported. If you make things for other people in other parts of the world, +this flexibility is handy. + +But it's a rather niche scenario, and more often than not it's due to the user not +realizing their units are set as they are. + +So now, when you draft a pattern with mixed units, we'll show you a warning box to make +sure that you do actually intend to use mixed units. + +### Per-pattern default seam allowance +The roll-out of Benjamin raised another issue: standard seam allowance. + +For a bow tie, the current standard seam allowance (1cm for metric, 5/8" for imperial) +is too large. So Wouter wanted some way to change the standard seam allowance. + +![Here too, we've added a little notification to make sure you are aware](https://posts.freesewing.org/uploads/non_standard_sa_warning_e5046e98a7.png) + +So, that's what we implemented. Going forward, patterns can set the standard seam allowance +(for both metric and imperial). If they don't, we revert to 1cm|5/8" as before. + +Note that this is only the default seam allowance. When you draft a pattern you can still +set the seam allowance to whatever you like. + +### Social media accounts + +If you clicked the link to the welcome page, or if you check out the +settings in [your profile](/profile) you'll see that you can now enter your +username for a few other sites: + + - Twitter + - Instagram + - GitHub + +No need to worry, [your privacy is in good hands here](/blog/privacy-choices/). +I am not interested in collecting your data, and the only reason +this is here is because people [asked for it](https://github.com/freesewing/site/issues/184). + +![After Quentin added his Instagram and GitHub accounts to his settings, his comment now have links to those accounts])comments-social.png) + +Links to your social media accounts will appear on your profile page and along your comments. + +### More showcases + +We've added a bunch of new [showcases](/showcase) this month. +Every maker that has one or more showcases here on the site has their own page +that lists all their showcases. + +![An example of links on a maker page. In this case, Anneke](https://posts.freesewing.org/uploads/maker_links_8504a1b00d.png) + +This month, we've updated those pages with links to the blog and/or social media +accounts of these makers. +The idea is that people who feel you've made a cool thing can find out a bit more about you. + +### Referrer policy, or why you never get any visitors from freesewing.org + +We've rolled out the strictest referral policy: `no-referrer`. It blocks all referrer information. + +This means that if you run Google analytics -- or some other website statistics tool -- +on your blog or website, you won't see traffic from freesewing.org. + +![Our referrer policy: No](https://posts.freesewing.org/uploads/no_13049a23c3.gif) + +That doesn't mean that people aren't clicking links to your blog, but we simply +block the referrer header from being set, so Google has no idea where people come from. + +Why you ask? Because privacy. + +### On-demand tiler +When you draft a pattern here, you can download it in a number of formats, all neatly tiled +so you can print them. + +You can also download the SVG source code to make further changes to the patterns. +But once you have made those changes, there's no easy way for you to get it as a printable PDF. + +![The on-demand tiler does what you'd expect](tiler.svg) + +Well now there is. We've added [an on-demand tiler](/tools/tiler) to the site that does just that. +Upload your SVG, pick the format of your choice, and we'll tile it for you. + +## Looking ahead to December + +I had hoped to release my winter coat pattern during November, but alas that didn't work out. +I'm actually still making it, and when it's ready there will be a few tweaks required to the pattern +before I can release it. + +But that news will have to play second fiddle to our wrap up of the year +(traditionally on December 10th here). It's not just about what happened over the last 12 months, +we'll also be rolling out some changes to safeguard the future of this project. + +10 more sleeps :) + + diff --git a/markdown/org/blog/roundup-2017-11/en.md b/markdown/org/blog/roundup-2017-11/en.md new file mode 100644 index 00000000000..1f4dbe186e0 --- /dev/null +++ b/markdown/org/blog/roundup-2017-11/en.md @@ -0,0 +1,164 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of December" +date: "2017-11-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c9c5c5e10d2ed6e9f2935b047afa76c1ddd7c834-2000x1333.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - November 2017: Benjamin, on-boarding, showcases, and our on-demand tiler" +--- + + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at November +November has been busy around here. While lot of the work has been happening behind the scenes +-- more on that in December -- there's also a list of things that are already rolled out. + +Here's the most important changes: + +### Meet Benjamin +![Wouter showing off Benjamin](https://posts.freesewing.org/uploads/benjamin_fc9844f4bd.jpg) +First up: a new pattern. The Benjamin Bow tie is [now available](/patterns/benjamin) in beta. + +![More bow ties from Wouter's personal stash](https://posts.freesewing.org/uploads/bowties_4f3e05ec53.jpg) + +Benjamin is a bow tie, and as I explained in [the announcement blog post](/en/blog/benjamin-bow-tie-beta/) +this release is kind of a big deal. + +That's because it's the first ever pattern to have been contributed by the community. +More specifically, it was [Wouter](/users/xdpug) who designed and programmed the pattern. + +So shout-out to him for being the first person to contribute a pattern. And if you +[hang around in the freesewing chat room](https://discord.freesewing.org/), +you know that he's already started working on his next pattern. + + +### Better user on-boarding + +I've changed the sign-up flow a bit to help people discover all the options they can set in their account. + +![The welcome page guides you through your account setup](https://posts.freesewing.org/uploads/welcome_e02a39ca3b.png) + +The change is two-fold. First you are now auto-magically logged in +when you click the email confirmation link for your account. + +Second, we send you to the welcome page and guide you +through a few steps to finalize your account setup. Specifically: + + - Configure your units + - Configure your username + - Configure your profile picture + - Configure your social media accounts + +(More on that last one later in this post) + +All of these settings are available in [your account](/account), but people +frequently don't realize that. +With the new sign-up flow, that should no longer be the case. + +> ##### Hey, I never got a handy welcome page like that +> At any time, you can go to [the welcome page](/welcome) +> to check or update your account settings. + +### Mixed units warning + +One of the issues that drove the changes to the on-boarding of new users was the +issue of mixed units. + +Mixed units is when your account is configured in metric, but your model is set +to imperial (or vice-versa). + +![An example warning when units are mixed between your account and your model](https://posts.freesewing.org/uploads/units_mismatch_warning_058d7de9b4.png) + +This is supported. If you make things for other people in other parts of the world, +this flexibility is handy. + +But it's a rather niche scenario, and more often than not it's due to the user not +realizing their units are set as they are. + +So now, when you draft a pattern with mixed units, we'll show you a warning box to make +sure that you do actually intend to use mixed units. + +### Per-pattern default seam allowance +The roll-out of Benjamin raised another issue: standard seam allowance. + +For a bow tie, the current standard seam allowance (1cm for metric, 5/8" for imperial) +is too large. So Wouter wanted some way to change the standard seam allowance. + +![Here too, we've added a little notification to make sure you are aware](https://posts.freesewing.org/uploads/non_standard_sa_warning_e5046e98a7.png) + +So, that's what we implemented. Going forward, patterns can set the standard seam allowance +(for both metric and imperial). If they don't, we revert to 1cm|5/8" as before. + +Note that this is only the default seam allowance. When you draft a pattern you can still +set the seam allowance to whatever you like. + +### Social media accounts + +If you clicked the link to the welcome page, or if you check out the +settings in [your profile](/profile) you'll see that you can now enter your +username for a few other sites: + + - Twitter + - Instagram + - GitHub + +No need to worry, [your privacy is in good hands here](/blog/privacy-choices/). +I am not interested in collecting your data, and the only reason +this is here is because people [asked for it](https://github.com/freesewing/site/issues/184). + +![After Quentin added his Instagram and GitHub accounts to his settings, his comment now have links to those accounts])comments-social.png) + +Links to your social media accounts will appear on your profile page and along your comments. + +### More showcases + +We've added a bunch of new [showcases](/showcase) this month. +Every maker that has one or more showcases here on the site has their own page +that lists all their showcases. + +![An example of links on a maker page. In this case, Anneke](https://posts.freesewing.org/uploads/maker_links_8504a1b00d.png) + +This month, we've updated those pages with links to the blog and/or social media +accounts of these makers. +The idea is that people who feel you've made a cool thing can find out a bit more about you. + +### Referrer policy, or why you never get any visitors from freesewing.org + +We've rolled out the strictest referral policy: `no-referrer`. It blocks all referrer information. + +This means that if you run Google analytics -- or some other website statistics tool -- +on your blog or website, you won't see traffic from freesewing.org. + +![Our referrer policy: No](https://posts.freesewing.org/uploads/no_13049a23c3.gif) + +That doesn't mean that people aren't clicking links to your blog, but we simply +block the referrer header from being set, so Google has no idea where people come from. + +Why you ask? Because privacy. + +### On-demand tiler +When you draft a pattern here, you can download it in a number of formats, all neatly tiled +so you can print them. + +You can also download the SVG source code to make further changes to the patterns. +But once you have made those changes, there's no easy way for you to get it as a printable PDF. + +![The on-demand tiler does what you'd expect](tiler.svg) + +Well now there is. We've added [an on-demand tiler](/tools/tiler) to the site that does just that. +Upload your SVG, pick the format of your choice, and we'll tile it for you. + +## Looking ahead to December + +I had hoped to release my winter coat pattern during November, but alas that didn't work out. +I'm actually still making it, and when it's ready there will be a few tweaks required to the pattern +before I can release it. + +But that news will have to play second fiddle to our wrap up of the year +(traditionally on December 10th here). It's not just about what happened over the last 12 months, +we'll also be rolling out some changes to safeguard the future of this project. + +10 more sleeps :) + + diff --git a/markdown/org/blog/roundup-2017-11/es.md b/markdown/org/blog/roundup-2017-11/es.md new file mode 100644 index 00000000000..b09d6fe2f50 --- /dev/null +++ b/markdown/org/blog/roundup-2017-11/es.md @@ -0,0 +1,164 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of December" +date: "2017-11-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c9c5c5e10d2ed6e9f2935b047afa76c1ddd7c834-2000x1333.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - November 2017: Benjamin, on-boarding, showcases, and our on-demand tiler [No traducido]" +--- + + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at November +November has been busy around here. While lot of the work has been happening behind the scenes +-- more on that in December -- there's also a list of things that are already rolled out. + +Here's the most important changes: + +### Meet Benjamin +![Wouter showing off Benjamin](https://posts.freesewing.org/uploads/benjamin_fc9844f4bd.jpg) +First up: a new pattern. The Benjamin Bow tie is [now available](/patterns/benjamin) in beta. + +![More bow ties from Wouter's personal stash](https://posts.freesewing.org/uploads/bowties_4f3e05ec53.jpg) + +Benjamin is a bow tie, and as I explained in [the announcement blog post](/en/blog/benjamin-bow-tie-beta/) +this release is kind of a big deal. + +That's because it's the first ever pattern to have been contributed by the community. +More specifically, it was [Wouter](/users/xdpug) who designed and programmed the pattern. + +So shout-out to him for being the first person to contribute a pattern. And if you +[hang around in the freesewing chat room](https://discord.freesewing.org/), +you know that he's already started working on his next pattern. + + +### Better user on-boarding + +I've changed the sign-up flow a bit to help people discover all the options they can set in their account. + +![The welcome page guides you through your account setup](https://posts.freesewing.org/uploads/welcome_e02a39ca3b.png) + +The change is two-fold. First you are now auto-magically logged in +when you click the email confirmation link for your account. + +Second, we send you to the welcome page and guide you +through a few steps to finalize your account setup. Specifically: + + - Configure your units + - Configure your username + - Configure your profile picture + - Configure your social media accounts + +(More on that last one later in this post) + +All of these settings are available in [your account](/account), but people +frequently don't realize that. +With the new sign-up flow, that should no longer be the case. + +> ##### Hey, I never got a handy welcome page like that +> At any time, you can go to [the welcome page](/welcome) +> to check or update your account settings. + +### Mixed units warning + +One of the issues that drove the changes to the on-boarding of new users was the +issue of mixed units. + +Mixed units is when your account is configured in metric, but your model is set +to imperial (or vice-versa). + +![An example warning when units are mixed between your account and your model](https://posts.freesewing.org/uploads/units_mismatch_warning_058d7de9b4.png) + +This is supported. If you make things for other people in other parts of the world, +this flexibility is handy. + +But it's a rather niche scenario, and more often than not it's due to the user not +realizing their units are set as they are. + +So now, when you draft a pattern with mixed units, we'll show you a warning box to make +sure that you do actually intend to use mixed units. + +### Per-pattern default seam allowance +The roll-out of Benjamin raised another issue: standard seam allowance. + +For a bow tie, the current standard seam allowance (1cm for metric, 5/8" for imperial) +is too large. So Wouter wanted some way to change the standard seam allowance. + +![Here too, we've added a little notification to make sure you are aware](https://posts.freesewing.org/uploads/non_standard_sa_warning_e5046e98a7.png) + +So, that's what we implemented. Going forward, patterns can set the standard seam allowance +(for both metric and imperial). If they don't, we revert to 1cm|5/8" as before. + +Note that this is only the default seam allowance. When you draft a pattern you can still +set the seam allowance to whatever you like. + +### Social media accounts + +If you clicked the link to the welcome page, or if you check out the +settings in [your profile](/profile) you'll see that you can now enter your +username for a few other sites: + + - Twitter + - Instagram + - GitHub + +No need to worry, [your privacy is in good hands here](/blog/privacy-choices/). +I am not interested in collecting your data, and the only reason +this is here is because people [asked for it](https://github.com/freesewing/site/issues/184). + +![After Quentin added his Instagram and GitHub accounts to his settings, his comment now have links to those accounts])comments-social.png) + +Links to your social media accounts will appear on your profile page and along your comments. + +### More showcases + +We've added a bunch of new [showcases](/showcase) this month. +Every maker that has one or more showcases here on the site has their own page +that lists all their showcases. + +![An example of links on a maker page. In this case, Anneke](https://posts.freesewing.org/uploads/maker_links_8504a1b00d.png) + +This month, we've updated those pages with links to the blog and/or social media +accounts of these makers. +The idea is that people who feel you've made a cool thing can find out a bit more about you. + +### Referrer policy, or why you never get any visitors from freesewing.org + +We've rolled out the strictest referral policy: `no-referrer`. It blocks all referrer information. + +This means that if you run Google analytics -- or some other website statistics tool -- +on your blog or website, you won't see traffic from freesewing.org. + +![Our referrer policy: No](https://posts.freesewing.org/uploads/no_13049a23c3.gif) + +That doesn't mean that people aren't clicking links to your blog, but we simply +block the referrer header from being set, so Google has no idea where people come from. + +Why you ask? Because privacy. + +### On-demand tiler +When you draft a pattern here, you can download it in a number of formats, all neatly tiled +so you can print them. + +You can also download the SVG source code to make further changes to the patterns. +But once you have made those changes, there's no easy way for you to get it as a printable PDF. + +![The on-demand tiler does what you'd expect](tiler.svg) + +Well now there is. We've added [an on-demand tiler](/tools/tiler) to the site that does just that. +Upload your SVG, pick the format of your choice, and we'll tile it for you. + +## Looking ahead to December + +I had hoped to release my winter coat pattern during November, but alas that didn't work out. +I'm actually still making it, and when it's ready there will be a few tweaks required to the pattern +before I can release it. + +But that news will have to play second fiddle to our wrap up of the year +(traditionally on December 10th here). It's not just about what happened over the last 12 months, +we'll also be rolling out some changes to safeguard the future of this project. + +10 more sleeps :) + + diff --git a/markdown/org/blog/roundup-2017-11/fr.md b/markdown/org/blog/roundup-2017-11/fr.md new file mode 100644 index 00000000000..4076fd23793 --- /dev/null +++ b/markdown/org/blog/roundup-2017-11/fr.md @@ -0,0 +1,164 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of December" +date: "2017-11-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c9c5c5e10d2ed6e9f2935b047afa76c1ddd7c834-2000x1333.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - November 2017: Benjamin, on-boarding, showcases, and our on-demand tiler [Non traduit]" +--- + + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at November +November has been busy around here. While lot of the work has been happening behind the scenes +-- more on that in December -- there's also a list of things that are already rolled out. + +Here's the most important changes: + +### Meet Benjamin +![Wouter showing off Benjamin](https://posts.freesewing.org/uploads/benjamin_fc9844f4bd.jpg) +First up: a new pattern. The Benjamin Bow tie is [now available](/patterns/benjamin) in beta. + +![More bow ties from Wouter's personal stash](https://posts.freesewing.org/uploads/bowties_4f3e05ec53.jpg) + +Benjamin is a bow tie, and as I explained in [the announcement blog post](/en/blog/benjamin-bow-tie-beta/) +this release is kind of a big deal. + +That's because it's the first ever pattern to have been contributed by the community. +More specifically, it was [Wouter](/users/xdpug) who designed and programmed the pattern. + +So shout-out to him for being the first person to contribute a pattern. And if you +[hang around in the freesewing chat room](https://discord.freesewing.org/), +you know that he's already started working on his next pattern. + + +### Better user on-boarding + +I've changed the sign-up flow a bit to help people discover all the options they can set in their account. + +![The welcome page guides you through your account setup](https://posts.freesewing.org/uploads/welcome_e02a39ca3b.png) + +The change is two-fold. First you are now auto-magically logged in +when you click the email confirmation link for your account. + +Second, we send you to the welcome page and guide you +through a few steps to finalize your account setup. Specifically: + + - Configure your units + - Configure your username + - Configure your profile picture + - Configure your social media accounts + +(More on that last one later in this post) + +All of these settings are available in [your account](/account), but people +frequently don't realize that. +With the new sign-up flow, that should no longer be the case. + +> ##### Hey, I never got a handy welcome page like that +> At any time, you can go to [the welcome page](/welcome) +> to check or update your account settings. + +### Mixed units warning + +One of the issues that drove the changes to the on-boarding of new users was the +issue of mixed units. + +Mixed units is when your account is configured in metric, but your model is set +to imperial (or vice-versa). + +![An example warning when units are mixed between your account and your model](https://posts.freesewing.org/uploads/units_mismatch_warning_058d7de9b4.png) + +This is supported. If you make things for other people in other parts of the world, +this flexibility is handy. + +But it's a rather niche scenario, and more often than not it's due to the user not +realizing their units are set as they are. + +So now, when you draft a pattern with mixed units, we'll show you a warning box to make +sure that you do actually intend to use mixed units. + +### Per-pattern default seam allowance +The roll-out of Benjamin raised another issue: standard seam allowance. + +For a bow tie, the current standard seam allowance (1cm for metric, 5/8" for imperial) +is too large. So Wouter wanted some way to change the standard seam allowance. + +![Here too, we've added a little notification to make sure you are aware](https://posts.freesewing.org/uploads/non_standard_sa_warning_e5046e98a7.png) + +So, that's what we implemented. Going forward, patterns can set the standard seam allowance +(for both metric and imperial). If they don't, we revert to 1cm|5/8" as before. + +Note that this is only the default seam allowance. When you draft a pattern you can still +set the seam allowance to whatever you like. + +### Social media accounts + +If you clicked the link to the welcome page, or if you check out the +settings in [your profile](/profile) you'll see that you can now enter your +username for a few other sites: + + - Twitter + - Instagram + - GitHub + +No need to worry, [your privacy is in good hands here](/blog/privacy-choices/). +I am not interested in collecting your data, and the only reason +this is here is because people [asked for it](https://github.com/freesewing/site/issues/184). + +![After Quentin added his Instagram and GitHub accounts to his settings, his comment now have links to those accounts])comments-social.png) + +Links to your social media accounts will appear on your profile page and along your comments. + +### More showcases + +We've added a bunch of new [showcases](/showcase) this month. +Every maker that has one or more showcases here on the site has their own page +that lists all their showcases. + +![An example of links on a maker page. In this case, Anneke](https://posts.freesewing.org/uploads/maker_links_8504a1b00d.png) + +This month, we've updated those pages with links to the blog and/or social media +accounts of these makers. +The idea is that people who feel you've made a cool thing can find out a bit more about you. + +### Referrer policy, or why you never get any visitors from freesewing.org + +We've rolled out the strictest referral policy: `no-referrer`. It blocks all referrer information. + +This means that if you run Google analytics -- or some other website statistics tool -- +on your blog or website, you won't see traffic from freesewing.org. + +![Our referrer policy: No](https://posts.freesewing.org/uploads/no_13049a23c3.gif) + +That doesn't mean that people aren't clicking links to your blog, but we simply +block the referrer header from being set, so Google has no idea where people come from. + +Why you ask? Because privacy. + +### On-demand tiler +When you draft a pattern here, you can download it in a number of formats, all neatly tiled +so you can print them. + +You can also download the SVG source code to make further changes to the patterns. +But once you have made those changes, there's no easy way for you to get it as a printable PDF. + +![The on-demand tiler does what you'd expect](tiler.svg) + +Well now there is. We've added [an on-demand tiler](/tools/tiler) to the site that does just that. +Upload your SVG, pick the format of your choice, and we'll tile it for you. + +## Looking ahead to December + +I had hoped to release my winter coat pattern during November, but alas that didn't work out. +I'm actually still making it, and when it's ready there will be a few tweaks required to the pattern +before I can release it. + +But that news will have to play second fiddle to our wrap up of the year +(traditionally on December 10th here). It's not just about what happened over the last 12 months, +we'll also be rolling out some changes to safeguard the future of this project. + +10 more sleeps :) + + diff --git a/markdown/org/blog/roundup-2017-11/nl.md b/markdown/org/blog/roundup-2017-11/nl.md new file mode 100644 index 00000000000..5884988f3c3 --- /dev/null +++ b/markdown/org/blog/roundup-2017-11/nl.md @@ -0,0 +1,164 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of December" +date: "2017-11-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c9c5c5e10d2ed6e9f2935b047afa76c1ddd7c834-2000x1333.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - November 2017: Benjamin, on-boarding, showcases, and our on-demand tiler [Niet vertaald]" +--- + + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at November +November has been busy around here. While lot of the work has been happening behind the scenes +-- more on that in December -- there's also a list of things that are already rolled out. + +Here's the most important changes: + +### Meet Benjamin +![Wouter showing off Benjamin](https://posts.freesewing.org/uploads/benjamin_fc9844f4bd.jpg) +First up: a new pattern. The Benjamin Bow tie is [now available](/patterns/benjamin) in beta. + +![More bow ties from Wouter's personal stash](https://posts.freesewing.org/uploads/bowties_4f3e05ec53.jpg) + +Benjamin is a bow tie, and as I explained in [the announcement blog post](/en/blog/benjamin-bow-tie-beta/) +this release is kind of a big deal. + +That's because it's the first ever pattern to have been contributed by the community. +More specifically, it was [Wouter](/users/xdpug) who designed and programmed the pattern. + +So shout-out to him for being the first person to contribute a pattern. And if you +[hang around in the freesewing chat room](https://discord.freesewing.org/), +you know that he's already started working on his next pattern. + + +### Better user on-boarding + +I've changed the sign-up flow a bit to help people discover all the options they can set in their account. + +![The welcome page guides you through your account setup](https://posts.freesewing.org/uploads/welcome_e02a39ca3b.png) + +The change is two-fold. First you are now auto-magically logged in +when you click the email confirmation link for your account. + +Second, we send you to the welcome page and guide you +through a few steps to finalize your account setup. Specifically: + + - Configure your units + - Configure your username + - Configure your profile picture + - Configure your social media accounts + +(More on that last one later in this post) + +All of these settings are available in [your account](/account), but people +frequently don't realize that. +With the new sign-up flow, that should no longer be the case. + +> ##### Hey, I never got a handy welcome page like that +> At any time, you can go to [the welcome page](/welcome) +> to check or update your account settings. + +### Mixed units warning + +One of the issues that drove the changes to the on-boarding of new users was the +issue of mixed units. + +Mixed units is when your account is configured in metric, but your model is set +to imperial (or vice-versa). + +![An example warning when units are mixed between your account and your model](https://posts.freesewing.org/uploads/units_mismatch_warning_058d7de9b4.png) + +This is supported. If you make things for other people in other parts of the world, +this flexibility is handy. + +But it's a rather niche scenario, and more often than not it's due to the user not +realizing their units are set as they are. + +So now, when you draft a pattern with mixed units, we'll show you a warning box to make +sure that you do actually intend to use mixed units. + +### Per-pattern default seam allowance +The roll-out of Benjamin raised another issue: standard seam allowance. + +For a bow tie, the current standard seam allowance (1cm for metric, 5/8" for imperial) +is too large. So Wouter wanted some way to change the standard seam allowance. + +![Here too, we've added a little notification to make sure you are aware](https://posts.freesewing.org/uploads/non_standard_sa_warning_e5046e98a7.png) + +So, that's what we implemented. Going forward, patterns can set the standard seam allowance +(for both metric and imperial). If they don't, we revert to 1cm|5/8" as before. + +Note that this is only the default seam allowance. When you draft a pattern you can still +set the seam allowance to whatever you like. + +### Social media accounts + +If you clicked the link to the welcome page, or if you check out the +settings in [your profile](/profile) you'll see that you can now enter your +username for a few other sites: + + - Twitter + - Instagram + - GitHub + +No need to worry, [your privacy is in good hands here](/blog/privacy-choices/). +I am not interested in collecting your data, and the only reason +this is here is because people [asked for it](https://github.com/freesewing/site/issues/184). + +![After Quentin added his Instagram and GitHub accounts to his settings, his comment now have links to those accounts])comments-social.png) + +Links to your social media accounts will appear on your profile page and along your comments. + +### More showcases + +We've added a bunch of new [showcases](/showcase) this month. +Every maker that has one or more showcases here on the site has their own page +that lists all their showcases. + +![An example of links on a maker page. In this case, Anneke](https://posts.freesewing.org/uploads/maker_links_8504a1b00d.png) + +This month, we've updated those pages with links to the blog and/or social media +accounts of these makers. +The idea is that people who feel you've made a cool thing can find out a bit more about you. + +### Referrer policy, or why you never get any visitors from freesewing.org + +We've rolled out the strictest referral policy: `no-referrer`. It blocks all referrer information. + +This means that if you run Google analytics -- or some other website statistics tool -- +on your blog or website, you won't see traffic from freesewing.org. + +![Our referrer policy: No](https://posts.freesewing.org/uploads/no_13049a23c3.gif) + +That doesn't mean that people aren't clicking links to your blog, but we simply +block the referrer header from being set, so Google has no idea where people come from. + +Why you ask? Because privacy. + +### On-demand tiler +When you draft a pattern here, you can download it in a number of formats, all neatly tiled +so you can print them. + +You can also download the SVG source code to make further changes to the patterns. +But once you have made those changes, there's no easy way for you to get it as a printable PDF. + +![The on-demand tiler does what you'd expect](tiler.svg) + +Well now there is. We've added [an on-demand tiler](/tools/tiler) to the site that does just that. +Upload your SVG, pick the format of your choice, and we'll tile it for you. + +## Looking ahead to December + +I had hoped to release my winter coat pattern during November, but alas that didn't work out. +I'm actually still making it, and when it's ready there will be a few tweaks required to the pattern +before I can release it. + +But that news will have to play second fiddle to our wrap up of the year +(traditionally on December 10th here). It's not just about what happened over the last 12 months, +we'll also be rolling out some changes to safeguard the future of this project. + +10 more sleeps :) + + diff --git a/markdown/org/blog/roundup-2017-12/de.md b/markdown/org/blog/roundup-2017-12/de.md new file mode 100644 index 00000000000..1881d8ddf5c --- /dev/null +++ b/markdown/org/blog/roundup-2017-12/de.md @@ -0,0 +1,159 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of January" +date: "2017-12-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/7203a0f33c8c3d1cd6abdbca5c0fd85f44db3893-2000x1330.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - December 2017: Patrons, Bent, Carlton, Florent, and the looming Inkscape issue [Nicht übersetzt]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at December +As you may or may not know, for freesewing the year starts on December 10th. +This way, I only have to write this blog post on New Year's eve, rather than roll out a bunch of new changes. + +What changes? I'm glad you asked: + +### We have patrons now + +This was really big news for me, and something that we had been working on behind the scenes for a good while. +But 3 weeks ago, we finally unveiled our new patron system. + +The [announcement blog post](/blog/calling-all-patrons/) has all the details, plus an open-hearted look at the +financial side of this project. If you haven't read it yet, I recommend it. + +![Spreading the word about our new patron approach](https://posts.freesewing.org/uploads/patrons_ig_bad479bb83.png) + + +The gist of it is that we are building a bedrock of loyal supporters to ensure a +sustainable future for freesewing.org, our code, our patterns, and our community. + +These people are our Patrons, and they support us with a small monthly contribution. +We have three tiers, and they all come with their own prices and perks. You can find all the info +on [the patrons sign-up page](/patrons/join). + +We are 3 weeks in now, and so far [25 people](/patrons) have shown their support for this project by becoming a patron. + +Needless to say, this is truly wonderful news that we're all very excited about. + + +### A logo tweak + +The roll out of our patron system had an unforeseen side-effect: We needed to simplify the freesewing logo a bit +so we could order all that swag with the logo on it. + +![The new logo](https://posts.freesewing.org/uploads/logo_cb4d9e16ca.svg) +![The old logo](https://posts.freesewing.org/uploads/old_logo_flag_cbfc5a5ff1.png) + +Turns out there's a limit to the amount of detail you can get embossed into jeans rivets or buttons, or woven into labels. +(that's just some of the swag our patrons get). + +So, we've streamlined the logo a bit. It's been on the site and our social media accounts since December 10th, but +we hadn't updated our auto-generated avatars yet. That's something we've managed to squeeze in in the last hours of +December (and the year) so that's good too. + +### New patterns + +We've had three (yes 3) pattern releases in December. + +[Florent](/patterns/florent) is a flat cap pattern that was contributed by +[Quentin](/users/ptzcb). The [announcement blog post](/blog/florent-flat-cap-beta/) has all the details. + +Then later this month, we published [Carlton](/patterns/carlton) and [Bent](/patterns/bent), the block it's based on. +I've worked with [Anneke](/showcase/maker/annekecaramin) to make this pattern happen, and a female version of the coat is coming. +You know what, you should probably read all about it [in this blog post](/announcing-carlton-and-bent/). + +### Model name and draft reference are now printed on every pattern part + +We got a request to add the model and draft info to the printed pattern. People who were using a given pattern +for different people (imagine making a hoodie for yourself and your partner) got confused about which parts belonged to which draft. + +That seemed like a good idea to us, so we've added this info to the patterns. If you have an +older draft in your account, you can simply re-draft it to update it. + +### Data export + +We've grouped a few harder to find pages in a new [Tools](/tools/) entry in the account section of the menu. + +It contains a link to our RSS feed of the blog, our on-demand tiler, and a link to remove your account, +but none of those are new, we've just grouped them so they'd be easier to find. + +What is new is the ability to export all the data we have on file for you. + +This work is in preparation of the changes we'll be making next month, which brings me to: + +## Looking ahead to January + +There's new patterns in the pipeline, but I'm not ready to commit to a deadline for these yet, mostly because +we have a bunch of other stuff on our plate. Including: + +### Open data and privacy talk + +We had a bit of a debate about whether or not we should publish anonymized measurements data here at freesewing. + +I won't repeat everything here, but [our tweet](https://twitter.com/j__st/status/941586171158777856) +and [Instagram post](https://www.instagram.com/p/Bct2jUEnuS9/) on the topic get a lot of responses. + +A vast majority of people supports this idea, and as such we have plans to move ahead with it. +However, if we do this, we want to do it right and completely in the open. +So expect a blog post on the matter shortly. + +The questions that came up as we were discussing the possibility of publishing this data tend to +revolve around privacy. We are --- and remain --- committed to protecting the privacy or all +our users and visitors, and have written about +[the choices we have made to guarantee your privacy](/blog/privacy-choices/). + +Thinking about these issues made us realize that we want to provide a more iron-clad +guarantee than a blog post. So, we will draft and publish a privacy notice in line +with the upcoming GDPR. + +Don't know what GDPR is? Good. Keep reading. + +### GDPR compliance + +The GDPR is the [General Data Protection Regulation](https://en.wikipedia.org/wiki/General_Data_Protection_Regulation) +of the European Union. It replaces the *Data Protection Directive* and is a more ambitious piece of +data protection legislation. + +The GDPR will become active in May 2018, and by that time, freesewing will be ready for it. +Specifically, we will publish a privacy notice that outlines exactly what happens to your data, +and we will make certain that all your rights are respected. + +We are still planning how exactly we will tackle this, and for the most part, these will be cosmetic changes +and that won't change anything about freesewing as such. + +But we value your privacy, and we want to practice what we preach, so we'll be making sure to do what's right. + +### Core issue #204 - The Inkscape default units quandary + +Under the heading *Important changes* the +[release notes for Inkscape +version 0.92](http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92#Important_changes) list: + +> The default resolution was changed from 90dpi to 96dpi, to match the CSS standard. + +This seemingly trivial update to the open source SVG editor will have some profound ripple effects for freesewing. + +While it won't impact our code as such, we use Inkscape to turn the SVG patterns we generate into the PDFs that you +print at home. And if now Inkscape thinks that one inch no longer holds 90, but 96 pixels, your patterns will be +scaled incorrectly, which is kind of a big deal. + +Given that we can continue to run an older build of Inkscape to do our bidding, this doesn't mean things are on fire just yet. +But it's a problem we will have to tackle sooner rather than later. + +That's because even when we fix it, once we start using the new Inkscape, it will still incorrectly handle the drafts +that have been generated prior to the fix and that are still stored in people's profiles. +Needless to say, I see a lot of mucking about with the SVG viewbox in my future. + +There's other changes in the newest Inkscape too that can potentially wreak havoc. Most likely to cause a stink-up +is the new way the *line-height* attribute will be handled in text. Less dramatic, but still inconvenient. + +While these changes add an unwelcome number of entries to our to-do list, it's worth pointing out that +the Inkscape maintainers make these changes because they thing it's the right thing, and that going forward, +this will be the better option. + +So, in the same spirit, we'll make sure to follow suit. + +But that's for next year. + diff --git a/markdown/org/blog/roundup-2017-12/en.md b/markdown/org/blog/roundup-2017-12/en.md new file mode 100644 index 00000000000..56428f773c2 --- /dev/null +++ b/markdown/org/blog/roundup-2017-12/en.md @@ -0,0 +1,159 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of January" +date: "2017-12-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/7203a0f33c8c3d1cd6abdbca5c0fd85f44db3893-2000x1330.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - December 2017: Patrons, Bent, Carlton, Florent, and the looming Inkscape issue" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at December +As you may or may not know, for freesewing the year starts on December 10th. +This way, I only have to write this blog post on New Year's eve, rather than roll out a bunch of new changes. + +What changes? I'm glad you asked: + +### We have patrons now + +This was really big news for me, and something that we had been working on behind the scenes for a good while. +But 3 weeks ago, we finally unveiled our new patron system. + +The [announcement blog post](/blog/calling-all-patrons/) has all the details, plus an open-hearted look at the +financial side of this project. If you haven't read it yet, I recommend it. + +![Spreading the word about our new patron approach](https://posts.freesewing.org/uploads/patrons_ig_bad479bb83.png) + + +The gist of it is that we are building a bedrock of loyal supporters to ensure a +sustainable future for freesewing.org, our code, our patterns, and our community. + +These people are our Patrons, and they support us with a small monthly contribution. +We have three tiers, and they all come with their own prices and perks. You can find all the info +on [the patrons sign-up page](/patrons/join). + +We are 3 weeks in now, and so far [25 people](/patrons) have shown their support for this project by becoming a patron. + +Needless to say, this is truly wonderful news that we're all very excited about. + + +### A logo tweak + +The roll out of our patron system had an unforeseen side-effect: We needed to simplify the freesewing logo a bit +so we could order all that swag with the logo on it. + +![The new logo](https://posts.freesewing.org/uploads/logo_cb4d9e16ca.svg) +![The old logo](https://posts.freesewing.org/uploads/old_logo_flag_cbfc5a5ff1.png) + +Turns out there's a limit to the amount of detail you can get embossed into jeans rivets or buttons, or woven into labels. +(that's just some of the swag our patrons get). + +So, we've streamlined the logo a bit. It's been on the site and our social media accounts since December 10th, but +we hadn't updated our auto-generated avatars yet. That's something we've managed to squeeze in in the last hours of +December (and the year) so that's good too. + +### New patterns + +We've had three (yes 3) pattern releases in December. + +[Florent](/patterns/florent) is a flat cap pattern that was contributed by +[Quentin](/users/ptzcb). The [announcement blog post](/blog/florent-flat-cap-beta/) has all the details. + +Then later this month, we published [Carlton](/patterns/carlton) and [Bent](/patterns/bent), the block it's based on. +I've worked with [Anneke](/showcase/maker/annekecaramin) to make this pattern happen, and a female version of the coat is coming. +You know what, you should probably read all about it [in this blog post](/announcing-carlton-and-bent/). + +### Model name and draft reference are now printed on every pattern part + +We got a request to add the model and draft info to the printed pattern. People who were using a given pattern +for different people (imagine making a hoodie for yourself and your partner) got confused about which parts belonged to which draft. + +That seemed like a good idea to us, so we've added this info to the patterns. If you have an +older draft in your account, you can simply re-draft it to update it. + +### Data export + +We've grouped a few harder to find pages in a new [Tools](/tools/) entry in the account section of the menu. + +It contains a link to our RSS feed of the blog, our on-demand tiler, and a link to remove your account, +but none of those are new, we've just grouped them so they'd be easier to find. + +What is new is the ability to export all the data we have on file for you. + +This work is in preparation of the changes we'll be making next month, which brings me to: + +## Looking ahead to January + +There's new patterns in the pipeline, but I'm not ready to commit to a deadline for these yet, mostly because +we have a bunch of other stuff on our plate. Including: + +### Open data and privacy talk + +We had a bit of a debate about whether or not we should publish anonymized measurements data here at freesewing. + +I won't repeat everything here, but [our tweet](https://twitter.com/j__st/status/941586171158777856) +and [Instagram post](https://www.instagram.com/p/Bct2jUEnuS9/) on the topic get a lot of responses. + +A vast majority of people supports this idea, and as such we have plans to move ahead with it. +However, if we do this, we want to do it right and completely in the open. +So expect a blog post on the matter shortly. + +The questions that came up as we were discussing the possibility of publishing this data tend to +revolve around privacy. We are --- and remain --- committed to protecting the privacy or all +our users and visitors, and have written about +[the choices we have made to guarantee your privacy](/blog/privacy-choices/). + +Thinking about these issues made us realize that we want to provide a more iron-clad +guarantee than a blog post. So, we will draft and publish a privacy notice in line +with the upcoming GDPR. + +Don't know what GDPR is? Good. Keep reading. + +### GDPR compliance + +The GDPR is the [General Data Protection Regulation](https://en.wikipedia.org/wiki/General_Data_Protection_Regulation) +of the European Union. It replaces the *Data Protection Directive* and is a more ambitious piece of +data protection legislation. + +The GDPR will become active in May 2018, and by that time, freesewing will be ready for it. +Specifically, we will publish a privacy notice that outlines exactly what happens to your data, +and we will make certain that all your rights are respected. + +We are still planning how exactly we will tackle this, and for the most part, these will be cosmetic changes +and that won't change anything about freesewing as such. + +But we value your privacy, and we want to practice what we preach, so we'll be making sure to do what's right. + +### Core issue #204 - The Inkscape default units quandary + +Under the heading *Important changes* the +[release notes for Inkscape +version 0.92](http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92#Important_changes) list: + +> The default resolution was changed from 90dpi to 96dpi, to match the CSS standard. + +This seemingly trivial update to the open source SVG editor will have some profound ripple effects for freesewing. + +While it won't impact our code as such, we use Inkscape to turn the SVG patterns we generate into the PDFs that you +print at home. And if now Inkscape thinks that one inch no longer holds 90, but 96 pixels, your patterns will be +scaled incorrectly, which is kind of a big deal. + +Given that we can continue to run an older build of Inkscape to do our bidding, this doesn't mean things are on fire just yet. +But it's a problem we will have to tackle sooner rather than later. + +That's because even when we fix it, once we start using the new Inkscape, it will still incorrectly handle the drafts +that have been generated prior to the fix and that are still stored in people's profiles. +Needless to say, I see a lot of mucking about with the SVG viewbox in my future. + +There's other changes in the newest Inkscape too that can potentially wreak havoc. Most likely to cause a stink-up +is the new way the *line-height* attribute will be handled in text. Less dramatic, but still inconvenient. + +While these changes add an unwelcome number of entries to our to-do list, it's worth pointing out that +the Inkscape maintainers make these changes because they thing it's the right thing, and that going forward, +this will be the better option. + +So, in the same spirit, we'll make sure to follow suit. + +But that's for next year. + diff --git a/markdown/org/blog/roundup-2017-12/es.md b/markdown/org/blog/roundup-2017-12/es.md new file mode 100644 index 00000000000..5c5943d975c --- /dev/null +++ b/markdown/org/blog/roundup-2017-12/es.md @@ -0,0 +1,159 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of January" +date: "2017-12-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/7203a0f33c8c3d1cd6abdbca5c0fd85f44db3893-2000x1330.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - December 2017: Patrons, Bent, Carlton, Florent, and the looming Inkscape issue [No traducido]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at December +As you may or may not know, for freesewing the year starts on December 10th. +This way, I only have to write this blog post on New Year's eve, rather than roll out a bunch of new changes. + +What changes? I'm glad you asked: + +### We have patrons now + +This was really big news for me, and something that we had been working on behind the scenes for a good while. +But 3 weeks ago, we finally unveiled our new patron system. + +The [announcement blog post](/blog/calling-all-patrons/) has all the details, plus an open-hearted look at the +financial side of this project. If you haven't read it yet, I recommend it. + +![Spreading the word about our new patron approach](https://posts.freesewing.org/uploads/patrons_ig_bad479bb83.png) + + +The gist of it is that we are building a bedrock of loyal supporters to ensure a +sustainable future for freesewing.org, our code, our patterns, and our community. + +These people are our Patrons, and they support us with a small monthly contribution. +We have three tiers, and they all come with their own prices and perks. You can find all the info +on [the patrons sign-up page](/patrons/join). + +We are 3 weeks in now, and so far [25 people](/patrons) have shown their support for this project by becoming a patron. + +Needless to say, this is truly wonderful news that we're all very excited about. + + +### A logo tweak + +The roll out of our patron system had an unforeseen side-effect: We needed to simplify the freesewing logo a bit +so we could order all that swag with the logo on it. + +![The new logo](https://posts.freesewing.org/uploads/logo_cb4d9e16ca.svg) +![The old logo](https://posts.freesewing.org/uploads/old_logo_flag_cbfc5a5ff1.png) + +Turns out there's a limit to the amount of detail you can get embossed into jeans rivets or buttons, or woven into labels. +(that's just some of the swag our patrons get). + +So, we've streamlined the logo a bit. It's been on the site and our social media accounts since December 10th, but +we hadn't updated our auto-generated avatars yet. That's something we've managed to squeeze in in the last hours of +December (and the year) so that's good too. + +### New patterns + +We've had three (yes 3) pattern releases in December. + +[Florent](/patterns/florent) is a flat cap pattern that was contributed by +[Quentin](/users/ptzcb). The [announcement blog post](/blog/florent-flat-cap-beta/) has all the details. + +Then later this month, we published [Carlton](/patterns/carlton) and [Bent](/patterns/bent), the block it's based on. +I've worked with [Anneke](/showcase/maker/annekecaramin) to make this pattern happen, and a female version of the coat is coming. +You know what, you should probably read all about it [in this blog post](/announcing-carlton-and-bent/). + +### Model name and draft reference are now printed on every pattern part + +We got a request to add the model and draft info to the printed pattern. People who were using a given pattern +for different people (imagine making a hoodie for yourself and your partner) got confused about which parts belonged to which draft. + +That seemed like a good idea to us, so we've added this info to the patterns. If you have an +older draft in your account, you can simply re-draft it to update it. + +### Data export + +We've grouped a few harder to find pages in a new [Tools](/tools/) entry in the account section of the menu. + +It contains a link to our RSS feed of the blog, our on-demand tiler, and a link to remove your account, +but none of those are new, we've just grouped them so they'd be easier to find. + +What is new is the ability to export all the data we have on file for you. + +This work is in preparation of the changes we'll be making next month, which brings me to: + +## Looking ahead to January + +There's new patterns in the pipeline, but I'm not ready to commit to a deadline for these yet, mostly because +we have a bunch of other stuff on our plate. Including: + +### Open data and privacy talk + +We had a bit of a debate about whether or not we should publish anonymized measurements data here at freesewing. + +I won't repeat everything here, but [our tweet](https://twitter.com/j__st/status/941586171158777856) +and [Instagram post](https://www.instagram.com/p/Bct2jUEnuS9/) on the topic get a lot of responses. + +A vast majority of people supports this idea, and as such we have plans to move ahead with it. +However, if we do this, we want to do it right and completely in the open. +So expect a blog post on the matter shortly. + +The questions that came up as we were discussing the possibility of publishing this data tend to +revolve around privacy. We are --- and remain --- committed to protecting the privacy or all +our users and visitors, and have written about +[the choices we have made to guarantee your privacy](/blog/privacy-choices/). + +Thinking about these issues made us realize that we want to provide a more iron-clad +guarantee than a blog post. So, we will draft and publish a privacy notice in line +with the upcoming GDPR. + +Don't know what GDPR is? Good. Keep reading. + +### GDPR compliance + +The GDPR is the [General Data Protection Regulation](https://en.wikipedia.org/wiki/General_Data_Protection_Regulation) +of the European Union. It replaces the *Data Protection Directive* and is a more ambitious piece of +data protection legislation. + +The GDPR will become active in May 2018, and by that time, freesewing will be ready for it. +Specifically, we will publish a privacy notice that outlines exactly what happens to your data, +and we will make certain that all your rights are respected. + +We are still planning how exactly we will tackle this, and for the most part, these will be cosmetic changes +and that won't change anything about freesewing as such. + +But we value your privacy, and we want to practice what we preach, so we'll be making sure to do what's right. + +### Core issue #204 - The Inkscape default units quandary + +Under the heading *Important changes* the +[release notes for Inkscape +version 0.92](http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92#Important_changes) list: + +> The default resolution was changed from 90dpi to 96dpi, to match the CSS standard. + +This seemingly trivial update to the open source SVG editor will have some profound ripple effects for freesewing. + +While it won't impact our code as such, we use Inkscape to turn the SVG patterns we generate into the PDFs that you +print at home. And if now Inkscape thinks that one inch no longer holds 90, but 96 pixels, your patterns will be +scaled incorrectly, which is kind of a big deal. + +Given that we can continue to run an older build of Inkscape to do our bidding, this doesn't mean things are on fire just yet. +But it's a problem we will have to tackle sooner rather than later. + +That's because even when we fix it, once we start using the new Inkscape, it will still incorrectly handle the drafts +that have been generated prior to the fix and that are still stored in people's profiles. +Needless to say, I see a lot of mucking about with the SVG viewbox in my future. + +There's other changes in the newest Inkscape too that can potentially wreak havoc. Most likely to cause a stink-up +is the new way the *line-height* attribute will be handled in text. Less dramatic, but still inconvenient. + +While these changes add an unwelcome number of entries to our to-do list, it's worth pointing out that +the Inkscape maintainers make these changes because they thing it's the right thing, and that going forward, +this will be the better option. + +So, in the same spirit, we'll make sure to follow suit. + +But that's for next year. + diff --git a/markdown/org/blog/roundup-2017-12/fr.md b/markdown/org/blog/roundup-2017-12/fr.md new file mode 100644 index 00000000000..7edb9991de5 --- /dev/null +++ b/markdown/org/blog/roundup-2017-12/fr.md @@ -0,0 +1,159 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of January" +date: "2017-12-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/7203a0f33c8c3d1cd6abdbca5c0fd85f44db3893-2000x1330.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - December 2017: Patrons, Bent, Carlton, Florent, and the looming Inkscape issue [Non traduit]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at December +As you may or may not know, for freesewing the year starts on December 10th. +This way, I only have to write this blog post on New Year's eve, rather than roll out a bunch of new changes. + +What changes? I'm glad you asked: + +### We have patrons now + +This was really big news for me, and something that we had been working on behind the scenes for a good while. +But 3 weeks ago, we finally unveiled our new patron system. + +The [announcement blog post](/blog/calling-all-patrons/) has all the details, plus an open-hearted look at the +financial side of this project. If you haven't read it yet, I recommend it. + +![Spreading the word about our new patron approach](https://posts.freesewing.org/uploads/patrons_ig_bad479bb83.png) + + +The gist of it is that we are building a bedrock of loyal supporters to ensure a +sustainable future for freesewing.org, our code, our patterns, and our community. + +These people are our Patrons, and they support us with a small monthly contribution. +We have three tiers, and they all come with their own prices and perks. You can find all the info +on [the patrons sign-up page](/patrons/join). + +We are 3 weeks in now, and so far [25 people](/patrons) have shown their support for this project by becoming a patron. + +Needless to say, this is truly wonderful news that we're all very excited about. + + +### A logo tweak + +The roll out of our patron system had an unforeseen side-effect: We needed to simplify the freesewing logo a bit +so we could order all that swag with the logo on it. + +![The new logo](https://posts.freesewing.org/uploads/logo_cb4d9e16ca.svg) +![The old logo](https://posts.freesewing.org/uploads/old_logo_flag_cbfc5a5ff1.png) + +Turns out there's a limit to the amount of detail you can get embossed into jeans rivets or buttons, or woven into labels. +(that's just some of the swag our patrons get). + +So, we've streamlined the logo a bit. It's been on the site and our social media accounts since December 10th, but +we hadn't updated our auto-generated avatars yet. That's something we've managed to squeeze in in the last hours of +December (and the year) so that's good too. + +### New patterns + +We've had three (yes 3) pattern releases in December. + +[Florent](/patterns/florent) is a flat cap pattern that was contributed by +[Quentin](/users/ptzcb). The [announcement blog post](/blog/florent-flat-cap-beta/) has all the details. + +Then later this month, we published [Carlton](/patterns/carlton) and [Bent](/patterns/bent), the block it's based on. +I've worked with [Anneke](/showcase/maker/annekecaramin) to make this pattern happen, and a female version of the coat is coming. +You know what, you should probably read all about it [in this blog post](/announcing-carlton-and-bent/). + +### Model name and draft reference are now printed on every pattern part + +We got a request to add the model and draft info to the printed pattern. People who were using a given pattern +for different people (imagine making a hoodie for yourself and your partner) got confused about which parts belonged to which draft. + +That seemed like a good idea to us, so we've added this info to the patterns. If you have an +older draft in your account, you can simply re-draft it to update it. + +### Data export + +We've grouped a few harder to find pages in a new [Tools](/tools/) entry in the account section of the menu. + +It contains a link to our RSS feed of the blog, our on-demand tiler, and a link to remove your account, +but none of those are new, we've just grouped them so they'd be easier to find. + +What is new is the ability to export all the data we have on file for you. + +This work is in preparation of the changes we'll be making next month, which brings me to: + +## Looking ahead to January + +There's new patterns in the pipeline, but I'm not ready to commit to a deadline for these yet, mostly because +we have a bunch of other stuff on our plate. Including: + +### Open data and privacy talk + +We had a bit of a debate about whether or not we should publish anonymized measurements data here at freesewing. + +I won't repeat everything here, but [our tweet](https://twitter.com/j__st/status/941586171158777856) +and [Instagram post](https://www.instagram.com/p/Bct2jUEnuS9/) on the topic get a lot of responses. + +A vast majority of people supports this idea, and as such we have plans to move ahead with it. +However, if we do this, we want to do it right and completely in the open. +So expect a blog post on the matter shortly. + +The questions that came up as we were discussing the possibility of publishing this data tend to +revolve around privacy. We are --- and remain --- committed to protecting the privacy or all +our users and visitors, and have written about +[the choices we have made to guarantee your privacy](/blog/privacy-choices/). + +Thinking about these issues made us realize that we want to provide a more iron-clad +guarantee than a blog post. So, we will draft and publish a privacy notice in line +with the upcoming GDPR. + +Don't know what GDPR is? Good. Keep reading. + +### GDPR compliance + +The GDPR is the [General Data Protection Regulation](https://en.wikipedia.org/wiki/General_Data_Protection_Regulation) +of the European Union. It replaces the *Data Protection Directive* and is a more ambitious piece of +data protection legislation. + +The GDPR will become active in May 2018, and by that time, freesewing will be ready for it. +Specifically, we will publish a privacy notice that outlines exactly what happens to your data, +and we will make certain that all your rights are respected. + +We are still planning how exactly we will tackle this, and for the most part, these will be cosmetic changes +and that won't change anything about freesewing as such. + +But we value your privacy, and we want to practice what we preach, so we'll be making sure to do what's right. + +### Core issue #204 - The Inkscape default units quandary + +Under the heading *Important changes* the +[release notes for Inkscape +version 0.92](http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92#Important_changes) list: + +> The default resolution was changed from 90dpi to 96dpi, to match the CSS standard. + +This seemingly trivial update to the open source SVG editor will have some profound ripple effects for freesewing. + +While it won't impact our code as such, we use Inkscape to turn the SVG patterns we generate into the PDFs that you +print at home. And if now Inkscape thinks that one inch no longer holds 90, but 96 pixels, your patterns will be +scaled incorrectly, which is kind of a big deal. + +Given that we can continue to run an older build of Inkscape to do our bidding, this doesn't mean things are on fire just yet. +But it's a problem we will have to tackle sooner rather than later. + +That's because even when we fix it, once we start using the new Inkscape, it will still incorrectly handle the drafts +that have been generated prior to the fix and that are still stored in people's profiles. +Needless to say, I see a lot of mucking about with the SVG viewbox in my future. + +There's other changes in the newest Inkscape too that can potentially wreak havoc. Most likely to cause a stink-up +is the new way the *line-height* attribute will be handled in text. Less dramatic, but still inconvenient. + +While these changes add an unwelcome number of entries to our to-do list, it's worth pointing out that +the Inkscape maintainers make these changes because they thing it's the right thing, and that going forward, +this will be the better option. + +So, in the same spirit, we'll make sure to follow suit. + +But that's for next year. + diff --git a/markdown/org/blog/roundup-2017-12/nl.md b/markdown/org/blog/roundup-2017-12/nl.md new file mode 100644 index 00000000000..0953ed42b4c --- /dev/null +++ b/markdown/org/blog/roundup-2017-12/nl.md @@ -0,0 +1,159 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of January" +date: "2017-12-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/7203a0f33c8c3d1cd6abdbca5c0fd85f44db3893-2000x1330.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - December 2017: Patrons, Bent, Carlton, Florent, and the looming Inkscape issue [Niet vertaald]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at December +As you may or may not know, for freesewing the year starts on December 10th. +This way, I only have to write this blog post on New Year's eve, rather than roll out a bunch of new changes. + +What changes? I'm glad you asked: + +### We have patrons now + +This was really big news for me, and something that we had been working on behind the scenes for a good while. +But 3 weeks ago, we finally unveiled our new patron system. + +The [announcement blog post](/blog/calling-all-patrons/) has all the details, plus an open-hearted look at the +financial side of this project. If you haven't read it yet, I recommend it. + +![Spreading the word about our new patron approach](https://posts.freesewing.org/uploads/patrons_ig_bad479bb83.png) + + +The gist of it is that we are building a bedrock of loyal supporters to ensure a +sustainable future for freesewing.org, our code, our patterns, and our community. + +These people are our Patrons, and they support us with a small monthly contribution. +We have three tiers, and they all come with their own prices and perks. You can find all the info +on [the patrons sign-up page](/patrons/join). + +We are 3 weeks in now, and so far [25 people](/patrons) have shown their support for this project by becoming a patron. + +Needless to say, this is truly wonderful news that we're all very excited about. + + +### A logo tweak + +The roll out of our patron system had an unforeseen side-effect: We needed to simplify the freesewing logo a bit +so we could order all that swag with the logo on it. + +![The new logo](https://posts.freesewing.org/uploads/logo_cb4d9e16ca.svg) +![The old logo](https://posts.freesewing.org/uploads/old_logo_flag_cbfc5a5ff1.png) + +Turns out there's a limit to the amount of detail you can get embossed into jeans rivets or buttons, or woven into labels. +(that's just some of the swag our patrons get). + +So, we've streamlined the logo a bit. It's been on the site and our social media accounts since December 10th, but +we hadn't updated our auto-generated avatars yet. That's something we've managed to squeeze in in the last hours of +December (and the year) so that's good too. + +### New patterns + +We've had three (yes 3) pattern releases in December. + +[Florent](/patterns/florent) is a flat cap pattern that was contributed by +[Quentin](/users/ptzcb). The [announcement blog post](/blog/florent-flat-cap-beta/) has all the details. + +Then later this month, we published [Carlton](/patterns/carlton) and [Bent](/patterns/bent), the block it's based on. +I've worked with [Anneke](/showcase/maker/annekecaramin) to make this pattern happen, and a female version of the coat is coming. +You know what, you should probably read all about it [in this blog post](/announcing-carlton-and-bent/). + +### Model name and draft reference are now printed on every pattern part + +We got a request to add the model and draft info to the printed pattern. People who were using a given pattern +for different people (imagine making a hoodie for yourself and your partner) got confused about which parts belonged to which draft. + +That seemed like a good idea to us, so we've added this info to the patterns. If you have an +older draft in your account, you can simply re-draft it to update it. + +### Data export + +We've grouped a few harder to find pages in a new [Tools](/tools/) entry in the account section of the menu. + +It contains a link to our RSS feed of the blog, our on-demand tiler, and a link to remove your account, +but none of those are new, we've just grouped them so they'd be easier to find. + +What is new is the ability to export all the data we have on file for you. + +This work is in preparation of the changes we'll be making next month, which brings me to: + +## Looking ahead to January + +There's new patterns in the pipeline, but I'm not ready to commit to a deadline for these yet, mostly because +we have a bunch of other stuff on our plate. Including: + +### Open data and privacy talk + +We had a bit of a debate about whether or not we should publish anonymized measurements data here at freesewing. + +I won't repeat everything here, but [our tweet](https://twitter.com/j__st/status/941586171158777856) +and [Instagram post](https://www.instagram.com/p/Bct2jUEnuS9/) on the topic get a lot of responses. + +A vast majority of people supports this idea, and as such we have plans to move ahead with it. +However, if we do this, we want to do it right and completely in the open. +So expect a blog post on the matter shortly. + +The questions that came up as we were discussing the possibility of publishing this data tend to +revolve around privacy. We are --- and remain --- committed to protecting the privacy or all +our users and visitors, and have written about +[the choices we have made to guarantee your privacy](/blog/privacy-choices/). + +Thinking about these issues made us realize that we want to provide a more iron-clad +guarantee than a blog post. So, we will draft and publish a privacy notice in line +with the upcoming GDPR. + +Don't know what GDPR is? Good. Keep reading. + +### GDPR compliance + +The GDPR is the [General Data Protection Regulation](https://en.wikipedia.org/wiki/General_Data_Protection_Regulation) +of the European Union. It replaces the *Data Protection Directive* and is a more ambitious piece of +data protection legislation. + +The GDPR will become active in May 2018, and by that time, freesewing will be ready for it. +Specifically, we will publish a privacy notice that outlines exactly what happens to your data, +and we will make certain that all your rights are respected. + +We are still planning how exactly we will tackle this, and for the most part, these will be cosmetic changes +and that won't change anything about freesewing as such. + +But we value your privacy, and we want to practice what we preach, so we'll be making sure to do what's right. + +### Core issue #204 - The Inkscape default units quandary + +Under the heading *Important changes* the +[release notes for Inkscape +version 0.92](http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92#Important_changes) list: + +> The default resolution was changed from 90dpi to 96dpi, to match the CSS standard. + +This seemingly trivial update to the open source SVG editor will have some profound ripple effects for freesewing. + +While it won't impact our code as such, we use Inkscape to turn the SVG patterns we generate into the PDFs that you +print at home. And if now Inkscape thinks that one inch no longer holds 90, but 96 pixels, your patterns will be +scaled incorrectly, which is kind of a big deal. + +Given that we can continue to run an older build of Inkscape to do our bidding, this doesn't mean things are on fire just yet. +But it's a problem we will have to tackle sooner rather than later. + +That's because even when we fix it, once we start using the new Inkscape, it will still incorrectly handle the drafts +that have been generated prior to the fix and that are still stored in people's profiles. +Needless to say, I see a lot of mucking about with the SVG viewbox in my future. + +There's other changes in the newest Inkscape too that can potentially wreak havoc. Most likely to cause a stink-up +is the new way the *line-height* attribute will be handled in text. Less dramatic, but still inconvenient. + +While these changes add an unwelcome number of entries to our to-do list, it's worth pointing out that +the Inkscape maintainers make these changes because they thing it's the right thing, and that going forward, +this will be the better option. + +So, in the same spirit, we'll make sure to follow suit. + +But that's for next year. + diff --git a/markdown/org/blog/roundup-2018-01/de.md b/markdown/org/blog/roundup-2018-01/de.md new file mode 100644 index 00000000000..0bb65839d87 --- /dev/null +++ b/markdown/org/blog/roundup-2018-01/de.md @@ -0,0 +1,135 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of February" +date: "2018-01-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6fbc797ad0b3d50a8337bd2cb8401f04f63bffdd-2000x1125.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - January 2018: Inkscape DPI, version awareness, Bail, and Carlita [Nicht übersetzt]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at January +![More like this month](https://posts.freesewing.org/uploads/coffee_3f501d4076.gif) + +It might be [the record-breaking depressing weather in my neck of the woods +](https://www.theguardian.com/world/2018/jan/19/aint-no-sunshine-winter-darkest-europe), +but I feel like January took a lot out of me. So let's see if we have at least something +to show for it. + +### The Inkscape default units quandary + +At the start of the year, we rolled out core v1.3.0 to address [issue #204](https://github.com/freesewing/core/issues/204) +aka the the Inkscape default units quandary. + +It was a bit of an unusual fix because our hand was forced due to upstream changes made by the +Inkscape developers. In addition, we didn't only have to adapt our code, but also had to backport +the changes to all your existing drafts. + +If you were blissfully unaware of the whole thing, we wrote a blog post about it: +[Freesewing core v1.3.0 is out; Comes with fixes so good that we back-ported them to all your drafts](https://joost.freesewing.org/blog/core-v1.3.0-is-out/). + +### Version awareness + +We now keep track of which version of core generated your draft. We roll out fixes and improvements +all the time. So the drafts you have stored in your profile might be outdated. + +You are now informed about this, both on the draft's page itself and on your list of drafts. +A simple redraft will upgrade them to the latest version. + +> ##### Long-term vision for versioning +> +> This solution is a step up from the previous situation, but it doesn't allow for very +> granular version control. If you have 10 different Simon drafts stored in your profile, and we +> bump the core version number because we made a tweak to Carlton, all your drafts are marked +> as outdated, even though the changes don't impact them. +> +> With only a single core version number to depend on, there's no obvious way for us to keep track +> of what changes impact what pattern. +> +> The long-term plan here is to have a core version number and a pattern version number. +> This way, a version bump in one pattern will not impact other patterns. +> +> A version bump in core will still impact all patterns, but there should be far fewer core versions +> once we take all patterns out of core. +> +> The idea is that every pattern will be in its own repository, and we'll use composer to manage them +> as dependencies. +> +> But this is a long-term idea that won't be implemented until after we rewrite core. +> Yes, that's another long-term idea. + +### Bail for error handling + +In the first half of the month, we tried Rollbar for error handling and reporting. +While we liked the functionality it provided, we weren't too happy about the possible impact on +your privacy of sending that kind of data to a third party. + +So, we decided to write our own poor man's rollbar called Bail. Bail is now used in our data +and core backends, so when things break, we know about it. + +This effort also lead to a 2-week side-quest to write tests for our data backend. All details: +[Introducing freesewing bail: A poor man's rollbar --- because privacy](/blog/introducing-bail/) + +### Carlita is here + +A couple of days ago, we released the [Carlita Coat](/patterns/carlita), +the womenswear version of our Carlton coat. + +If you rushed out to get your hands on Carlita, it's good to know that she was released as +part of core v1.6.0 and we're now at v1.6.3, and that is mostly due to fixes and tweaks in +Carlton/Carlita. + +If you've got an earlier version of the pattern, please redraft. If you've already printed +it, perhaps have a look at [the changelog](https://github.com/freesewing/core/blob/develop/CHANGELOG.md) +to figure out what has changed. + +If you check the changelog, you'll also see that we started the month on core v1.2.9 and +are now running core v1.6.3, so I don't think it's just an idea that it was a busy month. + +## Looking ahead to February + +February is a short month so it's probably best to manage expectations. But here's +what I have in mind for it: + +### Carlton/Carlita documentation + +Quite frankly, this is like pulling teeth to me, so don't expect it to be finished by the +end of February, but I should at least have made some progress on the +documentation for the Carlton and Carlita patterns. + +On a related note, the increasing popularity of this site means I'm a lot more occupied with +various questions, and small issues that need my attention. + +All that feedback is a good thing +for it is how we improve things around here. But I do notice that it is becoming increasingly +difficult to dedicate a larger chunk of time to one specific thing. +Which is really what you need when tackling larger tasks such as writing documentation +or designing new patterns. + +I don't really have a solution for that, I'm just making the observation. + +### Maybe a Blake Blazer release + +I have a jacket pattern on my drawing board that's been there since the summer (it's called the Blake Blazer). +I really should just take out some time to wrap it up and publish it, but +I've been reluctant to do so because I can't seem to find the time to actually make +the jacket. + +I've used the pattern before for +[my refashioners make this year](/blog/the-refashioners-2017/), +but that's not exactly +a very representative example. + +I don't think I'll find the time to make a jacket in February, but perhaps a muslin is enough +to publish it in beta. + +### FOSDEM + +![All details on fosdem.org](https://posts.freesewing.org/uploads/fosdem_bb321397cc.png) + +[FOSDEM](http://fosdem.org/) --- the Free and Open Source Developers' European Meeting --- + is on the first weekend of February in Brussels. + +I'm planning to be there on Sunday, so if you're attending too, let me know or come and say hi. + diff --git a/markdown/org/blog/roundup-2018-01/en.md b/markdown/org/blog/roundup-2018-01/en.md new file mode 100644 index 00000000000..d255d458e25 --- /dev/null +++ b/markdown/org/blog/roundup-2018-01/en.md @@ -0,0 +1,135 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of February" +date: "2018-01-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6fbc797ad0b3d50a8337bd2cb8401f04f63bffdd-2000x1125.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - January 2018: Inkscape DPI, version awareness, Bail, and Carlita" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at January +![More like this month](https://posts.freesewing.org/uploads/coffee_3f501d4076.gif) + +It might be [the record-breaking depressing weather in my neck of the woods +](https://www.theguardian.com/world/2018/jan/19/aint-no-sunshine-winter-darkest-europe), +but I feel like January took a lot out of me. So let's see if we have at least something +to show for it. + +### The Inkscape default units quandary + +At the start of the year, we rolled out core v1.3.0 to address [issue #204](https://github.com/freesewing/core/issues/204) +aka the the Inkscape default units quandary. + +It was a bit of an unusual fix because our hand was forced due to upstream changes made by the +Inkscape developers. In addition, we didn't only have to adapt our code, but also had to backport +the changes to all your existing drafts. + +If you were blissfully unaware of the whole thing, we wrote a blog post about it: +[Freesewing core v1.3.0 is out; Comes with fixes so good that we back-ported them to all your drafts](https://joost.freesewing.org/blog/core-v1.3.0-is-out/). + +### Version awareness + +We now keep track of which version of core generated your draft. We roll out fixes and improvements +all the time. So the drafts you have stored in your profile might be outdated. + +You are now informed about this, both on the draft's page itself and on your list of drafts. +A simple redraft will upgrade them to the latest version. + +> ##### Long-term vision for versioning +> +> This solution is a step up from the previous situation, but it doesn't allow for very +> granular version control. If you have 10 different Simon drafts stored in your profile, and we +> bump the core version number because we made a tweak to Carlton, all your drafts are marked +> as outdated, even though the changes don't impact them. +> +> With only a single core version number to depend on, there's no obvious way for us to keep track +> of what changes impact what pattern. +> +> The long-term plan here is to have a core version number and a pattern version number. +> This way, a version bump in one pattern will not impact other patterns. +> +> A version bump in core will still impact all patterns, but there should be far fewer core versions +> once we take all patterns out of core. +> +> The idea is that every pattern will be in its own repository, and we'll use composer to manage them +> as dependencies. +> +> But this is a long-term idea that won't be implemented until after we rewrite core. +> Yes, that's another long-term idea. + +### Bail for error handling + +In the first half of the month, we tried Rollbar for error handling and reporting. +While we liked the functionality it provided, we weren't too happy about the possible impact on +your privacy of sending that kind of data to a third party. + +So, we decided to write our own poor man's rollbar called Bail. Bail is now used in our data +and core backends, so when things break, we know about it. + +This effort also lead to a 2-week side-quest to write tests for our data backend. All details: +[Introducing freesewing bail: A poor man's rollbar --- because privacy](/blog/introducing-bail/) + +### Carlita is here + +A couple of days ago, we released the [Carlita Coat](/patterns/carlita), +the womenswear version of our Carlton coat. + +If you rushed out to get your hands on Carlita, it's good to know that she was released as +part of core v1.6.0 and we're now at v1.6.3, and that is mostly due to fixes and tweaks in +Carlton/Carlita. + +If you've got an earlier version of the pattern, please redraft. If you've already printed +it, perhaps have a look at [the changelog](https://github.com/freesewing/core/blob/develop/CHANGELOG.md) +to figure out what has changed. + +If you check the changelog, you'll also see that we started the month on core v1.2.9 and +are now running core v1.6.3, so I don't think it's just an idea that it was a busy month. + +## Looking ahead to February + +February is a short month so it's probably best to manage expectations. But here's +what I have in mind for it: + +### Carlton/Carlita documentation + +Quite frankly, this is like pulling teeth to me, so don't expect it to be finished by the +end of February, but I should at least have made some progress on the +documentation for the Carlton and Carlita patterns. + +On a related note, the increasing popularity of this site means I'm a lot more occupied with +various questions, and small issues that need my attention. + +All that feedback is a good thing +for it is how we improve things around here. But I do notice that it is becoming increasingly +difficult to dedicate a larger chunk of time to one specific thing. +Which is really what you need when tackling larger tasks such as writing documentation +or designing new patterns. + +I don't really have a solution for that, I'm just making the observation. + +### Maybe a Blake Blazer release + +I have a jacket pattern on my drawing board that's been there since the summer (it's called the Blake Blazer). +I really should just take out some time to wrap it up and publish it, but +I've been reluctant to do so because I can't seem to find the time to actually make +the jacket. + +I've used the pattern before for +[my refashioners make this year](/blog/the-refashioners-2017/), +but that's not exactly +a very representative example. + +I don't think I'll find the time to make a jacket in February, but perhaps a muslin is enough +to publish it in beta. + +### FOSDEM + +![All details on fosdem.org](https://posts.freesewing.org/uploads/fosdem_bb321397cc.png) + +[FOSDEM](http://fosdem.org/) --- the Free and Open Source Developers' European Meeting --- + is on the first weekend of February in Brussels. + +I'm planning to be there on Sunday, so if you're attending too, let me know or come and say hi. + diff --git a/markdown/org/blog/roundup-2018-01/es.md b/markdown/org/blog/roundup-2018-01/es.md new file mode 100644 index 00000000000..75d86a2ad17 --- /dev/null +++ b/markdown/org/blog/roundup-2018-01/es.md @@ -0,0 +1,135 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of February" +date: "2018-01-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6fbc797ad0b3d50a8337bd2cb8401f04f63bffdd-2000x1125.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - January 2018: Inkscape DPI, version awareness, Bail, and Carlita [No traducido]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at January +![More like this month](https://posts.freesewing.org/uploads/coffee_3f501d4076.gif) + +It might be [the record-breaking depressing weather in my neck of the woods +](https://www.theguardian.com/world/2018/jan/19/aint-no-sunshine-winter-darkest-europe), +but I feel like January took a lot out of me. So let's see if we have at least something +to show for it. + +### The Inkscape default units quandary + +At the start of the year, we rolled out core v1.3.0 to address [issue #204](https://github.com/freesewing/core/issues/204) +aka the the Inkscape default units quandary. + +It was a bit of an unusual fix because our hand was forced due to upstream changes made by the +Inkscape developers. In addition, we didn't only have to adapt our code, but also had to backport +the changes to all your existing drafts. + +If you were blissfully unaware of the whole thing, we wrote a blog post about it: +[Freesewing core v1.3.0 is out; Comes with fixes so good that we back-ported them to all your drafts](https://joost.freesewing.org/blog/core-v1.3.0-is-out/). + +### Version awareness + +We now keep track of which version of core generated your draft. We roll out fixes and improvements +all the time. So the drafts you have stored in your profile might be outdated. + +You are now informed about this, both on the draft's page itself and on your list of drafts. +A simple redraft will upgrade them to the latest version. + +> ##### Long-term vision for versioning +> +> This solution is a step up from the previous situation, but it doesn't allow for very +> granular version control. If you have 10 different Simon drafts stored in your profile, and we +> bump the core version number because we made a tweak to Carlton, all your drafts are marked +> as outdated, even though the changes don't impact them. +> +> With only a single core version number to depend on, there's no obvious way for us to keep track +> of what changes impact what pattern. +> +> The long-term plan here is to have a core version number and a pattern version number. +> This way, a version bump in one pattern will not impact other patterns. +> +> A version bump in core will still impact all patterns, but there should be far fewer core versions +> once we take all patterns out of core. +> +> The idea is that every pattern will be in its own repository, and we'll use composer to manage them +> as dependencies. +> +> But this is a long-term idea that won't be implemented until after we rewrite core. +> Yes, that's another long-term idea. + +### Bail for error handling + +In the first half of the month, we tried Rollbar for error handling and reporting. +While we liked the functionality it provided, we weren't too happy about the possible impact on +your privacy of sending that kind of data to a third party. + +So, we decided to write our own poor man's rollbar called Bail. Bail is now used in our data +and core backends, so when things break, we know about it. + +This effort also lead to a 2-week side-quest to write tests for our data backend. All details: +[Introducing freesewing bail: A poor man's rollbar --- because privacy](/blog/introducing-bail/) + +### Carlita is here + +A couple of days ago, we released the [Carlita Coat](/patterns/carlita), +the womenswear version of our Carlton coat. + +If you rushed out to get your hands on Carlita, it's good to know that she was released as +part of core v1.6.0 and we're now at v1.6.3, and that is mostly due to fixes and tweaks in +Carlton/Carlita. + +If you've got an earlier version of the pattern, please redraft. If you've already printed +it, perhaps have a look at [the changelog](https://github.com/freesewing/core/blob/develop/CHANGELOG.md) +to figure out what has changed. + +If you check the changelog, you'll also see that we started the month on core v1.2.9 and +are now running core v1.6.3, so I don't think it's just an idea that it was a busy month. + +## Looking ahead to February + +February is a short month so it's probably best to manage expectations. But here's +what I have in mind for it: + +### Carlton/Carlita documentation + +Quite frankly, this is like pulling teeth to me, so don't expect it to be finished by the +end of February, but I should at least have made some progress on the +documentation for the Carlton and Carlita patterns. + +On a related note, the increasing popularity of this site means I'm a lot more occupied with +various questions, and small issues that need my attention. + +All that feedback is a good thing +for it is how we improve things around here. But I do notice that it is becoming increasingly +difficult to dedicate a larger chunk of time to one specific thing. +Which is really what you need when tackling larger tasks such as writing documentation +or designing new patterns. + +I don't really have a solution for that, I'm just making the observation. + +### Maybe a Blake Blazer release + +I have a jacket pattern on my drawing board that's been there since the summer (it's called the Blake Blazer). +I really should just take out some time to wrap it up and publish it, but +I've been reluctant to do so because I can't seem to find the time to actually make +the jacket. + +I've used the pattern before for +[my refashioners make this year](/blog/the-refashioners-2017/), +but that's not exactly +a very representative example. + +I don't think I'll find the time to make a jacket in February, but perhaps a muslin is enough +to publish it in beta. + +### FOSDEM + +![All details on fosdem.org](https://posts.freesewing.org/uploads/fosdem_bb321397cc.png) + +[FOSDEM](http://fosdem.org/) --- the Free and Open Source Developers' European Meeting --- + is on the first weekend of February in Brussels. + +I'm planning to be there on Sunday, so if you're attending too, let me know or come and say hi. + diff --git a/markdown/org/blog/roundup-2018-01/fr.md b/markdown/org/blog/roundup-2018-01/fr.md new file mode 100644 index 00000000000..fb7fc3862a6 --- /dev/null +++ b/markdown/org/blog/roundup-2018-01/fr.md @@ -0,0 +1,135 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of February" +date: "2018-01-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6fbc797ad0b3d50a8337bd2cb8401f04f63bffdd-2000x1125.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - January 2018: Inkscape DPI, version awareness, Bail, and Carlita [Non traduit]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at January +![More like this month](https://posts.freesewing.org/uploads/coffee_3f501d4076.gif) + +It might be [the record-breaking depressing weather in my neck of the woods +](https://www.theguardian.com/world/2018/jan/19/aint-no-sunshine-winter-darkest-europe), +but I feel like January took a lot out of me. So let's see if we have at least something +to show for it. + +### The Inkscape default units quandary + +At the start of the year, we rolled out core v1.3.0 to address [issue #204](https://github.com/freesewing/core/issues/204) +aka the the Inkscape default units quandary. + +It was a bit of an unusual fix because our hand was forced due to upstream changes made by the +Inkscape developers. In addition, we didn't only have to adapt our code, but also had to backport +the changes to all your existing drafts. + +If you were blissfully unaware of the whole thing, we wrote a blog post about it: +[Freesewing core v1.3.0 is out; Comes with fixes so good that we back-ported them to all your drafts](https://joost.freesewing.org/blog/core-v1.3.0-is-out/). + +### Version awareness + +We now keep track of which version of core generated your draft. We roll out fixes and improvements +all the time. So the drafts you have stored in your profile might be outdated. + +You are now informed about this, both on the draft's page itself and on your list of drafts. +A simple redraft will upgrade them to the latest version. + +> ##### Long-term vision for versioning +> +> This solution is a step up from the previous situation, but it doesn't allow for very +> granular version control. If you have 10 different Simon drafts stored in your profile, and we +> bump the core version number because we made a tweak to Carlton, all your drafts are marked +> as outdated, even though the changes don't impact them. +> +> With only a single core version number to depend on, there's no obvious way for us to keep track +> of what changes impact what pattern. +> +> The long-term plan here is to have a core version number and a pattern version number. +> This way, a version bump in one pattern will not impact other patterns. +> +> A version bump in core will still impact all patterns, but there should be far fewer core versions +> once we take all patterns out of core. +> +> The idea is that every pattern will be in its own repository, and we'll use composer to manage them +> as dependencies. +> +> But this is a long-term idea that won't be implemented until after we rewrite core. +> Yes, that's another long-term idea. + +### Bail for error handling + +In the first half of the month, we tried Rollbar for error handling and reporting. +While we liked the functionality it provided, we weren't too happy about the possible impact on +your privacy of sending that kind of data to a third party. + +So, we decided to write our own poor man's rollbar called Bail. Bail is now used in our data +and core backends, so when things break, we know about it. + +This effort also lead to a 2-week side-quest to write tests for our data backend. All details: +[Introducing freesewing bail: A poor man's rollbar --- because privacy](/blog/introducing-bail/) + +### Carlita is here + +A couple of days ago, we released the [Carlita Coat](/patterns/carlita), +the womenswear version of our Carlton coat. + +If you rushed out to get your hands on Carlita, it's good to know that she was released as +part of core v1.6.0 and we're now at v1.6.3, and that is mostly due to fixes and tweaks in +Carlton/Carlita. + +If you've got an earlier version of the pattern, please redraft. If you've already printed +it, perhaps have a look at [the changelog](https://github.com/freesewing/core/blob/develop/CHANGELOG.md) +to figure out what has changed. + +If you check the changelog, you'll also see that we started the month on core v1.2.9 and +are now running core v1.6.3, so I don't think it's just an idea that it was a busy month. + +## Looking ahead to February + +February is a short month so it's probably best to manage expectations. But here's +what I have in mind for it: + +### Carlton/Carlita documentation + +Quite frankly, this is like pulling teeth to me, so don't expect it to be finished by the +end of February, but I should at least have made some progress on the +documentation for the Carlton and Carlita patterns. + +On a related note, the increasing popularity of this site means I'm a lot more occupied with +various questions, and small issues that need my attention. + +All that feedback is a good thing +for it is how we improve things around here. But I do notice that it is becoming increasingly +difficult to dedicate a larger chunk of time to one specific thing. +Which is really what you need when tackling larger tasks such as writing documentation +or designing new patterns. + +I don't really have a solution for that, I'm just making the observation. + +### Maybe a Blake Blazer release + +I have a jacket pattern on my drawing board that's been there since the summer (it's called the Blake Blazer). +I really should just take out some time to wrap it up and publish it, but +I've been reluctant to do so because I can't seem to find the time to actually make +the jacket. + +I've used the pattern before for +[my refashioners make this year](/blog/the-refashioners-2017/), +but that's not exactly +a very representative example. + +I don't think I'll find the time to make a jacket in February, but perhaps a muslin is enough +to publish it in beta. + +### FOSDEM + +![All details on fosdem.org](https://posts.freesewing.org/uploads/fosdem_bb321397cc.png) + +[FOSDEM](http://fosdem.org/) --- the Free and Open Source Developers' European Meeting --- + is on the first weekend of February in Brussels. + +I'm planning to be there on Sunday, so if you're attending too, let me know or come and say hi. + diff --git a/markdown/org/blog/roundup-2018-01/nl.md b/markdown/org/blog/roundup-2018-01/nl.md new file mode 100644 index 00000000000..6841aef5db3 --- /dev/null +++ b/markdown/org/blog/roundup-2018-01/nl.md @@ -0,0 +1,135 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of February" +date: "2018-01-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6fbc797ad0b3d50a8337bd2cb8401f04f63bffdd-2000x1125.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - January 2018: Inkscape DPI, version awareness, Bail, and Carlita [Niet vertaald]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at January +![More like this month](https://posts.freesewing.org/uploads/coffee_3f501d4076.gif) + +It might be [the record-breaking depressing weather in my neck of the woods +](https://www.theguardian.com/world/2018/jan/19/aint-no-sunshine-winter-darkest-europe), +but I feel like January took a lot out of me. So let's see if we have at least something +to show for it. + +### The Inkscape default units quandary + +At the start of the year, we rolled out core v1.3.0 to address [issue #204](https://github.com/freesewing/core/issues/204) +aka the the Inkscape default units quandary. + +It was a bit of an unusual fix because our hand was forced due to upstream changes made by the +Inkscape developers. In addition, we didn't only have to adapt our code, but also had to backport +the changes to all your existing drafts. + +If you were blissfully unaware of the whole thing, we wrote a blog post about it: +[Freesewing core v1.3.0 is out; Comes with fixes so good that we back-ported them to all your drafts](https://joost.freesewing.org/blog/core-v1.3.0-is-out/). + +### Version awareness + +We now keep track of which version of core generated your draft. We roll out fixes and improvements +all the time. So the drafts you have stored in your profile might be outdated. + +You are now informed about this, both on the draft's page itself and on your list of drafts. +A simple redraft will upgrade them to the latest version. + +> ##### Long-term vision for versioning +> +> This solution is a step up from the previous situation, but it doesn't allow for very +> granular version control. If you have 10 different Simon drafts stored in your profile, and we +> bump the core version number because we made a tweak to Carlton, all your drafts are marked +> as outdated, even though the changes don't impact them. +> +> With only a single core version number to depend on, there's no obvious way for us to keep track +> of what changes impact what pattern. +> +> The long-term plan here is to have a core version number and a pattern version number. +> This way, a version bump in one pattern will not impact other patterns. +> +> A version bump in core will still impact all patterns, but there should be far fewer core versions +> once we take all patterns out of core. +> +> The idea is that every pattern will be in its own repository, and we'll use composer to manage them +> as dependencies. +> +> But this is a long-term idea that won't be implemented until after we rewrite core. +> Yes, that's another long-term idea. + +### Bail for error handling + +In the first half of the month, we tried Rollbar for error handling and reporting. +While we liked the functionality it provided, we weren't too happy about the possible impact on +your privacy of sending that kind of data to a third party. + +So, we decided to write our own poor man's rollbar called Bail. Bail is now used in our data +and core backends, so when things break, we know about it. + +This effort also lead to a 2-week side-quest to write tests for our data backend. All details: +[Introducing freesewing bail: A poor man's rollbar --- because privacy](/blog/introducing-bail/) + +### Carlita is here + +A couple of days ago, we released the [Carlita Coat](/patterns/carlita), +the womenswear version of our Carlton coat. + +If you rushed out to get your hands on Carlita, it's good to know that she was released as +part of core v1.6.0 and we're now at v1.6.3, and that is mostly due to fixes and tweaks in +Carlton/Carlita. + +If you've got an earlier version of the pattern, please redraft. If you've already printed +it, perhaps have a look at [the changelog](https://github.com/freesewing/core/blob/develop/CHANGELOG.md) +to figure out what has changed. + +If you check the changelog, you'll also see that we started the month on core v1.2.9 and +are now running core v1.6.3, so I don't think it's just an idea that it was a busy month. + +## Looking ahead to February + +February is a short month so it's probably best to manage expectations. But here's +what I have in mind for it: + +### Carlton/Carlita documentation + +Quite frankly, this is like pulling teeth to me, so don't expect it to be finished by the +end of February, but I should at least have made some progress on the +documentation for the Carlton and Carlita patterns. + +On a related note, the increasing popularity of this site means I'm a lot more occupied with +various questions, and small issues that need my attention. + +All that feedback is a good thing +for it is how we improve things around here. But I do notice that it is becoming increasingly +difficult to dedicate a larger chunk of time to one specific thing. +Which is really what you need when tackling larger tasks such as writing documentation +or designing new patterns. + +I don't really have a solution for that, I'm just making the observation. + +### Maybe a Blake Blazer release + +I have a jacket pattern on my drawing board that's been there since the summer (it's called the Blake Blazer). +I really should just take out some time to wrap it up and publish it, but +I've been reluctant to do so because I can't seem to find the time to actually make +the jacket. + +I've used the pattern before for +[my refashioners make this year](/blog/the-refashioners-2017/), +but that's not exactly +a very representative example. + +I don't think I'll find the time to make a jacket in February, but perhaps a muslin is enough +to publish it in beta. + +### FOSDEM + +![All details on fosdem.org](https://posts.freesewing.org/uploads/fosdem_bb321397cc.png) + +[FOSDEM](http://fosdem.org/) --- the Free and Open Source Developers' European Meeting --- + is on the first weekend of February in Brussels. + +I'm planning to be there on Sunday, so if you're attending too, let me know or come and say hi. + diff --git a/markdown/org/blog/roundup-2018-02/de.md b/markdown/org/blog/roundup-2018-02/de.md new file mode 100644 index 00000000000..71ef986bd8b --- /dev/null +++ b/markdown/org/blog/roundup-2018-02/de.md @@ -0,0 +1,100 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of March" +date: "2018-02-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8e0079e2521a2bf71545d736a2549180902c0d50-1980x1311.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - February 2018: Core 1.7.0 with Sven, Carlton, and Carlita improvements. Plus GDRP, vim, and Jaeger [Nicht übersetzt]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at February + +I had this secret ambition to release a new pattern every month this year. +It's only February and that plan seems to already have gone off the rails. + +Let's look at the things that did happen in February before we talk about what didn't. + +### Core v1.7.0 is out + +Earlier today, I pulled the trigger on core release 1.7.0. +As usual, [the changelog](https://github.com/freesewing/core/blob/develop/CHANGELOG.md#170) +has all the info, but most significant to users are +[the new ribbing options in the Sven pattern](/docs/patterns/sven/options#ribbing), as well as +a bunch of additional improvements to Carlton/Carlita. + +Those Carlton/Carlita improvements are driven by the fact that myself and [Anneke](/showcase/maker/annekecaramin) +have started to work on [the documentation +for these patterns](/docs/patterns/carlton/). +And every time we write something like *apply fusible interfacing here*, we also go back to the pattern to +mark exactly where this fusible needs to go. + +Needless to say, that's a bunch of work. But it should help with the construction of these coat patterns, +especially for those people for which this is their first time making a coat. + +### GDPR battle plan + +I don't want to make it sound like writing a blog post is an achievement these days, but +I do think [our *GDRP battle plan* blog post](/blog/gdpr-plan) is worth mentioning because +these are important developments, and the workload this generates is significant. + +While nothing is set in stone yet, the post outlines our plan to tackle GDRP-compliance, +something which we'll be focusing on in the next months. + + +### Vim snippets for freesewing core + +In [a blog post that is the embodiment of the term *niche*](/blog/core-vim-snippets) we announced the +availability of a vim plugin that provides freesewing core specific snippets. + +Essentially, IF you want to develop patterns and IF you use the vim editor, these are for you. + +Arguably, that's a lot of ifs. + +### Jaeger sneak preview + +Meet Jaeger, the sports coat pattern that I hoped to release this month. + +![Jaeger is ready, but I haven't made one yet](jaeger.png") + +Those of you with good memories may remember that I mentioned last month that I would +perhaps release this during February. Although back then it still went by a different name. + +As I also foreshadowed last month, I did not find the time +to make one. +As a matter of fact, my most problematic bottle neck in designing new patterns seems to be finding the +time to actually make them. Which is all the more problematic with a pattern as involved as a jacket. +Truth be told, I'm still not sure where I found the time to make that Carlton coat. + +Anyway, all this to say that the pattern is ready, except that I've never made the latest version of it. +And I feel like I can't release it like this. + +So, if you'd like to make a muslin of this --- or even the real thing --- let me know in the +comments, and I'll make sure we'll get you a draft. + +That might also help moving this pattern release forward, for I already know I won't have much time +to work on a jacket next month. + +Speaking of which... + +## Looking ahead to March + +I have two weeks of holiday in March (Yay!) the largest part of which I'll be in Bangkok (more Yay!). + +That means I won't be doing much sewing next month, but there should be some quality time for me and my laptop, +so I wanted to tackle one of the larger items on my mid-term todo-list. + +My initial plan was to rewrite core, you can find some details +[in this ticket on the matter](https://github.com/freesewing/core/issues/236) + +However, looking ahead at the months to come, the most pressing issue is that looming GDPR deadline in May which +will also require a lot of work. + +So, I figured it would make more sense to tackle another thing on the todo list of lofty goals: rewrite the frontend. + +Rather than add yet another pile of jQuery code to handle all the GDPR stuff, the idea is to fork the frontend +and port it to [vue.js](https://vuejs.org/). For this too, [there is an open issue where you can follow its progress](https://github.com/freesewing/site/issues/311). + +Given that I have zero experience with vue.js, this should be fun. If you'd like to help out, please leave a comment. + diff --git a/markdown/org/blog/roundup-2018-02/en.md b/markdown/org/blog/roundup-2018-02/en.md new file mode 100644 index 00000000000..ed564a46444 --- /dev/null +++ b/markdown/org/blog/roundup-2018-02/en.md @@ -0,0 +1,100 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of March" +date: "2018-02-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8e0079e2521a2bf71545d736a2549180902c0d50-1980x1311.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - February 2018: Core 1.7.0 with Sven, Carlton, and Carlita improvements. Plus GDRP, vim, and Jaeger" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at February + +I had this secret ambition to release a new pattern every month this year. +It's only February and that plan seems to already have gone off the rails. + +Let's look at the things that did happen in February before we talk about what didn't. + +### Core v1.7.0 is out + +Earlier today, I pulled the trigger on core release 1.7.0. +As usual, [the changelog](https://github.com/freesewing/core/blob/develop/CHANGELOG.md#170) +has all the info, but most significant to users are +[the new ribbing options in the Sven pattern](/docs/patterns/sven/options#ribbing), as well as +a bunch of additional improvements to Carlton/Carlita. + +Those Carlton/Carlita improvements are driven by the fact that myself and [Anneke](/showcase/maker/annekecaramin) +have started to work on [the documentation +for these patterns](/docs/patterns/carlton/). +And every time we write something like *apply fusible interfacing here*, we also go back to the pattern to +mark exactly where this fusible needs to go. + +Needless to say, that's a bunch of work. But it should help with the construction of these coat patterns, +especially for those people for which this is their first time making a coat. + +### GDPR battle plan + +I don't want to make it sound like writing a blog post is an achievement these days, but +I do think [our *GDRP battle plan* blog post](/blog/gdpr-plan) is worth mentioning because +these are important developments, and the workload this generates is significant. + +While nothing is set in stone yet, the post outlines our plan to tackle GDRP-compliance, +something which we'll be focusing on in the next months. + + +### Vim snippets for freesewing core + +In [a blog post that is the embodiment of the term *niche*](/blog/core-vim-snippets) we announced the +availability of a vim plugin that provides freesewing core specific snippets. + +Essentially, IF you want to develop patterns and IF you use the vim editor, these are for you. + +Arguably, that's a lot of ifs. + +### Jaeger sneak preview + +Meet Jaeger, the sports coat pattern that I hoped to release this month. + +![Jaeger is ready, but I haven't made one yet](jaeger.png") + +Those of you with good memories may remember that I mentioned last month that I would +perhaps release this during February. Although back then it still went by a different name. + +As I also foreshadowed last month, I did not find the time +to make one. +As a matter of fact, my most problematic bottle neck in designing new patterns seems to be finding the +time to actually make them. Which is all the more problematic with a pattern as involved as a jacket. +Truth be told, I'm still not sure where I found the time to make that Carlton coat. + +Anyway, all this to say that the pattern is ready, except that I've never made the latest version of it. +And I feel like I can't release it like this. + +So, if you'd like to make a muslin of this --- or even the real thing --- let me know in the +comments, and I'll make sure we'll get you a draft. + +That might also help moving this pattern release forward, for I already know I won't have much time +to work on a jacket next month. + +Speaking of which... + +## Looking ahead to March + +I have two weeks of holiday in March (Yay!) the largest part of which I'll be in Bangkok (more Yay!). + +That means I won't be doing much sewing next month, but there should be some quality time for me and my laptop, +so I wanted to tackle one of the larger items on my mid-term todo-list. + +My initial plan was to rewrite core, you can find some details +[in this ticket on the matter](https://github.com/freesewing/core/issues/236) + +However, looking ahead at the months to come, the most pressing issue is that looming GDPR deadline in May which +will also require a lot of work. + +So, I figured it would make more sense to tackle another thing on the todo list of lofty goals: rewrite the frontend. + +Rather than add yet another pile of jQuery code to handle all the GDPR stuff, the idea is to fork the frontend +and port it to [vue.js](https://vuejs.org/). For this too, [there is an open issue where you can follow its progress](https://github.com/freesewing/site/issues/311). + +Given that I have zero experience with vue.js, this should be fun. If you'd like to help out, please leave a comment. + diff --git a/markdown/org/blog/roundup-2018-02/es.md b/markdown/org/blog/roundup-2018-02/es.md new file mode 100644 index 00000000000..250df9a3b12 --- /dev/null +++ b/markdown/org/blog/roundup-2018-02/es.md @@ -0,0 +1,100 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of March" +date: "2018-02-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8e0079e2521a2bf71545d736a2549180902c0d50-1980x1311.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - February 2018: Core 1.7.0 with Sven, Carlton, and Carlita improvements. Plus GDRP, vim, and Jaeger [No traducido]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at February + +I had this secret ambition to release a new pattern every month this year. +It's only February and that plan seems to already have gone off the rails. + +Let's look at the things that did happen in February before we talk about what didn't. + +### Core v1.7.0 is out + +Earlier today, I pulled the trigger on core release 1.7.0. +As usual, [the changelog](https://github.com/freesewing/core/blob/develop/CHANGELOG.md#170) +has all the info, but most significant to users are +[the new ribbing options in the Sven pattern](/docs/patterns/sven/options#ribbing), as well as +a bunch of additional improvements to Carlton/Carlita. + +Those Carlton/Carlita improvements are driven by the fact that myself and [Anneke](/showcase/maker/annekecaramin) +have started to work on [the documentation +for these patterns](/docs/patterns/carlton/). +And every time we write something like *apply fusible interfacing here*, we also go back to the pattern to +mark exactly where this fusible needs to go. + +Needless to say, that's a bunch of work. But it should help with the construction of these coat patterns, +especially for those people for which this is their first time making a coat. + +### GDPR battle plan + +I don't want to make it sound like writing a blog post is an achievement these days, but +I do think [our *GDRP battle plan* blog post](/blog/gdpr-plan) is worth mentioning because +these are important developments, and the workload this generates is significant. + +While nothing is set in stone yet, the post outlines our plan to tackle GDRP-compliance, +something which we'll be focusing on in the next months. + + +### Vim snippets for freesewing core + +In [a blog post that is the embodiment of the term *niche*](/blog/core-vim-snippets) we announced the +availability of a vim plugin that provides freesewing core specific snippets. + +Essentially, IF you want to develop patterns and IF you use the vim editor, these are for you. + +Arguably, that's a lot of ifs. + +### Jaeger sneak preview + +Meet Jaeger, the sports coat pattern that I hoped to release this month. + +![Jaeger is ready, but I haven't made one yet](jaeger.png") + +Those of you with good memories may remember that I mentioned last month that I would +perhaps release this during February. Although back then it still went by a different name. + +As I also foreshadowed last month, I did not find the time +to make one. +As a matter of fact, my most problematic bottle neck in designing new patterns seems to be finding the +time to actually make them. Which is all the more problematic with a pattern as involved as a jacket. +Truth be told, I'm still not sure where I found the time to make that Carlton coat. + +Anyway, all this to say that the pattern is ready, except that I've never made the latest version of it. +And I feel like I can't release it like this. + +So, if you'd like to make a muslin of this --- or even the real thing --- let me know in the +comments, and I'll make sure we'll get you a draft. + +That might also help moving this pattern release forward, for I already know I won't have much time +to work on a jacket next month. + +Speaking of which... + +## Looking ahead to March + +I have two weeks of holiday in March (Yay!) the largest part of which I'll be in Bangkok (more Yay!). + +That means I won't be doing much sewing next month, but there should be some quality time for me and my laptop, +so I wanted to tackle one of the larger items on my mid-term todo-list. + +My initial plan was to rewrite core, you can find some details +[in this ticket on the matter](https://github.com/freesewing/core/issues/236) + +However, looking ahead at the months to come, the most pressing issue is that looming GDPR deadline in May which +will also require a lot of work. + +So, I figured it would make more sense to tackle another thing on the todo list of lofty goals: rewrite the frontend. + +Rather than add yet another pile of jQuery code to handle all the GDPR stuff, the idea is to fork the frontend +and port it to [vue.js](https://vuejs.org/). For this too, [there is an open issue where you can follow its progress](https://github.com/freesewing/site/issues/311). + +Given that I have zero experience with vue.js, this should be fun. If you'd like to help out, please leave a comment. + diff --git a/markdown/org/blog/roundup-2018-02/fr.md b/markdown/org/blog/roundup-2018-02/fr.md new file mode 100644 index 00000000000..d51ee2b02bf --- /dev/null +++ b/markdown/org/blog/roundup-2018-02/fr.md @@ -0,0 +1,100 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of March" +date: "2018-02-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8e0079e2521a2bf71545d736a2549180902c0d50-1980x1311.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - February 2018: Core 1.7.0 with Sven, Carlton, and Carlita improvements. Plus GDRP, vim, and Jaeger [Non traduit]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at February + +I had this secret ambition to release a new pattern every month this year. +It's only February and that plan seems to already have gone off the rails. + +Let's look at the things that did happen in February before we talk about what didn't. + +### Core v1.7.0 is out + +Earlier today, I pulled the trigger on core release 1.7.0. +As usual, [the changelog](https://github.com/freesewing/core/blob/develop/CHANGELOG.md#170) +has all the info, but most significant to users are +[the new ribbing options in the Sven pattern](/docs/patterns/sven/options#ribbing), as well as +a bunch of additional improvements to Carlton/Carlita. + +Those Carlton/Carlita improvements are driven by the fact that myself and [Anneke](/showcase/maker/annekecaramin) +have started to work on [the documentation +for these patterns](/docs/patterns/carlton/). +And every time we write something like *apply fusible interfacing here*, we also go back to the pattern to +mark exactly where this fusible needs to go. + +Needless to say, that's a bunch of work. But it should help with the construction of these coat patterns, +especially for those people for which this is their first time making a coat. + +### GDPR battle plan + +I don't want to make it sound like writing a blog post is an achievement these days, but +I do think [our *GDRP battle plan* blog post](/blog/gdpr-plan) is worth mentioning because +these are important developments, and the workload this generates is significant. + +While nothing is set in stone yet, the post outlines our plan to tackle GDRP-compliance, +something which we'll be focusing on in the next months. + + +### Vim snippets for freesewing core + +In [a blog post that is the embodiment of the term *niche*](/blog/core-vim-snippets) we announced the +availability of a vim plugin that provides freesewing core specific snippets. + +Essentially, IF you want to develop patterns and IF you use the vim editor, these are for you. + +Arguably, that's a lot of ifs. + +### Jaeger sneak preview + +Meet Jaeger, the sports coat pattern that I hoped to release this month. + +![Jaeger is ready, but I haven't made one yet](jaeger.png") + +Those of you with good memories may remember that I mentioned last month that I would +perhaps release this during February. Although back then it still went by a different name. + +As I also foreshadowed last month, I did not find the time +to make one. +As a matter of fact, my most problematic bottle neck in designing new patterns seems to be finding the +time to actually make them. Which is all the more problematic with a pattern as involved as a jacket. +Truth be told, I'm still not sure where I found the time to make that Carlton coat. + +Anyway, all this to say that the pattern is ready, except that I've never made the latest version of it. +And I feel like I can't release it like this. + +So, if you'd like to make a muslin of this --- or even the real thing --- let me know in the +comments, and I'll make sure we'll get you a draft. + +That might also help moving this pattern release forward, for I already know I won't have much time +to work on a jacket next month. + +Speaking of which... + +## Looking ahead to March + +I have two weeks of holiday in March (Yay!) the largest part of which I'll be in Bangkok (more Yay!). + +That means I won't be doing much sewing next month, but there should be some quality time for me and my laptop, +so I wanted to tackle one of the larger items on my mid-term todo-list. + +My initial plan was to rewrite core, you can find some details +[in this ticket on the matter](https://github.com/freesewing/core/issues/236) + +However, looking ahead at the months to come, the most pressing issue is that looming GDPR deadline in May which +will also require a lot of work. + +So, I figured it would make more sense to tackle another thing on the todo list of lofty goals: rewrite the frontend. + +Rather than add yet another pile of jQuery code to handle all the GDPR stuff, the idea is to fork the frontend +and port it to [vue.js](https://vuejs.org/). For this too, [there is an open issue where you can follow its progress](https://github.com/freesewing/site/issues/311). + +Given that I have zero experience with vue.js, this should be fun. If you'd like to help out, please leave a comment. + diff --git a/markdown/org/blog/roundup-2018-02/nl.md b/markdown/org/blog/roundup-2018-02/nl.md new file mode 100644 index 00000000000..35555b92638 --- /dev/null +++ b/markdown/org/blog/roundup-2018-02/nl.md @@ -0,0 +1,100 @@ +--- +author: "joostdecock" +caption: "Your new login background for the month of March" +date: "2018-02-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8e0079e2521a2bf71545d736a2549180902c0d50-1980x1311.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - February 2018: Core 1.7.0 with Sven, Carlton, and Carlita improvements. Plus GDRP, vim, and Jaeger [Niet vertaald]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at February + +I had this secret ambition to release a new pattern every month this year. +It's only February and that plan seems to already have gone off the rails. + +Let's look at the things that did happen in February before we talk about what didn't. + +### Core v1.7.0 is out + +Earlier today, I pulled the trigger on core release 1.7.0. +As usual, [the changelog](https://github.com/freesewing/core/blob/develop/CHANGELOG.md#170) +has all the info, but most significant to users are +[the new ribbing options in the Sven pattern](/docs/patterns/sven/options#ribbing), as well as +a bunch of additional improvements to Carlton/Carlita. + +Those Carlton/Carlita improvements are driven by the fact that myself and [Anneke](/showcase/maker/annekecaramin) +have started to work on [the documentation +for these patterns](/docs/patterns/carlton/). +And every time we write something like *apply fusible interfacing here*, we also go back to the pattern to +mark exactly where this fusible needs to go. + +Needless to say, that's a bunch of work. But it should help with the construction of these coat patterns, +especially for those people for which this is their first time making a coat. + +### GDPR battle plan + +I don't want to make it sound like writing a blog post is an achievement these days, but +I do think [our *GDRP battle plan* blog post](/blog/gdpr-plan) is worth mentioning because +these are important developments, and the workload this generates is significant. + +While nothing is set in stone yet, the post outlines our plan to tackle GDRP-compliance, +something which we'll be focusing on in the next months. + + +### Vim snippets for freesewing core + +In [a blog post that is the embodiment of the term *niche*](/blog/core-vim-snippets) we announced the +availability of a vim plugin that provides freesewing core specific snippets. + +Essentially, IF you want to develop patterns and IF you use the vim editor, these are for you. + +Arguably, that's a lot of ifs. + +### Jaeger sneak preview + +Meet Jaeger, the sports coat pattern that I hoped to release this month. + +![Jaeger is ready, but I haven't made one yet](jaeger.png") + +Those of you with good memories may remember that I mentioned last month that I would +perhaps release this during February. Although back then it still went by a different name. + +As I also foreshadowed last month, I did not find the time +to make one. +As a matter of fact, my most problematic bottle neck in designing new patterns seems to be finding the +time to actually make them. Which is all the more problematic with a pattern as involved as a jacket. +Truth be told, I'm still not sure where I found the time to make that Carlton coat. + +Anyway, all this to say that the pattern is ready, except that I've never made the latest version of it. +And I feel like I can't release it like this. + +So, if you'd like to make a muslin of this --- or even the real thing --- let me know in the +comments, and I'll make sure we'll get you a draft. + +That might also help moving this pattern release forward, for I already know I won't have much time +to work on a jacket next month. + +Speaking of which... + +## Looking ahead to March + +I have two weeks of holiday in March (Yay!) the largest part of which I'll be in Bangkok (more Yay!). + +That means I won't be doing much sewing next month, but there should be some quality time for me and my laptop, +so I wanted to tackle one of the larger items on my mid-term todo-list. + +My initial plan was to rewrite core, you can find some details +[in this ticket on the matter](https://github.com/freesewing/core/issues/236) + +However, looking ahead at the months to come, the most pressing issue is that looming GDPR deadline in May which +will also require a lot of work. + +So, I figured it would make more sense to tackle another thing on the todo list of lofty goals: rewrite the frontend. + +Rather than add yet another pile of jQuery code to handle all the GDPR stuff, the idea is to fork the frontend +and port it to [vue.js](https://vuejs.org/). For this too, [there is an open issue where you can follow its progress](https://github.com/freesewing/site/issues/311). + +Given that I have zero experience with vue.js, this should be fun. If you'd like to help out, please leave a comment. + diff --git a/markdown/org/blog/roundup-2018-03/de.md b/markdown/org/blog/roundup-2018-03/de.md new file mode 100644 index 00000000000..c0839fc7f54 --- /dev/null +++ b/markdown/org/blog/roundup-2018-03/de.md @@ -0,0 +1,82 @@ +--- +author: "joostdecock" +caption: "Your login background for April" +date: "2018-03-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/637be1530f8be9387a2be4feac90b92a145b1ddd-1920x1280.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - March 2018: Parlez-vous français? Sprechen Sie Deutsch? ¿Hablas español? 你會說中文嗎？ [Nicht übersetzt]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at March + +As a general rule of thumb, the less you hear from me, the harder I'm working. +Chances are you didn't hear from me during March at all. And yes, that's because I'm working hard. + +Here's why: + +### The Jaeger Jacket is now available + +We've had the new [Jaeger Jacket](/patterns/jaeger) jacket in the pipeline for a while now. +I had stalled a release because I couldn't find the time to make one, something which seems to +be a general problem for pattern releases. + +So, I asked for help and a number of people stepped up and offered to make up (a muslin of) a Jaeger jacket. + +That went well, so a couple of weeks ago we finally pushed out Jaeger for general availability. +It's part of our core 1.8 release, and [the announcement post](/blog/core-1.8-jaeger-across-back/) has all the details. + +### The *across back* measurement is no more + +The across back measurement was cause of a great deal of confusion among our users. +More often than not, when someone contacted us because their pattern looked wonky, +an unrealistic across back measurement was to blame. + +So, we stepped in and removed that measurement in favour of calculating it from the *shoulder to shoulder* +measurement, and giving you a new *across back factor* option so you can still tweak it if you want to. + +For a more detailed description, please refer to [the core 1.8 release blog post](/blog/core-1.8-jaeger-across-back/). + +## Looking ahead to April + +### The big GDPR overhaul + +Last month we [outlined our GDPR battle plan](/blog/gdpr-plan/) and shortly afterwards I made a decision: +Rather than implement all these changes in the site, I would start over from scratch. + +Or rather, I've given myself until the end of April to work on this. At which time I will need to decide +whether it's possible to migrate the entire site before GDPR doomsday (May 25th) or should I abandon this +effort and do what needs to be done in the current site. + +>Rather than implement all these changes in the site, I would start over from scratch. + +I like the first scenario better and have been working on it pretty much day and (part of the) night +during the last couple of weeks. + +I can't really show you much, but the goal is to build the new site on top of +[the Nuxt framework](https://nuxtjs.org/). Doing so would allow us to drop Ruby from the freesewing technology stack, +which would streamline deployment and development. + +My hope is also that using a modern and popular JS frontend framework will make it easier/more attractive +contribute changes to the site. + +### Translators wanted + +Speaking of contributions. Since I'll be rewriting the site from scratch, I've decided to add a new challenge to the mix: i18n. + +In case you're wondering, i18n is short for internationalisation, aka making the site available in different languages. + +Yes, May 25th will be here soon, and yes I need more work like I need another hole in my head. +But I feel it's an important project to try and make freesewing.org available to as many people as possible. +And for this, we need to get rid of the language barrier. + +Now I'm hopeful that I'll be able to take care of the technical aspects of making the site multi-lingual. +But that won't do us any good without translations. So that's where you come in :) + +> #### If you're willing to help with the effort of translating freesewing, please [get in touch](/contact). We need your help. + +It would also help if you could spread the word a bit :) + + + diff --git a/markdown/org/blog/roundup-2018-03/en.md b/markdown/org/blog/roundup-2018-03/en.md new file mode 100644 index 00000000000..96ce8a16a5e --- /dev/null +++ b/markdown/org/blog/roundup-2018-03/en.md @@ -0,0 +1,82 @@ +--- +author: "joostdecock" +caption: "Your login background for April" +date: "2018-03-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/637be1530f8be9387a2be4feac90b92a145b1ddd-1920x1280.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - March 2018: Parlez-vous français? Sprechen Sie Deutsch? ¿Hablas español? 你會說中文嗎？" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at March + +As a general rule of thumb, the less you hear from me, the harder I'm working. +Chances are you didn't hear from me during March at all. And yes, that's because I'm working hard. + +Here's why: + +### The Jaeger Jacket is now available + +We've had the new [Jaeger Jacket](/patterns/jaeger) jacket in the pipeline for a while now. +I had stalled a release because I couldn't find the time to make one, something which seems to +be a general problem for pattern releases. + +So, I asked for help and a number of people stepped up and offered to make up (a muslin of) a Jaeger jacket. + +That went well, so a couple of weeks ago we finally pushed out Jaeger for general availability. +It's part of our core 1.8 release, and [the announcement post](/blog/core-1.8-jaeger-across-back/) has all the details. + +### The *across back* measurement is no more + +The across back measurement was cause of a great deal of confusion among our users. +More often than not, when someone contacted us because their pattern looked wonky, +an unrealistic across back measurement was to blame. + +So, we stepped in and removed that measurement in favour of calculating it from the *shoulder to shoulder* +measurement, and giving you a new *across back factor* option so you can still tweak it if you want to. + +For a more detailed description, please refer to [the core 1.8 release blog post](/blog/core-1.8-jaeger-across-back/). + +## Looking ahead to April + +### The big GDPR overhaul + +Last month we [outlined our GDPR battle plan](/blog/gdpr-plan/) and shortly afterwards I made a decision: +Rather than implement all these changes in the site, I would start over from scratch. + +Or rather, I've given myself until the end of April to work on this. At which time I will need to decide +whether it's possible to migrate the entire site before GDPR doomsday (May 25th) or should I abandon this +effort and do what needs to be done in the current site. + +>Rather than implement all these changes in the site, I would start over from scratch. + +I like the first scenario better and have been working on it pretty much day and (part of the) night +during the last couple of weeks. + +I can't really show you much, but the goal is to build the new site on top of +[the Nuxt framework](https://nuxtjs.org/). Doing so would allow us to drop Ruby from the freesewing technology stack, +which would streamline deployment and development. + +My hope is also that using a modern and popular JS frontend framework will make it easier/more attractive +contribute changes to the site. + +### Translators wanted + +Speaking of contributions. Since I'll be rewriting the site from scratch, I've decided to add a new challenge to the mix: i18n. + +In case you're wondering, i18n is short for internationalisation, aka making the site available in different languages. + +Yes, May 25th will be here soon, and yes I need more work like I need another hole in my head. +But I feel it's an important project to try and make freesewing.org available to as many people as possible. +And for this, we need to get rid of the language barrier. + +Now I'm hopeful that I'll be able to take care of the technical aspects of making the site multi-lingual. +But that won't do us any good without translations. So that's where you come in :) + +> #### If you're willing to help with the effort of translating freesewing, please [get in touch](/contact). We need your help. + +It would also help if you could spread the word a bit :) + + + diff --git a/markdown/org/blog/roundup-2018-03/es.md b/markdown/org/blog/roundup-2018-03/es.md new file mode 100644 index 00000000000..eb3c8b4f794 --- /dev/null +++ b/markdown/org/blog/roundup-2018-03/es.md @@ -0,0 +1,82 @@ +--- +author: "joostdecock" +caption: "Your login background for April" +date: "2018-03-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/637be1530f8be9387a2be4feac90b92a145b1ddd-1920x1280.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - March 2018: Parlez-vous français? Sprechen Sie Deutsch? ¿Hablas español? 你會說中文嗎？ [No traducido]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at March + +As a general rule of thumb, the less you hear from me, the harder I'm working. +Chances are you didn't hear from me during March at all. And yes, that's because I'm working hard. + +Here's why: + +### The Jaeger Jacket is now available + +We've had the new [Jaeger Jacket](/patterns/jaeger) jacket in the pipeline for a while now. +I had stalled a release because I couldn't find the time to make one, something which seems to +be a general problem for pattern releases. + +So, I asked for help and a number of people stepped up and offered to make up (a muslin of) a Jaeger jacket. + +That went well, so a couple of weeks ago we finally pushed out Jaeger for general availability. +It's part of our core 1.8 release, and [the announcement post](/blog/core-1.8-jaeger-across-back/) has all the details. + +### The *across back* measurement is no more + +The across back measurement was cause of a great deal of confusion among our users. +More often than not, when someone contacted us because their pattern looked wonky, +an unrealistic across back measurement was to blame. + +So, we stepped in and removed that measurement in favour of calculating it from the *shoulder to shoulder* +measurement, and giving you a new *across back factor* option so you can still tweak it if you want to. + +For a more detailed description, please refer to [the core 1.8 release blog post](/blog/core-1.8-jaeger-across-back/). + +## Looking ahead to April + +### The big GDPR overhaul + +Last month we [outlined our GDPR battle plan](/blog/gdpr-plan/) and shortly afterwards I made a decision: +Rather than implement all these changes in the site, I would start over from scratch. + +Or rather, I've given myself until the end of April to work on this. At which time I will need to decide +whether it's possible to migrate the entire site before GDPR doomsday (May 25th) or should I abandon this +effort and do what needs to be done in the current site. + +>Rather than implement all these changes in the site, I would start over from scratch. + +I like the first scenario better and have been working on it pretty much day and (part of the) night +during the last couple of weeks. + +I can't really show you much, but the goal is to build the new site on top of +[the Nuxt framework](https://nuxtjs.org/). Doing so would allow us to drop Ruby from the freesewing technology stack, +which would streamline deployment and development. + +My hope is also that using a modern and popular JS frontend framework will make it easier/more attractive +contribute changes to the site. + +### Translators wanted + +Speaking of contributions. Since I'll be rewriting the site from scratch, I've decided to add a new challenge to the mix: i18n. + +In case you're wondering, i18n is short for internationalisation, aka making the site available in different languages. + +Yes, May 25th will be here soon, and yes I need more work like I need another hole in my head. +But I feel it's an important project to try and make freesewing.org available to as many people as possible. +And for this, we need to get rid of the language barrier. + +Now I'm hopeful that I'll be able to take care of the technical aspects of making the site multi-lingual. +But that won't do us any good without translations. So that's where you come in :) + +> #### If you're willing to help with the effort of translating freesewing, please [get in touch](/contact). We need your help. + +It would also help if you could spread the word a bit :) + + + diff --git a/markdown/org/blog/roundup-2018-03/fr.md b/markdown/org/blog/roundup-2018-03/fr.md new file mode 100644 index 00000000000..906c1e39f13 --- /dev/null +++ b/markdown/org/blog/roundup-2018-03/fr.md @@ -0,0 +1,82 @@ +--- +author: "joostdecock" +caption: "Your login background for April" +date: "2018-03-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/637be1530f8be9387a2be4feac90b92a145b1ddd-1920x1280.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - March 2018: Parlez-vous français? Sprechen Sie Deutsch? ¿Hablas español? 你會說中文嗎？ [Non traduit]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at March + +As a general rule of thumb, the less you hear from me, the harder I'm working. +Chances are you didn't hear from me during March at all. And yes, that's because I'm working hard. + +Here's why: + +### The Jaeger Jacket is now available + +We've had the new [Jaeger Jacket](/patterns/jaeger) jacket in the pipeline for a while now. +I had stalled a release because I couldn't find the time to make one, something which seems to +be a general problem for pattern releases. + +So, I asked for help and a number of people stepped up and offered to make up (a muslin of) a Jaeger jacket. + +That went well, so a couple of weeks ago we finally pushed out Jaeger for general availability. +It's part of our core 1.8 release, and [the announcement post](/blog/core-1.8-jaeger-across-back/) has all the details. + +### The *across back* measurement is no more + +The across back measurement was cause of a great deal of confusion among our users. +More often than not, when someone contacted us because their pattern looked wonky, +an unrealistic across back measurement was to blame. + +So, we stepped in and removed that measurement in favour of calculating it from the *shoulder to shoulder* +measurement, and giving you a new *across back factor* option so you can still tweak it if you want to. + +For a more detailed description, please refer to [the core 1.8 release blog post](/blog/core-1.8-jaeger-across-back/). + +## Looking ahead to April + +### The big GDPR overhaul + +Last month we [outlined our GDPR battle plan](/blog/gdpr-plan/) and shortly afterwards I made a decision: +Rather than implement all these changes in the site, I would start over from scratch. + +Or rather, I've given myself until the end of April to work on this. At which time I will need to decide +whether it's possible to migrate the entire site before GDPR doomsday (May 25th) or should I abandon this +effort and do what needs to be done in the current site. + +>Rather than implement all these changes in the site, I would start over from scratch. + +I like the first scenario better and have been working on it pretty much day and (part of the) night +during the last couple of weeks. + +I can't really show you much, but the goal is to build the new site on top of +[the Nuxt framework](https://nuxtjs.org/). Doing so would allow us to drop Ruby from the freesewing technology stack, +which would streamline deployment and development. + +My hope is also that using a modern and popular JS frontend framework will make it easier/more attractive +contribute changes to the site. + +### Translators wanted + +Speaking of contributions. Since I'll be rewriting the site from scratch, I've decided to add a new challenge to the mix: i18n. + +In case you're wondering, i18n is short for internationalisation, aka making the site available in different languages. + +Yes, May 25th will be here soon, and yes I need more work like I need another hole in my head. +But I feel it's an important project to try and make freesewing.org available to as many people as possible. +And for this, we need to get rid of the language barrier. + +Now I'm hopeful that I'll be able to take care of the technical aspects of making the site multi-lingual. +But that won't do us any good without translations. So that's where you come in :) + +> #### If you're willing to help with the effort of translating freesewing, please [get in touch](/contact). We need your help. + +It would also help if you could spread the word a bit :) + + + diff --git a/markdown/org/blog/roundup-2018-03/nl.md b/markdown/org/blog/roundup-2018-03/nl.md new file mode 100644 index 00000000000..68fd957457a --- /dev/null +++ b/markdown/org/blog/roundup-2018-03/nl.md @@ -0,0 +1,82 @@ +--- +author: "joostdecock" +caption: "Your login background for April" +date: "2018-03-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/637be1530f8be9387a2be4feac90b92a145b1ddd-1920x1280.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - March 2018: Parlez-vous français? Sprechen Sie Deutsch? ¿Hablas español? 你會說中文嗎？ [Niet vertaald]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at March + +As a general rule of thumb, the less you hear from me, the harder I'm working. +Chances are you didn't hear from me during March at all. And yes, that's because I'm working hard. + +Here's why: + +### The Jaeger Jacket is now available + +We've had the new [Jaeger Jacket](/patterns/jaeger) jacket in the pipeline for a while now. +I had stalled a release because I couldn't find the time to make one, something which seems to +be a general problem for pattern releases. + +So, I asked for help and a number of people stepped up and offered to make up (a muslin of) a Jaeger jacket. + +That went well, so a couple of weeks ago we finally pushed out Jaeger for general availability. +It's part of our core 1.8 release, and [the announcement post](/blog/core-1.8-jaeger-across-back/) has all the details. + +### The *across back* measurement is no more + +The across back measurement was cause of a great deal of confusion among our users. +More often than not, when someone contacted us because their pattern looked wonky, +an unrealistic across back measurement was to blame. + +So, we stepped in and removed that measurement in favour of calculating it from the *shoulder to shoulder* +measurement, and giving you a new *across back factor* option so you can still tweak it if you want to. + +For a more detailed description, please refer to [the core 1.8 release blog post](/blog/core-1.8-jaeger-across-back/). + +## Looking ahead to April + +### The big GDPR overhaul + +Last month we [outlined our GDPR battle plan](/blog/gdpr-plan/) and shortly afterwards I made a decision: +Rather than implement all these changes in the site, I would start over from scratch. + +Or rather, I've given myself until the end of April to work on this. At which time I will need to decide +whether it's possible to migrate the entire site before GDPR doomsday (May 25th) or should I abandon this +effort and do what needs to be done in the current site. + +>Rather than implement all these changes in the site, I would start over from scratch. + +I like the first scenario better and have been working on it pretty much day and (part of the) night +during the last couple of weeks. + +I can't really show you much, but the goal is to build the new site on top of +[the Nuxt framework](https://nuxtjs.org/). Doing so would allow us to drop Ruby from the freesewing technology stack, +which would streamline deployment and development. + +My hope is also that using a modern and popular JS frontend framework will make it easier/more attractive +contribute changes to the site. + +### Translators wanted + +Speaking of contributions. Since I'll be rewriting the site from scratch, I've decided to add a new challenge to the mix: i18n. + +In case you're wondering, i18n is short for internationalisation, aka making the site available in different languages. + +Yes, May 25th will be here soon, and yes I need more work like I need another hole in my head. +But I feel it's an important project to try and make freesewing.org available to as many people as possible. +And for this, we need to get rid of the language barrier. + +Now I'm hopeful that I'll be able to take care of the technical aspects of making the site multi-lingual. +But that won't do us any good without translations. So that's where you come in :) + +> #### If you're willing to help with the effort of translating freesewing, please [get in touch](/contact). We need your help. + +It would also help if you could spread the word a bit :) + + + diff --git a/markdown/org/blog/roundup-2018-04/de.md b/markdown/org/blog/roundup-2018-04/de.md new file mode 100644 index 00000000000..88cc6782043 --- /dev/null +++ b/markdown/org/blog/roundup-2018-04/de.md @@ -0,0 +1,27 @@ +--- +author: "joostdecock" +caption: "Ihr Login-Hintergrund für Mai" +date: "2018-04-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/992689c621b6b83a80706620ae5cd92262dcf4bd-1920x1273.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monatliche Übersicht - April 2018: Ruhe vor dem Sturm" +--- + + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Rückblick auf April + +Hast du sie bekommen? Alle diese E-Mails, Benachrichtigungen und Popups von Unternehmen, die Sie informieren. dass sie einige Änderungen an ihrer Datenschutzerklärung vorgenommen haben oder wie sie mit Ihren Daten umgehen, und würden Sie bitte diesen Änderungen zustimmen? + +Ich wette, das haben Sie, genau wie ich. Und mit jedem von ihnen werde ich etwas nervöser, wenn die GDPR-Frist am 25. Mai näher rückt, aber ich bin noch nicht bereit, Ihnen eine dieser E-Mails zu schicken. + +Unsere [sorgfältig ausgearbeiteten Pläne](/blog/gdpr-plan/) sind nur ein kleiner Teil der Änderungen, an denen wir arbeiten, und deshalb dauert es etwas länger als erwartet. + +Ich könnte ein wenig mehr darüber schreiben, aber ich habe eine Menge Arbeit zu erledigen und sehr wenig Zeit, um es zu tun. Also, wenn es trotzdem so ist, denke ich, dass ich lieber wieder an die Arbeit gehen möchte. + +## Ausblick auf den Mai + +Erwarten Sie Änderungen. Viele Änderungen. Nichts, worüber man sich Sorgen machen müsste.😉 + + diff --git a/markdown/org/blog/roundup-2018-04/en.md b/markdown/org/blog/roundup-2018-04/en.md new file mode 100644 index 00000000000..a3189c0ff5f --- /dev/null +++ b/markdown/org/blog/roundup-2018-04/en.md @@ -0,0 +1,30 @@ +--- +author: "joostdecock" +caption: "Your login background for May" +date: "2018-04-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/992689c621b6b83a80706620ae5cd92262dcf4bd-1920x1273.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - April 2018: Calm before the storm" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at April + +Did you get them? All those emails, notifications, and popups from companies informing you +that they've made some changes to their privacy policy, or the way they handle your data, +and would you please agree to these changes? + +I bet you did, as did I. And with each one of them, I grow a bit more nervous as the +GDPR deadline of May 25th is approaching, yet I'm not ready yet to send you one of those emails. + +Our [carefully laid plans](/blog/gdpr-plan/) are but a small part of the changes we're working on, +and that's why it's all taking a bit longer than expected. + +I could write a bit more about it, but I've got a ton of work to do and very little time to do it in. +So if it's all the same, I think I'd rather get back to work. + +## Looking ahead to May + +Expect changes. A lot of changes. Nothing to worry about though 😉 + diff --git a/markdown/org/blog/roundup-2018-04/es.md b/markdown/org/blog/roundup-2018-04/es.md new file mode 100644 index 00000000000..b5503ac9ee1 --- /dev/null +++ b/markdown/org/blog/roundup-2018-04/es.md @@ -0,0 +1,30 @@ +--- +author: "joostdecock" +caption: "Your login background for May" +date: "2018-04-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/992689c621b6b83a80706620ae5cd92262dcf4bd-1920x1273.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - April 2018: Calm before the storm [No traducido]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at April + +Did you get them? All those emails, notifications, and popups from companies informing you +that they've made some changes to their privacy policy, or the way they handle your data, +and would you please agree to these changes? + +I bet you did, as did I. And with each one of them, I grow a bit more nervous as the +GDPR deadline of May 25th is approaching, yet I'm not ready yet to send you one of those emails. + +Our [carefully laid plans](/blog/gdpr-plan/) are but a small part of the changes we're working on, +and that's why it's all taking a bit longer than expected. + +I could write a bit more about it, but I've got a ton of work to do and very little time to do it in. +So if it's all the same, I think I'd rather get back to work. + +## Looking ahead to May + +Expect changes. A lot of changes. Nothing to worry about though 😉 + diff --git a/markdown/org/blog/roundup-2018-04/fr.md b/markdown/org/blog/roundup-2018-04/fr.md new file mode 100644 index 00000000000..feff7733ed7 --- /dev/null +++ b/markdown/org/blog/roundup-2018-04/fr.md @@ -0,0 +1,30 @@ +--- +author: "joostdecock" +caption: "Your login background for May" +date: "2018-04-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/992689c621b6b83a80706620ae5cd92262dcf4bd-1920x1273.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - April 2018: Calm before the storm [Non traduit]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at April + +Did you get them? All those emails, notifications, and popups from companies informing you +that they've made some changes to their privacy policy, or the way they handle your data, +and would you please agree to these changes? + +I bet you did, as did I. And with each one of them, I grow a bit more nervous as the +GDPR deadline of May 25th is approaching, yet I'm not ready yet to send you one of those emails. + +Our [carefully laid plans](/blog/gdpr-plan/) are but a small part of the changes we're working on, +and that's why it's all taking a bit longer than expected. + +I could write a bit more about it, but I've got a ton of work to do and very little time to do it in. +So if it's all the same, I think I'd rather get back to work. + +## Looking ahead to May + +Expect changes. A lot of changes. Nothing to worry about though 😉 + diff --git a/markdown/org/blog/roundup-2018-04/nl.md b/markdown/org/blog/roundup-2018-04/nl.md new file mode 100644 index 00000000000..f3d17c4ffef --- /dev/null +++ b/markdown/org/blog/roundup-2018-04/nl.md @@ -0,0 +1,30 @@ +--- +author: "joostdecock" +caption: "Your login background for May" +date: "2018-04-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/992689c621b6b83a80706620ae5cd92262dcf4bd-1920x1273.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - April 2018: Calm before the storm [Niet vertaald]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at April + +Did you get them? All those emails, notifications, and popups from companies informing you +that they've made some changes to their privacy policy, or the way they handle your data, +and would you please agree to these changes? + +I bet you did, as did I. And with each one of them, I grow a bit more nervous as the +GDPR deadline of May 25th is approaching, yet I'm not ready yet to send you one of those emails. + +Our [carefully laid plans](/blog/gdpr-plan/) are but a small part of the changes we're working on, +and that's why it's all taking a bit longer than expected. + +I could write a bit more about it, but I've got a ton of work to do and very little time to do it in. +So if it's all the same, I think I'd rather get back to work. + +## Looking ahead to May + +Expect changes. A lot of changes. Nothing to worry about though 😉 + diff --git a/markdown/org/blog/roundup-2018-05/de.md b/markdown/org/blog/roundup-2018-05/de.md new file mode 100644 index 00000000000..647b7956d1c --- /dev/null +++ b/markdown/org/blog/roundup-2018-05/de.md @@ -0,0 +1,55 @@ +--- +author: "joostdecock" +caption: "Your login background for June" +date: "2018-05-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/63d370c4ad7447d762f2ed053279bc3f11c7583d-1920x1080.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - May 2018: The post-GDPR era is upon us [Nicht übersetzt]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at May + +Well here we are, the GPPR deadline of May 25th is getting smaller and smaller in +our rear-view mirror, and we have a new website. + +Both of those things are obviously related, but you probably [already knew that](/blog/gdpr-ready). + +May has been an incredibly hectic month, with a lot of self-inflicted stress because rather +than just implement the changes required for GDPR, we decided to rebuild the entire site. +However, as the GDPR changes needed to be ready in time, that meant that the entire site had to +be ready. + +*Ready* is obviously open to interpretation, and even though we published the site on time +— with 1.5 hours to spare to be precise — there were still a few loose ends left and right. + +We've fixed a bunch of those and I'd like to thank all of you who reported issues and helped us +fix them by sharing their experience. + +A lot of time and effort has been invested in making the site multi-lingual, and it's been great +to be able to launch with three langauges enabled. All the translators are doing great work +and I hope we'll be able to turn on a few other langauges relatively soon. + +Apart from [open issues](https://github.com/freesewing/site/issues), +we also still have to port some of the documentation to the new site, +which is something that we'll continue to work on in June. Speaking of which: + +## Looking ahead to June + +Don't expect any ground breaking changes in June. We're going to keep on ironing out the +last kinks on the site, and continue to port the remaining documentation that's still +missing from the site. + +I can't — and won't — make any promises and expect other people to keep them, so while I can't +commit to any translation work, great strides are being made in the French and Swedish translations, +so that's all very exciting. + +I'm also thrilled that this translation work is turning out to be a good on-ramp for people +with no prior experience as open source contributors. Not only that, but translators are now +actually fixing small bugs left and right which is really terrific. + +Obviously there's a lot of work that remains to be done, so if you're still standing on the +sidelines wondering whether this is something for you, don't be shy. +[Stop by our chat room to say hello](https://discord.freesewing.org/), we don't bite ☺️ + diff --git a/markdown/org/blog/roundup-2018-05/en.md b/markdown/org/blog/roundup-2018-05/en.md new file mode 100644 index 00000000000..124d8cb221d --- /dev/null +++ b/markdown/org/blog/roundup-2018-05/en.md @@ -0,0 +1,55 @@ +--- +author: "joostdecock" +caption: "Your login background for June" +date: "2018-05-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/63d370c4ad7447d762f2ed053279bc3f11c7583d-1920x1080.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - May 2018: The post-GDPR era is upon us" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at May + +Well here we are, the GPPR deadline of May 25th is getting smaller and smaller in +our rear-view mirror, and we have a new website. + +Both of those things are obviously related, but you probably [already knew that](/blog/gdpr-ready). + +May has been an incredibly hectic month, with a lot of self-inflicted stress because rather +than just implement the changes required for GDPR, we decided to rebuild the entire site. +However, as the GDPR changes needed to be ready in time, that meant that the entire site had to +be ready. + +*Ready* is obviously open to interpretation, and even though we published the site on time +— with 1.5 hours to spare to be precise — there were still a few loose ends left and right. + +We've fixed a bunch of those and I'd like to thank all of you who reported issues and helped us +fix them by sharing their experience. + +A lot of time and effort has been invested in making the site multi-lingual, and it's been great +to be able to launch with three langauges enabled. All the translators are doing great work +and I hope we'll be able to turn on a few other langauges relatively soon. + +Apart from [open issues](https://github.com/freesewing/site/issues), +we also still have to port some of the documentation to the new site, +which is something that we'll continue to work on in June. Speaking of which: + +## Looking ahead to June + +Don't expect any ground breaking changes in June. We're going to keep on ironing out the +last kinks on the site, and continue to port the remaining documentation that's still +missing from the site. + +I can't — and won't — make any promises and expect other people to keep them, so while I can't +commit to any translation work, great strides are being made in the French and Swedish translations, +so that's all very exciting. + +I'm also thrilled that this translation work is turning out to be a good on-ramp for people +with no prior experience as open source contributors. Not only that, but translators are now +actually fixing small bugs left and right which is really terrific. + +Obviously there's a lot of work that remains to be done, so if you're still standing on the +sidelines wondering whether this is something for you, don't be shy. +[Stop by our chat room to say hello](https://discord.freesewing.org/), we don't bite ☺️ + diff --git a/markdown/org/blog/roundup-2018-05/es.md b/markdown/org/blog/roundup-2018-05/es.md new file mode 100644 index 00000000000..70229bf9e0a --- /dev/null +++ b/markdown/org/blog/roundup-2018-05/es.md @@ -0,0 +1,55 @@ +--- +author: "joostdecock" +caption: "Your login background for June" +date: "2018-05-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/63d370c4ad7447d762f2ed053279bc3f11c7583d-1920x1080.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - May 2018: The post-GDPR era is upon us [No traducido]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at May + +Well here we are, the GPPR deadline of May 25th is getting smaller and smaller in +our rear-view mirror, and we have a new website. + +Both of those things are obviously related, but you probably [already knew that](/blog/gdpr-ready). + +May has been an incredibly hectic month, with a lot of self-inflicted stress because rather +than just implement the changes required for GDPR, we decided to rebuild the entire site. +However, as the GDPR changes needed to be ready in time, that meant that the entire site had to +be ready. + +*Ready* is obviously open to interpretation, and even though we published the site on time +— with 1.5 hours to spare to be precise — there were still a few loose ends left and right. + +We've fixed a bunch of those and I'd like to thank all of you who reported issues and helped us +fix them by sharing their experience. + +A lot of time and effort has been invested in making the site multi-lingual, and it's been great +to be able to launch with three langauges enabled. All the translators are doing great work +and I hope we'll be able to turn on a few other langauges relatively soon. + +Apart from [open issues](https://github.com/freesewing/site/issues), +we also still have to port some of the documentation to the new site, +which is something that we'll continue to work on in June. Speaking of which: + +## Looking ahead to June + +Don't expect any ground breaking changes in June. We're going to keep on ironing out the +last kinks on the site, and continue to port the remaining documentation that's still +missing from the site. + +I can't — and won't — make any promises and expect other people to keep them, so while I can't +commit to any translation work, great strides are being made in the French and Swedish translations, +so that's all very exciting. + +I'm also thrilled that this translation work is turning out to be a good on-ramp for people +with no prior experience as open source contributors. Not only that, but translators are now +actually fixing small bugs left and right which is really terrific. + +Obviously there's a lot of work that remains to be done, so if you're still standing on the +sidelines wondering whether this is something for you, don't be shy. +[Stop by our chat room to say hello](https://discord.freesewing.org/), we don't bite ☺️ + diff --git a/markdown/org/blog/roundup-2018-05/fr.md b/markdown/org/blog/roundup-2018-05/fr.md new file mode 100644 index 00000000000..6e826c3f0bd --- /dev/null +++ b/markdown/org/blog/roundup-2018-05/fr.md @@ -0,0 +1,55 @@ +--- +author: "joostdecock" +caption: "Your login background for June" +date: "2018-05-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/63d370c4ad7447d762f2ed053279bc3f11c7583d-1920x1080.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - May 2018: The post-GDPR era is upon us [Non traduit]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at May + +Well here we are, the GPPR deadline of May 25th is getting smaller and smaller in +our rear-view mirror, and we have a new website. + +Both of those things are obviously related, but you probably [already knew that](/blog/gdpr-ready). + +May has been an incredibly hectic month, with a lot of self-inflicted stress because rather +than just implement the changes required for GDPR, we decided to rebuild the entire site. +However, as the GDPR changes needed to be ready in time, that meant that the entire site had to +be ready. + +*Ready* is obviously open to interpretation, and even though we published the site on time +— with 1.5 hours to spare to be precise — there were still a few loose ends left and right. + +We've fixed a bunch of those and I'd like to thank all of you who reported issues and helped us +fix them by sharing their experience. + +A lot of time and effort has been invested in making the site multi-lingual, and it's been great +to be able to launch with three langauges enabled. All the translators are doing great work +and I hope we'll be able to turn on a few other langauges relatively soon. + +Apart from [open issues](https://github.com/freesewing/site/issues), +we also still have to port some of the documentation to the new site, +which is something that we'll continue to work on in June. Speaking of which: + +## Looking ahead to June + +Don't expect any ground breaking changes in June. We're going to keep on ironing out the +last kinks on the site, and continue to port the remaining documentation that's still +missing from the site. + +I can't — and won't — make any promises and expect other people to keep them, so while I can't +commit to any translation work, great strides are being made in the French and Swedish translations, +so that's all very exciting. + +I'm also thrilled that this translation work is turning out to be a good on-ramp for people +with no prior experience as open source contributors. Not only that, but translators are now +actually fixing small bugs left and right which is really terrific. + +Obviously there's a lot of work that remains to be done, so if you're still standing on the +sidelines wondering whether this is something for you, don't be shy. +[Stop by our chat room to say hello](https://discord.freesewing.org/), we don't bite ☺️ + diff --git a/markdown/org/blog/roundup-2018-05/nl.md b/markdown/org/blog/roundup-2018-05/nl.md new file mode 100644 index 00000000000..17dc8446a0c --- /dev/null +++ b/markdown/org/blog/roundup-2018-05/nl.md @@ -0,0 +1,55 @@ +--- +author: "joostdecock" +caption: "Your login background for June" +date: "2018-05-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/63d370c4ad7447d762f2ed053279bc3f11c7583d-1920x1080.jpg" +intro: "This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month." +title: "Monthly roundup - May 2018: The post-GDPR era is upon us [Niet vertaald]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, and a look at what lies ahead in the next month. + +## Looking back at May + +Well here we are, the GPPR deadline of May 25th is getting smaller and smaller in +our rear-view mirror, and we have a new website. + +Both of those things are obviously related, but you probably [already knew that](/blog/gdpr-ready). + +May has been an incredibly hectic month, with a lot of self-inflicted stress because rather +than just implement the changes required for GDPR, we decided to rebuild the entire site. +However, as the GDPR changes needed to be ready in time, that meant that the entire site had to +be ready. + +*Ready* is obviously open to interpretation, and even though we published the site on time +— with 1.5 hours to spare to be precise — there were still a few loose ends left and right. + +We've fixed a bunch of those and I'd like to thank all of you who reported issues and helped us +fix them by sharing their experience. + +A lot of time and effort has been invested in making the site multi-lingual, and it's been great +to be able to launch with three langauges enabled. All the translators are doing great work +and I hope we'll be able to turn on a few other langauges relatively soon. + +Apart from [open issues](https://github.com/freesewing/site/issues), +we also still have to port some of the documentation to the new site, +which is something that we'll continue to work on in June. Speaking of which: + +## Looking ahead to June + +Don't expect any ground breaking changes in June. We're going to keep on ironing out the +last kinks on the site, and continue to port the remaining documentation that's still +missing from the site. + +I can't — and won't — make any promises and expect other people to keep them, so while I can't +commit to any translation work, great strides are being made in the French and Swedish translations, +so that's all very exciting. + +I'm also thrilled that this translation work is turning out to be a good on-ramp for people +with no prior experience as open source contributors. Not only that, but translators are now +actually fixing small bugs left and right which is really terrific. + +Obviously there's a lot of work that remains to be done, so if you're still standing on the +sidelines wondering whether this is something for you, don't be shy. +[Stop by our chat room to say hello](https://discord.freesewing.org/), we don't bite ☺️ + diff --git a/markdown/org/blog/roundup-2018-06/de.md b/markdown/org/blog/roundup-2018-06/de.md new file mode 100644 index 00000000000..8994cd1f04a --- /dev/null +++ b/markdown/org/blog/roundup-2018-06/de.md @@ -0,0 +1,54 @@ +--- +author: "joostdecock" +caption: "Your login background for July" +date: "2018-06-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d4f2c83df7c4bc98b2bee3159b3f042bf0c1177f-1920x1279.jpg" +intro: "Monthly roundup - June 2018: German, Penelope, and more womenswear on the horizon [Nicht übersetzt]" +title: "Monthly roundup - June 2018: German, Penelope, and more womenswear on the horizon [Nicht übersetzt]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at June + +After the mad scramble in May to get the new site ready for the GDPR deadline, +June has (thankfully) been a bit let hectic. + +Not that we haven't been busy. We've resolved a few issues with the new site, +and while there's a few things that still need work, the most pressing issues have been resolved. + +We've also completed the port of the documentation, which was something that was on our +todo-list for June. +It's always nice to make a plan and then follow through on it. + +With the migration demanding less of our time and attention, we've turned our attention +back to building our pattern repository, and just before the end of the month, we were +able to publish the [Penelope Pencil Skirt](/patterns/penelope). + +The pattern was designed by [@woutervdub](/users/woutervdub), it's his second pattern +after he previously made [Benjamin](/patterns/benjamin). + +To make certain the release wouldn't go unnoticed, we asked freesewing's illustrator +[Roy van der Hel](https://www.deviantart.com/royvdhel-art) to drew an illustration +for Penelope, and as always, he nailed it. + +![Fun fact: Roy van der Hel means: Roy from Hel, and that's his real name](penelope.jpg) + +Oh, and I'd almost forgot. The website is now available in German, so +tell your German-speaking friends about it! + +## Looking ahead to July + +As you could read in the [Penelope announcement blog post](/blog/announcing-penelope) we +are planning more womenswear patterns, and that's what our focus will be on in July. + +Some of those plans are more mid-term, but we should be releasing a circle skirt pattern +in July designed by [@AlfaLyr](/users/alfalyr), who also provided much of the Spanish translation +of the site. + +We also started working on a basic bodice block for women, but that will probably take a while +to complete. + +Watch this space. + diff --git a/markdown/org/blog/roundup-2018-06/en.md b/markdown/org/blog/roundup-2018-06/en.md new file mode 100644 index 00000000000..a2bd73d5430 --- /dev/null +++ b/markdown/org/blog/roundup-2018-06/en.md @@ -0,0 +1,54 @@ +--- +author: "joostdecock" +caption: "Your login background for July" +date: "2018-06-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d4f2c83df7c4bc98b2bee3159b3f042bf0c1177f-1920x1279.jpg" +intro: "Monthly roundup - June 2018: German, Penelope, and more womenswear on the horizon" +title: "Monthly roundup - June 2018: German, Penelope, and more womenswear on the horizon" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at June + +After the mad scramble in May to get the new site ready for the GDPR deadline, +June has (thankfully) been a bit let hectic. + +Not that we haven't been busy. We've resolved a few issues with the new site, +and while there's a few things that still need work, the most pressing issues have been resolved. + +We've also completed the port of the documentation, which was something that was on our +todo-list for June. +It's always nice to make a plan and then follow through on it. + +With the migration demanding less of our time and attention, we've turned our attention +back to building our pattern repository, and just before the end of the month, we were +able to publish the [Penelope Pencil Skirt](/patterns/penelope). + +The pattern was designed by [@woutervdub](/users/woutervdub), it's his second pattern +after he previously made [Benjamin](/patterns/benjamin). + +To make certain the release wouldn't go unnoticed, we asked freesewing's illustrator +[Roy van der Hel](https://www.deviantart.com/royvdhel-art) to drew an illustration +for Penelope, and as always, he nailed it. + +![Fun fact: Roy van der Hel means: Roy from Hel, and that's his real name](penelope.jpg) + +Oh, and I'd almost forgot. The website is now available in German, so +tell your German-speaking friends about it! + +## Looking ahead to July + +As you could read in the [Penelope announcement blog post](/blog/announcing-penelope) we +are planning more womenswear patterns, and that's what our focus will be on in July. + +Some of those plans are more mid-term, but we should be releasing a circle skirt pattern +in July designed by [@AlfaLyr](/users/alfalyr), who also provided much of the Spanish translation +of the site. + +We also started working on a basic bodice block for women, but that will probably take a while +to complete. + +Watch this space. + diff --git a/markdown/org/blog/roundup-2018-06/es.md b/markdown/org/blog/roundup-2018-06/es.md new file mode 100644 index 00000000000..dc8f4af98ba --- /dev/null +++ b/markdown/org/blog/roundup-2018-06/es.md @@ -0,0 +1,54 @@ +--- +author: "joostdecock" +caption: "Your login background for July" +date: "2018-06-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d4f2c83df7c4bc98b2bee3159b3f042bf0c1177f-1920x1279.jpg" +intro: "Monthly roundup - June 2018: German, Penelope, and more womenswear on the horizon [No traducido]" +title: "Monthly roundup - June 2018: German, Penelope, and more womenswear on the horizon [No traducido]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at June + +After the mad scramble in May to get the new site ready for the GDPR deadline, +June has (thankfully) been a bit let hectic. + +Not that we haven't been busy. We've resolved a few issues with the new site, +and while there's a few things that still need work, the most pressing issues have been resolved. + +We've also completed the port of the documentation, which was something that was on our +todo-list for June. +It's always nice to make a plan and then follow through on it. + +With the migration demanding less of our time and attention, we've turned our attention +back to building our pattern repository, and just before the end of the month, we were +able to publish the [Penelope Pencil Skirt](/patterns/penelope). + +The pattern was designed by [@woutervdub](/users/woutervdub), it's his second pattern +after he previously made [Benjamin](/patterns/benjamin). + +To make certain the release wouldn't go unnoticed, we asked freesewing's illustrator +[Roy van der Hel](https://www.deviantart.com/royvdhel-art) to drew an illustration +for Penelope, and as always, he nailed it. + +![Fun fact: Roy van der Hel means: Roy from Hel, and that's his real name](penelope.jpg) + +Oh, and I'd almost forgot. The website is now available in German, so +tell your German-speaking friends about it! + +## Looking ahead to July + +As you could read in the [Penelope announcement blog post](/blog/announcing-penelope) we +are planning more womenswear patterns, and that's what our focus will be on in July. + +Some of those plans are more mid-term, but we should be releasing a circle skirt pattern +in July designed by [@AlfaLyr](/users/alfalyr), who also provided much of the Spanish translation +of the site. + +We also started working on a basic bodice block for women, but that will probably take a while +to complete. + +Watch this space. + diff --git a/markdown/org/blog/roundup-2018-06/fr.md b/markdown/org/blog/roundup-2018-06/fr.md new file mode 100644 index 00000000000..d79203a18ff --- /dev/null +++ b/markdown/org/blog/roundup-2018-06/fr.md @@ -0,0 +1,54 @@ +--- +author: "joostdecock" +caption: "Your login background for July" +date: "2018-06-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d4f2c83df7c4bc98b2bee3159b3f042bf0c1177f-1920x1279.jpg" +intro: "Monthly roundup - June 2018: German, Penelope, and more womenswear on the horizon [Non traduit]" +title: "Monthly roundup - June 2018: German, Penelope, and more womenswear on the horizon [Non traduit]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at June + +After the mad scramble in May to get the new site ready for the GDPR deadline, +June has (thankfully) been a bit let hectic. + +Not that we haven't been busy. We've resolved a few issues with the new site, +and while there's a few things that still need work, the most pressing issues have been resolved. + +We've also completed the port of the documentation, which was something that was on our +todo-list for June. +It's always nice to make a plan and then follow through on it. + +With the migration demanding less of our time and attention, we've turned our attention +back to building our pattern repository, and just before the end of the month, we were +able to publish the [Penelope Pencil Skirt](/patterns/penelope). + +The pattern was designed by [@woutervdub](/users/woutervdub), it's his second pattern +after he previously made [Benjamin](/patterns/benjamin). + +To make certain the release wouldn't go unnoticed, we asked freesewing's illustrator +[Roy van der Hel](https://www.deviantart.com/royvdhel-art) to drew an illustration +for Penelope, and as always, he nailed it. + +![Fun fact: Roy van der Hel means: Roy from Hel, and that's his real name](penelope.jpg) + +Oh, and I'd almost forgot. The website is now available in German, so +tell your German-speaking friends about it! + +## Looking ahead to July + +As you could read in the [Penelope announcement blog post](/blog/announcing-penelope) we +are planning more womenswear patterns, and that's what our focus will be on in July. + +Some of those plans are more mid-term, but we should be releasing a circle skirt pattern +in July designed by [@AlfaLyr](/users/alfalyr), who also provided much of the Spanish translation +of the site. + +We also started working on a basic bodice block for women, but that will probably take a while +to complete. + +Watch this space. + diff --git a/markdown/org/blog/roundup-2018-06/nl.md b/markdown/org/blog/roundup-2018-06/nl.md new file mode 100644 index 00000000000..3f1308227dd --- /dev/null +++ b/markdown/org/blog/roundup-2018-06/nl.md @@ -0,0 +1,54 @@ +--- +author: "joostdecock" +caption: "Your login background for July" +date: "2018-06-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d4f2c83df7c4bc98b2bee3159b3f042bf0c1177f-1920x1279.jpg" +intro: "Monthly roundup - June 2018: German, Penelope, and more womenswear on the horizon [Niet vertaald]" +title: "Monthly roundup - June 2018: German, Penelope, and more womenswear on the horizon [Niet vertaald]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at June + +After the mad scramble in May to get the new site ready for the GDPR deadline, +June has (thankfully) been a bit let hectic. + +Not that we haven't been busy. We've resolved a few issues with the new site, +and while there's a few things that still need work, the most pressing issues have been resolved. + +We've also completed the port of the documentation, which was something that was on our +todo-list for June. +It's always nice to make a plan and then follow through on it. + +With the migration demanding less of our time and attention, we've turned our attention +back to building our pattern repository, and just before the end of the month, we were +able to publish the [Penelope Pencil Skirt](/patterns/penelope). + +The pattern was designed by [@woutervdub](/users/woutervdub), it's his second pattern +after he previously made [Benjamin](/patterns/benjamin). + +To make certain the release wouldn't go unnoticed, we asked freesewing's illustrator +[Roy van der Hel](https://www.deviantart.com/royvdhel-art) to drew an illustration +for Penelope, and as always, he nailed it. + +![Fun fact: Roy van der Hel means: Roy from Hel, and that's his real name](penelope.jpg) + +Oh, and I'd almost forgot. The website is now available in German, so +tell your German-speaking friends about it! + +## Looking ahead to July + +As you could read in the [Penelope announcement blog post](/blog/announcing-penelope) we +are planning more womenswear patterns, and that's what our focus will be on in July. + +Some of those plans are more mid-term, but we should be releasing a circle skirt pattern +in July designed by [@AlfaLyr](/users/alfalyr), who also provided much of the Spanish translation +of the site. + +We also started working on a basic bodice block for women, but that will probably take a while +to complete. + +Watch this space. + diff --git a/markdown/org/blog/roundup-2018-07/de.md b/markdown/org/blog/roundup-2018-07/de.md new file mode 100644 index 00000000000..78010e4180d --- /dev/null +++ b/markdown/org/blog/roundup-2018-07/de.md @@ -0,0 +1,39 @@ +--- +author: "joostdecock" +caption: "Your login background for August" +date: "2018-07-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/73ad81c28d5045aeaaebc1e182accac4f93f52eb-1920x1280.jpg" +intro: "Monthly roundup - July 2018: French and waiting for Sandy [Nicht übersetzt]" +title: "Monthly roundup - July 2018: French and waiting for Sandy [Nicht übersetzt]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at July + +It's the summer time, and the heatwave across Europe isn't exactly helping with our productivity. +What I'm saying is: I said we would have a new pattern out in July, but it's going to be late. +We're still waiting for the final artwork, although I can show you the initial sketch now: + +![Meat the Sandy Circle Skirt](https://posts.freesewing.org/uploads/schets_bb8fb5c30a.png) + +This is Sandy, it's a circle skirt pattern, and it will be out in August. Promise :) + +Apart from that, thanks to some great work of [our translators](/i18n/), +we've also enabled our fifth language on the website: [French](/fr). +We've seen an increase in users signing up with .fr email addresses, +so that goes to show that translation really does help make the site accessible to more people. + +Now apart from this, I don't have much to talk about that you can see right here on the site. +That doesn't mean we haven't been busy. Much to the contrary! + +I've started porting freesewing core to node.js. It's really early days so I can't really talk about it too much, but I will do so at a later date. + +## Looking ahead to August + +August will bring the release of Sandy, and we'll also celebrate our first year here at freesewing.org. + +Perhaps that will be a good time to talk about our plans for the future :) + + diff --git a/markdown/org/blog/roundup-2018-07/en.md b/markdown/org/blog/roundup-2018-07/en.md new file mode 100644 index 00000000000..80464eaab02 --- /dev/null +++ b/markdown/org/blog/roundup-2018-07/en.md @@ -0,0 +1,39 @@ +--- +author: "joostdecock" +caption: "Your login background for August" +date: "2018-07-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/73ad81c28d5045aeaaebc1e182accac4f93f52eb-1920x1280.jpg" +intro: "Monthly roundup - July 2018: French and waiting for Sandy" +title: "Monthly roundup - July 2018: French and waiting for Sandy" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at July + +It's the summer time, and the heatwave across Europe isn't exactly helping with our productivity. +What I'm saying is: I said we would have a new pattern out in July, but it's going to be late. +We're still waiting for the final artwork, although I can show you the initial sketch now: + +![Meat the Sandy Circle Skirt](https://posts.freesewing.org/uploads/schets_bb8fb5c30a.png) + +This is Sandy, it's a circle skirt pattern, and it will be out in August. Promise :) + +Apart from that, thanks to some great work of [our translators](/i18n/), +we've also enabled our fifth language on the website: [French](/fr). +We've seen an increase in users signing up with .fr email addresses, +so that goes to show that translation really does help make the site accessible to more people. + +Now apart from this, I don't have much to talk about that you can see right here on the site. +That doesn't mean we haven't been busy. Much to the contrary! + +I've started porting freesewing core to node.js. It's really early days so I can't really talk about it too much, but I will do so at a later date. + +## Looking ahead to August + +August will bring the release of Sandy, and we'll also celebrate our first year here at freesewing.org. + +Perhaps that will be a good time to talk about our plans for the future :) + + diff --git a/markdown/org/blog/roundup-2018-07/es.md b/markdown/org/blog/roundup-2018-07/es.md new file mode 100644 index 00000000000..222ba3d50d2 --- /dev/null +++ b/markdown/org/blog/roundup-2018-07/es.md @@ -0,0 +1,39 @@ +--- +author: "joostdecock" +caption: "Your login background for August" +date: "2018-07-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/73ad81c28d5045aeaaebc1e182accac4f93f52eb-1920x1280.jpg" +intro: "Monthly roundup - July 2018: French and waiting for Sandy [No traducido]" +title: "Monthly roundup - July 2018: French and waiting for Sandy [No traducido]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at July + +It's the summer time, and the heatwave across Europe isn't exactly helping with our productivity. +What I'm saying is: I said we would have a new pattern out in July, but it's going to be late. +We're still waiting for the final artwork, although I can show you the initial sketch now: + +![Meat the Sandy Circle Skirt](https://posts.freesewing.org/uploads/schets_bb8fb5c30a.png) + +This is Sandy, it's a circle skirt pattern, and it will be out in August. Promise :) + +Apart from that, thanks to some great work of [our translators](/i18n/), +we've also enabled our fifth language on the website: [French](/fr). +We've seen an increase in users signing up with .fr email addresses, +so that goes to show that translation really does help make the site accessible to more people. + +Now apart from this, I don't have much to talk about that you can see right here on the site. +That doesn't mean we haven't been busy. Much to the contrary! + +I've started porting freesewing core to node.js. It's really early days so I can't really talk about it too much, but I will do so at a later date. + +## Looking ahead to August + +August will bring the release of Sandy, and we'll also celebrate our first year here at freesewing.org. + +Perhaps that will be a good time to talk about our plans for the future :) + + diff --git a/markdown/org/blog/roundup-2018-07/fr.md b/markdown/org/blog/roundup-2018-07/fr.md new file mode 100644 index 00000000000..a5f9dd554f9 --- /dev/null +++ b/markdown/org/blog/roundup-2018-07/fr.md @@ -0,0 +1,39 @@ +--- +author: "joostdecock" +caption: "Your login background for August" +date: "2018-07-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/73ad81c28d5045aeaaebc1e182accac4f93f52eb-1920x1280.jpg" +intro: "Monthly roundup - July 2018: French and waiting for Sandy [Non traduit]" +title: "Monthly roundup - July 2018: French and waiting for Sandy [Non traduit]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at July + +It's the summer time, and the heatwave across Europe isn't exactly helping with our productivity. +What I'm saying is: I said we would have a new pattern out in July, but it's going to be late. +We're still waiting for the final artwork, although I can show you the initial sketch now: + +![Meat the Sandy Circle Skirt](https://posts.freesewing.org/uploads/schets_bb8fb5c30a.png) + +This is Sandy, it's a circle skirt pattern, and it will be out in August. Promise :) + +Apart from that, thanks to some great work of [our translators](/i18n/), +we've also enabled our fifth language on the website: [French](/fr). +We've seen an increase in users signing up with .fr email addresses, +so that goes to show that translation really does help make the site accessible to more people. + +Now apart from this, I don't have much to talk about that you can see right here on the site. +That doesn't mean we haven't been busy. Much to the contrary! + +I've started porting freesewing core to node.js. It's really early days so I can't really talk about it too much, but I will do so at a later date. + +## Looking ahead to August + +August will bring the release of Sandy, and we'll also celebrate our first year here at freesewing.org. + +Perhaps that will be a good time to talk about our plans for the future :) + + diff --git a/markdown/org/blog/roundup-2018-07/nl.md b/markdown/org/blog/roundup-2018-07/nl.md new file mode 100644 index 00000000000..9bab884b73c --- /dev/null +++ b/markdown/org/blog/roundup-2018-07/nl.md @@ -0,0 +1,39 @@ +--- +author: "joostdecock" +caption: "Your login background for August" +date: "2018-07-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/73ad81c28d5045aeaaebc1e182accac4f93f52eb-1920x1280.jpg" +intro: "Monthly roundup - July 2018: French and waiting for Sandy [Niet vertaald]" +title: "Monthly roundup - July 2018: French and waiting for Sandy [Niet vertaald]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at July + +It's the summer time, and the heatwave across Europe isn't exactly helping with our productivity. +What I'm saying is: I said we would have a new pattern out in July, but it's going to be late. +We're still waiting for the final artwork, although I can show you the initial sketch now: + +![Meat the Sandy Circle Skirt](https://posts.freesewing.org/uploads/schets_bb8fb5c30a.png) + +This is Sandy, it's a circle skirt pattern, and it will be out in August. Promise :) + +Apart from that, thanks to some great work of [our translators](/i18n/), +we've also enabled our fifth language on the website: [French](/fr). +We've seen an increase in users signing up with .fr email addresses, +so that goes to show that translation really does help make the site accessible to more people. + +Now apart from this, I don't have much to talk about that you can see right here on the site. +That doesn't mean we haven't been busy. Much to the contrary! + +I've started porting freesewing core to node.js. It's really early days so I can't really talk about it too much, but I will do so at a later date. + +## Looking ahead to August + +August will bring the release of Sandy, and we'll also celebrate our first year here at freesewing.org. + +Perhaps that will be a good time to talk about our plans for the future :) + + diff --git a/markdown/org/blog/roundup-2018-09/de.md b/markdown/org/blog/roundup-2018-09/de.md new file mode 100644 index 00000000000..4769a378383 --- /dev/null +++ b/markdown/org/blog/roundup-2018-09/de.md @@ -0,0 +1,52 @@ +--- +author: "joostdecock" +caption: "Your login background for October" +date: "2018-09-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b5a652991874d5eb4b6aa694653fcc483330a49d-1920x1280.jpg" +intro: "Monthly roundup - September 2018: Shin, loads of JavaScript, and a long TODO list [Nicht übersetzt]" +title: "Monthly roundup - September 2018: Shin, loads of JavaScript, and a long TODO list [Nicht übersetzt]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at September + +GitHub tells me that I've made 329 commits in 32 repositories during September. +Most of that work is an investment in the future, and it will be a while before you'll +be able to reap the benefits of it. + +But not all, because between all the other stuff, I did find time to release the +[Shin swim trunk pattern](/patterns/shin): + +![Shin are swim trunks that I would qualify as menswear, but I see no reason women can't wear them](cover.jpg) + +### Pics or it didn't happen + +Also new are a bunch of showcases, which is always nice, including this +Jaeger jacket by [Paul](/users/Tiger751023): + +![A Jaeger jacket by Paul](/showcase/linnen-jaeger-by-paul/showcase.jpg) + +If you're making our patterns, please don't hesitate to send in your pictures so we can add some more! + +### Shadow boxing + +All the other work has mostly been JavaScript code as part of our future plans. +I am aware that this kind of work is invisible to most of you (you don't stalk mmy on GitHub, do you?) +and that the perception can be that not much is going on here. + +The opposite is true. I am working harder on this project than ever, but for now it's mostly in the shadows. + +To try shine some light on what's going on, +I have created [a long todo-list](https://github.com/freesewing/todo), +so if you'd like to help out (or if you're just curious what we're up to) go ahead and have a look. + +Note that not all tasks are technical. We also need to pick pretty colors for the new patterns for example. + + +## Looking ahead to October + +I have two weeks of holiday in October, and I have promised myself I would (try to) +put away my laptop and make some clothes. I'm curious to see how that goes. + diff --git a/markdown/org/blog/roundup-2018-09/en.md b/markdown/org/blog/roundup-2018-09/en.md new file mode 100644 index 00000000000..0f5237e433d --- /dev/null +++ b/markdown/org/blog/roundup-2018-09/en.md @@ -0,0 +1,52 @@ +--- +author: "joostdecock" +caption: "Your login background for October" +date: "2018-09-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b5a652991874d5eb4b6aa694653fcc483330a49d-1920x1280.jpg" +intro: "Monthly roundup - September 2018: Shin, loads of JavaScript, and a long TODO list" +title: "Monthly roundup - September 2018: Shin, loads of JavaScript, and a long TODO list" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at September + +GitHub tells me that I've made 329 commits in 32 repositories during September. +Most of that work is an investment in the future, and it will be a while before you'll +be able to reap the benefits of it. + +But not all, because between all the other stuff, I did find time to release the +[Shin swim trunk pattern](/patterns/shin): + +![Shin are swim trunks that I would qualify as menswear, but I see no reason women can't wear them](cover.jpg) + +### Pics or it didn't happen + +Also new are a bunch of showcases, which is always nice, including this +Jaeger jacket by [Paul](/users/Tiger751023): + +![A Jaeger jacket by Paul](/showcase/linnen-jaeger-by-paul/showcase.jpg) + +If you're making our patterns, please don't hesitate to send in your pictures so we can add some more! + +### Shadow boxing + +All the other work has mostly been JavaScript code as part of our future plans. +I am aware that this kind of work is invisible to most of you (you don't stalk mmy on GitHub, do you?) +and that the perception can be that not much is going on here. + +The opposite is true. I am working harder on this project than ever, but for now it's mostly in the shadows. + +To try shine some light on what's going on, +I have created [a long todo-list](https://github.com/freesewing/todo), +so if you'd like to help out (or if you're just curious what we're up to) go ahead and have a look. + +Note that not all tasks are technical. We also need to pick pretty colors for the new patterns for example. + + +## Looking ahead to October + +I have two weeks of holiday in October, and I have promised myself I would (try to) +put away my laptop and make some clothes. I'm curious to see how that goes. + diff --git a/markdown/org/blog/roundup-2018-09/es.md b/markdown/org/blog/roundup-2018-09/es.md new file mode 100644 index 00000000000..9a40a3499bf --- /dev/null +++ b/markdown/org/blog/roundup-2018-09/es.md @@ -0,0 +1,52 @@ +--- +author: "joostdecock" +caption: "Your login background for October" +date: "2018-09-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b5a652991874d5eb4b6aa694653fcc483330a49d-1920x1280.jpg" +intro: "Monthly roundup - September 2018: Shin, loads of JavaScript, and a long TODO list [No traducido]" +title: "Monthly roundup - September 2018: Shin, loads of JavaScript, and a long TODO list [No traducido]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at September + +GitHub tells me that I've made 329 commits in 32 repositories during September. +Most of that work is an investment in the future, and it will be a while before you'll +be able to reap the benefits of it. + +But not all, because between all the other stuff, I did find time to release the +[Shin swim trunk pattern](/patterns/shin): + +![Shin are swim trunks that I would qualify as menswear, but I see no reason women can't wear them](cover.jpg) + +### Pics or it didn't happen + +Also new are a bunch of showcases, which is always nice, including this +Jaeger jacket by [Paul](/users/Tiger751023): + +![A Jaeger jacket by Paul](/showcase/linnen-jaeger-by-paul/showcase.jpg) + +If you're making our patterns, please don't hesitate to send in your pictures so we can add some more! + +### Shadow boxing + +All the other work has mostly been JavaScript code as part of our future plans. +I am aware that this kind of work is invisible to most of you (you don't stalk mmy on GitHub, do you?) +and that the perception can be that not much is going on here. + +The opposite is true. I am working harder on this project than ever, but for now it's mostly in the shadows. + +To try shine some light on what's going on, +I have created [a long todo-list](https://github.com/freesewing/todo), +so if you'd like to help out (or if you're just curious what we're up to) go ahead and have a look. + +Note that not all tasks are technical. We also need to pick pretty colors for the new patterns for example. + + +## Looking ahead to October + +I have two weeks of holiday in October, and I have promised myself I would (try to) +put away my laptop and make some clothes. I'm curious to see how that goes. + diff --git a/markdown/org/blog/roundup-2018-09/fr.md b/markdown/org/blog/roundup-2018-09/fr.md new file mode 100644 index 00000000000..2114bf67e45 --- /dev/null +++ b/markdown/org/blog/roundup-2018-09/fr.md @@ -0,0 +1,52 @@ +--- +author: "joostdecock" +caption: "Your login background for October" +date: "2018-09-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b5a652991874d5eb4b6aa694653fcc483330a49d-1920x1280.jpg" +intro: "Monthly roundup - September 2018: Shin, loads of JavaScript, and a long TODO list [Non traduit]" +title: "Monthly roundup - September 2018: Shin, loads of JavaScript, and a long TODO list [Non traduit]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at September + +GitHub tells me that I've made 329 commits in 32 repositories during September. +Most of that work is an investment in the future, and it will be a while before you'll +be able to reap the benefits of it. + +But not all, because between all the other stuff, I did find time to release the +[Shin swim trunk pattern](/patterns/shin): + +![Shin are swim trunks that I would qualify as menswear, but I see no reason women can't wear them](cover.jpg) + +### Pics or it didn't happen + +Also new are a bunch of showcases, which is always nice, including this +Jaeger jacket by [Paul](/users/Tiger751023): + +![A Jaeger jacket by Paul](/showcase/linnen-jaeger-by-paul/showcase.jpg) + +If you're making our patterns, please don't hesitate to send in your pictures so we can add some more! + +### Shadow boxing + +All the other work has mostly been JavaScript code as part of our future plans. +I am aware that this kind of work is invisible to most of you (you don't stalk mmy on GitHub, do you?) +and that the perception can be that not much is going on here. + +The opposite is true. I am working harder on this project than ever, but for now it's mostly in the shadows. + +To try shine some light on what's going on, +I have created [a long todo-list](https://github.com/freesewing/todo), +so if you'd like to help out (or if you're just curious what we're up to) go ahead and have a look. + +Note that not all tasks are technical. We also need to pick pretty colors for the new patterns for example. + + +## Looking ahead to October + +I have two weeks of holiday in October, and I have promised myself I would (try to) +put away my laptop and make some clothes. I'm curious to see how that goes. + diff --git a/markdown/org/blog/roundup-2018-09/nl.md b/markdown/org/blog/roundup-2018-09/nl.md new file mode 100644 index 00000000000..a32681547a6 --- /dev/null +++ b/markdown/org/blog/roundup-2018-09/nl.md @@ -0,0 +1,52 @@ +--- +author: "joostdecock" +caption: "Your login background for October" +date: "2018-09-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b5a652991874d5eb4b6aa694653fcc483330a49d-1920x1280.jpg" +intro: "Monthly roundup - September 2018: Shin, loads of JavaScript, and a long TODO list [Niet vertaald]" +title: "Monthly roundup - September 2018: Shin, loads of JavaScript, and a long TODO list [Niet vertaald]" +--- + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at September + +GitHub tells me that I've made 329 commits in 32 repositories during September. +Most of that work is an investment in the future, and it will be a while before you'll +be able to reap the benefits of it. + +But not all, because between all the other stuff, I did find time to release the +[Shin swim trunk pattern](/patterns/shin): + +![Shin are swim trunks that I would qualify as menswear, but I see no reason women can't wear them](cover.jpg) + +### Pics or it didn't happen + +Also new are a bunch of showcases, which is always nice, including this +Jaeger jacket by [Paul](/users/Tiger751023): + +![A Jaeger jacket by Paul](/showcase/linnen-jaeger-by-paul/showcase.jpg) + +If you're making our patterns, please don't hesitate to send in your pictures so we can add some more! + +### Shadow boxing + +All the other work has mostly been JavaScript code as part of our future plans. +I am aware that this kind of work is invisible to most of you (you don't stalk mmy on GitHub, do you?) +and that the perception can be that not much is going on here. + +The opposite is true. I am working harder on this project than ever, but for now it's mostly in the shadows. + +To try shine some light on what's going on, +I have created [a long todo-list](https://github.com/freesewing/todo), +so if you'd like to help out (or if you're just curious what we're up to) go ahead and have a look. + +Note that not all tasks are technical. We also need to pick pretty colors for the new patterns for example. + + +## Looking ahead to October + +I have two weeks of holiday in October, and I have promised myself I would (try to) +put away my laptop and make some clothes. I'm curious to see how that goes. + diff --git a/markdown/org/blog/roundup-2018-10/de.md b/markdown/org/blog/roundup-2018-10/de.md new file mode 100644 index 00000000000..6a14bc707ee --- /dev/null +++ b/markdown/org/blog/roundup-2018-10/de.md @@ -0,0 +1,43 @@ +--- +author: "joostdecock" +caption: "Your login background for November" +date: "2018-11-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5be11786eaed9bba641fa66b812a3fc9f68aed1d-1920x1410.jpg" +intro: "Monthly roundup - October 2018: Progress on beta.freesewing.org [Nicht übersetzt]" +title: "Monthly roundup - October 2018: Progress on beta.freesewing.org [Nicht übersetzt]" +--- + + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at October + +Skeletons pack up their rattling chains, and your *sexy Brett Kavanaugh* costume +has found a new home in the attic. This can only mean one thing: Halloween is over, +here comes November. + +I am currently under the influence of influenza, so pardon me if I keep this short. + +What I can tell you about October is that a lot of work has been done, and while it's not +always obvious to somehow showcase this behind-the-scenes work, +[our beta website](https://beta.freesewing.org/) is +slowly starting to gain more and more features. + +Not that we're anything close to finishing it. But you can login with your current freesewing +username and password. Which means that we've successfully migrated all our data to our new backend. + +It's baby steps, but with each passing day, and each line of code written, we get a little closer +to where we want to go. + +## Looking ahead to November + +In early December we traditionally do our yearly roundup, which means that November is kind of +that last month we have to come up with something to show off. + +I've somehow made peace with the fact that things won't be nearly as ready as I'd like them to be. +But on the other hand, I am still excited about all the work we are doing/have been doing, so +hopefully that will shine through regardless of whether we can show you much or not. + +Now if you don't mind, I'll get back to tea and tissues. + diff --git a/markdown/org/blog/roundup-2018-10/en.md b/markdown/org/blog/roundup-2018-10/en.md new file mode 100644 index 00000000000..8619f1eb3db --- /dev/null +++ b/markdown/org/blog/roundup-2018-10/en.md @@ -0,0 +1,43 @@ +--- +author: "joostdecock" +caption: "Your login background for November" +date: "2018-11-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5be11786eaed9bba641fa66b812a3fc9f68aed1d-1920x1410.jpg" +intro: "Monthly roundup - October 2018: Progress on beta.freesewing.org" +title: "Monthly roundup - October 2018: Progress on beta.freesewing.org" +--- + + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at October + +Skeletons pack up their rattling chains, and your *sexy Brett Kavanaugh* costume +has found a new home in the attic. This can only mean one thing: Halloween is over, +here comes November. + +I am currently under the influence of influenza, so pardon me if I keep this short. + +What I can tell you about October is that a lot of work has been done, and while it's not +always obvious to somehow showcase this behind-the-scenes work, +[our beta website](https://beta.freesewing.org/) is +slowly starting to gain more and more features. + +Not that we're anything close to finishing it. But you can login with your current freesewing +username and password. Which means that we've successfully migrated all our data to our new backend. + +It's baby steps, but with each passing day, and each line of code written, we get a little closer +to where we want to go. + +## Looking ahead to November + +In early December we traditionally do our yearly roundup, which means that November is kind of +that last month we have to come up with something to show off. + +I've somehow made peace with the fact that things won't be nearly as ready as I'd like them to be. +But on the other hand, I am still excited about all the work we are doing/have been doing, so +hopefully that will shine through regardless of whether we can show you much or not. + +Now if you don't mind, I'll get back to tea and tissues. + diff --git a/markdown/org/blog/roundup-2018-10/es.md b/markdown/org/blog/roundup-2018-10/es.md new file mode 100644 index 00000000000..efbc3d197c0 --- /dev/null +++ b/markdown/org/blog/roundup-2018-10/es.md @@ -0,0 +1,43 @@ +--- +author: "joostdecock" +caption: "Your login background for November" +date: "2018-11-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5be11786eaed9bba641fa66b812a3fc9f68aed1d-1920x1410.jpg" +intro: "Monthly roundup - October 2018: Progress on beta.freesewing.org [No traducido]" +title: "Monthly roundup - October 2018: Progress on beta.freesewing.org [No traducido]" +--- + + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at October + +Skeletons pack up their rattling chains, and your *sexy Brett Kavanaugh* costume +has found a new home in the attic. This can only mean one thing: Halloween is over, +here comes November. + +I am currently under the influence of influenza, so pardon me if I keep this short. + +What I can tell you about October is that a lot of work has been done, and while it's not +always obvious to somehow showcase this behind-the-scenes work, +[our beta website](https://beta.freesewing.org/) is +slowly starting to gain more and more features. + +Not that we're anything close to finishing it. But you can login with your current freesewing +username and password. Which means that we've successfully migrated all our data to our new backend. + +It's baby steps, but with each passing day, and each line of code written, we get a little closer +to where we want to go. + +## Looking ahead to November + +In early December we traditionally do our yearly roundup, which means that November is kind of +that last month we have to come up with something to show off. + +I've somehow made peace with the fact that things won't be nearly as ready as I'd like them to be. +But on the other hand, I am still excited about all the work we are doing/have been doing, so +hopefully that will shine through regardless of whether we can show you much or not. + +Now if you don't mind, I'll get back to tea and tissues. + diff --git a/markdown/org/blog/roundup-2018-10/fr.md b/markdown/org/blog/roundup-2018-10/fr.md new file mode 100644 index 00000000000..4ad8d701d2a --- /dev/null +++ b/markdown/org/blog/roundup-2018-10/fr.md @@ -0,0 +1,43 @@ +--- +author: "joostdecock" +caption: "Your login background for November" +date: "2018-11-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5be11786eaed9bba641fa66b812a3fc9f68aed1d-1920x1410.jpg" +intro: "Monthly roundup - October 2018: Progress on beta.freesewing.org [Non traduit]" +title: "Monthly roundup - October 2018: Progress on beta.freesewing.org [Non traduit]" +--- + + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at October + +Skeletons pack up their rattling chains, and your *sexy Brett Kavanaugh* costume +has found a new home in the attic. This can only mean one thing: Halloween is over, +here comes November. + +I am currently under the influence of influenza, so pardon me if I keep this short. + +What I can tell you about October is that a lot of work has been done, and while it's not +always obvious to somehow showcase this behind-the-scenes work, +[our beta website](https://beta.freesewing.org/) is +slowly starting to gain more and more features. + +Not that we're anything close to finishing it. But you can login with your current freesewing +username and password. Which means that we've successfully migrated all our data to our new backend. + +It's baby steps, but with each passing day, and each line of code written, we get a little closer +to where we want to go. + +## Looking ahead to November + +In early December we traditionally do our yearly roundup, which means that November is kind of +that last month we have to come up with something to show off. + +I've somehow made peace with the fact that things won't be nearly as ready as I'd like them to be. +But on the other hand, I am still excited about all the work we are doing/have been doing, so +hopefully that will shine through regardless of whether we can show you much or not. + +Now if you don't mind, I'll get back to tea and tissues. + diff --git a/markdown/org/blog/roundup-2018-10/nl.md b/markdown/org/blog/roundup-2018-10/nl.md new file mode 100644 index 00000000000..2ef07c0e453 --- /dev/null +++ b/markdown/org/blog/roundup-2018-10/nl.md @@ -0,0 +1,43 @@ +--- +author: "joostdecock" +caption: "Your login background for November" +date: "2018-11-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5be11786eaed9bba641fa66b812a3fc9f68aed1d-1920x1410.jpg" +intro: "Monthly roundup - October 2018: Progress on beta.freesewing.org [Niet vertaald]" +title: "Monthly roundup - October 2018: Progress on beta.freesewing.org [Niet vertaald]" +--- + + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at October + +Skeletons pack up their rattling chains, and your *sexy Brett Kavanaugh* costume +has found a new home in the attic. This can only mean one thing: Halloween is over, +here comes November. + +I am currently under the influence of influenza, so pardon me if I keep this short. + +What I can tell you about October is that a lot of work has been done, and while it's not +always obvious to somehow showcase this behind-the-scenes work, +[our beta website](https://beta.freesewing.org/) is +slowly starting to gain more and more features. + +Not that we're anything close to finishing it. But you can login with your current freesewing +username and password. Which means that we've successfully migrated all our data to our new backend. + +It's baby steps, but with each passing day, and each line of code written, we get a little closer +to where we want to go. + +## Looking ahead to November + +In early December we traditionally do our yearly roundup, which means that November is kind of +that last month we have to come up with something to show off. + +I've somehow made peace with the fact that things won't be nearly as ready as I'd like them to be. +But on the other hand, I am still excited about all the work we are doing/have been doing, so +hopefully that will shine through regardless of whether we can show you much or not. + +Now if you don't mind, I'll get back to tea and tissues. + diff --git a/markdown/org/blog/roundup-2018-11/de.md b/markdown/org/blog/roundup-2018-11/de.md new file mode 100644 index 00000000000..edcf6797c5e --- /dev/null +++ b/markdown/org/blog/roundup-2018-11/de.md @@ -0,0 +1,52 @@ +--- +author: "joostdecock" +caption: "Your login background for December" +date: "2018-11-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ebdb5fce7cd9b56f2f9d51d05dbda187195e30b6-1920x1280.jpg" +intro: "Monthly roundup - November 2018: New showcases and a (false) security alarm [Nicht übersetzt]" +title: "Monthly roundup - November 2018: New showcases and a (false) security alarm [Nicht übersetzt]" +--- + + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at November + +I have been very busy this month, but more about that in our roundup post for the year +which you can expect on December 10th. + +Because I've been busy, a few showcase posts had fallen through the cracks. +I've cleared the backlog in my inbox now, and as a result we have +[a new Bruce showcase by Felix](/en/showcase/bruce-three-pack) and +[a new Sandy showcase by Karin](/en/showcase/sandy-by-karin). + +If you've made one of our patterns, make sure to send in your pictures +so we can add them too. I mean, even if it takes a while, I do eventually +get around to it :) + + +Earlier this week, I woke to the unsettling news that a popular package on +NPM [had been hijacked by malicious actors](https://arstechnica.com/information-technology/2018/11/hacker-backdoors-widely-used-open-source-software-to-steal-bitcoin/). + +That's obviously shitty behaviour, but the fact that this package is a dependency +of our backend (as in, we use it) made for a rude awakening. +Our backend was patched by the time I got to work (yay for trains), but as more information +came to light, it turned out it was never a problem in the first place. + +For one thing, the dependency was a so-called development dependency. Code that is included +while developing, but not included in the production build. + +Furthermore, the malicious actors were targetting a very specific set of people in order +to make off with their bitcoin, so there was never an issue. + +As the story was developing, we +[posted updates on Twitter](https://twitter.com/freesewing_org/status/1067312509672177664) +so if you want to make sure you want to hear all the latest news, make sure to follow +[@freesewing_org](https://twitter.com/freesewing_org) on Twitter. + + +## Looking ahead to December + +In early December we traditionally do our yearly roundup, so more on that soon :) + diff --git a/markdown/org/blog/roundup-2018-11/en.md b/markdown/org/blog/roundup-2018-11/en.md new file mode 100644 index 00000000000..8ecb6ae5291 --- /dev/null +++ b/markdown/org/blog/roundup-2018-11/en.md @@ -0,0 +1,52 @@ +--- +author: "joostdecock" +caption: "Your login background for December" +date: "2018-11-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ebdb5fce7cd9b56f2f9d51d05dbda187195e30b6-1920x1280.jpg" +intro: "Monthly roundup - November 2018: New showcases and a (false) security alarm" +title: "Monthly roundup - November 2018: New showcases and a (false) security alarm" +--- + + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at November + +I have been very busy this month, but more about that in our roundup post for the year +which you can expect on December 10th. + +Because I've been busy, a few showcase posts had fallen through the cracks. +I've cleared the backlog in my inbox now, and as a result we have +[a new Bruce showcase by Felix](/en/showcase/bruce-three-pack) and +[a new Sandy showcase by Karin](/en/showcase/sandy-by-karin). + +If you've made one of our patterns, make sure to send in your pictures +so we can add them too. I mean, even if it takes a while, I do eventually +get around to it :) + + +Earlier this week, I woke to the unsettling news that a popular package on +NPM [had been hijacked by malicious actors](https://arstechnica.com/information-technology/2018/11/hacker-backdoors-widely-used-open-source-software-to-steal-bitcoin/). + +That's obviously shitty behaviour, but the fact that this package is a dependency +of our backend (as in, we use it) made for a rude awakening. +Our backend was patched by the time I got to work (yay for trains), but as more information +came to light, it turned out it was never a problem in the first place. + +For one thing, the dependency was a so-called development dependency. Code that is included +while developing, but not included in the production build. + +Furthermore, the malicious actors were targetting a very specific set of people in order +to make off with their bitcoin, so there was never an issue. + +As the story was developing, we +[posted updates on Twitter](https://twitter.com/freesewing_org/status/1067312509672177664) +so if you want to make sure you want to hear all the latest news, make sure to follow +[@freesewing_org](https://twitter.com/freesewing_org) on Twitter. + + +## Looking ahead to December + +In early December we traditionally do our yearly roundup, so more on that soon :) + diff --git a/markdown/org/blog/roundup-2018-11/es.md b/markdown/org/blog/roundup-2018-11/es.md new file mode 100644 index 00000000000..328545484ee --- /dev/null +++ b/markdown/org/blog/roundup-2018-11/es.md @@ -0,0 +1,52 @@ +--- +author: "joostdecock" +caption: "Your login background for December" +date: "2018-11-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ebdb5fce7cd9b56f2f9d51d05dbda187195e30b6-1920x1280.jpg" +intro: "Monthly roundup - November 2018: New showcases and a (false) security alarm [No traducido]" +title: "Monthly roundup - November 2018: New showcases and a (false) security alarm [No traducido]" +--- + + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at November + +I have been very busy this month, but more about that in our roundup post for the year +which you can expect on December 10th. + +Because I've been busy, a few showcase posts had fallen through the cracks. +I've cleared the backlog in my inbox now, and as a result we have +[a new Bruce showcase by Felix](/en/showcase/bruce-three-pack) and +[a new Sandy showcase by Karin](/en/showcase/sandy-by-karin). + +If you've made one of our patterns, make sure to send in your pictures +so we can add them too. I mean, even if it takes a while, I do eventually +get around to it :) + + +Earlier this week, I woke to the unsettling news that a popular package on +NPM [had been hijacked by malicious actors](https://arstechnica.com/information-technology/2018/11/hacker-backdoors-widely-used-open-source-software-to-steal-bitcoin/). + +That's obviously shitty behaviour, but the fact that this package is a dependency +of our backend (as in, we use it) made for a rude awakening. +Our backend was patched by the time I got to work (yay for trains), but as more information +came to light, it turned out it was never a problem in the first place. + +For one thing, the dependency was a so-called development dependency. Code that is included +while developing, but not included in the production build. + +Furthermore, the malicious actors were targetting a very specific set of people in order +to make off with their bitcoin, so there was never an issue. + +As the story was developing, we +[posted updates on Twitter](https://twitter.com/freesewing_org/status/1067312509672177664) +so if you want to make sure you want to hear all the latest news, make sure to follow +[@freesewing_org](https://twitter.com/freesewing_org) on Twitter. + + +## Looking ahead to December + +In early December we traditionally do our yearly roundup, so more on that soon :) + diff --git a/markdown/org/blog/roundup-2018-11/fr.md b/markdown/org/blog/roundup-2018-11/fr.md new file mode 100644 index 00000000000..e4fdf4ccd4d --- /dev/null +++ b/markdown/org/blog/roundup-2018-11/fr.md @@ -0,0 +1,52 @@ +--- +author: "joostdecock" +caption: "Your login background for December" +date: "2018-11-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ebdb5fce7cd9b56f2f9d51d05dbda187195e30b6-1920x1280.jpg" +intro: "Monthly roundup - November 2018: New showcases and a (false) security alarm [Non traduit]" +title: "Monthly roundup - November 2018: New showcases and a (false) security alarm [Non traduit]" +--- + + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at November + +I have been very busy this month, but more about that in our roundup post for the year +which you can expect on December 10th. + +Because I've been busy, a few showcase posts had fallen through the cracks. +I've cleared the backlog in my inbox now, and as a result we have +[a new Bruce showcase by Felix](/en/showcase/bruce-three-pack) and +[a new Sandy showcase by Karin](/en/showcase/sandy-by-karin). + +If you've made one of our patterns, make sure to send in your pictures +so we can add them too. I mean, even if it takes a while, I do eventually +get around to it :) + + +Earlier this week, I woke to the unsettling news that a popular package on +NPM [had been hijacked by malicious actors](https://arstechnica.com/information-technology/2018/11/hacker-backdoors-widely-used-open-source-software-to-steal-bitcoin/). + +That's obviously shitty behaviour, but the fact that this package is a dependency +of our backend (as in, we use it) made for a rude awakening. +Our backend was patched by the time I got to work (yay for trains), but as more information +came to light, it turned out it was never a problem in the first place. + +For one thing, the dependency was a so-called development dependency. Code that is included +while developing, but not included in the production build. + +Furthermore, the malicious actors were targetting a very specific set of people in order +to make off with their bitcoin, so there was never an issue. + +As the story was developing, we +[posted updates on Twitter](https://twitter.com/freesewing_org/status/1067312509672177664) +so if you want to make sure you want to hear all the latest news, make sure to follow +[@freesewing_org](https://twitter.com/freesewing_org) on Twitter. + + +## Looking ahead to December + +In early December we traditionally do our yearly roundup, so more on that soon :) + diff --git a/markdown/org/blog/roundup-2018-11/nl.md b/markdown/org/blog/roundup-2018-11/nl.md new file mode 100644 index 00000000000..2ea5cb42964 --- /dev/null +++ b/markdown/org/blog/roundup-2018-11/nl.md @@ -0,0 +1,52 @@ +--- +author: "joostdecock" +caption: "Your login background for December" +date: "2018-11-30" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ebdb5fce7cd9b56f2f9d51d05dbda187195e30b6-1920x1280.jpg" +intro: "Monthly roundup - November 2018: New showcases and a (false) security alarm [Niet vertaald]" +title: "Monthly roundup - November 2018: New showcases and a (false) security alarm [Niet vertaald]" +--- + + +This is your monthly roundup of the freesewing news of the last four weeks, +and a look at what lies ahead in the next month. + +## Looking back at November + +I have been very busy this month, but more about that in our roundup post for the year +which you can expect on December 10th. + +Because I've been busy, a few showcase posts had fallen through the cracks. +I've cleared the backlog in my inbox now, and as a result we have +[a new Bruce showcase by Felix](/en/showcase/bruce-three-pack) and +[a new Sandy showcase by Karin](/en/showcase/sandy-by-karin). + +If you've made one of our patterns, make sure to send in your pictures +so we can add them too. I mean, even if it takes a while, I do eventually +get around to it :) + + +Earlier this week, I woke to the unsettling news that a popular package on +NPM [had been hijacked by malicious actors](https://arstechnica.com/information-technology/2018/11/hacker-backdoors-widely-used-open-source-software-to-steal-bitcoin/). + +That's obviously shitty behaviour, but the fact that this package is a dependency +of our backend (as in, we use it) made for a rude awakening. +Our backend was patched by the time I got to work (yay for trains), but as more information +came to light, it turned out it was never a problem in the first place. + +For one thing, the dependency was a so-called development dependency. Code that is included +while developing, but not included in the production build. + +Furthermore, the malicious actors were targetting a very specific set of people in order +to make off with their bitcoin, so there was never an issue. + +As the story was developing, we +[posted updates on Twitter](https://twitter.com/freesewing_org/status/1067312509672177664) +so if you want to make sure you want to hear all the latest news, make sure to follow +[@freesewing_org](https://twitter.com/freesewing_org) on Twitter. + + +## Looking ahead to December + +In early December we traditionally do our yearly roundup, so more on that soon :) + diff --git a/markdown/org/blog/roundup-2019-01/de.md b/markdown/org/blog/roundup-2019-01/de.md new file mode 100644 index 00000000000..3c3a9461a93 --- /dev/null +++ b/markdown/org/blog/roundup-2019-01/de.md @@ -0,0 +1,144 @@ +--- +author: "joostdecock" +caption: "Your login background for February" +date: "2019-01-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/26bf3d41513702ad361b5a0f15dcff2350cc852b-1920x1440.jpg" +intro: "Is it really the end of January? Already?" +title: "Monthly roundup - January 2019: The big beta update [Nicht übersetzt]" +--- + + +Is it really the end of January? Already? + +After using the Xmas break to port [Simon](/en/patterns/simon) — +not exactly the most trivial of patterns — I'm fairly confident that +all patterns will be ok. Simon has 61 options, so if it works +for Simon, it will work for all patterns, or at least that's how I see it. + +Seven patterns have now been ported. That might not seem like much, +but it does get rather tedious every time we make a change that touches the patterns, +as we then have 7 to update. +So I decided to put the pattern porting on hold for a while, and instead focus +my attention on [our new beta website](/en/). + +## Gatsby is now our static site generator + +The new website is built on top of [Gatsby](https://www.gatsbyjs.org/), a static site generator +written in JavaScript and powered by [React](https://reactjs.org/). We've been fairly committed +to [the JAMstack architecture](/en/blog/freesewing-goes-jamstack) here at freesewing.org. + +It's our third rewrite of the site since we launched freesewing.org and I admit that that's +a bit much. As in, I really hope the site we're building now will stick around for a while. + +Then again, rapid iterations are a good thing, especially as we were still finding our feet. +We do what it takes to get it right, and while the question +of *what's the purpose of this all* is perhaps on some of your minds, I feel +like beta.freesewing.org has gotten to the point where it answers that question. + +## (almost) everything happens in your browser now + +We rewrote our platform in JavaScript. That thing that runs in your browser. +Previously, whenever you wanted to change the style of your cuffs or something, we needed +to send your wishes to a backend, who'd then generate a draft and send it back. + +Now, when you tweak an option, we don't need a round-trip to a backend to show you +what things look like. Because everything runs in your browser. So if you change something, +it just updates right there on your screen. + +That's sort of what we had in mind all along, but it's still a powerful moment when +all the pieces finally start to fall in place and things actually work. + +That being said, not everything runs in the browser yet. Specifically turning your +patterns into PDFs is something that we handle in the backend as we're still +working on that part. + +## No account needed + +Our [new demo](https://beta.freesewing.org/en/demo) allows you to kick the tires without +the need to sign up. When signing up, there's no need to create an account with password, as +we now support signing up with your existing Google or GitHub account. + +People who already have an account will be able to login with their Google or GitHub account, +provided the email address of their freesewing account matches. + +## You can change everything + +We've made many changes to try and make it easier for developers to get started with +freesewing. But we've also made changes for people who contribute in other ways. + +All our (markdown) content can now be edited on the site. No GitHub account needed, +just click the little pencil icon next to the title, submit your changes, and we're good. + +Same good news for translators. All the translations can also be edited online. We've +also updated our documentation for translators and editors to reflect this new simplified workflow. + +## Custom layouts + +The login/signup with GitHub/Google accounts was a feature requested by users, and so is this one: +We now support the creation of a custom layout for your pattern. Here's how it works: + +When a pattern is drafted, the different pattern parts are laid out on the pattern automatically. +Often that's great, but sometimes you wish your could make some changes. +For example, you may want to get your pattern printed in a copy shop so you want to make +sure it fits on the width of their roll of paper. Or you want to save some paper by squeezing +some parts together. + +It's in early beta (as in, it still breaks from time to time) but you can now change the width +of your pattern, move your pattern parts around, rotate them, or even mirror them vertically +or horizontally to suit whatever your plans are. All of that can be done in your browser, on the site. + +## Developer documentation + +We've also integrated our developer documentation on the new site. +Until yesterday, documentation about the new platform was hosted on a separate site, +but now, we've ported the documentation and everything is integrated in our (future) website. + +## We won't migrate your drafts + +Time to talk about the things we won't be doing: We will not migrate your existing drafts. +The new platform is just too different. There is no way for us to migrate your existing drafts +in a way that makes sense. So, when the day comes we switch over to the new site, your drafts +will no longer be there. + +You can download all your data from our site, but if you don't do that yourself, +your v1 drafts will be gone. + +## No more comments + +I have decided to not implement a comments feature because I feel having them +raises the wrong expectations. + +Freesewing is not another [Pattern Review](https://sewing.patternreview.com/), +or [Thread and Needles](https://www.threadandneedles.org/), +or [The Fold Line](https://thefoldline.com/), +or [Textillia](https://www.textillia.com/), +or [Kollabora](http://www.kollabora.com/), +or whatever the *Raverly of sewing* du jour is. + +I don't want freesewing.org to compete with these websites. They +do their thing, we do ours. Their value proposition is the community, ours is not. +That doesn't mean our community isn't valuable. It just means that we don't +need our community to gather on our website. Our community exists wherever it +goes. Be it Twitter, Instagram, Reddit, blogs, or some social network that I've never +even heard of. It doesn't matter, it's all good. + +Building a community on the website takes time, it takes effort, it takes work. +And we simply don't have the bandwidth for that. So I'd rather we focus +on [our core mission](/en/docs/faq/#whats-your-end-game), and let people talk +about freesewing wherever it is they talk about things. + +## Paris anyone? + +I've mentioned I'd like to do some sort of meetup this year, and while I haven't really +had any time to work out what that would mean, we might end up meeting anyway. + +Specifically, [Charlotte](https://englishgirlathome.com/) (aka English girl at home) +and [Carmen](https://www.carmencitab.com/) (aka CarmencitaB) are organising the +[Paris Sewcial](https://englishgirlathome.com/2019/01/23/paris-sewcial-paris-coud-2019-registration-open/) +meetup in May. I'll be heading to Paris to be part of that, so if you +are too, we'll meet up there. + +Registration is +[right this way](https://www.eventbrite.co.uk/e/paris-sewcial-paris-coud-registration-54520802187). + + diff --git a/markdown/org/blog/roundup-2019-01/en.md b/markdown/org/blog/roundup-2019-01/en.md new file mode 100644 index 00000000000..b9dd8accf02 --- /dev/null +++ b/markdown/org/blog/roundup-2019-01/en.md @@ -0,0 +1,144 @@ +--- +author: "joostdecock" +caption: "Your login background for February" +date: "2019-01-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/26bf3d41513702ad361b5a0f15dcff2350cc852b-1920x1440.jpg" +intro: "Is it really the end of January? Already?" +title: "Monthly roundup - January 2019: The big beta update" +--- + + +Is it really the end of January? Already? + +After using the Xmas break to port [Simon](/en/patterns/simon) — +not exactly the most trivial of patterns — I'm fairly confident that +all patterns will be ok. Simon has 61 options, so if it works +for Simon, it will work for all patterns, or at least that's how I see it. + +Seven patterns have now been ported. That might not seem like much, +but it does get rather tedious every time we make a change that touches the patterns, +as we then have 7 to update. +So I decided to put the pattern porting on hold for a while, and instead focus +my attention on [our new beta website](/en/). + +## Gatsby is now our static site generator + +The new website is built on top of [Gatsby](https://www.gatsbyjs.org/), a static site generator +written in JavaScript and powered by [React](https://reactjs.org/). We've been fairly committed +to [the JAMstack architecture](/en/blog/freesewing-goes-jamstack) here at freesewing.org. + +It's our third rewrite of the site since we launched freesewing.org and I admit that that's +a bit much. As in, I really hope the site we're building now will stick around for a while. + +Then again, rapid iterations are a good thing, especially as we were still finding our feet. +We do what it takes to get it right, and while the question +of *what's the purpose of this all* is perhaps on some of your minds, I feel +like beta.freesewing.org has gotten to the point where it answers that question. + +## (almost) everything happens in your browser now + +We rewrote our platform in JavaScript. That thing that runs in your browser. +Previously, whenever you wanted to change the style of your cuffs or something, we needed +to send your wishes to a backend, who'd then generate a draft and send it back. + +Now, when you tweak an option, we don't need a round-trip to a backend to show you +what things look like. Because everything runs in your browser. So if you change something, +it just updates right there on your screen. + +That's sort of what we had in mind all along, but it's still a powerful moment when +all the pieces finally start to fall in place and things actually work. + +That being said, not everything runs in the browser yet. Specifically turning your +patterns into PDFs is something that we handle in the backend as we're still +working on that part. + +## No account needed + +Our [new demo](https://beta.freesewing.org/en/demo) allows you to kick the tires without +the need to sign up. When signing up, there's no need to create an account with password, as +we now support signing up with your existing Google or GitHub account. + +People who already have an account will be able to login with their Google or GitHub account, +provided the email address of their freesewing account matches. + +## You can change everything + +We've made many changes to try and make it easier for developers to get started with +freesewing. But we've also made changes for people who contribute in other ways. + +All our (markdown) content can now be edited on the site. No GitHub account needed, +just click the little pencil icon next to the title, submit your changes, and we're good. + +Same good news for translators. All the translations can also be edited online. We've +also updated our documentation for translators and editors to reflect this new simplified workflow. + +## Custom layouts + +The login/signup with GitHub/Google accounts was a feature requested by users, and so is this one: +We now support the creation of a custom layout for your pattern. Here's how it works: + +When a pattern is drafted, the different pattern parts are laid out on the pattern automatically. +Often that's great, but sometimes you wish your could make some changes. +For example, you may want to get your pattern printed in a copy shop so you want to make +sure it fits on the width of their roll of paper. Or you want to save some paper by squeezing +some parts together. + +It's in early beta (as in, it still breaks from time to time) but you can now change the width +of your pattern, move your pattern parts around, rotate them, or even mirror them vertically +or horizontally to suit whatever your plans are. All of that can be done in your browser, on the site. + +## Developer documentation + +We've also integrated our developer documentation on the new site. +Until yesterday, documentation about the new platform was hosted on a separate site, +but now, we've ported the documentation and everything is integrated in our (future) website. + +## We won't migrate your drafts + +Time to talk about the things we won't be doing: We will not migrate your existing drafts. +The new platform is just too different. There is no way for us to migrate your existing drafts +in a way that makes sense. So, when the day comes we switch over to the new site, your drafts +will no longer be there. + +You can download all your data from our site, but if you don't do that yourself, +your v1 drafts will be gone. + +## No more comments + +I have decided to not implement a comments feature because I feel having them +raises the wrong expectations. + +Freesewing is not another [Pattern Review](https://sewing.patternreview.com/), +or [Thread and Needles](https://www.threadandneedles.org/), +or [The Fold Line](https://thefoldline.com/), +or [Textillia](https://www.textillia.com/), +or [Kollabora](http://www.kollabora.com/), +or whatever the *Raverly of sewing* du jour is. + +I don't want freesewing.org to compete with these websites. They +do their thing, we do ours. Their value proposition is the community, ours is not. +That doesn't mean our community isn't valuable. It just means that we don't +need our community to gather on our website. Our community exists wherever it +goes. Be it Twitter, Instagram, Reddit, blogs, or some social network that I've never +even heard of. It doesn't matter, it's all good. + +Building a community on the website takes time, it takes effort, it takes work. +And we simply don't have the bandwidth for that. So I'd rather we focus +on [our core mission](/en/docs/faq/#whats-your-end-game), and let people talk +about freesewing wherever it is they talk about things. + +## Paris anyone? + +I've mentioned I'd like to do some sort of meetup this year, and while I haven't really +had any time to work out what that would mean, we might end up meeting anyway. + +Specifically, [Charlotte](https://englishgirlathome.com/) (aka English girl at home) +and [Carmen](https://www.carmencitab.com/) (aka CarmencitaB) are organising the +[Paris Sewcial](https://englishgirlathome.com/2019/01/23/paris-sewcial-paris-coud-2019-registration-open/) +meetup in May. I'll be heading to Paris to be part of that, so if you +are too, we'll meet up there. + +Registration is +[right this way](https://www.eventbrite.co.uk/e/paris-sewcial-paris-coud-registration-54520802187). + + diff --git a/markdown/org/blog/roundup-2019-01/es.md b/markdown/org/blog/roundup-2019-01/es.md new file mode 100644 index 00000000000..57b4ed98419 --- /dev/null +++ b/markdown/org/blog/roundup-2019-01/es.md @@ -0,0 +1,144 @@ +--- +author: "joostdecock" +caption: "Your login background for February" +date: "2019-01-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/26bf3d41513702ad361b5a0f15dcff2350cc852b-1920x1440.jpg" +intro: "Is it really the end of January? Already?" +title: "Monthly roundup - January 2019: The big beta update [No traducido]" +--- + + +Is it really the end of January? Already? + +After using the Xmas break to port [Simon](/en/patterns/simon) — +not exactly the most trivial of patterns — I'm fairly confident that +all patterns will be ok. Simon has 61 options, so if it works +for Simon, it will work for all patterns, or at least that's how I see it. + +Seven patterns have now been ported. That might not seem like much, +but it does get rather tedious every time we make a change that touches the patterns, +as we then have 7 to update. +So I decided to put the pattern porting on hold for a while, and instead focus +my attention on [our new beta website](/en/). + +## Gatsby is now our static site generator + +The new website is built on top of [Gatsby](https://www.gatsbyjs.org/), a static site generator +written in JavaScript and powered by [React](https://reactjs.org/). We've been fairly committed +to [the JAMstack architecture](/en/blog/freesewing-goes-jamstack) here at freesewing.org. + +It's our third rewrite of the site since we launched freesewing.org and I admit that that's +a bit much. As in, I really hope the site we're building now will stick around for a while. + +Then again, rapid iterations are a good thing, especially as we were still finding our feet. +We do what it takes to get it right, and while the question +of *what's the purpose of this all* is perhaps on some of your minds, I feel +like beta.freesewing.org has gotten to the point where it answers that question. + +## (almost) everything happens in your browser now + +We rewrote our platform in JavaScript. That thing that runs in your browser. +Previously, whenever you wanted to change the style of your cuffs or something, we needed +to send your wishes to a backend, who'd then generate a draft and send it back. + +Now, when you tweak an option, we don't need a round-trip to a backend to show you +what things look like. Because everything runs in your browser. So if you change something, +it just updates right there on your screen. + +That's sort of what we had in mind all along, but it's still a powerful moment when +all the pieces finally start to fall in place and things actually work. + +That being said, not everything runs in the browser yet. Specifically turning your +patterns into PDFs is something that we handle in the backend as we're still +working on that part. + +## No account needed + +Our [new demo](https://beta.freesewing.org/en/demo) allows you to kick the tires without +the need to sign up. When signing up, there's no need to create an account with password, as +we now support signing up with your existing Google or GitHub account. + +People who already have an account will be able to login with their Google or GitHub account, +provided the email address of their freesewing account matches. + +## You can change everything + +We've made many changes to try and make it easier for developers to get started with +freesewing. But we've also made changes for people who contribute in other ways. + +All our (markdown) content can now be edited on the site. No GitHub account needed, +just click the little pencil icon next to the title, submit your changes, and we're good. + +Same good news for translators. All the translations can also be edited online. We've +also updated our documentation for translators and editors to reflect this new simplified workflow. + +## Custom layouts + +The login/signup with GitHub/Google accounts was a feature requested by users, and so is this one: +We now support the creation of a custom layout for your pattern. Here's how it works: + +When a pattern is drafted, the different pattern parts are laid out on the pattern automatically. +Often that's great, but sometimes you wish your could make some changes. +For example, you may want to get your pattern printed in a copy shop so you want to make +sure it fits on the width of their roll of paper. Or you want to save some paper by squeezing +some parts together. + +It's in early beta (as in, it still breaks from time to time) but you can now change the width +of your pattern, move your pattern parts around, rotate them, or even mirror them vertically +or horizontally to suit whatever your plans are. All of that can be done in your browser, on the site. + +## Developer documentation + +We've also integrated our developer documentation on the new site. +Until yesterday, documentation about the new platform was hosted on a separate site, +but now, we've ported the documentation and everything is integrated in our (future) website. + +## We won't migrate your drafts + +Time to talk about the things we won't be doing: We will not migrate your existing drafts. +The new platform is just too different. There is no way for us to migrate your existing drafts +in a way that makes sense. So, when the day comes we switch over to the new site, your drafts +will no longer be there. + +You can download all your data from our site, but if you don't do that yourself, +your v1 drafts will be gone. + +## No more comments + +I have decided to not implement a comments feature because I feel having them +raises the wrong expectations. + +Freesewing is not another [Pattern Review](https://sewing.patternreview.com/), +or [Thread and Needles](https://www.threadandneedles.org/), +or [The Fold Line](https://thefoldline.com/), +or [Textillia](https://www.textillia.com/), +or [Kollabora](http://www.kollabora.com/), +or whatever the *Raverly of sewing* du jour is. + +I don't want freesewing.org to compete with these websites. They +do their thing, we do ours. Their value proposition is the community, ours is not. +That doesn't mean our community isn't valuable. It just means that we don't +need our community to gather on our website. Our community exists wherever it +goes. Be it Twitter, Instagram, Reddit, blogs, or some social network that I've never +even heard of. It doesn't matter, it's all good. + +Building a community on the website takes time, it takes effort, it takes work. +And we simply don't have the bandwidth for that. So I'd rather we focus +on [our core mission](/en/docs/faq/#whats-your-end-game), and let people talk +about freesewing wherever it is they talk about things. + +## Paris anyone? + +I've mentioned I'd like to do some sort of meetup this year, and while I haven't really +had any time to work out what that would mean, we might end up meeting anyway. + +Specifically, [Charlotte](https://englishgirlathome.com/) (aka English girl at home) +and [Carmen](https://www.carmencitab.com/) (aka CarmencitaB) are organising the +[Paris Sewcial](https://englishgirlathome.com/2019/01/23/paris-sewcial-paris-coud-2019-registration-open/) +meetup in May. I'll be heading to Paris to be part of that, so if you +are too, we'll meet up there. + +Registration is +[right this way](https://www.eventbrite.co.uk/e/paris-sewcial-paris-coud-registration-54520802187). + + diff --git a/markdown/org/blog/roundup-2019-01/fr.md b/markdown/org/blog/roundup-2019-01/fr.md new file mode 100644 index 00000000000..ceef019e9a1 --- /dev/null +++ b/markdown/org/blog/roundup-2019-01/fr.md @@ -0,0 +1,144 @@ +--- +author: "joostdecock" +caption: "Your login background for February" +date: "2019-01-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/26bf3d41513702ad361b5a0f15dcff2350cc852b-1920x1440.jpg" +intro: "Is it really the end of January? Already?" +title: "Monthly roundup - January 2019: The big beta update [Non traduit]" +--- + + +Is it really the end of January? Already? + +After using the Xmas break to port [Simon](/en/patterns/simon) — +not exactly the most trivial of patterns — I'm fairly confident that +all patterns will be ok. Simon has 61 options, so if it works +for Simon, it will work for all patterns, or at least that's how I see it. + +Seven patterns have now been ported. That might not seem like much, +but it does get rather tedious every time we make a change that touches the patterns, +as we then have 7 to update. +So I decided to put the pattern porting on hold for a while, and instead focus +my attention on [our new beta website](/en/). + +## Gatsby is now our static site generator + +The new website is built on top of [Gatsby](https://www.gatsbyjs.org/), a static site generator +written in JavaScript and powered by [React](https://reactjs.org/). We've been fairly committed +to [the JAMstack architecture](/en/blog/freesewing-goes-jamstack) here at freesewing.org. + +It's our third rewrite of the site since we launched freesewing.org and I admit that that's +a bit much. As in, I really hope the site we're building now will stick around for a while. + +Then again, rapid iterations are a good thing, especially as we were still finding our feet. +We do what it takes to get it right, and while the question +of *what's the purpose of this all* is perhaps on some of your minds, I feel +like beta.freesewing.org has gotten to the point where it answers that question. + +## (almost) everything happens in your browser now + +We rewrote our platform in JavaScript. That thing that runs in your browser. +Previously, whenever you wanted to change the style of your cuffs or something, we needed +to send your wishes to a backend, who'd then generate a draft and send it back. + +Now, when you tweak an option, we don't need a round-trip to a backend to show you +what things look like. Because everything runs in your browser. So if you change something, +it just updates right there on your screen. + +That's sort of what we had in mind all along, but it's still a powerful moment when +all the pieces finally start to fall in place and things actually work. + +That being said, not everything runs in the browser yet. Specifically turning your +patterns into PDFs is something that we handle in the backend as we're still +working on that part. + +## No account needed + +Our [new demo](https://beta.freesewing.org/en/demo) allows you to kick the tires without +the need to sign up. When signing up, there's no need to create an account with password, as +we now support signing up with your existing Google or GitHub account. + +People who already have an account will be able to login with their Google or GitHub account, +provided the email address of their freesewing account matches. + +## You can change everything + +We've made many changes to try and make it easier for developers to get started with +freesewing. But we've also made changes for people who contribute in other ways. + +All our (markdown) content can now be edited on the site. No GitHub account needed, +just click the little pencil icon next to the title, submit your changes, and we're good. + +Same good news for translators. All the translations can also be edited online. We've +also updated our documentation for translators and editors to reflect this new simplified workflow. + +## Custom layouts + +The login/signup with GitHub/Google accounts was a feature requested by users, and so is this one: +We now support the creation of a custom layout for your pattern. Here's how it works: + +When a pattern is drafted, the different pattern parts are laid out on the pattern automatically. +Often that's great, but sometimes you wish your could make some changes. +For example, you may want to get your pattern printed in a copy shop so you want to make +sure it fits on the width of their roll of paper. Or you want to save some paper by squeezing +some parts together. + +It's in early beta (as in, it still breaks from time to time) but you can now change the width +of your pattern, move your pattern parts around, rotate them, or even mirror them vertically +or horizontally to suit whatever your plans are. All of that can be done in your browser, on the site. + +## Developer documentation + +We've also integrated our developer documentation on the new site. +Until yesterday, documentation about the new platform was hosted on a separate site, +but now, we've ported the documentation and everything is integrated in our (future) website. + +## We won't migrate your drafts + +Time to talk about the things we won't be doing: We will not migrate your existing drafts. +The new platform is just too different. There is no way for us to migrate your existing drafts +in a way that makes sense. So, when the day comes we switch over to the new site, your drafts +will no longer be there. + +You can download all your data from our site, but if you don't do that yourself, +your v1 drafts will be gone. + +## No more comments + +I have decided to not implement a comments feature because I feel having them +raises the wrong expectations. + +Freesewing is not another [Pattern Review](https://sewing.patternreview.com/), +or [Thread and Needles](https://www.threadandneedles.org/), +or [The Fold Line](https://thefoldline.com/), +or [Textillia](https://www.textillia.com/), +or [Kollabora](http://www.kollabora.com/), +or whatever the *Raverly of sewing* du jour is. + +I don't want freesewing.org to compete with these websites. They +do their thing, we do ours. Their value proposition is the community, ours is not. +That doesn't mean our community isn't valuable. It just means that we don't +need our community to gather on our website. Our community exists wherever it +goes. Be it Twitter, Instagram, Reddit, blogs, or some social network that I've never +even heard of. It doesn't matter, it's all good. + +Building a community on the website takes time, it takes effort, it takes work. +And we simply don't have the bandwidth for that. So I'd rather we focus +on [our core mission](/en/docs/faq/#whats-your-end-game), and let people talk +about freesewing wherever it is they talk about things. + +## Paris anyone? + +I've mentioned I'd like to do some sort of meetup this year, and while I haven't really +had any time to work out what that would mean, we might end up meeting anyway. + +Specifically, [Charlotte](https://englishgirlathome.com/) (aka English girl at home) +and [Carmen](https://www.carmencitab.com/) (aka CarmencitaB) are organising the +[Paris Sewcial](https://englishgirlathome.com/2019/01/23/paris-sewcial-paris-coud-2019-registration-open/) +meetup in May. I'll be heading to Paris to be part of that, so if you +are too, we'll meet up there. + +Registration is +[right this way](https://www.eventbrite.co.uk/e/paris-sewcial-paris-coud-registration-54520802187). + + diff --git a/markdown/org/blog/roundup-2019-01/nl.md b/markdown/org/blog/roundup-2019-01/nl.md new file mode 100644 index 00000000000..5297e6053a4 --- /dev/null +++ b/markdown/org/blog/roundup-2019-01/nl.md @@ -0,0 +1,144 @@ +--- +author: "joostdecock" +caption: "Your login background for February" +date: "2019-01-31" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/26bf3d41513702ad361b5a0f15dcff2350cc852b-1920x1440.jpg" +intro: "Is it really the end of January? Already?" +title: "Monthly roundup - January 2019: The big beta update [Niet vertaald]" +--- + + +Is it really the end of January? Already? + +After using the Xmas break to port [Simon](/en/patterns/simon) — +not exactly the most trivial of patterns — I'm fairly confident that +all patterns will be ok. Simon has 61 options, so if it works +for Simon, it will work for all patterns, or at least that's how I see it. + +Seven patterns have now been ported. That might not seem like much, +but it does get rather tedious every time we make a change that touches the patterns, +as we then have 7 to update. +So I decided to put the pattern porting on hold for a while, and instead focus +my attention on [our new beta website](/en/). + +## Gatsby is now our static site generator + +The new website is built on top of [Gatsby](https://www.gatsbyjs.org/), a static site generator +written in JavaScript and powered by [React](https://reactjs.org/). We've been fairly committed +to [the JAMstack architecture](/en/blog/freesewing-goes-jamstack) here at freesewing.org. + +It's our third rewrite of the site since we launched freesewing.org and I admit that that's +a bit much. As in, I really hope the site we're building now will stick around for a while. + +Then again, rapid iterations are a good thing, especially as we were still finding our feet. +We do what it takes to get it right, and while the question +of *what's the purpose of this all* is perhaps on some of your minds, I feel +like beta.freesewing.org has gotten to the point where it answers that question. + +## (almost) everything happens in your browser now + +We rewrote our platform in JavaScript. That thing that runs in your browser. +Previously, whenever you wanted to change the style of your cuffs or something, we needed +to send your wishes to a backend, who'd then generate a draft and send it back. + +Now, when you tweak an option, we don't need a round-trip to a backend to show you +what things look like. Because everything runs in your browser. So if you change something, +it just updates right there on your screen. + +That's sort of what we had in mind all along, but it's still a powerful moment when +all the pieces finally start to fall in place and things actually work. + +That being said, not everything runs in the browser yet. Specifically turning your +patterns into PDFs is something that we handle in the backend as we're still +working on that part. + +## No account needed + +Our [new demo](https://beta.freesewing.org/en/demo) allows you to kick the tires without +the need to sign up. When signing up, there's no need to create an account with password, as +we now support signing up with your existing Google or GitHub account. + +People who already have an account will be able to login with their Google or GitHub account, +provided the email address of their freesewing account matches. + +## You can change everything + +We've made many changes to try and make it easier for developers to get started with +freesewing. But we've also made changes for people who contribute in other ways. + +All our (markdown) content can now be edited on the site. No GitHub account needed, +just click the little pencil icon next to the title, submit your changes, and we're good. + +Same good news for translators. All the translations can also be edited online. We've +also updated our documentation for translators and editors to reflect this new simplified workflow. + +## Custom layouts + +The login/signup with GitHub/Google accounts was a feature requested by users, and so is this one: +We now support the creation of a custom layout for your pattern. Here's how it works: + +When a pattern is drafted, the different pattern parts are laid out on the pattern automatically. +Often that's great, but sometimes you wish your could make some changes. +For example, you may want to get your pattern printed in a copy shop so you want to make +sure it fits on the width of their roll of paper. Or you want to save some paper by squeezing +some parts together. + +It's in early beta (as in, it still breaks from time to time) but you can now change the width +of your pattern, move your pattern parts around, rotate them, or even mirror them vertically +or horizontally to suit whatever your plans are. All of that can be done in your browser, on the site. + +## Developer documentation + +We've also integrated our developer documentation on the new site. +Until yesterday, documentation about the new platform was hosted on a separate site, +but now, we've ported the documentation and everything is integrated in our (future) website. + +## We won't migrate your drafts + +Time to talk about the things we won't be doing: We will not migrate your existing drafts. +The new platform is just too different. There is no way for us to migrate your existing drafts +in a way that makes sense. So, when the day comes we switch over to the new site, your drafts +will no longer be there. + +You can download all your data from our site, but if you don't do that yourself, +your v1 drafts will be gone. + +## No more comments + +I have decided to not implement a comments feature because I feel having them +raises the wrong expectations. + +Freesewing is not another [Pattern Review](https://sewing.patternreview.com/), +or [Thread and Needles](https://www.threadandneedles.org/), +or [The Fold Line](https://thefoldline.com/), +or [Textillia](https://www.textillia.com/), +or [Kollabora](http://www.kollabora.com/), +or whatever the *Raverly of sewing* du jour is. + +I don't want freesewing.org to compete with these websites. They +do their thing, we do ours. Their value proposition is the community, ours is not. +That doesn't mean our community isn't valuable. It just means that we don't +need our community to gather on our website. Our community exists wherever it +goes. Be it Twitter, Instagram, Reddit, blogs, or some social network that I've never +even heard of. It doesn't matter, it's all good. + +Building a community on the website takes time, it takes effort, it takes work. +And we simply don't have the bandwidth for that. So I'd rather we focus +on [our core mission](/en/docs/faq/#whats-your-end-game), and let people talk +about freesewing wherever it is they talk about things. + +## Paris anyone? + +I've mentioned I'd like to do some sort of meetup this year, and while I haven't really +had any time to work out what that would mean, we might end up meeting anyway. + +Specifically, [Charlotte](https://englishgirlathome.com/) (aka English girl at home) +and [Carmen](https://www.carmencitab.com/) (aka CarmencitaB) are organising the +[Paris Sewcial](https://englishgirlathome.com/2019/01/23/paris-sewcial-paris-coud-2019-registration-open/) +meetup in May. I'll be heading to Paris to be part of that, so if you +are too, we'll meet up there. + +Registration is +[right this way](https://www.eventbrite.co.uk/e/paris-sewcial-paris-coud-registration-54520802187). + + diff --git a/markdown/org/blog/the-refashioners-2017/de.md b/markdown/org/blog/the-refashioners-2017/de.md new file mode 100644 index 00000000000..06e75d1eed1 --- /dev/null +++ b/markdown/org/blog/the-refashioners-2017/de.md @@ -0,0 +1,158 @@ +--- +author: "joostdecock" +caption: "They said I was crazy to make a zebra jacket, so I made it anyway. And it sank into the swamp." +date: "2017-09-04" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/35dda6f4c8ec6f2689e2741cc49cf178e4a39474-3300x2200.jpg" +intro: "For the uninitiated, the refashioners is a yearly event/competition hosted by the charming (and very persuasive) Portia Lawrie ." +title: "The Refashioners 2017 - Now with a Blake Blazer preview and 100% more zebra [Nicht übersetzt]" +--- + +For the uninitiated, the refashioners is a yearly event/competition hosted by the charming (and very persuasive) +[Portia Lawrie](http://www.makery.uk/). + +Its focus is on giving old, unworn, or unloved garments a new lease on life through the art of refashioning. + +This bonanza of garment Frankensteining kicks of with a series of *hors-compétition* makes, aimed at getting +the creative juices flowing. And [just like last year](http://www.makery.uk/2016/08/the-refashioners-2016-joost/), +I got asked to be one of those *warm-up acts*. + +Before I talk a bit about how it went, here's some pictures of what I made: + +![Yup, defenitely a zebra jacket](https://posts.freesewing.org/uploads/zebra1_f856635d39.jpg) + +![A view of the back](https://posts.freesewing.org/uploads/zebra2_c1df8979c5.jpg) + +![Stripe matching with sleevecap ease is tricky](https://posts.freesewing.org/uploads/zebra3_db4d55ad19.jpg) + +![A look at the insanity that lies beneath](https://posts.freesewing.org/uploads/zebra4_154c70b269.jpg) + +![Recycled buttons](https://posts.freesewing.org/uploads/zebra5_139563ceb2.jpg) + +![I case you missed it, this jacket comes with patch pocket](https://posts.freesewing.org/uploads/zebra6_34df45c31e.jpg) + +## The male romper lobby +Last year, the theme was jeans, this year it's suits. And from the moment I shared that snippet of info +with a handful of friends, they've conspiring to get me to make a male romper. + +![Sorcha trying to get me to make a romper](https://posts.freesewing.org/uploads/romper_chat_6cf0df4477.png) + +![Anneke trying to help by sketching a romper for me](https://posts.freesewing.org/uploads/romper_sketch_09c8005525.jpg) + +With friends like that, who needs enemies. + +## How I got to zebra + +The first thing I did was limit my options. Too much choice tends to paralize. + +I decided to not only respect the suit theme with regards to the source material, but also concerning the techniques involved. +Making a suit, and especially jacket construction, is a fine art and I wanted that to be part of my project. + +So, no messenger bags or (dare I say it) shoes out of recycled suits, I wanted to make a jacket. + +The problem is that suits are rather challenging to refashion. There's just not a lot of large pieces of pristine fabric to work with. + +![The front part of a jacket does not leave you with a lot to work with](https://posts.freesewing.org/uploads/front_part_4401c51b7b.jpg) + +In addition, I'm really tall so there is simply no way I can salvage enough fabric form a suit to make a new jacket +without having to sew a bunch of scraps together. + +I was worried that this sort of patchwork jacket was going to look super hobo. +But since I don't really have any other option to make a jacket, I started thinking about what sort of patchwork would be most acceptable. + +![Eurek(zebr)a!](https://posts.freesewing.org/uploads/real_zebra_b1decba3b1.jpg) + +And then one day in the shower it hit me: zebra! If I could find a black and a white suit, I could cut them into stripes +and join those together to form the pattern parts I needed. If it was going to be patchwork, I might as well embrace it, right? + +## The Blake Blazer pattern + +My first idea was to make a jacket in muslin, draw zebra stripes on it, take it apart, cut out the stripes, and use that as my pattern. +But I was worried this process would not be precise enough. + +Also, what pattern would I use to make the jacket in the first place? I don't really use patterns that I haven't designed myself +because I'm more of an uphill ice-skating kinda guy. + +![Some mofos are always trying to ice-skate uphill](https://posts.freesewing.org/uploads/ice_skating_uphill_80ab69e9bd.gif) + +So, I set out to design the Blake Blazer. It's a jacket/sportscoat pattern that I initially hoped to release with this post, but +you're going to have to give me some more time for that. + +![The early draft of the Blake Blazer that I used for this jacket](https://posts.freesewing.org/uploads/blake_f3e813a99d.svg) + +To get those zebra stripes as precise as possible, I decided to add the stripes to the pattern. +This way, I could make sure they would match and whenever they don't in the jacket, I've got my own shoddy workmanship to blame. + +Also, for this project, I decided to make it a bit of a cropped look because I was worried I wouldn't have enough fabric to work with. + +## Finding suits to refashion + +With my pattern sorted, I started looking into the source material for my make. +As it happens, I have a cardboard box full of old and unloved suits that's still in storage since my last move. + +I've always intended to take these apart to learn from their construction so this was the perfect opportunity. + +![A box of suits to reverse engineer](https://posts.freesewing.org/uploads/suits_box_434d198619.jpg) + +![Treasure!](https://posts.freesewing.org/uploads/suits_inside_0637374422.jpg) + +I have two black suits to choose from, but absolutely no white suits. So I hit the thriftstores only to discover that white suits are a bit of a rarity. + +I was unable to find any white suit even though I visited 8 different thrift stores. To make matters worse, I couldn't even find a +white suit in any of the second hand stores I visited with one exception: I found a white suit in a second hand store, but it was 200 euro. + +Apart from the fact that I'm not made of money, I don't think buying a 200 euro second hand suit only to rip it apart is much in line with the spirit +of the refashioners. + +I briefly contemplated a different colour combination, but nobody is waiting for a black and navy zebra. + +![I ended up using the one on the left](https://posts.freesewing.org/uploads/suits_black_53828cb3ec.jpg) + +![Never a good sign when things are secured with a steel cable](https://posts.freesewing.org/uploads/suits_white_c02d4bf0c8.jpg) + +Fortunately, the rules of the refashioners are that at least 50% of your make should be recycled suits. Apart from that, you do what you want. + +So, by making the black stripes dominant, making the entire facing out of black, and recycling the inner parts of the suit (think canvas, shouler padding, buttons and so on) I would have no problem reaching that 50% treshold. + +So, true to the thrifty spirit of refashioners, I picked up some white fabric in the haberdasher that was 4 euro per meter. +Something that I would soon regret as I tried to make this piece of glorified plastic play nice with the wool of the black suit. + +## Putting it all together + +I wanted the zebra stripes to look like a real zebra, so no straight lines. I addition, I noticed that a zebra's stripes don't continue on his back and belly +but sort of a run before they hit the center. I wanted to replicate that look, and lived to regret it. + +![These scraps are waiting to become an undersleeve](https://posts.freesewing.org/uploads/sleeve_parts_052a369ca4.jpg) + +I ended up having to hand baste all the different parts together. This jacket's outer shell is made up of 93 different scraps and pieces that are all puzzled together. + +![This are not scraps to be thrown out, but scraps to be made into a jacket](https://posts.freesewing.org/uploads/scraps_412f72f0f2.jpg) + +In addition, I had to squeeze all the new parts out of the old suit parts, which meant that in some cases I was left with as little as a few mm of seam allowance. + +![Cutting the new sleeve parts out of the old sleeve](https://posts.freesewing.org/uploads/sleeve_2fd77b450d.jpg) + +Suffice to say, it was stressful. And after I had puzzled together the initial parts, I still had to -- you know -- make a jacket. +Which was kinda challenging with all that stripe matching I needed to do. + +![Construction slowly moving forward](https://posts.freesewing.org/uploads/front_9821526627.jpg) + +![Preparing the patch pockets](https://posts.freesewing.org/uploads/pocket_db7596902d.jpg) + +## Final notes + +I ran out of time to add the lining, but part of me feels it would be a shame to cover up the insanity that is the inside of the jacket. + +And I'm not entirely pleased with the collar. I had made one muslin test garment, but now that I've made the real thing, I am going to go back to the pattern and make some tweaks before releasing it. + +In the meanwhile, enjoy some [more pictures of the jacket in this Flickr set](https://www.flickr.com/photos/__niki__/albums/72157684742893052). + +## Now it's your turn + +So this is it, my contribution for The Refasioners 2017. I hope I was able to inspire you for some refashioning of your own. +If nothing else, maybe it was a good reminder of what not to try ;) + + +> ##### More refashioners +> To stay up to date with The Refashioners 2017, see all the other inspiring refashions AND +> find out how you could win an amazing prize go to: [www.makery.uk/the-refashioners/](http://www.makery.uk/the-refashioners/) + diff --git a/markdown/org/blog/the-refashioners-2017/en.md b/markdown/org/blog/the-refashioners-2017/en.md new file mode 100644 index 00000000000..ab2b7c0f489 --- /dev/null +++ b/markdown/org/blog/the-refashioners-2017/en.md @@ -0,0 +1,158 @@ +--- +author: "joostdecock" +caption: "They said I was crazy to make a zebra jacket, so I made it anyway. And it sank into the swamp." +date: "2017-09-04" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/35dda6f4c8ec6f2689e2741cc49cf178e4a39474-3300x2200.jpg" +intro: "For the uninitiated, the refashioners is a yearly event/competition hosted by the charming (and very persuasive) Portia Lawrie ." +title: "The Refashioners 2017 - Now with a Blake Blazer preview and 100% more zebra" +--- + +For the uninitiated, the refashioners is a yearly event/competition hosted by the charming (and very persuasive) +[Portia Lawrie](http://www.makery.uk/). + +Its focus is on giving old, unworn, or unloved garments a new lease on life through the art of refashioning. + +This bonanza of garment Frankensteining kicks of with a series of *hors-compétition* makes, aimed at getting +the creative juices flowing. And [just like last year](http://www.makery.uk/2016/08/the-refashioners-2016-joost/), +I got asked to be one of those *warm-up acts*. + +Before I talk a bit about how it went, here's some pictures of what I made: + +![Yup, defenitely a zebra jacket](https://posts.freesewing.org/uploads/zebra1_f856635d39.jpg) + +![A view of the back](https://posts.freesewing.org/uploads/zebra2_c1df8979c5.jpg) + +![Stripe matching with sleevecap ease is tricky](https://posts.freesewing.org/uploads/zebra3_db4d55ad19.jpg) + +![A look at the insanity that lies beneath](https://posts.freesewing.org/uploads/zebra4_154c70b269.jpg) + +![Recycled buttons](https://posts.freesewing.org/uploads/zebra5_139563ceb2.jpg) + +![I case you missed it, this jacket comes with patch pocket](https://posts.freesewing.org/uploads/zebra6_34df45c31e.jpg) + +## The male romper lobby +Last year, the theme was jeans, this year it's suits. And from the moment I shared that snippet of info +with a handful of friends, they've conspiring to get me to make a male romper. + +![Sorcha trying to get me to make a romper](https://posts.freesewing.org/uploads/romper_chat_6cf0df4477.png) + +![Anneke trying to help by sketching a romper for me](https://posts.freesewing.org/uploads/romper_sketch_09c8005525.jpg) + +With friends like that, who needs enemies. + +## How I got to zebra + +The first thing I did was limit my options. Too much choice tends to paralize. + +I decided to not only respect the suit theme with regards to the source material, but also concerning the techniques involved. +Making a suit, and especially jacket construction, is a fine art and I wanted that to be part of my project. + +So, no messenger bags or (dare I say it) shoes out of recycled suits, I wanted to make a jacket. + +The problem is that suits are rather challenging to refashion. There's just not a lot of large pieces of pristine fabric to work with. + +![The front part of a jacket does not leave you with a lot to work with](https://posts.freesewing.org/uploads/front_part_4401c51b7b.jpg) + +In addition, I'm really tall so there is simply no way I can salvage enough fabric form a suit to make a new jacket +without having to sew a bunch of scraps together. + +I was worried that this sort of patchwork jacket was going to look super hobo. +But since I don't really have any other option to make a jacket, I started thinking about what sort of patchwork would be most acceptable. + +![Eurek(zebr)a!](https://posts.freesewing.org/uploads/real_zebra_b1decba3b1.jpg) + +And then one day in the shower it hit me: zebra! If I could find a black and a white suit, I could cut them into stripes +and join those together to form the pattern parts I needed. If it was going to be patchwork, I might as well embrace it, right? + +## The Blake Blazer pattern + +My first idea was to make a jacket in muslin, draw zebra stripes on it, take it apart, cut out the stripes, and use that as my pattern. +But I was worried this process would not be precise enough. + +Also, what pattern would I use to make the jacket in the first place? I don't really use patterns that I haven't designed myself +because I'm more of an uphill ice-skating kinda guy. + +![Some mofos are always trying to ice-skate uphill](https://posts.freesewing.org/uploads/ice_skating_uphill_80ab69e9bd.gif) + +So, I set out to design the Blake Blazer. It's a jacket/sportscoat pattern that I initially hoped to release with this post, but +you're going to have to give me some more time for that. + +![The early draft of the Blake Blazer that I used for this jacket](https://posts.freesewing.org/uploads/blake_f3e813a99d.svg) + +To get those zebra stripes as precise as possible, I decided to add the stripes to the pattern. +This way, I could make sure they would match and whenever they don't in the jacket, I've got my own shoddy workmanship to blame. + +Also, for this project, I decided to make it a bit of a cropped look because I was worried I wouldn't have enough fabric to work with. + +## Finding suits to refashion + +With my pattern sorted, I started looking into the source material for my make. +As it happens, I have a cardboard box full of old and unloved suits that's still in storage since my last move. + +I've always intended to take these apart to learn from their construction so this was the perfect opportunity. + +![A box of suits to reverse engineer](https://posts.freesewing.org/uploads/suits_box_434d198619.jpg) + +![Treasure!](https://posts.freesewing.org/uploads/suits_inside_0637374422.jpg) + +I have two black suits to choose from, but absolutely no white suits. So I hit the thriftstores only to discover that white suits are a bit of a rarity. + +I was unable to find any white suit even though I visited 8 different thrift stores. To make matters worse, I couldn't even find a +white suit in any of the second hand stores I visited with one exception: I found a white suit in a second hand store, but it was 200 euro. + +Apart from the fact that I'm not made of money, I don't think buying a 200 euro second hand suit only to rip it apart is much in line with the spirit +of the refashioners. + +I briefly contemplated a different colour combination, but nobody is waiting for a black and navy zebra. + +![I ended up using the one on the left](https://posts.freesewing.org/uploads/suits_black_53828cb3ec.jpg) + +![Never a good sign when things are secured with a steel cable](https://posts.freesewing.org/uploads/suits_white_c02d4bf0c8.jpg) + +Fortunately, the rules of the refashioners are that at least 50% of your make should be recycled suits. Apart from that, you do what you want. + +So, by making the black stripes dominant, making the entire facing out of black, and recycling the inner parts of the suit (think canvas, shouler padding, buttons and so on) I would have no problem reaching that 50% treshold. + +So, true to the thrifty spirit of refashioners, I picked up some white fabric in the haberdasher that was 4 euro per meter. +Something that I would soon regret as I tried to make this piece of glorified plastic play nice with the wool of the black suit. + +## Putting it all together + +I wanted the zebra stripes to look like a real zebra, so no straight lines. I addition, I noticed that a zebra's stripes don't continue on his back and belly +but sort of a run before they hit the center. I wanted to replicate that look, and lived to regret it. + +![These scraps are waiting to become an undersleeve](https://posts.freesewing.org/uploads/sleeve_parts_052a369ca4.jpg) + +I ended up having to hand baste all the different parts together. This jacket's outer shell is made up of 93 different scraps and pieces that are all puzzled together. + +![This are not scraps to be thrown out, but scraps to be made into a jacket](https://posts.freesewing.org/uploads/scraps_412f72f0f2.jpg) + +In addition, I had to squeeze all the new parts out of the old suit parts, which meant that in some cases I was left with as little as a few mm of seam allowance. + +![Cutting the new sleeve parts out of the old sleeve](https://posts.freesewing.org/uploads/sleeve_2fd77b450d.jpg) + +Suffice to say, it was stressful. And after I had puzzled together the initial parts, I still had to -- you know -- make a jacket. +Which was kinda challenging with all that stripe matching I needed to do. + +![Construction slowly moving forward](https://posts.freesewing.org/uploads/front_9821526627.jpg) + +![Preparing the patch pockets](https://posts.freesewing.org/uploads/pocket_db7596902d.jpg) + +## Final notes + +I ran out of time to add the lining, but part of me feels it would be a shame to cover up the insanity that is the inside of the jacket. + +And I'm not entirely pleased with the collar. I had made one muslin test garment, but now that I've made the real thing, I am going to go back to the pattern and make some tweaks before releasing it. + +In the meanwhile, enjoy some [more pictures of the jacket in this Flickr set](https://www.flickr.com/photos/__niki__/albums/72157684742893052). + +## Now it's your turn + +So this is it, my contribution for The Refasioners 2017. I hope I was able to inspire you for some refashioning of your own. +If nothing else, maybe it was a good reminder of what not to try ;) + + +> ##### More refashioners +> To stay up to date with The Refashioners 2017, see all the other inspiring refashions AND +> find out how you could win an amazing prize go to: [www.makery.uk/the-refashioners/](http://www.makery.uk/the-refashioners/) + diff --git a/markdown/org/blog/the-refashioners-2017/es.md b/markdown/org/blog/the-refashioners-2017/es.md new file mode 100644 index 00000000000..4ed08b10bb2 --- /dev/null +++ b/markdown/org/blog/the-refashioners-2017/es.md @@ -0,0 +1,158 @@ +--- +author: "joostdecock" +caption: "They said I was crazy to make a zebra jacket, so I made it anyway. And it sank into the swamp." +date: "2017-09-04" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/35dda6f4c8ec6f2689e2741cc49cf178e4a39474-3300x2200.jpg" +intro: "For the uninitiated, the refashioners is a yearly event/competition hosted by the charming (and very persuasive) Portia Lawrie ." +title: "The Refashioners 2017 - Now with a Blake Blazer preview and 100% more zebra [No traducido]" +--- + +For the uninitiated, the refashioners is a yearly event/competition hosted by the charming (and very persuasive) +[Portia Lawrie](http://www.makery.uk/). + +Its focus is on giving old, unworn, or unloved garments a new lease on life through the art of refashioning. + +This bonanza of garment Frankensteining kicks of with a series of *hors-compétition* makes, aimed at getting +the creative juices flowing. And [just like last year](http://www.makery.uk/2016/08/the-refashioners-2016-joost/), +I got asked to be one of those *warm-up acts*. + +Before I talk a bit about how it went, here's some pictures of what I made: + +![Yup, defenitely a zebra jacket](https://posts.freesewing.org/uploads/zebra1_f856635d39.jpg) + +![A view of the back](https://posts.freesewing.org/uploads/zebra2_c1df8979c5.jpg) + +![Stripe matching with sleevecap ease is tricky](https://posts.freesewing.org/uploads/zebra3_db4d55ad19.jpg) + +![A look at the insanity that lies beneath](https://posts.freesewing.org/uploads/zebra4_154c70b269.jpg) + +![Recycled buttons](https://posts.freesewing.org/uploads/zebra5_139563ceb2.jpg) + +![I case you missed it, this jacket comes with patch pocket](https://posts.freesewing.org/uploads/zebra6_34df45c31e.jpg) + +## The male romper lobby +Last year, the theme was jeans, this year it's suits. And from the moment I shared that snippet of info +with a handful of friends, they've conspiring to get me to make a male romper. + +![Sorcha trying to get me to make a romper](https://posts.freesewing.org/uploads/romper_chat_6cf0df4477.png) + +![Anneke trying to help by sketching a romper for me](https://posts.freesewing.org/uploads/romper_sketch_09c8005525.jpg) + +With friends like that, who needs enemies. + +## How I got to zebra + +The first thing I did was limit my options. Too much choice tends to paralize. + +I decided to not only respect the suit theme with regards to the source material, but also concerning the techniques involved. +Making a suit, and especially jacket construction, is a fine art and I wanted that to be part of my project. + +So, no messenger bags or (dare I say it) shoes out of recycled suits, I wanted to make a jacket. + +The problem is that suits are rather challenging to refashion. There's just not a lot of large pieces of pristine fabric to work with. + +![The front part of a jacket does not leave you with a lot to work with](https://posts.freesewing.org/uploads/front_part_4401c51b7b.jpg) + +In addition, I'm really tall so there is simply no way I can salvage enough fabric form a suit to make a new jacket +without having to sew a bunch of scraps together. + +I was worried that this sort of patchwork jacket was going to look super hobo. +But since I don't really have any other option to make a jacket, I started thinking about what sort of patchwork would be most acceptable. + +![Eurek(zebr)a!](https://posts.freesewing.org/uploads/real_zebra_b1decba3b1.jpg) + +And then one day in the shower it hit me: zebra! If I could find a black and a white suit, I could cut them into stripes +and join those together to form the pattern parts I needed. If it was going to be patchwork, I might as well embrace it, right? + +## The Blake Blazer pattern + +My first idea was to make a jacket in muslin, draw zebra stripes on it, take it apart, cut out the stripes, and use that as my pattern. +But I was worried this process would not be precise enough. + +Also, what pattern would I use to make the jacket in the first place? I don't really use patterns that I haven't designed myself +because I'm more of an uphill ice-skating kinda guy. + +![Some mofos are always trying to ice-skate uphill](https://posts.freesewing.org/uploads/ice_skating_uphill_80ab69e9bd.gif) + +So, I set out to design the Blake Blazer. It's a jacket/sportscoat pattern that I initially hoped to release with this post, but +you're going to have to give me some more time for that. + +![The early draft of the Blake Blazer that I used for this jacket](https://posts.freesewing.org/uploads/blake_f3e813a99d.svg) + +To get those zebra stripes as precise as possible, I decided to add the stripes to the pattern. +This way, I could make sure they would match and whenever they don't in the jacket, I've got my own shoddy workmanship to blame. + +Also, for this project, I decided to make it a bit of a cropped look because I was worried I wouldn't have enough fabric to work with. + +## Finding suits to refashion + +With my pattern sorted, I started looking into the source material for my make. +As it happens, I have a cardboard box full of old and unloved suits that's still in storage since my last move. + +I've always intended to take these apart to learn from their construction so this was the perfect opportunity. + +![A box of suits to reverse engineer](https://posts.freesewing.org/uploads/suits_box_434d198619.jpg) + +![Treasure!](https://posts.freesewing.org/uploads/suits_inside_0637374422.jpg) + +I have two black suits to choose from, but absolutely no white suits. So I hit the thriftstores only to discover that white suits are a bit of a rarity. + +I was unable to find any white suit even though I visited 8 different thrift stores. To make matters worse, I couldn't even find a +white suit in any of the second hand stores I visited with one exception: I found a white suit in a second hand store, but it was 200 euro. + +Apart from the fact that I'm not made of money, I don't think buying a 200 euro second hand suit only to rip it apart is much in line with the spirit +of the refashioners. + +I briefly contemplated a different colour combination, but nobody is waiting for a black and navy zebra. + +![I ended up using the one on the left](https://posts.freesewing.org/uploads/suits_black_53828cb3ec.jpg) + +![Never a good sign when things are secured with a steel cable](https://posts.freesewing.org/uploads/suits_white_c02d4bf0c8.jpg) + +Fortunately, the rules of the refashioners are that at least 50% of your make should be recycled suits. Apart from that, you do what you want. + +So, by making the black stripes dominant, making the entire facing out of black, and recycling the inner parts of the suit (think canvas, shouler padding, buttons and so on) I would have no problem reaching that 50% treshold. + +So, true to the thrifty spirit of refashioners, I picked up some white fabric in the haberdasher that was 4 euro per meter. +Something that I would soon regret as I tried to make this piece of glorified plastic play nice with the wool of the black suit. + +## Putting it all together + +I wanted the zebra stripes to look like a real zebra, so no straight lines. I addition, I noticed that a zebra's stripes don't continue on his back and belly +but sort of a run before they hit the center. I wanted to replicate that look, and lived to regret it. + +![These scraps are waiting to become an undersleeve](https://posts.freesewing.org/uploads/sleeve_parts_052a369ca4.jpg) + +I ended up having to hand baste all the different parts together. This jacket's outer shell is made up of 93 different scraps and pieces that are all puzzled together. + +![This are not scraps to be thrown out, but scraps to be made into a jacket](https://posts.freesewing.org/uploads/scraps_412f72f0f2.jpg) + +In addition, I had to squeeze all the new parts out of the old suit parts, which meant that in some cases I was left with as little as a few mm of seam allowance. + +![Cutting the new sleeve parts out of the old sleeve](https://posts.freesewing.org/uploads/sleeve_2fd77b450d.jpg) + +Suffice to say, it was stressful. And after I had puzzled together the initial parts, I still had to -- you know -- make a jacket. +Which was kinda challenging with all that stripe matching I needed to do. + +![Construction slowly moving forward](https://posts.freesewing.org/uploads/front_9821526627.jpg) + +![Preparing the patch pockets](https://posts.freesewing.org/uploads/pocket_db7596902d.jpg) + +## Final notes + +I ran out of time to add the lining, but part of me feels it would be a shame to cover up the insanity that is the inside of the jacket. + +And I'm not entirely pleased with the collar. I had made one muslin test garment, but now that I've made the real thing, I am going to go back to the pattern and make some tweaks before releasing it. + +In the meanwhile, enjoy some [more pictures of the jacket in this Flickr set](https://www.flickr.com/photos/__niki__/albums/72157684742893052). + +## Now it's your turn + +So this is it, my contribution for The Refasioners 2017. I hope I was able to inspire you for some refashioning of your own. +If nothing else, maybe it was a good reminder of what not to try ;) + + +> ##### More refashioners +> To stay up to date with The Refashioners 2017, see all the other inspiring refashions AND +> find out how you could win an amazing prize go to: [www.makery.uk/the-refashioners/](http://www.makery.uk/the-refashioners/) + diff --git a/markdown/org/blog/the-refashioners-2017/fr.md b/markdown/org/blog/the-refashioners-2017/fr.md new file mode 100644 index 00000000000..0710daa42a8 --- /dev/null +++ b/markdown/org/blog/the-refashioners-2017/fr.md @@ -0,0 +1,158 @@ +--- +author: "joostdecock" +caption: "They said I was crazy to make a zebra jacket, so I made it anyway. And it sank into the swamp." +date: "2017-09-04" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/35dda6f4c8ec6f2689e2741cc49cf178e4a39474-3300x2200.jpg" +intro: "For the uninitiated, the refashioners is a yearly event/competition hosted by the charming (and very persuasive) Portia Lawrie ." +title: "The Refashioners 2017 - Now with a Blake Blazer preview and 100% more zebra [Non traduit]" +--- + +For the uninitiated, the refashioners is a yearly event/competition hosted by the charming (and very persuasive) +[Portia Lawrie](http://www.makery.uk/). + +Its focus is on giving old, unworn, or unloved garments a new lease on life through the art of refashioning. + +This bonanza of garment Frankensteining kicks of with a series of *hors-compétition* makes, aimed at getting +the creative juices flowing. And [just like last year](http://www.makery.uk/2016/08/the-refashioners-2016-joost/), +I got asked to be one of those *warm-up acts*. + +Before I talk a bit about how it went, here's some pictures of what I made: + +![Yup, defenitely a zebra jacket](https://posts.freesewing.org/uploads/zebra1_f856635d39.jpg) + +![A view of the back](https://posts.freesewing.org/uploads/zebra2_c1df8979c5.jpg) + +![Stripe matching with sleevecap ease is tricky](https://posts.freesewing.org/uploads/zebra3_db4d55ad19.jpg) + +![A look at the insanity that lies beneath](https://posts.freesewing.org/uploads/zebra4_154c70b269.jpg) + +![Recycled buttons](https://posts.freesewing.org/uploads/zebra5_139563ceb2.jpg) + +![I case you missed it, this jacket comes with patch pocket](https://posts.freesewing.org/uploads/zebra6_34df45c31e.jpg) + +## The male romper lobby +Last year, the theme was jeans, this year it's suits. And from the moment I shared that snippet of info +with a handful of friends, they've conspiring to get me to make a male romper. + +![Sorcha trying to get me to make a romper](https://posts.freesewing.org/uploads/romper_chat_6cf0df4477.png) + +![Anneke trying to help by sketching a romper for me](https://posts.freesewing.org/uploads/romper_sketch_09c8005525.jpg) + +With friends like that, who needs enemies. + +## How I got to zebra + +The first thing I did was limit my options. Too much choice tends to paralize. + +I decided to not only respect the suit theme with regards to the source material, but also concerning the techniques involved. +Making a suit, and especially jacket construction, is a fine art and I wanted that to be part of my project. + +So, no messenger bags or (dare I say it) shoes out of recycled suits, I wanted to make a jacket. + +The problem is that suits are rather challenging to refashion. There's just not a lot of large pieces of pristine fabric to work with. + +![The front part of a jacket does not leave you with a lot to work with](https://posts.freesewing.org/uploads/front_part_4401c51b7b.jpg) + +In addition, I'm really tall so there is simply no way I can salvage enough fabric form a suit to make a new jacket +without having to sew a bunch of scraps together. + +I was worried that this sort of patchwork jacket was going to look super hobo. +But since I don't really have any other option to make a jacket, I started thinking about what sort of patchwork would be most acceptable. + +![Eurek(zebr)a!](https://posts.freesewing.org/uploads/real_zebra_b1decba3b1.jpg) + +And then one day in the shower it hit me: zebra! If I could find a black and a white suit, I could cut them into stripes +and join those together to form the pattern parts I needed. If it was going to be patchwork, I might as well embrace it, right? + +## The Blake Blazer pattern + +My first idea was to make a jacket in muslin, draw zebra stripes on it, take it apart, cut out the stripes, and use that as my pattern. +But I was worried this process would not be precise enough. + +Also, what pattern would I use to make the jacket in the first place? I don't really use patterns that I haven't designed myself +because I'm more of an uphill ice-skating kinda guy. + +![Some mofos are always trying to ice-skate uphill](https://posts.freesewing.org/uploads/ice_skating_uphill_80ab69e9bd.gif) + +So, I set out to design the Blake Blazer. It's a jacket/sportscoat pattern that I initially hoped to release with this post, but +you're going to have to give me some more time for that. + +![The early draft of the Blake Blazer that I used for this jacket](https://posts.freesewing.org/uploads/blake_f3e813a99d.svg) + +To get those zebra stripes as precise as possible, I decided to add the stripes to the pattern. +This way, I could make sure they would match and whenever they don't in the jacket, I've got my own shoddy workmanship to blame. + +Also, for this project, I decided to make it a bit of a cropped look because I was worried I wouldn't have enough fabric to work with. + +## Finding suits to refashion + +With my pattern sorted, I started looking into the source material for my make. +As it happens, I have a cardboard box full of old and unloved suits that's still in storage since my last move. + +I've always intended to take these apart to learn from their construction so this was the perfect opportunity. + +![A box of suits to reverse engineer](https://posts.freesewing.org/uploads/suits_box_434d198619.jpg) + +![Treasure!](https://posts.freesewing.org/uploads/suits_inside_0637374422.jpg) + +I have two black suits to choose from, but absolutely no white suits. So I hit the thriftstores only to discover that white suits are a bit of a rarity. + +I was unable to find any white suit even though I visited 8 different thrift stores. To make matters worse, I couldn't even find a +white suit in any of the second hand stores I visited with one exception: I found a white suit in a second hand store, but it was 200 euro. + +Apart from the fact that I'm not made of money, I don't think buying a 200 euro second hand suit only to rip it apart is much in line with the spirit +of the refashioners. + +I briefly contemplated a different colour combination, but nobody is waiting for a black and navy zebra. + +![I ended up using the one on the left](https://posts.freesewing.org/uploads/suits_black_53828cb3ec.jpg) + +![Never a good sign when things are secured with a steel cable](https://posts.freesewing.org/uploads/suits_white_c02d4bf0c8.jpg) + +Fortunately, the rules of the refashioners are that at least 50% of your make should be recycled suits. Apart from that, you do what you want. + +So, by making the black stripes dominant, making the entire facing out of black, and recycling the inner parts of the suit (think canvas, shouler padding, buttons and so on) I would have no problem reaching that 50% treshold. + +So, true to the thrifty spirit of refashioners, I picked up some white fabric in the haberdasher that was 4 euro per meter. +Something that I would soon regret as I tried to make this piece of glorified plastic play nice with the wool of the black suit. + +## Putting it all together + +I wanted the zebra stripes to look like a real zebra, so no straight lines. I addition, I noticed that a zebra's stripes don't continue on his back and belly +but sort of a run before they hit the center. I wanted to replicate that look, and lived to regret it. + +![These scraps are waiting to become an undersleeve](https://posts.freesewing.org/uploads/sleeve_parts_052a369ca4.jpg) + +I ended up having to hand baste all the different parts together. This jacket's outer shell is made up of 93 different scraps and pieces that are all puzzled together. + +![This are not scraps to be thrown out, but scraps to be made into a jacket](https://posts.freesewing.org/uploads/scraps_412f72f0f2.jpg) + +In addition, I had to squeeze all the new parts out of the old suit parts, which meant that in some cases I was left with as little as a few mm of seam allowance. + +![Cutting the new sleeve parts out of the old sleeve](https://posts.freesewing.org/uploads/sleeve_2fd77b450d.jpg) + +Suffice to say, it was stressful. And after I had puzzled together the initial parts, I still had to -- you know -- make a jacket. +Which was kinda challenging with all that stripe matching I needed to do. + +![Construction slowly moving forward](https://posts.freesewing.org/uploads/front_9821526627.jpg) + +![Preparing the patch pockets](https://posts.freesewing.org/uploads/pocket_db7596902d.jpg) + +## Final notes + +I ran out of time to add the lining, but part of me feels it would be a shame to cover up the insanity that is the inside of the jacket. + +And I'm not entirely pleased with the collar. I had made one muslin test garment, but now that I've made the real thing, I am going to go back to the pattern and make some tweaks before releasing it. + +In the meanwhile, enjoy some [more pictures of the jacket in this Flickr set](https://www.flickr.com/photos/__niki__/albums/72157684742893052). + +## Now it's your turn + +So this is it, my contribution for The Refasioners 2017. I hope I was able to inspire you for some refashioning of your own. +If nothing else, maybe it was a good reminder of what not to try ;) + + +> ##### More refashioners +> To stay up to date with The Refashioners 2017, see all the other inspiring refashions AND +> find out how you could win an amazing prize go to: [www.makery.uk/the-refashioners/](http://www.makery.uk/the-refashioners/) + diff --git a/markdown/org/blog/the-refashioners-2017/nl.md b/markdown/org/blog/the-refashioners-2017/nl.md new file mode 100644 index 00000000000..64599ebe781 --- /dev/null +++ b/markdown/org/blog/the-refashioners-2017/nl.md @@ -0,0 +1,158 @@ +--- +author: "joostdecock" +caption: "They said I was crazy to make a zebra jacket, so I made it anyway. And it sank into the swamp." +date: "2017-09-04" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/35dda6f4c8ec6f2689e2741cc49cf178e4a39474-3300x2200.jpg" +intro: "For the uninitiated, the refashioners is a yearly event/competition hosted by the charming (and very persuasive) Portia Lawrie ." +title: "The Refashioners 2017 - Now with a Blake Blazer preview and 100% more zebra [Niet vertaald]" +--- + +For the uninitiated, the refashioners is a yearly event/competition hosted by the charming (and very persuasive) +[Portia Lawrie](http://www.makery.uk/). + +Its focus is on giving old, unworn, or unloved garments a new lease on life through the art of refashioning. + +This bonanza of garment Frankensteining kicks of with a series of *hors-compétition* makes, aimed at getting +the creative juices flowing. And [just like last year](http://www.makery.uk/2016/08/the-refashioners-2016-joost/), +I got asked to be one of those *warm-up acts*. + +Before I talk a bit about how it went, here's some pictures of what I made: + +![Yup, defenitely a zebra jacket](https://posts.freesewing.org/uploads/zebra1_f856635d39.jpg) + +![A view of the back](https://posts.freesewing.org/uploads/zebra2_c1df8979c5.jpg) + +![Stripe matching with sleevecap ease is tricky](https://posts.freesewing.org/uploads/zebra3_db4d55ad19.jpg) + +![A look at the insanity that lies beneath](https://posts.freesewing.org/uploads/zebra4_154c70b269.jpg) + +![Recycled buttons](https://posts.freesewing.org/uploads/zebra5_139563ceb2.jpg) + +![I case you missed it, this jacket comes with patch pocket](https://posts.freesewing.org/uploads/zebra6_34df45c31e.jpg) + +## The male romper lobby +Last year, the theme was jeans, this year it's suits. And from the moment I shared that snippet of info +with a handful of friends, they've conspiring to get me to make a male romper. + +![Sorcha trying to get me to make a romper](https://posts.freesewing.org/uploads/romper_chat_6cf0df4477.png) + +![Anneke trying to help by sketching a romper for me](https://posts.freesewing.org/uploads/romper_sketch_09c8005525.jpg) + +With friends like that, who needs enemies. + +## How I got to zebra + +The first thing I did was limit my options. Too much choice tends to paralize. + +I decided to not only respect the suit theme with regards to the source material, but also concerning the techniques involved. +Making a suit, and especially jacket construction, is a fine art and I wanted that to be part of my project. + +So, no messenger bags or (dare I say it) shoes out of recycled suits, I wanted to make a jacket. + +The problem is that suits are rather challenging to refashion. There's just not a lot of large pieces of pristine fabric to work with. + +![The front part of a jacket does not leave you with a lot to work with](https://posts.freesewing.org/uploads/front_part_4401c51b7b.jpg) + +In addition, I'm really tall so there is simply no way I can salvage enough fabric form a suit to make a new jacket +without having to sew a bunch of scraps together. + +I was worried that this sort of patchwork jacket was going to look super hobo. +But since I don't really have any other option to make a jacket, I started thinking about what sort of patchwork would be most acceptable. + +![Eurek(zebr)a!](https://posts.freesewing.org/uploads/real_zebra_b1decba3b1.jpg) + +And then one day in the shower it hit me: zebra! If I could find a black and a white suit, I could cut them into stripes +and join those together to form the pattern parts I needed. If it was going to be patchwork, I might as well embrace it, right? + +## The Blake Blazer pattern + +My first idea was to make a jacket in muslin, draw zebra stripes on it, take it apart, cut out the stripes, and use that as my pattern. +But I was worried this process would not be precise enough. + +Also, what pattern would I use to make the jacket in the first place? I don't really use patterns that I haven't designed myself +because I'm more of an uphill ice-skating kinda guy. + +![Some mofos are always trying to ice-skate uphill](https://posts.freesewing.org/uploads/ice_skating_uphill_80ab69e9bd.gif) + +So, I set out to design the Blake Blazer. It's a jacket/sportscoat pattern that I initially hoped to release with this post, but +you're going to have to give me some more time for that. + +![The early draft of the Blake Blazer that I used for this jacket](https://posts.freesewing.org/uploads/blake_f3e813a99d.svg) + +To get those zebra stripes as precise as possible, I decided to add the stripes to the pattern. +This way, I could make sure they would match and whenever they don't in the jacket, I've got my own shoddy workmanship to blame. + +Also, for this project, I decided to make it a bit of a cropped look because I was worried I wouldn't have enough fabric to work with. + +## Finding suits to refashion + +With my pattern sorted, I started looking into the source material for my make. +As it happens, I have a cardboard box full of old and unloved suits that's still in storage since my last move. + +I've always intended to take these apart to learn from their construction so this was the perfect opportunity. + +![A box of suits to reverse engineer](https://posts.freesewing.org/uploads/suits_box_434d198619.jpg) + +![Treasure!](https://posts.freesewing.org/uploads/suits_inside_0637374422.jpg) + +I have two black suits to choose from, but absolutely no white suits. So I hit the thriftstores only to discover that white suits are a bit of a rarity. + +I was unable to find any white suit even though I visited 8 different thrift stores. To make matters worse, I couldn't even find a +white suit in any of the second hand stores I visited with one exception: I found a white suit in a second hand store, but it was 200 euro. + +Apart from the fact that I'm not made of money, I don't think buying a 200 euro second hand suit only to rip it apart is much in line with the spirit +of the refashioners. + +I briefly contemplated a different colour combination, but nobody is waiting for a black and navy zebra. + +![I ended up using the one on the left](https://posts.freesewing.org/uploads/suits_black_53828cb3ec.jpg) + +![Never a good sign when things are secured with a steel cable](https://posts.freesewing.org/uploads/suits_white_c02d4bf0c8.jpg) + +Fortunately, the rules of the refashioners are that at least 50% of your make should be recycled suits. Apart from that, you do what you want. + +So, by making the black stripes dominant, making the entire facing out of black, and recycling the inner parts of the suit (think canvas, shouler padding, buttons and so on) I would have no problem reaching that 50% treshold. + +So, true to the thrifty spirit of refashioners, I picked up some white fabric in the haberdasher that was 4 euro per meter. +Something that I would soon regret as I tried to make this piece of glorified plastic play nice with the wool of the black suit. + +## Putting it all together + +I wanted the zebra stripes to look like a real zebra, so no straight lines. I addition, I noticed that a zebra's stripes don't continue on his back and belly +but sort of a run before they hit the center. I wanted to replicate that look, and lived to regret it. + +![These scraps are waiting to become an undersleeve](https://posts.freesewing.org/uploads/sleeve_parts_052a369ca4.jpg) + +I ended up having to hand baste all the different parts together. This jacket's outer shell is made up of 93 different scraps and pieces that are all puzzled together. + +![This are not scraps to be thrown out, but scraps to be made into a jacket](https://posts.freesewing.org/uploads/scraps_412f72f0f2.jpg) + +In addition, I had to squeeze all the new parts out of the old suit parts, which meant that in some cases I was left with as little as a few mm of seam allowance. + +![Cutting the new sleeve parts out of the old sleeve](https://posts.freesewing.org/uploads/sleeve_2fd77b450d.jpg) + +Suffice to say, it was stressful. And after I had puzzled together the initial parts, I still had to -- you know -- make a jacket. +Which was kinda challenging with all that stripe matching I needed to do. + +![Construction slowly moving forward](https://posts.freesewing.org/uploads/front_9821526627.jpg) + +![Preparing the patch pockets](https://posts.freesewing.org/uploads/pocket_db7596902d.jpg) + +## Final notes + +I ran out of time to add the lining, but part of me feels it would be a shame to cover up the insanity that is the inside of the jacket. + +And I'm not entirely pleased with the collar. I had made one muslin test garment, but now that I've made the real thing, I am going to go back to the pattern and make some tweaks before releasing it. + +In the meanwhile, enjoy some [more pictures of the jacket in this Flickr set](https://www.flickr.com/photos/__niki__/albums/72157684742893052). + +## Now it's your turn + +So this is it, my contribution for The Refasioners 2017. I hope I was able to inspire you for some refashioning of your own. +If nothing else, maybe it was a good reminder of what not to try ;) + + +> ##### More refashioners +> To stay up to date with The Refashioners 2017, see all the other inspiring refashions AND +> find out how you could win an amazing prize go to: [www.makery.uk/the-refashioners/](http://www.makery.uk/the-refashioners/) + diff --git a/markdown/org/blog/v2-22-then-v3/en.md b/markdown/org/blog/v2-22-then-v3/en.md new file mode 100644 index 00000000000..c2804beaadc --- /dev/null +++ b/markdown/org/blog/v2-22-then-v3/en.md @@ -0,0 +1,27 @@ +--- +author: "joostdecock" +caption: "We're moving on" +date: "2022-08-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6a5739e3f4ab7694fdd0d1f46c9ec7ecd4c6431b-1920x1280.jpg" +intro: "We have released version 2.22 of FreeSewing. As always, a minor version bump indicates a new design, and this time it's the Octoplushy design by Wouter." +title: "FreeSewing v2.22 is out, and will be the final minor release before v3" +--- + +We have released version 2.22 of FreeSewing. As always, a minor version bump indicates a new design, and this time it's the [Octoplushy design](/designs/octoplushy) by Wouter. + +Version 2.22 is planned to be the last minor release in the v2 branch. Momentum for version 3 has been building for a while, and during [this weekend's contributor call](https://github.com/freesewing/freesewing/discussions/2582) we decided we'd double down on those efforts and focus all our attention on the upcoming version 3. + +## What does this all mean? + +In the short term, you might not even notice. FreeSewing.org will continue running the production-ready v2 code, while we start building version 3. + +For developers and/or pattern designers, the situation is different. Effective immediately, our (default) `develop` branch in [our monorepo](https://github.com/freesewing/freesewing) is where we'll be working on version 3 code. +Version 2 code is now in the `v2` branch where will will backport fixes for as long as version 3 is under development. + +To keep up to date of all changes, please refer to [freesewing.dev](https://freesewing.dev) where we will over time document everything you need to know about the migration. + +## When can we expect version 3? + +We have a lot of exciting plans, but they will take some time to manifest. I suspect the first production release of version 3 code, and the rollout on FreeSewing.org will be a matter for 2023. + + diff --git a/markdown/org/newsletter/2021q2/en.md b/markdown/org/newsletter/2021q2/en.md new file mode 100644 index 00000000000..25696d762d5 --- /dev/null +++ b/markdown/org/newsletter/2021q2/en.md @@ -0,0 +1,416 @@ +--- +date: "2021-04-01" +edition: "2021q2" +intro: "Welcome to the 2021 Spring edition of the FreeSewing newsletter. Here's what we have included for you:" +title: "2021 Spring edition" +--- + +Welcome to the 2021 Spring edition of the FreeSewing newsletter. +Here's what we have included for you: + +- 👕 Pattern releases winter 2021 (1-minute read - by Joost) +- 🕵️ Behind the seams: Wouter van Wageningen (9-minute read - by An & Wouter) +- 🔍 Spotlight on some lesser-know FreeSewing features (3-minute read - by Joost) +- 🤯 Some of the more crazy ideas on our drawing board (3-minute read - by Joost) +- ❤️ FreeSewing is brought to you by the kindness of strangers (5-minute read by Joost) + +We hope you enjoy it. +If not, mash that reply button and tell us what you'd like to read instead ¯\\\_(ツ)\_/¯ + +  + +  + + + +# 👕 Pattern releases winter 2021 + +Here's a quick recap of the new patterns we released in the first quarter of this year: + + - [The Bella bodice block for womenswear](https://freesewing.org/blog/bella-bodice-block/): A collaboration with somebody from the industry to replicate the kind of bodice block that's used in fashion today. Currently it has a bust dart towards the side-seam. A variation with a shoulder dart is on our todo list. + - [The Hortensia handbag](https://freesewing.org/blog/announcing-hortensia/): Another collaboration, this time between Stofsuchti and long-time contributor Wouter Van Wageningen brought the first handbag pattern to FreeSewing. + - [The Cornelius cycling breeches](https://freesewing.org/blog/cornelius-cycling-breeches/): More from Wouter still, these cycling breeches or knickerbockers are based on the Keystone drafting method. + +Click through any of the links for the blog posts announcing these patterns. + + +  + +--- + +  + +# 🕵️ Behind the seams: Wouter van Wageningen + +> *With two pattern releases to his name in the last 3 months,* +> *who better to shine a spotlight on than long time contributor Wouter.* +> +> *An — one of our newer contributors — interviewed him for this newsletter:* + +## Bio + +Born in the Netherlands and lived there for 30 years before moving to “the States”. +He accompanied his American wife when she wanted to return and has been living there for +over 20 years. He now considers it his home, while recognizing all the emotional ties to +The Netherlands when he goes back to visit. + +While a busy IT manager, he likes to create new patterns for FreeSewing from time to time. + +## How did you learn about freesewing? + +When I started sewing many years ago, I was continuously looking for patterns for men. +The site of Joost, Makemypattern (since late 2012), came up in one of my searches, and +I thought it was an interesting concept. + +## How did you become a contributor? + +In the beginning, there were no contributors other than Joost, that I remember. He had +made this framework that allowed other people to make patterns that could be incorporated. +Being a programmer, as a professional and hobbyist, this intrigued me. The originally site +was created in the PHP programming language, one I had not worked with before. I thought +this made for an interesting challenge to contribute to the work of Joost. + +As this was my first experience with the toolset, the language, and making patterns, +I picked something as easy as [a bow tie](https://freesewing.org/designs/benjamin/). +It is a simple object, as it is flat with a width and a height, but no real depth. +Therefore, I didn’t have to try to shape a piece of fabric around a 3D shape. The result passed the muster of Joost, and became an official pattern on the site. + +Before finding FreeSewing, I had drawn a pencil skirt for my partner by just using +her measurements. I realized while working on the bow tie that I could try to combine +the experience of making this skirt with that of making the pattern for the bow tie, and +make another pattern for FreeSewing. +Thus, [the Penelope pencil skirt](https://freesewing.org/designs/penelope/) was born. + +## What has been your contributor work so far? + +I have created [the Waralee wrap pants](https://freesewing.org/designs/waralee/), +[Albert apron](https://freesewing.org/designs/albert/), and [Cornelius cycling breeches](https://freesewing.org/designs/cornelius/). +I also did the implementation of [the Hortensia handbag](https://freesewing.org/designs/hortensia/), but that is not my design. I got the drawings and measurements from the designer (Stoffsuchti), and translated those +into a FreeSewing pattern. + +The Benjamin bow tie was totally my own creation, exactly as I imagined what it should look. +The Penelope and Waralee designs were built from the knowledge I gathered by reading about those types of garments, and implementing my interpretation of them. +The Cornelius is actually an implementation of a pattern in an existing drafting system (The "Keystone" System). + +## When and why did you start sewing? + +Seven or eight years ago, I wanted to know what it would be like to wear a kilt. But +kilts are insanely expensive. They are made of very nice wool and it takes an enormous amount of time to make a real Scottish kilt. There are these “utility kilts”, which are basically cargo pants made into a kilt. More +practical with pockets, and made out of cotton, but they still cost around $200. + +Because I was still figuring out whether I would enjoy wearing a kilt, it didn't make much sense to me to invest that much. While researching this I found [a website dedicated to people wearing kilts](http://www.xmarksthescot.com/), and it had a documented process on how to create your own utility kilt. +I did have a sewing machine, it seemed within my abilities, so I bought some fabric and started sewing. +One kilt became two, and then I figured I needed a shirt to go along with it. It should be somewhat +contemporary to old kilts. With a little searching I found a pattern to make such a shirt. And that led to making more and more shirts, and then pants and... + +At one point I decided that I wasn't going to buy any more clothes, I was just going to make them. +One exception to that are underwear and socks, as these don’t give me much pleasure in making them, and are usually ridiculously cheap. I have knitted a pair of socks, and I like knitting a lot. I just don't seem to be able to knit fast enough to keep up with the wear and tear. +The other exception is athletic or technical clothing, as I just cannot buy the fabrics (e.g. eVent) you need for it. +These are exclusively sold to vendors of this type of clothing. I have recently made some yoga pants and biking shorts for myself, so this may change. + +## What is your daily job, outside of freesewing? + +IT manager. I take care of the IT needs for a union of homecare workers. + +## What are you currently working on? + +Nothing for FreeSewing at the moment, but I am looking into the possibility to make a pattern based +on the trouser block. That way, I don't have to start from scratch as I usually do, and just extend +Joost's work. I'm looking forward to trying this approach, but I first have to complete my doublet. + +## Which project did you just finish? + +The [Cornelius cycling breeches](https://freesewing.org/designs/cornelius/) and the implementation of [the Hortensia handbag](https://freesewing.org/designs/hortensia/). + +## What sewing project are you most proud of? + +I'm proud of a lot of projects; my first shirt (even though it has a lot of faults), my first tailored coat, all of my art shirts, … +But if I had to pick one, it would probably be [my Mondrian shirt](https://shirtartistry.blog/2019/01/23/mondrian-shirt-the-beginning/). It was the one where I went all the way from a concept in my mind, though creating it on paper, to turning it into a garment. + +## What in your life are you most proud of? + +Everybody will answer that with something like 'my children'. And I am proud of the persons they've become. +But I think that is more something they have done, than what I have done. I was just there to help +them when needed. One of the things I've done that I'm proud of is having been a volunteer firefighter for 10 years. +And, for the last 20 years or so, I've worked for nonprofits trying to make the world a better place. + +## What do you love the most about sewing? + +The creativity. I like to make things. I discovered that with sewing, in contrast to things like wood or metal working, I can be really precise. And I can find the patience in myself to create that precision. +What’s more, if I make a mistake, I can usually undo it (e.g. take the seam out). It's a lot harder to take things apart once you've glued them together. +I also like that I can make something that is a flat drawing on a piece of paper into something that is a +real three dimensional thing, by turning those patterns into pieces of fabric and sewing them together. +Even the trail and error process to adapt a pattern to my needs, or to create a new pattern from scratch, is interesting to me. It's a discovery journey with practical outcomes. +And, although I'm not good at all of the required skills, I can do most of them well enough that I can go from something in my head to something that I can wear, and that is very satisfying. + +## What do you hate the most about sewing? + +I am a bit too impatient to do large parts of sewing by hand, and that is my least favorable part of sewing. The occasional basting is fine, it is the sewing of a full seam by hand that is beyond me. +I have made buttonholes by hand on my tailored jacket, and that was satisfying by itself. Yet it takes too much time +and it doesn't fascinate me enough to allow me to become good at it. It'll most likely take a long time before I’ll do it again. For some reason I don't mind doing the pad stitching for lapels and such on tailored jackets. + +## What’s the hardest part of sewing to you? + +It is nearly impossible for me to draw the mental picture that is in my head on a piece of paper. I'm really +bad at drawing free form. Because of this, I cannot, not even temporarily, put the end result of a certain clothing design on a piece of paper to look at it. And therefore I cannot get someone else’s opinion or input on it +before I create it. It is frustrating. + +## What would be your advice for starting sewists/sewistas? + +First of all, go for it and concentrate on the parts of the sewing process you enjoy. Look at the big +picture of creating a garment for yourself, and let that motivate you to get through the parts you +don't like so much. + +Secondly, just keep going and don’t look at things that didn't work out so well too much. Everything +takes practice, and you will get better at it. Break up things into smaller parts and think about +what you can do to improve that one part. Maybe there's a different way to do this step that works +better for you. + +Lastly, don’t be intimidated by patterns. Try different patterns, designers, and techniques. Pick out what works for you. All designers have their own way of doing certain things, and they may not always align with your strengths and weeknesses. I always +do a zipper fly the same way, regardless of what the designer suggested. My way works for me and +gives me good results. Others may prefer other techniques, so find your own by trying a lot of different ways. + +And most of all; enjoy the process of creating. The end product is an additinal benefit. Through the enjoyment of the process, you will gain the experience to get good at it. And with that, you will get the garments you like. + +## Are you married? + +Not anymore, after 25 years we amicably split up. I have a new partner now. + +## Do you have children? + +Five in total, two adult children of myself and three almost adults of my partner. + +## Are you a dog person or a cat person? + +I am a dog person, but I don’t have a dog anymore. + +## Do you have pets? + +I have had three dogs. I would enjoy having a dog, but my current life style and freedom to travel does not match up with having one. + +## If there was one thing you could take with you to an uninhibited island what would it be? Why? + +A knife, because it seems to be the most useful item to help me survive. + +## If there was one person you could take with you to an uninhibited island, who would it be? Why? + +Nobody, since I could not forgive myself for putting someone else through the same ordeal. +I love what thousands of years of society has brought us, and I don't want to be without its fruits. So it would be cruel for me to subject someone else to this punishment. + + +  + +--- + +  + + +# 🔍 Spotlight on some lesser-know FreeSewing features + +Regardless of whether you've only recently discovered FreeSewing, or have been a user for many years, here are some things you might not have discovered on your own: + +## Multilingualism + +FreeSewing is available in 5 languages, each with their own website. In addition to [English at freesewing.org](https://freesewing.org/), we have websites in [French](https://fr.freesewing.org/), [German](https://de.freesewing.org/), [Dutch](https://nl.freesewing.org/), and [Spanish](https://es.freesewing.org/). + +If you'd like to help us add more languages, [get in touch](https://discord.freesewing.org/). +## Paperless patterns + +Not a fan of printing and sticking pages together? Or perhaps you don't have a printer? Don't despair, because FreeSewing provides **paperless patterns**. + +You'll find the **paperless** option under the **Pattern options**. Flick it on and now you'll have dimensions as well as a grid in either metric or imperial so you can transfer your pattern directly to fabric or another medium like pattern paper. + +## Custom layout/tiler + +Laying out the different pattern parts on your pattern happens automatically. But alas, it's one of those things that computers are far worse at that humans. Often you can save a bunch of pages by squishing things together yourself. If only you could, right? + +Turns out you can. Simply **Export** your pattern as **SVG** and fire up **Inkscape** (which you can [download for free](https://inkscape.org/)). + +When you open the pattern in Inkscape, the entire pattern will be in a *group*, so first thing to do is to **select** it and **right-click** and choose **ungroup**. Now you can rotate and flip each part around and arrange them just as you like. When you're happy, click **File** -> **Document properties** and choose **Resize page to content**. + +When you're done, save the SVG and upload it to our custom tiler: https://tiler.freesewing.org/ +There you can upload the SVG and pick your page size, and you'll get a PDF just like on the website. Only this time, with your own layout 👍 + +## Remove details from a pattern + +This option was originally intended for laser cutters, but has other uses too. + +For this, you'll have to enable so-called **Expert mode**. Under **Pattern options**, click **Expert mode** and set it to **Show**. +Now, you'll have the **Advanced** option under which you'll find **Detail**. If you set it to **Hide**, your pattern will not only show the outline of the different pattern parts. + +This is also handy for when you are making doll clothes as the titles, logo, and size box end up being taking up more space than the pattern itself. + +## Include only certain pattern parts + +Since we've unlocked **Expert mode**, here's another tip you mightn't be aware of: the **Contents** option. This option allows you to not draft the entire pattern, but only those parts that you want. + +This can be handy if you want to make a change to a pattern and only print those parts that are affected. But also if you want to combine different styles. For example you can generate a complete Simon pattern, and then additional collar or cuff styles where only the collar/cuffs are included in the pattern. + +Got an idea for some other cool feature you'd like to see? Make sure to [let us know](https://discord.freesewing.org/). + + +  + +--- + +  + + +# 🤯 Some of the more crazy ideas on our drawing board + +We're rarely stuck for things to do, because some work is never finished: adding more patterns, writing more or better documentation, improving user experience, and so on. + +But sometimes, we also like to shoot the breeze and come up with some ideas that are a bit off the beaten path. Here's a selection of them that we've been mulling over. Don't consider it a sneak preview though, some of these are bona fide moonshots: + +## Allowing users to create their own pattern layouts on the site + +The pattern layout — the way the individual pattern pieces are laid out on the page — seems like the low-hanging fruit of improvements. Almost without exception, your pattern will not be the most optimal layout. + +Thing is, computers are not very good at this sort of spacial problem that's called *packing*. We could try to tweak the algorithm, but human beings are just intuitively better at it than computers are. + +**The goal** +To make it possible (and ideally easy) for people to do their own layout. So that before you export your pattern, you have the option to arrange it just as you like it. + +**What it would take** +This is something that's been on the drawing board for quite some time. FreeSewing core already has support for custom layouts, so it's really *just* a matter of creating the frontend interface to handle the layouting. + +**Roadblocks** +Doing the SVG layout on mobile is a minefield. + +**Chances of this happening** +High. We're almost certainly going to do this at some point. + +## Using 3D renders to showcase patterns or options + +3D in general is something we have our eye on, but in this case it's really about presenting the patterns to the user. People want to know what they're going to get, and line drawings and showcases can only go so far to show that. + +The idea would be to be able to show patterns on a 3D avatar. However, a big caveat is that we would have to be able to somehow automate this process since we can't go manually creating a 3D render of every pattern & option. + +**The goal** +Create 3D renders of different patterns and the effect of pattern options. Integrating this with our build pipeline so those renders can be auto-generated. + +**What it would take** +Some work has been done already. Last year we wrote a DXF-exporter plugin that can export patterns as DXF, a popular format in 3D tools. We did some initial tests with CLO3D but the lack of automation options not to mention the fact that it's a closed-source commercial product made us abandon that path. + +The right thing to do would be using Blender so that this work would benefit the open source community. + +**Roadblocks** +Blender is not that easy to learn. Automation and plugins in Blender need to be written in Python, and we're a JavaScript project. Basically, we have nobody who knows how to even start on this today. + +**Chances of this happening** +Medium. Could really use some help on this. + +## Frankenstein patterns + +The name *Frankenstein pattern* is something that came up during one of our contributor calls, and the name sort of stuck. The idea is that you could mix and match parts from different patterns to create your own combinations. Like, pick a top and combine it with the sleeves from another top and perhaps the collar from yet another top. + +**The goal** +Allow patterns to be created by combining different building blocks. + +**Roadblocks** +This would require some sort of inter-pattern API or interface specification. + +**Chances of this happening** +Low. For pattern developers, combining parts from different patterns is already possible via inheritance. Exposing this sort of functionality to the user level would already be a significant challenge. But doing it in a way that requires no code and merely some clicking around is pretty far out there. + + +  + +--- + +  + + +# ❤️ FreeSewing is brought to you by the kindness of strangers + +On April 5th 2011, a Tuesday of all days, I published a sewing pattern on my blog. +BXR-M01A was a pattern for boxer briefs that came in one size only, and was free to download under a Creative Commons license. + +It was also the very first pattern I ever published. + +The event as such doesn’t deserve much attention, but it just happens to have occurred 10 years ago — almost to the day. +So it seemed a good starting point for a brief history of how we got from there to here. + +## The Early Days + +I started drafting my own sewing patterns because I had fitting issues with store-bought ones. +Drafting my own patterns held the promise of flawless fit with just a bit of effort (Oh, how naive I was!). +The fiddling about with paper had me bored in no time, so I set out to try to automate that part of the process. +I came up with a way to reduce the pattern to a number of steps, and abstract away the measurements. +Now, you could feed it whatever measurements you wanted, and it would re-draft the pattern for you. + +I launched the beta version of my little pattern machine in February of 2012. +It wasn’t an immediate success. +As a matter of fact, to the best of my knowledge, only one person ever tested it. +That person was Nico in Copenhagen (who I've sadly lost track of) who wrote: + +> *That is sooo cool.* +> *I will enter my thoughts about your project using your feed back thingy on the pattern web site.* +> *But you should know that the overall fit is amazing! I think I have a new favourite pattern :-)* + +## makemypattern.com + +One good review is perhaps not much to go on, but I found it rather encouraging and set out to walk this path a bit further. +Fast-forward six months and I’d rewritten the thing from scratch, and with four patterns available officially launched makemypattern.com in September of 2012. + +Things sort of trickled along as I added a pattern every now and then. +Then, in January 2014 I got an email from Tin Doan in Canada asking how they could donate to the site. +I sort of expected this to be some sort of scam, but I still answered the email asking “Are you for real?”. Tin answered: + +> *Yes Joost, I'm serious. Please kindly accept $200.00 from me.* + +Sure enough, I soon found myself at the receiving end of a $200 donation. +To this day, it remains the highest amount I've ever received in a single donation. + +This unexpected yet very tangible token of support felt like a fork in the road. +I'd been happy building this thing mostly as a learning experience. +Now it felt like perhaps it needed a bit more devotion and care. + +In retrospect, this point probably marks the end of my social life 😂 good thing I had found a partner by now (phew). + +## Pivot to Open Source and freesewing.org + +So of course I rewrote the whole thing — again — into what would turn out to be the last version of makemypattern.com. +By the summer of 2016, five years after my first pattern release, and four years after launching makemypattern.com, +my little hobby project had made a lot of headway, and I found myself at another turning point: +Keep doing what I'm doing, or try to break through the next barrier. + +Up until this point, I had been doing makemypattern.com on my own. +The code wasn’t even available. I wanted to make it into an open source project that people could contribute to. +But I had never started it with that ambition, and it was going to take some serious refactoring +to make it into something that people would be able to wrap their heads around. + +So I did exactly that, and in March 2017 I launched v1.0.0 of freesewing.org. +A new name (and logo) to mark the transition to an open source project. +This was a much more mature release, with a documented API and it led to the first patterns contributed by others. +It also came with a hat I hadn't worn before, open source maintainer. + +## FreeSewing v2.0.0: It's JavaScript Now + +During all this time, the world of frontend development had changed and we could do so much more in a browser. +Rather than picking a bunch of options and getting a pattern in the end, the idea of seeing +the pattern update in your browser as you changed options was — at least in theory — attainable now. + +With that goal in mind, I started over again, this time in JavaScript. +And in August of 2019 v2.0.0 landed on freesewing.org. +A complete rewrite in JavaScript with a new website to boot. + +Since then, I've been able to keep myself from rewriting the entire thing again 🤞 + +## The Family You Choose + +We're getting closer to present time, but there's one more moment that stands out for me, +and that's a blog post from August 2020 where — maybe for the first time — I explicitly asked for help to grow the project. +Since then, a community has developed around FreeSewing that feels more valuable to me than any code I could ever write. + +Motivation is a powerful thing, and I wonder whether FreeSewing would exist today if it wasn't for the full-on enthusiasm of Nico in the early days. +Or whether it would have fizzled out without Tin injecting some rocket fuel in the form of a donation. +Or whether perhaps I would have succumbed to burnout by now if I hadn't found such a great group of people to walk this road with me. + +Speaking of which: There are countless individuals who have contributed to get to where we are today. +I couldn't possible mention them all. But what they have in common is that at one point, they were complete strangers to me, as I was to them. + +It’s the kindness of strangers that brought us here. + +Thank you strangers. + diff --git a/markdown/org/newsletter/2021q3/en.md b/markdown/org/newsletter/2021q3/en.md new file mode 100644 index 00000000000..63828d6b7fe --- /dev/null +++ b/markdown/org/newsletter/2021q3/en.md @@ -0,0 +1,299 @@ +--- +date: "2021-07-01" +edition: "2021q3" +intro: "Welcome to the 2021 Summer edition of the FreeSewing newsletter. Here's what we've included for you:" +title: "2021 Summer edition" +--- + +Welcome to the 2021 Summer edition of the FreeSewing newsletter. +Here's what we've included for you: + +- 🩲 Pattern releases spring 2021 (1-minute read - by Natalia) +- 👀 Help Sanne test her new bodice block (1-minute read - by Joost) +- 😢 Farewell David: Remembering David Page Coffin (2-minute read - by Joost) +- 🕵️ Behind the seams: An Gargouri (8-minute read - by Eleonore) +- 🤓 Git good: Let’s walk through a simple FreeSewing contribution together (2-minute read - by Natalia) +- ⚡ FreeSewing v2.16: This one's for the developers (1-minute read - by Joost) +- 🤷 Gender inclusivity (3-minute read - by Karen) + +We hope you enjoy it. +If not, mash that reply button and tell us what you'd like to read instead ¯\\\_(ツ)\_/¯ + + +  + +  + +# 🩲 Pattern releases spring 2021 + +Here's a quick recap of the new patterns we released in the second quarter of this year: + + - [The Ursula undies](https://freesewing.org/blog/announcing-ursula/): A highly-customizable underwear pattern with plenty of options to achieve different styles. This is my first pattern design. My hope is that Ursula will help you customize undies with the perfect look and fit for your own body. Interested in making a test pair and helping to refine the pattern? I'd love to chat with you over in the [FreeSewing Discord](https://discord.freesewing.org/). + - [The Charlie Chinos trousers](https://freesewing.org/blog/announcing-charlie/): Joost designed a new trouser pattern that will adapt better to differently shaped bodies. Charlie has 31 options that allow you to configure your trousers so you get them just as you like. + +Click through either of the links for the blog posts announcing these patterns. + +  + +--- + +  + +# 👀 Help Sanne test her new bodice block + +Sanne is working on a bodice block that is based on her own drafting experience and the +techniques she learned. She's hoping to get some feedback from a couple of more testers, +particularly people with larger cup sizes. + +If you'd like to help out, you can [generate your own version of the block online](https://bodice-block-sannek.netlify.app/). + +  + +--- + +  + + +# 😢 Farewell David: Remembering David Page Coffin + +In early May, I received news of the passing of David Page Coffin. David was editor of Threads +Magazine back when animals could talk, and his books on making trousers and shirts adorns my +bookshelves, as I'm sure they do many others. +David was also a friend of FreeSewing, and he reached out to me a couple of years ago to discuss plans +he had for a new book. He wanted to make another book about shirts. Not so much about the basic grunt +work of making a shirt that fits. But more about all the little style variations and creative +embellishments one could add to a shirt to make it into something really special. + +Still, he also felt that somebody who would pick up a book about making shirts would also expect +to, you know, make a shirt from it. So he was wondering whether he could point them to FreeSewing's +Simon pattern instead of having to dedicate a section of the book to the basics. + +I really enjoyed talking to David at length about what he was working on, and his tacit endorsement +felt like a big deal from someone who would have no trouble getting his foot in the door of a +household-brand pattern company. + +Like so many other ideas and good intentions, this one too ended up in the time-deprived *maybe +one day* pile. + +Still, for a brief moment I was allowed to bask in the David's enthusiasm. It is a conversation I will +continue to cherish. And also one that made one thing painfully clear to me: He will be sorely missed. + + +  + +--- + +  + + +# 🕵️ Behind the seams: An Gargouri + +> *When we were discussing what kind of content we would like to create for* +> *the very newsletter you’re reading now, An didn’t have to think long.* +> *She wanted to interview as many contributors as she could, and share* +> *what she found out with you. Why? “I’m just a curious person”, she says.* +> *Which made us curious about her.* + +## How did you learn about FreeSewing? + +I only started sewing last year, so I’m still very much a beginner. +I started out with face masks and when those worked out okay, +I got excited and started on the most complicated dress pattern I could find. +Needless to say, that didn’t turn out great. So I backtracked and started looking for +sewing patterns with accompanying instruction videos. I mean, those are basically +free sewing lessons. Awesome, right? + +That’s how I found the pattern for +the [Bruce boxer briefs](https://freesewing.org/designs/bruce/) with Joost’s +video instructions. And honestly, once you understand how FreeSewing works, +how could you not get hooked? I started entering measurements and watching the magic happen. +I was so impressed that all of this was available for free, that I became a Patron. +Joost sent me an e-mail with a link to [FreeSewing’s Discord](https://discord.freesewing.org/) — +an online platform for community building — and that’s where +I found out about the contributor calls. Being a curious person, the rest is history! + +## How did you become a contributor? + +That happened sort of by accident. Like I said, I’m curious. +I wanted to know all about FreeSewing’s contributor team, so these interviews +were a great way to ask all my nosy questions. Maybe I got a bit carried away. +That [first interview with Wouter](https://freesewing.org/newsletter/2021q2/#%EF%B8%8F-behind-the-seams-wouter-van-wageningen) took +so much time! But I’m also not one to quit when I’ve started something, +so you’ll see more of these interviews in the next editions of the newsletter. +By the way, if anyone would like to be interviewed, I’m here and I can’t wait to hear everything you have to say! + +## What do you enjoy the most about your interviews with contributors? + +I especially love people’s answers to the question what they would take with them to an +uninhabited island. But I’m not giving anything away. You’ll have to wait to read the interviews yourself. + +## What would YOU take with you to an uninhabited island? + +Why didn’t I see this question coming?! I would take one of the books that I never get around to reading. +Let’s see … ‘Making History’ by Stephen Fry. Or wait, is there food on this island? I’m not going to +fish or anything, and I don’t think I’d be good at starting a fire. Maybe I should just take some canned food. +And I’ll need my meds. + +## And if you could take one person? + + +That’s easy. I’d take my husband, Bart. That would solve all my problems, anyway. +Bart will fish and hunt and light a fire. He can do anything. + +## Are you a sewist? A coder? Both? Neither? + +Right now, I’m mostly a sewist. I did try to learn coding 15 years ago. +That’s actually how I met my husband. And then, well, other priorities took over. +I can feel the itch to pick it up again now. FreeSewing has me excited about pattern drafting and coding. +I’d love to find out what I can do if I set my mind to it. + +## What are you working on right now? + +I’m proud to say I’ve just started using patterns without videos again and feeling good about it! +I just made a muslin for a pretty blouse with a cut-out and little buttons, and it’s looking good. +I’m going to have a go at it in my fashion fabric. You know, I’m a princess at heart. +I love girly dresses and blouses, especially those vintage styles with cinched waists. +Those aren’t the best silhouettes for me, though. That’s why I want to learn how to draft my own patterns. +I love the idea of turning 2D pieces into a 3D garment and making it fit my body. +I think that’s a really cool thing about sewing, by the way. +The pattern pieces can look like such a puzzle, but once you start putting it together, it suddenly turns into a garment. + +## Anything you dislike about sewing? + +Honestly? I dislike most of the process other than actually sewing the pieces together. +I also really hate cutting patterns out of fabric. That’s where Bart comes in, usually. +I tend to buy less fabric than I’ll actually need, but Bart is so good at pattern +tetris that he can make almost anything fit onto the fabric. + +## Any advice for fellow sewists? + +Just keep going. It can be so frustrating when things don’t work out the way you’d envisioned. +But you just have to wait for things to ‘click’. And they will, eventually. +I think, Haha! I’m still a beginner myself! + +## Do you sew more for yourself or for others? + +Bart dislikes new things, so if I make him anything, he’ll wait five years before he decides to wear it. +And our son Luc has more clothes than he can wear already. He doesn’t need any more. +So I sew for me. I’m the only one who’s actually grateful for handmade clothes! + +## What do you do outside of FreeSewing? + +Professionally, I’m a management assistant, although I’m not working at the moment. +I’m really proud that I got my bachelor’s degree, even though people said I couldn’t do it. +Clearly I could, and I’m so glad that I pushed through! I’m not sure where I’m headed right +now in my career, but I’m taking this time to organize our home. Nothing Marie Kondo-style, mind you. +I’d be terrible at that. I love having stuff around. But it sure would be nice if all that stuff was a bit more organized. + +## What else do we need to know about you? + +I can be a bit of a bull in a china shop. Forgive me! +I’m impulsive, I’m honest and sometimes I should think twice before I say something. +But it all comes from a good place! + + +  + +--- + +  + + +# 🤓 Git(Hub) Good: Let’s walk through a simple FreeSewing contribution together + +You — yes, you — can contribute to FreeSewing. On the way, you can +learn a little bit about GitHub. Don’t panic. You’ll love it. + +I think the easiest way to get your feet wet is cruising around the documentation +at [FreeSewing.org](https://freesewing.org/) or [FreeSewing.dev](https://freesewing.dev). +Occasionally you’ll find a typo or a broken link, or just an opportunity to phrase something more clearly. + +On [FreeSewing.dev](https://freesewing.dev), you can click on [For Editors](https://freesewing.dev/editors/) +for a friendly reference guide. At time of writing, I did that and tried clicking +the [Common tasks for editors](https://freesewing.dev/howtos/editors/) link at the bottom. +It took me to a *Page not found* message with a sad robot. Yippee!! Let’s fix it. + +First, let’s find the correct link. I know I’m looking for a page called *Common tasks for editors*, +so I click the magnifying glass icon, put “Common tasks for editors” in the search bar and +get this: https://freesewing.dev/editors/howtos. Looks good. + +Then, let’s go back to the *For editors* page. Click the pencil icon next to the page title. + +Hey, now we’re in GitHub. Let’s create an account. + +After creating our account, we'll fork the FreeSewing markdown repository, or repo. +The repo contains a bunch of FreeSewing’s files and the history of changes to those files. + +At this point, we're editing the *For editors* file. We’ll swap out the old link with the +new link we identified, and then propose changes. Let’s give the proposal a nice title and description. + +Time to submit a pull request! Now we’re cooking with fire. A pull request, or PR, is a way to +tell FreeSewing that we are proposing a change. In this case we’re saying: "Hi, I found a broken link and I fixed it". + +Finally, someone at FreeSewing will review the PR and say: "Cool, this looks great, +so I’ll accept the change; I’ll *merge* it". That will send you, the author, a brief email, +it’ll be updated in GitHub, and when Joost next deploys the site, typically within a week or so, +you’ll see your contributions live on FreeSewing.org or FreeSewing.dev. Crushed it. + + +  + +--- + +  + + +# ⚡ FreeSewing v2.16: This one's for the developers + +We rolled out FreeSewing 2.16 in May, and a minor version bump typically means a new pattern. +Not this time though, because we've been working hard on updating our development environment +to React 17, CRA 4, and Webpack 5. + +That's great news for (aspiring) developers and pattern designers, as React's new *FAST_REFRESH* +makes everything just so much better. + +There's a lot of work that went into this release, but I also know it's all kinda technical and +under-the-hood stuff. So rather than ramble on about it here, +I will just [point you to the blog post on the matter](https://freesewing.org/blog/react-17/). + + +  + +--- + +  + + +# 🤷 Gender Inclusivity + +A month or two back, some FreeSewing users asked a really great question +on the [Discord](https://chat.freesewing.org/). +What is the goal of having a "womenswear" and "menswear" tag on FreeSewing patterns, +and is it really necessary? While some of our users found the tags helpful for sorting, +others felt alienated by the terminology, or didn't feel like either term represented +them. We thought we could do better, so we've made a few changes. + +**Tags are gone!** 🎉 + +Instead, we now have departments. For the moment, these departments include +Accessories, Bottoms, Tops, Coats & Jackets, Underwear, and Swimwear. +The departments are listed at the top of the [Designs](https://freesewing.org/designs/) page, +along with difficulty ratings and types of patterns (pattern or block). +If you are looking for something in particular, you can use the departments to filter +patterns, then decide what's right for you! + +**Why is this an improvement?** 🤔 + +The old categories on FreeSewing's Designs page, including menswear and womenswear, +were developed based on the types of categories you might find at a clothing shop. +However, we're not a clothing shop. And that's kind of the point. +FreeSewing patterns are made-to-measure because they're meant for everyone. +We think these new departments are a better representation of that. + +These categories were also not visible on the Designs page - you had to do a little more +work to filter patterns. As we add more patterns to FreeSewing, it made sense to add some filters, +so you can more easily find just what you're looking for. + +Thanks to the users who started this discussion and helped make FreeSewing a little better! ♥ + + diff --git a/markdown/org/newsletter/2021q4/en.md b/markdown/org/newsletter/2021q4/en.md new file mode 100644 index 00000000000..c89a6b9353d --- /dev/null +++ b/markdown/org/newsletter/2021q4/en.md @@ -0,0 +1,154 @@ +--- +date: "2021-10-01" +edition: "2021q4" +intro: "2021 Fall edition" +title: "2021 Fall edition" +--- + +Welcome to the 2021 Autumn edition of the FreeSewing newsletter. +Here's what we have included for you: + +- 🎉 Pattern releases fall 2021 (1-minute read - by Karen) +- ✏ Call for feedback: Hellgy's user survey (1-minute read - by Karen, 5-minute survey by Hellgy) +- ✨ Version 3 roadmap (3-minute read - by joost) +- 🕵 Behind the seams: Anneke (5-minute read - by Anneke, An, and Eleonore) +- 👻 Halloween 🕷 costume 👽 ideas (1-minute read - by bobgeorgethe3rd and Lucian) +- 😋 We have a TikTok now! (1-minute read - by Lucian) +- 🎧 Sew over 50 podcast, double-dose with Wouter and Joost (1-minute read - by Karen, over an hour of podcast fun by Maria) +- 👕 Pattern Project (2-minute read - by joost) + +We hope you enjoy it. +If not, mash that reply button and tell us what you'd like to read instead ¯\\\_(ツ)\_/¯ + +  + +  + +## 🎉 Pattern releases fall 2021 + +A new pattern is out that's perfect for fall, at least if you're in the northern hemisphere. + +[The Yuri hoodie](https://freesewing.org/blog/annnouncing-yuri/) is based on the [Hugo](https://freesewing.org/designs/hugo/) and [Huey](https://freesewing.org/designs/huey/) hoodie patterns, but it's got something a little extra. +Or rather, it doesn't. Yuri has no zippers! + +Designed by [Hellgy](https://freesewing.org/makers/hellgy/) and coded by [Biou](https://github.com/biou/), Yuri uses overlapping panels secured with buttons to keep you cozy and stylish. + +  + +--- + +  + +## ✏ Call for feedback: FreeSewing user survey + +FreeSewing rockstar Hellgy [didn't just release a new pattern this quarter](https://freesewing.org/blog/annnouncing-yuri/), they also put together [a FreeSewing user survey]((https://forms.gle/7zFSJP7AbUeg3Tbo9))! +Their goal: find out what our users like or dislike and find easy or difficult, then use that information to help with the UX/UI design of the site. + +Here's where we need you! Do you have 5 minutes and want to help out FreeSewing? [Fill out the FreeSewing user survey](https://forms.gle/7zFSJP7AbUeg3Tbo9) and let us know how you use the site and what your experience has been. + +  + +--- + +  + +## ✨ Version 3 roadmap +It's been a bit over 2 years [since FreeSewing v2.0.0 came out](https://freesewing.org/blog/announcing-v2/). Since its release, we've been working on adding new designs as well as improving things big and small, and it's fair to say that the v2.19 release that we're currently preparing is leaps and bounds ahead of that 2.0 version from 2 years ago. + +Still, there's a number of things we'd like to do but we can't. Or at least not without breaking a bunch of stuff, which we won't because FreeSewing practices something called [semantic versioning](https://semver.org/). That's a fancy term that boils down to version numbers that looks like major.minor.patch. For example: 2.18.1. + +The way it works is that for bugfixes, you increase the patch level. For new features, you increase the minor level. And the major number is only increased for so-called breaking changes. + +Another way to look at it is that when you practice semantic versioning, you make a promise to your users: As long as you stick to the same major version, we won't break your stuff. +That is not super relevant for regular users of freesewing.org but is very important for people who are building on top of our software, and example of which you can read further down in this newsletter. + +In practical terms, everything we have a *ooh that would be nice but it would break things* idea, we file it under *maybe in the next major release*. And after two years, we feel we've got enough of a grab-bag of ideas to start being serious about what we want to see in version 3. + +To that extend, we have published [the FreeSewing v3 roadmap](https://github.com/freesewing/freesewing/discussions/1278). It is a list of all the things that we would like to see happen in the next major release. And it's open for feedback, suggestions, and ideas. In other words, if there's something you always wanted to see in FreeSewing, or if you've got some great ideas for us, now is the time to chime in. You can [comment on the roadmap]((https://github.com/freesewing/freesewing/discussions/1278)), or [join us on Discord](https://discord.freesewing.org/). + +  + +--- + +  + + +## 🕵 Behind the seams: Anneke +*We’re happy to introduce you to another of FreeSewing’s contributors. She’s multi-talented, has green hair and the best sense of humour. Anneke was around before FreeSewing was even a thing. Without her, FreeSewing wouldn’t have a face … or should we say, skull?* + +### How did you learn about FreeSewing? +“I met Joost at a blog meet-up, way back in the day. You know it was a long time ago because Joost still left the house and socialising was still allowed. Anyway, we started following each other and that’s how I found about his patterns-to-measurements project. It was still called MakeMyPattern at that time. Apart from my work as a seamstress and getting a second degree in animal care, I’m also an illustrator. At some point Joost asked me to design a logo for FreeSewing, and that’s how Skully happened.” + +### What else have you been up to as a contributor? +“Joost and I created a pattern together, Carlton and Carlita. They are two versions of the coat Benedict Cumberbatch wears in “Sherlock”. I also help out with translations, manage our Facebook group and test new patterns if they are something that I would wear.” + +### What drew you to sewing? +“I started sewing over ten years ago. My mother had no inspiration for a birthday present but she saw me messing around with some fabric and gave me a sewing machine. It all went downhill from there. I currently work as a seamstress parttime, doing mostly repairs and alterations. It's very different from sewing from scratch, and interesting in its own way. I still sew for fun, too. I love how sewing gives me absolute control over my wardrobe. I'm no longer limited to what's on offer in shops, I can wear whatever I want in the materials that I want. As someone who can get very sensitive to textures and fit, this is a huge advantage.” + +### What’s the hardest part of sewing to you? +“Finding the balance between doing something I enjoy and owning too many clothes. Sewing for others feels too much like work, so if I sew in my spare time, it’s always for me. But you do end up with a LOT of clothes, and that makes me feel guilty or wasteful sometimes. I try to see the giant wardrobe as a testimony to my learning process, and donate the things that are no longer worn so they get another chance. On a less serious note, I’m terrible at cleaning up after myself when I’m sewing. I’m a messy person and it’s a messy activity. What can you do?” + +### What would be your advise for starting sewists/sewistas? +“Be ambitious. You will learn a lot from projects that challenge you. It's OK to start with very simple things just to learn how to use your machine, but don't be afraid of zippers or buttons or collars. The internet is full of information and tutorials, and if you mess it up, learn from it and try again. I’m still proud of my own “milestone” projects that tought me new skills and pushed me forward. My first real coat, first pair of jeans, first underwire bra.” + +### Are you a dog or a cat person? +“I’m an animal person. All animals are good in my book. Except for mosquitos, they can go fuck themselves. Can I say that?” (You can, and you did.) + +### Where can we find you on social media? +You can find my (relatively quiet) blog at www.annekecaramin.com or my Instagram at [@annekecaramin](https://www.instagram.com/annekecaramin/). + +  + +--- + +  + +## 👻 Halloween 🕷 costume 👽 ideas +With Halloween just four weeks away, we've got something special lined up for you: Lucian and bobgeorgethe3rd are putting the finishing touches on a list of ideas for awesome costumes to sew. +And — best of all — you can make all of them from FreeSewing patterns! + +The ideas range all the way from recreating a Victorian-esque look with extravagant sleeves, to embodying the role of Spongebob. + +There's plenty of options, for all ages, so keep on eye on [our blog](https://freesewing.org/blog/) for spooky updates as Halloween draws closer. + +  + +--- + +  + +## 😋 We have a TikTok now! +You may have noticed that [our Instagram account](https://www.instagram.com/freesewing_org/) has been posting a lot more lately. True! But that's not the only social media work done; we have a TikTok account now! [You can find it under @freesewing_org](https://www.tiktok.com/@freesewing_org), which is the name all of our social accounts carry. Who knows what the future holds... 👀 + +  + +--- + +  + +## 🎧 Sew over 50 podcast, double-dose with Wouter and Joost +FreeSewing's very own Wouter (you may remember him from the interview in the first FreeSewing newsletter) has been interviewed for the Sew Over 50 podcast! Tune in to learn about how Wouter got into sewing, the projects that intrigue him, his advice for new sewists, and his work with FreeSewing! + +And just under the wire for this newsletter, Joost has also been recently interviewed by Sew Organised Style, sharing how FreeSewing came to be, how you can get involved, and what brought Joost to sewing in the first place! Plus bonus thoughts on finding the perfect shoes. + +Find out more on the [Sew Organised Style page](https://seworganisedstylepodcast.com/), and listen to Wouter's podcast [here](https://seworganisedstylepodcast.com/2021/08/12/wouter-vdub/) and Joost's podcast [here](https://seworganisedstylepodcast.com/2021/09/27/freesewing-org/), or look for Sew Organised Style on your favorite podcast app. + +  + +--- + +  + +## 👕 Pattern project + +To be clear: This is not an ad. But I do want to talk about a new clothing company based in the UK named Pattern Project. They describe themselves on [their website](https://www.pattern-project.com/) as: + +> *Pattern Project is a South London micro-factory. We make clean, urban, local manufacturing of clothing possible and cost-effective. We produce clothing after it is sold in a matter of days.* +> +> *We sell Sew-It-Yourself Kits and Ready-To-Wear clothes. The kits contain precut and annotated fabric are easy to make and take less time than regular sewing.* + +The reason I'm writing about them in our newsletter can't be glanced from their website, nor will you [read about it in the press](https://www.theguardian.com/lifeandstyle/2021/sep/28/sew-it-yourself-inside-the-zero-waste-zero-sweatshop-revolution). But behind the scenes of this micro-factory, FreeSewing churns out the patterns for the laser machines that cut the fabric. + +It feels significant somehow to cross that threshold from *nice hobby website you've got there* into a place where FreeSewing is a project on which other build their business, and in a very tangible way, their livelihood. + +I don't even know if the achievement this unlocks carries a name. But I wanted to share it and thank all our contributors and patrons for their support without which we would have never gotten this far. diff --git a/markdown/org/newsletter/2022q1/en.md b/markdown/org/newsletter/2022q1/en.md new file mode 100644 index 00000000000..60050f55458 --- /dev/null +++ b/markdown/org/newsletter/2022q1/en.md @@ -0,0 +1,187 @@ +--- +date: "2022-01-01" +edition: "2022q1" +intro: "Welcome to the 2022 Winter edition of the FreeSewing newsletter." +title: "2022 Winter edition" +--- + +Welcome to the 2022 Winter edition of the FreeSewing newsletter. + +Unlike other editions where we drop a Smörgåsbord of blurbs from various contributors in your mailbox, you're going to have to do with just me this time around. That means a bunch of em dashes — everyone's favorite punctuation mark — and I'm happy to report that two paragraphs in I've already managed to squeeze in one of them A's with a circle over it. Nice! + +So much for form, let's talk content. Here's what I'll be covering: + + - 🎉 2021 is salted and burned + - 🧐 What our contributors have been up to in 2021 + - 🎖️ FreeSewing is now an '*all contributors*' project + - 🚧 Why version 3 has been put on hold + - 🤓 What I've been up to in 2021 + - 🐛 FreeSewing's bug bounty program + - ⛑️ Yearly revenue and where it went (spoiler: same as always) + - 🤞 What I hope will happen this year + +Y'all ready for this? Let's do it. + +  + +  + +## 🎉 2021 is salted and burned + +Well yes I binge-watched all 15 seasons of [Supernatural](https://en.wikipedia.org/wiki/Supernatural_(American_TV_series)) this year because what else were we supposed to do, locked in our homes as we were. And if that dreamboat Dean has taught me anything, it's that you should salt, then burn whatever you want to get rid of for good. + +I don't mean to say there was nothing good about 2021. As a matter of fact, within the context of FreeSewing it was another absolutely fantastic year. + +But I find it in poor taste to be jubilant about a year that for many people was — yet again — about hanging in there and dealing with the many-faced monster that is the COVID pandemic. + +I hope you are all ok and that you did not have to bid farewell to any of your loved ones. I hope that your mental health is resilient enough to deal with all this. And if it's not, then I hope you have people to talk to. If you don't have those, you can talk to me. Hit reply and we'll figure it out somehow. We should not have to deal with any of this on our own, so don't be shy. + +With that out of the way, let's look at some of the good things that happened over the course of last year. + +  + +--- + +  + +## 🧐 What our contributors have been up to last year + +We put out 53 FreeSewing releases this year, on average more than one per week. It speaks to the continuous churn that goes on in a healthy and thriving open source project. [Work is never over](https://www.youtube.com/watch?v=yydNF8tuVmU), and an ever growing number of people drive FreeSewing forward. + +The most visible of those changes are in our growing catalog of designs, with the [Bella Bodice Block](https://freesewing.org/designs/bella/), the [Hortensia Handbag](https://freesewing.org/designs/hortensia/), the [Cornelius Cycling Breeches](https://freesewing.org/designs/cornelius/), the [Charlie Chinos](https://freesewing.org/designs/charlie/), the [Bee Bikini Top](https://freesewing.org/designs/bee/), the [Lunetius Lacerna](https://freesewing.org/designs/lunetius/), the [Tiberius Tunic](https://freesewing.org/designs/tiberius/), the [Walburga Wappenrock](https://freesewing.org/designs/walburga/), and the [Yuri Hoodie](https://freesewing.org/designs/yuri/) all new patterns that were added in 2021. + +What I am personally very excited about is that a variety of people were involved in these new patterns, which means the list of people capable of independently cranking out parametric designs is steadily increasing. That is great news for the future. + +There is more of course. I think we've added more [showcases](https://freesewing.org/showcase/) this year than any previous year, and [our community on Discord](https://discord.freesewing.org/) is thriving in ways that I never would have dared to imagine. + +I'd like to thank all of those people for lending a hand, being part of our community, and just being awesome. If you had told me a couple of years ago that FreeSewing would evolve into a thriving D&D community with a sewing website attached I would not have believed you 😂 + +  + +--- + +  + +## 🎖️ FreeSewing is now an '*all contributors*' project + +Since we're singing the contributors praise — which I really can't do enough — now would be a good time to point out that FreeSewing is now officially an [all contributors](https://allcontributors.org/) project. + +Traditionally, contributions in open source are measured by commits, in other words: contributions to code. The revision control system (git in our case) tracks those contributors automatically, so it's easy enough to pull up a list of people who've pushed code. + +But there are many other ways that people contribute to FreeSewing. From translation to proofreading, community building, design work, you name it. + +As an all-contributors project, we want to value those contributions in a similar way and so we now maintain a list of contributors rather than relying on get's list of contributors. We are also showcasing that list of contributors prominently both [in our Readme](https://github.com/freesewing/freesewing#contributors-) and on our (future) websites (more on that later). + +So anybody who contributes can be added, and should be added. Doing so is a shared responsibility, since the big downside of such a maintained list is of course that we risk forgetting people. If that's the case, do reach out and let us know, we'll be happy to add you. + + +  + +--- + +  + +## 🚧 Why version 3 has been put on hold + +As you may know, we put out [our roadmap for FreeSewing version 3](https://github.com/freesewing/freesewing/discussions/1278) which reads like a wish list of things people would like to see in the next major release. + +After some initial testing-of-the-waters for some of these new features, and I have decided to put v3 on hold for now. + +The reason is that many of the things on the wish list don't require a new major version. In other words, we can add them without breaking backwards compatibility. Case in point, several of the v3 proposals/ideas have already been implemented in the current release. + +On the other hand, one of the things that will cause breaking changes is moving to ESM-only releases. It gets a bit technical but there's different ways to bundle up your Javascript code, and we currently publish both CJS and ESM bundles. One of the goals of v3 was to move to ESM-only, but I feel that we were putting too many things in this v3 basket making the entire effort an unwieldy affair and difficult to wrap your head around. + +So, I'm putting those things that will cause breaking changes (like pure-ESM) on hold until we've implemented all the changes we can already implement today. So by delaying it, we're actually going to see new features sooner because most of the breaking stuff is so far under the hood that you probably wouldn't even notice when it changes. + +  + +--- + +  + +## 🤓 What I've been up to last year + +As I mentioned earlier, the fact that more people than ever are now contributing patterns is one of of my personal highlights of the year. But it did not come about by divine intervention. + +16 months ago, at the end of August 2020, I wrote about the challenges of scaling my own labour, and how I wanted to [see FreeSewing grow beyond what I can do on my own](https://freesewing.org/blog/a-call-for-help/). + +In retrospect, I feel that post marks the moment where I pivoted from guy-working-on-open-source-thing to an open source maintainer. +My efforts ever since have been preliminary focused on facilitating the work of others, clearing hurdles for aspiring contributors, and simplifying the developer experience. + +Which is why I am not concerned that I *only* designed two patterns in 2021. More patterns are always nice, but I prefer to focus on things that are hard for other people to do. Like the [migration to React 17 and Webpack 5](https://freesewing.org/blog/react-17/) which happened in release 2.16 and brought with it an improved developer experience. + +But all of that remains on the '*pattern design*' side of things. But there's a lot more that goes into running FreeSewing. + +Last summer, I set out to work on [project 2022](https://freesewing.dev/blog/project-2022) in which I wanted to bring a similar easy on-ramp to other aspects of the project. Working on our backend code, our websites, writing blog posts, and so on. + +I'm happy to say there's been a lot of progress in this area. Perhaps a good illustration of this is our move to Strapi — a so-called [headless CMS](https://strapi.io/) — for our blog and showcase posts as well as for our newsletter content. Prior to the move, we had several years worth of blog posts, all written by yours truly. Since the move, we've had other people writing blog posts, and I can't even remember last time I published a showcase posts because ever since we moved to Strapi, that's taken care of by others now. + +We're also consolidating as much work & code as possible into [our monorepo on Github](https://github.com/freesewing/freesewing) as that makes it easier to wrap your head around the project, and track transversal changes — such as when changes to the website necessitate accompanying backend changes. + +Our markdown content and backend code has been consolidated into our monorepo. We were able to [merge our two translation projects on Crowdin into one](https://crowdin.com/project/freesewing), and the efforts started this summer to migrate our frontend code from GatsbyJS to [NextJS](https://nextjs.org/) paid dividends at the last day of the year when I deployed [our new freesewing.dev website](https://freesewing.dev/) in production. + +It's been re-written from the ground up to be better, faster, and perhaps most importantly, easier for people new(ish) to the project to work on, improve, or just see in what novel ways they can break it. + +The new FreeSewing.dev was built from the start to share code with what shall become the new FreeSewing.org, so that's something to look forward to this year. + +  + +--- + +  + +## 🐛 FreeSewing's bug bounty program + +One of my personal low points of this year was when one of our users reached out because of an issue in their shirt pattern. An issue that I was able to trace back to a regression bug that was triggered by a new feature request we had implemented some time prior. + +To have, what I personally consider to be one of our flagship patterns, hobbled by a bug that passed under the radar made my heart sink. I can't help but think about all the people who tried the pattern in the meanwhile, didn't get good results, and in completely understandable fashion most likely concluded that this entire FreeSewing thing is utter garbage. +After all, sewing patterns are traditionally a finished product. Not one that receives numerous improvements and bug fixes throughout the year. + + +We have taken steps to try and prevent similar mishaps from happening. There's been a significant effort made to increase the number of unit tests that help us spot issues. I wrote a new plugin specifically for this reason that allows us to compare generated patterns across FreeSewing versions/changes. We now also keep sampled output for each and every pattern option under version control, so that we can trace exactly what patterns are being impacted by changes to the codebase. + +But, things will still slip under the radar from time to time, which is why we're launching **the FreeSewing bug bounty program**: + +> If you find a bug in one of our patterns, or in our core library, we will (with your permission) add you to our list of contributors, and send you a little something to say thanks. + +Obviously, we're no Apple or Google, so we can't fork over cold hard cash as reward, but we have nice stickers, so that's something :) + + +  + +--- + +  + +## ⛑️ Yearly revenue and where it went (spoiler: same as always) + +Yearly revenue for FreeSewing in 2021 was 10,070.77 euro. In accordance with [our revenue pledge](https://freesewing.org/docs/various/pledge/), it was all donated to [Doctors Without Borders/Médecins Sans Frontières](http://msf.org/). + +And, for the second year in a row MSF deployed its teams not just in the South, but also in Europe and the US to help manage the COVID pandemic. + +In the hospital where my wife works — one of the main hubs for COVID care in the country — the COVID ward was at one point was even run by teams from MSF as their experience in running healthcare facilities in the middle of a crisis is simply unparalleled. + +There were probably similar initiatives and MSF teams working in your vicinity, often under the radar, but always there where they are needed the most. + +FreeSewing's revenue is 100% made up of patron contributions, and I feel an enormous depth of gratitude towards those kind-hearted and generous souls who make this possible. 2020 was an absolute bumper year for FreeSewing with an influx of COVID-inspired goodwill pushing our revenue beyond 5 figures for the first time. I did not expect that to hold in 2021 yet once again our patrons delivered. + +They are the real heroes of this story. I can't thank them enough. + +  + +--- + +  + +## 🤞 What I hope will happen this year + +- I hope we'll be able to rebuild FreeSewing.org and make it better, faster, and more feature-packed +- I hope we'll be able to continue to chip away at gendered terminology, and strive to make patterns that *just work* to support you and how you express yourself +- I hope we'll continue to welcome new contributors who are excited to build this thing together +- I hope we'll continue to bask in the love and support of our patrons so we can pay it forward and help those in dire straits +- I hope you all have a great year filled with health, happiness, and hugs + +  + +love +joost diff --git a/markdown/org/newsletter/2022q2/en.md b/markdown/org/newsletter/2022q2/en.md new file mode 100644 index 00000000000..e31ad5667af --- /dev/null +++ b/markdown/org/newsletter/2022q2/en.md @@ -0,0 +1,203 @@ +--- +date: "2022-04-01" +edition: "2022q2" +intro: "Welcome to the 2022 Spring edition of the FreeSewing newsletter." +title: "2022 Spring edition" +--- + +Welcome to the 2022 Spring edition of the FreeSewing newsletter. + +Today is April 1st, so to be clear; None of these are jokes: + +- 👸 All hail the Showcase Queen (by Karen) +- 🕵 Behind the Seams: Eléonore (by An) +- 🤓 FreeSewing's new lab as a preview of things to come (by Joost) +- 🤝 Friendship ended with Netlify / Now Vercel is our best friend (by Joost) + +Let's go, we don't have all day. + +  + +  + +## 👸 All hail the Showcase Queen + +For just over a year, there's been one person at FreeSewing who, when someone posts a cool new FreeSewing project on +[Discord](https://discord.freesewing.org) or on social media, made sure that it didn't just disappear into the internet ether +like so much ephemeral web content. In fact, this person was so accomplished that we developed a special Discord role +just for her: "Showcase Queen." + +During her tenure as the Showcase Queen, [Natalia](https://freesewing.org/makers/nataliasayang/) posted dozens of Showcases, +first in the old format and more recently in Strapi. (Full disclosure, the number here is not specific because I stopped +counting once I got into the thirties.) With Natalia's help, there are now examples of almost every FreeSewing pattern +available on the website's Showcase. If you read that "almost" as a call to action, just wait, your time to shine is in one +more brief paragraph, because... + +Now, after an unprecedented reign, our queen has decided to relinquish her post and turn her role over to the people. + +Here's the part where you come in. + +Have you used a FreeSewing pattern to make something you just can't wait to share with people? That you're proud of? +That looks or fits or feels fantastic? If so, we would *love* if you would consider adding it to the FreeSewing +Showcase! Don't worry, the technical part [is easy](https://freesewing.dev/howtos/editors/showcase), and there are tons of folks in the FreeSewing community who can +help if that bit is daunting. + +But there's one thing we can't help with, and that's creating great and helpful images for your Showcase. + +Or can we... 🤔 + +Below are just a few easy tips and tricks for helping future sewists with your Showcase post. Of course, any +Showcase is infinitely better than nothing, so go ahead and send us those low-light mirror selfies - we love them. + +But if you want to take things to the next level, a few things to consider: +- Show the whole garment! From multiple angles, if possible. It's awesome to see garments from the front, but back +and side views can be really helpful, too. Bonus points for adding in a seated picture, which are especially great +for sewists who use a wheelchair. +- Take pictures in the best light you can — that might be next to a bright window, in a room where you've turned +on all the extra lamps you could find, or that elusive "golden hour" outdoors. Bonus points if you can make it bright +enough to not need a flash. +- A neutral background can be helpful for seeing details. So can close-up pictures! If you nailed that welt pocket +or hand-stitched all your buttonholes, go ahead and show them off. + +If you read all that and thought, "Yikes, that's intimidating!" never fear. The beauty of FreeSewing Showcase posts +is that they're created by the entire FreeSewing community, and each of them, even the ones taken on a potato phone, +make FreeSewing just a tiny bit better. But if they're really great, or you start making sure incredible garments +get added to the site, you might just get the chance for your own title as "Showcase Queen." + +Thank you, Natalia! 👑 + +  + +--- + +  + +## 🕵 Behind the Seams: Eléonore + +### How did you learn about freesewing? +I met Joost through some mutual sewing friends back when FreeSewing was still Makemypattern.com. I loved what he was doing with the project and how he wanted to make it grow, so I stuck around. + +### How did you become a contributor? +I'm really bad at saying "no" when someone needs help. + +### What has been your contributor work so far? +I manage our Instagram (badly) and help out with translations (occasionally). + +### When and why did you start sewing? +I learned the basics from my mum, but never heard about the concept of sewing from a pattern. I just more or less winged it whenever I wanted to make anything. Those projects all turned out terrible, of course. Then when I went through a long period of depression years ago, my parents gave me a sewing machine and I started looking into making my own clothes more seriously. It kept my hands busy when my mind was wading through the mud. That machine was the best gift I've ever received. I seriously think sewing saved me. + +### What is your daily job, outside of freesewing? +I am a copy editor and I do communications and training for a healthcare IT company. That last job is very new and was sort of sprung on me in the middle of the COVID crisis. It's been A LOT, but it's so rewarding. + +### What are you currently working on? +In sewing? I am working on clothes that fit my behind. I'm not going to lie, my butt is proving a tough nut to crack. + +### Which project did you just finish? +I took a break from my own fitting woes and made a pair of trousers for my husband. He said the previous pair I made him was perfect, so I made no adjustments. And wouldn’t you know it: he’s gained weight. THEY DON’T FIT. Always take new measurements, kids. + +### What sewing/coding project are you most proud of? +I once made a TARDIS outfit for a wedding. It was what I imagined the TARDIS would look like if she were invited to a fancy party. It was nerdy and glorious and it included a corset with a hand-embroidered patch that said "bigger on the inside". + +### What in your life are you most proud of? +That I'm still here. + +### What do you love the most about sewing? +The certainty that if you just keep at it, you will see progress. + +### What do you hate the most about sewing? +That sometimes you have to keep at it for a VERY long time. + +### What’s the hardest part of sewing to you? +Fit. Always and forever, fit. I find it fascinating how a 2D pattern translates into a 3D garment, but wow, it can be frustrating when it doesn't translate the way you want it to! + +### What would be your advice for starting sewists/sewistas? +To keep at it! And not to get too hung up on "fails". If you end up with a garment that you love: that's great. If you don't, that's fine: you've spent a few hours doing something you enjoy and that's worth just as much, if not more. + +### Are you a dog person or a cat person? +Definitely a cat person. + +### Do you have pets? +Cats! We have two: sweet, reserved, anxious Aiko (who takes after me) and hyperactive, talkative, goofy Asra (who takes after my husband). + +### If there was one thing you could take with you to an uninhabited island what would it be? Why? +Oh, do I have to choose? My Kindle, my sewing machine, my piano? No, the piano would hate the salty air and I'm guessing there are no power outlets on this island for my sewing machine. I'll take the Kindle. Wait, I would need to charge that too. But just one book would never be enough. I'm getting anxious about this whole island thing. + +### If there was one person you could take with you to an uninhabited island, who would it be? Why? +I'll have to say my husband, since there's a good reason that I married him. He can come. If he's quiet and serves me drinks. + +  + +--- + +  + + +## 🤓 FreeSewing's new lab is a preview of things to come + +On the very last day of 2021, we published our new website for developers, available at [freesewing.dev](https://freesewing.dev/). It was the first major milestone in our migration from GastbyJS to NextJS and the consolidation of our frontend code in our monorepo. [Our roadmap](https://github.com/freesewing/freesewing/discussions/1278) has all the details. + +The next logical step would be freesewing.org, our flagship website for makers and the one you're most likely to be familiar with. But in parallel we're also looking to provide a better developer experience for people working in our monorepo. + +So, I decided that I would start by tackling the very heart of what makes our website meaningful: The interface to generate, test, and export patterns. It is by a wide margin the most complex thing to make happen (not to mention make intuitive) and the thinking is that whatever problems we're going to run into, this is where they will prop up. + +The result of that work so far is now available on https://lab.freesewing.dev/ If you're expecting a freesewing.org-equivalent site there, you're probably going to be disappointed. It really is only about the pattern configuration. But there's some things that I think are worthy of some excitement. + +### One website, many languages +FreeSewing currently supports 5 languages (en, fr, es, de, nl) and the way we handle that is by having a subdomain for each language (eg the Spanish site lives at https://es.freesewing.org/). On the surface, that is an elegant solution and it works well when it works well. In practice, what we've found is that sometimes language-specific bugs crop up, more often than not because some malformed content generated by the translation software. Problem is, when this happens, it's not always picked up/noticed and the result is that it's not uncommon for the non-English versions of the site to lag behind one of more releases. + +There's also the fact that building 5 sites for each change requires 5x the build minutes, and recently we've been overshooting our build minutes graciously provided by Netlify pretty much every month. + +The lab site implements a different solution that we hope to use as the blueprint for the future freesewing.org. It's one site that carries all languages with the language changes handled in the URL. That means one single build for all languages, keeping all our users on the latest and greatest release. + +### One development environment, many patterns +Currently, each pattern has its own development environment, which is the same as what you get running `npx create-freesewing-pattern`. For developers working in our monorepo, that adds friction, in particular when working on patterns that extend another pattern. + +The new lab is one development environment for *all* our patterns making it easy to make cross-cutting changes to various patterns. Furthermore, when you spin it up in development mode in our monorepo, it will load all pattern code from source and seamlessly update whenever you make changes to any pattern. + +### One development environment, many versions +This improvement is aimed squarely at making it easier to track down regression bugs in patterns. A regression bug is when things worked fine before, but now for some reason they do not. This typically happens when a new feature or improvement has unintended side-effects. + +Previously, there was no simple way to compare the (result of the) latest version of the code with the previous version. Our new lab however has a dropdown that simply lets you pick the version of your choice and will create that version of the pattern. This should be a real boon for tracking down those bugs. + +### Custom layout (work-in-progress) +If your eyes has somewhat glazed over from all that developer talk, fear not, there's also some cool features for end users in this new code. + +For one thing, I started working on one of our most popular feature requests: Custom layouts. The idea is that you can change yourself the way the pattern is laid out since computers are actually not very good at choosing the optimal layout. + +This has been divided into two different layouts: One layout for printing (where you can try to cram everything into as small a space as possible), and one layout for your fabric (where you will want to keep grainlines and so on into account). + +It's still a work-in-progress and certainly rough around the edges (as is the entire lab to be honest) but the intent is clear: We absolutely want this to be part of freesewing.org on the very first day of our migration. + +If you're interested in seeing what work working on, or just curious, head over to https://lab.freesewing.dev/ and we'd love to hear your feedback [on Discord](https://discord.freesewing.org/). + +  + +--- + +  + +## 🤝 Friendship ended with Netlify / Now Vercel is our best friend + +Ok, so I kinda wanted to reference [this meme](https://knowyourmeme.com/memes/friendship-ended-with-mudasir) but let me be absolutely clear: Friendship with [Netlify](https://www.netlify.com/) is not over. As a matter of fact, they are a really great company and I can't recommend them enough. + +But, some of our plans and ambitions bump into the limits of what can be done in a static site (looking at you i18n routing) and so we ended up with these great plans/ideas but no obvious way to deploy them without breaking the bank. + +Which is why I am very happy to let you know that [Vercel](https://www.vercel.com/?utm_source=freesewing&utm_campaign=oss) — the very company behind the [NextJS](https://nextjs.org/) framework that we're migrating to — has agreed to become a FreeSewing sponsor; In other words, Vercel will host and build FreeSewing's websites free of charge, much like Netlify has been doing for us for years. + +But unlike Netlify, which is a pure static hosting service, Vercel runs a server-side NextJS instance which means we can do all sorts of cool stuff server-side. + +This is really exciting news and I'm very happy that Vercel has agreed to sponsor FreeSewing. We also want to thank Netlify for the many years that we've benefited from their service. +And, while we're at it, I feel obliged to point out that we have more sponsors: + +- [Algolia](https://www.algolia.com/) handles our search +- [Bugsnag](https://www.bugsnag.com/) handles our bug reports +- [Crowdin](https://www.crowdin.com/) handles translation + +To be clear: We don't receive money from any of these companies and this is not some sort of paid advertising. But all of these companies wave their fees for FreeSewing because they believe that what we do is worthwhile. + +And I for one do not think that's something we should take for granted. + + + + + diff --git a/markdown/org/newsletter/2022q3/en.md b/markdown/org/newsletter/2022q3/en.md new file mode 100644 index 00000000000..1c13b0b1de5 --- /dev/null +++ b/markdown/org/newsletter/2022q3/en.md @@ -0,0 +1,242 @@ +--- +date: "2022-07-01" +edition: "2022q3" +intro: "2022 Summer edition" +title: "2022 Summer edition" +--- + +Welcome to the 2022 Summer edition of the FreeSewing newsletter. +Here's what's in it for you today: + +- 🦈 FreeSewing 2.21 adds five new patterns (4-minute read - by Karen) +- 🔨 Changes to our monorepo structure (2-minute read - by Natalia) +- 🚸 Honey, we shrunk FreeSewing: Adapting FreeSewing designs for kiddos (2-minute read - by Natalia) +- 👨‍💻 FreeSewing *afk* (1-minute read - by Lexander) +- 🕵️ Behind the Seams: Starfetcher (4-minute read - by Karen & Starfetcher) +- 💰 Should we be down because FreeSewing's revenue is down? (2-minute read - by Joost) + +Let's jump right in! + +  + +  + +## 🦈 FreeSewing 2.21 adds five new patterns + +FreeSewing 2.21 adds Bob, Hi, Lucy, Noble and Unice designs. + +### Bob the bib + +Long-time followers of FreeSewing may recognize Bob, a classic bib, and the result of the FreeSewing pattern design tutorial. Want to sew up Bob without learning how to develop a FreeSewing pattern? Now you can! Although we think you should still learn how to develop a FreeSewing pattern, like the folks below. + +[Discover Bob on FreeSewing.org](https://freesewing.org/designs/bob) + +### BLÅHAJ, nay Hi + +When (the UK branch of) a certain Swedish yellow/blue colored furniture giant announced that it would discontinue its universally beloved plush shark, the internet did not handle it very well. +People love soft and cuddly sharks and the idea of ever being without one to keep you company when things are rough was quite frankly unsettling. + +So plans were made, strategies discussed, but for a while it seemed we were just going to have to accept defeat. +Smash cut to Wouter Van Wageningen, one of FreeSewings' most senior pattern designers, who embarked on a singular mission: To save the sharks. +Suffice to say. He did. Because of course he did. + +Wouter named the pattern Hi and those of you who share his Dutch roots will get the play on words here 🦈 +So now you can sew up your very own Hi, a friendly and fabulous plush shark and frankly an internet icon. + +This is FreeSewing's first plush pattern, and as such it is not be tailored to any measurements, but it's still parametric! You can sew up Hi in any size from roughly 5 centimeters to 5 meters, and you can modify its mouth, its nose pointiness, and make your Hi "aggressive" (that's when you give it pointy teeth). Another great thing about Hi: it'll fit anyone in your life! Does your sibling, cat, in-law, crush, boss, GM, barista, or anyone else in your life need a Hi? Probably. Do you need a Hi? Almost definitely. +Does it need to be 5 meters long? No, but it wants to. + +[Discover Hi on FreeSewing.org](https://freesewing.org/designs/hi) + +### Lucy + +[Lucy](https://en.wikipedia.org/wiki/Lucy_Locket) is a perfect accessory for the historically-inspired sewist, a historical pocket that you can tie around your waist, designed by SeaZeeZee. Traditionally, these could have been worn under other layers of clothing, creating an easy way to carry things that was obscured by skirts or aprons, but there's no requirement to hide your Lucy under a bushel (or a bustle). Make one in just about any fabric you like - Lucy looks great in that cute quilting cotton you couldn't resist, that scrap you love too much to throw away, or the textile that you're intimidated by but want to take for a test drive. A Lucy in sequins, velvet, or vinyl? Definitely cool. 😎 + +[Discover Lucy on FreeSewing.org](https://freesewing.org/designs/lucy) + +### Noble + +Hi isn't the only pattern release from Wouter Van Wageningen this quarter. For those looking to experiment with their own pattern drafting, Wouter has created the Noble block, a sleeveless prince(ss) seam block based on the Bella block pattern. Blocks are the basis for other patterns, so Noble doesn't have finishes or closures, but it makes a great, made-to-measure starting point for self-drafted patterns. + +[Discover Noble on FreeSewing.org](https://freesewing.org/designs/noble) + +### Unice + +Last but not least, first-time FreeSewing designer Anna Puk has released a new underwear pattern, Unice! Unice is a variation on Ursula, a basic, highly customizable underwear pattern. Trying to figure out whether to sew up Ursula or Unice? Unice was designed to accommodate a full rear, so it might be a good one to try if you find that undies in your size don't provide adequate coverage in the back, or if your jeans are always tighter across the seat than the thighs or waist. Or, even better, make them both! After all, you can never have too many undies. (And if you do, please hop into the [Discord](https://freesewing.org/community/where/discord/) or onto our social channels, @freesewing_org on Instagram and Twitter, and let us know how they work out for you!) + +[Discover Unice on FreeSewing.org](https://freesewing.org/designs/unice) + +  + +--- + +  + +## 🔨 Changes to our monorepo structure + +Big things are happening. + +There have been some changes in the monorepo structure. With the previous single yarn workspace in packages now split up in: +- designs for designs +- plugins for plugins +- packages for NPM packages that are neither design nor plugin +- sites for websites, backend code, our svg tiler and so on + +The monorepo has been stripped of the individual development environments for designs. Instead, all development on designs should now happen in the lab. +There's a new command `yarn tips` that you can run that will give you a quick summary of how to work within our monorepo. +And you can run `yarn lab` to start the lab from the root of the repo, or from any design or plugin folder. + +If you want to add a new design, run `yarn new design` and everything will be taken care of for you. + +The old stand-alone development environment (`npx create-freesewing-pattern`) is deprecated (ever since v2.21 running it will show a warning about that) but still available. +Those who are looking for stand-alone development should try out the replacement that uses that same improved development environment as our monorepo. +To launch it run: `npx @freesewing/new-design` + +Want a full list of what's new? Check out the [notes from the latest contributor call](https://github.com/freesewing/freesewing/discussions/2270). + +  + +--- + +  + +## 🚸 Honey, we shrunk FreeSewing: Adapting FreeSewing designs for kiddos + +First dolls, now children?! FreeSewing contributors seem intent on making mini versions of our designs. + +We wanted to talk a moment to highlight some of the great projects folks are making for their kids and some of the lessons they've shared. Don't miss the photos in the [showcase](https://freesewing.org/showcase/). + +If you're interested in adapting a FreeSewing design for a young person, a few things to consider: + +- **Make test garments!** Making a muslin is a good habit in general, and especially important when sewing for people whose measurements may not have been tested yet with a FreeSewing design as their proportions won't necessarily work smoothly the first time around. `comixminx` is the undisputed champion of Shin sewing trunks, having sewn several test pairs on the way to making wearable pairs for each of [her](https://freesewing.org/showcase/shin-swim-trunks-for-comixminxs-kid/) [kids](https://freesewing.org/showcase/more-shin-swim-shorts/). +- **Consider trying out a block.** As evidenced in `Bob3000`'s adorable [chore coat](https://freesewing.org/showcase/bob3000-chore-coat/) for his kid, based on the Brian block, the basic shape of a block might be a good starting point to which you can add design elements. +- **Use lots of ease when designing for toddlers.** `mathstitch` ended up drafting their own collared shirt and it turned out rather wonderfully. They shared some tips for anyone who might try to adapt an existing design in the future! They suggest adding heaps of ease because toddlers are so active and uncoordinated, tend to adopt unusual postures all the time like crouching and crawling, and some have big bellies and lots of puppy fat. 🐶 A short sleevecap is appropriate. If your kiddo is still in diapers, the shirt needs to flare at the hips to accommodate that, and you'll want to ensure the buttons end far enough up from the bottom of the shirt. +- **Add adjustable elements to make garments fit for longer.** `Rowan` made a tiny [Albert apron](https://freesewing.org/showcase/a-tiny-albert-apron/) for their kid's birthday and added adjusters to the straps. Great idea to maximize the number of wears they can get out of this very cute accessory. +- **Sew quickly.** `AMJ` reports having seen kids change sizes between fitting and sewing. 😀 + +If you're trying out one of our designs with your kid, we hope you'll come chat about it in [Discord](https://discord.freesewing.org/). + +  + +--- + +  + +## 👨‍💻 FreeSewing *afk* + +FreeSewing is going outside! FreeSewing will be part of the [May Contain Hackers](https://mch2022.org/) camp as a short talk by Lexander. Mark your calendar for July 24th, 09:40 PM CEST; it can be followed with a livestream. + +Lexander will describe about what FreeSewing is, Joost’s (and other volunteers’) motivations behind it, a bit about the tech, and why it’s important for fashion and clothing as a whole. More info is in the full description [on the event’s site](https://program.mch2022.org/mch2021-2020/talk/M9JWKM/). + +  + +--- + +  + +## 🕵️ Behind the Seams: Starfetcher + +### How did you learn about FreeSewing? + +I can't quite remember, but I think I was searching for sewing patterns one day and had the glorious insight to use "open source sewing pattern" as a keyword. The search engine did its job. + +### How did you become a contributor? + +While reading the developer docs I found a few typos and decided to correct them, while starting on translations I found some more, and suddenly I was a contributor. Joining the contributor calls was the next logical step, and I haven't looked back since. + +### What has been your contributor work so far? + +Apart from fixing typos and broken links, I sporadically do some translation work and have coded three historically inspired patterns: Lunetius, Tiberius and Walburga. + +### Are you a sewist? A coder? Both? Neither? + +Both, and it depends on my mood what I like to do more. + +### When and why did you start sewing? + +As a child, my mother taught me the basics, but it wasn't until my late teens that I started to take it seriously when I decided to sew my own costume for my birthday party (my birthday parties were and still are always costume parties). I did lots of mistakes (like finishing the edges before sewing the parts together), but I was (and still am) incredibly proud of it. Then I took a break from sewing again, but rediscovered it in my middle tweens when I got back into cosplay. + +### What is your daily job, outside of FreeSewing? + +Right now I'm doing my PhD in experimental physics, so I have a good mixture of hands-on work at the machine and cursing a lot at the computer at 11PM. + +### What are you currently working on? + +Currently I'm working on making foam armour to complement the fabric parts of my costume (consisting of Lunetius, Tiberius and Walburga, of course). It's a new technique for me so it's lots of fun to play around with. + +### Which project did you just finish? + +I just finished coding and sewing Pythia the paenula, my upcoming FreeSewing pattern for another type of historically inspired cloak. Now I'm procrastinating on hunting down the last bugs. + +### What sewing/coding project are you most proud of? + +On the sewing side, I'm still very proud of the first costume I sew by myself, but the trickiest one so far is the Sailor Fuku I made a few years back. Oh, and the Victorian shirt with lots of pleating on the front, where I also had to adjust the sizing of basically everything (an experience that ultimately led me to FreeSewing). +Coding-wise, that's probably a work-related thing where I made some nice graphical representations with Python and LaTeX. + +### What in your life are you most proud of? + +That's a hard question! Probably all the combined experiences that taught me everything I know today. + +### What do you love the most about sewing? + +The magical feeling when you finish something and you put it on and it's just perfect. + +### What do you hate the most about sewing? + +The sinking feeling when you finish something and you realise something went wrong and your immediate future probably involves the thread picker or the cutting mat if you're unlucky. Oh, and hemming skirts, especially hemming two combined full circle skirts because you wanted the volume at 2AM. + +### What’s the hardest part of sewing to you? + +Laying out pattern pieces with the correct grainline and cutting things out without forgetting the seam allowance. + +### What would be your advice for starting sewists? + +Just dive right in! Don't be afraid to make mistakes and don't be afraid to ask for help, but just try. + +### Do you sew mostly for yourself, or for others like friends and family? + +Mostly just for me, though I tried to sew something as a present a few times - so far I never finished any. + +### What are you up to when you’re not making clothes or designing patterns? - Would you like to share ways to follow you on social media? + +I like table top roleplaying games (DSA, Cthulhu, ...), video games, reading, photography, fencing and archery (still an amateur, mind). I'm also responsible for directing the acting portion of my old schools musical group. No social media for me. + +### Do you have pets? Family? + +Sadly no pets, although my SO has a cute dog. I'm pretty close to my parents. + +### Are you a dog person or a cat person? + +Both! Though if I were forced to choose, I'd pick... a penguin. + +### If there was one thing you could take with you to an uninhabited island, what would it be? Why? + +Apart from things like water and food and a knife? Probably my ebook reader, upgraded with solar cells, and loaded to the brim with books for entertainment and survival. + +### If there was one person you could take with you to an uninhabited island, who would it be? Why? + +That's tricky! If it's voluntary, my SO, but they'd have hard time without electricity and other perks of civilization. If it's not voluntary, someone who increases my chances of survival, like a really strong doctor. + +  + +--- + +  + +## 💰 Should we be down because FreeSewing's revenue is down? + +I'm going to assume you're familiar with [FreeSewing's revenue pledge](https://freesewing.org/docs/various/pledge/)? If not, go ahead and read it. I'll wait. + +Over the first 6 months of 2022, FreeSewing's revenue was 25% lower than the (average) revenue of 2021. + +This is not entirely unexpected. There was an influx of new patrons during the Covid pandemic, and we are now on the down-slope of that wave. +Many patrons who discovered FreeSewing because of our facemask pattern are now leaving us because they don't see the point in extending their support. Others are feeling the cost-of-living crisis and have either lowered their contributions or cancelled them altogether. + +I am truly appreciative of all these contributions, but seeing patrons leave does tend to make me wonder whether we have a problem? +I personally don't think so. But I'm not a 100% certain about that either. And on the bad days, it certainly feeds into my doubts about... well, everything really. + +There are many different metrics you could point to that show FreeSewing is thriving. Whether it's the number of designs we have available, the size and activity of the community, or something as easy to measure as number of commits. + +Yet still... + +After mulling it for a while, I figured the best thing to do is just be transparent about what's going on: FreeSewing is doing fine, but we are seeing less financial support than we used to. Revenue will be lower this year, from the looks of things by at least 25%. diff --git a/markdown/org/newsletter/2022q4/en.md b/markdown/org/newsletter/2022q4/en.md new file mode 100644 index 00000000000..09ebddb99d2 --- /dev/null +++ b/markdown/org/newsletter/2022q4/en.md @@ -0,0 +1,194 @@ +--- +date: "2022-10-01" +edition: "2022q4" +intro: "2022 Autumn edition" +title: "2022 Autumn edition" +--- + +Welcome to the 2022 Autumn edition of the FreeSewing newsletter. +Here's what's in it for you today: + +- 🏁 FreeSewing 2.22 is out and will be the final v2 release (1-minute read - by Joost) +- 🔱 FreeSewing version 3; What is it, and when can you expect it? (3-minute read - by Joost) +- 🚀 We've crossed the 50.000 commits milestone (1-minute read - by Joost) +- ⛵ FreeSewing at the Serendiep in Rotterdam (1-minute read - by Lexander) +- 🕵️ Behind the Seams: Enoch (4-minute read - by Karen & Enoch) + +Let's jump right in! + +  + +  + +## 🏁 FreeSewing 2.22 is out and will be the final v2 release + +FreeSewing 2.22 came out towards the end of August, featuring a new plushie +design by Wouter — who also signed for Hi the shark. This time, it's +[Octoplushy](https://freesewing.org/designs/octoplushy/) which is, you guessed +it, an octopus. + +What's certainly less adorable but perhaps not relevant is that this will be the +final minor release under version 2. That's right, version 3 of FreeSewing is +coming, and while we continue to support version 2 — not to mention that it's +still powering FreeSewing.org — our focus is now very much on the next major +version: FreeSewing v3. + +  + +--- + +  + +## 🔱 FreeSewing version 3; What is it, and when can you expect it? + +For a bit over a month now, we've put the version 2 code base in long-term storage and have started working towards version 3. +And while it will be a while before this lands in production — which means FreeSewing.org for us — I'd like to give a very brief highlight tour of some of the things that are happening with FreeSewing version 3 right now that I am personally most excited about. + +### Part-level configuration, aka pack support + +On [our road map](https://github.com/freesewing/freesewing/discussions/1278) — which if you have been paying attention has ever more things under the *already implemented* heading — we had so-called support for *packs*. The idea was that we'd love to make it possible to create designs by freely combining different components. Like perhaps you'd get the sleeves from a *sleeve pack* and the collar from a *collar pack*, add some pockets from a *collar pack* and so on. + +It's one of those things that makes a lot of sense, but begs the question: How will all of this work under the hood? +In v2 of FreeSewing, implementing these ideas would have been non-trivial because even though we support extending patterns into other designs, the process is too cumbersome for this level of ad-hoc mashing together different designs. + +So that's something we wanted to address in version 3, and to do so we've essentially move all configuration to the part level. For example a sleeve part will have it's own options defined and list what measurements it needs and so on. You can now just pull that sleeve part out of the design (or in the future a sleeve pack) and use it in your own design without having to worry about measurements and options and so on. + +It's the most fundamental change in V3, but it's something that will open the door to a lot of creative combinations of various designs in the future. + +### Support for multiple sets of settings, or as we call them: Multisets + +Patterns are ultimately drafted for users by passing them a bunch of *settings*. The measurements to use, how you'd like the options to be just your way and so on. + +In FreeSewing version 3, you'll still be able to pass multiple sets of these settings to the pattern. +This has a bunch of interesting applications. For example, if you're working with an asymmetric body, you'd be able to pass in two different sets of measurements and say "*give me those and those parts with these measurements, and the other parts with those measurements*". + +We also use this new feature under the hood to handle how we *sample* patterns. Which is when we compare various iterations of a pattern with each other. This used to be somewhat bolted on top in a semi-awkward way. But in version 3, it's as simple as compiling a list of different sets of settings (since one gets tired of typing/saying *sets of settings* rather quickly, we refer to them as *multisets*) and then we can *simply* pass them to the pattern and it *just works*. + +### Stack support + +Closely related to multiset support is support for stacks in the layout phase. +Stacks are a bit like *layers*. Typically, when lay-outing each part is its own thing and we would lay them out individually. +Now, you can say that different parts are part of the same *stack* and they would be stacked on top of each other in the layout, like layers. + +It's once again something we use internally for some of our sampling/comparing work, but also opens up interesting possibilities and I'm curious to see how people will end up using these features. + +### And so much more + +There's really is a lot more going on in version 3, with improvements and tweaks big and small. +But these are some of the more fundamental changes. We're also still working on it, so if you have a great idea, [our road map](https://github.com/freesewing/freesewing/discussions/1278) is the more formal way to propose them. For a more informal chat, stop by [the FreeSewing Discord](https://discord.freesewing.org/) where we hang out and coordinate our work. + +### When can you expect version 3? + +The short answer to when you can expect version 3 is *sometime in 2023*. If that seems long, it's because we're really re-working things from the ground up. The changes outlined above are really foundational changes, and they need to ripple through the entire machinery built on top of those foundations before it can all come together in something that can be released on FreeSewing.org. + +And we also want to make sure we get it right. So we're going to keep on keeping on, and release it when it's ready. + +  + +--- + +  + +## 🚀 We've crossed the 50.000 commits milestone + +A couple of days ago, we crossed the threshold of 50.000 commits [on our monorepo](https://github.com/freesewing/freesewing). + +Numbers in itself aren't really that meaningful, not to mention that you can always game the system. So I don't mean to imply that this milestone in itself has some sort of special significance. But I do feel that at a time that most work (on v3) is happening behind the scenes, it serves as a good reminder that FreeSewing is a bit like a swan. It might seem to glide forward seemingly effortlessly at a steady pace, but there is frantic pedaling going on beneath the surface. + +  + +--- + +  + +## ⛵ FreeSewing at the Serendiep in Rotterdam (1-minute read - by Lexander) + +FreeSewing was invited to join an exposition hosted by Serendiep, which is a ship that's home to art and science, with a theater space and machines inside. The week-long exposition was part of a bigger whole: the city of Rotterdam is celebrating the 150th birthday of one of their canals. + +The workshop began with me, Lexander, introducing FreeSewing and explaining the concept, and we spent the evening making a sleeveless Teagan as a sleeping shirt. We were with a group of a few people and did the whole FreeSewing process: taking the measurements, assembling the paper pattern, cutting the fabric pieces and sewing them together. + +The Teagan fit nicely and overall it was a really fun experience! I’m looking forward to what the future will bring. + +  + +--- + +  + +## 🕵️ Behind the Seams: Enoch + +One of our Contributor Call hosts sat down (virtually) with Enoch to learn a little more about hir background and journey to becoming a FreeSewing contributor! The interview below has been edited for length, and any errors, oversights, etc. are entirely the fault of the interviewer. + +### How did you learn about FreeSewing? + +I learned to sew in grade school, but since then hadn’t done much sewing until the pandemic. In March 2020, just before lockdown, I wrapped up a long-time project, so, like many people, I found myself with some free time. Just prior to that I had finally received a diagnosis to explain my decades-long struggle with exhaustion (Restless Legs Syndrome, of all things), and medicating it meant that for the first time ever I had enough energy to have interests and hobbies. + +So I dusted off my old sewing machine and started playing around. At some point I was trying to make a piece that I couldn’t find a pattern for, so I learned enough pattern drafting to pull something together to make it happen. Because I'm a coder with an interest in open source, once I had done it in paper for myself, I wanted to automate it, and in automating it I wanted to make it available for as many bodies as possible. I decided I needed a parametric pattern, and tried out a few different things before finding FreeSewing. + +### How did you become a contributor? + +Once I started developing patterns in FreeSewing, I found myself thinking, “It would be cool if there were this. It would be cool if there were that.” For instance, as I was designing, I wanted to be able to generate line drawings to preview how different settings and measurements would impact the finished garments, and then I wanted to be able to drop in my fabrics and see how they would look on the designs. Adding the custom option types I wanted wasn't very straightforward, so my first PR was me trying to make it easier to replace small parts of the workbench. My first few PRs broke some stuff, so I got more involved just trying to clean up after myself. And then I really got into it. + +I've worked on open source software before in small amounts, and I've been the sole developer on software that was technically open sourced, but this is my first time being in the community of an open source software, and I'm finding that part of it really rewarding. To have all these people focusing on all these different areas of making it good, and all in basically constant communication with one another is super cool. The human element really matters, and FreeSewing is so much about the human element at all levels. Iit drives me to contribute at a higher and more consistent level. And I think Joost deserves a lot of credit for having written this massive thing and still managing to really foster this community around building and bettering it. + +### What has been your contributor work so far? + +I've done a few smaller things, but there are two big things I’ve worked on, and one still in the works! + +The first is getting Gitpod set up. Gitpod allows you to do your development in the browser, so that you don’t have to manage dependencies locally. This is especially useful for Windows developers because our environment isn't very Windows friendly, and it's not officially supported. I've also recently submitted some updates to the environment to help smooth things for Windows folks who really prefer to develop locally. + +The second is an update to the Printing Layout tool for the Lab. I reworked the moving and rotating functionality so that it works more smoothly and we now have snapped rotation in addition to free rotation. I also overhauled our export to PDF system so that when you export it looks as you would expect it to based on how you laid it out. We have a lot more control over the tiling now, and Joost doesn't have to maintain any C code alongside everything else. + +Still In progress is the Cutting Layout tool, which will allow you to specify a fabric width and lay out all the pieces (and if you're supposed to cut two, it'll give you two of them) so you can figure out how much fabric your pattern needs. + +### Are you a sewist? A coder? Both? Neither? + +Both! But I’ve definitely done more coding. That’s my job, so I’ve done it most days for ten years. + +### When and why did you start sewing? + +I started sewing early – I took sewing classes in elementary school, and my dad bought me a sewing machine in exchange for promising to hem all his pants (which I never did). Then, except for a semester or two of costume design in college, I hardly sewed again until more recently. I did learn to use an industrial machine, though! + +### What are you currently working on? + +I've been slow recently, but I always have ideas – I have a whole backlog of things I want to make for my partner, and I also do woodworking and am restoring a steel tanker desk and some rosewood mid-century side tables, and I’m working on a design for the back and front yard of my home. I learned a lot of 3D modeling during the pandemic, and it’s cooling off enough now (in the southern US) to work in the yard. + +### What project did you just finish? + +I just finished a tunic for my partner, and I designed the suit I wore to my sister’s wedding.. I handed the design off to a tailor, but when the suit was delivered, the sleeves were attached in the most baffling manner, and I ended up having to attach them myself. It turned out beautiful, although I’m still unhappy with the sleeves. + +### What do you love the most about sewing? + +I like that sewing opens up the world. You can realize or fix or customize whatever you want, and sewing allows you to get a perfect fit (or at least try…), whatever that means to you. I'm a very aesthetically driven person who was raised by very aesthetically driven people, and I believe in the transformative power of clothes, so it's great to be able to take that control for yourself. +Plus, I love to have any skill, and sewing is really a whole category of skills that really allows you to imagine a thing and say, “Yeah, we can do that.” + +### What do you hate the most about sewing? + +Seam ripping – which I have to do a ton of. And I sometimes feel there are too many steps to making the things it interests me to make. + +I think in reality I don’t often actually find sewing an enjoyable activity – on the one hand, I'm very ambitious, but on the other hand I'm very risk-averse and a massive perfectionist, so I have to do like 3 muslins before a final version of anything. But then I get distracted, which results in a lot of prototypes that I just wear even though they’re more a proof of concept than an actual garment. The most extreme example is from when I was a teen: I was experimenting with making my own chest binders, and the first one I made that worked out, which I wore for probably two years, was held together with ribbons and safety pins. Eventually I needed a new one, which I sewed fully, but for those first two years you can see the outline of safety pins through my shirt in every picture. + +### What would be your advice for starting sewists? + +Start with something that interests you. Lots of folks are taught to start with samplers, zipper bags, etc., and that works if it will interest you to develop the fundamentals. But if you want to tackle something ambitious, buy some cheap fabric and go for it! It won’t be nearly as bad as you think it is, and there’s always more fabric. + +### Do you sew mostly for yourself, or for others like friends and family? + +I mostly sew for other people, but I’ll make things sometimes because it seems easier to make a piece of clothing than to go and find it. I guess I’m a “make it if I don’t think it exists in the world” kind of sewer, but I’ll buy a tee shirt even though I could sew one. Or one time I sewed a pair of pants the day before a trip because I didn't have enough pants and going shopping sounded more inconvenient. + +### What are you up to when you’re not making clothes or designing patterns? + +I’m always doing something – woodworking, design, I occasionally code other things, I’m always washing dishes… I like puzzles, and finally finished a 1500 piece one that I kept taking months-long breaks from. I made a little free puzzle library for the finished ones, but nobody ever comes and takes any puzzles from me. + +### Do you have pets? Family? + +I prefer people to animals, and I live with a partner in a beautiful, pet-free home. My partner and I share a philosophy of "the loved ones of my loved ones are my loved ones", which allows us to think about family really lovingly and expansively. I'm also lucky to have a great adult relationship with my family of origin, though I don't currently live close to them. + +### If there was one person you could take with you to an uninhabited island, who would it be? Why? +Honestly, my partner is the person – we’ve lived together for almost 5 years, and being around each other constantly during the pandemic really brought us closer, (and taught us how to set better boundaries!) so I feel confident we'd be ok in a deserted island scenario. They would grow us food and I would build us shelter, and it would be great. + +### Would you like to share ways to follow you on social media? +You can follow me on Instagram at @enoch\_tries\_everything, but be warned it’s very rarely updated. + + + diff --git a/markdown/org/newsletter/2023q1/en.md b/markdown/org/newsletter/2023q1/en.md new file mode 100644 index 00000000000..9eb48f0c1ba --- /dev/null +++ b/markdown/org/newsletter/2023q1/en.md @@ -0,0 +1,152 @@ +--- +date: "2023-01-01" +edition: "2023q1" +intro: "Welcome to the 2023 Winter edition of the FreeSewing newsletter." +title: "2023 Winter edition" +--- + +Welcome to the 2023 Winter edition of the FreeSewing newsletter. + +First up: Happy new year to those who celebrate. May 2023 bring you everything you've hoped for, and perhaps some nice surprises too. + +As is a tradition this time of the year, our contributors enjoy a break to enjoy the holidays, and what you'll find below is made up almost entirely of the ramblings of me, Joost. + +In addition, it's new year's day, so I'm not going to make this too long. Here's what's in store today: + +- 🏁 2022 was the year of FreeSewing 2.22 (1-minute read - by Joost) +- ✋ 2023 will be the year of FreeSewing 3 (1-minute read - by Joost) +- 💜 The cost of loving (2-minute read - by Joost) +- 🕵️ Behind the Seams: Zwaluw (4-minute read - by Karen & Zwaluw) + +Let's get right to it. + +  + +  + +## 🏁 2022 was the year of FreeSewing 2.22 + +You won't find this on the list of any 2022 retrospective, but this is not a newsletter for hot takes about the news, this is the FreeSewing newsletter. And for us, 2022 was the year we release FreeSewing v2.22 and decided it would be the last v2 release ever. + +The [FreeSewing contributor call of 20 august 2022](https://github.com/freesewing/freesewing/discussions/2582) marks the official moment were we decided to wrap up development of v2 with one final release, and then turn our attention to version 3. + +In the months leading up to this moment, we had already made great strides in trying to implement many of the things on [our road map](https://github.com/freesewing/freesewing/discussions/1278), and it feels weird to me somehow that only four months have passed since when I think about all the work that has been done on v3. + +On the developer side of things, we've completely switched over already. FreeSewing.dev holds our developer documentation for v3, while the _legacy_ v2 documentation is relegated to v2.freesewing.dev. + +Our development environment for v3 is also ready — run `npx @freesewing/new-design@next` to try it yourself — and we also rewrote our backend to support our future plans, like hooking up our development environment to the backend so designers can use the measurements data they have stored in their FreeSewing account to test their designs. + + +  + +--- + +  + +## ✋ 2023 will be the year of FreeSewing 3 + +The current `next` release of FreeSewing is v3.0.0-alpha.4. The race has started now to turn that into `beta` and then finally put it in production on FreeSewing.org. + +I've talked about some of the new things in FreeSewing v3 in [our last newsletter](https://freesewing.org/newsletter/2022q4/). +I could talk about it more, but talk is cheap. You want to see it, right? Well you can't. It's not ready. +It was also not supposed to be ready. We started the effort late in August this year, and from the very start put the release at _sometime in 2023_. + +But, you can start the clock today and I promise that it will be out before the end of the year. If it's Q4, I will be a bit disappointed. If it's Q3, I will be happy. If it's Q2 I will be thrilled. And if it's Q1 I'll be very surprised. + +The only thing that's really left to do right now — apart from copious amounts of polish and bug fixes obviously — is to write a new frontend. In other words, a new FreeSewing.org where you can actually use all of the cool stuff we've been working on. + +In many ways, it will be the crowning achievement of version 3. The thing that brings everything together. + +No pressure. + +  + +--- + +  + +## 💜 The cost of loving + +FreeSewing's revenue during 2022 was `9.325,54` euro. That's down from `10.070,77` in 2021, which was in turn lower than the `10.736,82` of revenue in 2020. Still, it's more than double of the `4.109,38` euro revenue of 2019 and I think that's worth pointing out because 2019 was the last pre-pandemic year. + +We've seen an enormous influx of users, patrons, and revenue in 2020 undoubtedly because [our face mask pattern](https://freesewing.org/designs/florence/) was wildly popular during the PPE shortage that year. That peak has been tapering off ever since, and has pushed year-on-year revenue into a downward trend. Furthermore, inflation and the cost of living crisis has been particularly tangible this year, and I've received more than one apologetic message from patrons who wanted to continue supporting us but felt obliged to cut us from their monthly budget to ensure they would be able to support themselves and/or their families. + +So I don't feel bad about revenue being lower this year. I think it's been a difficult year for many people, and we have always been looking for support from those who could spare it without hardship. Yes, it's nice to break the `10.000` barrier. Yes, I would love to get to `12.000` and reach `1.000` MRR (monthly recurring revenue) but I'm not going to let that get in the way of being proud of the work we do. + +I am proud not only of the work we do, but because FreeSewing is a force for good in this world. +With the addition of this year's `9.325,54`, FreeSewing's contributions to [Médecins sans frontières/Doctors Without Borders](https://www.msf.org/) stands at `38.814,94` euro or about 41.6k US dollar. Money that helps people who are in a worse situation than we all are. + +So I am proud of those numbers, and most of all I am proud of the FreeSewing patrons who are behind them. They are the real heroes. + +  + +--- + +  + +## 🕵️ Behind the Seams: Zwaluw + +One of our Contributor Call hosts sat down (virtually) with Zwaluw (who goes by Z or Zee) to learn a little more about their background and journey to becoming a FreeSewing contributor! The interview below has been edited for length, and any errors, oversights, etc. are entirely the fault of the interviewer! + +### How did you learn about FreeSewing? +I don’t remember! I’m very active now, but I remember looking at the site a long while back and thinking it was cool, but I don’t remember how I got there… Maybe googling made-to-measure patterns? + +### How did you become a contributor? +That I do remember, it was writing documentation! I don’t remember if Starf asked or I offered, but my first project was writing the documentation for [Lunetius](https://freesewing.org/designs/lunetius/), a historical Roman cloak. + +### What has been your contributor work so far? +My first contribution work was the documentation for Lunetius, and I still help with documentation sometimes, but I’ve also started developing patterns. In particular, I’ve made [Lucy](https://freesewing.org/designs/lucy/), a historical tie-on pocket, and Jane. Jane is a to-be-released shift pattern (or underwear for historical garments), and there’s not a lot of patterns out there for those. For so many people in the historical sewing community, you make a shift and get it over with, and that’s not me. Jane gives you options on a pattern that’s pretty loosely fitted, but you might want more or less ease, different sleeves, etc. + +### Are you a sewist? A coder? Both? Neither? +I’m definitely both! I’ve sewn for much longer, and FreeSewing is how I started to learn Javascript and Markdown. I’d wanted to learn, but I had done absolutely no coding before, and something about FreeSewing really appealed. I think because I thought, “If I learn this, I can make a pattern.” It’s a really cool way to learn about web design and how to build websites, and I love joining the Contributor Calls. (Note from the interviewer: you too can join the Contributor Calls, every other Saturday! Schedules and agendas are posted in the [Discussions](https://github.com/freesewing/freesewing/discussions) section of the FreeSewing monorepo on Github. The next one is [January 7th!](https://github.com/freesewing/freesewing/discussions/3201)) + +### When and why did you start sewing? +I first started sewing around when I was ten years old, so sixteen years ago, and I’ve been making my own clothes for most of that time. At some point, I got into historical sewing, and it definitely influences my modern clothing. I like to make historical things that also work for me in my daily life. For example, I wear a lot of walking skirts. + +My dream project is a Victorian bustle gown, but it’s a lot of work. I do have a lobster bustle and corset, so maybe I will do a corset cover next… + +### What are you currently working on? +Right now, I’m working on a quilt in shades of blue that is all hand sewn. + +I like to have multiple types of projects going at once, though, so I am also working on a warm winter skirt made from IKEA flannel bedsheets in a beautiful gray and white plaid. Currently, I’m debating how to create the flannel waistband while keeping it from getting too bulky. I’ve also got some 1780s stays that are hand sewn except for the boning channels, with synthetic whalebone boning, and I need to make a bunch of new shifts, as some of my current ones are getting worn out. + +### Which project did you just finish? +The skirt I’m wearing! It’s a wool skirt for going to Tromsø, Norway in the Arctic Circle and I needed very warm stuff for that. While I was there, I also made so many napkins for the people whose house I was staying in. Sometimes I’ll use handcrafts as a fidget. + +### What sewing/coding project are you most proud of? +I think I’m most proud of Jane, a shift designed on FreeSewing that’s slated for release in 2023. That was my first coding project, and it’s done now, and functional! [Lucy](https://freesewing.org/designs/lucy/) I slapped together in a weekend, while Jane I’ve been working on for a year. + +### What in your life are you most proud of? +My family isn’t super crafty, but both my grandmothers were sewists, and my Dutch grandmother was a weaver, and I’m definitely proud that I’m continuing that, even though they never got a chance to teach me. I have my grandmother’s old looms, and my great grandmother's sewing machine. Looms are too big for a studio, but the sewing machine is one of those ancient black cast iron Singers that you crank by hand, and it still works! I can’t date it specifically, because it is from before they had serial numbers (which means it’s pre-1860s). + +### What do you love the most about sewing? +I love the meditative aspect of sewing. I can’t do meditation, and I’m not a mindfulness person, but when I sit down with a project and hand stitch, it’s very calming. I will machine stitch some things, too, but I find myself thinking: “This is so fast, I don’t enjoy this.” + +### What’s the hardest part of sewing to you? +The historical sewing community can be pretty inaccessible – if you don’t have a lot of money or time, then getting into this hobby can be really hard, and I wish that wasn’t the case. It’s part of what makes FreeSewing so cool – everyone’s donating their time and skills, so you’re not paying $30 for a pattern that doesn’t even properly fit you. + +For me personally, I think the hardest part is pacing, and making sure I don’t overdo it and hurt my hands. I do my best to have projects in different buckets: complicated, easy, practical… And I switch between them to not completely burn myself out. I need to recognize when I need to not sew for a few days, and then usually I end up switching to FreeSewing things! + +### What would be your advice for starting sewists? +Do something you enjoy. Even if it’s a big project and it’s overwhelming, it’s more fun to do that than to do something easy. And don’t forget your thimble. Historical costuming folks so often don’t have a thimble, or don’t stitch ergonomically, and it can really hurt your hands. I did not start out as a hand sewist – I took a class with Sarah at Williamsburg. I basically spent an hour sewing, and my hands hurt, and it didn’t work, and she saw and taught me her method. I’ve been handsewing ever since. (You can find Sarah on Instagram at [@sewnstories](https://www.instagram.com/sewnstories/).) + +### Do you sew mostly for yourself, or for others like friends and family? +I sew mostly for myself. I have made things for other people occasionally, but not a lot. Sometimes I have a time where I don’t have enough spoons and I really want to make things, but I already have enough towels, aprons, etc. So then I’ll make things for other people. And I am theoretically available for commissions (but it’s slow). + +### What are you up to when you’re not making clothes or designing patterns? +Reading books – I don’t have any favorite genres, but my favorite author is Terry Pratchett. I’m excited that we’re finally getting a Discworld movie version that looks good! Besides reading, I spend some of my time playing video games (I’m currently playing Destiny 2) and resting. + +### Would you like to share ways to follow you on social media? +I’m bad about posting, but my Instagram is [@zwaluwz](https://www.instagram.com/zwaluwz/). It also includes pictures of my cat, who was leash-trained! + +### Do you have pets? Family? +I had a cat named Q, but he passed away last April. I’m hoping to move, so that I can have a cat again, because my landlord won’t let me get a new cat. + +### Are you a dog person or a cat person? +Both! I do not discriminate in animals. I got to handle a bunch of snakes once, and it was the happiest I’ve ever been. Maybe I should just get a lizard… Or a hognose snake… + +### If there was one thing you could take with you to an uninhabited island, what would it be? Why? +A sewing project! + +### If there was one person you could take with you to an uninhabited island, who would it be? Why? +I don’t think I would take people, I’d just have a nice quiet time. diff --git a/markdown/org/newsletter/2023q2/en.md b/markdown/org/newsletter/2023q2/en.md new file mode 100644 index 00000000000..65b7920a7da --- /dev/null +++ b/markdown/org/newsletter/2023q2/en.md @@ -0,0 +1,173 @@ +--- +date: "2023-04-01" +edition: "2023q2" +intro: "Welcome to the 2023 Spring edition of the FreeSewing newsletter." +title: "2023 Spring edition" +--- + +Welcome to the 2023 Spring edition of the FreeSewing newsletter. + +Here's what's we've included for you today: + +- ☕ Keeping up with all the hottest FreeSewing gossip (3-minute read - by Karen) +- 🐑 Call for pattern shepherds (2-minute read - by Karen) +- 💵 Looking for a 1000 true fans (3-minute read - by Joost) +- 🕵️ Behind the Seams: Benjamin F. (4-minute read - by Benjamin & Karen) +- 🦈 Want to write for the newsletter? (1-minute read - by Karen) + +  + +  + +## ☕ Keeping up with all the hottest FreeSewing gossip + +Okay, so you're a fan of FreeSewing, you're excited for V3, and in the meantime, you're wondering where to get all the hottest gossip about what's going on behind the scenes. Fear not! We've got solutions for you. + +First off, have you checked out our [Discord](https://freesewing.org/community/where/discord/)? This is where you can catch all the fun previews, like what patterns are slated for release in V3, recommendations and tips from fabric types to hard-to-find hardware to sewing machine maintenance, all the cool tinkering developers are working on behind the scenes, and more. If you want to be truly in the know, this is where it's at. (It's also literally where it's at, if you want to join FreeSewing's biweekly contributor calls, which happen in the voice chat.) + +If you hate Discord, there are still options for you, though. Benjamin F. (of "Behind the Seams" fame) has been recapping the highlights from Discord as a GitHub discussion here: [Discord recaps](https://github.com/freesewing/freesewing/discussions/3523). Check it out for a quick perusal of recent hot topics. + +And last but not least, there is of course the FreeSewing site itself. While some updates are on hold pending V3, you can still check out our Showcases to get a peek into some of the wonderful and impressive things that FreeSewing users have been making in recent months. A few highlights: + +- The tiniest Hi ever made: [MicroHi](https://freesewing.org/showcase/microhi) +- This detailed how-to on making a [drop-shoulder Sven](https://freesewing.org/showcase/drop-shoulder-sven) +- A matching set of [multi-generational Florents](https://freesewing.org/showcase/matching-florents) +- How to [modify Aaron into a tank dress](https://freesewing.org/showcase/aaron-dress-by-ts) +- An incredible, impeccable [Classic Carlton by Boris](https://freesewing.org/showcase/carlton-by-boris) (check out the reinforcement embroidery!) --> + +...And a bunch more that didn't fit here but are equally incredible, and you'll just have to go check out the [Showcase](https://freesewing.org/showcase/) to find out more. 😉 + +  + +--- + +  + +## 🐑 Call for pattern shepherds + +Are you an expert at making a particular FreeSewing pattern? Maybe you've tried all the options, or you know why it goes haywire in certain edge cases, or you've made it for all your friends and fam as gifts? If this rings true, then yours is exactly the kind of expertise we're looking for. + +As you might have noticed, FreeSewing is growing and adding new capabilities! And when V3 rolls out, there are several new patterns that will come with it. But every pattern could use someone who is familiar with its foibles and intricacies. A lot of the time, this is the pattern designer. In other cases, it's the person who developed the pattern's documentation. And then there are the patterns that exist on FreeSewing's site, but their designer has moved on to new challenges, or no one has made the pattern in a while. These patterns can sometimes fall prey to problems that no one notices. Then, when new users try them out, it can be a needlessly rough experience. + +A pattern shepherd is someone who keeps an eye on things so this doesn't happen for their pattern. You don't need to be a programming prodigy or a sewing savant for this role, just someone who is familiar with the pattern, what goes into it, and how it goes together. If something breaks, you might fix it yourself, but you could also file a bug report to let the rest of the community know and recruit help. If this sounds like something you'd be interested in, reply to this email and let us know! + +Bonus: FreeSewing has a bug bounty program that nets you (a) our undying appreciation, and (b) sometimes cool swag. + +  + +--- + +  + +## 💵 Looking for a 1000 true fans + +I realized a few weeks ago that it has now been more than 6 months that we started working on version 3 of FreeSewing, and that's both an eternity and not very long at all. + +It's an eternity if you've been waiting with bated breath for its release. (If you're in this group, then please bear with us because gosh have we been busy). +But it's not very long at all if you consider all the changes that we are cramming into this new major version. I took stock the other day and I realized there is almost nothing that we aren't completely redesigning or doing differently and better. A brief list from the top of my mind: + +- Database: From MongoDB to Sqlite +- Backend: Completely rewritten +- Javascript: From CJS/ESM to pure ESM, and from default exports to named exports +- Bundler: From Rollup to Esbuild +- Hosting: From Netlify to Vercel +- FreeSewing.dev: From Gatsby to NextJS +- FreeSewing.org: From Gatsby to NextJS, and being completely rewritten +- Development environment: From CRA (Create React App) to NextJS +- Component library: From MaterialUI/MUI to TailwindCSS/DaisyUI + +I am sticking to technical changes here, there's obviously new features and other things that will be different/better. +But these are the foundations that are changing, so is the kind of stuff that won't be immediately obvious to you. + +The one thing that is not on the list above is our payment processor (currently PayPal, we'll probably migrate to Stripe) which brings me to the one thing we haven't (yet) changed: Subscriptions. + +Currently, we have 3 tiers of subscriptions. 2, 4, and 8 euro per month. +Some users have reached out to me because they wanted to do more for FreeSewing and [we've setup a 25$/month subscription plan for those generous souls](https://static.freesewing.org/fs-25/). + +That got me thinking about the subscription model and how the project is supported financially in general. +You may remember that I wrote last year that FreeSewing's revenue was trending ever so slightly downward, and it's something that I tend to get nervous about when I consider how many changes we are making. +People don't typically like change, and there is a certain risk that we'll alienate people with v3. + +Then again, mass appeal is never been our shtick. We don't need millions, [all you need is a 1000 true fans](https://kk.org/thetechnium/1000-true-fans/). So in v3, we will also overhaul subscriptions. +We'll implement a pure [pay what you can](https://en.wikipedia.org/wiki/Pay_what_you_can) model. +So today, you can either not pay, or pay 2, 4, 8, or 25 euro/dollar per month. +In the future, you will still be able to not pay, or pay whatever you feel is right. +Current subscriptions will not be terminated, although you are of course welcome to migrate to the new subscription model. + +The future will tell whether this will be good or bad move for FreeSewing. +But I believe that betting on our true fans is our winning strategy. So that's what we'll do 🤞 + + +  + +--- + +  + + +## 🕵️ Behind the Seams: Benjamin F. + +FreeSewing contributor Benjamin (BenJamesBen on GitHub) has been absolutely astounding us lately with his work supporting FreeSewing. So, we asked him if he wouldn't mind being the subject of this quarter's newsletter, and of course he not only said yes, but came back with something fantastic, funny, and unique. As always, any errors, oversights, etc. are entirely the fault of the interviewer! + +### Tell us about your involvement with FreeSewing. +Thank you for giving me the opportunity to talk about FreeSewing. I think that it's a pretty great organization in that it provides patterns free of charge to people. To me, that is the best thing that FreeSewing does. In the United States there is a retail store that regularly has sales where you can buy paper patterns for $2.00 USD, but I've heard that patterns are much more expensive in other countries. And, in some places paper patterns simply aren't available at all in stores. FreeSewing provides free patterns to everyone! + +### I see that you do a lot of coding-type work for FreeSewing? +I used to work doing computer stuff (software QA and testing), and my education background is also in computer science. A lot of what I've done in the past involves looking at code that other people have written, figuring out what it does, and troubleshooting issues. So, I've just taken that background and applied it to FreeSewing, testing the website and patterns to make sure things are working correctly, trying to fix bugs that pop up. + +### Are you also a sewist? +That's actually a good question, in a philosophical sense that is. I own a sewing machine and took sewing lessons. I have a fabric stash and multiple unfinished projects I should be working on. But, actual sewing? I don't seem to do much sewing. I do spend a lot of time watching sewing videos on YouTube. Does watching sewing videos count towards being a sewist? + +### What unfinished projects are you avoiding working on and watching YouTube instead? +I started working on a pirate/18th century shirt design for FreeSewing. All the code is written, and it produces patterns just fine. However, I haven't actually tested it to see if the generated patterns make sense fit-wise. (I guessed at the pattern measurements, just inventing numbers that seemed to make sense.) The next step is to make a test garment to check fit, make alterations to the pattern, and change the code accordingly. + +I also owe my sister a pillow made to custom measurements. (I basically just need to sew a rectangular bag with a zipper closure that she can stuff it with extra memory foam that she has own hand.) And finally, my first, original unfinished project is a Hawaiian/bowling style camp shirt, Kwik Sew 3484. (I bought the pattern back when Kwik Sew was its own company and still made garment patterns, if that gives you an idea of just how long the project has been unfinished.) + +### The pirate shirt sounds interesting. +I chose it because 1. I actually want a pirate shirt, and 2. It seemed like a good, easy design to make (all the pieces are rectangles!). However, although I am somewhat interested in historical clothing, I am not at all interested in historical sewing methods-- sewing by hand, that is. I plan to use a sewing machine to sew my pirate shirt. + +Fun fact: Pirates also sewed using sewing machines (that they took from the ships they plundered). However, instead of removing pins as they sewed, they would leave the pins in and sew over them-- which can be really dangerous. That is why so many pirates had to wear eye patches. + +### You said you owned a sewing machine? +It's a Kenmore-badged machine that was made by Janome. I think it was the most basic model available at the time. No stitch length or width adjustment, 4-step buttonhole, front loading bobbin. I bought it new at Sears back when Sears still existed and sold sewing machines. (That should give you another clue about how long my camp shirt unfinished project has been unfinished!) + +### What sewing projects would you like to work on in the future, that is assuming you finish your existing unfinished projects? +I would like to make my own tailor's ham. (Another simple pattern-- just two ovals.) I am considering making my own underpants since I need some new ones. Though, I am not sure whether it might be more practical or cost effective to simply buy them from the store. And, I am somewhat intimidated of sewing knit fabric. I've also gotten interested in patterns for sewing your own custom, made-to-measure dress form/mannequin. However, that seems like it might be too difficult a project. + +Finally, someday I would like to make a garment out of upholstery or curtain fabric. It seems like it might be an interesting challenge to use that type of fabric. Plus, Scarlett O'Hara wore a dress made from curtains, and as a result she got to marry Rhett Butler. Maria made clothes from curtains, and she got to marry Captain Von Trapp. (And, she was almost a nun!) If I were to make clothes out of curtains, imagine who I could marry!? + +### Getting back to coding, is it a difficult task to create a FreeSewing pattern? I'm thinking about people who might be experienced sewists who can design patterns but who don't have coding knowledge. +It isn't necessarily difficult converting an existing pattern into code. The first challenge is to learn how to think about how the pattern is drafted and describe it in terms of measurements and angles. Sort of like if you had to describe how to draft a pattern to someone over the phone or through text messages. Once you are able to write down instructions like, "draw a Point A", "draw another point 10 cm at a 45 degree angle above and to the right of A and label it Point B", "draw a line between Point A and Point B", etc., you can translate the drafting instructions into code. + +The next challenge might be to take the existing pattern which was made for one specific person and think about how it might be converted to patterns for other people with different measurements. You would have to think, "why was this part's fabric measurement 10 cm"? If it is because it was slightly larger than the wrist circumference, then perhaps the measurement could instead be converted to "the wrist circumference, plus 10%". I think that the skillset might be similar to that of pattern grading. + +For the coding itself, perhaps the best way to learn (apart from taking a formal coding course of which there are plenty of free ones on the internet) might be to look at the code for an existing FreeSewing design. I suspect that many people learn how to code by looking at existing code, copying it, and making changes to it to see what the changes do. FreeSewing provides a lab tool that allows you to view changes to the designs that you make or edit, so you can play around with things and learn from experimentation. If you need any help or get stuck, there are plenty of people on the Discord who would be happy to help! + +### Thank you. Any final words? +I find it somewhat amazing that the FreeSewing community is so geographically diverse, spread throughout the world, and still able to communicate with and help each other. I am glad to be part of this community. Though, it occurs to me that with the anonymity of the internet, nobody has actually seen me or knows who I am. For all anybody knows, I could be a cat on the internet just pretending to be a person. (If I were a cat, this wouldn't be considered "catfishing". We cats just call it "fishing"!) + +  + +--- + +  + + + + +## 🦈 Want to write for the newsletter? + +Hey! It's Karen, your friend from the [contributor calls](https://freesewing.org/community/calls/), the [Discord](discord.freesewing.org), and a bunch of the stuff written in this newsletter! Every quarter, we put out this newsletter as a way of keeping folks caught up on what's new with FreeSewing, cool updates, impressive accomplishments, weird projects, etc. But it only works because there's a whole incredible cohort of folks creating, designing, and contributing. (Here's where you come in.) + +If you read this newsletter and thought: +- "But what about fill-in-the-blank question?" or +- "Ooh, that reminds me of a FreeSewing project I've been working on behind the scenes..." or +- "Wow, I wish someone would do a deep dive on this topic!" + +...We would love to know that. And if you want to write that article yourself, well then I will personally be overjoyed and will help you in any way I can to make that possibility a reality. + +Maybe you made a garment that required some clever hacking or took on a life of its own, and you're really proud of it. Maybe you've got a fork of the FreeSewing monorepo where you're tinkering away with something exciting. Maybe you don't know what you'd like to write about, but you love FreeSewing and want to contribute, or you're hoping to build your cred as a reputable wordsmith. (Okay, actually, reputable might be a stretch, but that's part of our charm.) + +Reach out! You can find us on [Discord](discord.freesewing.org), or on [Github](https://github.com/freesewing/), or you can just reply to this email. We'd love to hear from you. 🧡 + + diff --git a/markdown/org/newsletter/2023q3/en.md b/markdown/org/newsletter/2023q3/en.md new file mode 100644 index 00000000000..84cddc29878 --- /dev/null +++ b/markdown/org/newsletter/2023q3/en.md @@ -0,0 +1,279 @@ +--- +date: "2023-07-01" +edition: "2023q3" +intro: "Welcome to the 2023 Summer edition of the FreeSewing newsletter. Here's what we have included for you:" +title: "2023 Summer edition" +--- + +Welcome to the 2023 Summer edition of the FreeSewing newsletter. + +Here's what's we've included for you today: + + +- 🚨 Intermittent signup trouble as v2 infrastructure struggles with load (2-minute read by Joost) +- 🕵️ Behind the Seams: Jasmine (6-minute read - by Jasmine & Karen) +- 🪡 Technique of the week (2-minute read - by Karen) +- 🙏 Help us with social media (2-minute read - by Bob & Karen) +- ⚫ It's always darkest before dawn (3-minute read by Joost) + +  + +--- + +  + +## 🚨 Intermittent signup trouble as v2 infrastructure struggles with load + +FreeSewing has recently been experiencing intermittent email delivery issues, +which causes problems for new users trying to sign up, or other actions that +rely on transactional emails, such as password resets. + +The underlying issue is that we are getting rate-limited by the SMTP relays we +use to send out these transactional emails, and this causes people to wait in +vain for their signup email, password reset, and so on. + +We have been using a free-tier service for the delivery of these messages, and +historically this has worked fine for us. There's been moments in the past +where a large influx of new users would trigger these problems, for example +during the height of the PPE shortage in the early stages of the COVID pandemic +when FreeSewing (and our face mask pattern) was linked to in the +New York Times, Forbes, and several other new outlets that dwarf us in scale. + +What used to be an exceptional event is now becoming more common, and it's +something that I personally tend to lose sleep over because it +disproportionately impacts the on-boarding process. Sure, there's going to be +the occasional user who will have trouble resetting their password. But the +vast majority of people who are impacted by this are new users, who are +attempting to sign up. + +It is a bad first impression when they can't get in, and as we all know, bad +first impressions can be hard to recover from. + +After mulling it over for a while, I've decided to... do nothing. Or rather, to +keep working on the more permanent fix, which is the v3 infrastructure where +we've switched transactional email to a different partner where we are a paying +customer, so there will be no rate limiting. Downing tools now to go +firefighting on the current production v2 infrastructure would only delay the +release of v3, which will resolve this problem once and for all. + +As a mitigating factor, we have already migrated the delivery of this newsletter to our new infrastructure, as this will lighten the +load on our *budget* of transactional emails per day. So +unlike before, we're actually paying money to get this to your inbox. It's not +a lot of money per email of course, but it's just one of the many changes we +need to make to scale up FreeSewing. + +So, apologies to all those people who have been impacted by these intermittent +issues. I know that nothing I say here can undo the frustration of hitting +refresh on your inbox and not getting that email. But I wanted to be open about +the underlying issues and why -- confronted with a lot of work and limited +resources -- I've decided to keep my eye on the prize. + + +  + +--- + +  + +## 🕵️ Behind the Seams: Jasmine + +If you haven't met Jasmine yet, you're missing out (and you should come hang out in our [Discord](https://discord.freesewing.org/)). She's got some cool sewing projects under her belt, but another big reason we reached out to interview her was the exceptional contributions Jasmine makes to the FreeSewing community. Have a question, a problem, or a celebration to share? Jasmine has cheered on and helped out countless folks in the community and brings support and joy (and incredibly cute puppies) to the folks of FreeSewing. So without further ado, here's a little bit more about one of our favorite FreeSewists! + +### How did you learn about FreeSewing? +I think it was in search of a way to draft a body block... + +My body is proportioned in a way I don't really find easily in ready made patterns. So the idea was to figure out a basic block to use as a template when adjusting patterns. + +### How did you become a contributor? +I'm a contributor? When did that happen? I guess it started with sharing my makes with the community, and then hacking the Sven sweater to emulate an oversized sweater I loved but absolutely couldn't afford. + +### What has been your contributor work so far? +The [family of Florents](https://freesewing.org/showcase/matching-florents/) have found their way onto the showcase pages, and the [hacked Sven](https://freesewing.org/showcase/drop-shoulder-sven/) did as well. I also wrote out how I adapted the design to an oversized drop-shoulder style. + +### Are you a sewist? A coder? Both? Neither? +A sewist. Learning to code is on my wish list, but I don't have the bandwidth for it at the moment. + +### When and why did you start sewing? +I've wanted to learn to mend for a long time, as well as adjusting the fit on bought items. The same proportions that don't fit into sewing patterns easily also make it so I can get into standard sized clothes. But they never fit me properly. Everything tends to gape at my waist. + +### What is your daily job, outside of FreeSewing? +I'm an X-ray technician at a small hospital. For the most part, I do hospital radiology, but a small portion of my hours is spent on patient radiation dose management and optimisation. + +### What are you currently working on? +Sewing is mostly paused at the moment as my partner and I have a lot of renovation projects we need to focus on right now. There's a small handsewing project I'll work on to kill time during a quiet night shift at work, but nothing concrete at the moment. + +### Which project did you just finish? +I just finished some adjustments on a pair of trousers I made two years ago. They're a loose fit with a drawstring waist, and my first sewing project. I was thrilled even just managing to follow the instructions at that point, but the back and front panels are identical. With my body shape and rear estate, to use coined FreeSewing lingo, that's not ideal. So I removed some material from the front, and added patch pockets from some scraps I had left of the fabric. + +### What sewing/coding project are you most proud of? +The loose fitted pleated trousers I made after the Folkwear Rosie the Riveter pattern. It included a lot of new challenges I'd never taken on before. I'm sort of still picking projects in a way that forces me to learn a new thing each time, and this one definitely pushed the limits of my confidence. + +### What in your life are you most proud of? +There's so much to choose from. Some pieces of my writing? The ones where I dragged my guts and tears and snot across the page? I don't know. Stories and art matter. Certainly. But I think right now it's the puppies we raised. Seeing them come into the world, watching them waddle around and explore, and help them grow into wonderful family members for their future humans? That might be it. I'm already both dreading and looking forward to our second litter. + +### What do you love the most about sewing? +The way the tactile work helps settle the chaos in my brain. When I hit the right rhythm, it can feel meditative. +And I end up with garments that do what I want them to, rather than having to search endlessly for what will end up as a compromise both in terms of fit and style, and sustainability and fair labour issues. Plus-sized shopping can feel like one of the seven levels of hell. + +### What do you hate the most about sewing? +Cutting. + +### What’s the hardest part of sewing to you? +Usually, that's knowing when to stop. I will either fall into a hyperfocused rabbit hole and then realise it's 4am and possibly time to go to sleep, or I'll just keep doing one more seam and then one more, and then I get so tired I make a stupid mistake. + +### What would be your advice for starting sewists? +Sew things you're excited about. Practice projects like bags and bookmarks are great, but if you're motivated to finish a thing and use it, it becomes so much more fun. If you're prone to self-doubt, picking projects to expand or solidify your skills gradually can really work well. But if you're excited about it, and eager to get to work, by all means, go for that lined coat with lovely construction details and tailored elements. (Thinking of the lovely coats and jackets FreeSewing features.) + +### Do you sew mostly for yourself, or for others like friends and family? +Mostly myself, but two of my Florent triplets were made for relatives, and last winter I made a bunch of wristwarmers out of offcuts of sweater fabric, as stocking stuffer gifts for my family. + +### What are you up to when you’re not making clothes or designing patterns? Would you like to share ways to follow you on social media? +Lol, how much space do we have here? As already mentioned, my partner and I ate licensed breeders of Belgian Tervuren Shepherds, though we stick to a litter every two years, pretty much. With the amount of time and energy invested in the puppies, more would not be sustainable. We also compete with our girls at dog agility trials and conformation shows. +And then I'm also a writer, poet, narrator, and podcaster. Links to my creative work can be found at [JasmineArch.com](JasmineArch.com), and I also venture onto Tiktok now and then, where I'm [@jaztellsstories](https://www.tiktok.com/@jaztellsstories). + +### Do you have pets? Family? +We currently have four dogs, though that number is set to grow in the coming years, I suspect. + +### Are you a dog person or a cat person? +I like cats and will definitely want one as soon as my Lucie girl is not with us anymore. She loves cats too, but a little too much, I'm afraid. The cat would not be amused. But dogs are closer to my heart. The connection we have through working and training with our dogs is something I don't see happening with a cat anytime soon. + +### If there was one thing you could take with you to an uninhabited island, what would it be? Why? +Oomph. Only one? A well-stocked ereader that has a solar cell to recharge. + +### If there was one person you could take with you to an uninhabited island, who would it be? Why? +Shit. Can't I go alone? The older I get, the more of an introvert I'm becoming. Otherwise, I'd want one of my dogs. My youngest, Vroni, makes an excellent blanket in the evening, and she's always happy, cheerful, and ready for a game of some sort. While some humans make for excellent company, they're usually a bit heavy to use as a blanket. + +  + +--- + +  + +## 🪡 Technique of the week (X-minute read - by Karen) + +First things first, yes, this newsletter comes out quarterly, so this title's moderately apocryphal. "Technique of the quarter" lacks panache, so here we are. Just work with us. + +In a recent [Contributor Call](https://freesewing.org/community/calls/), some FreeSewing contributors mentioned that great tips and techniques sometimes get shared between the community on [Discord](https://discord.freesewing.org/), and it would be great to share them more broadly. So, here goes! + +A few weeks ago, a new sewist was having trouble with the top thread snapping over and over, and it led to some great troubleshooting tips. While this time, it didn't work (sometimes you have to throw in the towel and get your machine serviced, like if the timing's off), we thought the suggestions would be great to share! + +### Is your thread snapping when you try to sew? A few things that might be worth checking... +- The tension might be off. It's usually a numbered dial near the top of the machine, and it should generally be set to around 4 or 4.5, unless you're tinkering with it or more familiar with tension. If you're having problems and the tension is set to 2 or 7 or something, odds are high that's the problem. +- Do you have the presser foot up while you're threading the machine? This separates the tension discs, so your thread can slip between them. +- Maybe something's up with your tension discs themselves. These are the little discs that your thread travels between before it goes through the takeup lever. They hold the thread at the right tension, and if your thread slips outside of them, it can cause all sorts of problems. If the thread's definitely between the tension discs, but you think they're the source of the issue, make sure they're all cleaned out and no lint or dust is caught between them. +- Make sure you've got the right bobbin. Sometimes they look right, but even a minor variation from what's recommended for your specific machine can cause major problems. Once you're sure of that, make sure the bobbin is loaded in the right direction! +- It's also always worth making sure you've got a good fresh needle! The wrong size needle for the fabric can mess up your thread tension and your fabric. + +Good luck sewing! + +  + +--- + +  + + +## 🙏 Help us with social media + +Hey! Did you know FreeSewing is on social media? If the answer to that question is no, well, you're not alone. We could use some interested parties who are socially savvy to pick up the loose ends we've left trailing around Instagram, Reddit, and other platforms. + +### What platforms do you need help with? +Currently, FreeSewing is on [Discord](https://discord.freesewing.org/), [Facebook](https://www.facebook.com/groups/627769821272714), [Instagram](https://instagram.com/freesewing_org), [Reddit](https://www.reddit.com/r/freesewing/), [Twitter](https://twitter.com/freesewing_org), and [YouTube](https://youtube.com/channel/UCLAyxEL72gHvuKBpa-GmCvQ). (If you want to check out the whole list again later, you can find all of them here: [Where to find us](https://freesewing.org/community/where/).) + +Frankly, I don't think we're going to say no to support with any of them, but in particular our Instagram and Reddit accounts could use someone at the helm, and it's been a while since our YouTube had exciting new content. + +### What would I actually be doing? +Great question! It's important to FreeSewing that people volunteering their time are getting to work on things that they find interesting, joyful, motivating, etc. So, if you've got strong thoughts on the way one of these items could or should be managed, we're all ears. That being said, sometimes guidelines are helpful, so here's a little info. + +**Instagram**: This person would at least monitor messages and tags, and would re-post cool makes from FreeSewing users that tagged us or used one of the [FreeSewing hashtags](https://freesewing.org/community/hashtags/). You would abide by the [Community Standards](https://freesewing.org/docs/various/community-standards/) in all of their interactions on behalf of FreeSewing. If you wanted to go above and beyond, you might actually create content, pulling from makes posted in the showcase, cool things happening on [Github](https://github.com/freesewing/) or [Discord](https://discord.freesewing.org/), updates from [Contributor Calls](https://freesewing.org/community/calls/), etc. + +**Reddit**: This person would moderate the [FreeSewing subreddit], making sure that contributors were adhering to FreeSewing's [Community Standards](https://freesewing.org/docs/various/community-standards/). You would answer questions where possible and function as a connector to the rest of the FreeSewing community in cases where questions and contributions should be shared with more contributors. + +### What if, like so many before me, I can't commit long-term but would like to contribute *something*? + +**Create a YouTube tutorial**: You know how we said that our YouTube could use some new content? If you're ever inclined to make, for instance, a tutorial for a pattern, a video on how you hacked something to work for you, a how-to on some aspect of developing and contributing code to FreeSewing... Well, this list could go on, but the short version is that we'd love to see it. + +**Join our Facebook group or Discord**: It's only fun if it's a community. + +**Write for the newsletter**: If you've used a FreeSewing pattern for something interesting, developed a cool new contribution for FreeSewing, would love to share a deep dive on a sewing technique, we'll gladly help get it into the newsletter, onto the Showcase, or wherever it best fits. + +You can let us know if you're game to help out with any of these by simply replying to this email, or by hopping in the Discord. + +  + +--- + +  + + + +## ⚫ It's always darkest before dawn + +I had to look it up but at the beginning of this year, I wrote the following +about the release of FreeSewing version 3: + +> *You can start the clock today and I promise that it will be out before the end of the year.* +> *If it's Q4, I will be a bit disappointed. If it's Q3, I will be happy.* +> *If it's Q2 I will be thrilled. And if it's Q1 I'll be very surprised.* + +Today marks the start of Q3 and so the pressure mounts to deliver on that promise. +I had initially penciled in the 25th of August as a bit of a hard deadline +because it marks 6 years to the day since I launched FreeSewing.org. + +If I had been smart, I would have gone back to [that announcement blog +post](https://freesewing.org/blog/open-for-business/) and heeded the warning in +its prophetic opening sentence: + +> *When I released freesewing core back in March, I did not expect it to take +> another 5 months to finally have a proper front-end for it, but here we are.* + +Because this is exactly the situation we find ourselves in today. The +foundational work is largely completed. We may still tweak things left and right +as we make progress, but the main effort is now on building a new frontend for +our flagship website. Somehow, we need to make all of that work under the hood +available to you in a way that is simple yet powerful, and intuitive despite +FreeSewing providing functionality that is not what people typically expect from +*a sewing pattern website*. + +I am no longer certain that I'll make that self-imposed August 25 deadline. +Although I am still cautiously optimistic that by the end of this quarter, when +the next edition of this newsletter rolls around, we'll have reasons to +celebrate. Still, it will be ready when it's ready. Estimating the amount of +time it will take to write software is notoriously difficult when it's your day +job, it gets increasingly more hand-wavy when you are limited to your evenings +and weekends to move the needle. + +This somewhat stoic *it will be ready when it's ready* attitude does not mean I +am less determined to make it happen. It's more the realization that as much as +I want to sprint to the finish line, this is more like a marathon. And blowing +up before the finish line is a clear and present danger. + +The last month or so has been difficult for me. The increasing pressure to +deliver had sucked most of the joy out of my FreeSewing work, and I found +myself irritable and easily triggered. I was attending a session on burnout +prevention at work recently, and I recognized so many of the warning flags in +myself that I realized that staying the course was too dangerous. + +My commitment to the success and growth of FreeSewing remains unwavering. On +the other hand, I felt something had to give, so I ultimately decided that the +best way forward for the foreseeable future would be to *only* focus on getting +v3 out the door. + +So for the time being, and probably at least until v3 is ready, I am taking a +step back from the community to allow me to work on FreeSewing free of +distractions. It is this same somewhat hermit-like focus that has brought +FreeSewing into this world, it's what brought you (the current) FreeSewing v2, +and I believe it will get us to FreeSewing v3 as well. + +I'm in a better place now. It was touch-and-go there for a moment, and I'd like +to apologize to those members of the community who had to deal with my +increasingly frazzled mental health in the weeks leading up to my course +correction. + +I'm still not sure I'll make the deadlines I've set out for myself. But I feel +positive and hopeful again that the work we're doing is worthwhile and will pay +off in the end. And -- should there by any doubt about that -- I know for a +fact that the FreeSewing community is perfectly wonderful without me around too. +And on some of my more difficult days, probably even more so. + + diff --git a/markdown/org/showcase/aaron-by-joost/de.md b/markdown/org/showcase/aaron-by-joost/de.md new file mode 100644 index 00000000000..596eb3f9518 --- /dev/null +++ b/markdown/org/showcase/aaron-by-joost/de.md @@ -0,0 +1,12 @@ +--- +maker: "Joost De Cock" +caption: "An Aaron A-shirt by Joost" +date: "2017-03-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f4f808be6bd3b6f7dd33c4da10e7dd81a8a89df8-2048x1365.jpg" +intro: "Here's an Aaron top I whipped up. I wear this under my shirts, and I'm rather pleased with it." +title: "[auf Englisch] Joost does Aaron" +--- + + +Here's an Aaron top I whipped up. I wear this under my shirts, and I'm rather pleased with it. + diff --git a/markdown/org/showcase/aaron-by-joost/en.md b/markdown/org/showcase/aaron-by-joost/en.md new file mode 100644 index 00000000000..6d3b786a386 --- /dev/null +++ b/markdown/org/showcase/aaron-by-joost/en.md @@ -0,0 +1,11 @@ +--- +maker: "Joost De Cock" +caption: "An Aaron A-shirt by Joost" +date: "2017-03-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f4f808be6bd3b6f7dd33c4da10e7dd81a8a89df8-2048x1365.jpg" +intro: "Here's an Aaron top I whipped up. I wear this under my shirts, and I'm rather pleased with it." +title: "Joost does Aaron" +--- + +Here's an Aaron top I whipped up. I wear this under my shirts, and I'm rather pleased with it. + diff --git a/markdown/org/showcase/aaron-by-joost/es.md b/markdown/org/showcase/aaron-by-joost/es.md new file mode 100644 index 00000000000..b6b5fb530f1 --- /dev/null +++ b/markdown/org/showcase/aaron-by-joost/es.md @@ -0,0 +1,11 @@ +--- +maker: "Joost De Cock" +caption: "An Aaron A-shirt by Joost" +date: "2017-03-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f4f808be6bd3b6f7dd33c4da10e7dd81a8a89df8-2048x1365.jpg" +intro: "Here's an Aaron top I whipped up. I wear this under my shirts, and I'm rather pleased with it." +title: "Joost does Aaron [No traducido]" +--- + +Here's an Aaron top I whipped up. I wear this under my shirts, and I'm rather pleased with it. + diff --git a/markdown/org/showcase/aaron-by-joost/fr.md b/markdown/org/showcase/aaron-by-joost/fr.md new file mode 100644 index 00000000000..8b5f486fa85 --- /dev/null +++ b/markdown/org/showcase/aaron-by-joost/fr.md @@ -0,0 +1,12 @@ +--- +maker: "Joost De Cock" +caption: "Un débardeur Aaron par Joost" +date: "2017-03-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f4f808be6bd3b6f7dd33c4da10e7dd81a8a89df8-2048x1365.jpg" +intro: "Voici un débardeur Aaron que j'ai cousu rapidement. Je le porte sous mes chemises, et j'en suis plutôt content." +title: "Joost fait Aaron" +--- + + +Voici un débardeur Aaron que j'ai cousu rapidement. Je le porte sous mes chemises, et j'en suis plutôt content. + diff --git a/markdown/org/showcase/aaron-by-joost/nl.md b/markdown/org/showcase/aaron-by-joost/nl.md new file mode 100644 index 00000000000..458879c0cfe --- /dev/null +++ b/markdown/org/showcase/aaron-by-joost/nl.md @@ -0,0 +1,12 @@ +--- +maker: "Joost De Cock" +caption: "Een Aaron hemdje door Joost" +date: "2017-03-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f4f808be6bd3b6f7dd33c4da10e7dd81a8a89df8-2048x1365.jpg" +intro: "Hier is een Aaron hemdje dat ik in elkaar geflanst heb. Ik draag dit onder mijn hemden, en ben er best blij mee." +title: "Joost doet Aaron" +--- + + +Hier is een Aaron hemdje dat ik in elkaar geflanst heb. Ik draag dit onder mijn hemden, en ben er best blij mee. + diff --git a/markdown/org/showcase/airline-blanket-sven/de.md b/markdown/org/showcase/airline-blanket-sven/de.md new file mode 100644 index 00000000000..164bf463df9 --- /dev/null +++ b/markdown/org/showcase/airline-blanket-sven/de.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "You'll never look at those blankets on a plane the same way again." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9a8c3ceab1c7e91e3a6740fe34e73e8abec95acd-1080x1080.jpg" +intro: "This image is from the Instagram feed of funloveadventure . It is published here with permission." +title: "[auf Englisch] A Sven made out of two airline blankets" +--- + + +[This image](https://www.instagram.com/p/BeKLaPfhGbU/) is from [the Instagram feed of funloveadventure](https://www.instagram.com/funloveadventure/). It is published here with permission. + diff --git a/markdown/org/showcase/airline-blanket-sven/en.md b/markdown/org/showcase/airline-blanket-sven/en.md new file mode 100644 index 00000000000..a61d2793724 --- /dev/null +++ b/markdown/org/showcase/airline-blanket-sven/en.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "You'll never look at those blankets on a plane the same way again." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9a8c3ceab1c7e91e3a6740fe34e73e8abec95acd-1080x1080.jpg" +intro: "A Sven made out of two airline blankets" +title: "A Sven made out of two airline blankets" +--- + + +[This image](https://www.instagram.com/p/BeKLaPfhGbU/) +is from [the Instagram feed of funloveadventure](https://www.instagram.com/funloveadventure/). +It is published here with permission. + diff --git a/markdown/org/showcase/airline-blanket-sven/es.md b/markdown/org/showcase/airline-blanket-sven/es.md new file mode 100644 index 00000000000..71eba75e017 --- /dev/null +++ b/markdown/org/showcase/airline-blanket-sven/es.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "You'll never look at those blankets on a plane the same way again." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9a8c3ceab1c7e91e3a6740fe34e73e8abec95acd-1080x1080.jpg" +intro: "A Sven made out of two airline blankets [No traducido]" +title: "A Sven made out of two airline blankets [No traducido]" +--- + + +[This image](https://www.instagram.com/p/BeKLaPfhGbU/) +is from [the Instagram feed of funloveadventure](https://www.instagram.com/funloveadventure/). +It is published here with permission. + diff --git a/markdown/org/showcase/airline-blanket-sven/fr.md b/markdown/org/showcase/airline-blanket-sven/fr.md new file mode 100644 index 00000000000..df85c5c8b8d --- /dev/null +++ b/markdown/org/showcase/airline-blanket-sven/fr.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Vous ne regarderez plus jamais ces couvertures d'avion de la même façon." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9a8c3ceab1c7e91e3a6740fe34e73e8abec95acd-1080x1080.jpg" +intro: "Cette photo est issue du feed Instagram de funloveadventure . Elle est publiée ici avec son autorisation." +title: "Un Sven fait avec eux couvertures de compagnie aérienne" +--- + + +[Cette photo](https://www.instagram.com/p/BeKLaPfhGbU/) est issue du [feed Instagram de funloveadventure](https://www.instagram.com/funloveadventure/). Elle est publiée ici avec son autorisation. + diff --git a/markdown/org/showcase/airline-blanket-sven/nl.md b/markdown/org/showcase/airline-blanket-sven/nl.md new file mode 100644 index 00000000000..a8f673df6b8 --- /dev/null +++ b/markdown/org/showcase/airline-blanket-sven/nl.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Die dekentjes op het vliegtuig zullen nooit meer hezelfde zijn." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9a8c3ceab1c7e91e3a6740fe34e73e8abec95acd-1080x1080.jpg" +intro: "Deze afbeelding komt van de Instagram feed van funloveadventure . Ze werd hier gepost met toestemming." +title: "Een Sven gemaakt uit twee vliegtuigdekens" +--- + + +[Deze afbeelding](https://www.instagram.com/p/BeKLaPfhGbU/) komt van [de Instagram feed van funloveadventure](https://www.instagram.com/funloveadventure/). Ze werd hier gepost met toestemming. + diff --git a/markdown/org/showcase/albert-by-wouter/de.md b/markdown/org/showcase/albert-by-wouter/de.md new file mode 100644 index 00000000000..e773fd54990 --- /dev/null +++ b/markdown/org/showcase/albert-by-wouter/de.md @@ -0,0 +1,12 @@ +--- +maker: "Wouter.vdub" +caption: "The customer is very happy with it!" +date: "2020-10-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ebef91daa8acf992f814415e610a655a03278186-1200x1600.jpg" +intro: "[auf Englisch] The first version of albert, made for his daughter, by Wouter.vdub" +title: "[auf Englisch] The first version of albert, made for his daughter, by Wouter.vdub" +--- + +![View of the front](https://posts.freesewing.org/uploads/albert_by_wouter_albert_back_846f1b89ac.jpg "View of the front") + +This version has some extra straps on the back to keep it closed. My daughter teaches in a school, so it's important to be able to bend over and not have it open up in the back. The cross straps work fine for normal kitchen use. diff --git a/markdown/org/showcase/albert-by-wouter/en.md b/markdown/org/showcase/albert-by-wouter/en.md new file mode 100644 index 00000000000..f1bcbaac7e9 --- /dev/null +++ b/markdown/org/showcase/albert-by-wouter/en.md @@ -0,0 +1,13 @@ +--- +maker: "Wouter.vdub" +caption: "The customer is very happy with it!" +date: "2020-10-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ebef91daa8acf992f814415e610a655a03278186-1200x1600.jpg" +intro: "The first version of albert, made for his daughter, by Wouter.vdub" +title: "The first version of albert, made for his daughter, by Wouter.vdub" +--- + +![View of the back ](https://posts.freesewing.org/uploads/albert_by_wouter_albert_back_846f1b89ac.jpg "View of the back ") +![View of the front](https://posts.freesewing.org/uploads/albert_by_wouter_albert_side_8505eb3b84.jpg "View of the front") + +This version has some extra straps on the back to keep it closed. My daughter teaches in a school, so it's important to be able to bend over and not have it open up in the back. The cross straps work fine for normal kitchen use. diff --git a/markdown/org/showcase/albert-by-wouter/es.md b/markdown/org/showcase/albert-by-wouter/es.md new file mode 100644 index 00000000000..7211be58c52 --- /dev/null +++ b/markdown/org/showcase/albert-by-wouter/es.md @@ -0,0 +1,13 @@ +--- +maker: "Wouter.vdub" +caption: "The customer is very happy with it!" +date: "2020-10-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ebef91daa8acf992f814415e610a655a03278186-1200x1600.jpg" +intro: "The first version of albert, made for his daughter, by Wouter.vdub [No traducido]" +title: "The first version of albert, made for his daughter, by Wouter.vdub [No traducido]" +--- + +![View of the back ](https://posts.freesewing.org/uploads/albert_by_wouter_albert_back_846f1b89ac.jpg "View of the back ") +![View of the front](https://posts.freesewing.org/uploads/albert_by_wouter_albert_side_8505eb3b84.jpg "View of the front") + +This version has some extra straps on the back to keep it closed. My daughter teaches in a school, so it's important to be able to bend over and not have it open up in the back. The cross straps work fine for normal kitchen use. diff --git a/markdown/org/showcase/albert-by-wouter/fr.md b/markdown/org/showcase/albert-by-wouter/fr.md new file mode 100644 index 00000000000..3bd7957a645 --- /dev/null +++ b/markdown/org/showcase/albert-by-wouter/fr.md @@ -0,0 +1,12 @@ +--- +maker: "Wouter.vdub" +caption: "La cliente en est très satisfaite !" +date: "2020-10-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ebef91daa8acf992f814415e610a655a03278186-1200x1600.jpg" +intro: "La première version de l'albert, faite pour sa fille, par Wouter.vdub" +title: "La première version de l'albert, faite pour sa fille, par Wouter.vdub" +--- + +![Photo de l'avant](https://posts.freesewing.org/uploads/albert_by_wouter_albert_back_846f1b89ac.jpg "Photo de l'avant") + +Cette version a quelques liens supplémentaires au dos pour le garder fermé. Ma fille enseigne dans une école, il est donc important de pouvoir se plier et qu'il ne s'ouvre pas dans le dos. Les liens croisés fonctionnent très bien pour une utilisation normale en cuisine. diff --git a/markdown/org/showcase/albert-by-wouter/nl.md b/markdown/org/showcase/albert-by-wouter/nl.md new file mode 100644 index 00000000000..4e431b63171 --- /dev/null +++ b/markdown/org/showcase/albert-by-wouter/nl.md @@ -0,0 +1,13 @@ +--- +maker: "Wouter.vdub" +caption: "The customer is very happy with it!" +date: "2020-10-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ebef91daa8acf992f814415e610a655a03278186-1200x1600.jpg" +intro: "The first version of albert, made for his daughter, by Wouter.vdub [Niet vertaald]" +title: "The first version of albert, made for his daughter, by Wouter.vdub [Niet vertaald]" +--- + +![View of the back ](https://posts.freesewing.org/uploads/albert_by_wouter_albert_back_846f1b89ac.jpg "View of the back ") +![View of the front](https://posts.freesewing.org/uploads/albert_by_wouter_albert_side_8505eb3b84.jpg "View of the front") + +This version has some extra straps on the back to keep it closed. My daughter teaches in a school, so it's important to be able to bend over and not have it open up in the back. The cross straps work fine for normal kitchen use. diff --git a/markdown/org/showcase/anneke-huey-black/de.md b/markdown/org/showcase/anneke-huey-black/de.md new file mode 100644 index 00000000000..93dae9dff14 --- /dev/null +++ b/markdown/org/showcase/anneke-huey-black/de.md @@ -0,0 +1,21 @@ +--- +maker: "Anneke Caramin" +caption: "Anneke mit ihrem neusten Huey, diesmal in Schwarz." +date: "2020-10-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4e6d5a2fdf43b6904230f7ef7594bbcd41dd8759-640x640.jpg" +intro: "Anneke hat einige Variationen des Hey Kapuzenpullis gemacht. Check out her other ones here and here ." +title: "Ein schwarzer Huey von Anneke" +--- + +Anneke hat einige Variationen des Hey Kapuzenpullis gemacht. Check out her other ones [here](https://freesewing.org/showcase/anneke-huey/) and [here](https://freesewing.org/showcase/anneke-huey-grey/). + +Andere Ansichten. + + +![Frontansicht von Huey](https://posts.freesewing.org/uploads/anneke_huey_black_anneke2_a377a78430.jpg "Frontansicht von Huey") + +![Rückansicht von Huey](https://posts.freesewing.org/uploads/anneke_huey_black_anneke3_02ae401053.jpg "Rückansicht von Huey") + +Dieser Beitrag erschien ursprünglich auf [Instagram](https://www.instagram.com/p/Bz3jSeJIiYG/?utm_source=ig_web_copy_link). + +It is reposted here with permission. diff --git a/markdown/org/showcase/anneke-huey-black/en.md b/markdown/org/showcase/anneke-huey-black/en.md new file mode 100644 index 00000000000..4d8e1c475bc --- /dev/null +++ b/markdown/org/showcase/anneke-huey-black/en.md @@ -0,0 +1,23 @@ +--- +maker: "Anneke Caramin" +caption: "Anneke rocking her latest Huey, this time in black." +date: "2020-10-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4e6d5a2fdf43b6904230f7ef7594bbcd41dd8759-640x640.jpg" +intro: "A Black Huey by Anneke" +title: "A Black Huey by Anneke" +--- + +Anneke has made several variations on the Huey hoodie. Check out her other +ones [here](https://freesewing.org/showcase/anneke-huey/) and +[here](https://freesewing.org/showcase/anneke-huey-grey/). + +Other views. + +![Front view of Huey](https://posts.freesewing.org/uploads/anneke_huey_black_anneke2_a377a78430.jpg "Front view of Huey") + +![Back view of Huey](https://posts.freesewing.org/uploads/anneke_huey_black_anneke3_02ae401053.jpg "Back view of Huey") + +This post originally appeared on +[Instagram](https://www.instagram.com/p/Bz3jSeJIiYG/?utm_source=ig_web_copy_link). + +It is reposted here with permission. diff --git a/markdown/org/showcase/anneke-huey-black/es.md b/markdown/org/showcase/anneke-huey-black/es.md new file mode 100644 index 00000000000..870491bedec --- /dev/null +++ b/markdown/org/showcase/anneke-huey-black/es.md @@ -0,0 +1,23 @@ +--- +maker: "Anneke Caramin" +caption: "Anneke rocking her latest Huey, this time in black." +date: "2020-10-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4e6d5a2fdf43b6904230f7ef7594bbcd41dd8759-640x640.jpg" +intro: "A Black Huey by Anneke [No traducido]" +title: "A Black Huey by Anneke [No traducido]" +--- + +Anneke has made several variations on the Huey hoodie. Check out her other +ones [here](https://freesewing.org/showcase/anneke-huey/) and +[here](https://freesewing.org/showcase/anneke-huey-grey/). + +Other views. + +![Front view of Huey](https://posts.freesewing.org/uploads/anneke_huey_black_anneke2_a377a78430.jpg "Front view of Huey") + +![Back view of Huey](https://posts.freesewing.org/uploads/anneke_huey_black_anneke3_02ae401053.jpg "Back view of Huey") + +This post originally appeared on +[Instagram](https://www.instagram.com/p/Bz3jSeJIiYG/?utm_source=ig_web_copy_link). + +It is reposted here with permission. diff --git a/markdown/org/showcase/anneke-huey-black/fr.md b/markdown/org/showcase/anneke-huey-black/fr.md new file mode 100644 index 00000000000..e1120d7771c --- /dev/null +++ b/markdown/org/showcase/anneke-huey-black/fr.md @@ -0,0 +1,22 @@ +--- +maker: "Anneke Caramin" +caption: "Anneke dans son dernier Huey, cette fois en noir." +date: "2020-10-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4e6d5a2fdf43b6904230f7ef7594bbcd41dd8759-640x640.jpg" +intro: "Anneke a fait plusieurs variations du gilet à capuche Huey. Découvrez ses autres versions ici et ici ." +title: "Un Huey noir par Anneke" +--- + +Anneke a fait plusieurs variations du gilet à capuche Huey. Découvrez ses autres versions [ici](https://fr.freesewing.org/showcase/anneke-huey/) et [ici](https://fr.freesewing.org/showcase/anneke-huey-grey/). + +Autres vues + + +![Vue de devant de Huey](https://posts.freesewing.org/uploads/anneke_huey_black_anneke2_a377a78430.jpg "Vue de devant Huey") + +![Vue de dos Huey](https://posts.freesewing.org/uploads/anneke_huey_black_anneke3_02ae401053.jpg "Vue de dos Huey") + + +Ce message est apparu à l'origine sur [Instagram](https://www.instagram.com/p/Bz3jSeJIiYG/?utm_source=ig_web_copy_link). + +Elle est publiée ici avec son autorisation. diff --git a/markdown/org/showcase/anneke-huey-black/nl.md b/markdown/org/showcase/anneke-huey-black/nl.md new file mode 100644 index 00000000000..a6b015865b2 --- /dev/null +++ b/markdown/org/showcase/anneke-huey-black/nl.md @@ -0,0 +1,20 @@ +--- +maker: "Anneke Caramin" +caption: "Anneke rocking her latest Huey, this time in black." +date: "2020-10-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4e6d5a2fdf43b6904230f7ef7594bbcd41dd8759-640x640.jpg" +intro: "Anneke has made several variations on the Huey hoodie. Check out her other ones here and here ." +title: "[Engelstalig] A Black Huey by Anneke" +--- + +Anneke has made several variations on the Huey hoodie. Check out her other ones [here](https://freesewing.org/showcase/anneke-huey/) and [here](https://freesewing.org/showcase/anneke-huey-grey/). + +Other views. + +![Front view of Huey](https://posts.freesewing.org/uploads/anneke_huey_black_anneke2_a377a78430.jpg) + +![Back view of Huey](https://posts.freesewing.org/uploads/anneke_huey_black_anneke2_a377a78430.jpg "Back view of Huey") + +This post originally appeared on [Instagram](https://www.instagram.com/p/Bz3jSeJIiYG/?utm_source=ig_web_copy_link). + +Hij werd hier gepost met toestemming. diff --git a/markdown/org/showcase/anneke-huey-grey/de.md b/markdown/org/showcase/anneke-huey-grey/de.md new file mode 100644 index 00000000000..c9f0610858e --- /dev/null +++ b/markdown/org/showcase/anneke-huey-grey/de.md @@ -0,0 +1,12 @@ +--- +maker: "Anneke Caramin" +caption: "Anneke trägt einen hellgrauen Huey mit schwarzen Bündchen, die auf diesem schwarzem Rock nicht sehr offensichtlich sind." +date: "2017-12-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d52577b6695162b240cb298ab4af8d828527a84d-2000x1295.jpg" +intro: "Das ist Annekes zweiter Huey" +title: "Noch ein grauer Huey von Anneke Caramin" +--- + + +Das ist Annekes [zweiter Huey](/en/showcase/anneke-huey/) + diff --git a/markdown/org/showcase/anneke-huey-grey/en.md b/markdown/org/showcase/anneke-huey-grey/en.md new file mode 100644 index 00000000000..666a7972e5a --- /dev/null +++ b/markdown/org/showcase/anneke-huey-grey/en.md @@ -0,0 +1,11 @@ +--- +maker: "Anneke Caramin" +caption: "Anneke is wearing a light grey Huey with black ribbing, which isn't very obvious on this black skirt." +date: "2017-12-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d52577b6695162b240cb298ab4af8d828527a84d-2000x1295.jpg" +intro: "This is Anneke's second Huey" +title: "Another grey Huey by Anneke Caramin" +--- + +This is Anneke's [second Huey](/en/showcase/anneke-huey/) + diff --git a/markdown/org/showcase/anneke-huey-grey/es.md b/markdown/org/showcase/anneke-huey-grey/es.md new file mode 100644 index 00000000000..4b2e4e54080 --- /dev/null +++ b/markdown/org/showcase/anneke-huey-grey/es.md @@ -0,0 +1,11 @@ +--- +maker: "Anneke Caramin" +caption: "Anneke is wearing a light grey Huey with black ribbing, which isn't very obvious on this black skirt." +date: "2017-12-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d52577b6695162b240cb298ab4af8d828527a84d-2000x1295.jpg" +intro: "This is Anneke's second Huey" +title: "Another grey Huey by Anneke Caramin [No traducido]" +--- + +This is Anneke's [second Huey](/en/showcase/anneke-huey/) + diff --git a/markdown/org/showcase/anneke-huey-grey/fr.md b/markdown/org/showcase/anneke-huey-grey/fr.md new file mode 100644 index 00000000000..cc853162479 --- /dev/null +++ b/markdown/org/showcase/anneke-huey-grey/fr.md @@ -0,0 +1,12 @@ +--- +maker: "Anneke Caramin" +caption: "Anneke porte un Huey gris clair avec des bandes noires, ce qui n'est pas très évident sur cette jupe noire." +date: "2017-12-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d52577b6695162b240cb298ab4af8d828527a84d-2000x1295.jpg" +intro: "Voici la seconde Huey d'Anneke" +title: "Un autre Huey gris par Anneke Caramin" +--- + + +Voici la [seconde Huey d'Anneke](/en/showcase/anneke-huey/) + diff --git a/markdown/org/showcase/anneke-huey-grey/nl.md b/markdown/org/showcase/anneke-huey-grey/nl.md new file mode 100644 index 00000000000..b1817fae72d --- /dev/null +++ b/markdown/org/showcase/anneke-huey-grey/nl.md @@ -0,0 +1,12 @@ +--- +maker: "Anneke Caramin" +caption: "Anneke draagt een lichtgrijze Huey met zwarte boordstof, die niet echt zichtbaar is op deze zwarte rok." +date: "2017-12-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d52577b6695162b240cb298ab4af8d828527a84d-2000x1295.jpg" +intro: "Dit is de tweede Huey die Anneke maakte" +title: "Nog een grijze Huey van Anneke Caramin" +--- + + +Dit is de [tweede Huey](/en/showcase/anneke-huey/) die Anneke maakte + diff --git a/markdown/org/showcase/anneke-huey/de.md b/markdown/org/showcase/anneke-huey/de.md new file mode 100644 index 00000000000..337dbc00859 --- /dev/null +++ b/markdown/org/showcase/anneke-huey/de.md @@ -0,0 +1,20 @@ +--- +maker: "Anneke Caramin" +caption: "Anneke seen here wearing Huey, while simultaniously smashing the patriarchy by refusing to smile." +date: "2017-11-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f70ab6381595eaff09641462c31b6b20121a1e3a-970x776.jpg" +intro: "[auf Englisch] A grey Huey by Anneke Caramin" +title: "[auf Englisch] A grey Huey by Anneke Caramin" +--- + +![View of the inside](https://posts.freesewing.org/uploads/anneke_huey_facing_8c3874be29.jpg "View of the inside") + + + +###### See the original on Anneke's blog +This post [originally appeared](http://www.annekecaramin.com/2017/11/pleasure-dot-loathing-dot-huey-dot.html) +on [annekecaramin.com](http://www.annekecaramin.com/). + +It is reposted here with permission. + + diff --git a/markdown/org/showcase/anneke-huey/en.md b/markdown/org/showcase/anneke-huey/en.md new file mode 100644 index 00000000000..6677e4326a8 --- /dev/null +++ b/markdown/org/showcase/anneke-huey/en.md @@ -0,0 +1,18 @@ +--- +maker: "Anneke Caramin" +caption: "Anneke seen here wearing Huey, while simultaniously smashing the patriarchy by refusing to smile." +date: "2017-11-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f70ab6381595eaff09641462c31b6b20121a1e3a-970x776.jpg" +intro: "A grey Huey by Anneke Caramin" +title: "A grey Huey by Anneke Caramin" +--- + +![View of the inside](https://posts.freesewing.org/uploads/anneke_huey_facing_8c3874be29.jpg "View of the inside") + +**See the original on Anneke's blog** + +This post [originally appeared](http://www.annekecaramin.com/2017/11/pleasure-dot-loathing-dot-huey-dot.html) +on [annekecaramin.com](http://www.annekecaramin.com/). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/anneke-huey/es.md b/markdown/org/showcase/anneke-huey/es.md new file mode 100644 index 00000000000..79cd99f72fb --- /dev/null +++ b/markdown/org/showcase/anneke-huey/es.md @@ -0,0 +1,18 @@ +--- +maker: "Anneke Caramin" +caption: "Anneke seen here wearing Huey, while simultaniously smashing the patriarchy by refusing to smile." +date: "2017-11-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f70ab6381595eaff09641462c31b6b20121a1e3a-970x776.jpg" +intro: "A grey Huey by Anneke Caramin [No traducido]" +title: "A grey Huey by Anneke Caramin [No traducido]" +--- + +![View of the inside](https://posts.freesewing.org/uploads/anneke_huey_facing_8c3874be29.jpg "View of the inside") + +**See the original on Anneke's blog** + +This post [originally appeared](http://www.annekecaramin.com/2017/11/pleasure-dot-loathing-dot-huey-dot.html) +on [annekecaramin.com](http://www.annekecaramin.com/). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/anneke-huey/fr.md b/markdown/org/showcase/anneke-huey/fr.md new file mode 100644 index 00000000000..05ae6253014 --- /dev/null +++ b/markdown/org/showcase/anneke-huey/fr.md @@ -0,0 +1,20 @@ +--- +maker: "Anneke Caramin" +caption: "Anneke porte ici Huey, tout en détruisant simultanément le patriarcat en refusant de sourire." +date: "2017-11-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f70ab6381595eaff09641462c31b6b20121a1e3a-970x776.jpg" +intro: "Un Huey gris par Anneke Caramin" +title: "Un Huey gris par Anneke Caramin" +--- + +![Vue de l'intérieur](https://posts.freesewing.org/uploads/anneke_huey_facing_8c3874be29.jpg "Vue de l'intérieur") + + + +###### Voir l'original sur le blog d'Anneke +Ce post [est apparu à l'origine](http://www.annekecaramin.com/2017/11/pleasure-dot-loathing-dot-huey-dot.html) +sur [annekecaramin.com](http://www.annekecaramin.com/). + +Elle est publiée ici avec son autorisation. + + diff --git a/markdown/org/showcase/anneke-huey/nl.md b/markdown/org/showcase/anneke-huey/nl.md new file mode 100644 index 00000000000..51f411d7172 --- /dev/null +++ b/markdown/org/showcase/anneke-huey/nl.md @@ -0,0 +1,20 @@ +--- +maker: "Anneke Caramin" +caption: "Anneke wordt hier gespot met een Huey, en verplettert tegelijk het patriarchaat door niet te lachen." +date: "2017-11-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f70ab6381595eaff09641462c31b6b20121a1e3a-970x776.jpg" +intro: "Een grijze Huey van Anneke Caramin" +title: "Een grijze Huey van Anneke Caramin" +--- + +![Zicht op de binnenkant](https://posts.freesewing.org/uploads/anneke_huey_facing_8c3874be29.jpg "Zicht op de binnenkant") + + + +###### See the original on Anneke's blog +This post [originally appeared](http://www.annekecaramin.com/2017/11/pleasure-dot-loathing-dot-huey-dot.html) +on [annekecaramin.com](http://www.annekecaramin.com/). + +Hij werd hier gepost met toestemming. + + diff --git a/markdown/org/showcase/bella-block/de.md b/markdown/org/showcase/bella-block/de.md new file mode 100644 index 00000000000..d845a8c3654 --- /dev/null +++ b/markdown/org/showcase/bella-block/de.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "This is a muslin of the Bella bodice block made with minimal adjustments" +date: "2021-01-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/854a688f4a7447de0b44f8371dbb2d3e0fdce9ea-1488x1680.jpg" +intro: "This is a muslin of the Bella bodice block made with minimal adjustments. The neckline seam allowance has been trimmed away and the seams were left raw, but otherwise it was made as generated." +title: "[auf Englisch] Bella bodice block" +--- + + +This is a muslin of the Bella bodice block made with minimal adjustments. The neckline seam allowance has been trimmed away and the seams were left raw, but otherwise it was made as generated. + + + +This picture is from the [FreeSewing Discord](https://discord.freesewing.org/) and has been shared here with permission. + + + diff --git a/markdown/org/showcase/bella-block/en.md b/markdown/org/showcase/bella-block/en.md new file mode 100644 index 00000000000..a6129c9b70a --- /dev/null +++ b/markdown/org/showcase/bella-block/en.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "This is a muslin of the Bella bodice block made with minimal adjustments" +date: "2021-01-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/854a688f4a7447de0b44f8371dbb2d3e0fdce9ea-1488x1680.jpg" +intro: "Bella bodice block" +title: "Bella bodice block" +--- + + +This is a muslin of the Bella bodice block made with minimal adjustments. +The neckline seam allowance has been trimmed away and the seams were left raw, but otherwise it was made as generated. + + + +This picture is from the [FreeSewing Discord](https://discord.freesewing.org/) and has been shared here with permission. + + + diff --git a/markdown/org/showcase/bella-block/es.md b/markdown/org/showcase/bella-block/es.md new file mode 100644 index 00000000000..bee75c5294b --- /dev/null +++ b/markdown/org/showcase/bella-block/es.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "This is a muslin of the Bella bodice block made with minimal adjustments" +date: "2021-01-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/854a688f4a7447de0b44f8371dbb2d3e0fdce9ea-1488x1680.jpg" +intro: "Bella bodice block [No traducido]" +title: "Bella bodice block [No traducido]" +--- + + +This is a muslin of the Bella bodice block made with minimal adjustments. +The neckline seam allowance has been trimmed away and the seams were left raw, but otherwise it was made as generated. + + + +This picture is from the [FreeSewing Discord](https://discord.freesewing.org/) and has been shared here with permission. + + + diff --git a/markdown/org/showcase/bella-block/fr.md b/markdown/org/showcase/bella-block/fr.md new file mode 100644 index 00000000000..706ae91ad00 --- /dev/null +++ b/markdown/org/showcase/bella-block/fr.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Il s'agit d'une toile du bloc de buste Bella faite avec un minimum d'ajustements" +date: "2021-01-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/854a688f4a7447de0b44f8371dbb2d3e0fdce9ea-1488x1680.jpg" +intro: "Il s'agit d'une toile du bloc de buste Bella faite avec un minimum d'ajustements. La marge de couture de l'encolure a été enlevée et les coutures ont été laissées brutes, mais autrement, elle a été faite comme prévue." +title: "Bloc de corsage de Bella" +--- + + +Il s'agit d'une toile du bloc de buste Bella faite avec un minimum d'ajustements. La marge de couture de l'encolure a été enlevée et les coutures ont été laissées brutes, mais autrement, elle a été faite comme prévue. + + + +Cette image provient du [Discord FreeSewing](https://discord.freesewing.org/) et a été partagée ici avec permission. + + + diff --git a/markdown/org/showcase/bella-block/nl.md b/markdown/org/showcase/bella-block/nl.md new file mode 100644 index 00000000000..0935deb8ae8 --- /dev/null +++ b/markdown/org/showcase/bella-block/nl.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Dit is een toile van het Bella basispatroon met minimale aanpassingen" +date: "2021-01-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/854a688f4a7447de0b44f8371dbb2d3e0fdce9ea-1488x1680.jpg" +intro: "Dit is een toile van het Bella basispatroon met minimale aanpassingen. De naadwaarde aan de halslijn is weggeknipt en de naden werden niet afgewerkt, maar verder is het gemaakt zoals het gegenereerd werd." +title: "Bella basispatroon bovenstuk" +--- + + +Dit is een toile van het Bella basispatroon met minimale aanpassingen. De naadwaarde aan de halslijn is weggeknipt en de naden werden niet afgewerkt, maar verder is het gemaakt zoals het gegenereerd werd. + + + +Deze foto komt van de [FreeSewing Discord](https://discord.freesewing.org/) en is hier gedeeld met toestemming. + + + diff --git a/markdown/org/showcase/bella-by-karen/de.md b/markdown/org/showcase/bella-by-karen/de.md new file mode 100644 index 00000000000..764afb5ca2b --- /dev/null +++ b/markdown/org/showcase/bella-by-karen/de.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Karen's shirt based on the Bella block" +date: "2021-02-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d5ba88624a180a770eb8f022022447b5c7f91649-810x810.jpg" +intro: "Karen made this fabulous shirt based on the Bella block. She used the Bella block with most default options, only modifying to take in the back darts a bit more. She added several additional design elements to make this shirt." +title: "[auf Englisch] Bella by Karen" +--- + + +Karen made this fabulous shirt based on the Bella block. She used the Bella block with most default options, only modifying to take in the back darts a bit more. She added several additional design elements to make this shirt. + + + +This picture is from Discord and is reposted here with permission. + + + diff --git a/markdown/org/showcase/bella-by-karen/en.md b/markdown/org/showcase/bella-by-karen/en.md new file mode 100644 index 00000000000..75649cd3878 --- /dev/null +++ b/markdown/org/showcase/bella-by-karen/en.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Karen's shirt based on the Bella block" +date: "2021-02-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d5ba88624a180a770eb8f022022447b5c7f91649-810x810.jpg" +intro: "Karen made this fabulous shirt based on the Bella block. She used the Bella block with most default options, only modifying to take in the back darts a bit more. She added several additional design elements to make this shirt." +title: "Bella by Karen" +--- + + +Karen made this fabulous shirt based on the Bella block. She used the Bella block with most default options, only modifying to take in the back darts a bit more. She added several additional design elements to make this shirt. + + + +This picture is from Discord and is reposted here with permission. + + + diff --git a/markdown/org/showcase/bella-by-karen/es.md b/markdown/org/showcase/bella-by-karen/es.md new file mode 100644 index 00000000000..fc4225a3797 --- /dev/null +++ b/markdown/org/showcase/bella-by-karen/es.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Karen's shirt based on the Bella block" +date: "2021-02-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d5ba88624a180a770eb8f022022447b5c7f91649-810x810.jpg" +intro: "Karen made this fabulous shirt based on the Bella block. She used the Bella block with most default options, only modifying to take in the back darts a bit more. She added several additional design elements to make this shirt." +title: "Bella by Karen [No traducido]" +--- + + +Karen made this fabulous shirt based on the Bella block. She used the Bella block with most default options, only modifying to take in the back darts a bit more. She added several additional design elements to make this shirt. + + + +This picture is from Discord and is reposted here with permission. + + + diff --git a/markdown/org/showcase/bella-by-karen/fr.md b/markdown/org/showcase/bella-by-karen/fr.md new file mode 100644 index 00000000000..216f7c76b16 --- /dev/null +++ b/markdown/org/showcase/bella-by-karen/fr.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Chemise de Karen basée sur le bloc Bella" +date: "2021-02-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d5ba88624a180a770eb8f022022447b5c7f91649-810x810.jpg" +intro: "Karen a fait cette fabuleuse chemise basée sur le bloc Bella. Elle a utilisé le bloc Bella avec la plupart des options par défaut, en modifiant seulement un peu les pinces arrière. Elle a ajouté plusieurs éléments de design supplémentaires pour fabriquer cette chemise." +title: "Bella par Karen" +--- + + +Karen a fait cette fabuleuse chemise basée sur le bloc Bella. Elle a utilisé le bloc Bella avec la plupart des options par défaut, en modifiant seulement un peu les pinces arrière. Elle a ajouté plusieurs éléments de design supplémentaires pour fabriquer cette chemise. + + + +Cette photo provient de Discord et est republiée ici avec permission. + + + diff --git a/markdown/org/showcase/bella-by-karen/nl.md b/markdown/org/showcase/bella-by-karen/nl.md new file mode 100644 index 00000000000..c39cffc7561 --- /dev/null +++ b/markdown/org/showcase/bella-by-karen/nl.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Karen's shirt based on the Bella block" +date: "2021-02-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d5ba88624a180a770eb8f022022447b5c7f91649-810x810.jpg" +intro: "Karen made this fabulous shirt based on the Bella block. She used the Bella block with most default options, only modifying to take in the back darts a bit more. She added several additional design elements to make this shirt." +title: "Bella by Karen [Niet vertaald]" +--- + + +Karen made this fabulous shirt based on the Bella block. She used the Bella block with most default options, only modifying to take in the back darts a bit more. She added several additional design elements to make this shirt. + + + +This picture is from Discord and is reposted here with permission. + + + diff --git a/markdown/org/showcase/black-bruce/de.md b/markdown/org/showcase/black-bruce/de.md new file mode 100644 index 00000000000..49a9ce93e95 --- /dev/null +++ b/markdown/org/showcase/black-bruce/de.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "Seems the husband was not willing to model these" +date: "2017-09-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/cc7d2096649640ce7638cb6ba4c81815bd8fef29-720x890.jpg" +intro: "Judy wrote:" +title: "[auf Englisch] Black boxers by Judy" +--- + + +Judy wrote: + +> Since my husband is inexplicably reluctant to let me photograph him in his undies for the internet I took them to work and asked one of the very obliging blokes we keep hanging around to model for me! +> +> These are the [#bruceboxers](https://www.instagram.com/explore/tags/bruceboxers/) from [@freesewing_org](https://www.instagram.com/freesewing_org/) made from a merino/nylon/lycra from [@wearethefabricstore](https://www.instagram.com/wearethefabricstore/) in Dunedin. +> +> David loves them - reckons these are the best undies he's ever had, so major awesome-wife points for me! (They fit him much better than the dummy) + +> ##### Check the original in judywillimentross's Instagram feed +> +> This picture is from [the Instagram feed](https://www.instagram.com/p/BZAT_btB_dq/) of [judywillimentross](https://www.instagram.com/judywillimentross/), aka [Judy336](/users/qdzpx). + diff --git a/markdown/org/showcase/black-bruce/en.md b/markdown/org/showcase/black-bruce/en.md new file mode 100644 index 00000000000..2eeb6aa605c --- /dev/null +++ b/markdown/org/showcase/black-bruce/en.md @@ -0,0 +1,29 @@ +--- +maker: "unknown" +caption: "Seems the husband was not willing to model these" +date: "2017-09-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/cc7d2096649640ce7638cb6ba4c81815bd8fef29-720x890.jpg" +intro: "Judy wrote:" +title: "Black boxers by Judy" +--- + +Judy wrote: + +> Since my husband is inexplicably reluctant to let me photograph +> him in his undies for the internet I took them to work and asked +> one of the very obliging blokes we keep hanging around to model for me! +> +> These are the [#bruceboxers](https://www.instagram.com/explore/tags/bruceboxers/) +> from [@freesewing_org](https://www.instagram.com/freesewing_org/) made from a +> merino/nylon/lycra from [@wearethefabricstore](https://www.instagram.com/wearethefabricstore/) +> in Dunedin. +> +> David loves them - reckons these are the best undies he's +> ever had, so major awesome-wife points for me! +> (They fit him much better than the dummy) + +> ##### Check the original in judywillimentross's Instagram feed +> +> This picture is from [the Instagram feed](https://www.instagram.com/p/BZAT_btB_dq/) +> of [judywillimentross](https://www.instagram.com/judywillimentross/), aka [Judy336](/users/qdzpx). + diff --git a/markdown/org/showcase/black-bruce/es.md b/markdown/org/showcase/black-bruce/es.md new file mode 100644 index 00000000000..23b84569fae --- /dev/null +++ b/markdown/org/showcase/black-bruce/es.md @@ -0,0 +1,29 @@ +--- +maker: "unknown" +caption: "Seems the husband was not willing to model these" +date: "2017-09-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/cc7d2096649640ce7638cb6ba4c81815bd8fef29-720x890.jpg" +intro: "Judy wrote:" +title: "Black boxers by Judy [No traducido]" +--- + +Judy wrote: + +> Since my husband is inexplicably reluctant to let me photograph +> him in his undies for the internet I took them to work and asked +> one of the very obliging blokes we keep hanging around to model for me! +> +> These are the [#bruceboxers](https://www.instagram.com/explore/tags/bruceboxers/) +> from [@freesewing_org](https://www.instagram.com/freesewing_org/) made from a +> merino/nylon/lycra from [@wearethefabricstore](https://www.instagram.com/wearethefabricstore/) +> in Dunedin. +> +> David loves them - reckons these are the best undies he's +> ever had, so major awesome-wife points for me! +> (They fit him much better than the dummy) + +> ##### Check the original in judywillimentross's Instagram feed +> +> This picture is from [the Instagram feed](https://www.instagram.com/p/BZAT_btB_dq/) +> of [judywillimentross](https://www.instagram.com/judywillimentross/), aka [Judy336](/users/qdzpx). + diff --git a/markdown/org/showcase/black-bruce/fr.md b/markdown/org/showcase/black-bruce/fr.md new file mode 100644 index 00000000000..8132815e1a6 --- /dev/null +++ b/markdown/org/showcase/black-bruce/fr.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "Il semble que le mari n'ait pas voulu faire le mannequin" +date: "2017-09-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/cc7d2096649640ce7638cb6ba4c81815bd8fef29-720x890.jpg" +intro: "Judy a écrit :" +title: "Boxers noirs par Judy" +--- + + +Judy a écrit : + +> Puisque mon mari est inexplicablement réticent à me laisser le photographier lui dans ses sous-vêtements pour Internet, je les ai pris pour travailler et j'ai demandé à l'un des mannequins très obligeant que nous gardons à disposition pour mes modèles ! +> +> Voici les [#bruceboxers](https://www.instagram.com/explore/tags/bruceboxers/) de [@freesewing_org](https://www.instagram.com/freesewing_org/) à partir d'un mérino/nylon/lycra de [@wearethefabricstore](https://www.instagram.com/wearethefabricstore/) dans Dunedin. +> +> David les aime - ce sont les meilleurs sous-vêtements qu'il ait jamais eu , donc ça me donne de supers bons-points en tant qu'épouse ! (Ils lui vont beaucoup mieux qu'au mannequin) + +> ##### Consultez le post original dans le profil Instagram de judywillimentross +> +> Cette photo provient du [profil Instagram](https://www.instagram.com/p/BZAT_btB_dq/) de [judywillimentross](https://www.instagram.com/judywillimentross/), aka [Judy336](/users/qdzpx). + diff --git a/markdown/org/showcase/black-bruce/nl.md b/markdown/org/showcase/black-bruce/nl.md new file mode 100644 index 00000000000..45ed4f51828 --- /dev/null +++ b/markdown/org/showcase/black-bruce/nl.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "Het lijkt erop dat de echtgenoot geen zin had model te spelen" +date: "2017-09-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/cc7d2096649640ce7638cb6ba4c81815bd8fef29-720x890.jpg" +intro: "Judy schreef:" +title: "Zwarte boxershort door Judy" +--- + + +Judy schreef: + +> Aangezien mijn echtgenoot het om één of andere reden niet ziet zitten dat ik hem in zijn ondergoed fotografeer voor het internet heb ik de onderbroek meegenomen naar mijn werk en één van de brave jongens die daar rondhangen gevraagd model te zijn! +> +> Dit zijn de [#bruceboxers](https://www.instagram.com/explore/tags/bruceboxers/) van [@freesewing_org](https://www.instagram.com/freesewing_org/) gemaakt uit een merino/nylon/lycra van [@wearethefabricstore](https://www.instagram.com/wearethefabricstore/) in Dunedin. +> +> David is er wild van - vindt het de beste onderbroek die hij ooit gehad heeft, dus extra bonuspunten voor mij! (Ze passen hem veel beter dan de pop) + +> ##### Bekijk het origineel in de Instagram feed van judywillimentross +> +> Deze afbeelding is van [de Instagram feed](https://www.instagram.com/p/BZAT_btB_dq/) van [judywillimentross](https://www.instagram.com/judywillimentross/), aka [Judy336](/users/qdzpx). + diff --git a/markdown/org/showcase/black-hugo/de.md b/markdown/org/showcase/black-hugo/de.md new file mode 100644 index 00000000000..41045d82982 --- /dev/null +++ b/markdown/org/showcase/black-hugo/de.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Love the detail of the different fabric on the inside of the hood" +date: "2016-01-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d19447441b0ccec9460b210d48292d5cd7a3b5a8-1080x1080.jpg" +intro: "This picture is from the Instagram feed of taliajane_designs ." +title: "[auf Englisch] A black hugo hoodie by Natalie" +--- + + +This picture is from [the Instagram feed](https://www.instagram.com/p/BAqm70Lqg9o/) of [taliajane_designs](https://www.instagram.com/taliajane_designs/). + diff --git a/markdown/org/showcase/black-hugo/en.md b/markdown/org/showcase/black-hugo/en.md new file mode 100644 index 00000000000..0594ba9d2e8 --- /dev/null +++ b/markdown/org/showcase/black-hugo/en.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Love the detail of the different fabric on the inside of the hood" +date: "2016-01-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d19447441b0ccec9460b210d48292d5cd7a3b5a8-1080x1080.jpg" +intro: "This picture is from the Instagram feed of taliajane_designs ." +title: "A black hugo hoodie by Natalie" +--- + + +This picture is from [the Instagram feed](https://www.instagram.com/p/BAqm70Lqg9o/) of [taliajane_designs](https://www.instagram.com/taliajane_designs/). + diff --git a/markdown/org/showcase/black-hugo/es.md b/markdown/org/showcase/black-hugo/es.md new file mode 100644 index 00000000000..bafbe748846 --- /dev/null +++ b/markdown/org/showcase/black-hugo/es.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Love the detail of the different fabric on the inside of the hood" +date: "2016-01-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d19447441b0ccec9460b210d48292d5cd7a3b5a8-1080x1080.jpg" +intro: "This picture is from the Instagram feed of taliajane_designs ." +title: "A black hugo hoodie by Natalie [No traducido]" +--- + + +This picture is from [the Instagram feed](https://www.instagram.com/p/BAqm70Lqg9o/) of [taliajane_designs](https://www.instagram.com/taliajane_designs/). + diff --git a/markdown/org/showcase/black-hugo/fr.md b/markdown/org/showcase/black-hugo/fr.md new file mode 100644 index 00000000000..d9e686360de --- /dev/null +++ b/markdown/org/showcase/black-hugo/fr.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Appréciez le détail du tissu contrastant à l'intérieur de la capuche" +date: "2016-01-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d19447441b0ccec9460b210d48292d5cd7a3b5a8-1080x1080.jpg" +intro: "Cette photo provient du compte Instagram de taliajane_designs ." +title: "Un sweat à capuche Hugo noir par Natalie" +--- + + +Cette photo provient du [compte Instagram](https://www.instagram.com/p/BAqm70Lqg9o/) de [taliajane_designs](https://www.instagram.com/taliajane_designs/). + diff --git a/markdown/org/showcase/black-hugo/nl.md b/markdown/org/showcase/black-hugo/nl.md new file mode 100644 index 00000000000..ed4e54fc178 --- /dev/null +++ b/markdown/org/showcase/black-hugo/nl.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "De verschillende stof aan de binnenkant van de kap is een geweldig detail" +date: "2016-01-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d19447441b0ccec9460b210d48292d5cd7a3b5a8-1080x1080.jpg" +intro: "Deze afbeelding is van de Instagram feed van taliajane_designs ." +title: "Een zwarte Hugo hoodie door Natalie" +--- + + +Deze afbeelding is van [de Instagram feed](https://www.instagram.com/p/BAqm70Lqg9o/) van [taliajane_designs](https://www.instagram.com/taliajane_designs/). + diff --git a/markdown/org/showcase/bleach-dyed-bruce/de.md b/markdown/org/showcase/bleach-dyed-bruce/de.md new file mode 100644 index 00000000000..bb8cfeaa3a9 --- /dev/null +++ b/markdown/org/showcase/bleach-dyed-bruce/de.md @@ -0,0 +1,24 @@ +--- +maker: "unknown" +caption: "These are made of black tshirt fabric she bleach dyed myself, using desert plants for the design." +date: "2018-01-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9e8834593713a2a6e4903d53e789b430449f947a-1280x960.jpg" +intro: "[auf Englisch] Bleach dyed Bruce by Reanna" +title: "[auf Englisch] Bleach dyed Bruce by Reanna" +--- + +![The back of the pair shown above](https://posts.freesewing.org/uploads/bleach_dyed_bruce_1_back_c91de98a99.jpg "The back of the pair shown above") + +![The front of a second pair](https://posts.freesewing.org/uploads/bleach_dyed_bruce_2_front_d9e26ac24b.jpg "The front of a second pair") + +![The back of a second pair](https://posts.freesewing.org/uploads/bleach_dyed_bruce_2_back_f97d0b323f.jpg "The back of a second pair") + + + +###### See the original on Tumblr +These were taken from [this Tumblr post](http://alderrr.tumblr.com/post/168948306776/christmas-crafting-2-pairs-of-mens-underwear) +on [the blog](http://alderrr.tumblr.com/) of [@Alderrr](/users/Alderrr). + +They are reposted here with permission. + + diff --git a/markdown/org/showcase/bleach-dyed-bruce/en.md b/markdown/org/showcase/bleach-dyed-bruce/en.md new file mode 100644 index 00000000000..1afa2c7b228 --- /dev/null +++ b/markdown/org/showcase/bleach-dyed-bruce/en.md @@ -0,0 +1,25 @@ +--- +maker: "unknown" +caption: "These are made of black tshirt fabric she bleach dyed myself, using desert plants for the design." +date: "2018-01-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9e8834593713a2a6e4903d53e789b430449f947a-1280x960.jpg" +intro: "Bleach dyed Bruce by Reanna" +title: "Bleach dyed Bruce by Reanna" +--- + +![The back of the pair shown above](https://posts.freesewing.org/uploads/bleach_dyed_bruce_1_back_c91de98a99.jpg "The back of the pair shown above") + +![The front of a second pair](https://posts.freesewing.org/uploads/bleach_dyed_bruce_2_front_d9e26ac24b.jpg "The front of a second pair") + +![The back of a second pair](https://posts.freesewing.org/uploads/bleach_dyed_bruce_2_back_f97d0b323f.jpg "The back of a second pair") + + + + +###### See the original on Tumblr +These were taken from [this Tumblr post](http://alderrr.tumblr.com/post/168948306776/christmas-crafting-2-pairs-of-mens-underwear) +on [the blog](http://alderrr.tumblr.com/) of [@Alderrr](/users/Alderrr). + +They are reposted here with permission. + + diff --git a/markdown/org/showcase/bleach-dyed-bruce/es.md b/markdown/org/showcase/bleach-dyed-bruce/es.md new file mode 100644 index 00000000000..a346fe2b318 --- /dev/null +++ b/markdown/org/showcase/bleach-dyed-bruce/es.md @@ -0,0 +1,25 @@ +--- +maker: "unknown" +caption: "These are made of black tshirt fabric she bleach dyed myself, using desert plants for the design." +date: "2018-01-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9e8834593713a2a6e4903d53e789b430449f947a-1280x960.jpg" +intro: "Bleach dyed Bruce by Reanna [No traducido]" +title: "Bleach dyed Bruce by Reanna [No traducido]" +--- + +![The back of the pair shown above](https://posts.freesewing.org/uploads/bleach_dyed_bruce_1_back_c91de98a99.jpg "The back of the pair shown above") + +![The front of a second pair](https://posts.freesewing.org/uploads/bleach_dyed_bruce_2_front_d9e26ac24b.jpg "The front of a second pair") + +![The back of a second pair](https://posts.freesewing.org/uploads/bleach_dyed_bruce_2_back_f97d0b323f.jpg "The back of a second pair") + + + + +###### See the original on Tumblr +These were taken from [this Tumblr post](http://alderrr.tumblr.com/post/168948306776/christmas-crafting-2-pairs-of-mens-underwear) +on [the blog](http://alderrr.tumblr.com/) of [@Alderrr](/users/Alderrr). + +They are reposted here with permission. + + diff --git a/markdown/org/showcase/bleach-dyed-bruce/fr.md b/markdown/org/showcase/bleach-dyed-bruce/fr.md new file mode 100644 index 00000000000..c4211345500 --- /dev/null +++ b/markdown/org/showcase/bleach-dyed-bruce/fr.md @@ -0,0 +1,24 @@ +--- +maker: "unknown" +caption: "Ils sont faits à partir du tissu de tee-shirt noir qu'elle a blanchi elle-même, en utilisant des plantes désertiques pour le design." +date: "2018-01-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9e8834593713a2a6e4903d53e789b430449f947a-1280x960.jpg" +intro: "Bruce blanchi à la javel par Reanna" +title: "Bruce blanchi à la javel par Reanna" +--- + +![L'arrière du modèle montré ci-dessus](https://posts.freesewing.org/uploads/bleach_dyed_bruce_1_back_c91de98a99.jpg "L'arrière du modèle montré ci-dessus") + +![La face avant d'un second boxer](https://posts.freesewing.org/uploads/bleach_dyed_bruce_2_front_d9e26ac24b.jpg "La face avant d'un second boxer") + +![Le dos du second boxer](https://posts.freesewing.org/uploads/bleach_dyed_bruce_2_back_f97d0b323f.jpg "Le dos du second boxer") + + + +###### Voir l'original sur Tumblr +Ils ont été extraits de [ce post Tumblr](http://alderrr.tumblr.com/post/168948306776/christmas-crafting-2-pairs-of-mens-underwear) +on [the blog](http://alderrr.tumblr.com/) de [@Alderrr](/users/Alderrr). + +Ils sont repostés ici avec autorisation. + + diff --git a/markdown/org/showcase/bleach-dyed-bruce/nl.md b/markdown/org/showcase/bleach-dyed-bruce/nl.md new file mode 100644 index 00000000000..19b2a145ad4 --- /dev/null +++ b/markdown/org/showcase/bleach-dyed-bruce/nl.md @@ -0,0 +1,24 @@ +--- +maker: "unknown" +caption: "Dit is gemaakt uit zwarte t-shirtstof die geverfd werd met bleekwater. Voor het ontwerp werden woestijnplanten gebruikt." +date: "2018-01-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9e8834593713a2a6e4903d53e789b430449f947a-1280x960.jpg" +intro: "Gebleekte Bruce door Reanna" +title: "Gebleekte Bruce door Reanna" +--- + +![De achterkant van de boxershort hierboven](https://posts.freesewing.org/uploads/bleach_dyed_bruce_1_back_c91de98a99.jpg "De achterkant van de boxershort hierboven") + +![De voorkant van een tweede](https://posts.freesewing.org/uploads/bleach_dyed_bruce_2_front_d9e26ac24b.jpg "De voorkant van een tweede") + +![De achterkant van een tweede](https://posts.freesewing.org/uploads/bleach_dyed_bruce_2_back_f97d0b323f.jpg "De achterkant van een tweede") + + + +###### See the original on Tumblr +These were taken from [this Tumblr post](http://alderrr.tumblr.com/post/168948306776/christmas-crafting-2-pairs-of-mens-underwear) +on [the blog](http://alderrr.tumblr.com/) of [@Alderrr](/users/Alderrr). + +Ze werden hier gepost met toestemming. + + diff --git a/markdown/org/showcase/blue-simon/de.md b/markdown/org/showcase/blue-simon/de.md new file mode 100644 index 00000000000..18299b05af0 --- /dev/null +++ b/markdown/org/showcase/blue-simon/de.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "That's some quality posing right there." +date: "2017-10-09" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/bdb5e72db9290457048b763783bf8a2de51ce0c1-1080x1080.jpg" +intro: "[auf Englisch] A blue Simon shirt by feelingmyoats" +title: "[auf Englisch] A blue Simon shirt by feelingmyoats" +--- + +![View of the front](https://posts.freesewing.org/uploads/blue_simon_front_1a4a8e9897.jpg "View of the front") + +![View of the back](https://posts.freesewing.org/uploads/blue_simon_back_a038252972.jpg "View of the back") + + + +###### See the original on Instagram +This post [originally appeared](https://www.instagram.com/p/BZ6X2CkjZor/) +on [the Instagram feed of feelinmyoats](https://www.instagram.com/feelinmyoats/). + +It is reposted here with permission. + + diff --git a/markdown/org/showcase/blue-simon/en.md b/markdown/org/showcase/blue-simon/en.md new file mode 100644 index 00000000000..9c40b7e8dd8 --- /dev/null +++ b/markdown/org/showcase/blue-simon/en.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "That's some quality posing right there." +date: "2017-10-09" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/bdb5e72db9290457048b763783bf8a2de51ce0c1-1080x1080.jpg" +intro: "A blue Simon shirt by feelingmyoats" +title: "A blue Simon shirt by feelingmyoats" +--- + +![View of the front](https://posts.freesewing.org/uploads/blue_simon_front_1a4a8e9897.jpg "View of the front") + +![View of the back](https://posts.freesewing.org/uploads/blue_simon_back_a038252972.jpg) + + + +###### See the original on Instagram +This post [originally appeared](https://www.instagram.com/p/BZ6X2CkjZor/) +on [the Instagram feed of feelinmyoats](https://www.instagram.com/feelinmyoats/). + +It is reposted here with permission. + + diff --git a/markdown/org/showcase/blue-simon/es.md b/markdown/org/showcase/blue-simon/es.md new file mode 100644 index 00000000000..3debe8f319a --- /dev/null +++ b/markdown/org/showcase/blue-simon/es.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "That's some quality posing right there." +date: "2017-10-09" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/bdb5e72db9290457048b763783bf8a2de51ce0c1-1080x1080.jpg" +intro: "A blue Simon shirt by feelingmyoats [No traducido]" +title: "A blue Simon shirt by feelingmyoats [No traducido]" +--- + +![View of the front](https://posts.freesewing.org/uploads/blue_simon_front_1a4a8e9897.jpg "View of the front") + +![View of the back](https://posts.freesewing.org/uploads/blue_simon_back_a038252972.jpg) + + + +###### See the original on Instagram +This post [originally appeared](https://www.instagram.com/p/BZ6X2CkjZor/) +on [the Instagram feed of feelinmyoats](https://www.instagram.com/feelinmyoats/). + +It is reposted here with permission. + + diff --git a/markdown/org/showcase/blue-simon/fr.md b/markdown/org/showcase/blue-simon/fr.md new file mode 100644 index 00000000000..696a6438354 --- /dev/null +++ b/markdown/org/showcase/blue-simon/fr.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "C'est de qualité en posant juste là." +date: "2017-10-09" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/bdb5e72db9290457048b763783bf8a2de51ce0c1-1080x1080.jpg" +intro: "Une chemise bleue Simon par feelingmyoats" +title: "Une chemise bleue Simon par feelingmyoats" +--- + +![Photo de l'avant](https://posts.freesewing.org/uploads/blue_simon_front_1a4a8e9897.jpg "Photo de l'avant") + +![Vue du dos](back.jpg) + + + +###### Voir l'original sur Instagram +Ce post [est apparu à l'origine](https://www.instagram.com/p/BZ6X2CkjZor/) +sur [le feed Instagram de feelinmyoats](https://www.instagram.com/feelinmyoats/). + +Elle est publiée ici avec son autorisation. + + diff --git a/markdown/org/showcase/blue-simon/nl.md b/markdown/org/showcase/blue-simon/nl.md new file mode 100644 index 00000000000..7a08be69ee0 --- /dev/null +++ b/markdown/org/showcase/blue-simon/nl.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "Wat een pose!" +date: "2017-10-09" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/bdb5e72db9290457048b763783bf8a2de51ce0c1-1080x1080.jpg" +intro: "Een blauw Simon hemd door feelingmyoats" +title: "Een blauw Simon hemd door feelingmyoats" +--- + +![Zicht op de voorkant](https://posts.freesewing.org/uploads/blue_simon_front_1a4a8e9897.jpg "Zicht op de voorkant") + +![Zicht op de achterkant](back.jpg) + + + +###### See the original on Instagram +This post [originally appeared](https://www.instagram.com/p/BZ6X2CkjZor/) +on [the Instagram feed of feelinmyoats](https://www.instagram.com/feelinmyoats/). + +Hij werd hier gepost met toestemming. + + diff --git a/markdown/org/showcase/blue-theo/de.md b/markdown/org/showcase/blue-theo/de.md new file mode 100644 index 00000000000..7bd2e4bcbc5 --- /dev/null +++ b/markdown/org/showcase/blue-theo/de.md @@ -0,0 +1,11 @@ +--- +maker: "Joost De Cock" +caption: "Gosh we were so young back then" +date: "2015-04-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3b2975abda700d4c4388ac975e67a1c1ca7f7b81-960x1280.jpg" +intro: "FIXME_no_intro" +title: "[auf Englisch] Blue cotton Theo trousers by joost" +--- + + + diff --git a/markdown/org/showcase/blue-theo/en.md b/markdown/org/showcase/blue-theo/en.md new file mode 100644 index 00000000000..566ff054739 --- /dev/null +++ b/markdown/org/showcase/blue-theo/en.md @@ -0,0 +1,10 @@ +--- +maker: "Joost De Cock" +caption: "Gosh we were so young back then" +date: "2015-04-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3b2975abda700d4c4388ac975e67a1c1ca7f7b81-960x1280.jpg" +intro: "That's it. That't the whole post" +title: "Blue cotton Theo trousers by joost" +--- + +That's it. That't the whole post diff --git a/markdown/org/showcase/blue-theo/es.md b/markdown/org/showcase/blue-theo/es.md new file mode 100644 index 00000000000..befd97ae092 --- /dev/null +++ b/markdown/org/showcase/blue-theo/es.md @@ -0,0 +1,10 @@ +--- +maker: "Joost De Cock" +caption: "Gosh we were so young back then" +date: "2015-04-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3b2975abda700d4c4388ac975e67a1c1ca7f7b81-960x1280.jpg" +intro: "That's it. That't the whole post" +title: "Blue cotton Theo trousers by joost [No traducido]" +--- + +That's it. That't the whole post diff --git a/markdown/org/showcase/blue-theo/fr.md b/markdown/org/showcase/blue-theo/fr.md new file mode 100644 index 00000000000..3d23dfebf14 --- /dev/null +++ b/markdown/org/showcase/blue-theo/fr.md @@ -0,0 +1,11 @@ +--- +maker: "Joost De Cock" +caption: "Mon dieu nous étions si jeunes à l'époque" +date: "2015-04-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3b2975abda700d4c4388ac975e67a1c1ca7f7b81-960x1280.jpg" +intro: "FIXME_no_intro" +title: "Pantalon en coton bleu Theo par joostdecock" +--- + + + diff --git a/markdown/org/showcase/blue-theo/nl.md b/markdown/org/showcase/blue-theo/nl.md new file mode 100644 index 00000000000..48b58d46dc0 --- /dev/null +++ b/markdown/org/showcase/blue-theo/nl.md @@ -0,0 +1,11 @@ +--- +maker: "Joost De Cock" +caption: "Wat waren we toen jong" +date: "2015-04-13" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3b2975abda700d4c4388ac975e67a1c1ca7f7b81-960x1280.jpg" +intro: "FIXME_no_intro" +title: "Blauw katoenen Theo broek door joost" +--- + + + diff --git a/markdown/org/showcase/bound-wahid/de.md b/markdown/org/showcase/bound-wahid/de.md new file mode 100644 index 00000000000..ed1ba515c5e --- /dev/null +++ b/markdown/org/showcase/bound-wahid/de.md @@ -0,0 +1,21 @@ +--- +maker: "unknown" +caption: "Believe it or not, this is only his third sewing project ever." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3d05ee5656f7aac511d95ed567dab54c6545cd88-1080x1080.jpg" +intro: "[auf Englisch] A Wahid Waistcoat with bound buttonholes" +title: "[auf Englisch] A Wahid Waistcoat with bound buttonholes" +--- + +![Side view](https://posts.freesewing.org/uploads/bound_wahid_2_8cecc34558.jpg "Side view") + +![Front view](https://posts.freesewing.org/uploads/bound_wahid_3_f8978b57b8.jpg "Front view") + +![Flat lay](https://posts.freesewing.org/uploads/bound_wahid_4_7ee387162d.jpg "Flat lay") + +> ##### See the originals on the Instragram feed of funloveadventure +> +> These images are from [the Instagram feed](https://www.instagram.com/funloveadventure/) of FIXME. They are published here with permission. + +> FIXME: What user is this? + diff --git a/markdown/org/showcase/bound-wahid/en.md b/markdown/org/showcase/bound-wahid/en.md new file mode 100644 index 00000000000..9480612593e --- /dev/null +++ b/markdown/org/showcase/bound-wahid/en.md @@ -0,0 +1,23 @@ +--- +maker: "unknown" +caption: "Believe it or not, this is only his third sewing project ever." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3d05ee5656f7aac511d95ed567dab54c6545cd88-1080x1080.jpg" +intro: "A Wahid Waistcoat with bound buttonholes" +title: "A Wahid Waistcoat with bound buttonholes" +--- + +![Side view](https://posts.freesewing.org/uploads/bound_wahid_2_8cecc34558.jpg "Side view") + +![Front view](https://posts.freesewing.org/uploads/bound_wahid_3_f8978b57b8.jpg "Front view") + +![Flat lay](https://posts.freesewing.org/uploads/bound_wahid_4_7ee387162d.jpg "Flat lay") + +> ##### See the originals on the Instragram feed of funloveadventure +> +> These images are from +> [the Instagram feed](https://www.instagram.com/funloveadventure/) of FIXME. +> They are published here with permission. + +> FIXME: What user is this? + diff --git a/markdown/org/showcase/bound-wahid/es.md b/markdown/org/showcase/bound-wahid/es.md new file mode 100644 index 00000000000..b9694316e93 --- /dev/null +++ b/markdown/org/showcase/bound-wahid/es.md @@ -0,0 +1,23 @@ +--- +maker: "unknown" +caption: "Believe it or not, this is only his third sewing project ever." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3d05ee5656f7aac511d95ed567dab54c6545cd88-1080x1080.jpg" +intro: "A Wahid Waistcoat with bound buttonholes [No traducido]" +title: "A Wahid Waistcoat with bound buttonholes [No traducido]" +--- + +![Side view](https://posts.freesewing.org/uploads/bound_wahid_2_8cecc34558.jpg "Side view") + +![Front view](https://posts.freesewing.org/uploads/bound_wahid_3_f8978b57b8.jpg "Front view") + +![Flat lay](https://posts.freesewing.org/uploads/bound_wahid_4_7ee387162d.jpg "Flat lay") + +> ##### See the originals on the Instragram feed of funloveadventure +> +> These images are from +> [the Instagram feed](https://www.instagram.com/funloveadventure/) of FIXME. +> They are published here with permission. + +> FIXME: What user is this? + diff --git a/markdown/org/showcase/bound-wahid/fr.md b/markdown/org/showcase/bound-wahid/fr.md new file mode 100644 index 00000000000..c5b9616b481 --- /dev/null +++ b/markdown/org/showcase/bound-wahid/fr.md @@ -0,0 +1,21 @@ +--- +maker: "unknown" +caption: "Croyez-le ou non, il ne s'agit là que de son troisième projet de couture." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3d05ee5656f7aac511d95ed567dab54c6545cd88-1080x1080.jpg" +intro: "Un gilet Wahid avec des boutonnières renforcées" +title: "Un gilet Wahid avec des boutonnières renforcées" +--- + +![Side view](https://posts.freesewing.org/uploads/bound_wahid_2_8cecc34558.jpg "Side view") + +![Front view](https://posts.freesewing.org/uploads/bound_wahid_3_f8978b57b8.jpg "Front view") + +![Flat lay](https://posts.freesewing.org/uploads/bound_wahid_4_7ee387162d.jpg "Flat lay") + +> ##### Voir les originaux sur le feed Instragram de funloveadventure +> +> Ces photos proviennent du [feed Instagram](https://www.instagram.com/funloveadventure/) de funloveadventure. Elles sont repostées ici avec autorisation. + +> [lien direct du post](https://www.instagram.com/p/BekzdhvhbQO/) + diff --git a/markdown/org/showcase/bound-wahid/nl.md b/markdown/org/showcase/bound-wahid/nl.md new file mode 100644 index 00000000000..be596af1428 --- /dev/null +++ b/markdown/org/showcase/bound-wahid/nl.md @@ -0,0 +1,21 @@ +--- +maker: "unknown" +caption: "Geloof het of niet, maar dit is pas zijn derde naaiproject ooit." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3d05ee5656f7aac511d95ed567dab54c6545cd88-1080x1080.jpg" +intro: "Een Wahid gilet met paspel knoopsgaten" +title: "Een Wahid gilet met paspel knoopsgaten" +--- + +![Zicht op de zijkant](https://posts.freesewing.org/uploads/bound_wahid_2_8cecc34558.jpg "Zicht op de zijkant") + +![Zicht op de voorkant](https://posts.freesewing.org/uploads/bound_wahid_3_f8978b57b8.jpg "Zicht op de voorkant") + +![Flat lay](https://posts.freesewing.org/uploads/bound_wahid_4_7ee387162d.jpg "Flat lay") + +> ##### Zie het origineel in de Instagram feed van funloveadventure +> +> These images are from [the Instagram feed](https://www.instagram.com/funloveadventure/) of FIXME. They are published here with permission. + +> FIXME: What user is this? + diff --git a/markdown/org/showcase/brian-by-stefan-1/de.md b/markdown/org/showcase/brian-by-stefan-1/de.md new file mode 100644 index 00000000000..6ddfae361ef --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-1/de.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Stefan showing off his new T-shirt, which is based on the Brian Body Block." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0c745934ec9e842f4c842dbb43c2cbc17e0968f1-1937x1936.jpg" +intro: "This picture originally appeared in the twitter feed of @SThanheiser ." +title: "[auf Englisch] Stefan makes a T-shirt based on Brian 1/4" +--- + + +This picture [originally appeared](https://twitter.com/SThanheiser/status/933942463332536320) in the twitter feed of [@SThanheiser](https://twitter.com/SThanheiser). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/brian-by-stefan-1/en.md b/markdown/org/showcase/brian-by-stefan-1/en.md new file mode 100644 index 00000000000..b4f50eb89b0 --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-1/en.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Stefan showing off his new T-shirt, which is based on the Brian Body Block." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0c745934ec9e842f4c842dbb43c2cbc17e0968f1-1937x1936.jpg" +intro: "This picture originally appeared in the twitter feed of @SThanheiser ." +title: "Stefan makes a T-shirt based on Brian 1/4" +--- + + +This picture [originally appeared](https://twitter.com/SThanheiser/status/933942463332536320) +in the twitter feed of [@SThanheiser](https://twitter.com/SThanheiser). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/brian-by-stefan-1/es.md b/markdown/org/showcase/brian-by-stefan-1/es.md new file mode 100644 index 00000000000..1dd4f38af99 --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-1/es.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Stefan showing off his new T-shirt, which is based on the Brian Body Block." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0c745934ec9e842f4c842dbb43c2cbc17e0968f1-1937x1936.jpg" +intro: "This picture originally appeared in the twitter feed of @SThanheiser ." +title: "Stefan makes a T-shirt based on Brian 1/4 [No traducido]" +--- + + +This picture [originally appeared](https://twitter.com/SThanheiser/status/933942463332536320) +in the twitter feed of [@SThanheiser](https://twitter.com/SThanheiser). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/brian-by-stefan-1/fr.md b/markdown/org/showcase/brian-by-stefan-1/fr.md new file mode 100644 index 00000000000..1c9bb306771 --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-1/fr.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Stefan montre son nouveau T-shirt, qui est basé sur le buste de base Brian." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0c745934ec9e842f4c842dbb43c2cbc17e0968f1-1937x1936.jpg" +intro: "Cette photo provient du feed twitter de @SThanheiser ." +title: "Stefan a fait un T-shirt basé sur Brian" +--- + + +Cette [photo](https://twitter.com/SThanheiser/status/933942463332536320) provient du feed twitter de [@SThanheiser](https://twitter.com/SThanheiser). + +Elle est publiée ici avec son autorisation. + diff --git a/markdown/org/showcase/brian-by-stefan-1/nl.md b/markdown/org/showcase/brian-by-stefan-1/nl.md new file mode 100644 index 00000000000..df67f17fb8f --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-1/nl.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Stefan stoeft met zijn nieuwe t-shirt, gebaseerd op de Brian basisvorm." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0c745934ec9e842f4c842dbb43c2cbc17e0968f1-1937x1936.jpg" +intro: "Deze foto verscheen oorspronkelijk in de Twitter feed van @SThanheiser ." +title: "Stefan maakt een t-shirt gebaseerd op Brian 1/4 " +--- + + +Deze foto [verscheen oorspronkelijk](https://twitter.com/SThanheiser/status/933942463332536320) in de Twitter feed van [@SThanheiser](https://twitter.com/SThanheiser). + +Hij werd hier gepost met toestemming. + diff --git a/markdown/org/showcase/brian-by-stefan-2/de.md b/markdown/org/showcase/brian-by-stefan-2/de.md new file mode 100644 index 00000000000..d039967f982 --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-2/de.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Stefan showing off his new T-shirt, which is based on the Brian Body Block." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/2c7cf37e1f57ef685ee9e767ab84ceeed677f3c5-1971x1970.jpg" +intro: "This picture originally appeared in the twitter feed of @SThanheiser ." +title: "Stefan makes a T-shirt based on Brian 2/4 [Nicht übersetzt]" +--- + + +This picture [originally appeared](https://twitter.com/SThanheiser/status/933942463332536320) +in the twitter feed of [@SThanheiser](https://twitter.com/SThanheiser). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/brian-by-stefan-2/en.md b/markdown/org/showcase/brian-by-stefan-2/en.md new file mode 100644 index 00000000000..8c439d1e37b --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-2/en.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Stefan showing off his new T-shirt, which is based on the Brian Body Block." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/2c7cf37e1f57ef685ee9e767ab84ceeed677f3c5-1971x1970.jpg" +intro: "This picture originally appeared in the twitter feed of @SThanheiser ." +title: "Stefan makes a T-shirt based on Brian 2/4" +--- + + +This picture [originally appeared](https://twitter.com/SThanheiser/status/933942463332536320) +in the twitter feed of [@SThanheiser](https://twitter.com/SThanheiser). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/brian-by-stefan-2/es.md b/markdown/org/showcase/brian-by-stefan-2/es.md new file mode 100644 index 00000000000..9f579de8b17 --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-2/es.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Stefan showing off his new T-shirt, which is based on the Brian Body Block." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/2c7cf37e1f57ef685ee9e767ab84ceeed677f3c5-1971x1970.jpg" +intro: "This picture originally appeared in the twitter feed of @SThanheiser ." +title: "Stefan makes a T-shirt based on Brian 2/4 [No traducido]" +--- + + +This picture [originally appeared](https://twitter.com/SThanheiser/status/933942463332536320) +in the twitter feed of [@SThanheiser](https://twitter.com/SThanheiser). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/brian-by-stefan-2/fr.md b/markdown/org/showcase/brian-by-stefan-2/fr.md new file mode 100644 index 00000000000..a342aa7ff69 --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-2/fr.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Stefan montre son nouveau T-shirt, qui est basé sur le buste de base Brian." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/2c7cf37e1f57ef685ee9e767ab84ceeed677f3c5-1971x1970.jpg" +intro: "Cette photo provient du feed twitter de @SThanheiser ." +title: "Stefan a fait un T-shirt basé sur BrianB6etJ" +--- + + +Cette [photo](https://twitter.com/SThanheiser/status/933942463332536320) provient du feed twitter de [@SThanheiser](https://twitter.com/SThanheiser). + +Elle est publiée ici avec son autorisation. + diff --git a/markdown/org/showcase/brian-by-stefan-2/nl.md b/markdown/org/showcase/brian-by-stefan-2/nl.md new file mode 100644 index 00000000000..875522a3137 --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-2/nl.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Stefan stoeft met zijn nieuwe t-shirt, gebaseerd op de Brian basisvorm." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/2c7cf37e1f57ef685ee9e767ab84ceeed677f3c5-1971x1970.jpg" +intro: "Deze foto verscheen oorspronkelijk in de Twitter feed van @SThanheiser ." +title: "Stefan maakt een t-shirt gebaseerd op Brian 2/4" +--- + + +Deze foto [verscheen oorspronkelijk](https://twitter.com/SThanheiser/status/933942463332536320) in de Twitter feed van [@SThanheiser](https://twitter.com/SThanheiser). + +Hij werd hier gepost met toestemming. + diff --git a/markdown/org/showcase/brian-by-stefan-3/de.md b/markdown/org/showcase/brian-by-stefan-3/de.md new file mode 100644 index 00000000000..f6e40906673 --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-3/de.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Stefan showing off his new T-shirt, which is based on the Brian Body Block." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c640419601bc0933c4a8c1c4106ef8c6abd70c81-2008x2007.jpg" +intro: "This picture originally appeared in the twitter feed of @SThanheiser ." +title: "Stefan makes a T-shirt based on Brian 3/4 [Nicht übersetzt]" +--- + + +This picture [originally appeared](https://twitter.com/SThanheiser/status/933942463332536320) +in the twitter feed of [@SThanheiser](https://twitter.com/SThanheiser). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/brian-by-stefan-3/en.md b/markdown/org/showcase/brian-by-stefan-3/en.md new file mode 100644 index 00000000000..c63eb9eeb80 --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-3/en.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Stefan showing off his new T-shirt, which is based on the Brian Body Block." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c640419601bc0933c4a8c1c4106ef8c6abd70c81-2008x2007.jpg" +intro: "This picture originally appeared in the twitter feed of @SThanheiser ." +title: "Stefan makes a T-shirt based on Brian 3/4" +--- + + +This picture [originally appeared](https://twitter.com/SThanheiser/status/933942463332536320) +in the twitter feed of [@SThanheiser](https://twitter.com/SThanheiser). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/brian-by-stefan-3/es.md b/markdown/org/showcase/brian-by-stefan-3/es.md new file mode 100644 index 00000000000..783cc859f58 --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-3/es.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Stefan showing off his new T-shirt, which is based on the Brian Body Block." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c640419601bc0933c4a8c1c4106ef8c6abd70c81-2008x2007.jpg" +intro: "This picture originally appeared in the twitter feed of @SThanheiser ." +title: "Stefan makes a T-shirt based on Brian 3/4 [No traducido]" +--- + + +This picture [originally appeared](https://twitter.com/SThanheiser/status/933942463332536320) +in the twitter feed of [@SThanheiser](https://twitter.com/SThanheiser). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/brian-by-stefan-3/fr.md b/markdown/org/showcase/brian-by-stefan-3/fr.md new file mode 100644 index 00000000000..5efb7c750ab --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-3/fr.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Stefan montre son nouveau T-shirt, qui est basé sur le buste de base Brian." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c640419601bc0933c4a8c1c4106ef8c6abd70c81-2008x2007.jpg" +intro: "Cette photo provient du feed twitter de @SThanheiser ." +title: "Stefan a fait un T-shirt basé sur Brian8KIzK" +--- + + +Cette [photo](https://twitter.com/SThanheiser/status/933942463332536320) provient du feed twitter de [@SThanheiser](https://twitter.com/SThanheiser). + +Elle est publiée ici avec son autorisation. + diff --git a/markdown/org/showcase/brian-by-stefan-3/nl.md b/markdown/org/showcase/brian-by-stefan-3/nl.md new file mode 100644 index 00000000000..802122dffdd --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-3/nl.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Stefan stoeft met zijn nieuwe t-shirt, gebaseerd op de Brian basisvorm." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c640419601bc0933c4a8c1c4106ef8c6abd70c81-2008x2007.jpg" +intro: "Deze foto verscheen oorspronkelijk in de Twitter feed van @SThanheiser ." +title: "Stefan maakt een t-shirt gebaseerd op Brian" +--- + + +Deze foto [verscheen oorspronkelijk](https://twitter.com/SThanheiser/status/933942463332536320) in de Twitter feed van [@SThanheiser](https://twitter.com/SThanheiser). + +Hij werd hier gepost met toestemming. + diff --git a/markdown/org/showcase/brian-by-stefan-4/de.md b/markdown/org/showcase/brian-by-stefan-4/de.md new file mode 100644 index 00000000000..5172bdb3fa9 --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-4/de.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Stefan showing off his new T-shirt, which is based on the Brian Body Block." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/72a8175d98f267194c48ad940c734853a62e4e66-2045x2044.jpg" +intro: "This picture originally appeared in the twitter feed of @SThanheiser ." +title: "Stefan makes a T-shirt based on Brian 4/4 [Nicht übersetzt]" +--- + + +This picture [originally appeared](https://twitter.com/SThanheiser/status/933942463332536320) +in the twitter feed of [@SThanheiser](https://twitter.com/SThanheiser). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/brian-by-stefan-4/en.md b/markdown/org/showcase/brian-by-stefan-4/en.md new file mode 100644 index 00000000000..3c6a5f10c11 --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-4/en.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Stefan showing off his new T-shirt, which is based on the Brian Body Block." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/72a8175d98f267194c48ad940c734853a62e4e66-2045x2044.jpg" +intro: "This picture originally appeared in the twitter feed of @SThanheiser ." +title: "Stefan makes a T-shirt based on Brian 4/4" +--- + + +This picture [originally appeared](https://twitter.com/SThanheiser/status/933942463332536320) +in the twitter feed of [@SThanheiser](https://twitter.com/SThanheiser). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/brian-by-stefan-4/es.md b/markdown/org/showcase/brian-by-stefan-4/es.md new file mode 100644 index 00000000000..ef1c07914db --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-4/es.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Stefan showing off his new T-shirt, which is based on the Brian Body Block." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/72a8175d98f267194c48ad940c734853a62e4e66-2045x2044.jpg" +intro: "This picture originally appeared in the twitter feed of @SThanheiser ." +title: "Stefan makes a T-shirt based on Brian 4/4 [No traducido]" +--- + + +This picture [originally appeared](https://twitter.com/SThanheiser/status/933942463332536320) +in the twitter feed of [@SThanheiser](https://twitter.com/SThanheiser). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/brian-by-stefan-4/fr.md b/markdown/org/showcase/brian-by-stefan-4/fr.md new file mode 100644 index 00000000000..15b5dacdbef --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-4/fr.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Stefan montre son nouveau T-shirt, qui est basé sur le buste de base Brian." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/72a8175d98f267194c48ad940c734853a62e4e66-2045x2044.jpg" +intro: "Cette photo provient du feed twitter de @SThanheiser ." +title: "Stefan a fait un T-shirt basé sur BrianEc36t" +--- + + +Cette [photo](https://twitter.com/SThanheiser/status/933942463332536320) provient du feed twitter de [@SThanheiser](https://twitter.com/SThanheiser). + +Elle est publiée ici avec son autorisation. + diff --git a/markdown/org/showcase/brian-by-stefan-4/nl.md b/markdown/org/showcase/brian-by-stefan-4/nl.md new file mode 100644 index 00000000000..660dec307df --- /dev/null +++ b/markdown/org/showcase/brian-by-stefan-4/nl.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Stefan stoeft met zijn nieuwe t-shirt, gebaseerd op de Brian basisvorm." +date: "2017-11-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/72a8175d98f267194c48ad940c734853a62e4e66-2045x2044.jpg" +intro: "Deze foto verscheen oorspronkelijk in de Twitter feed van @SThanheiser ." +title: "Stefan maakt een t-shirt gebaseerd op Briann2WQL" +--- + + +Deze foto [verscheen oorspronkelijk](https://twitter.com/SThanheiser/status/933942463332536320) in de Twitter feed van [@SThanheiser](https://twitter.com/SThanheiser). + +Hij werd hier gepost met toestemming. + diff --git a/markdown/org/showcase/bruce-on-doll/de.md b/markdown/org/showcase/bruce-on-doll/de.md new file mode 100644 index 00000000000..9186cce471f --- /dev/null +++ b/markdown/org/showcase/bruce-on-doll/de.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "The doll is named Jon, and its owner is Alicia" +date: "2017-08-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/93d6c7b74ed2a82966163c93ff72aceb6858fc68-467x700.jpg" +intro: "This image was reposted (with premission) from the denofangles.com forum." +title: "[auf Englisch] Bruce on this doll because why not?" +--- + + +This image was reposted (with premission) from the [denofangles.com](https://denofangels.com/posts/12259581/) forum. + diff --git a/markdown/org/showcase/bruce-on-doll/en.md b/markdown/org/showcase/bruce-on-doll/en.md new file mode 100644 index 00000000000..da605f46910 --- /dev/null +++ b/markdown/org/showcase/bruce-on-doll/en.md @@ -0,0 +1,13 @@ +--- +maker: "unknown" +caption: "The doll is named Jon, and its owner is Alicia" +date: "2017-08-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/93d6c7b74ed2a82966163c93ff72aceb6858fc68-467x700.jpg" +intro: "This image was reposted (with premission) from the denofangles.com forum." +title: "Bruce on this doll because why not?" +--- + + +This image was reposted (with premission) from the +[denofangles.com](https://denofangels.com/posts/12259581/) forum. + diff --git a/markdown/org/showcase/bruce-on-doll/es.md b/markdown/org/showcase/bruce-on-doll/es.md new file mode 100644 index 00000000000..d9576982719 --- /dev/null +++ b/markdown/org/showcase/bruce-on-doll/es.md @@ -0,0 +1,13 @@ +--- +maker: "unknown" +caption: "The doll is named Jon, and its owner is Alicia" +date: "2017-08-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/93d6c7b74ed2a82966163c93ff72aceb6858fc68-467x700.jpg" +intro: "This image was reposted (with premission) from the denofangles.com forum." +title: "Bruce on this doll because why not? [No traducido]" +--- + + +This image was reposted (with premission) from the +[denofangles.com](https://denofangels.com/posts/12259581/) forum. + diff --git a/markdown/org/showcase/bruce-on-doll/fr.md b/markdown/org/showcase/bruce-on-doll/fr.md new file mode 100644 index 00000000000..d1a9ac64bdc --- /dev/null +++ b/markdown/org/showcase/bruce-on-doll/fr.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "La poupée s'appelle Jon, et son propriétaire est Alicia" +date: "2017-08-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/93d6c7b74ed2a82966163c93ff72aceb6858fc68-467x700.jpg" +intro: "Cette photo a été repostée (avec permission) à partir de denofangles.com ." +title: "Bruce sur cette poupée parce que pourquoi pas ?" +--- + + +Cette photo a été repostée (avec permission) à partir de [denofangles.com](https://denofangels.com/posts/12259581/). + diff --git a/markdown/org/showcase/bruce-on-doll/nl.md b/markdown/org/showcase/bruce-on-doll/nl.md new file mode 100644 index 00000000000..866e6abde1d --- /dev/null +++ b/markdown/org/showcase/bruce-on-doll/nl.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "De pop heet Jon, en de eigenaar Alicia" +date: "2017-08-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/93d6c7b74ed2a82966163c93ff72aceb6858fc68-467x700.jpg" +intro: "Deze afbeelding werd hier (met toestemming) gepost vanop het denofangels.com forum." +title: "Bruce op deze pop, waarom niet?" +--- + + +Deze afbeelding werd hier (met toestemming) gepost vanop het [denofangels.com](https://denofangels.com/posts/12259581/) forum. + diff --git a/markdown/org/showcase/bruce-three-pack/de.md b/markdown/org/showcase/bruce-three-pack/de.md new file mode 100644 index 00000000000..535f868116b --- /dev/null +++ b/markdown/org/showcase/bruce-three-pack/de.md @@ -0,0 +1,21 @@ +--- +maker: "unknown" +caption: "Theo made three of these from leftover jersey." +date: "2018-10-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/305d6d6adbdad633bc2cd33b0de6f7a199a38c28-3043x2282.jpg" +intro: "Felix made three of these, and he writes:" +title: "A Bruce three-pack [Nicht übersetzt]" +--- + +Felix made three of these, and he writes: + +> I just finished a three-pack* of Bruce underpants. +> I used some jersey leftovers and tried some elastic stitches on +> my sewing machine, not all seams were perfect - but now I know +> which settings are the best. +> +> They fit excellent! + +Here's a picture of the back: + +![Back image](https://posts.freesewing.org/uploads/bruce_three_pack_back_6ed8c9ae38.jpg "Back image") diff --git a/markdown/org/showcase/bruce-three-pack/en.md b/markdown/org/showcase/bruce-three-pack/en.md new file mode 100644 index 00000000000..310c490a412 --- /dev/null +++ b/markdown/org/showcase/bruce-three-pack/en.md @@ -0,0 +1,21 @@ +--- +maker: "unknown" +caption: "Theo made three of these from leftover jersey." +date: "2018-10-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/305d6d6adbdad633bc2cd33b0de6f7a199a38c28-3043x2282.jpg" +intro: "Felix made three of these, and he writes:" +title: "A Bruce three-pack" +--- + +Felix made three of these, and he writes: + +> I just finished a three-pack* of Bruce underpants. +> I used some jersey leftovers and tried some elastic stitches on +> my sewing machine, not all seams were perfect - but now I know +> which settings are the best. +> +> They fit excellent! + +Here's a picture of the back: + +![Back image](https://posts.freesewing.org/uploads/bruce_three_pack_back_6ed8c9ae38.jpg "Back image") diff --git a/markdown/org/showcase/bruce-three-pack/es.md b/markdown/org/showcase/bruce-three-pack/es.md new file mode 100644 index 00000000000..8eeeb4fa8d4 --- /dev/null +++ b/markdown/org/showcase/bruce-three-pack/es.md @@ -0,0 +1,21 @@ +--- +maker: "unknown" +caption: "Theo made three of these from leftover jersey." +date: "2018-10-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/305d6d6adbdad633bc2cd33b0de6f7a199a38c28-3043x2282.jpg" +intro: "Felix made three of these, and he writes:" +title: "A Bruce three-pack [No traducido]" +--- + +Felix made three of these, and he writes: + +> I just finished a three-pack* of Bruce underpants. +> I used some jersey leftovers and tried some elastic stitches on +> my sewing machine, not all seams were perfect - but now I know +> which settings are the best. +> +> They fit excellent! + +Here's a picture of the back: + +![Back image](https://posts.freesewing.org/uploads/bruce_three_pack_back_6ed8c9ae38.jpg "Back image") diff --git a/markdown/org/showcase/bruce-three-pack/fr.md b/markdown/org/showcase/bruce-three-pack/fr.md new file mode 100644 index 00000000000..00e43b0983a --- /dev/null +++ b/markdown/org/showcase/bruce-three-pack/fr.md @@ -0,0 +1,20 @@ +--- +maker: "unknown" +caption: "Theo en a fait trois à partir du chutes de jersey." +date: "2018-10-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/305d6d6adbdad633bc2cd33b0de6f7a199a38c28-3043x2282.jpg" +intro: "Félix en a fait trois, et il écrit :" +title: "Un lot de trois Bruce" +--- + + +Félix en a fait trois, et il écrit : + +> Je viens de terminer un lot de trois boxers Bruce. J'ai utilisé des restes de jersey et j'ai essayé quelques points élastiques sur ma machine à coudre, toutes les coutures n'étaient pas parfaites - mais maintenant je sais quels paramètres sont les meilleurs. +> +> Ils sont parfaits ! + +Voici une photo du dos : + +![Photo du dos](https://posts.freesewing.org/uploads/bruce_three_pack_back_6ed8c9ae38.jpg "Photo du dos") + diff --git a/markdown/org/showcase/bruce-three-pack/nl.md b/markdown/org/showcase/bruce-three-pack/nl.md new file mode 100644 index 00000000000..827ea1f9b45 --- /dev/null +++ b/markdown/org/showcase/bruce-three-pack/nl.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "Theo maakte er zo drie uit overgebleven jersey." +date: "2018-10-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/305d6d6adbdad633bc2cd33b0de6f7a199a38c28-3043x2282.jpg" +intro: "Felix maakte drie boxershorts, en schrijft:" +title: "Een Bruce trio" +--- + + +Felix maakte drie boxershorts, en schrijft: + +> Ik heb net een trio van Bruce boxershorts gemaakt. Ik gebruikte een paar restjes jersey en probeerde een paar elastische steken op mijn naaimachine. Niet alle naden zijn perfect, maar nu weet ik welke instellingen het best werken. +> +> Ze passen perfect! + +Hier is een foto van de achterkant: + +![Zicht op de achterkant](https://posts.freesewing.org/uploads/bruce_three_pack_back_6ed8c9ae38.jpg "Zicht op de achterkant") diff --git a/markdown/org/showcase/bruces-by-paul/de.md b/markdown/org/showcase/bruces-by-paul/de.md new file mode 100644 index 00000000000..e296def4fed --- /dev/null +++ b/markdown/org/showcase/bruces-by-paul/de.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "A few bruces to use up left over textile from t-shirts and dresses" +date: "2018-12-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ebfd17f37ad974a3d2814f4d03a7dbe4db3608a8-2000x1296.jpg" +intro: "[auf Englisch] Bruces by Paul" +title: "[auf Englisch] Bruces by Paul" +--- + +![View of the back](https://posts.freesewing.org/uploads/bruces_by_paul_back_19f9daa0e8.jpg "View of the back") diff --git a/markdown/org/showcase/bruces-by-paul/en.md b/markdown/org/showcase/bruces-by-paul/en.md new file mode 100644 index 00000000000..bddd126a8f3 --- /dev/null +++ b/markdown/org/showcase/bruces-by-paul/en.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "A few bruces to use up left over textile from t-shirts and dresses" +date: "2018-12-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ebfd17f37ad974a3d2814f4d03a7dbe4db3608a8-2000x1296.jpg" +intro: "Bruces by Paul" +title: "Bruces by Paul" +--- + +![View of the back](https://posts.freesewing.org/uploads/bruces_by_paul_back_19f9daa0e8.jpg "View of the back") diff --git a/markdown/org/showcase/bruces-by-paul/es.md b/markdown/org/showcase/bruces-by-paul/es.md new file mode 100644 index 00000000000..3524afb33f2 --- /dev/null +++ b/markdown/org/showcase/bruces-by-paul/es.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "A few bruces to use up left over textile from t-shirts and dresses" +date: "2018-12-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ebfd17f37ad974a3d2814f4d03a7dbe4db3608a8-2000x1296.jpg" +intro: "Bruces by Paul [No traducido]" +title: "Bruces by Paul [No traducido]" +--- + +![View of the back](https://posts.freesewing.org/uploads/bruces_by_paul_back_19f9daa0e8.jpg "View of the back") diff --git a/markdown/org/showcase/bruces-by-paul/fr.md b/markdown/org/showcase/bruces-by-paul/fr.md new file mode 100644 index 00000000000..5e81038a2ad --- /dev/null +++ b/markdown/org/showcase/bruces-by-paul/fr.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "Quelques Bruces pour réutiliser les tissus à partir de t-shirts et robes" +date: "2018-12-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ebfd17f37ad974a3d2814f4d03a7dbe4db3608a8-2000x1296.jpg" +intro: "Des Bruces faits par Paul" +title: "Des Bruces faits par Paul" +--- + +![Vue du dos](https://posts.freesewing.org/uploads/bruces_by_paul_back_19f9daa0e8.jpg "Vue du dos") diff --git a/markdown/org/showcase/bruces-by-paul/nl.md b/markdown/org/showcase/bruces-by-paul/nl.md new file mode 100644 index 00000000000..c455d2758a8 --- /dev/null +++ b/markdown/org/showcase/bruces-by-paul/nl.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "Een paar exemplaren van Bruce om resten stof van t-shirts en jurken op te gebruiken" +date: "2018-12-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ebfd17f37ad974a3d2814f4d03a7dbe4db3608a8-2000x1296.jpg" +intro: "Bruce door Paul" +title: "Bruce door Paul" +--- + +![Zicht op de achterkant](https://posts.freesewing.org/uploads/bruces_by_paul_back_19f9daa0e8.jpg "Zicht op de achterkant") diff --git a/markdown/org/showcase/bulbasaur-huey/de.md b/markdown/org/showcase/bulbasaur-huey/de.md new file mode 100644 index 00000000000..bce09228678 --- /dev/null +++ b/markdown/org/showcase/bulbasaur-huey/de.md @@ -0,0 +1,25 @@ +--- +maker: "unknown" +caption: "Bulbasaurs are strong AND cute" +date: "2017-11-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d7242993d4c611f4a5d48ba63b1b9a3139a1c6cd-2000x1333.jpg" +intro: " " +title: "[auf Englisch] A Bulbasaur Huey Hoodie Hack" +--- + +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_1_4f299d4b87.jpg "Bulbasaurs are strong AND cute") +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_2_6587c21b85.jpg "Bulbasaurs are strong AND cute") +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_3_b1f5057533.jpg "Bulbasaurs are strong AND cute") +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_4_f46df0bf35.jpg "Bulbasaurs are strong AND cute") +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_5_e95c003b27.jpg "Bulbasaurs are strong AND cute") +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_6_e82a85e020.jpg "Bulbasaurs are strong AND cute") + + + +###### See the original on Frankie's blog +These picture are from the [Bulbasaur Costume for Children In Need](http://knitwits-owls.blogspot.be/2017/11/bulbasaur-costume-for-children-in-need.html) +blog post on [knitwits-owls.blogspot.com](http://knitwits-owls.blogspot.be). + +They are reposted here with permission. + + diff --git a/markdown/org/showcase/bulbasaur-huey/en.md b/markdown/org/showcase/bulbasaur-huey/en.md new file mode 100644 index 00000000000..6c00e4e8b6a --- /dev/null +++ b/markdown/org/showcase/bulbasaur-huey/en.md @@ -0,0 +1,25 @@ +--- +maker: "unknown" +caption: "Bulbasaurs are strong AND cute" +date: "2017-11-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d7242993d4c611f4a5d48ba63b1b9a3139a1c6cd-2000x1333.jpg" +intro: " " +title: "A Bulbasaur Huey Hoodie Hack" +--- + +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_1_4f299d4b87.jpg "Bulbasaurs are strong AND cute") +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_2_6587c21b85.jpg "Bulbasaurs are strong AND cute") +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_3_b1f5057533.jpg "Bulbasaurs are strong AND cute") +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_4_f46df0bf35.jpg "Bulbasaurs are strong AND cute") +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_5_e95c003b27.jpg "Bulbasaurs are strong AND cute") +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_6_e82a85e020.jpg) + + + +###### See the original on Frankie's blog +These picture are from the [Bulbasaur Costume for Children In Need](http://knitwits-owls.blogspot.be/2017/11/bulbasaur-costume-for-children-in-need.html) +blog post on [knitwits-owls.blogspot.com](http://knitwits-owls.blogspot.be). + +They are reposted here with permission. + + diff --git a/markdown/org/showcase/bulbasaur-huey/es.md b/markdown/org/showcase/bulbasaur-huey/es.md new file mode 100644 index 00000000000..6b6441c3b66 --- /dev/null +++ b/markdown/org/showcase/bulbasaur-huey/es.md @@ -0,0 +1,25 @@ +--- +maker: "unknown" +caption: "Bulbasaurs are strong AND cute" +date: "2017-11-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d7242993d4c611f4a5d48ba63b1b9a3139a1c6cd-2000x1333.jpg" +intro: " " +title: "A Bulbasaur Huey Hoodie Hack [No traducido]" +--- + +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_1_4f299d4b87.jpg "Bulbasaurs are strong AND cute") +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_2_6587c21b85.jpg "Bulbasaurs are strong AND cute") +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_3_b1f5057533.jpg "Bulbasaurs are strong AND cute") +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_4_f46df0bf35.jpg "Bulbasaurs are strong AND cute") +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_5_e95c003b27.jpg "Bulbasaurs are strong AND cute") +![Bulbasaurs are strong AND cute](https://posts.freesewing.org/uploads/bulbasaur_huey_6_e82a85e020.jpg) + + + +###### See the original on Frankie's blog +These picture are from the [Bulbasaur Costume for Children In Need](http://knitwits-owls.blogspot.be/2017/11/bulbasaur-costume-for-children-in-need.html) +blog post on [knitwits-owls.blogspot.com](http://knitwits-owls.blogspot.be). + +They are reposted here with permission. + + diff --git a/markdown/org/showcase/bulbasaur-huey/fr.md b/markdown/org/showcase/bulbasaur-huey/fr.md new file mode 100644 index 00000000000..52b35976baa --- /dev/null +++ b/markdown/org/showcase/bulbasaur-huey/fr.md @@ -0,0 +1,25 @@ +--- +maker: "unknown" +caption: "Les Bulbizarres sont forts ET mignons" +date: "2017-11-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d7242993d4c611f4a5d48ba63b1b9a3139a1c6cd-2000x1333.jpg" +intro: " " +title: "Un Hack du sweat zippé à capuche Huey en Bulbizarre" +--- + +![Les Bulbizarres sont forts ET mignons](https://posts.freesewing.org/uploads/bulbasaur_huey_1_4f299d4b87.jpg "Les Bulbizarres sont forts ET mignons") +![Les Bulbizarres sont forts ET mignons](https://posts.freesewing.org/uploads/bulbasaur_huey_2_6587c21b85.jpg "Les Bulbizarres sont forts ET mignons") +![Les Bulbizarres sont forts ET mignons](https://posts.freesewing.org/uploads/bulbasaur_huey_3_b1f5057533.jpg "Les Bulbizarres sont forts ET mignons") +![Les Bulbizarres sont forts ET mignons](https://posts.freesewing.org/uploads/bulbasaur_huey_4_f46df0bf35.jpg "Les Bulbizarres sont forts ET mignons") +![Les Bulbizarres sont forts ET mignons](https://posts.freesewing.org/uploads/bulbasaur_huey_5_e95c003b27.jpg "Les Bulbizarres sont forts ET mignons") +![Les Bulbizarres sont forts ET mignons](https://posts.freesewing.org/uploads/bulbasaur_huey_6_e82a85e020.jpg) + + + +###### Voir l'original sur le blog de Frankie +Ces photos proviennent de [Costume Bulbizarre pour enfants dans le besoin](http://knitwits-owls.blogspot.be/2017/11/bulbasaur-costume-for-children-in-need.html) +l'article de blog sur [knitwits-owls.blogspot.com](http://knitwits-owls.blogspot.be). + +Elles sont repostées ici avec autorisation. + + diff --git a/markdown/org/showcase/bulbasaur-huey/nl.md b/markdown/org/showcase/bulbasaur-huey/nl.md new file mode 100644 index 00000000000..81a675b5959 --- /dev/null +++ b/markdown/org/showcase/bulbasaur-huey/nl.md @@ -0,0 +1,25 @@ +--- +maker: "unknown" +caption: "Bulbasaurs zijn sterk EN schattig" +date: "2017-11-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/d7242993d4c611f4a5d48ba63b1b9a3139a1c6cd-2000x1333.jpg" +intro: " " +title: "Een Bulbasaur Huey Hoodie Hack" +--- + +![Bulbasaurs zijn sterk EN schattig](https://posts.freesewing.org/uploads/bulbasaur_huey_1_4f299d4b87.jpg "Bulbasaurs zijn sterk EN schattig") +![Bulbasaurs zijn sterk EN schattig](https://posts.freesewing.org/uploads/bulbasaur_huey_2_6587c21b85.jpg "Bulbasaurs zijn sterk EN schattig") +![Bulbasaurs zijn sterk EN schattig](https://posts.freesewing.org/uploads/bulbasaur_huey_3_b1f5057533.jpg "Bulbasaurs zijn sterk EN schattig") +![Bulbasaurs zijn sterk EN schattig](https://posts.freesewing.org/uploads/bulbasaur_huey_4_f46df0bf35.jpg "Bulbasaurs zijn sterk EN schattig") +![Bulbasaurs zijn sterk EN schattig](https://posts.freesewing.org/uploads/bulbasaur_huey_5_e95c003b27.jpg "Bulbasaurs zijn sterk EN schattig") +![Bulbasaurs zijn sterk EN schattig](5.jpg) ![Bulbasaurs zijn sterk EN schattig](6.jpg) + + + +###### See the original on Frankie's blog +These picture are from the [Bulbasaur Costume for Children In Need](http://knitwits-owls.blogspot.be/2017/11/bulbasaur-costume-for-children-in-need.html) +blog post on [knitwits-owls.blogspot.com](http://knitwits-owls.blogspot.be). + +Ze werden hier gepost met toestemming. + + diff --git a/markdown/org/showcase/carlton-by-rudy/de.md b/markdown/org/showcase/carlton-by-rudy/de.md new file mode 100644 index 00000000000..48a451f3f6f --- /dev/null +++ b/markdown/org/showcase/carlton-by-rudy/de.md @@ -0,0 +1,24 @@ +--- +maker: "unknown" +caption: "The Carlton coat by Rudy" +date: "2021-02-26" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4aef096adffa48aa1d8b1cb45fb2d417993eb707-613x613.jpg" +intro: "This stylish Carlton coat was made by Rudy, who shared:" +title: "[auf Englisch] Carlton coat by Rudy" +--- + +This stylish Carlton coat was made by Rudy, who shared: + +> My take on the Carlton coat. My first big sewing project and first time using a freesewing pattern. I even made my own buttons :) + +![View of the front](https://posts.freesewing.org/uploads/carlton_by_rudy_carltonrudy2_ff73f3dc38.jpg "View of the front") + +![Buttoned view](carltonrudy3.jpg) + +![View of the back](carltonrudy4.jpg) + + + +This picture is from Rudy, [@rudy_lee21 on Instagram](https://www.instagram.com/rudy_lee21/). It is reposted here with permission. + + diff --git a/markdown/org/showcase/carlton-by-rudy/en.md b/markdown/org/showcase/carlton-by-rudy/en.md new file mode 100644 index 00000000000..2adee52a8b7 --- /dev/null +++ b/markdown/org/showcase/carlton-by-rudy/en.md @@ -0,0 +1,24 @@ +--- +maker: "unknown" +caption: "The Carlton coat by Rudy" +date: "2021-02-26" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4aef096adffa48aa1d8b1cb45fb2d417993eb707-613x613.jpg" +intro: "This stylish Carlton coat was made by Rudy, who shared:" +title: "Carlton coat by Rudy" +--- + +This stylish Carlton coat was made by Rudy, who shared: + +> My take on the Carlton coat. My first big sewing project and first time using a freesewing pattern. I even made my own buttons :) + +![View of the front](https://posts.freesewing.org/uploads/carlton_by_rudy_carltonrudy2_ff73f3dc38.jpg "View of the front") + +![Buttoned view](https://posts.freesewing.org/uploads/carlton_by_rudy_carltonrudy3_dfe71f082f.jpg "Buttoned view") + +![View of the back](https://posts.freesewing.org/uploads/carlton_by_rudy_carltonrudy4_09a14b90d7.jpg) + + + +This picture is from Rudy, [@rudy_lee21 on Instagram](https://www.instagram.com/rudy_lee21/). It is reposted here with permission. + + diff --git a/markdown/org/showcase/carlton-by-rudy/es.md b/markdown/org/showcase/carlton-by-rudy/es.md new file mode 100644 index 00000000000..282544a539e --- /dev/null +++ b/markdown/org/showcase/carlton-by-rudy/es.md @@ -0,0 +1,24 @@ +--- +maker: "unknown" +caption: "The Carlton coat by Rudy" +date: "2021-02-26" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4aef096adffa48aa1d8b1cb45fb2d417993eb707-613x613.jpg" +intro: "This stylish Carlton coat was made by Rudy, who shared:" +title: "Carlton coat by Rudy [No traducido]" +--- + +This stylish Carlton coat was made by Rudy, who shared: + +> My take on the Carlton coat. My first big sewing project and first time using a freesewing pattern. I even made my own buttons :) + +![View of the front](https://posts.freesewing.org/uploads/carlton_by_rudy_carltonrudy2_ff73f3dc38.jpg "View of the front") + +![Buttoned view](https://posts.freesewing.org/uploads/carlton_by_rudy_carltonrudy3_dfe71f082f.jpg "Buttoned view") + +![View of the back](https://posts.freesewing.org/uploads/carlton_by_rudy_carltonrudy4_09a14b90d7.jpg) + + + +This picture is from Rudy, [@rudy_lee21 on Instagram](https://www.instagram.com/rudy_lee21/). It is reposted here with permission. + + diff --git a/markdown/org/showcase/carlton-by-rudy/fr.md b/markdown/org/showcase/carlton-by-rudy/fr.md new file mode 100644 index 00000000000..5d241333d4c --- /dev/null +++ b/markdown/org/showcase/carlton-by-rudy/fr.md @@ -0,0 +1,24 @@ +--- +maker: "unknown" +caption: "Le manteau Carlton par Rudy" +date: "2021-02-26" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4aef096adffa48aa1d8b1cb45fb2d417993eb707-613x613.jpg" +intro: "Ce manteau élégant Carlton a été fait par Rudy qui a partagé :" +title: "Manteau Carlton par Rudy" +--- + +Ce manteau élégant Carlton a été fait par Rudy qui a partagé : + +> Ma version du manteau Carlton. Mon premier grand projet de couture et la première fois en utilisant un patron freesewing. J'ai même fait mes propres boutons :) + +![Photo de l'avant](https://posts.freesewing.org/uploads/carlton_by_rudy_carltonrudy2_ff73f3dc38.jpg "Photo de l'avant") + +![Vue boutonnée](https://posts.freesewing.org/uploads/carlton_by_rudy_carltonrudy3_dfe71f082f.jpg "Vue boutonnée") + +![Vue du dos](https://posts.freesewing.org/uploads/carlton_by_rudy_carltonrudy4_09a14b90d7.jpg "Vue du dos") + + + +Cette photo provient de Rudy, [@rudy_lee21 sur Instagram](https://www.instagram.com/rudy_lee21/). Elle est publiée ici avec son autorisation. + + diff --git a/markdown/org/showcase/carlton-by-rudy/nl.md b/markdown/org/showcase/carlton-by-rudy/nl.md new file mode 100644 index 00000000000..967498d1243 --- /dev/null +++ b/markdown/org/showcase/carlton-by-rudy/nl.md @@ -0,0 +1,24 @@ +--- +maker: "unknown" +caption: "The Carlton coat by Rudy" +date: "2021-02-26" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4aef096adffa48aa1d8b1cb45fb2d417993eb707-613x613.jpg" +intro: "This stylish Carlton coat was made by Rudy, who shared:" +title: "Carlton coat by Rudy [Niet vertaald]" +--- + +This stylish Carlton coat was made by Rudy, who shared: + +> My take on the Carlton coat. My first big sewing project and first time using a freesewing pattern. I even made my own buttons :) + +![View of the front](https://posts.freesewing.org/uploads/carlton_by_rudy_carltonrudy2_ff73f3dc38.jpg "View of the front") + +![Buttoned view](https://posts.freesewing.org/uploads/carlton_by_rudy_carltonrudy3_dfe71f082f.jpg "Buttoned view") + +![View of the back](https://posts.freesewing.org/uploads/carlton_by_rudy_carltonrudy4_09a14b90d7.jpg) + + + +This picture is from Rudy, [@rudy_lee21 on Instagram](https://www.instagram.com/rudy_lee21/). It is reposted here with permission. + + diff --git a/markdown/org/showcase/casual-pink-simon/de.md b/markdown/org/showcase/casual-pink-simon/de.md new file mode 100644 index 00000000000..78785707280 --- /dev/null +++ b/markdown/org/showcase/casual-pink-simon/de.md @@ -0,0 +1,11 @@ +--- +maker: "Joost De Cock" +caption: "A Simon shirt by Joost" +date: "2017-03-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/126118086acff3eb0102a5defaa8ef47977a23c0-2048x1365.jpg" +intro: "FIXME_no_intro" +title: "[auf Englisch] Joost does Simon" +--- + + + diff --git a/markdown/org/showcase/casual-pink-simon/en.md b/markdown/org/showcase/casual-pink-simon/en.md new file mode 100644 index 00000000000..31ace9f4f38 --- /dev/null +++ b/markdown/org/showcase/casual-pink-simon/en.md @@ -0,0 +1,10 @@ +--- +maker: "Joost De Cock" +caption: "A Simon shirt by Joost" +date: "2017-03-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/126118086acff3eb0102a5defaa8ef47977a23c0-2048x1365.jpg" +intro: "FIXME_no_intro" +title: "Joost does Simon" +--- + + diff --git a/markdown/org/showcase/casual-pink-simon/es.md b/markdown/org/showcase/casual-pink-simon/es.md new file mode 100644 index 00000000000..05dfce18fbd --- /dev/null +++ b/markdown/org/showcase/casual-pink-simon/es.md @@ -0,0 +1,10 @@ +--- +maker: "Joost De Cock" +caption: "A Simon shirt by Joost" +date: "2017-03-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/126118086acff3eb0102a5defaa8ef47977a23c0-2048x1365.jpg" +intro: "FIXME_no_intro" +title: "Joost does Simon [No traducido]" +--- + + diff --git a/markdown/org/showcase/casual-pink-simon/fr.md b/markdown/org/showcase/casual-pink-simon/fr.md new file mode 100644 index 00000000000..6ff816747cf --- /dev/null +++ b/markdown/org/showcase/casual-pink-simon/fr.md @@ -0,0 +1,11 @@ +--- +maker: "Joost De Cock" +caption: "Une chemise Simon par Joost" +date: "2017-03-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/126118086acff3eb0102a5defaa8ef47977a23c0-2048x1365.jpg" +intro: "FIXME_no_intro" +title: "Joost fait Simon" +--- + + + diff --git a/markdown/org/showcase/casual-pink-simon/nl.md b/markdown/org/showcase/casual-pink-simon/nl.md new file mode 100644 index 00000000000..95173e6e2c7 --- /dev/null +++ b/markdown/org/showcase/casual-pink-simon/nl.md @@ -0,0 +1,11 @@ +--- +maker: "Joost De Cock" +caption: "Een Simon hemd door Joost" +date: "2017-03-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/126118086acff3eb0102a5defaa8ef47977a23c0-2048x1365.jpg" +intro: "FIXME_no_intro" +title: "Joost maakt Simon" +--- + + + diff --git a/markdown/org/showcase/charlie-by-bob/de.md b/markdown/org/showcase/charlie-by-bob/de.md new file mode 100644 index 00000000000..46ee4aeeb64 --- /dev/null +++ b/markdown/org/showcase/charlie-by-bob/de.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Bob's first pair of Charlie trousers" +date: "2021-05-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ee76fe8c268daeeccaf13b26086bd70e4f8537b0-1200x1600.jpg" +intro: "Bob3000's first pair of Charlie trousers are super rad! Keep an eye out for an upcoming second pair in selvedge denim." +title: "[auf Englisch] Charlie by Bob3000" +--- + + +Bob3000's first pair of Charlie trousers are super rad! Keep an eye out for an upcoming second pair in selvedge denim. + + + +Dieses Bild stammt von bob3000 aus dem [FreeSewing Discord](https://discord.freesewing.org/). It is reposted here with permission. + + + diff --git a/markdown/org/showcase/charlie-by-bob/en.md b/markdown/org/showcase/charlie-by-bob/en.md new file mode 100644 index 00000000000..e29a07bda5b --- /dev/null +++ b/markdown/org/showcase/charlie-by-bob/en.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Bob's first pair of Charlie trousers" +date: "2021-05-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ee76fe8c268daeeccaf13b26086bd70e4f8537b0-1200x1600.jpg" +intro: "Bob3000's first pair of Charlie trousers are super rad! Keep an eye out for an upcoming second pair in selvedge denim." +title: "Charlie by Bob3000" +--- + + +Bob3000's first pair of Charlie trousers are super rad! Keep an eye out for an upcoming second pair in selvedge denim. + + + +This picture is from bob3000 on [the FreeSewing Discord](https://discord.freesewing.org/). It is reposted here with permission. + + + diff --git a/markdown/org/showcase/charlie-by-bob/es.md b/markdown/org/showcase/charlie-by-bob/es.md new file mode 100644 index 00000000000..38d24bad385 --- /dev/null +++ b/markdown/org/showcase/charlie-by-bob/es.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Bob's first pair of Charlie trousers" +date: "2021-05-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ee76fe8c268daeeccaf13b26086bd70e4f8537b0-1200x1600.jpg" +intro: "Bob3000's first pair of Charlie trousers are super rad! Keep an eye out for an upcoming second pair in selvedge denim." +title: "Charlie by Bob3000 [No traducido]" +--- + + +Bob3000's first pair of Charlie trousers are super rad! Keep an eye out for an upcoming second pair in selvedge denim. + + + +This picture is from bob3000 on [the FreeSewing Discord](https://discord.freesewing.org/). It is reposted here with permission. + + + diff --git a/markdown/org/showcase/charlie-by-bob/fr.md b/markdown/org/showcase/charlie-by-bob/fr.md new file mode 100644 index 00000000000..a9754ec2754 --- /dev/null +++ b/markdown/org/showcase/charlie-by-bob/fr.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Bob's first pair of Charlie trousers" +date: "2021-05-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ee76fe8c268daeeccaf13b26086bd70e4f8537b0-1200x1600.jpg" +intro: "Bob3000's first pair of Charlie trousers are super rad! Keep an eye out for an upcoming second pair in selvedge denim." +title: "[En anglais] Charlie by Bob3000" +--- + + +Bob3000's first pair of Charlie trousers are super rad! Keep an eye out for an upcoming second pair in selvedge denim. + + + +This picture is from bob3000 on [the FreeSewing Discord](https://discord.freesewing.org/). Elle est publiée ici avec son autorisation. + + + diff --git a/markdown/org/showcase/charlie-by-bob/nl.md b/markdown/org/showcase/charlie-by-bob/nl.md new file mode 100644 index 00000000000..4f87d4ed61b --- /dev/null +++ b/markdown/org/showcase/charlie-by-bob/nl.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Bob's first pair of Charlie trousers" +date: "2021-05-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ee76fe8c268daeeccaf13b26086bd70e4f8537b0-1200x1600.jpg" +intro: "Bob3000's first pair of Charlie trousers are super rad! Keep an eye out for an upcoming second pair in selvedge denim." +title: "Charlie by Bob3000 [Niet vertaald]" +--- + + +Bob3000's first pair of Charlie trousers are super rad! Keep an eye out for an upcoming second pair in selvedge denim. + + + +This picture is from bob3000 on [the FreeSewing Discord](https://discord.freesewing.org/). It is reposted here with permission. + + + diff --git a/markdown/org/showcase/charlie-by-joost-2/de.md b/markdown/org/showcase/charlie-by-joost-2/de.md new file mode 100644 index 00000000000..98fc5768057 --- /dev/null +++ b/markdown/org/showcase/charlie-by-joost-2/de.md @@ -0,0 +1,18 @@ +--- +maker: "Joost De Cock" +caption: "Moar Charlie" +date: "2021-05-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/20ccf81fc098beaab92cbb48ee1a37b9f6a011c9-600x800.jpg" +intro: "Joost made another excellent pair of Charlie Chinos in this tan fabric." +title: "Another Charlie by Joost" +--- + + +Joost made another excellent pair of Charlie Chinos in this tan fabric. + +![Another view](https://posts.freesewing.org/uploads/charlie_by_joost_2_charliebyjoost3_78b3eecfb6.jpg) + +![A look at the fabric](https://posts.freesewing.org/uploads/charlie_by_joost_2_charliebyjoost4_0329b2ca47.jpg) + +This picture is from Joost, [@j__st on Twitter](https://twitter.com/j__st). It is reposted here with permission. + diff --git a/markdown/org/showcase/charlie-by-joost-2/en.md b/markdown/org/showcase/charlie-by-joost-2/en.md new file mode 100644 index 00000000000..98fc5768057 --- /dev/null +++ b/markdown/org/showcase/charlie-by-joost-2/en.md @@ -0,0 +1,18 @@ +--- +maker: "Joost De Cock" +caption: "Moar Charlie" +date: "2021-05-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/20ccf81fc098beaab92cbb48ee1a37b9f6a011c9-600x800.jpg" +intro: "Joost made another excellent pair of Charlie Chinos in this tan fabric." +title: "Another Charlie by Joost" +--- + + +Joost made another excellent pair of Charlie Chinos in this tan fabric. + +![Another view](https://posts.freesewing.org/uploads/charlie_by_joost_2_charliebyjoost3_78b3eecfb6.jpg) + +![A look at the fabric](https://posts.freesewing.org/uploads/charlie_by_joost_2_charliebyjoost4_0329b2ca47.jpg) + +This picture is from Joost, [@j__st on Twitter](https://twitter.com/j__st). It is reposted here with permission. + diff --git a/markdown/org/showcase/charlie-by-joost-2/es.md b/markdown/org/showcase/charlie-by-joost-2/es.md new file mode 100644 index 00000000000..eb275dc673b --- /dev/null +++ b/markdown/org/showcase/charlie-by-joost-2/es.md @@ -0,0 +1,18 @@ +--- +maker: "Joost De Cock" +caption: "Moar Charlie" +date: "2021-05-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/20ccf81fc098beaab92cbb48ee1a37b9f6a011c9-600x800.jpg" +intro: "Joost made another excellent pair of Charlie Chinos in this tan fabric." +title: "Another Charlie by Joost [No traducido]" +--- + + +Joost made another excellent pair of Charlie Chinos in this tan fabric. + +![Another view](https://posts.freesewing.org/uploads/charlie_by_joost_2_charliebyjoost3_78b3eecfb6.jpg) + +![A look at the fabric](https://posts.freesewing.org/uploads/charlie_by_joost_2_charliebyjoost4_0329b2ca47.jpg) + +This picture is from Joost, [@j__st on Twitter](https://twitter.com/j__st). It is reposted here with permission. + diff --git a/markdown/org/showcase/charlie-by-joost-2/fr.md b/markdown/org/showcase/charlie-by-joost-2/fr.md new file mode 100644 index 00000000000..98fc5768057 --- /dev/null +++ b/markdown/org/showcase/charlie-by-joost-2/fr.md @@ -0,0 +1,18 @@ +--- +maker: "Joost De Cock" +caption: "Moar Charlie" +date: "2021-05-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/20ccf81fc098beaab92cbb48ee1a37b9f6a011c9-600x800.jpg" +intro: "Joost made another excellent pair of Charlie Chinos in this tan fabric." +title: "Another Charlie by Joost" +--- + + +Joost made another excellent pair of Charlie Chinos in this tan fabric. + +![Another view](https://posts.freesewing.org/uploads/charlie_by_joost_2_charliebyjoost3_78b3eecfb6.jpg) + +![A look at the fabric](https://posts.freesewing.org/uploads/charlie_by_joost_2_charliebyjoost4_0329b2ca47.jpg) + +This picture is from Joost, [@j__st on Twitter](https://twitter.com/j__st). It is reposted here with permission. + diff --git a/markdown/org/showcase/charlie-by-joost-2/nl.md b/markdown/org/showcase/charlie-by-joost-2/nl.md new file mode 100644 index 00000000000..2c9b6bab001 --- /dev/null +++ b/markdown/org/showcase/charlie-by-joost-2/nl.md @@ -0,0 +1,18 @@ +--- +maker: "Joost De Cock" +caption: "Moar Charlie" +date: "2021-05-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/20ccf81fc098beaab92cbb48ee1a37b9f6a011c9-600x800.jpg" +intro: "Joost made another excellent pair of Charlie Chinos in this tan fabric." +title: "Another Charlie by Joost [Niet vertaald]" +--- + + +Joost made another excellent pair of Charlie Chinos in this tan fabric. + +![Another view](https://posts.freesewing.org/uploads/charlie_by_joost_2_charliebyjoost3_78b3eecfb6.jpg) + +![A look at the fabric](https://posts.freesewing.org/uploads/charlie_by_joost_2_charliebyjoost4_0329b2ca47.jpg) + +This picture is from Joost, [@j__st on Twitter](https://twitter.com/j__st). It is reposted here with permission. + diff --git a/markdown/org/showcase/charlie-by-joost/de.md b/markdown/org/showcase/charlie-by-joost/de.md new file mode 100644 index 00000000000..37bfd9b708d --- /dev/null +++ b/markdown/org/showcase/charlie-by-joost/de.md @@ -0,0 +1,18 @@ +--- +maker: "Joost De Cock" +caption: "The first ever pair of Charlie Chinos" +date: "2021-05-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4316e61ba68384487d5e6c1f6c50c3fc935ebdcb-600x800.jpg" +intro: "Joost made this pair of Charlie Chinos trousers and the entire FreeSewing community immediately fell for the trousers' design and the fabric. While Joost couldn't tell us where the fabric came from (it was from his stash), he release the Charlie pattern a few days later." +title: "[auf Englisch] Charlie by Joost" +--- + + +Joost made this pair of Charlie Chinos trousers and the entire FreeSewing community immediately fell for the trousers' design and the fabric. While Joost couldn't tell us where the fabric came from (it was from his stash), he *did* release the Charlie pattern a few days later. + + + +This picture is from Joost, [@j__st on Twitter](https://twitter.com/j__st). It is reposted here with permission. + + + diff --git a/markdown/org/showcase/charlie-by-joost/en.md b/markdown/org/showcase/charlie-by-joost/en.md new file mode 100644 index 00000000000..ae38bc61f5b --- /dev/null +++ b/markdown/org/showcase/charlie-by-joost/en.md @@ -0,0 +1,14 @@ +--- +maker: "Joost De Cock" +caption: "The first ever pair of Charlie Chinos" +date: "2021-05-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4316e61ba68384487d5e6c1f6c50c3fc935ebdcb-600x800.jpg" +intro: "Joost made this pair of Charlie Chinos trousers and the entire FreeSewing community immediately fell for the trousers' design and the fabric. While Joost couldn't tell us where the fabric came from (it was from his stash), he release the Charlie pattern a few days later." +title: "Charlie by Joost" +--- + + +Joost made this pair of Charlie Chinos trousers and the entire FreeSewing community immediately fell for the trousers' design and the fabric. While Joost couldn't tell us where the fabric came from (it was from his stash), he *did* release the Charlie pattern a few days later. + +This picture is from Joost, [@j__st on Twitter](https://twitter.com/j__st). It is reposted here with permission. + diff --git a/markdown/org/showcase/charlie-by-joost/es.md b/markdown/org/showcase/charlie-by-joost/es.md new file mode 100644 index 00000000000..8a796db36ae --- /dev/null +++ b/markdown/org/showcase/charlie-by-joost/es.md @@ -0,0 +1,14 @@ +--- +maker: "Joost De Cock" +caption: "The first ever pair of Charlie Chinos" +date: "2021-05-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4316e61ba68384487d5e6c1f6c50c3fc935ebdcb-600x800.jpg" +intro: "Joost made this pair of Charlie Chinos trousers and the entire FreeSewing community immediately fell for the trousers' design and the fabric. While Joost couldn't tell us where the fabric came from (it was from his stash), he release the Charlie pattern a few days later." +title: "Charlie by Joost [No traducido]" +--- + + +Joost made this pair of Charlie Chinos trousers and the entire FreeSewing community immediately fell for the trousers' design and the fabric. While Joost couldn't tell us where the fabric came from (it was from his stash), he *did* release the Charlie pattern a few days later. + +This picture is from Joost, [@j__st on Twitter](https://twitter.com/j__st). It is reposted here with permission. + diff --git a/markdown/org/showcase/charlie-by-joost/fr.md b/markdown/org/showcase/charlie-by-joost/fr.md new file mode 100644 index 00000000000..655b458504b --- /dev/null +++ b/markdown/org/showcase/charlie-by-joost/fr.md @@ -0,0 +1,18 @@ +--- +maker: "Joost De Cock" +caption: "The first ever pair of Charlie Chinos" +date: "2021-05-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4316e61ba68384487d5e6c1f6c50c3fc935ebdcb-600x800.jpg" +intro: "Joost made this pair of Charlie Chinos trousers and the entire FreeSewing community immediately fell for the trousers' design and the fabric. While Joost couldn't tell us where the fabric came from (it was from his stash), he release the Charlie pattern a few days later." +title: "[En anglais] Charlie by Joost" +--- + + +Joost made this pair of Charlie Chinos trousers and the entire FreeSewing community immediately fell for the trousers' design and the fabric. While Joost couldn't tell us where the fabric came from (it was from his stash), he *did* release the Charlie pattern a few days later. + + + +This picture is from Joost, [@j__st on Twitter](https://twitter.com/j__st). Elle est publiée ici avec son autorisation. + + + diff --git a/markdown/org/showcase/charlie-by-joost/nl.md b/markdown/org/showcase/charlie-by-joost/nl.md new file mode 100644 index 00000000000..ee530375265 --- /dev/null +++ b/markdown/org/showcase/charlie-by-joost/nl.md @@ -0,0 +1,14 @@ +--- +maker: "Joost De Cock" +caption: "The first ever pair of Charlie Chinos" +date: "2021-05-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4316e61ba68384487d5e6c1f6c50c3fc935ebdcb-600x800.jpg" +intro: "Joost made this pair of Charlie Chinos trousers and the entire FreeSewing community immediately fell for the trousers' design and the fabric. While Joost couldn't tell us where the fabric came from (it was from his stash), he release the Charlie pattern a few days later." +title: "Charlie by Joost [Niet vertaald]" +--- + + +Joost made this pair of Charlie Chinos trousers and the entire FreeSewing community immediately fell for the trousers' design and the fabric. While Joost couldn't tell us where the fabric came from (it was from his stash), he *did* release the Charlie pattern a few days later. + +This picture is from Joost, [@j__st on Twitter](https://twitter.com/j__st). It is reposted here with permission. + diff --git a/markdown/org/showcase/charlie-on-sorcha/de.md b/markdown/org/showcase/charlie-on-sorcha/de.md new file mode 100644 index 00000000000..0a942713cc0 --- /dev/null +++ b/markdown/org/showcase/charlie-on-sorcha/de.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "A pair of Charlie Chinos on Sorcha" +date: "2021-05-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6aa91015d49712d1b56cdb3d6d56d04d372f2fab-2000x1331.jpg" +intro: "Sorcha is posing in a pair of Charlie chinos ." +title: "[auf Englisch] Charlie on Sorcha" +--- + +Sorcha is posing in a pair of [Charlie chinos](/designs/charlie/). + +![Rückansicht](https://posts.freesewing.org/uploads/charlie_on_sorcha_back_0ce0ffb9bb.jpg "Rückansicht") + +![Side view](https://posts.freesewing.org/uploads/charlie_on_sorcha_side_736bec4f5a.jpg "Side view") + +![Front view](front.jpg) diff --git a/markdown/org/showcase/charlie-on-sorcha/en.md b/markdown/org/showcase/charlie-on-sorcha/en.md new file mode 100644 index 00000000000..175c6cc7cba --- /dev/null +++ b/markdown/org/showcase/charlie-on-sorcha/en.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "A pair of Charlie Chinos on Sorcha" +date: "2021-05-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6aa91015d49712d1b56cdb3d6d56d04d372f2fab-2000x1331.jpg" +intro: "Sorcha is posing in a pair of Charlie chinos ." +title: "Charlie on Sorcha" +--- + +Sorcha is posing in a pair of [Charlie chinos](/designs/charlie/). + +![Back view](https://posts.freesewing.org/uploads/charlie_on_sorcha_back_0ce0ffb9bb.jpg "Back view") + +![Side view](https://posts.freesewing.org/uploads/charlie_on_sorcha_side_736bec4f5a.jpg "Side view") + +![Front view](https://posts.freesewing.org/uploads/charlie_on_sorcha_front_a415cd7031.jpg "Front view") diff --git a/markdown/org/showcase/charlie-on-sorcha/es.md b/markdown/org/showcase/charlie-on-sorcha/es.md new file mode 100644 index 00000000000..89c884aaa70 --- /dev/null +++ b/markdown/org/showcase/charlie-on-sorcha/es.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "A pair of Charlie Chinos on Sorcha" +date: "2021-05-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6aa91015d49712d1b56cdb3d6d56d04d372f2fab-2000x1331.jpg" +intro: "Sorcha is posing in a pair of Charlie chinos ." +title: "Charlie on Sorcha [No traducido]" +--- + +Sorcha is posing in a pair of [Charlie chinos](/designs/charlie/). + +![Back view](https://posts.freesewing.org/uploads/charlie_on_sorcha_back_0ce0ffb9bb.jpg "Back view") + +![Side view](https://posts.freesewing.org/uploads/charlie_on_sorcha_side_736bec4f5a.jpg "Side view") + +![Front view](https://posts.freesewing.org/uploads/charlie_on_sorcha_front_a415cd7031.jpg "Front view") diff --git a/markdown/org/showcase/charlie-on-sorcha/fr.md b/markdown/org/showcase/charlie-on-sorcha/fr.md new file mode 100644 index 00000000000..59bddd8a413 --- /dev/null +++ b/markdown/org/showcase/charlie-on-sorcha/fr.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "A pair of Charlie Chinos on Sorcha" +date: "2021-05-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6aa91015d49712d1b56cdb3d6d56d04d372f2fab-2000x1331.jpg" +intro: "Sorcha is posing in a pair of Charlie chinos ." +title: "[En anglais] Charlie on Sorcha" +--- + +Sorcha is posing in a pair of [Charlie chinos](/designs/charlie/). + +![Vue de derrière](https://posts.freesewing.org/uploads/charlie_on_sorcha_back_0ce0ffb9bb.jpg "Vue de derrière") + +![Side view](https://posts.freesewing.org/uploads/charlie_on_sorcha_side_736bec4f5a.jpg "Side view") + +![Front view](https://posts.freesewing.org/uploads/charlie_on_sorcha_front_a415cd7031.jpg "Front view") diff --git a/markdown/org/showcase/charlie-on-sorcha/nl.md b/markdown/org/showcase/charlie-on-sorcha/nl.md new file mode 100644 index 00000000000..7489595c3e9 --- /dev/null +++ b/markdown/org/showcase/charlie-on-sorcha/nl.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "A pair of Charlie Chinos on Sorcha" +date: "2021-05-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6aa91015d49712d1b56cdb3d6d56d04d372f2fab-2000x1331.jpg" +intro: "Sorcha is posing in a pair of Charlie chinos ." +title: "Charlie on Sorcha [Niet vertaald]" +--- + +Sorcha is posing in a pair of [Charlie chinos](/designs/charlie/). + +![Back view](https://posts.freesewing.org/uploads/charlie_on_sorcha_back_0ce0ffb9bb.jpg "Back view") + +![Side view](https://posts.freesewing.org/uploads/charlie_on_sorcha_side_736bec4f5a.jpg "Side view") + +![Front view](https://posts.freesewing.org/uploads/charlie_on_sorcha_front_a415cd7031.jpg "Front view") diff --git a/markdown/org/showcase/claire-does-sven/de.md b/markdown/org/showcase/claire-does-sven/de.md new file mode 100644 index 00000000000..2a9d5ab77e4 --- /dev/null +++ b/markdown/org/showcase/claire-does-sven/de.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Not sure what's the most adorable here. The sweater or the girl." +date: "2018-12-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/eb82ceffa42a328a5e2ffa423fe3d5d09963aa9f-3497x2134.jpg" +intro: "Claire made this Sven in a red/black striped jersey and added what we can only assume is her spirit animal." +title: "[auf Englisch] Sven by Claire" +--- + + +Claire made this Sven in a red/black striped jersey and added what we can only assume is her spirit animal. + diff --git a/markdown/org/showcase/claire-does-sven/en.md b/markdown/org/showcase/claire-does-sven/en.md new file mode 100644 index 00000000000..f80af169bcc --- /dev/null +++ b/markdown/org/showcase/claire-does-sven/en.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Not sure what's the most adorable here. The sweater or the girl." +date: "2018-12-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/eb82ceffa42a328a5e2ffa423fe3d5d09963aa9f-3497x2134.jpg" +intro: "Claire made this Sven in a red/black striped jersey and added what we can only assume is her spirit animal." +title: "Sven by Claire" +--- + + +Claire made this Sven in a red/black striped jersey and added what we can only assume is her spirit animal. + diff --git a/markdown/org/showcase/claire-does-sven/es.md b/markdown/org/showcase/claire-does-sven/es.md new file mode 100644 index 00000000000..d76ad249114 --- /dev/null +++ b/markdown/org/showcase/claire-does-sven/es.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Not sure what's the most adorable here. The sweater or the girl." +date: "2018-12-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/eb82ceffa42a328a5e2ffa423fe3d5d09963aa9f-3497x2134.jpg" +intro: "Claire made this Sven in a red/black striped jersey and added what we can only assume is her spirit animal." +title: "Sven by Claire [No traducido]" +--- + + +Claire made this Sven in a red/black striped jersey and added what we can only assume is her spirit animal. + diff --git a/markdown/org/showcase/claire-does-sven/fr.md b/markdown/org/showcase/claire-does-sven/fr.md new file mode 100644 index 00000000000..8aeffb49346 --- /dev/null +++ b/markdown/org/showcase/claire-does-sven/fr.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Dur de savoir ce qui est le plus adorable ici. Le sweat ou la fille." +date: "2018-12-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/eb82ceffa42a328a5e2ffa423fe3d5d09963aa9f-3497x2134.jpg" +intro: "Claire a fait ce Sven dans un jersey à rayures rouge/noire et a ajouté ce que nous pouvons seulement supposer est son animal spirituel." +title: "Sven par Claire" +--- + + +Claire a fait ce Sven dans un jersey à rayures rouge/noire et a ajouté ce que nous pouvons seulement supposer est son animal spirituel. + diff --git a/markdown/org/showcase/claire-does-sven/nl.md b/markdown/org/showcase/claire-does-sven/nl.md new file mode 100644 index 00000000000..0efe2937c8d --- /dev/null +++ b/markdown/org/showcase/claire-does-sven/nl.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Niet zeker wat hier het lieflijkst is. De trui of het meisje." +date: "2018-12-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/eb82ceffa42a328a5e2ffa423fe3d5d09963aa9f-3497x2134.jpg" +intro: "Claire maakte deze Sven in een rood/zwart gestreepte jersey en voegde zo te zien haar spirit animak toe." +title: "Sven door Claire" +--- + + +Claire maakte deze Sven in een rood/zwart gestreepte jersey en voegde zo te zien haar spirit animak toe. + diff --git a/markdown/org/showcase/corduroy-theo/de.md b/markdown/org/showcase/corduroy-theo/de.md new file mode 100644 index 00000000000..97f73e568bf --- /dev/null +++ b/markdown/org/showcase/corduroy-theo/de.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Gus in his brown corduroys" +date: "2017-01-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4addf70ac76582708c6aa4518028517d00dbaba2-1200x1600.jpg" +intro: "This picture is from the fabricated.com blog. You should read the entire post ." +title: "[auf Englisch] Corduroy trousers for Gus, by Fabricated" +--- + + +This picture is from the [fabricated.com](http://fabrickated.com/) blog. You should read [the entire post](http://fabrickated.com/2017/01/21/manswap-7-finishing-the-brown-corduroy-trousers/). + diff --git a/markdown/org/showcase/corduroy-theo/en.md b/markdown/org/showcase/corduroy-theo/en.md new file mode 100644 index 00000000000..5217e5dec26 --- /dev/null +++ b/markdown/org/showcase/corduroy-theo/en.md @@ -0,0 +1,13 @@ +--- +maker: "unknown" +caption: "Gus in his brown corduroys" +date: "2017-01-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4addf70ac76582708c6aa4518028517d00dbaba2-1200x1600.jpg" +intro: "Corduroy trousers for Gus, by Fabricated" +title: "Corduroy trousers for Gus, by Fabricated" +--- + + +This picture is from the [fabricated.com](http://fabrickated.com/) blog. +You should read [the entire post](http://fabrickated.com/2017/01/21/manswap-7-finishing-the-brown-corduroy-trousers/). + diff --git a/markdown/org/showcase/corduroy-theo/es.md b/markdown/org/showcase/corduroy-theo/es.md new file mode 100644 index 00000000000..1766daec118 --- /dev/null +++ b/markdown/org/showcase/corduroy-theo/es.md @@ -0,0 +1,13 @@ +--- +maker: "unknown" +caption: "Gus in his brown corduroys" +date: "2017-01-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4addf70ac76582708c6aa4518028517d00dbaba2-1200x1600.jpg" +intro: "Corduroy trousers for Gus, by Fabricated [No traducido]" +title: "Corduroy trousers for Gus, by Fabricated [No traducido]" +--- + + +This picture is from the [fabricated.com](http://fabrickated.com/) blog. +You should read [the entire post](http://fabrickated.com/2017/01/21/manswap-7-finishing-the-brown-corduroy-trousers/). + diff --git a/markdown/org/showcase/corduroy-theo/fr.md b/markdown/org/showcase/corduroy-theo/fr.md new file mode 100644 index 00000000000..0f4bb90184d --- /dev/null +++ b/markdown/org/showcase/corduroy-theo/fr.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Gus dans son pantalon Theo marron" +date: "2017-01-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4addf70ac76582708c6aa4518028517d00dbaba2-1200x1600.jpg" +intro: "Cette photo provient du site fabrikated.com . Vous devriez lire l'article entier ." +title: "Pantalon en velours côtelé pour Gus, par Fabrikated" +--- + + +Cette photo provient du site [fabrikated.com](http://fabrickated.com/). Vous devriez lire [l'article entier](http://fabrickated.com/2017/01/21/manswap-7-finishing-the-brown-corduroy-trousers/). + diff --git a/markdown/org/showcase/corduroy-theo/nl.md b/markdown/org/showcase/corduroy-theo/nl.md new file mode 100644 index 00000000000..cc39f1a0ddd --- /dev/null +++ b/markdown/org/showcase/corduroy-theo/nl.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Gus in zijn bruine ribfluweel" +date: "2017-01-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4addf70ac76582708c6aa4518028517d00dbaba2-1200x1600.jpg" +intro: "Deze foto komt van de fabricated.com blog. Je zou de hele post moeten lezen." +title: "Corduroy broek voor Gus, door Fabricated" +--- + + +Deze foto komt van de [fabricated.com](http://fabrickated.com/) blog. Je zou de [hele post](http://fabrickated.com/2017/01/21/manswap-7-finishing-the-brown-corduroy-trousers/) moeten lezen. + diff --git a/markdown/org/showcase/cornelius-by-wouter/de.md b/markdown/org/showcase/cornelius-by-wouter/de.md new file mode 100644 index 00000000000..d1d515b1d36 --- /dev/null +++ b/markdown/org/showcase/cornelius-by-wouter/de.md @@ -0,0 +1,22 @@ +--- +maker: "Wouter.vdub" +caption: "Cornelius cycling breeches by Wouter, feat. cyclist's calves" +date: "2021-03-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/abd61dc5abc173a4e858d03b5f1af80fed297957-571x613.jpg" +intro: "Wouter created the Cornelius cycling breeches pattern based on the Keystone systems. Read more on the FreeSewing blog ." +title: "[auf Englisch] Cornelius by Wouter" +--- + +Wouter created the Cornelius cycling breeches pattern based on the Keystone systems. Read more [on the FreeSewing blog](https://freesewing.org/blog/cornelius-cycling-breeches/). + +Wouter teilt auch Dinge auf [Instagram @Wouter.vdub](https://www.instagram.com/Wouter.vdub/) and [bloggt bei ShirtArtistry](https://shirtartistry.blog/). + +![View of the side](https://posts.freesewing.org/uploads/cornelius_by_wouter_cornelius2_de4bd8f66a.jpg "View of the side") + +![Eine andere Ansicht](https://posts.freesewing.org/uploads/cornelius_by_wouter_cornelius3_615eb9fce1.jpg "Eine andere Ansicht") + + + +This picture is from Wouter on Discord. It is reposted here with permission. + + diff --git a/markdown/org/showcase/cornelius-by-wouter/en.md b/markdown/org/showcase/cornelius-by-wouter/en.md new file mode 100644 index 00000000000..10ba26bf511 --- /dev/null +++ b/markdown/org/showcase/cornelius-by-wouter/en.md @@ -0,0 +1,22 @@ +--- +maker: "Wouter.vdub" +caption: "Cornelius cycling breeches by Wouter, feat. cyclist's calves" +date: "2021-03-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/abd61dc5abc173a4e858d03b5f1af80fed297957-571x613.jpg" +intro: "Wouter created the Cornelius cycling breeches pattern based on the Keystone systems. Read more on the FreeSewing blog ." +title: "Cornelius by Wouter" +--- + +Wouter created the Cornelius cycling breeches pattern based on the Keystone systems. Read more [on the FreeSewing blog](https://freesewing.org/blog/cornelius-cycling-breeches/). + +Wouter also shares on [the Instagram feed @Wouter.vdub](https://www.instagram.com/Wouter.vdub/) and [blogs at ShirtArtistry](https://shirtartistry.blog/). + +![View of the side](https://posts.freesewing.org/uploads/cornelius_by_wouter_cornelius2_de4bd8f66a.jpg "View of the side") + +![Another view](https://posts.freesewing.org/uploads/cornelius_by_wouter_cornelius3_615eb9fce1.jpg) + + + +This picture is from Wouter on Discord. It is reposted here with permission. + + diff --git a/markdown/org/showcase/cornelius-by-wouter/es.md b/markdown/org/showcase/cornelius-by-wouter/es.md new file mode 100644 index 00000000000..c1046693623 --- /dev/null +++ b/markdown/org/showcase/cornelius-by-wouter/es.md @@ -0,0 +1,22 @@ +--- +maker: "Wouter.vdub" +caption: "Cornelius cycling breeches by Wouter, feat. cyclist's calves" +date: "2021-03-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/abd61dc5abc173a4e858d03b5f1af80fed297957-571x613.jpg" +intro: "Wouter created the Cornelius cycling breeches pattern based on the Keystone systems. Read more on the FreeSewing blog ." +title: "Cornelius by Wouter [No traducido]" +--- + +Wouter created the Cornelius cycling breeches pattern based on the Keystone systems. Read more [on the FreeSewing blog](https://freesewing.org/blog/cornelius-cycling-breeches/). + +Wouter also shares on [the Instagram feed @Wouter.vdub](https://www.instagram.com/Wouter.vdub/) and [blogs at ShirtArtistry](https://shirtartistry.blog/). + +![View of the side](https://posts.freesewing.org/uploads/cornelius_by_wouter_cornelius2_de4bd8f66a.jpg "View of the side") + +![Another view](https://posts.freesewing.org/uploads/cornelius_by_wouter_cornelius3_615eb9fce1.jpg) + + + +This picture is from Wouter on Discord. It is reposted here with permission. + + diff --git a/markdown/org/showcase/cornelius-by-wouter/fr.md b/markdown/org/showcase/cornelius-by-wouter/fr.md new file mode 100644 index 00000000000..6df9d253960 --- /dev/null +++ b/markdown/org/showcase/cornelius-by-wouter/fr.md @@ -0,0 +1,22 @@ +--- +maker: "Wouter.vdub" +caption: "Cornelius cycling breeches by Wouter, feat. cyclist's calves" +date: "2021-03-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/abd61dc5abc173a4e858d03b5f1af80fed297957-571x613.jpg" +intro: "Wouter created the Cornelius cycling breeches pattern based on the Keystone systems. Read more on the FreeSewing blog ." +title: "[En anglais] Cornelius by Wouter" +--- + +Wouter created the Cornelius cycling breeches pattern based on the Keystone systems. Read more [on the FreeSewing blog](https://freesewing.org/blog/cornelius-cycling-breeches/). + +Wouter also shares on [the Instagram feed @Wouter.vdub](https://www.instagram.com/Wouter.vdub/) and [blogs at ShirtArtistry](https://shirtartistry.blog/). + +![Vue du côté](https://posts.freesewing.org/uploads/cornelius_by_wouter_cornelius2_de4bd8f66a.jpg "Vue du côté") + +![Une autre vue](https://posts.freesewing.org/uploads/cornelius_by_wouter_cornelius3_615eb9fce1.jpg "Une autre vue") + + + +Cette photo provient de Wouter sur Discord. Elle est publiée ici avec son autorisation. + + diff --git a/markdown/org/showcase/cornelius-by-wouter/nl.md b/markdown/org/showcase/cornelius-by-wouter/nl.md new file mode 100644 index 00000000000..f37d16bddea --- /dev/null +++ b/markdown/org/showcase/cornelius-by-wouter/nl.md @@ -0,0 +1,22 @@ +--- +maker: "Wouter.vdub" +caption: "Cornelius cycling breeches by Wouter, feat. cyclist's calves" +date: "2021-03-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/abd61dc5abc173a4e858d03b5f1af80fed297957-571x613.jpg" +intro: "Wouter created the Cornelius cycling breeches pattern based on the Keystone systems. Read more on the FreeSewing blog ." +title: "Cornelius by Wouter [Niet vertaald]" +--- + +Wouter created the Cornelius cycling breeches pattern based on the Keystone systems. Read more [on the FreeSewing blog](https://freesewing.org/blog/cornelius-cycling-breeches/). + +Wouter also shares on [the Instagram feed @Wouter.vdub](https://www.instagram.com/Wouter.vdub/) and [blogs at ShirtArtistry](https://shirtartistry.blog/). + +![View of the side](https://posts.freesewing.org/uploads/cornelius_by_wouter_cornelius2_de4bd8f66a.jpg "View of the side") + +![Another view](https://posts.freesewing.org/uploads/cornelius_by_wouter_cornelius3_615eb9fce1.jpg) + + + +This picture is from Wouter on Discord. It is reposted here with permission. + + diff --git a/markdown/org/showcase/fantastic-four-hugo/de.md b/markdown/org/showcase/fantastic-four-hugo/de.md new file mode 100644 index 00000000000..a9900b74502 --- /dev/null +++ b/markdown/org/showcase/fantastic-four-hugo/de.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "I'm digging this look." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4812bf0a9667224088fe258addf79f4e21ab9170-1080x1350.jpg" +intro: "This image is from the Instagram feed of Gillian ." +title: "[auf Englisch] A Fantastic Four themed Hugo" +--- + + +[This image](https://www.instagram.com/p/Beyg_MMhMH0PsSBwQkKVqMT7pObcJ0Ffb7jAAw0/?taken-by=gilliancrafts) is from [the Instagram feed of Gillian](https://www.instagram.com/gilliancrafts/). + +It is published here with permission. + diff --git a/markdown/org/showcase/fantastic-four-hugo/en.md b/markdown/org/showcase/fantastic-four-hugo/en.md new file mode 100644 index 00000000000..cd5f721768d --- /dev/null +++ b/markdown/org/showcase/fantastic-four-hugo/en.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "I'm digging this look." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4812bf0a9667224088fe258addf79f4e21ab9170-1080x1350.jpg" +intro: "This image is from the Instagram feed of Gillian ." +title: "A Fantastic Four themed Hugo" +--- + + +[This image](https://www.instagram.com/p/Beyg_MMhMH0PsSBwQkKVqMT7pObcJ0Ffb7jAAw0/?taken-by=gilliancrafts) +is from [the Instagram feed of Gillian](https://www.instagram.com/gilliancrafts/). + +It is published here with permission. + diff --git a/markdown/org/showcase/fantastic-four-hugo/es.md b/markdown/org/showcase/fantastic-four-hugo/es.md new file mode 100644 index 00000000000..571085763cd --- /dev/null +++ b/markdown/org/showcase/fantastic-four-hugo/es.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "I'm digging this look." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4812bf0a9667224088fe258addf79f4e21ab9170-1080x1350.jpg" +intro: "This image is from the Instagram feed of Gillian ." +title: "A Fantastic Four themed Hugo [No traducido]" +--- + + +[This image](https://www.instagram.com/p/Beyg_MMhMH0PsSBwQkKVqMT7pObcJ0Ffb7jAAw0/?taken-by=gilliancrafts) +is from [the Instagram feed of Gillian](https://www.instagram.com/gilliancrafts/). + +It is published here with permission. + diff --git a/markdown/org/showcase/fantastic-four-hugo/fr.md b/markdown/org/showcase/fantastic-four-hugo/fr.md new file mode 100644 index 00000000000..b980bf321f4 --- /dev/null +++ b/markdown/org/showcase/fantastic-four-hugo/fr.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Je creuse ce look." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4812bf0a9667224088fe258addf79f4e21ab9170-1080x1350.jpg" +intro: "Cette photo provient du feed Instagram de Gillian ." +title: "Un Hugo sur le thème des quatre fantastiques" +--- + + +[Cette photo](https://www.instagram.com/p/Beyg_MMhMH0PsSBwQkKVqMT7pObcJ0Ffb7jAAw0/?taken-by=gilliancrafts) provient du [feed Instagram de Gillian](https://www.instagram.com/gilliancrafts/). + +Elle est publiée ici avec son autorisation. + diff --git a/markdown/org/showcase/fantastic-four-hugo/nl.md b/markdown/org/showcase/fantastic-four-hugo/nl.md new file mode 100644 index 00000000000..67782672d14 --- /dev/null +++ b/markdown/org/showcase/fantastic-four-hugo/nl.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Dit zie ik wel zitten." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4812bf0a9667224088fe258addf79f4e21ab9170-1080x1350.jpg" +intro: "Deze afbeelding komt van de Instagram feed van Gillian ." +title: "Een Fantastic Four Hugo" +--- + + +[Deze afbeelding](https://www.instagram.com/p/Beyg_MMhMH0PsSBwQkKVqMT7pObcJ0Ffb7jAAw0/?taken-by=gilliancrafts) komt van [de Instagram feed van Gillian](https://www.instagram.com/gilliancrafts/). + +Ze werd hier gepost met toestemming. + diff --git a/markdown/org/showcase/fighter-hoodie/de.md b/markdown/org/showcase/fighter-hoodie/de.md new file mode 100644 index 00000000000..b1abfbb6d83 --- /dev/null +++ b/markdown/org/showcase/fighter-hoodie/de.md @@ -0,0 +1,26 @@ +--- +maker: "unknown" +caption: "Anne's husband Sigvard is a trainer at the local kick boxing club. Hence the name fighter hoodie" +date: "2017-11-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8f0b0ca919900145250b0af08401775198623eda-1001x1500.jpg" +intro: "[auf Englisch] The fighter hoodie: Hugo with a zip" +title: "[auf Englisch] The fighter hoodie: Hugo with a zip" +--- + +![Another view](https://posts.freesewing.org/uploads/fighter_hoodie_1_69359b6e7d.jpg "Another view") + +![Another view](https://posts.freesewing.org/uploads/fighter_hoodie_2_c74c303646.jpg "Another view") + +![Another view](https://posts.freesewing.org/uploads/fighter_hoodie_3_f8766d848b.jpg "Another view") + +![Another view](https://posts.freesewing.org/uploads/fighter_hoodie_4_881e549c9b.jpg "Another view") + + + +###### See the original on [@Topstitched](/users/Topstitched)'s blog +These picture are from the [Back again with the fighter hoodie](http://www.topstitched.net/?p=1431) +blog post on [topstitched.net](http://www.topstitched.net/). + +They are reposted here with permission. + + diff --git a/markdown/org/showcase/fighter-hoodie/en.md b/markdown/org/showcase/fighter-hoodie/en.md new file mode 100644 index 00000000000..0108d1dbc97 --- /dev/null +++ b/markdown/org/showcase/fighter-hoodie/en.md @@ -0,0 +1,26 @@ +--- +maker: "unknown" +caption: "Anne's husband Sigvard is a trainer at the local kick boxing club. Hence the name fighter hoodie" +date: "2017-11-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8f0b0ca919900145250b0af08401775198623eda-1001x1500.jpg" +intro: "The fighter hoodie: Hugo with a zip" +title: "The fighter hoodie: Hugo with a zip" +--- + +![Another view](https://posts.freesewing.org/uploads/fighter_hoodie_1_69359b6e7d.jpg "Another view") + +![Another view](https://posts.freesewing.org/uploads/fighter_hoodie_2_c74c303646.jpg) + +![Another view](https://posts.freesewing.org/uploads/fighter_hoodie_3_f8766d848b.jpg) + +![Another view](https://posts.freesewing.org/uploads/fighter_hoodie_4_881e549c9b.jpg) + + + +###### See the original on [@Topstitched](/users/Topstitched)'s blog +These picture are from the [Back again with the fighter hoodie](http://www.topstitched.net/?p=1431) +blog post on [topstitched.net](http://www.topstitched.net/). + +They are reposted here with permission. + + diff --git a/markdown/org/showcase/fighter-hoodie/es.md b/markdown/org/showcase/fighter-hoodie/es.md new file mode 100644 index 00000000000..1e7336ee6cd --- /dev/null +++ b/markdown/org/showcase/fighter-hoodie/es.md @@ -0,0 +1,26 @@ +--- +maker: "unknown" +caption: "Anne's husband Sigvard is a trainer at the local kick boxing club. Hence the name fighter hoodie" +date: "2017-11-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8f0b0ca919900145250b0af08401775198623eda-1001x1500.jpg" +intro: "The fighter hoodie: Hugo with a zip [No traducido]" +title: "The fighter hoodie: Hugo with a zip [No traducido]" +--- + +![Another view](https://posts.freesewing.org/uploads/fighter_hoodie_1_69359b6e7d.jpg "Another view") + +![Another view](https://posts.freesewing.org/uploads/fighter_hoodie_2_c74c303646.jpg) + +![Another view](https://posts.freesewing.org/uploads/fighter_hoodie_3_f8766d848b.jpg) + +![Another view](https://posts.freesewing.org/uploads/fighter_hoodie_4_881e549c9b.jpg) + + + +###### See the original on [@Topstitched](/users/Topstitched)'s blog +These picture are from the [Back again with the fighter hoodie](http://www.topstitched.net/?p=1431) +blog post on [topstitched.net](http://www.topstitched.net/). + +They are reposted here with permission. + + diff --git a/markdown/org/showcase/fighter-hoodie/fr.md b/markdown/org/showcase/fighter-hoodie/fr.md new file mode 100644 index 00000000000..04afeb0c6cb --- /dev/null +++ b/markdown/org/showcase/fighter-hoodie/fr.md @@ -0,0 +1,26 @@ +--- +maker: "unknown" +caption: "Anne's husband Sigvard is a trainer at the local kick boxing club. Hence the name fighter hoodie" +date: "2017-11-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8f0b0ca919900145250b0af08401775198623eda-1001x1500.jpg" +intro: "[En anglais] The fighter hoodie: Hugo with a zip" +title: "[En anglais] The fighter hoodie: Hugo with a zip" +--- + +![Another view](https://posts.freesewing.org/uploads/fighter_hoodie_1_69359b6e7d.jpg "Another view") + +![Another view](2.jpg) + +![Another view](3.jpg) + +![Another view](4.jpg) + + + +###### See the original on [@Topstitched](/users/Topstitched)'s blog +These picture are from the [Back again with the fighter hoodie](http://www.topstitched.net/?p=1431) +blog post on [topstitched.net](http://www.topstitched.net/). + +They are reposted here with permission. + + diff --git a/markdown/org/showcase/fighter-hoodie/nl.md b/markdown/org/showcase/fighter-hoodie/nl.md new file mode 100644 index 00000000000..43162d625e6 --- /dev/null +++ b/markdown/org/showcase/fighter-hoodie/nl.md @@ -0,0 +1,26 @@ +--- +maker: "unknown" +caption: "Anne's echtgenoot Sigvard is een trainer bij de lokale kickboksclub. Vandaar de naam gevechtshoodie" +date: "2017-11-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8f0b0ca919900145250b0af08401775198623eda-1001x1500.jpg" +intro: "Een gevechtshoodie: Hugo met een rits" +title: "Een gevechtshoodie: Hugo met een rits" +--- + +![Een andere kant](https://posts.freesewing.org/uploads/fighter_hoodie_1_69359b6e7d.jpg "Een andere kant") + +![Een andere kant](https://posts.freesewing.org/uploads/fighter_hoodie_2_c74c303646.jpg "Een andere kant") + +![Een andere kant](https://posts.freesewing.org/uploads/fighter_hoodie_3_f8766d848b.jpg "Een andere kant") + +![Een andere kant](4.jpg) + + + +###### See the original on [@Topstitched](/users/Topstitched)'s blog +These picture are from the [Back again with the fighter hoodie](http://www.topstitched.net/?p=1431) +blog post on [topstitched.net](http://www.topstitched.net/). + +Ze werden hier gepost met toestemming. + + diff --git a/markdown/org/showcase/florence-jv/de.md b/markdown/org/showcase/florence-jv/de.md new file mode 100644 index 00000000000..dbbd057a951 --- /dev/null +++ b/markdown/org/showcase/florence-jv/de.md @@ -0,0 +1,12 @@ +--- +maker: "RedBlaqueGolden" +caption: "Not all face masks are created equal" +date: "2020-07-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a5256f3dc2e94bbcaa08f48cb20a072f45d1c95e-1536x1153.jpg" +intro: "JV is a prolific maker and a friend of the site. True to form, they made this stunning Florence face mask." +title: "[auf Englisch] JV does Florence" +--- + + +JV is a prolific maker and a friend of the site. True to form, they made this stunning Florence face mask. + diff --git a/markdown/org/showcase/florence-jv/en.md b/markdown/org/showcase/florence-jv/en.md new file mode 100644 index 00000000000..ed5d07b13fa --- /dev/null +++ b/markdown/org/showcase/florence-jv/en.md @@ -0,0 +1,12 @@ +--- +maker: "RedBlaqueGolden" +caption: "Not all face masks are created equal" +date: "2020-07-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a5256f3dc2e94bbcaa08f48cb20a072f45d1c95e-1536x1153.jpg" +intro: "JV is a prolific maker and a friend of the site. True to form, they made this stunning Florence face mask." +title: "JV does Florence" +--- + + +JV is a prolific maker and a friend of the site. True to form, they made this stunning Florence face mask. + diff --git a/markdown/org/showcase/florence-jv/es.md b/markdown/org/showcase/florence-jv/es.md new file mode 100644 index 00000000000..d6f4b76cad9 --- /dev/null +++ b/markdown/org/showcase/florence-jv/es.md @@ -0,0 +1,12 @@ +--- +maker: "RedBlaqueGolden" +caption: "Not all face masks are created equal" +date: "2020-07-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a5256f3dc2e94bbcaa08f48cb20a072f45d1c95e-1536x1153.jpg" +intro: "JV is a prolific maker and a friend of the site. True to form, they made this stunning Florence face mask." +title: "JV does Florence [No traducido]" +--- + + +JV is a prolific maker and a friend of the site. True to form, they made this stunning Florence face mask. + diff --git a/markdown/org/showcase/florence-jv/fr.md b/markdown/org/showcase/florence-jv/fr.md new file mode 100644 index 00000000000..d7d31d0a55f --- /dev/null +++ b/markdown/org/showcase/florence-jv/fr.md @@ -0,0 +1,12 @@ +--- +maker: "RedBlaqueGolden" +caption: "Tous les masques ne sont pas réalisés de la même manière" +date: "2020-07-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a5256f3dc2e94bbcaa08f48cb20a072f45d1c95e-1536x1153.jpg" +intro: "JV est un couturier prolifique et un ami du site. Fidèle à sa forme, il a fait un masque Florence stupéfiant." +title: "JV fait Florence" +--- + + +JV est un couturier prolifique et un ami du site. Fidèle à sa forme, il a fait un masque Florence stupéfiant. + diff --git a/markdown/org/showcase/florence-jv/nl.md b/markdown/org/showcase/florence-jv/nl.md new file mode 100644 index 00000000000..422853c517f --- /dev/null +++ b/markdown/org/showcase/florence-jv/nl.md @@ -0,0 +1,12 @@ +--- +maker: "RedBlaqueGolden" +caption: "Not all face masks are created equal" +date: "2020-07-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a5256f3dc2e94bbcaa08f48cb20a072f45d1c95e-1536x1153.jpg" +intro: "JV is a prolific maker and a friend of the site. True to form, they made this stunning Florence face mask." +title: "JV does Florence [Niet vertaald]" +--- + + +JV is a prolific maker and a friend of the site. True to form, they made this stunning Florence face mask. + diff --git a/markdown/org/showcase/florence/de.md b/markdown/org/showcase/florence/de.md new file mode 100644 index 00000000000..c7b7ac0c3db --- /dev/null +++ b/markdown/org/showcase/florence/de.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "There's so many people who made our face mask, here's just a few of them" +date: "2020-07-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/85f06378981db4e6769579d583b5361e5b8b6e46-2000x1200.jpg" +intro: "When we published our face mask in February, we did not anticipate that it would blow up the way it did." +title: "[auf Englisch] Various Florence makers" +--- + + +When we published our face mask in February, we did not anticipate that it would blow up the way it did. + +Countless of people have made our mask, and in the avalange of questions and feedback, we haven't really kept trach of who did what. + +Above is selection of people who shared their makes with us on social media. +Thanks to all of them for doing so, and please do the same if you'd like us to showcase your makes. + diff --git a/markdown/org/showcase/florence/en.md b/markdown/org/showcase/florence/en.md new file mode 100644 index 00000000000..a357066de10 --- /dev/null +++ b/markdown/org/showcase/florence/en.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "There's so many people who made our face mask, here's just a few of them" +date: "2020-07-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/85f06378981db4e6769579d583b5361e5b8b6e46-2000x1200.jpg" +intro: "When we published our face mask in February, we did not anticipate that it would blow up the way it did." +title: "Various Florence makers" +--- + + +When we published our face mask in February, we did not anticipate that it would blow up the way it did. + +Countless of people have made our mask, and in the avalange of questions and feedback, we haven't really +kept trach of who did what. + +Above is selection of people who shared their makes with us on social media. +Thanks to all of them for doing so, and please do the same if you'd like us to showcase your makes. + diff --git a/markdown/org/showcase/florence/es.md b/markdown/org/showcase/florence/es.md new file mode 100644 index 00000000000..921bcd02635 --- /dev/null +++ b/markdown/org/showcase/florence/es.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "There's so many people who made our face mask, here's just a few of them" +date: "2020-07-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/85f06378981db4e6769579d583b5361e5b8b6e46-2000x1200.jpg" +intro: "When we published our face mask in February, we did not anticipate that it would blow up the way it did." +title: "Various Florence makers [No traducido]" +--- + + +When we published our face mask in February, we did not anticipate that it would blow up the way it did. + +Countless of people have made our mask, and in the avalange of questions and feedback, we haven't really +kept trach of who did what. + +Above is selection of people who shared their makes with us on social media. +Thanks to all of them for doing so, and please do the same if you'd like us to showcase your makes. + diff --git a/markdown/org/showcase/florence/fr.md b/markdown/org/showcase/florence/fr.md new file mode 100644 index 00000000000..feed801e1d1 --- /dev/null +++ b/markdown/org/showcase/florence/fr.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Il y a tellement de personnes qui ont fabriqué notre masque facial, voici quelques-unes d'entre elles" +date: "2020-07-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/85f06378981db4e6769579d583b5361e5b8b6e46-2000x1200.jpg" +intro: "Lorsque nous avons publié notre masque en février, nous ne nous attendions pas à ce qu'il explose comme il l'a fait." +title: "Diverses réalisations de Florence" +--- + + +Lorsque nous avons publié notre masque en février, nous ne nous attendions pas à ce qu'il explose comme il l'a fait. + +De nombreuses personnes ont fait de notre masque, et dans l'avalanche de questions et de retours, nous n'avons pas vraiment gardé la trace de qui a fait quoi. + +Ci-dessus se trouve la sélection de personnes qui ont partagé leurs marques avec nous sur les réseaux sociaux. +Merci à tous de l'avoir fait, et s'il vous plaît faites la même chose si vous souhaitez que nous présentions vos réalisations. + diff --git a/markdown/org/showcase/florence/nl.md b/markdown/org/showcase/florence/nl.md new file mode 100644 index 00000000000..5d6f8d38d86 --- /dev/null +++ b/markdown/org/showcase/florence/nl.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "There's so many people who made our face mask, here's just a few of them" +date: "2020-07-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/85f06378981db4e6769579d583b5361e5b8b6e46-2000x1200.jpg" +intro: "When we published our face mask in February, we did not anticipate that it would blow up the way it did." +title: "Various Florence makers [Niet vertaald]" +--- + + +When we published our face mask in February, we did not anticipate that it would blow up the way it did. + +Countless of people have made our mask, and in the avalange of questions and feedback, we haven't really +kept trach of who did what. + +Above is selection of people who shared their makes with us on social media. +Thanks to all of them for doing so, and please do the same if you'd like us to showcase your makes. + diff --git a/markdown/org/showcase/florent-by-enno/de.md b/markdown/org/showcase/florent-by-enno/de.md new file mode 100644 index 00000000000..f78d6cc41d8 --- /dev/null +++ b/markdown/org/showcase/florent-by-enno/de.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Enno made this Florent in a gorgeous mustard" +date: "2019-03-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a5b79cac257f7193ffd73aaea0c5a3834d4fd668-1080x1080.jpg" +intro: "Enno's got a vest to go with it too:" +title: "[auf Englisch] Florent by Enno" +--- + +Enno's got a vest to go with it too: + +![Cap and vest](https://posts.freesewing.org/uploads/florent_by_enno_2_c5ac858005.jpg "Cap and vest") diff --git a/markdown/org/showcase/florent-by-enno/en.md b/markdown/org/showcase/florent-by-enno/en.md new file mode 100644 index 00000000000..a968f1347ab --- /dev/null +++ b/markdown/org/showcase/florent-by-enno/en.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Enno made this Florent in a gorgeous mustard" +date: "2019-03-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a5b79cac257f7193ffd73aaea0c5a3834d4fd668-1080x1080.jpg" +intro: "Enno's got a vest to go with it too:" +title: "Florent by Enno" +--- + +Enno's got a vest to go with it too: + +![Cap and vest](https://posts.freesewing.org/uploads/florent_by_enno_2_c5ac858005.jpg "Cap and vest") diff --git a/markdown/org/showcase/florent-by-enno/es.md b/markdown/org/showcase/florent-by-enno/es.md new file mode 100644 index 00000000000..bb864b3ad0d --- /dev/null +++ b/markdown/org/showcase/florent-by-enno/es.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Enno made this Florent in a gorgeous mustard" +date: "2019-03-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a5b79cac257f7193ffd73aaea0c5a3834d4fd668-1080x1080.jpg" +intro: "Enno's got a vest to go with it too:" +title: "Florent by Enno [No traducido]" +--- + +Enno's got a vest to go with it too: + +![Cap and vest](https://posts.freesewing.org/uploads/florent_by_enno_2_c5ac858005.jpg "Cap and vest") diff --git a/markdown/org/showcase/florent-by-enno/fr.md b/markdown/org/showcase/florent-by-enno/fr.md new file mode 100644 index 00000000000..7dfe77e2c81 --- /dev/null +++ b/markdown/org/showcase/florent-by-enno/fr.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Enno a fait ce Florent dans un magnifique moutarde" +date: "2019-03-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a5b79cac257f7193ffd73aaea0c5a3834d4fd668-1080x1080.jpg" +intro: "Enno a aussi une veste pour l'accompagner :" +title: "Florent par Enno" +--- + +Enno a aussi une veste pour l'accompagner : + +![Casquette et veste](https://posts.freesewing.org/uploads/florent_by_enno_2_c5ac858005.jpg "Casquette et veste") diff --git a/markdown/org/showcase/florent-by-enno/nl.md b/markdown/org/showcase/florent-by-enno/nl.md new file mode 100644 index 00000000000..ca4dc23c69c --- /dev/null +++ b/markdown/org/showcase/florent-by-enno/nl.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Enno made this Florent in a gorgeous mustard" +date: "2019-03-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a5b79cac257f7193ffd73aaea0c5a3834d4fd668-1080x1080.jpg" +intro: "Enno's got a vest to go with it too:" +title: "Florent by Enno [Niet vertaald]" +--- + +Enno's got a vest to go with it too: + +![Cap and vest](https://posts.freesewing.org/uploads/florent_by_enno_2_c5ac858005.jpg "Cap and vest") diff --git a/markdown/org/showcase/florent-by-michele/de.md b/markdown/org/showcase/florent-by-michele/de.md new file mode 100644 index 00000000000..c996c4af913 --- /dev/null +++ b/markdown/org/showcase/florent-by-michele/de.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "A green Florent by Michele Nel" +date: "2017-12-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/210ddaa1ecb0afad4260d6c60627be34e46189d0-1280x960.jpg" +intro: " " +title: "[auf Englisch] Florent by Michele Nel" +--- + +![Eine andere Ansicht](https://posts.freesewing.org/uploads/florent_by_michele_24_24a438f855.jpg "Eine andere Ansicht") +![Eine andere Ansicht](https://posts.freesewing.org/uploads/florent_by_michele_25_e4e2c3a34b.jpg "Eine andere Ansicht") +![Eine andere Ansicht](https://posts.freesewing.org/uploads/florent_by_michele_27_43ced160e7.jpg "Eine andere Ansicht") +![Eine andere Ansicht](https://posts.freesewing.org/uploads/florent_by_michele_31_b665c3dc5b.jpg "Eine andere Ansicht") +![Eine andere Ansicht](https://posts.freesewing.org/uploads/florent_by_michele_38_e8e8777f34.jpg "Eine andere Ansicht") +![Eine andere Ansicht](https://posts.freesewing.org/uploads/florent_by_michele_43_9a583f3648.jpg "Eine andere Ansicht") +![Eine andere Ansicht](https://posts.freesewing.org/uploads/florent_by_michele_46_c480c6a1a9.jpg "Eine andere Ansicht") diff --git a/markdown/org/showcase/florent-by-michele/en.md b/markdown/org/showcase/florent-by-michele/en.md new file mode 100644 index 00000000000..987025eabea --- /dev/null +++ b/markdown/org/showcase/florent-by-michele/en.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "A green Florent by Michele Nel" +date: "2017-12-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/210ddaa1ecb0afad4260d6c60627be34e46189d0-1280x960.jpg" +intro: " " +title: "Florent by Michele Nel" +--- + +![Another view](https://posts.freesewing.org/uploads/florent_by_michele_24_24a438f855.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/florent_by_michele_25_e4e2c3a34b.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/florent_by_michele_27_43ced160e7.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/florent_by_michele_31_b665c3dc5b.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/florent_by_michele_38_e8e8777f34.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/florent_by_michele_43_9a583f3648.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/florent_by_michele_46_c480c6a1a9.jpg) diff --git a/markdown/org/showcase/florent-by-michele/es.md b/markdown/org/showcase/florent-by-michele/es.md new file mode 100644 index 00000000000..c502d802f84 --- /dev/null +++ b/markdown/org/showcase/florent-by-michele/es.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "A green Florent by Michele Nel" +date: "2017-12-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/210ddaa1ecb0afad4260d6c60627be34e46189d0-1280x960.jpg" +intro: " " +title: "Florent by Michele Nel [No traducido]" +--- + +![Another view](https://posts.freesewing.org/uploads/florent_by_michele_24_24a438f855.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/florent_by_michele_25_e4e2c3a34b.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/florent_by_michele_27_43ced160e7.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/florent_by_michele_31_b665c3dc5b.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/florent_by_michele_38_e8e8777f34.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/florent_by_michele_43_9a583f3648.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/florent_by_michele_46_c480c6a1a9.jpg) diff --git a/markdown/org/showcase/florent-by-michele/fr.md b/markdown/org/showcase/florent-by-michele/fr.md new file mode 100644 index 00000000000..5365bbbdf78 --- /dev/null +++ b/markdown/org/showcase/florent-by-michele/fr.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Un Florent vert de Michele Nel" +date: "2017-12-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/210ddaa1ecb0afad4260d6c60627be34e46189d0-1280x960.jpg" +intro: " " +title: "Florent par Michele Nel" +--- + +![Une autre vue](https://posts.freesewing.org/uploads/florent_by_michele_24_24a438f855.jpg "Une autre vue") +![Une autre vue](https://posts.freesewing.org/uploads/florent_by_michele_25_e4e2c3a34b.jpg "Une autre vue") +![Une autre vue](https://posts.freesewing.org/uploads/florent_by_michele_27_43ced160e7.jpg "Une autre vue") +![Une autre vue](https://posts.freesewing.org/uploads/florent_by_michele_31_b665c3dc5b.jpg "Une autre vue") +![Une autre vue](https://posts.freesewing.org/uploads/florent_by_michele_38_e8e8777f34.jpg "Une autre vue") +![Une autre vue](https://posts.freesewing.org/uploads/florent_by_michele_43_9a583f3648.jpg "Une autre vue") +![Une autre vue](https://posts.freesewing.org/uploads/florent_by_michele_46_c480c6a1a9.jpg "Une autre vue") + diff --git a/markdown/org/showcase/florent-by-michele/nl.md b/markdown/org/showcase/florent-by-michele/nl.md new file mode 100644 index 00000000000..66e0d890302 --- /dev/null +++ b/markdown/org/showcase/florent-by-michele/nl.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "Een groene Florent door Michele Nel" +date: "2017-12-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/210ddaa1ecb0afad4260d6c60627be34e46189d0-1280x960.jpg" +intro: " " +title: "Florent door Michele Nel" +--- + +![Een ander zicht](https://posts.freesewing.org/uploads/florent_by_michele_24_24a438f855.jpg "Een ander zicht") +![Een ander zicht](https://posts.freesewing.org/uploads/florent_by_michele_25_e4e2c3a34b.jpg "Een ander zicht") +![Een ander zicht](https://posts.freesewing.org/uploads/florent_by_michele_27_43ced160e7.jpg "Een ander zicht") +![Een ander zicht](https://posts.freesewing.org/uploads/florent_by_michele_31_b665c3dc5b.jpg "Een ander zicht") +![Een ander zicht](https://posts.freesewing.org/uploads/florent_by_michele_38_e8e8777f34.jpg "Een ander zicht") +![Een ander zicht](https://posts.freesewing.org/uploads/florent_by_michele_43_9a583f3648.jpg "Een ander zicht") +![Een ander zicht](https://posts.freesewing.org/uploads/florent_by_michele_46_c480c6a1a9.jpg "Een ander zicht") diff --git a/markdown/org/showcase/florent-by-wim/de.md b/markdown/org/showcase/florent-by-wim/de.md new file mode 100644 index 00000000000..a0975f7b99a --- /dev/null +++ b/markdown/org/showcase/florent-by-wim/de.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Florent flat cap" +date: "2018-09-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/05241effbb4966cca830512f81b1910e7ecf46f8-1094x889.jpg" +intro: "Here's Wim with a Florent flap cap." +title: "[auf Englisch] A Florent flat cap by Wim" +--- + +Here's Wim with a Florent flap cap. + + +![Another picture from this Florent](https://posts.freesewing.org/uploads/florent_by_wim_2_fd067a2d8c.jpg "Another picture from this Florent") + +![Another picture from this Florent](https://posts.freesewing.org/uploads/florent_by_wim_3_add715829e.jpg "Another picture from this Florent") diff --git a/markdown/org/showcase/florent-by-wim/en.md b/markdown/org/showcase/florent-by-wim/en.md new file mode 100644 index 00000000000..9a4c53b187f --- /dev/null +++ b/markdown/org/showcase/florent-by-wim/en.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Florent flat cap" +date: "2018-09-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/05241effbb4966cca830512f81b1910e7ecf46f8-1094x889.jpg" +intro: "Here's Wim with a Florent flap cap." +title: "A Florent flat cap by Wim" +--- + +Here's Wim with a Florent flap cap. + + +![Another picture from this Florent](https://posts.freesewing.org/uploads/florent_by_wim_2_fd067a2d8c.jpg "Another picture from this Florent") + +![Another picture from this Florent](https://posts.freesewing.org/uploads/florent_by_wim_3_add715829e.jpg) diff --git a/markdown/org/showcase/florent-by-wim/es.md b/markdown/org/showcase/florent-by-wim/es.md new file mode 100644 index 00000000000..de01fba7530 --- /dev/null +++ b/markdown/org/showcase/florent-by-wim/es.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Florent flat cap" +date: "2018-09-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/05241effbb4966cca830512f81b1910e7ecf46f8-1094x889.jpg" +intro: "Here's Wim with a Florent flap cap." +title: "A Florent flat cap by Wim [No traducido]" +--- + +Here's Wim with a Florent flap cap. + + +![Another picture from this Florent](https://posts.freesewing.org/uploads/florent_by_wim_2_fd067a2d8c.jpg "Another picture from this Florent") + +![Another picture from this Florent](https://posts.freesewing.org/uploads/florent_by_wim_3_add715829e.jpg) diff --git a/markdown/org/showcase/florent-by-wim/fr.md b/markdown/org/showcase/florent-by-wim/fr.md new file mode 100644 index 00000000000..7d74c2ccdaf --- /dev/null +++ b/markdown/org/showcase/florent-by-wim/fr.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Casquette plate Florent" +date: "2018-09-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/05241effbb4966cca830512f81b1910e7ecf46f8-1094x889.jpg" +intro: "Voici Wim avec une casquette plate Florent." +title: "Un casquette plate Florent par Wim" +--- + +Voici Wim avec une casquette plate Florent. + + +![Une autre photo de ce Florent](https://posts.freesewing.org/uploads/florent_by_wim_2_fd067a2d8c.jpg "Une autre photo de ce Florent") + +![Une autre photo de ce Florent](3.jpg) diff --git a/markdown/org/showcase/florent-by-wim/nl.md b/markdown/org/showcase/florent-by-wim/nl.md new file mode 100644 index 00000000000..174eab23057 --- /dev/null +++ b/markdown/org/showcase/florent-by-wim/nl.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Florent pet" +date: "2018-09-21" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/05241effbb4966cca830512f81b1910e7ecf46f8-1094x889.jpg" +intro: "Hier is Wim met een Florent pet." +title: "Een Florent pet door Wim" +--- + +Hier is Wim met een Florent pet. + + +![Nog een foto van deze Florent](https://posts.freesewing.org/uploads/florent_by_wim_2_fd067a2d8c.jpg "Nog een foto van deze Florent") + +![Nog een foto van deze Florent](3.jpg) diff --git a/markdown/org/showcase/florent-by-wouter/de.md b/markdown/org/showcase/florent-by-wouter/de.md new file mode 100644 index 00000000000..532472ac12c --- /dev/null +++ b/markdown/org/showcase/florent-by-wouter/de.md @@ -0,0 +1,16 @@ +--- +maker: "Wouter.vdub" +caption: "Turned out really well for a toile" +date: "2017-12-11" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f3126799846dc9ea9aecb423e7283bb715db93b4-3724x2785.jpg" +intro: "[auf Englisch] A test of Florent to see if the pattern works for others, by Wouter.vdub" +title: "[auf Englisch] A test of Florent to see if the pattern works for others, by Wouter.vdub" +--- + +![View of the front](https://posts.freesewing.org/uploads/florent_by_wouter_high_back_20ec93b7c1.jpg "View of the front") + +Wouter writes: + +> This was made as a toile, and although precision was used, some aspects could have been improved by using hand stitching, instead of machine stitching. +> +> Also, the pattern was printed with the standard `ease` of 1cm, and that was taken in at the back seam after the pieces were cut out. diff --git a/markdown/org/showcase/florent-by-wouter/en.md b/markdown/org/showcase/florent-by-wouter/en.md new file mode 100644 index 00000000000..ab6476b0b80 --- /dev/null +++ b/markdown/org/showcase/florent-by-wouter/en.md @@ -0,0 +1,19 @@ +--- +maker: "Wouter.vdub" +caption: "Turned out really well for a toile" +date: "2017-12-11" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f3126799846dc9ea9aecb423e7283bb715db93b4-3724x2785.jpg" +intro: "A test of Florent to see if the pattern works for others, by Wouter.vdub" +title: "A test of Florent to see if the pattern works for others, by Wouter.vdub" +--- + +![View of the back ](https://posts.freesewing.org/uploads/florent_by_wouter_high_back_20ec93b7c1.jpg "View of the back ") +![View of the front](https://posts.freesewing.org/uploads/florent_by_wouter_high_front_9f28a1eb39.jpg "View of the front") + +Wouter writes: + +> This was made as a toile, and although precision was used, some aspects could +> have been improved by using hand stitching, instead of machine stitching. +> +> Also, the pattern was printed with the standard `ease` of 1cm, and that +> was taken in at the back seam after the pieces were cut out. diff --git a/markdown/org/showcase/florent-by-wouter/es.md b/markdown/org/showcase/florent-by-wouter/es.md new file mode 100644 index 00000000000..c69143f1d1f --- /dev/null +++ b/markdown/org/showcase/florent-by-wouter/es.md @@ -0,0 +1,19 @@ +--- +maker: "Wouter.vdub" +caption: "Turned out really well for a toile" +date: "2017-12-11" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f3126799846dc9ea9aecb423e7283bb715db93b4-3724x2785.jpg" +intro: "A test of Florent to see if the pattern works for others, by Wouter.vdub [No traducido]" +title: "A test of Florent to see if the pattern works for others, by Wouter.vdub [No traducido]" +--- + +![View of the back ](https://posts.freesewing.org/uploads/florent_by_wouter_high_back_20ec93b7c1.jpg "View of the back ") +![View of the front](https://posts.freesewing.org/uploads/florent_by_wouter_high_front_9f28a1eb39.jpg "View of the front") + +Wouter writes: + +> This was made as a toile, and although precision was used, some aspects could +> have been improved by using hand stitching, instead of machine stitching. +> +> Also, the pattern was printed with the standard `ease` of 1cm, and that +> was taken in at the back seam after the pieces were cut out. diff --git a/markdown/org/showcase/florent-by-wouter/fr.md b/markdown/org/showcase/florent-by-wouter/fr.md new file mode 100644 index 00000000000..890338ff6d3 --- /dev/null +++ b/markdown/org/showcase/florent-by-wouter/fr.md @@ -0,0 +1,16 @@ +--- +maker: "Wouter.vdub" +caption: "Très bon résultat pour une toile" +date: "2017-12-11" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f3126799846dc9ea9aecb423e7283bb715db93b4-3724x2785.jpg" +intro: "Un test de Florent pour voir si le patron fonctionne pour les autres, par Wouter.vdub" +title: "Un test de Florent pour voir si le patron fonctionne pour les autres, par Wouter.vdub" +--- + +![Photo de l'avant](https://posts.freesewing.org/uploads/florent_by_wouter_high_back_20ec93b7c1.jpg "Photo de l'avant") + +Wouter écrit : + +> Cela a été réalisé en tant que toile, et bien que la précision ait été de mise, certains aspects auraient pu être améliorés en utilisant des points à la main, au lieu de coudre à la machine. +> +> De plus, le patron a été imprimé avec la marge`standard` de 1 cm, et cela a été pris dans la couture arrière après que les morceaux aient été découpés. diff --git a/markdown/org/showcase/florent-by-wouter/nl.md b/markdown/org/showcase/florent-by-wouter/nl.md new file mode 100644 index 00000000000..5a9d887fdcd --- /dev/null +++ b/markdown/org/showcase/florent-by-wouter/nl.md @@ -0,0 +1,16 @@ +--- +maker: "Wouter.vdub" +caption: "Heel goed gelukt voor een toile" +date: "2017-12-11" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f3126799846dc9ea9aecb423e7283bb715db93b4-3724x2785.jpg" +intro: "Een testversie van Florent om te zien of het patroon voor anderen werkt, door Wouter.vdub" +title: "Een testversie van Florent om te zien of het patroon voor anderen werkt, door Wouter.vdub" +--- + +![Zicht op de voorkant](https://posts.freesewing.org/uploads/florent_by_wouter_high_back_20ec93b7c1.jpg "Zicht op de voorkant") + +Wouter schrijft: + +> Dit was gemaakt als een toile, en alhoewel ik precies werkte hadden sommige stukken beter gekund door ze met de hand te doen in plaats van met de machine. +> +> Het patroon was ook geprint met de standaard `overwijdte` van 1 cm, en die werd in de achternaad weer ingenomen nadat de stukken uitgeknipt waren. diff --git a/markdown/org/showcase/french-terry-sven/de.md b/markdown/org/showcase/french-terry-sven/de.md new file mode 100644 index 00000000000..4e3fc4e6c44 --- /dev/null +++ b/markdown/org/showcase/french-terry-sven/de.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "The model is totally walking away with it though." +date: "2017-10-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fd444e514ea1ec6a2e2830b0a17bbc044f18a702-683x854.jpg" +intro: "This post is originally appeared on the Instagram feed of nadesmakes ." +title: "[auf Englisch] The Sven sweater in a French Terry with little to no stretch" +--- + + +This post is [originally appeared](https://www.instagram.com/p/BaBqKDtDelP/) on [the Instagram feed of nadesmakes](https://www.instagram.com/nadesmakes/). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/french-terry-sven/en.md b/markdown/org/showcase/french-terry-sven/en.md new file mode 100644 index 00000000000..7c24d65bfd3 --- /dev/null +++ b/markdown/org/showcase/french-terry-sven/en.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "The model is totally walking away with it though." +date: "2017-10-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fd444e514ea1ec6a2e2830b0a17bbc044f18a702-683x854.jpg" +intro: "This post is originally appeared on the Instagram feed of nadesmakes ." +title: "The Sven sweater in a French Terry with little to no stretch" +--- + + +This post is [originally appeared](https://www.instagram.com/p/BaBqKDtDelP/) +on [the Instagram feed of nadesmakes](https://www.instagram.com/nadesmakes/). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/french-terry-sven/es.md b/markdown/org/showcase/french-terry-sven/es.md new file mode 100644 index 00000000000..8222e43727a --- /dev/null +++ b/markdown/org/showcase/french-terry-sven/es.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "The model is totally walking away with it though." +date: "2017-10-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fd444e514ea1ec6a2e2830b0a17bbc044f18a702-683x854.jpg" +intro: "This post is originally appeared on the Instagram feed of nadesmakes ." +title: "The Sven sweater in a French Terry with little to no stretch [No traducido]" +--- + + +This post is [originally appeared](https://www.instagram.com/p/BaBqKDtDelP/) +on [the Instagram feed of nadesmakes](https://www.instagram.com/nadesmakes/). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/french-terry-sven/fr.md b/markdown/org/showcase/french-terry-sven/fr.md new file mode 100644 index 00000000000..70435ebf0b9 --- /dev/null +++ b/markdown/org/showcase/french-terry-sven/fr.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Mais le modèle s'en fiche totalement." +date: "2017-10-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fd444e514ea1ec6a2e2830b0a17bbc044f18a702-683x854.jpg" +intro: "Ce message est initialement apparu sur le feed Instagram de nadesmakes ." +title: "Le sweat Sven dans un french Terry avec peu d'élasticité" +--- + + +Ce message est [initialement apparu](https://www.instagram.com/p/BaBqKDtDelP/) sur [le feed Instagram de nadesmakes](https://www.instagram.com/nadesmakes/). + +Elle est publiée ici avec son autorisation. + diff --git a/markdown/org/showcase/french-terry-sven/nl.md b/markdown/org/showcase/french-terry-sven/nl.md new file mode 100644 index 00000000000..8177dbd9eea --- /dev/null +++ b/markdown/org/showcase/french-terry-sven/nl.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Het model komt er helemaal mee weg." +date: "2017-10-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fd444e514ea1ec6a2e2830b0a17bbc044f18a702-683x854.jpg" +intro: "Deze post verscheen eerst op de Instagram feed van nadesmakes ." +title: "De Sven sweater in een French terry met weinig tot geen stretch" +--- + + +Deze post [verscheen eerst](https://www.instagram.com/p/BaBqKDtDelP/) op de [Instagram feed van nadesmakes](https://www.instagram.com/nadesmakes/). + +Hij werd hier gepost met toestemming. + diff --git a/markdown/org/showcase/green-wahid/de.md b/markdown/org/showcase/green-wahid/de.md new file mode 100644 index 00000000000..c5f2836b781 --- /dev/null +++ b/markdown/org/showcase/green-wahid/de.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "That's some A-grade unselfish sewing we've got here" +date: "2016-08-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e7559ec0b220cf12bf7457c3816db1771737b30f-579x699.jpg" +intro: "This picture is from the Unselfish Sewing - Wahid Waistcoat blogpost on rememberinggravity.wordpress.com" +title: "[auf Englisch] A green Wahid waistcoat by Rose" +--- + + +This picture is from the [Unselfish Sewing - Wahid Waistcoat](https://rememberinggravity.wordpress.com/2016/08/17/unselfish-sewing-wahid-waistcoat/) blogpost on [rememberinggravity.wordpress.com](https://rememberinggravity.wordpress.com/) + diff --git a/markdown/org/showcase/green-wahid/en.md b/markdown/org/showcase/green-wahid/en.md new file mode 100644 index 00000000000..6450c1929e0 --- /dev/null +++ b/markdown/org/showcase/green-wahid/en.md @@ -0,0 +1,13 @@ +--- +maker: "unknown" +caption: "That's some A-grade unselfish sewing we've got here" +date: "2016-08-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e7559ec0b220cf12bf7457c3816db1771737b30f-579x699.jpg" +intro: "This picture is from the Unselfish Sewing - Wahid Waistcoat blogpost on rememberinggravity.wordpress.com" +title: "A green Wahid waistcoat by Rose" +--- + + +This picture is from the [Unselfish Sewing - Wahid Waistcoat](https://rememberinggravity.wordpress.com/2016/08/17/unselfish-sewing-wahid-waistcoat/) +blogpost on [rememberinggravity.wordpress.com](https://rememberinggravity.wordpress.com/) + diff --git a/markdown/org/showcase/green-wahid/es.md b/markdown/org/showcase/green-wahid/es.md new file mode 100644 index 00000000000..a2db48033e2 --- /dev/null +++ b/markdown/org/showcase/green-wahid/es.md @@ -0,0 +1,13 @@ +--- +maker: "unknown" +caption: "That's some A-grade unselfish sewing we've got here" +date: "2016-08-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e7559ec0b220cf12bf7457c3816db1771737b30f-579x699.jpg" +intro: "This picture is from the Unselfish Sewing - Wahid Waistcoat blogpost on rememberinggravity.wordpress.com" +title: "A green Wahid waistcoat by Rose [No traducido]" +--- + + +This picture is from the [Unselfish Sewing - Wahid Waistcoat](https://rememberinggravity.wordpress.com/2016/08/17/unselfish-sewing-wahid-waistcoat/) +blogpost on [rememberinggravity.wordpress.com](https://rememberinggravity.wordpress.com/) + diff --git a/markdown/org/showcase/green-wahid/fr.md b/markdown/org/showcase/green-wahid/fr.md new file mode 100644 index 00000000000..a377d25c52e --- /dev/null +++ b/markdown/org/showcase/green-wahid/fr.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "C'est une couture désintéressée de haute qualité que nous avons ici" +date: "2016-08-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e7559ec0b220cf12bf7457c3816db1771737b30f-579x699.jpg" +intro: "Cette image provient de l'article de blog couture désintéressée - Gilet Wahid sur rappelinggravity.wordpress.com" +title: "Un gilet Wahid vert par Rose" +--- + + +Cette image provient de l'article de blog [couture désintéressée - Gilet Wahid](https://rememberinggravity.wordpress.com/2016/08/17/unselfish-sewing-wahid-waistcoat/) sur [rappelinggravity.wordpress.com](https://rememberinggravity.wordpress.com/) + diff --git a/markdown/org/showcase/green-wahid/nl.md b/markdown/org/showcase/green-wahid/nl.md new file mode 100644 index 00000000000..77417a3598d --- /dev/null +++ b/markdown/org/showcase/green-wahid/nl.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Dat is een stukje eersteklas onzelfzuchtig naaiwerk hier" +date: "2016-08-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e7559ec0b220cf12bf7457c3816db1771737b30f-579x699.jpg" +intro: "Deze foto komt uit de blogpost Unselfish Sewing - Wahid Waistcoat op rememberinggravity.wordpress.com" +title: "Een groene Wahid gilet door Rose" +--- + + +Deze foto komt uit de blogpost [Unselfish Sewing - Wahid Waistcoat](https://rememberinggravity.wordpress.com/2016/08/17/unselfish-sewing-wahid-waistcoat/) op [rememberinggravity.wordpress.com](https://rememberinggravity.wordpress.com/) + diff --git a/markdown/org/showcase/grey-sven/de.md b/markdown/org/showcase/grey-sven/de.md new file mode 100644 index 00000000000..fb871f2b3e1 --- /dev/null +++ b/markdown/org/showcase/grey-sven/de.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Ksenia made this Sven for her man." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8470f4414deeee3d072401616b01be02c8b98bc7-1080x1080.jpg" +intro: "This image is from the Instagram feed of Ksenia ." +title: "[auf Englisch] Sven in grey terry A grey terry Sven" +--- + + +[This image](https://www.instagram.com/p/BehvZ1fj4yo/) is from [the Instagram feed of Ksenia](https://www.instagram.com/owl.laughing/). + +It is published here with permission. + diff --git a/markdown/org/showcase/grey-sven/en.md b/markdown/org/showcase/grey-sven/en.md new file mode 100644 index 00000000000..8f9a9fc5e3f --- /dev/null +++ b/markdown/org/showcase/grey-sven/en.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Ksenia made this Sven for her man." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8470f4414deeee3d072401616b01be02c8b98bc7-1080x1080.jpg" +intro: "This image is from the Instagram feed of Ksenia ." +title: "Sven in grey terry A grey terry Sven" +--- + + +[This image](https://www.instagram.com/p/BehvZ1fj4yo/) +is from [the Instagram feed of Ksenia](https://www.instagram.com/owl.laughing/). + +It is published here with permission. + diff --git a/markdown/org/showcase/grey-sven/es.md b/markdown/org/showcase/grey-sven/es.md new file mode 100644 index 00000000000..709754df6eb --- /dev/null +++ b/markdown/org/showcase/grey-sven/es.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Ksenia made this Sven for her man." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8470f4414deeee3d072401616b01be02c8b98bc7-1080x1080.jpg" +intro: "This image is from the Instagram feed of Ksenia ." +title: "Sven in grey terry A grey terry Sven [No traducido]" +--- + + +[This image](https://www.instagram.com/p/BehvZ1fj4yo/) +is from [the Instagram feed of Ksenia](https://www.instagram.com/owl.laughing/). + +It is published here with permission. + diff --git a/markdown/org/showcase/grey-sven/fr.md b/markdown/org/showcase/grey-sven/fr.md new file mode 100644 index 00000000000..82a3750c117 --- /dev/null +++ b/markdown/org/showcase/grey-sven/fr.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Ksenia a fait ce Sven pour son homme." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8470f4414deeee3d072401616b01be02c8b98bc7-1080x1080.jpg" +intro: "Cette photo est issue du feed Instagram de Ksenia ." +title: "Sven en french terry gris" +--- + + +[Cette photo](https://www.instagram.com/p/BehvZ1fj4yo/) est issue [du feed Instagram de Ksenia](https://www.instagram.com/owl.laughing/). + +Elle est publiée ici avec son autorisation. + diff --git a/markdown/org/showcase/grey-sven/nl.md b/markdown/org/showcase/grey-sven/nl.md new file mode 100644 index 00000000000..45daf0dc95f --- /dev/null +++ b/markdown/org/showcase/grey-sven/nl.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Ksenia maakte deze Sven voor haar (s)vent." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8470f4414deeee3d072401616b01be02c8b98bc7-1080x1080.jpg" +intro: "Deze afbeelding komt van de Instagram feed van Ksenia ." +title: "Sven in grijze terry" +--- + + +[Deze afbeelding](https://www.instagram.com/p/BehvZ1fj4yo/) komt van [de Instagram feed van Ksenia](https://www.instagram.com/owl.laughing/). + +Ze werd hier gepost met toestemming. + diff --git a/markdown/org/showcase/hortensia-by-wouter/de.md b/markdown/org/showcase/hortensia-by-wouter/de.md new file mode 100644 index 00000000000..c3c9375f638 --- /dev/null +++ b/markdown/org/showcase/hortensia-by-wouter/de.md @@ -0,0 +1,24 @@ +--- +maker: "Wouter.vdub" +caption: "Haring's Hortensia handbag by Wouter" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/7192891ad24b1dc1ccb1a4093dc70e3678bb65c7-661x612.jpg" +intro: "Not only did Wouter sew this Haring's Hortensia handbag, he also designed the fabric and made the pattern! He shared that he made the fabric design with his daughter and had it printed through Spoonflower." +title: "[auf Englisch] Hortensia by Wouter" +--- + +Not only did Wouter sew this Haring's Hortensia handbag, he also designed the fabric and made the pattern! He shared that he made the fabric design with his daughter and had it printed through Spoonflower. + +Wouter also shares on [the Instagram feed @Wouter.vdub](https://www.instagram.com/Wouter.vdub/) and [blogs at ShirtArtistry]https://shirtartistry.blog/). + +![View of the front](https://posts.freesewing.org/uploads/hortensia_by_wouter_hortensia2_ec8a517447.jpg "View of the front") + +![View of the side](hortensia3.jpg) + +![View of the zipper](hortensia4.jpg) + + + +This picture is from Wouter on Discord. It is reposted here with permission. + + diff --git a/markdown/org/showcase/hortensia-by-wouter/en.md b/markdown/org/showcase/hortensia-by-wouter/en.md new file mode 100644 index 00000000000..9ad0c05bf10 --- /dev/null +++ b/markdown/org/showcase/hortensia-by-wouter/en.md @@ -0,0 +1,24 @@ +--- +maker: "Wouter.vdub" +caption: "Haring's Hortensia handbag by Wouter" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/7192891ad24b1dc1ccb1a4093dc70e3678bb65c7-661x612.jpg" +intro: "Not only did Wouter sew this Haring's Hortensia handbag, he also designed the fabric and made the pattern! He shared that he made the fabric design with his daughter and had it printed through Spoonflower." +title: "Hortensia by Wouter" +--- + +Not only did Wouter sew this Haring's Hortensia handbag, he also designed the fabric and made the pattern! He shared that he made the fabric design with his daughter and had it printed through Spoonflower. + +Wouter also shares on [the Instagram feed @Wouter.vdub](https://www.instagram.com/Wouter.vdub/) and [blogs at ShirtArtistry]https://shirtartistry.blog/). + +![View of the front](https://posts.freesewing.org/uploads/hortensia_by_wouter_hortensia2_ec8a517447.jpg "View of the front") + +![View of the side](https://posts.freesewing.org/uploads/hortensia_by_wouter_hortensia3_9946bc8cde.jpg) + +![View of the zipper](https://posts.freesewing.org/uploads/hortensia_by_wouter_hortensia4_39f92d992c.jpg) + + + +This picture is from Wouter on Discord. It is reposted here with permission. + + diff --git a/markdown/org/showcase/hortensia-by-wouter/es.md b/markdown/org/showcase/hortensia-by-wouter/es.md new file mode 100644 index 00000000000..9a2493fad51 --- /dev/null +++ b/markdown/org/showcase/hortensia-by-wouter/es.md @@ -0,0 +1,24 @@ +--- +maker: "Wouter.vdub" +caption: "Haring's Hortensia handbag by Wouter" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/7192891ad24b1dc1ccb1a4093dc70e3678bb65c7-661x612.jpg" +intro: "Not only did Wouter sew this Haring's Hortensia handbag, he also designed the fabric and made the pattern! He shared that he made the fabric design with his daughter and had it printed through Spoonflower." +title: "Hortensia by Wouter [No traducido]" +--- + +Not only did Wouter sew this Haring's Hortensia handbag, he also designed the fabric and made the pattern! He shared that he made the fabric design with his daughter and had it printed through Spoonflower. + +Wouter also shares on [the Instagram feed @Wouter.vdub](https://www.instagram.com/Wouter.vdub/) and [blogs at ShirtArtistry]https://shirtartistry.blog/). + +![View of the front](https://posts.freesewing.org/uploads/hortensia_by_wouter_hortensia2_ec8a517447.jpg "View of the front") + +![View of the side](https://posts.freesewing.org/uploads/hortensia_by_wouter_hortensia3_9946bc8cde.jpg) + +![View of the zipper](https://posts.freesewing.org/uploads/hortensia_by_wouter_hortensia4_39f92d992c.jpg) + + + +This picture is from Wouter on Discord. It is reposted here with permission. + + diff --git a/markdown/org/showcase/hortensia-by-wouter/fr.md b/markdown/org/showcase/hortensia-by-wouter/fr.md new file mode 100644 index 00000000000..ad12d5d92e8 --- /dev/null +++ b/markdown/org/showcase/hortensia-by-wouter/fr.md @@ -0,0 +1,24 @@ +--- +maker: "Wouter.vdub" +caption: "Sac à main Hortensia illustré Haring par Wouter" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/7192891ad24b1dc1ccb1a4093dc70e3678bb65c7-661x612.jpg" +intro: "Wouter n'a pas seulement cousu ce sac à main Hortensia aux illustrations d'Haring, il a aussi conçu le tissu et fait le patron ! Il a partagé qu'il a fait le design du tissu avec sa fille et l'a fait imprimer via Spoonflower." +title: "Hortensia par Wouter" +--- + +Wouter n'a pas seulement cousu ce sac à main Hortensia aux illustrations d'Haring, il a aussi conçu le tissu et fait le patron ! Il a partagé qu'il a fait le design du tissu avec sa fille et l'a fait imprimer via Spoonflower. + +Wouter partage également sur [son Instagram @Wouter.vdub](https://www.instagram.com/Wouter.vdub/) et [blogs à ShirtArtistry]https://shirtartistry.blog/). + +![Photo de l'avant](https://posts.freesewing.org/uploads/hortensia_by_wouter_hortensia2_ec8a517447.jpg "Photo de l'avant") + +![Vue du côté](https://posts.freesewing.org/uploads/hortensia_by_wouter_hortensia3_9946bc8cde.jpg "Vue du côté") + +![Vue de la fermeture à glissière](hortensia4.jpg) + + + +Cette photo provient de Wouter sur Discord. Elle est publiée ici avec son autorisation. + + diff --git a/markdown/org/showcase/hortensia-by-wouter/nl.md b/markdown/org/showcase/hortensia-by-wouter/nl.md new file mode 100644 index 00000000000..71d53b858ea --- /dev/null +++ b/markdown/org/showcase/hortensia-by-wouter/nl.md @@ -0,0 +1,24 @@ +--- +maker: "Wouter.vdub" +caption: "Haring's Hortensia handbag by Wouter" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/7192891ad24b1dc1ccb1a4093dc70e3678bb65c7-661x612.jpg" +intro: "Not only did Wouter sew this Haring's Hortensia handbag, he also designed the fabric and made the pattern! He shared that he made the fabric design with his daughter and had it printed through Spoonflower." +title: "Hortensia by Wouter [Niet vertaald]" +--- + +Not only did Wouter sew this Haring's Hortensia handbag, he also designed the fabric and made the pattern! He shared that he made the fabric design with his daughter and had it printed through Spoonflower. + +Wouter also shares on [the Instagram feed @Wouter.vdub](https://www.instagram.com/Wouter.vdub/) and [blogs at ShirtArtistry]https://shirtartistry.blog/). + +![View of the front](https://posts.freesewing.org/uploads/hortensia_by_wouter_hortensia2_ec8a517447.jpg "View of the front") + +![View of the side](https://posts.freesewing.org/uploads/hortensia_by_wouter_hortensia3_9946bc8cde.jpg) + +![View of the zipper](https://posts.freesewing.org/uploads/hortensia_by_wouter_hortensia4_39f92d992c.jpg) + + + +This picture is from Wouter on Discord. It is reposted here with permission. + + diff --git a/markdown/org/showcase/huey-by-minty/de.md b/markdown/org/showcase/huey-by-minty/de.md new file mode 100644 index 00000000000..37ca72c3d87 --- /dev/null +++ b/markdown/org/showcase/huey-by-minty/de.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Huey hoodie by Minty" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1ae81c4f08dd21d7db28538399d818c72ff586a9-810x1083.jpg" +intro: "This fantastic Huey hoodie was made by Minty! Minty shared that he made this with a regular machine instead of a serger." +title: "[auf Englisch] Huey by Minty" +--- + +This fantastic Huey hoodie was made by Minty! Minty shared that he made this with a regular machine instead of a serger. + +![Zipped view](https://posts.freesewing.org/uploads/huey_by_minty_hueyminty2_cb9e822561.jpg "Zipped view") + + + +This picture is from Minty on Discord. It is reposted here with permission. + + diff --git a/markdown/org/showcase/huey-by-minty/en.md b/markdown/org/showcase/huey-by-minty/en.md new file mode 100644 index 00000000000..e210fcc93f7 --- /dev/null +++ b/markdown/org/showcase/huey-by-minty/en.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Huey hoodie by Minty" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1ae81c4f08dd21d7db28538399d818c72ff586a9-810x1083.jpg" +intro: "This fantastic Huey hoodie was made by Minty! Minty shared that he made this with a regular machine instead of a serger." +title: "Huey by Minty" +--- + +This fantastic Huey hoodie was made by Minty! Minty shared that he made this with a regular machine instead of a serger. + +![Zipped view](https://posts.freesewing.org/uploads/huey_by_minty_hueyminty2_cb9e822561.jpg "Zipped view") + + + +This picture is from Minty on Discord. It is reposted here with permission. + + diff --git a/markdown/org/showcase/huey-by-minty/es.md b/markdown/org/showcase/huey-by-minty/es.md new file mode 100644 index 00000000000..4a2cec1fd35 --- /dev/null +++ b/markdown/org/showcase/huey-by-minty/es.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Huey hoodie by Minty" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1ae81c4f08dd21d7db28538399d818c72ff586a9-810x1083.jpg" +intro: "This fantastic Huey hoodie was made by Minty! Minty shared that he made this with a regular machine instead of a serger." +title: "Huey by Minty [No traducido]" +--- + +This fantastic Huey hoodie was made by Minty! Minty shared that he made this with a regular machine instead of a serger. + +![Zipped view](https://posts.freesewing.org/uploads/huey_by_minty_hueyminty2_cb9e822561.jpg "Zipped view") + + + +This picture is from Minty on Discord. It is reposted here with permission. + + diff --git a/markdown/org/showcase/huey-by-minty/fr.md b/markdown/org/showcase/huey-by-minty/fr.md new file mode 100644 index 00000000000..acb5dd20a1b --- /dev/null +++ b/markdown/org/showcase/huey-by-minty/fr.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Sweat à capuche Huey par Minty" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1ae81c4f08dd21d7db28538399d818c72ff586a9-810x1083.jpg" +intro: "Ce fantastique sweat à capuche Huey a été cousu par Minty! Minty a partagé qu'il l'a réalisé avec une machine normale sans surjeteuse." +title: "Huey par Minty" +--- + +Ce fantastique sweat à capuche Huey a été cousu par Minty! Minty a partagé qu'il l'a réalisé avec une machine normale sans surjeteuse. + +![Vue du zip](https://posts.freesewing.org/uploads/huey_by_minty_hueyminty2_cb9e822561.jpg "Vue du zip") + + + +Cette photo provient de Minty sur Discord. Elle est publiée ici avec son autorisation. + + diff --git a/markdown/org/showcase/huey-by-minty/nl.md b/markdown/org/showcase/huey-by-minty/nl.md new file mode 100644 index 00000000000..a96c5fee3d1 --- /dev/null +++ b/markdown/org/showcase/huey-by-minty/nl.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Huey hoodie by Minty" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1ae81c4f08dd21d7db28538399d818c72ff586a9-810x1083.jpg" +intro: "This fantastic Huey hoodie was made by Minty! Minty shared that he made this with a regular machine instead of a serger." +title: "Huey by Minty [Niet vertaald]" +--- + +This fantastic Huey hoodie was made by Minty! Minty shared that he made this with a regular machine instead of a serger. + +![Zipped view](https://posts.freesewing.org/uploads/huey_by_minty_hueyminty2_cb9e822561.jpg "Zipped view") + + + +This picture is from Minty on Discord. It is reposted here with permission. + + diff --git a/markdown/org/showcase/huey-by-paul/de.md b/markdown/org/showcase/huey-by-paul/de.md new file mode 100644 index 00000000000..daad4ec532d --- /dev/null +++ b/markdown/org/showcase/huey-by-paul/de.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Cotton hoodie with contrasting lining by Paul" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3a6bef4d69f110ee3ebe4d7c20f84a91fefbe266-2000x2976.jpg" +intro: "FIXME_no_intro" +title: "[auf Englisch] Huey by Paul" +--- + + + diff --git a/markdown/org/showcase/huey-by-paul/en.md b/markdown/org/showcase/huey-by-paul/en.md new file mode 100644 index 00000000000..e56936db511 --- /dev/null +++ b/markdown/org/showcase/huey-by-paul/en.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "Cotton hoodie with contrasting lining by Paul" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3a6bef4d69f110ee3ebe4d7c20f84a91fefbe266-2000x2976.jpg" +intro: "FIXME_no_intro" +title: "Huey by Paul" +--- + + diff --git a/markdown/org/showcase/huey-by-paul/es.md b/markdown/org/showcase/huey-by-paul/es.md new file mode 100644 index 00000000000..505931e2d62 --- /dev/null +++ b/markdown/org/showcase/huey-by-paul/es.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "Cotton hoodie with contrasting lining by Paul" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3a6bef4d69f110ee3ebe4d7c20f84a91fefbe266-2000x2976.jpg" +intro: "FIXME_no_intro" +title: "Huey by Paul [No traducido]" +--- + + diff --git a/markdown/org/showcase/huey-by-paul/fr.md b/markdown/org/showcase/huey-by-paul/fr.md new file mode 100644 index 00000000000..3a67c7bb718 --- /dev/null +++ b/markdown/org/showcase/huey-by-paul/fr.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Sweat à capuche en coton avec doublure contrastante par Paul" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3a6bef4d69f110ee3ebe4d7c20f84a91fefbe266-2000x2976.jpg" +intro: "FIXME_no_intro" +title: "Huey par Paul" +--- + + + diff --git a/markdown/org/showcase/huey-by-paul/nl.md b/markdown/org/showcase/huey-by-paul/nl.md new file mode 100644 index 00000000000..fa56b67c0ff --- /dev/null +++ b/markdown/org/showcase/huey-by-paul/nl.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Katoenen hoodie met contrasterende voering door Paul" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3a6bef4d69f110ee3ebe4d7c20f84a91fefbe266-2000x2976.jpg" +intro: "FIXME_no_intro" +title: "Huey door Paul" +--- + + + diff --git a/markdown/org/showcase/hugo-by-karin/de.md b/markdown/org/showcase/hugo-by-karin/de.md new file mode 100644 index 00000000000..fbe770fa5a7 --- /dev/null +++ b/markdown/org/showcase/hugo-by-karin/de.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Some work on fit and sleeves, but a great end result." +date: "2018-10-07" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5dc9f5f74dc466d258437a2aca91ab10fcca1e70-2712x1905.jpg" +intro: "Karin has more details of this make on her blog ." +title: "[auf Englisch] A hacked Hugo Hoodie by Karin" +--- + + +Karin has more details of this make [on her blog](https://www.karinkay.nl/freesewing-hugo-hoodie/). + diff --git a/markdown/org/showcase/hugo-by-karin/en.md b/markdown/org/showcase/hugo-by-karin/en.md new file mode 100644 index 00000000000..74480a1b713 --- /dev/null +++ b/markdown/org/showcase/hugo-by-karin/en.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Some work on fit and sleeves, but a great end result." +date: "2018-10-07" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5dc9f5f74dc466d258437a2aca91ab10fcca1e70-2712x1905.jpg" +intro: "Karin has more details of this make on her blog ." +title: "A hacked Hugo Hoodie by Karin" +--- + + +Karin has more details of this make [on her blog](https://www.karinkay.nl/freesewing-hugo-hoodie/). + diff --git a/markdown/org/showcase/hugo-by-karin/es.md b/markdown/org/showcase/hugo-by-karin/es.md new file mode 100644 index 00000000000..93999c140ba --- /dev/null +++ b/markdown/org/showcase/hugo-by-karin/es.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Some work on fit and sleeves, but a great end result." +date: "2018-10-07" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5dc9f5f74dc466d258437a2aca91ab10fcca1e70-2712x1905.jpg" +intro: "Karin has more details of this make on her blog ." +title: "A hacked Hugo Hoodie by Karin [No traducido]" +--- + + +Karin has more details of this make [on her blog](https://www.karinkay.nl/freesewing-hugo-hoodie/). + diff --git a/markdown/org/showcase/hugo-by-karin/fr.md b/markdown/org/showcase/hugo-by-karin/fr.md new file mode 100644 index 00000000000..20a9a358e63 --- /dev/null +++ b/markdown/org/showcase/hugo-by-karin/fr.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Un peu de travail sur la forme et les manches, mais un excellent résultat final." +date: "2018-10-07" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5dc9f5f74dc466d258437a2aca91ab10fcca1e70-2712x1905.jpg" +intro: "Karin donne plus de détails sur cette réalisation sur son blog ." +title: "Un Hugo à capuche haché par Karin" +--- + + +Karin donne plus de détails sur cette réalisation [sur son blog](https://www.karinkay.nl/freesewing-hugo-hoodie/). + diff --git a/markdown/org/showcase/hugo-by-karin/nl.md b/markdown/org/showcase/hugo-by-karin/nl.md new file mode 100644 index 00000000000..0fe87b9fe5d --- /dev/null +++ b/markdown/org/showcase/hugo-by-karin/nl.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Wat werk aan de pasvorm en de mouwen, maar een geweldig eindresultaat." +date: "2018-10-07" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5dc9f5f74dc466d258437a2aca91ab10fcca1e70-2712x1905.jpg" +intro: "Karin heeft meer details over dit stuk op haar blog ." +title: "Een Hugo hack door Karin" +--- + + +Karin heeft meer details over dit stuk [op haar blog](https://www.karinkay.nl/freesewing-hugo-hoodie/). + diff --git a/markdown/org/showcase/hugo-by-lainey/de.md b/markdown/org/showcase/hugo-by-lainey/de.md new file mode 100644 index 00000000000..04ca0c8c5bd --- /dev/null +++ b/markdown/org/showcase/hugo-by-lainey/de.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "An Aaron A-shirt by Joost" +date: "2019-02-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/574a1082b46ca29961461e9fa3f0a03772a1da74-1000x972.jpg" +intro: "Lainey hacked this Hugo and gave it extra warm lining and zippers on the pouch pocket." +title: "[auf Englisch] A hacked Hugo by Lainey" +--- + +Lainey hacked this Hugo and gave it extra warm lining and zippers on the pouch pocket. + +![Eine andere Ansicht](https://posts.freesewing.org/uploads/hugo_by_lainey_2_81b29a8f49.jpg "Eine andere Ansicht") diff --git a/markdown/org/showcase/hugo-by-lainey/en.md b/markdown/org/showcase/hugo-by-lainey/en.md new file mode 100644 index 00000000000..403473eca46 --- /dev/null +++ b/markdown/org/showcase/hugo-by-lainey/en.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "An Aaron A-shirt by Joost" +date: "2019-02-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/574a1082b46ca29961461e9fa3f0a03772a1da74-1000x972.jpg" +intro: "Lainey hacked this Hugo and gave it extra warm lining and zippers on the pouch pocket." +title: "A hacked Hugo by Lainey" +--- + +Lainey hacked this Hugo and gave it extra warm lining and zippers on the pouch pocket. + +![Another view](https://posts.freesewing.org/uploads/hugo_by_lainey_2_81b29a8f49.jpg "Another view") diff --git a/markdown/org/showcase/hugo-by-lainey/es.md b/markdown/org/showcase/hugo-by-lainey/es.md new file mode 100644 index 00000000000..c9228110c49 --- /dev/null +++ b/markdown/org/showcase/hugo-by-lainey/es.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "An Aaron A-shirt by Joost" +date: "2019-02-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/574a1082b46ca29961461e9fa3f0a03772a1da74-1000x972.jpg" +intro: "Lainey hacked this Hugo and gave it extra warm lining and zippers on the pouch pocket." +title: "A hacked Hugo by Lainey [No traducido]" +--- + +Lainey hacked this Hugo and gave it extra warm lining and zippers on the pouch pocket. + +![Another view](https://posts.freesewing.org/uploads/hugo_by_lainey_2_81b29a8f49.jpg "Another view") diff --git a/markdown/org/showcase/hugo-by-lainey/fr.md b/markdown/org/showcase/hugo-by-lainey/fr.md new file mode 100644 index 00000000000..96172d84bd2 --- /dev/null +++ b/markdown/org/showcase/hugo-by-lainey/fr.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Un débardeur Aaron par Joost" +date: "2019-02-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/574a1082b46ca29961461e9fa3f0a03772a1da74-1000x972.jpg" +intro: "Lainey a hacké cet Hugo et lui a mis une doublure très chaude et des fermetures sur la poche ventrale." +title: "Un Hugo hacké par Lainey" +--- + +Lainey a hacké cet Hugo et lui a mis une doublure très chaude et des fermetures sur la poche ventrale. + +![Une autre vue](https://posts.freesewing.org/uploads/hugo_by_lainey_2_81b29a8f49.jpg "Une autre vue") diff --git a/markdown/org/showcase/hugo-by-lainey/nl.md b/markdown/org/showcase/hugo-by-lainey/nl.md new file mode 100644 index 00000000000..c96083c9571 --- /dev/null +++ b/markdown/org/showcase/hugo-by-lainey/nl.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Een Aaron hemdje door Joost" +date: "2019-02-24" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/574a1082b46ca29961461e9fa3f0a03772a1da74-1000x972.jpg" +intro: "Lainey hacked this Hugo and gave it extra warm lining and zippers on the pouch pocket." +title: "[Engelstalig] A hacked Hugo by Lainey" +--- + +Lainey hacked this Hugo and gave it extra warm lining and zippers on the pouch pocket. + +![Een andere kant](https://posts.freesewing.org/uploads/hugo_by_lainey_2_81b29a8f49.jpg "Een andere kant") diff --git a/markdown/org/showcase/hugo-saul/de.md b/markdown/org/showcase/hugo-saul/de.md new file mode 100644 index 00000000000..a26455c5df8 --- /dev/null +++ b/markdown/org/showcase/hugo-saul/de.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "Check out that ribbing!" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c73a63d22b171ce29161c068b9b259ba70e26d4d-1080x1080.jpg" +intro: "Saul sewed up this Hugo hoodie in black, but gave it that extra something with bright pink ribbing at the hem and wrists. Can't buy that at the shop!" +title: "[auf Englisch] Black Hugo with Pink Ribbing by Saul" +--- + + +Saul sewed up this Hugo hoodie in black, but gave it that extra something with bright pink ribbing at the hem and wrists. Can't buy that at the shop! + + +This picture is from the instagram feed of [Sarah](https://www.instagram.com/sarahlh98/). It is posted here with permission from Sarah and Saul. + + diff --git a/markdown/org/showcase/hugo-saul/en.md b/markdown/org/showcase/hugo-saul/en.md new file mode 100644 index 00000000000..64c7b3fff76 --- /dev/null +++ b/markdown/org/showcase/hugo-saul/en.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Check out that ribbing!" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c73a63d22b171ce29161c068b9b259ba70e26d4d-1080x1080.jpg" +intro: "Saul sewed up this Hugo hoodie in black, but gave it that extra something with bright pink ribbing at the hem and wrists. Can't buy that at the shop!" +title: "Black Hugo with Pink Ribbing by Saul" +--- + +Saul sewed up this Hugo hoodie in black, but gave it that extra something with bright pink ribbing at the hem and wrists. Can't buy that at the shop! + + +This picture is from the instagram feed of [Sarah](https://www.instagram.com/sarahlh98/). It is posted here with permission from Sarah and Saul. + + diff --git a/markdown/org/showcase/hugo-saul/es.md b/markdown/org/showcase/hugo-saul/es.md new file mode 100644 index 00000000000..c8ca1f998a4 --- /dev/null +++ b/markdown/org/showcase/hugo-saul/es.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Check out that ribbing!" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c73a63d22b171ce29161c068b9b259ba70e26d4d-1080x1080.jpg" +intro: "Saul sewed up this Hugo hoodie in black, but gave it that extra something with bright pink ribbing at the hem and wrists. Can't buy that at the shop!" +title: "Black Hugo with Pink Ribbing by Saul [No traducido]" +--- + +Saul sewed up this Hugo hoodie in black, but gave it that extra something with bright pink ribbing at the hem and wrists. Can't buy that at the shop! + + +This picture is from the instagram feed of [Sarah](https://www.instagram.com/sarahlh98/). It is posted here with permission from Sarah and Saul. + + diff --git a/markdown/org/showcase/hugo-saul/fr.md b/markdown/org/showcase/hugo-saul/fr.md new file mode 100644 index 00000000000..0d08a9b9441 --- /dev/null +++ b/markdown/org/showcase/hugo-saul/fr.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "Admirez ces bords-côtes !" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c73a63d22b171ce29161c068b9b259ba70e26d4d-1080x1080.jpg" +intro: "Saul a cousu ce sweat à capuche Hugo en noir, mais lui a donné ce truc en plus avec des bandes rose vif à l'ourlet et aux poignets. Vous ne trouverez pas ça en magasin !" +title: "Hugo noir avec bord-côte rose par Saul" +--- + + +Saul a cousu ce sweat à capuche Hugo en noir, mais lui a donné ce truc en plus avec des bandes rose vif à l'ourlet et aux poignets. Vous ne trouverez pas ça en magasin ! + + +Cette image provient du flux Instagram de [Sarah](https://www.instagram.com/sarahlh98/). Il est partagé ici avec la permission de Sarah et Saul. + + diff --git a/markdown/org/showcase/hugo-saul/nl.md b/markdown/org/showcase/hugo-saul/nl.md new file mode 100644 index 00000000000..29728cdeeea --- /dev/null +++ b/markdown/org/showcase/hugo-saul/nl.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Check out that ribbing!" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/c73a63d22b171ce29161c068b9b259ba70e26d4d-1080x1080.jpg" +intro: "Saul sewed up this Hugo hoodie in black, but gave it that extra something with bright pink ribbing at the hem and wrists. Can't buy that at the shop!" +title: "Black Hugo with Pink Ribbing by Saul [Niet vertaald]" +--- + +Saul sewed up this Hugo hoodie in black, but gave it that extra something with bright pink ribbing at the hem and wrists. Can't buy that at the shop! + + +This picture is from the instagram feed of [Sarah](https://www.instagram.com/sarahlh98/). It is posted here with permission from Sarah and Saul. + + diff --git a/markdown/org/showcase/husband-hugo/de.md b/markdown/org/showcase/husband-hugo/de.md new file mode 100644 index 00000000000..096da3e24fd --- /dev/null +++ b/markdown/org/showcase/husband-hugo/de.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Is it me or is Hugo a popular make for husbands?" +date: "2015-12-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/bc1b64060b3b0907157c2e1608b2b2610b81a4b0-1080x1080.jpg" +intro: "This picture is from the Instagram feed of uneanneedecouture ." +title: "[auf Englisch] A hugo for the husband, by Sonia" +--- + + +This picture is from [the Instagram feed](https://www.instagram.com/p/_1j7FSgynG/) of [uneanneedecouture](https://uneanneedecouture.wordpress.com/). + +> ##### More pictures and info on the original blog post +> +> This make is detailed in the [Le sweat en mérinos MakeMyPattern](https://uneanneedecouture.wordpress.com/2015/12/28/le-sweat-en-merinos-makemypattern/) on [uneanneedecouture.wordpress.com](https://uneanneedecouture.wordpress.com/). +> +> The blog post is in both French and English. + diff --git a/markdown/org/showcase/husband-hugo/en.md b/markdown/org/showcase/husband-hugo/en.md new file mode 100644 index 00000000000..6180190f2b7 --- /dev/null +++ b/markdown/org/showcase/husband-hugo/en.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Is it me or is Hugo a popular make for husbands?" +date: "2015-12-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/bc1b64060b3b0907157c2e1608b2b2610b81a4b0-1080x1080.jpg" +intro: "This picture is from the Instagram feed of uneanneedecouture ." +title: "A hugo for the husband, by Sonia" +--- + +This picture is from [the Instagram feed](https://www.instagram.com/p/_1j7FSgynG/) of [uneanneedecouture](https://uneanneedecouture.wordpress.com/). + +> ##### More pictures and info on the original blog post +> This make is detailed in the [Le sweat en mérinos MakeMyPattern](https://uneanneedecouture.wordpress.com/2015/12/28/le-sweat-en-merinos-makemypattern/) +> on [uneanneedecouture.wordpress.com](https://uneanneedecouture.wordpress.com/). +> +> The blog post is in both French and English. + diff --git a/markdown/org/showcase/husband-hugo/es.md b/markdown/org/showcase/husband-hugo/es.md new file mode 100644 index 00000000000..3c3b3757af5 --- /dev/null +++ b/markdown/org/showcase/husband-hugo/es.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Is it me or is Hugo a popular make for husbands?" +date: "2015-12-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/bc1b64060b3b0907157c2e1608b2b2610b81a4b0-1080x1080.jpg" +intro: "This picture is from the Instagram feed of uneanneedecouture ." +title: "A hugo for the husband, by Sonia [No traducido]" +--- + +This picture is from [the Instagram feed](https://www.instagram.com/p/_1j7FSgynG/) of [uneanneedecouture](https://uneanneedecouture.wordpress.com/). + +> ##### More pictures and info on the original blog post +> This make is detailed in the [Le sweat en mérinos MakeMyPattern](https://uneanneedecouture.wordpress.com/2015/12/28/le-sweat-en-merinos-makemypattern/) +> on [uneanneedecouture.wordpress.com](https://uneanneedecouture.wordpress.com/). +> +> The blog post is in both French and English. + diff --git a/markdown/org/showcase/husband-hugo/fr.md b/markdown/org/showcase/husband-hugo/fr.md new file mode 100644 index 00000000000..deab5481236 --- /dev/null +++ b/markdown/org/showcase/husband-hugo/fr.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Est-ce que c'est moi ou Hugo est une marque populaire pour les maris ?" +date: "2015-12-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/bc1b64060b3b0907157c2e1608b2b2610b81a4b0-1080x1080.jpg" +intro: "Cette photo provient du feed Instagram de uneanneedecouture ." +title: "Un hugo pour le mari, par Sonia" +--- + + +Cette photo provient du [feed Instagram](https://www.instagram.com/p/_1j7FSgynG/) de [uneanneedecouture](https://uneanneedecouture.wordpress.com/). + +> ##### Plus de photos et d'infos sur l'article de blog original +> +> Cette réalisation est détaillée dans l'article [Le sweat en mérinos MakeMyPattern](https://uneanneedecouture.wordpress.com/2015/12/28/le-sweat-en-merinos-makemypattern/) sur [uneanneedecouture.wordpress.com](https://uneanneedecouture.wordpress.com/). +> +> L'article de blog est en français et en anglais. + diff --git a/markdown/org/showcase/husband-hugo/nl.md b/markdown/org/showcase/husband-hugo/nl.md new file mode 100644 index 00000000000..f8d8ab6a82d --- /dev/null +++ b/markdown/org/showcase/husband-hugo/nl.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Ligt het aan mij of is Hugo een populair patroon voor echtgenoten?" +date: "2015-12-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/bc1b64060b3b0907157c2e1608b2b2610b81a4b0-1080x1080.jpg" +intro: "Deze afbeelding is van de Instagram feed van uneanneedecouture ." +title: "Een Hugo voor de echtgenoot, door Sonia" +--- + + +Deze afbeelding is van [de Instagram feed](https://www.instagram.com/p/_1j7FSgynG/) van [uneanneedecouture](https://uneanneedecouture.wordpress.com/). + +> ##### Meer foto's en info in de originele blogpost +> +> Dit stuk wordt beschreven in [Le sweat en mérinos MakeMyPattern](https://uneanneedecouture.wordpress.com/2015/12/28/le-sweat-en-merinos-makemypattern/) op [uneanneedecouture.wordpress.com](https://uneanneedecouture.wordpress.com/). +> +> De post is zowel in het Engels als in het Frans geschreven. + diff --git a/markdown/org/showcase/liberty-trayvon/de.md b/markdown/org/showcase/liberty-trayvon/de.md new file mode 100644 index 00000000000..64cf414bf7e --- /dev/null +++ b/markdown/org/showcase/liberty-trayvon/de.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Beautiful fabric, and a greatly made tie" +date: "2017-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a4df7c8446671138fe4f6e07eebf32058af31999-1080x1080.jpg" +intro: "My husband travelled to Ireland 🇮🇪 for a weekend (62hrs travelling for 60hrs on the ground 🙀) to attend his brother's wedding 👏 My contribution was this beautiful @libertylondon silk tie and pocket square made specifically for the big day. I was there in spirit." +title: "[auf Englisch] A Trayvon tie in a Liberty silk by Victoria" +--- + + +My husband travelled to Ireland 🇮🇪 for a weekend (62hrs travelling for 60hrs on the ground 🙀) to attend his brother's wedding 👏 My contribution was this beautiful @libertylondon silk tie and pocket square made specifically for the big day. I was there in spirit. + +> ##### See the original on Instagram +> +> [This picture](https://www.instagram.com/p/BZR3pyCHLjm/) is from the Instagram feed of [e2_clothing](https://www.instagram.com/e2_clothing/). + + + diff --git a/markdown/org/showcase/liberty-trayvon/en.md b/markdown/org/showcase/liberty-trayvon/en.md new file mode 100644 index 00000000000..a99a4a4993f --- /dev/null +++ b/markdown/org/showcase/liberty-trayvon/en.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "Beautiful fabric, and a greatly made tie" +date: "2017-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a4df7c8446671138fe4f6e07eebf32058af31999-1080x1080.jpg" +intro: "A Trayvon tie in a Liberty silk by Victoria" +title: "A Trayvon tie in a Liberty silk by Victoria" +--- + + +My husband travelled to Ireland 🇮🇪 for a weekend (62hrs travelling for 60hrs on the ground 🙀) to attend his brother's wedding 👏 +My contribution was this beautiful @libertylondon silk tie and pocket square made specifically for the big day. I was there in spirit. + +> ##### See the original on Instagram +> [This picture](https://www.instagram.com/p/BZR3pyCHLjm/) is from the Instagram feed +> of [e2_clothing](https://www.instagram.com/e2_clothing/). + + + diff --git a/markdown/org/showcase/liberty-trayvon/es.md b/markdown/org/showcase/liberty-trayvon/es.md new file mode 100644 index 00000000000..bf6530b6b8c --- /dev/null +++ b/markdown/org/showcase/liberty-trayvon/es.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "Beautiful fabric, and a greatly made tie" +date: "2017-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a4df7c8446671138fe4f6e07eebf32058af31999-1080x1080.jpg" +intro: "A Trayvon tie in a Liberty silk by Victoria [No traducido]" +title: "A Trayvon tie in a Liberty silk by Victoria [No traducido]" +--- + + +My husband travelled to Ireland 🇮🇪 for a weekend (62hrs travelling for 60hrs on the ground 🙀) to attend his brother's wedding 👏 +My contribution was this beautiful @libertylondon silk tie and pocket square made specifically for the big day. I was there in spirit. + +> ##### See the original on Instagram +> [This picture](https://www.instagram.com/p/BZR3pyCHLjm/) is from the Instagram feed +> of [e2_clothing](https://www.instagram.com/e2_clothing/). + + + diff --git a/markdown/org/showcase/liberty-trayvon/fr.md b/markdown/org/showcase/liberty-trayvon/fr.md new file mode 100644 index 00000000000..81c1cd80bce --- /dev/null +++ b/markdown/org/showcase/liberty-trayvon/fr.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Un beau tissu, et une super réalisation de cravate" +date: "2017-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a4df7c8446671138fe4f6e07eebf32058af31999-1080x1080.jpg" +intro: "Mon mari a voyagé en Irlande 🇮🇪 pour un week-end (62h de voyage pour 60h au sol 🙀) pour assister au mariage de son frère 👏 Ma contribution était cette belle cravate de soie de @libertylondon et un carré de poche faits spécialement pour ce grand jour. J'étais dans l'esprit." +title: "Une cravate Trayvon dans une soie Liberty par Victoria" +--- + + +Mon mari a voyagé en Irlande 🇮🇪 pour un week-end (62h de voyage pour 60h au sol 🙀) pour assister au mariage de son frère 👏 Ma contribution était cette belle cravate de soie de @libertylondon et un carré de poche faits spécialement pour ce grand jour. J'étais dans l'esprit. + +> ##### Voir l'original sur Instagram +> +> [Cette photo](https://www.instagram.com/p/BZR3pyCHLjm/) provient du feed Instagram de [e2_clothing](https://www.instagram.com/e2_clothing/). + + + diff --git a/markdown/org/showcase/liberty-trayvon/nl.md b/markdown/org/showcase/liberty-trayvon/nl.md new file mode 100644 index 00000000000..da6f44d4ea2 --- /dev/null +++ b/markdown/org/showcase/liberty-trayvon/nl.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Prachtige stof, en een goed gemaakte das" +date: "2017-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/a4df7c8446671138fe4f6e07eebf32058af31999-1080x1080.jpg" +intro: "Mijn echtgenoot reisde voor één weekend naar Ierland 🇮🇪(62 uur reizen om 60 uur ter plaatse te zijn 🙀) om naar het huwelijk van zijn broer te gaan 👏 Mijn bijdrage was deze mooie pochet en das in @libertylondonsilk, speciaal gemaakt voor de grote dag. Ik was in gedachten aanwezig." +title: "Een Trayvon das in Liberty zijde door Victoria" +--- + + +Mijn echtgenoot reisde voor één weekend naar Ierland 🇮🇪(62 uur reizen om 60 uur ter plaatse te zijn 🙀) om naar het huwelijk van zijn broer te gaan 👏 Mijn bijdrage was deze mooie pochet en das in @libertylondonsilk, speciaal gemaakt voor de grote dag. Ik was in gedachten aanwezig. + +> ##### Zie het origineel op Instagram +> +> [Deze afbeelding](https://www.instagram.com/p/BZR3pyCHLjm/) is afkomstig uit de Instagram feed van [e2_clothing](https://www.instagram.com/e2_clothing/). + + + diff --git a/markdown/org/showcase/linnen-jaeger-by-paul/de.md b/markdown/org/showcase/linnen-jaeger-by-paul/de.md new file mode 100644 index 00000000000..186def07c9b --- /dev/null +++ b/markdown/org/showcase/linnen-jaeger-by-paul/de.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Linnen Jaeger Sports Jacket by Paul" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9c349523bec04956439c08aded9408c5acd21a13-1640x2272.jpg" +intro: "FIXME_no_intro" +title: "[auf Englisch] Jaeger by Paul" +--- + + + diff --git a/markdown/org/showcase/linnen-jaeger-by-paul/en.md b/markdown/org/showcase/linnen-jaeger-by-paul/en.md new file mode 100644 index 00000000000..e28a25cd6d7 --- /dev/null +++ b/markdown/org/showcase/linnen-jaeger-by-paul/en.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "Linnen Jaeger Sports Jacket by Paul" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9c349523bec04956439c08aded9408c5acd21a13-1640x2272.jpg" +intro: "FIXME_no_intro" +title: "Jaeger by Paul" +--- + + diff --git a/markdown/org/showcase/linnen-jaeger-by-paul/es.md b/markdown/org/showcase/linnen-jaeger-by-paul/es.md new file mode 100644 index 00000000000..6e2ea2d3e07 --- /dev/null +++ b/markdown/org/showcase/linnen-jaeger-by-paul/es.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "Linnen Jaeger Sports Jacket by Paul" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9c349523bec04956439c08aded9408c5acd21a13-1640x2272.jpg" +intro: "FIXME_no_intro" +title: "Jaeger by Paul [No traducido]" +--- + + diff --git a/markdown/org/showcase/linnen-jaeger-by-paul/fr.md b/markdown/org/showcase/linnen-jaeger-by-paul/fr.md new file mode 100644 index 00000000000..9d2e8ae3a13 --- /dev/null +++ b/markdown/org/showcase/linnen-jaeger-by-paul/fr.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Veste Jaeger en lin par Paul" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9c349523bec04956439c08aded9408c5acd21a13-1640x2272.jpg" +intro: "FIXME_no_intro" +title: "Jaeger par Paul" +--- + + + diff --git a/markdown/org/showcase/linnen-jaeger-by-paul/nl.md b/markdown/org/showcase/linnen-jaeger-by-paul/nl.md new file mode 100644 index 00000000000..e00b7b9efbc --- /dev/null +++ b/markdown/org/showcase/linnen-jaeger-by-paul/nl.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Een linnen Jaeger jasje door Paul" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9c349523bec04956439c08aded9408c5acd21a13-1640x2272.jpg" +intro: "FIXME_no_intro" +title: "Jaeger door Paul" +--- + + + diff --git a/markdown/org/showcase/linnen-theo/de.md b/markdown/org/showcase/linnen-theo/de.md new file mode 100644 index 00000000000..27b4a685e53 --- /dev/null +++ b/markdown/org/showcase/linnen-theo/de.md @@ -0,0 +1,11 @@ +--- +maker: "Joost De Cock" +caption: "These are great in summer" +date: "2013-02-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/07536264d28ddbdfefb7c48a22e3cad6094b02da-2048x1365.jpg" +intro: "FIXME_no_intro" +title: "[auf Englisch] Brown greyish linnen Theo trousers by joostdecock" +--- + + + diff --git a/markdown/org/showcase/linnen-theo/en.md b/markdown/org/showcase/linnen-theo/en.md new file mode 100644 index 00000000000..0b6666a7812 --- /dev/null +++ b/markdown/org/showcase/linnen-theo/en.md @@ -0,0 +1,10 @@ +--- +maker: "Joost De Cock" +caption: "These are great in summer" +date: "2013-02-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/07536264d28ddbdfefb7c48a22e3cad6094b02da-2048x1365.jpg" +intro: "FIXME_no_intro" +title: "Brown greyish linnen Theo trousers by joostdecock" +--- + + diff --git a/markdown/org/showcase/linnen-theo/es.md b/markdown/org/showcase/linnen-theo/es.md new file mode 100644 index 00000000000..38607b6349f --- /dev/null +++ b/markdown/org/showcase/linnen-theo/es.md @@ -0,0 +1,10 @@ +--- +maker: "Joost De Cock" +caption: "These are great in summer" +date: "2013-02-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/07536264d28ddbdfefb7c48a22e3cad6094b02da-2048x1365.jpg" +intro: "FIXME_no_intro" +title: "Brown greyish linnen Theo trousers by joostdecock [No traducido]" +--- + + diff --git a/markdown/org/showcase/linnen-theo/fr.md b/markdown/org/showcase/linnen-theo/fr.md new file mode 100644 index 00000000000..c56dd2d4284 --- /dev/null +++ b/markdown/org/showcase/linnen-theo/fr.md @@ -0,0 +1,11 @@ +--- +maker: "Joost De Cock" +caption: "Celui-ci est génial en été" +date: "2013-02-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/07536264d28ddbdfefb7c48a22e3cad6094b02da-2048x1365.jpg" +intro: "FIXME_no_intro" +title: "Pantalon Theo en lin gris marron par joostdecock" +--- + + + diff --git a/markdown/org/showcase/linnen-theo/nl.md b/markdown/org/showcase/linnen-theo/nl.md new file mode 100644 index 00000000000..a82a99b753e --- /dev/null +++ b/markdown/org/showcase/linnen-theo/nl.md @@ -0,0 +1,10 @@ +--- +maker: "Joost De Cock" +caption: "These are great in summer" +date: "2013-02-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/07536264d28ddbdfefb7c48a22e3cad6094b02da-2048x1365.jpg" +intro: "FIXME_no_intro" +title: "Brown greyish linnen Theo trousers by joostdecock [Niet vertaald]" +--- + + diff --git a/markdown/org/showcase/mark-wears-simon/de.md b/markdown/org/showcase/mark-wears-simon/de.md new file mode 100644 index 00000000000..14a7f24ef4b --- /dev/null +++ b/markdown/org/showcase/mark-wears-simon/de.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "Good tie action too" +date: "2017-08-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8889aa644473d0615584ea0b69a570f95c69c1f9-1080x1080.jpg" +intro: "[auf Englisch] Mark wears a simon shirt made by his wife" +title: "[auf Englisch] Mark wears a simon shirt made by his wife" +--- + +![Another view](https://posts.freesewing.org/uploads/mark_wears_simon_2_a4950a3229.jpg "Another view") + +![And a back view](https://posts.freesewing.org/uploads/mark_wears_simon_3_9f40007ab0.jpg "And a back view") + +> ##### Check the original in the Instagram feed of swissarmywife +> +> This picture is from [the Instagram feed](https://www.instagram.com/p/BYAX07OFEPL/) of [swissarmywife](https://mnel2.wordpress.com/). It's posted here with permission. diff --git a/markdown/org/showcase/mark-wears-simon/en.md b/markdown/org/showcase/mark-wears-simon/en.md new file mode 100644 index 00000000000..d009cd26a3f --- /dev/null +++ b/markdown/org/showcase/mark-wears-simon/en.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Good tie action too" +date: "2017-08-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8889aa644473d0615584ea0b69a570f95c69c1f9-1080x1080.jpg" +intro: "Mark wears a simon shirt made by his wife" +title: "Mark wears a simon shirt made by his wife" +--- + +![Another view](https://posts.freesewing.org/uploads/mark_wears_simon_2_a4950a3229.jpg "Another view") + +![And a back view](https://posts.freesewing.org/uploads/mark_wears_simon_3_9f40007ab0.jpg "And a back view") + +> ##### Check the original in the Instagram feed of swissarmywife +> +> This picture is from [the Instagram feed](https://www.instagram.com/p/BYAX07OFEPL/) +> of [swissarmywife](https://mnel2.wordpress.com/). +> It's posted here with permission. diff --git a/markdown/org/showcase/mark-wears-simon/es.md b/markdown/org/showcase/mark-wears-simon/es.md new file mode 100644 index 00000000000..f504f2857f4 --- /dev/null +++ b/markdown/org/showcase/mark-wears-simon/es.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Good tie action too" +date: "2017-08-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8889aa644473d0615584ea0b69a570f95c69c1f9-1080x1080.jpg" +intro: "Mark wears a simon shirt made by his wife [No traducido]" +title: "Mark wears a simon shirt made by his wife [No traducido]" +--- + +![Another view](https://posts.freesewing.org/uploads/mark_wears_simon_2_a4950a3229.jpg "Another view") + +![And a back view](https://posts.freesewing.org/uploads/mark_wears_simon_3_9f40007ab0.jpg "And a back view") + +> ##### Check the original in the Instagram feed of swissarmywife +> +> This picture is from [the Instagram feed](https://www.instagram.com/p/BYAX07OFEPL/) +> of [swissarmywife](https://mnel2.wordpress.com/). +> It's posted here with permission. diff --git a/markdown/org/showcase/mark-wears-simon/fr.md b/markdown/org/showcase/mark-wears-simon/fr.md new file mode 100644 index 00000000000..44c1fd0cca3 --- /dev/null +++ b/markdown/org/showcase/mark-wears-simon/fr.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "Jolie cravate aussi" +date: "2017-08-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8889aa644473d0615584ea0b69a570f95c69c1f9-1080x1080.jpg" +intro: "Mark porte une chemise Simon faite par sa femme" +title: "Mark porte une chemise Simon faite par sa femme" +--- + +![Une autre vue](https://posts.freesewing.org/uploads/mark_wears_simon_2_a4950a3229.jpg "Une autre vue") + +![Et une vue de dos](https://posts.freesewing.org/uploads/mark_wears_simon_3_9f40007ab0.jpg "Et une vue de dos") + +> ##### Consultez l'original dans le feed Instagram de swissarmywife +> +> Cette photo provient du [feed Instagram](https://www.instagram.com/p/BYAX07OFEPL/) de [swissarmywife](https://mnel2.wordpress.com/). Elle est publiée ici avec son autorisation. diff --git a/markdown/org/showcase/mark-wears-simon/nl.md b/markdown/org/showcase/mark-wears-simon/nl.md new file mode 100644 index 00000000000..c62b6f37f5b --- /dev/null +++ b/markdown/org/showcase/mark-wears-simon/nl.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "Goeie das ook" +date: "2017-08-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8889aa644473d0615584ea0b69a570f95c69c1f9-1080x1080.jpg" +intro: "Mark draagt een Simon hemd, gemaakt door zijn vrouw" +title: "Mark draagt een Simon hemd, gemaakt door zijn vrouw" +--- + +![Een andere kant](https://posts.freesewing.org/uploads/mark_wears_simon_2_a4950a3229.jpg "Een andere kant") + +![En de achterkant](https://posts.freesewing.org/uploads/mark_wears_simon_3_9f40007ab0.jpg "En de achterkant") + +> ##### Bekijk het origineel in de Instagram feed van swissarmywife +> +> This picture is from [the Instagram feed](https://www.instagram.com/p/BYAX07OFEPL/) of [swissarmywife](https://mnel2.wordpress.com/). It's posted here with permission. diff --git a/markdown/org/showcase/matching-simon/de.md b/markdown/org/showcase/matching-simon/de.md new file mode 100644 index 00000000000..2602ead5e4a --- /dev/null +++ b/markdown/org/showcase/matching-simon/de.md @@ -0,0 +1,29 @@ +--- +maker: "unknown" +caption: "Is it me, or does this seriously overload one's cute sensors?" +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0d0673d758bb9ec6f60c01db5dba00a0d3fea7ee-1080x1080.jpg" +intro: "[auf Englisch] Matching simon shirts for these two cuties" +title: "[auf Englisch] Matching simon shirts for these two cuties" +--- + +![Model + tapemeasure](https://posts.freesewing.org/uploads/matching_simon_view2_07c4206346.jpg "Model + tapemeasure") + +![That fabric is gorgeous](view3.jpg) + +![Schulterneigung](view4.jpg) + +![View from the back](view5.jpg) + +![Hi camera](view6.jpg) + + + +###### See the originals on the Instragram feed of ecmtts + +These images are from +[the Instagram feed](https://www.instagram.com/ecmtts/) +of [@ericamattos](/users/ericamattos). +They are published here with permission. + + diff --git a/markdown/org/showcase/matching-simon/en.md b/markdown/org/showcase/matching-simon/en.md new file mode 100644 index 00000000000..0af83a31348 --- /dev/null +++ b/markdown/org/showcase/matching-simon/en.md @@ -0,0 +1,29 @@ +--- +maker: "unknown" +caption: "Is it me, or does this seriously overload one's cute sensors?" +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0d0673d758bb9ec6f60c01db5dba00a0d3fea7ee-1080x1080.jpg" +intro: "Matching simon shirts for these two cuties" +title: "Matching simon shirts for these two cuties" +--- + +![Model + tapemeasure](https://posts.freesewing.org/uploads/matching_simon_view2_07c4206346.jpg "Model + tapemeasure") + +![That fabric is gorgeous](https://posts.freesewing.org/uploads/matching_simon_view3_6be104bac1.jpg "That fabric is gorgeous") + +![Shoulder slope](https://posts.freesewing.org/uploads/matching_simon_view4_df63556bdf.jpg "Shoulder slope") + +![View from the back](https://posts.freesewing.org/uploads/matching_simon_view5_2e3b570060.jpg "View from the back") + +![Hi camera](https://posts.freesewing.org/uploads/matching_simon_view6_1b0caef89f.jpg) + + + +###### See the originals on the Instragram feed of ecmtts + +These images are from +[the Instagram feed](https://www.instagram.com/ecmtts/) +of [@ericamattos](/users/ericamattos). +They are published here with permission. + + diff --git a/markdown/org/showcase/matching-simon/es.md b/markdown/org/showcase/matching-simon/es.md new file mode 100644 index 00000000000..a812127f004 --- /dev/null +++ b/markdown/org/showcase/matching-simon/es.md @@ -0,0 +1,29 @@ +--- +maker: "unknown" +caption: "Is it me, or does this seriously overload one's cute sensors?" +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0d0673d758bb9ec6f60c01db5dba00a0d3fea7ee-1080x1080.jpg" +intro: "Matching simon shirts for these two cuties [No traducido]" +title: "Matching simon shirts for these two cuties [No traducido]" +--- + +![Model + tapemeasure](https://posts.freesewing.org/uploads/matching_simon_view2_07c4206346.jpg "Model + tapemeasure") + +![That fabric is gorgeous](https://posts.freesewing.org/uploads/matching_simon_view3_6be104bac1.jpg "That fabric is gorgeous") + +![Shoulder slope](https://posts.freesewing.org/uploads/matching_simon_view4_df63556bdf.jpg "Shoulder slope") + +![View from the back](https://posts.freesewing.org/uploads/matching_simon_view5_2e3b570060.jpg "View from the back") + +![Hi camera](https://posts.freesewing.org/uploads/matching_simon_view6_1b0caef89f.jpg) + + + +###### See the originals on the Instragram feed of ecmtts + +These images are from +[the Instagram feed](https://www.instagram.com/ecmtts/) +of [@ericamattos](/users/ericamattos). +They are published here with permission. + + diff --git a/markdown/org/showcase/matching-simon/fr.md b/markdown/org/showcase/matching-simon/fr.md new file mode 100644 index 00000000000..d7475c09b21 --- /dev/null +++ b/markdown/org/showcase/matching-simon/fr.md @@ -0,0 +1,29 @@ +--- +maker: "unknown" +caption: "Est-ce moi, ou est-ce que ça fait sérieusement grimper les capteurs de mignonitude ?" +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0d0673d758bb9ec6f60c01db5dba00a0d3fea7ee-1080x1080.jpg" +intro: "Chemises Simon assorties pour ces deux beaux-gosses" +title: "Chemises Simon assorties pour ces deux beaux-gosses" +--- + +![Modèle + mètre-ruban](https://posts.freesewing.org/uploads/matching_simon_view2_07c4206346.jpg "Modèle + mètre-ruban") + +![Ce tissu est magnifique](https://posts.freesewing.org/uploads/matching_simon_view3_6be104bac1.jpg "Ce tissu est magnifique") + +![Pente d'épaule](https://posts.freesewing.org/uploads/matching_simon_view4_df63556bdf.jpg "Pente d'épaule") + +![Vue du dos](https://posts.freesewing.org/uploads/matching_simon_view5_2e3b570060.jpg "Vue du dos") + +![Salut la caméra](https://posts.freesewing.org/uploads/matching_simon_view6_1b0caef89f.jpg "Salut la caméra") + + + +###### Voir les originaux sur le feed Instragram d'ecmtts + +Ces images proviennent du +[feed Instagram](https://www.instagram.com/ecmtts/) +de [@ericamattos](/users/ericamattos). +Elles sont repostées ici avec autorisation. + + diff --git a/markdown/org/showcase/matching-simon/nl.md b/markdown/org/showcase/matching-simon/nl.md new file mode 100644 index 00000000000..a0b14f1f1f4 --- /dev/null +++ b/markdown/org/showcase/matching-simon/nl.md @@ -0,0 +1,29 @@ +--- +maker: "unknown" +caption: "Ligt het aan mij, of is dit te veel schattigheid?" +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0d0673d758bb9ec6f60c01db5dba00a0d3fea7ee-1080x1080.jpg" +intro: "Matchende Simon hemden voor deze twee schatjes" +title: "Matchende Simon hemden voor deze twee schatjes" +--- + +![Model + lintmeter](https://posts.freesewing.org/uploads/matching_simon_view2_07c4206346.jpg "Model + lintmeter") + +![Deze stof is prachtig](https://posts.freesewing.org/uploads/matching_simon_view3_6be104bac1.jpg "Deze stof is prachtig") + +![Schouderhelling](https://posts.freesewing.org/uploads/matching_simon_view4_df63556bdf.jpg "Schouderhelling") + +![Achterkant](https://posts.freesewing.org/uploads/matching_simon_view5_2e3b570060.jpg "Achterkant") + +![Hallo camera](https://posts.freesewing.org/uploads/matching_simon_view6_1b0caef89f.jpg "Hallo camera") + + + +###### See the originals on the Instragram feed of ecmtts + +These images are from +[the Instagram feed](https://www.instagram.com/ecmtts/) +of [@ericamattos](/users/ericamattos). +They are published here with permission. + + diff --git a/markdown/org/showcase/more-wahid-by-adam/de.md b/markdown/org/showcase/more-wahid-by-adam/de.md new file mode 100644 index 00000000000..6b5ad287f57 --- /dev/null +++ b/markdown/org/showcase/more-wahid-by-adam/de.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "So. Much. Style." +date: "2020-08-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/be12610ca753f520a5ddebc6f034358551d9939c-1080x1349.jpg" +intro: "After his first jaw-dropping Wahid Adam is back with another beauty." +title: "[auf Englisch] Another Wahid waistcoat by Adam" +--- + + +After [his first jaw-dropping Wahid](/showcase/wahid-by-adam/) Adam is back with another beauty. + + + +This picture is from the [the Instagram feed](https://www.instagram.com/p/CDPh9MbhWuH/) of [Adam Bradley](https://www.instagram.com/grandmarquess/). +It is posted here with permission. + + + diff --git a/markdown/org/showcase/more-wahid-by-adam/en.md b/markdown/org/showcase/more-wahid-by-adam/en.md new file mode 100644 index 00000000000..aa19587dc43 --- /dev/null +++ b/markdown/org/showcase/more-wahid-by-adam/en.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "So. Much. Style." +date: "2020-08-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/be12610ca753f520a5ddebc6f034358551d9939c-1080x1349.jpg" +intro: "After his first jaw-dropping Wahid Adam is back with another beauty." +title: "Another Wahid waistcoat by Adam" +--- + + +After [his first jaw-dropping Wahid](/showcase/wahid-by-adam/) Adam is back with another beauty. + + + +This picture is from the [the Instagram feed](https://www.instagram.com/p/CDPh9MbhWuH/) of [Adam Bradley](https://www.instagram.com/grandmarquess/). +It is posted here with permission. + + + diff --git a/markdown/org/showcase/more-wahid-by-adam/es.md b/markdown/org/showcase/more-wahid-by-adam/es.md new file mode 100644 index 00000000000..281ce78d5e9 --- /dev/null +++ b/markdown/org/showcase/more-wahid-by-adam/es.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "So. Much. Style." +date: "2020-08-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/be12610ca753f520a5ddebc6f034358551d9939c-1080x1349.jpg" +intro: "After his first jaw-dropping Wahid Adam is back with another beauty." +title: "Another Wahid waistcoat by Adam [No traducido]" +--- + + +After [his first jaw-dropping Wahid](/showcase/wahid-by-adam/) Adam is back with another beauty. + + + +This picture is from the [the Instagram feed](https://www.instagram.com/p/CDPh9MbhWuH/) of [Adam Bradley](https://www.instagram.com/grandmarquess/). +It is posted here with permission. + + + diff --git a/markdown/org/showcase/more-wahid-by-adam/fr.md b/markdown/org/showcase/more-wahid-by-adam/fr.md new file mode 100644 index 00000000000..809206581a4 --- /dev/null +++ b/markdown/org/showcase/more-wahid-by-adam/fr.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "Trop. De. Style." +date: "2020-08-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/be12610ca753f520a5ddebc6f034358551d9939c-1080x1349.jpg" +intro: "Après son premier Wahid à couper le souffle Adam est de retour avec une autre beauté." +title: "Un autre gilet Wahid par Adam" +--- + + +Après [son premier Wahid à couper le souffle](/showcase/wahid-by-adam/) Adam est de retour avec une autre beauté. + + + +Cette image provient du [flux Instagram ](https://www.instagram.com/p/CDPh9MbhWuH/) de [Adam Bradley](https://www.instagram.com/grandmarquess/). +Elle est publiée ici avec son autorisation. + + + diff --git a/markdown/org/showcase/more-wahid-by-adam/nl.md b/markdown/org/showcase/more-wahid-by-adam/nl.md new file mode 100644 index 00000000000..38770feada8 --- /dev/null +++ b/markdown/org/showcase/more-wahid-by-adam/nl.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "Zo. Veel. Stijl." +date: "2020-08-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/be12610ca753f520a5ddebc6f034358551d9939c-1080x1349.jpg" +intro: "Na zijn eerste adembenemende Wahid is Adam terug met alweer een schoonheid." +title: "Nog een Wahid gilet door Adam" +--- + + +Na zijn [eerste adembenemende Wahid](/showcase/wahid-by-adam/) is Adam terug met alweer een schoonheid. + + + +Deze foto komt van de [the Instagram feed](https://www.instagram.com/p/CDPh9MbhWuH/) van [Adam Bradley](https://www.instagram.com/grandmarquess/). +Ze is hier gepost met toestemming. + + + diff --git a/markdown/org/showcase/nani-hugo/de.md b/markdown/org/showcase/nani-hugo/de.md new file mode 100644 index 00000000000..132db39773a --- /dev/null +++ b/markdown/org/showcase/nani-hugo/de.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "This is a very cool make IMHO" +date: "2016-03-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e2c7db3528aef1f3ae0a74e0a9ecce543b3cbd7a-1080x1080.jpg" +intro: "FIXME_no_intro" +title: "[auf Englisch] Hugo hacked into a zip-up hoodie by Nani Roma" +--- + + + diff --git a/markdown/org/showcase/nani-hugo/en.md b/markdown/org/showcase/nani-hugo/en.md new file mode 100644 index 00000000000..32683f8ac41 --- /dev/null +++ b/markdown/org/showcase/nani-hugo/en.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "This is a very cool make IMHO" +date: "2016-03-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e2c7db3528aef1f3ae0a74e0a9ecce543b3cbd7a-1080x1080.jpg" +intro: "FIXME_no_intro" +title: "Hugo hacked into a zip-up hoodie by Nani Roma" +--- + + diff --git a/markdown/org/showcase/nani-hugo/es.md b/markdown/org/showcase/nani-hugo/es.md new file mode 100644 index 00000000000..130d963e118 --- /dev/null +++ b/markdown/org/showcase/nani-hugo/es.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "This is a very cool make IMHO" +date: "2016-03-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e2c7db3528aef1f3ae0a74e0a9ecce543b3cbd7a-1080x1080.jpg" +intro: "FIXME_no_intro" +title: "Hugo hacked into a zip-up hoodie by Nani Roma [No traducido]" +--- + + diff --git a/markdown/org/showcase/nani-hugo/fr.md b/markdown/org/showcase/nani-hugo/fr.md new file mode 100644 index 00000000000..2b7cf3316d6 --- /dev/null +++ b/markdown/org/showcase/nani-hugo/fr.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "C'est une réalisation très cool je trouve" +date: "2016-03-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e2c7db3528aef1f3ae0a74e0a9ecce543b3cbd7a-1080x1080.jpg" +intro: "FIXME_no_intro" +title: "Hugo hacké en sweat à capuche zippée par Nani Roma" +--- + + + diff --git a/markdown/org/showcase/nani-hugo/nl.md b/markdown/org/showcase/nani-hugo/nl.md new file mode 100644 index 00000000000..0d384bd1a27 --- /dev/null +++ b/markdown/org/showcase/nani-hugo/nl.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Dit vind ik heel cool" +date: "2016-03-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e2c7db3528aef1f3ae0a74e0a9ecce543b3cbd7a-1080x1080.jpg" +intro: "FIXME_no_intro" +title: "Hugo als hoodie met rits door Nani Roma" +--- + + + diff --git a/markdown/org/showcase/nsfw-bruce/de.md b/markdown/org/showcase/nsfw-bruce/de.md new file mode 100644 index 00000000000..0372326e044 --- /dev/null +++ b/markdown/org/showcase/nsfw-bruce/de.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Depending on your job, this might be NSFW" +date: "2014-09-15" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1fb10c7a92f51c9184a5e9f9476ec836794a68d5-1920x1020.jpg" +intro: "FIXME_no_intro" +title: "[auf Englisch] The lesser-spotted shot of Bruce on an actual human being" +--- + + + diff --git a/markdown/org/showcase/nsfw-bruce/en.md b/markdown/org/showcase/nsfw-bruce/en.md new file mode 100644 index 00000000000..63dea7b624c --- /dev/null +++ b/markdown/org/showcase/nsfw-bruce/en.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "Depending on your job, this might be NSFW" +date: "2014-09-15" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1fb10c7a92f51c9184a5e9f9476ec836794a68d5-1920x1020.jpg" +intro: "FIXME_no_intro" +title: "The lesser-spotted shot of Bruce on an actual human being" +--- + + diff --git a/markdown/org/showcase/nsfw-bruce/es.md b/markdown/org/showcase/nsfw-bruce/es.md new file mode 100644 index 00000000000..de545099f40 --- /dev/null +++ b/markdown/org/showcase/nsfw-bruce/es.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "Depending on your job, this might be NSFW" +date: "2014-09-15" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1fb10c7a92f51c9184a5e9f9476ec836794a68d5-1920x1020.jpg" +intro: "FIXME_no_intro" +title: "The lesser-spotted shot of Bruce on an actual human being [No traducido]" +--- + + diff --git a/markdown/org/showcase/nsfw-bruce/fr.md b/markdown/org/showcase/nsfw-bruce/fr.md new file mode 100644 index 00000000000..e253dd50b85 --- /dev/null +++ b/markdown/org/showcase/nsfw-bruce/fr.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Selon votre travail, cela pourrait être une tenue indécente" +date: "2014-09-15" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1fb10c7a92f51c9184a5e9f9476ec836794a68d5-1920x1020.jpg" +intro: "FIXME_no_intro" +title: "La vue la plus plongeante de Bruce sur un être humain" +--- + + + diff --git a/markdown/org/showcase/nsfw-bruce/nl.md b/markdown/org/showcase/nsfw-bruce/nl.md new file mode 100644 index 00000000000..8927d6fce05 --- /dev/null +++ b/markdown/org/showcase/nsfw-bruce/nl.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Afhankelijk van je job is dit misschien NSFW" +date: "2014-09-15" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1fb10c7a92f51c9184a5e9f9476ec836794a68d5-1920x1020.jpg" +intro: "FIXME_no_intro" +title: "Een zeldzame waarneming van Bruce op een menselijk model" +--- + + + diff --git a/markdown/org/showcase/outfit-wahid-theo-florent-by-paul/de.md b/markdown/org/showcase/outfit-wahid-theo-florent-by-paul/de.md new file mode 100644 index 00000000000..b394e63c11c --- /dev/null +++ b/markdown/org/showcase/outfit-wahid-theo-florent-by-paul/de.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Outfit - Florent, Theodore & Wahid by Paul" +date: "2018-01-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6e7cb0f6aee7fd430e5f8cff0c3351073c35b313-2000x2793.jpg" +intro: "[auf Englisch] Outfit - Florent, Theodore & Wahid by Paul" +title: "[auf Englisch] Outfit - Florent, Theodore & Wahid by Paul" +--- + +![Outfit by Paul](/img/showcase/outfit-wahid-theodore-florent-by-paul/high_back.jpg "Outfit by Paul") + +![Outfit by Paul](/img/showcase/outfit-wahid-theodore-florent-by-paul/high_front.jpg) diff --git a/markdown/org/showcase/outfit-wahid-theo-florent-by-paul/en.md b/markdown/org/showcase/outfit-wahid-theo-florent-by-paul/en.md new file mode 100644 index 00000000000..1782b834c4f --- /dev/null +++ b/markdown/org/showcase/outfit-wahid-theo-florent-by-paul/en.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Outfit - Florent, Theodore & Wahid by Paul" +date: "2018-01-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6e7cb0f6aee7fd430e5f8cff0c3351073c35b313-2000x2793.jpg" +intro: "Outfit - Florent, Theodore & Wahid by Paul" +title: "Outfit - Florent, Theodore & Wahid by Paul" +--- + +![Outfit by Paul](/img/showcase/outfit-wahid-theodore-florent-by-paul/high_back.jpg "Outfit by Paul") + +![Outfit by Paul](/img/showcase/outfit-wahid-theodore-florent-by-paul/high_front.jpg "Outfit by Paul") diff --git a/markdown/org/showcase/outfit-wahid-theo-florent-by-paul/fr.md b/markdown/org/showcase/outfit-wahid-theo-florent-by-paul/fr.md new file mode 100644 index 00000000000..48a71dee751 --- /dev/null +++ b/markdown/org/showcase/outfit-wahid-theo-florent-by-paul/fr.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Ensemble - Florent, Theodore & Wahid par Paul" +date: "2018-01-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6e7cb0f6aee7fd430e5f8cff0c3351073c35b313-2000x2793.jpg" +intro: "Ensemble - Florent, Theodore & Wahid par Paul" +title: "Ensemble - Florent, Theodore & Wahid par Paul" +--- + +![Tenue par Paul](/img/showcase/outfit-wahid-theodore-florent-by-paul/high_back.jpg "Tenue par Paul") + +![Tenue par Paul](/img/showcase/outfit-wahid-theodore-florent-by-paul/high_front.jpg) diff --git a/markdown/org/showcase/outfit-wahid-theo-florent-by-paul/nl.md b/markdown/org/showcase/outfit-wahid-theo-florent-by-paul/nl.md new file mode 100644 index 00000000000..7a57b5c0271 --- /dev/null +++ b/markdown/org/showcase/outfit-wahid-theo-florent-by-paul/nl.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Outfit - Florent, Theodore & Wahid door paul" +date: "2018-01-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6e7cb0f6aee7fd430e5f8cff0c3351073c35b313-2000x2793.jpg" +intro: "Outfit - Florent, Theodore & Wahid door paul" +title: "Outfit - Florent, Theodore & Wahid door paul" +--- + +![Outfit door Paul](/img/showcase/outfit-wahid-theodore-florent-by-paul/high_back.jpg "Outfit door Paul") + +![Outfit door Paul](/img/showcase/outfit-wahid-theodore-florent-by-paul/high_front.jpg) diff --git a/markdown/org/showcase/outfit-wahid-theo-simon-by-paul/de.md b/markdown/org/showcase/outfit-wahid-theo-simon-by-paul/de.md new file mode 100644 index 00000000000..eb5f461e294 --- /dev/null +++ b/markdown/org/showcase/outfit-wahid-theo-simon-by-paul/de.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "Outfit - Simon, Theo & Wahid by Paul" +date: "2018-01-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4cf88b3cad5a8920a471a984b172e8f0fc7cee32-2000x2666.jpg" +intro: "Outfit - Simon, Theo & Wahid by Paul [Nicht übersetzt]" +title: "Outfit - Simon, Theo & Wahid by Paul [Nicht übersetzt]" +--- + +![Outfit by Paul](https://posts.freesewing.org/uploads/outfit_wahid_theo_simon_by_paul_high_back_808c2ace5b.jpg "Outfit by Paul") diff --git a/markdown/org/showcase/outfit-wahid-theo-simon-by-paul/en.md b/markdown/org/showcase/outfit-wahid-theo-simon-by-paul/en.md new file mode 100644 index 00000000000..2307750b498 --- /dev/null +++ b/markdown/org/showcase/outfit-wahid-theo-simon-by-paul/en.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "Outfit - Simon, Theo & Wahid by Paul" +date: "2018-01-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4cf88b3cad5a8920a471a984b172e8f0fc7cee32-2000x2666.jpg" +intro: "Outfit - Simon, Theo & Wahid by Paul" +title: "Outfit - Simon, Theo & Wahid by Paul" +--- + +![Outfit by Paul](https://posts.freesewing.org/uploads/outfit_wahid_theo_simon_by_paul_high_back_808c2ace5b.jpg "Outfit by Paul") diff --git a/markdown/org/showcase/outfit-wahid-theo-simon-by-paul/es.md b/markdown/org/showcase/outfit-wahid-theo-simon-by-paul/es.md new file mode 100644 index 00000000000..4265f7a2f2c --- /dev/null +++ b/markdown/org/showcase/outfit-wahid-theo-simon-by-paul/es.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "Outfit - Simon, Theo & Wahid by Paul" +date: "2018-01-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4cf88b3cad5a8920a471a984b172e8f0fc7cee32-2000x2666.jpg" +intro: "Outfit - Simon, Theo & Wahid by Paul [No traducido]" +title: "Outfit - Simon, Theo & Wahid by Paul [No traducido]" +--- + +![Outfit by Paul](https://posts.freesewing.org/uploads/outfit_wahid_theo_simon_by_paul_high_back_808c2ace5b.jpg "Outfit by Paul") diff --git a/markdown/org/showcase/outfit-wahid-theo-simon-by-paul/fr.md b/markdown/org/showcase/outfit-wahid-theo-simon-by-paul/fr.md new file mode 100644 index 00000000000..23477c17063 --- /dev/null +++ b/markdown/org/showcase/outfit-wahid-theo-simon-by-paul/fr.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "Outfit - Simon, Theo & Wahid by Paul" +date: "2018-01-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4cf88b3cad5a8920a471a984b172e8f0fc7cee32-2000x2666.jpg" +intro: "Outfit - Simon, Theo & Wahid by Paul [Non traduit]" +title: "Outfit - Simon, Theo & Wahid by Paul [Non traduit]" +--- + +![Outfit by Paul](https://posts.freesewing.org/uploads/outfit_wahid_theo_simon_by_paul_high_back_808c2ace5b.jpg "Outfit by Paul") diff --git a/markdown/org/showcase/paco-by-joost/de.md b/markdown/org/showcase/paco-by-joost/de.md new file mode 100644 index 00000000000..78be620bd08 --- /dev/null +++ b/markdown/org/showcase/paco-by-joost/de.md @@ -0,0 +1,14 @@ +--- +maker: "Joost De Cock" +caption: "These Paco pants were the initial test for this pattern" +date: "2020-08-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1bc82d4abb50ea1b7bda32dd64521e9ecfdd8467-2048x1536.jpg" +intro: "Here's the very first Paco pair I've made. These ones have side pockets, no back pockets, and an elasticated hem." +title: "[auf Englisch] Joost does Paco" +--- + + +Here's the very first Paco pair I've made. These ones have side pockets, no back pockets, and an elasticated hem. + +In other words, these are made with all default options. + diff --git a/markdown/org/showcase/paco-by-joost/en.md b/markdown/org/showcase/paco-by-joost/en.md new file mode 100644 index 00000000000..d6980d979ba --- /dev/null +++ b/markdown/org/showcase/paco-by-joost/en.md @@ -0,0 +1,14 @@ +--- +maker: "Joost De Cock" +caption: "These Paco pants were the initial test for this pattern" +date: "2020-08-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1bc82d4abb50ea1b7bda32dd64521e9ecfdd8467-2048x1536.jpg" +intro: "Here's the very first Paco pair I've made. These ones have side pockets, no back pockets, and an elasticated hem." +title: "Joost does Paco" +--- + + +Here's the very first Paco pair I've made. These ones have side pockets, no back pockets, and an elasticated hem. + +In other words, these are made with all default options. + diff --git a/markdown/org/showcase/paco-by-joost/es.md b/markdown/org/showcase/paco-by-joost/es.md new file mode 100644 index 00000000000..5d4c5fdf194 --- /dev/null +++ b/markdown/org/showcase/paco-by-joost/es.md @@ -0,0 +1,14 @@ +--- +maker: "Joost De Cock" +caption: "These Paco pants were the initial test for this pattern" +date: "2020-08-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1bc82d4abb50ea1b7bda32dd64521e9ecfdd8467-2048x1536.jpg" +intro: "Here's the very first Paco pair I've made. These ones have side pockets, no back pockets, and an elasticated hem." +title: "Joost does Paco [No traducido]" +--- + + +Here's the very first Paco pair I've made. These ones have side pockets, no back pockets, and an elasticated hem. + +In other words, these are made with all default options. + diff --git a/markdown/org/showcase/paco-by-joost/fr.md b/markdown/org/showcase/paco-by-joost/fr.md new file mode 100644 index 00000000000..a94832a1f42 --- /dev/null +++ b/markdown/org/showcase/paco-by-joost/fr.md @@ -0,0 +1,14 @@ +--- +maker: "Joost De Cock" +caption: "Ce pantalon Paco a été le premier test pour ce patron" +date: "2020-08-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1bc82d4abb50ea1b7bda32dd64521e9ecfdd8467-2048x1536.jpg" +intro: "Voici la toute première version de Paco que j'ai faite. Celui-ci a des poches latérales, pas de poches arrière, et une ceinture élastique." +title: "Joost fait Paco" +--- + + +Voici la toute première version de Paco que j'ai faite. Celui-ci a des poches latérales, pas de poches arrière, et une ceinture élastique. + +En d'autres termes, il est fait avec toutes les options par défaut. + diff --git a/markdown/org/showcase/paco-by-joost/nl.md b/markdown/org/showcase/paco-by-joost/nl.md new file mode 100644 index 00000000000..e15fba0e6cc --- /dev/null +++ b/markdown/org/showcase/paco-by-joost/nl.md @@ -0,0 +1,14 @@ +--- +maker: "Joost De Cock" +caption: "Deze Paco broek was de initiële test voor dit patroon" +date: "2020-08-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1bc82d4abb50ea1b7bda32dd64521e9ecfdd8467-2048x1536.jpg" +intro: "Hier is de eerste Paco broek die ik ooit gemaakt heb. De broek heeft zakken in de zijnaad, geen achterzakken, en een elastische zoom." +title: "Joost doet Paco" +--- + + +Hier is de eerste Paco broek die ik ooit gemaakt heb. De broek heeft zakken in de zijnaad, geen achterzakken, en een elastische zoom. + +Met andere woorden, deze zijn gemaakt met alle standaardopties. + diff --git a/markdown/org/showcase/paco-by-karen/de.md b/markdown/org/showcase/paco-by-karen/de.md new file mode 100644 index 00000000000..231c63d3b07 --- /dev/null +++ b/markdown/org/showcase/paco-by-karen/de.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Rayon Paco pants in a dark floral print" +date: "2021-04-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9255d1162b83bc4691a6029126944d2e714d33e1-1539x1800.jpg" +intro: "The Pacos were made in a rayon challis, with the default options (and the front rise lowered a touch). They're modelled here with a bonus Teagan T-shirt." +title: "[auf Englisch] Tropical Pacos" +--- + +The Pacos were made in a rayon challis, with the default options (and the front rise lowered a touch). They're modelled here with a bonus Teagan T-shirt. + +![Paco front view](https://posts.freesewing.org/uploads/paco_by_karen_showcase2_85c38807f6.jpeg "Paco front view") + +Some additional views... + +![Paco rear view](https://posts.freesewing.org/uploads/paco_by_karen_showcase3_ae80f66814.jpeg "Paco rear view") + +![Paco side view](https://posts.freesewing.org/uploads/paco_by_karen_showcase4_3a7cb22fff.jpeg "Paco side view") diff --git a/markdown/org/showcase/paco-by-karen/en.md b/markdown/org/showcase/paco-by-karen/en.md new file mode 100644 index 00000000000..6f53cc5827a --- /dev/null +++ b/markdown/org/showcase/paco-by-karen/en.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Rayon Paco pants in a dark floral print" +date: "2021-04-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9255d1162b83bc4691a6029126944d2e714d33e1-1539x1800.jpg" +intro: "The Pacos were made in a rayon challis, with the default options (and the front rise lowered a touch). They're modelled here with a bonus Teagan T-shirt." +title: "Tropical Pacos" +--- + +The Pacos were made in a rayon challis, with the default options (and the front rise lowered a touch). They're modelled here with a bonus Teagan T-shirt. + +![Paco front view](https://posts.freesewing.org/uploads/paco_by_karen_showcase2_85c38807f6.jpeg "Paco front view") + +Some additional views... + +![Paco rear view](https://posts.freesewing.org/uploads/paco_by_karen_showcase3_ae80f66814.jpeg) + +![Paco side view](https://posts.freesewing.org/uploads/paco_by_karen_showcase4_3a7cb22fff.jpeg) diff --git a/markdown/org/showcase/paco-by-karen/es.md b/markdown/org/showcase/paco-by-karen/es.md new file mode 100644 index 00000000000..321c2ce2456 --- /dev/null +++ b/markdown/org/showcase/paco-by-karen/es.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Rayon Paco pants in a dark floral print" +date: "2021-04-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9255d1162b83bc4691a6029126944d2e714d33e1-1539x1800.jpg" +intro: "The Pacos were made in a rayon challis, with the default options (and the front rise lowered a touch). They're modelled here with a bonus Teagan T-shirt." +title: "Tropical Pacos [No traducido]" +--- + +The Pacos were made in a rayon challis, with the default options (and the front rise lowered a touch). They're modelled here with a bonus Teagan T-shirt. + +![Paco front view](https://posts.freesewing.org/uploads/paco_by_karen_showcase2_85c38807f6.jpeg "Paco front view") + +Some additional views... + +![Paco rear view](https://posts.freesewing.org/uploads/paco_by_karen_showcase3_ae80f66814.jpeg) + +![Paco side view](https://posts.freesewing.org/uploads/paco_by_karen_showcase4_3a7cb22fff.jpeg) diff --git a/markdown/org/showcase/paco-by-karen/fr.md b/markdown/org/showcase/paco-by-karen/fr.md new file mode 100644 index 00000000000..5a91a3456e3 --- /dev/null +++ b/markdown/org/showcase/paco-by-karen/fr.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Rayon Paco pants in a dark floral print" +date: "2021-04-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9255d1162b83bc4691a6029126944d2e714d33e1-1539x1800.jpg" +intro: "The Pacos were made in a rayon challis, with the default options (and the front rise lowered a touch). They're modelled here with a bonus Teagan T-shirt." +title: "[En anglais] Tropical Pacos" +--- + +The Pacos were made in a rayon challis, with the default options (and the front rise lowered a touch). They're modelled here with a bonus Teagan T-shirt. + +![Paco front view](https://posts.freesewing.org/uploads/paco_by_karen_showcase2_85c38807f6.jpeg "Paco front view") + +Some additional views... + +![Paco rear view](https://posts.freesewing.org/uploads/paco_by_karen_showcase3_ae80f66814.jpeg "Paco rear view") + +![Paco side view](https://posts.freesewing.org/uploads/paco_by_karen_showcase4_3a7cb22fff.jpeg "Paco side view") diff --git a/markdown/org/showcase/paco-by-karen/nl.md b/markdown/org/showcase/paco-by-karen/nl.md new file mode 100644 index 00000000000..9f105c3ab4d --- /dev/null +++ b/markdown/org/showcase/paco-by-karen/nl.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Rayon Paco pants in a dark floral print" +date: "2021-04-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/9255d1162b83bc4691a6029126944d2e714d33e1-1539x1800.jpg" +intro: "The Pacos were made in a rayon challis, with the default options (and the front rise lowered a touch). They're modelled here with a bonus Teagan T-shirt." +title: "Tropical Pacos [Niet vertaald]" +--- + +The Pacos were made in a rayon challis, with the default options (and the front rise lowered a touch). They're modelled here with a bonus Teagan T-shirt. + +![Paco front view](https://posts.freesewing.org/uploads/paco_by_karen_showcase2_85c38807f6.jpeg "Paco front view") + +Some additional views... + +![Paco rear view](https://posts.freesewing.org/uploads/paco_by_karen_showcase3_ae80f66814.jpeg) + +![Paco side view](https://posts.freesewing.org/uploads/paco_by_karen_showcase4_3a7cb22fff.jpeg) diff --git a/markdown/org/showcase/pirate-bruce/de.md b/markdown/org/showcase/pirate-bruce/de.md new file mode 100644 index 00000000000..40f32463b41 --- /dev/null +++ b/markdown/org/showcase/pirate-bruce/de.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Arrr!" +date: "2016-08-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fc513fa163d3b36a2b8ba6d40825660640a72db4-1080x1080.jpg" +intro: "This picture is from the Instagram feed of Irene's Stoffen ." +title: "[auf Englisch] Boxers for Sjoerd, by Irene" +--- + + +This picture is from [the Instagram feed](https://www.instagram.com/p/BJS0jaThfh1/) of [Irene's Stoffen](https://www.facebook.com/irenes.stoffen). + diff --git a/markdown/org/showcase/pirate-bruce/en.md b/markdown/org/showcase/pirate-bruce/en.md new file mode 100644 index 00000000000..10f22dd6f86 --- /dev/null +++ b/markdown/org/showcase/pirate-bruce/en.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Arrr!" +date: "2016-08-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fc513fa163d3b36a2b8ba6d40825660640a72db4-1080x1080.jpg" +intro: "This picture is from the Instagram feed of Irene's Stoffen ." +title: "Boxers for Sjoerd, by Irene" +--- + + +This picture is from [the Instagram feed](https://www.instagram.com/p/BJS0jaThfh1/) of [Irene's Stoffen](https://www.facebook.com/irenes.stoffen). + diff --git a/markdown/org/showcase/pirate-bruce/es.md b/markdown/org/showcase/pirate-bruce/es.md new file mode 100644 index 00000000000..56dccd4abd6 --- /dev/null +++ b/markdown/org/showcase/pirate-bruce/es.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Arrr!" +date: "2016-08-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fc513fa163d3b36a2b8ba6d40825660640a72db4-1080x1080.jpg" +intro: "This picture is from the Instagram feed of Irene's Stoffen ." +title: "Boxers for Sjoerd, by Irene [No traducido]" +--- + + +This picture is from [the Instagram feed](https://www.instagram.com/p/BJS0jaThfh1/) of [Irene's Stoffen](https://www.facebook.com/irenes.stoffen). + diff --git a/markdown/org/showcase/pirate-bruce/fr.md b/markdown/org/showcase/pirate-bruce/fr.md new file mode 100644 index 00000000000..7d40069a9f1 --- /dev/null +++ b/markdown/org/showcase/pirate-bruce/fr.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "« Arrrr! »" +date: "2016-08-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fc513fa163d3b36a2b8ba6d40825660640a72db4-1080x1080.jpg" +intro: "Cette photo provient du flux Instagram de Irene's Stoffen ." +title: "Boxers pour Sjoerd, par Irene" +--- + + +Cette photo provient du [flux Instagram](https://www.instagram.com/p/BJS0jaThfh1/) de [Irene's Stoffen](https://www.facebook.com/irenes.stoffen). + diff --git a/markdown/org/showcase/pirate-bruce/nl.md b/markdown/org/showcase/pirate-bruce/nl.md new file mode 100644 index 00000000000..bc423033cc1 --- /dev/null +++ b/markdown/org/showcase/pirate-bruce/nl.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Arrr!" +date: "2016-08-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fc513fa163d3b36a2b8ba6d40825660640a72db4-1080x1080.jpg" +intro: "Deze afbeelding is van de Instagram feed van Irene's Stoffen ." +title: "Boxershort voor Sjoerd, door Irene" +--- + + +Deze afbeelding is van [de Instagram feed](https://www.instagram.com/p/BJS0jaThfh1/) van [Irene's Stoffen](https://www.facebook.com/irenes.stoffen). + diff --git a/markdown/org/showcase/purple-bruce/de.md b/markdown/org/showcase/purple-bruce/de.md new file mode 100644 index 00000000000..7bd009c20eb --- /dev/null +++ b/markdown/org/showcase/purple-bruce/de.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "These are slightly shortened in comparison to the original pattern" +date: "2016-08-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b83d4a336de7383c872655611bed5a6ce51aec1a-1080x1080.jpg" +intro: "This picture is from the Instagram feed of zephine_malvimavie ." +title: "[auf Englisch] Purple boxers by zephine_malvimavie" +--- + + +This picture is from [the Instagram feed](https://www.instagram.com/p/BJcIzihhz-b-2_3G5FtvtsnUz1ZKoqADYPAyZw0/) of [zephine_malvimavie](https://instagram.com/zephine_malvimavie). + diff --git a/markdown/org/showcase/purple-bruce/en.md b/markdown/org/showcase/purple-bruce/en.md new file mode 100644 index 00000000000..3ccbc8d654d --- /dev/null +++ b/markdown/org/showcase/purple-bruce/en.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "These are slightly shortened in comparison to the original pattern" +date: "2016-08-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b83d4a336de7383c872655611bed5a6ce51aec1a-1080x1080.jpg" +intro: "This picture is from the Instagram feed of zephine_malvimavie ." +title: "Purple boxers by zephine_malvimavie" +--- + + +This picture is from [the Instagram feed](https://www.instagram.com/p/BJcIzihhz-b-2_3G5FtvtsnUz1ZKoqADYPAyZw0/) of [zephine_malvimavie](https://instagram.com/zephine_malvimavie). + diff --git a/markdown/org/showcase/purple-bruce/es.md b/markdown/org/showcase/purple-bruce/es.md new file mode 100644 index 00000000000..1873f98ce82 --- /dev/null +++ b/markdown/org/showcase/purple-bruce/es.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "These are slightly shortened in comparison to the original pattern" +date: "2016-08-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b83d4a336de7383c872655611bed5a6ce51aec1a-1080x1080.jpg" +intro: "This picture is from the Instagram feed of zephine_malvimavie ." +title: "Purple boxers by zephine_malvimavie [No traducido]" +--- + + +This picture is from [the Instagram feed](https://www.instagram.com/p/BJcIzihhz-b-2_3G5FtvtsnUz1ZKoqADYPAyZw0/) of [zephine_malvimavie](https://instagram.com/zephine_malvimavie). + diff --git a/markdown/org/showcase/purple-bruce/fr.md b/markdown/org/showcase/purple-bruce/fr.md new file mode 100644 index 00000000000..9fb3ce5f216 --- /dev/null +++ b/markdown/org/showcase/purple-bruce/fr.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Ceux-ci sont légèrement raccourcis par rapport au modèle original" +date: "2016-08-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b83d4a336de7383c872655611bed5a6ce51aec1a-1080x1080.jpg" +intro: "Cette photo provient du flux Instagram de zephine_malvimavie ." +title: "Boxers violets par zephine_malvimavie" +--- + + +Cette photo provient du [flux Instagram](https://www.instagram.com/p/BJcIzihhz-b-2_3G5FtvtsnUz1ZKoqADYPAyZw0/) de [zephine_malvimavie](https://instagram.com/zephine_malvimavie). + diff --git a/markdown/org/showcase/purple-bruce/nl.md b/markdown/org/showcase/purple-bruce/nl.md new file mode 100644 index 00000000000..06a72447a4e --- /dev/null +++ b/markdown/org/showcase/purple-bruce/nl.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Deze zijn een beetje korter dan het originele patroon" +date: "2016-08-23" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/b83d4a336de7383c872655611bed5a6ce51aec1a-1080x1080.jpg" +intro: "Deze afbeelding is van de Instagram feed van zephine_malvimavie ." +title: "Paarse boxershort door zephine_malvimavie" +--- + + +Deze afbeelding is van [de Instagram feed](https://www.instagram.com/p/BJcIzihhz-b-2_3G5FtvtsnUz1ZKoqADYPAyZw0/) van [zephine_malvimavie](https://instagram.com/zephine_malvimavie). + diff --git a/markdown/org/showcase/purple-huey/de.md b/markdown/org/showcase/purple-huey/de.md new file mode 100644 index 00000000000..0d856eee5f6 --- /dev/null +++ b/markdown/org/showcase/purple-huey/de.md @@ -0,0 +1,14 @@ +--- +maker: "Joost De Cock" +caption: "Yes, that vintage Atari T-shirt is pretty sweet too." +date: "2017-10-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1a07778bc08dd8edb0866e87b6f1e74d3827e81e-2129x2129.jpg" +intro: "This post is originally appeared on the Instagram feed of joostdecock ." +title: "[auf Englisch] This was the first ever Huey that's been made and of course it's purple" +--- + + +This post is [originally appeared](https://www.instagram.com/p/BaRWb34jYCL/) on [the Instagram feed of joostdecock](https://www.instagram.com/joostdecock/). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/purple-huey/en.md b/markdown/org/showcase/purple-huey/en.md new file mode 100644 index 00000000000..08356836b74 --- /dev/null +++ b/markdown/org/showcase/purple-huey/en.md @@ -0,0 +1,15 @@ +--- +maker: "Joost De Cock" +caption: "Yes, that vintage Atari T-shirt is pretty sweet too." +date: "2017-10-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1a07778bc08dd8edb0866e87b6f1e74d3827e81e-2129x2129.jpg" +intro: "This post is originally appeared on the Instagram feed of joostdecock ." +title: "This was the first ever Huey that's been made and of course it's purple" +--- + + +This post is [originally appeared](https://www.instagram.com/p/BaRWb34jYCL/) +on [the Instagram feed of joostdecock](https://www.instagram.com/joostdecock/). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/purple-huey/es.md b/markdown/org/showcase/purple-huey/es.md new file mode 100644 index 00000000000..dcba0d78454 --- /dev/null +++ b/markdown/org/showcase/purple-huey/es.md @@ -0,0 +1,15 @@ +--- +maker: "Joost De Cock" +caption: "Yes, that vintage Atari T-shirt is pretty sweet too." +date: "2017-10-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1a07778bc08dd8edb0866e87b6f1e74d3827e81e-2129x2129.jpg" +intro: "This post is originally appeared on the Instagram feed of joostdecock ." +title: "This was the first ever Huey that's been made and of course it's purple [No traducido]" +--- + + +This post is [originally appeared](https://www.instagram.com/p/BaRWb34jYCL/) +on [the Instagram feed of joostdecock](https://www.instagram.com/joostdecock/). + +It is reposted here with permission. + diff --git a/markdown/org/showcase/purple-huey/fr.md b/markdown/org/showcase/purple-huey/fr.md new file mode 100644 index 00000000000..c36ec87ca3f --- /dev/null +++ b/markdown/org/showcase/purple-huey/fr.md @@ -0,0 +1,14 @@ +--- +maker: "Joost De Cock" +caption: "Oui, ce t-shirt vintage Atari est aussi assez chouette." +date: "2017-10-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1a07778bc08dd8edb0866e87b6f1e74d3827e81e-2129x2129.jpg" +intro: "Ce message est initialement apparu sur le flux Instagram de joostdecock ." +title: "C’était la toute première fois que Huey a été réalisé et bien sûr il est violet" +--- + + +Ce message est [initialement apparu](https://www.instagram.com/p/BaRWb34jYCL/) sur [le flux Instagram de joostdecock](https://www.instagram.com/joostdecock/). + +Elle est publiée ici avec son autorisation. + diff --git a/markdown/org/showcase/purple-huey/nl.md b/markdown/org/showcase/purple-huey/nl.md new file mode 100644 index 00000000000..cac6257ed0f --- /dev/null +++ b/markdown/org/showcase/purple-huey/nl.md @@ -0,0 +1,14 @@ +--- +maker: "Joost De Cock" +caption: "Ja, dat vintage Atari t-shirt mag er ook wel wezen." +date: "2017-10-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/1a07778bc08dd8edb0866e87b6f1e74d3827e81e-2129x2129.jpg" +intro: "Deze post verscheen eerst op de Instagram feed van joostdecock ." +title: "Dit was de eerste Huey ooit gemaakt en natuurlijk is hij paars" +--- + + +Deze post [verscheen eerst](https://www.instagram.com/p/BaRWb34jYCL/) op de [Instagram feed van joostdecock](https://www.instagram.com/joostdecock/). + +Hij werd hier gepost met toestemming. + diff --git a/markdown/org/showcase/quilted-jersey-huey/de.md b/markdown/org/showcase/quilted-jersey-huey/de.md new file mode 100644 index 00000000000..bec6d73fb2c --- /dev/null +++ b/markdown/org/showcase/quilted-jersey-huey/de.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "Going for that casual and too cool to look at the camera look." +date: "2017-12-11" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/25779f10f43cc87d9d4e201248b2e1a4f9af9009-1403x1403.jpg" +intro: "[auf Englisch] A Huey in quilted jersey by Andrew Myles, aka Buster" +title: "[auf Englisch] A Huey in quilted jersey by Andrew Myles, aka Buster" +--- + +![Don't you just love this quilted jersey Andrew used for this Huey](https://posts.freesewing.org/uploads/quilted_jersey_huey_high_detail_20acdff4f5.jpg "Don't you just love this quilted jersey Andrew used for this Huey") + + + +###### More pictures and info in the original blog post +This picture +[originally appeared](https://mensew.wordpress.com/2017/12/10/hugo-hoodie-freesewing-org/) +on [@Buster](/users/Buster)'s [MenSew](https://mensew.wordpress.com/) blog. It is reposted here with persmission. + +Do check out the blog post for there are loads more pictures and he also writes about his +experience using [freesewing.org](/). + + diff --git a/markdown/org/showcase/quilted-jersey-huey/en.md b/markdown/org/showcase/quilted-jersey-huey/en.md new file mode 100644 index 00000000000..0e10a72748f --- /dev/null +++ b/markdown/org/showcase/quilted-jersey-huey/en.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "Going for that casual and too cool to look at the camera look." +date: "2017-12-11" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/25779f10f43cc87d9d4e201248b2e1a4f9af9009-1403x1403.jpg" +intro: "A Huey in quilted jersey by Andrew Myles, aka Buster" +title: "A Huey in quilted jersey by Andrew Myles, aka Buster" +--- + +![Don't you just love this quilted jersey Andrew used for this Huey](https://posts.freesewing.org/uploads/quilted_jersey_huey_high_detail_20acdff4f5.jpg "Don't you just love this quilted jersey Andrew used for this Huey") + + + +###### More pictures and info in the original blog post +This picture +[originally appeared](https://mensew.wordpress.com/2017/12/10/hugo-hoodie-freesewing-org/) +on [@Buster](/users/Buster)'s [MenSew](https://mensew.wordpress.com/) blog. It is reposted here with persmission. + +Do check out the blog post for there are loads more pictures and he also writes about his +experience using [freesewing.org](/). + + diff --git a/markdown/org/showcase/quilted-jersey-huey/es.md b/markdown/org/showcase/quilted-jersey-huey/es.md new file mode 100644 index 00000000000..60437129b43 --- /dev/null +++ b/markdown/org/showcase/quilted-jersey-huey/es.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "Going for that casual and too cool to look at the camera look." +date: "2017-12-11" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/25779f10f43cc87d9d4e201248b2e1a4f9af9009-1403x1403.jpg" +intro: "A Huey in quilted jersey by Andrew Myles, aka Buster [No traducido]" +title: "A Huey in quilted jersey by Andrew Myles, aka Buster [No traducido]" +--- + +![Don't you just love this quilted jersey Andrew used for this Huey](https://posts.freesewing.org/uploads/quilted_jersey_huey_high_detail_20acdff4f5.jpg "Don't you just love this quilted jersey Andrew used for this Huey") + + + +###### More pictures and info in the original blog post +This picture +[originally appeared](https://mensew.wordpress.com/2017/12/10/hugo-hoodie-freesewing-org/) +on [@Buster](/users/Buster)'s [MenSew](https://mensew.wordpress.com/) blog. It is reposted here with persmission. + +Do check out the blog post for there are loads more pictures and he also writes about his +experience using [freesewing.org](/). + + diff --git a/markdown/org/showcase/quilted-jersey-huey/fr.md b/markdown/org/showcase/quilted-jersey-huey/fr.md new file mode 100644 index 00000000000..ef38a221851 --- /dev/null +++ b/markdown/org/showcase/quilted-jersey-huey/fr.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "Va pour ce look décontracté et trop cool pour regarder la caméra." +date: "2017-12-11" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/25779f10f43cc87d9d4e201248b2e1a4f9af9009-1403x1403.jpg" +intro: "Un Huey en jersey matelassé par Andrew Myles, aka Buster" +title: "Un Huey en jersey matelassé par Andrew Myles, aka Buster" +--- + +![N'adorez-vous pas ce jersey matelassé qu'Andrew a utilisé pour ce Huey ?](https://posts.freesewing.org/uploads/quilted_jersey_huey_high_detail_20acdff4f5.jpg "N'adorez-vous pas ce jersey matelassé qu'Andrew a utilisé pour ce Huey ?") + + + +###### Plus de photos et d'infos dans l'article de blog original +Cette photo +[est apparue à l'origine](https://mensew.wordpress.com/2017/12/10/hugo-hoodie-freesewing-org/) +sur le blog de [@Buster](/users/Buster) [MenSew](https://mensew.wordpress.com/). Elle est publiée ici avec son autorisation. + +Consultez l'article de blog car il y a beaucoup plus de photos et il écrit également sur son +expérience d'utilisation de [freesewing.org](/). + + diff --git a/markdown/org/showcase/quilted-jersey-huey/nl.md b/markdown/org/showcase/quilted-jersey-huey/nl.md new file mode 100644 index 00000000000..c0b7ba145dc --- /dev/null +++ b/markdown/org/showcase/quilted-jersey-huey/nl.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "Hij ging voor die casual en te cool om naar de camera te kijken look." +date: "2017-12-11" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/25779f10f43cc87d9d4e201248b2e1a4f9af9009-1403x1403.jpg" +intro: "Een Huey in gequilte jersey door Andrew Myles, alias Buster" +title: "Een Huey in gequilte jersey door Andrew Myles, alias Buster" +--- + +![Is deze gequilte jersey die Andrew gebruikte niet geweldig](https://posts.freesewing.org/uploads/quilted_jersey_huey_high_detail_20acdff4f5.jpg "Is deze gequilte jersey die Andrew gebruikte niet geweldig") + + + +###### More pictures and info in the original blog post +This picture +[originally appeared](https://mensew.wordpress.com/2017/12/10/hugo-hoodie-freesewing-org/) +on [@Buster](/users/Buster)'s [MenSew](https://mensew.wordpress.com/) blog. It is reposted here with persmission. + +Do check out the blog post for there are loads more pictures and he also writes about his +experience using [freesewing.org](/). + + diff --git a/markdown/org/showcase/red-button-simon/de.md b/markdown/org/showcase/red-button-simon/de.md new file mode 100644 index 00000000000..2859d15b726 --- /dev/null +++ b/markdown/org/showcase/red-button-simon/de.md @@ -0,0 +1,12 @@ +--- +maker: "Joost De Cock" +caption: "A Simon shirt by Joost" +date: "2017-04-03" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4a2c7ef48f9e59652e63af8e80f57272dfbf0873-1944x1944.jpg" +intro: "A Simon shirt with red contrasting buttons." +title: "Joost does SimonBmxfg" +--- + + +A Simon shirt with red contrasting buttons. + diff --git a/markdown/org/showcase/red-button-simon/en.md b/markdown/org/showcase/red-button-simon/en.md new file mode 100644 index 00000000000..e89e3aeb9c7 --- /dev/null +++ b/markdown/org/showcase/red-button-simon/en.md @@ -0,0 +1,11 @@ +--- +maker: "Joost De Cock" +caption: "A Simon shirt by Joost" +date: "2017-04-03" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4a2c7ef48f9e59652e63af8e80f57272dfbf0873-1944x1944.jpg" +intro: "A Simon shirt with red contrasting buttons." +title: "Joost does Simon again" +--- + +A Simon shirt with red contrasting buttons. + diff --git a/markdown/org/showcase/red-button-simon/es.md b/markdown/org/showcase/red-button-simon/es.md new file mode 100644 index 00000000000..baa8e4848da --- /dev/null +++ b/markdown/org/showcase/red-button-simon/es.md @@ -0,0 +1,11 @@ +--- +maker: "Joost De Cock" +caption: "A Simon shirt by Joost" +date: "2017-04-03" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4a2c7ef48f9e59652e63af8e80f57272dfbf0873-1944x1944.jpg" +intro: "A Simon shirt with red contrasting buttons." +title: "Joost does Simon again [No traducido]" +--- + +A Simon shirt with red contrasting buttons. + diff --git a/markdown/org/showcase/red-button-simon/fr.md b/markdown/org/showcase/red-button-simon/fr.md new file mode 100644 index 00000000000..9fa68e3a87c --- /dev/null +++ b/markdown/org/showcase/red-button-simon/fr.md @@ -0,0 +1,12 @@ +--- +maker: "Joost De Cock" +caption: "Une chemise Simon par Joost" +date: "2017-04-03" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4a2c7ef48f9e59652e63af8e80f57272dfbf0873-1944x1944.jpg" +intro: "Une chemise Simon aux boutons rouges contrastés." +title: "Joost fait SimonvO21m" +--- + + +Une chemise Simon aux boutons rouges contrastés. + diff --git a/markdown/org/showcase/red-button-simon/nl.md b/markdown/org/showcase/red-button-simon/nl.md new file mode 100644 index 00000000000..0af224b7de1 --- /dev/null +++ b/markdown/org/showcase/red-button-simon/nl.md @@ -0,0 +1,12 @@ +--- +maker: "Joost De Cock" +caption: "Een Simon hemd door Joost" +date: "2017-04-03" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4a2c7ef48f9e59652e63af8e80f57272dfbf0873-1944x1944.jpg" +intro: "Een Simon hemd met rode, contrasterende knopen." +title: "Joost maakt een Simon met rode knopen " +--- + + +Een Simon hemd met rode, contrasterende knopen. + diff --git a/markdown/org/showcase/red-theo/de.md b/markdown/org/showcase/red-theo/de.md new file mode 100644 index 00000000000..ad9c2367934 --- /dev/null +++ b/markdown/org/showcase/red-theo/de.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Not the greatest quality picture, but what can we do" +date: "2017-08-14" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/468efcd7ea0faf06b74fa10c0a092f21d374c7e8-1080x1142.jpg" +intro: "Petros writes (via Facebook messenger):" +title: "[auf Englisch] Red bermuda shorts by Petros" +--- + +Petros writes (via Facebook messenger): + +> Hi, Joost. The new platform is amazing. Congratulations!!! I have posted a comment under username Petros. I used the pattern Theo from the previous site and i sewed a bermuda shorts under your guidance and thorough instructions of the youtube tutorials you 've made. I have never sewed a gament this complex before and yet you made it easy. You are extraordinary. + +![Here's a view from the front](https://posts.freesewing.org/uploads/red_theo_2_6b1dc84c14.jpg "Here's a view from the front") diff --git a/markdown/org/showcase/red-theo/en.md b/markdown/org/showcase/red-theo/en.md new file mode 100644 index 00000000000..17b79259d30 --- /dev/null +++ b/markdown/org/showcase/red-theo/en.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Not the greatest quality picture, but what can we do" +date: "2017-08-14" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/468efcd7ea0faf06b74fa10c0a092f21d374c7e8-1080x1142.jpg" +intro: "Petros writes (via Facebook messenger):" +title: "Red bermuda shorts by Petros" +--- + +Petros writes (via Facebook messenger): + +> Hi, Joost. The new platform is amazing. Congratulations!!! I have posted a comment under username Petros. I used the pattern Theo from the previous site and i sewed a bermuda shorts under your guidance and thorough instructions of the youtube tutorials you 've made. I have never sewed a gament this complex before and yet you made it easy. You are extraordinary. + +![Here's a view from the front](https://posts.freesewing.org/uploads/red_theo_2_6b1dc84c14.jpg "Here's a view from the front") diff --git a/markdown/org/showcase/red-theo/es.md b/markdown/org/showcase/red-theo/es.md new file mode 100644 index 00000000000..73737978d11 --- /dev/null +++ b/markdown/org/showcase/red-theo/es.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Not the greatest quality picture, but what can we do" +date: "2017-08-14" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/468efcd7ea0faf06b74fa10c0a092f21d374c7e8-1080x1142.jpg" +intro: "Petros writes (via Facebook messenger):" +title: "Red bermuda shorts by Petros [No traducido]" +--- + +Petros writes (via Facebook messenger): + +> Hi, Joost. The new platform is amazing. Congratulations!!! I have posted a comment under username Petros. I used the pattern Theo from the previous site and i sewed a bermuda shorts under your guidance and thorough instructions of the youtube tutorials you 've made. I have never sewed a gament this complex before and yet you made it easy. You are extraordinary. + +![Here's a view from the front](https://posts.freesewing.org/uploads/red_theo_2_6b1dc84c14.jpg "Here's a view from the front") diff --git a/markdown/org/showcase/red-theo/fr.md b/markdown/org/showcase/red-theo/fr.md new file mode 100644 index 00000000000..9f50f964319 --- /dev/null +++ b/markdown/org/showcase/red-theo/fr.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Pas la plus grande qualité d'image, mais que pouvons-nous faire" +date: "2017-08-14" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/468efcd7ea0faf06b74fa10c0a092f21d374c7e8-1080x1142.jpg" +intro: "Petros écrit (via Facebook messenger) :" +title: "Bermudas rouges par Petros" +--- + +Petros écrit (via Facebook messenger) : + +> Salut Joost. La nouvelle plateforme est incroyable. Félicitations !!! J'ai publié un commentaire sous le nom d'utilisateur Petros. J'ai utilisé le patron Theo de l'ancien site et j'ai cousu un bermuda sous vos conseils et instructions approfondis des tutoriels youtube que vous avez faits. Je n'ai jamais coupé un vêtement aussi complexe auparavant et pourtant vous m'avez rendu la tâche facile. Vous êtes extraordinaire. + +![Voici une vue du devant](https://posts.freesewing.org/uploads/red_theo_2_6b1dc84c14.jpg "Voici une vue du devant") diff --git a/markdown/org/showcase/red-theo/nl.md b/markdown/org/showcase/red-theo/nl.md new file mode 100644 index 00000000000..1d7ea5b1580 --- /dev/null +++ b/markdown/org/showcase/red-theo/nl.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Niet de beste kwaliteit van foto, maar wat doe je eraan" +date: "2017-08-14" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/468efcd7ea0faf06b74fa10c0a092f21d374c7e8-1080x1142.jpg" +intro: "Petros schrijft (via Facebook messenger):" +title: "Rode bermuda door Petros" +--- + +Petros schrijft (via Facebook messenger): + +> Hey Joost. Het nieuwe platform is geweldig. Gefeliciteerd!!! Ik heb een commentaar gepost met de gebruikersnaam Petros. Ik heb het Theo patroon van de vorige site gebruikt en een bermuda genaaid met jouw hulp en de grondige instructies uit de youtube tutorials die je gemaakt hebt. Dit is het moeilijkste kledingstuk dat ik ooit gemaakt hebt en dankzij jou was het makkelijk. Je bent buitengewoon. + +![Zicht op de voorkant](https://posts.freesewing.org/uploads/red_theo_2_6b1dc84c14.jpg "Zicht op de voorkant") diff --git a/markdown/org/showcase/ricos-huey/de.md b/markdown/org/showcase/ricos-huey/de.md new file mode 100644 index 00000000000..169b23a6c8d --- /dev/null +++ b/markdown/org/showcase/ricos-huey/de.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "A FreeSewing user wearing their new Huey" +date: "2020-11-03" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/33aca2362964edd5ea4ea2363fefbdc3ce255a68-2000x1857.jpg" +intro: "Eine andere Ansicht" +title: "[auf Englisch] Huey by Ricos" +--- + +Eine andere Ansicht + +![Huey hoodie laying on a washing machine, instead of on a human](https://posts.freesewing.org/uploads/ricos_huey_ricos2_d8c625b557.jpg "Huey hoodie laying on a washing machine, instead of on a human") diff --git a/markdown/org/showcase/ricos-huey/en.md b/markdown/org/showcase/ricos-huey/en.md new file mode 100644 index 00000000000..36317ce8a80 --- /dev/null +++ b/markdown/org/showcase/ricos-huey/en.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "A FreeSewing user wearing their new Huey" +date: "2020-11-03" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/33aca2362964edd5ea4ea2363fefbdc3ce255a68-2000x1857.jpg" +intro: "Another view" +title: "Huey by Ricos" +--- + +Another view + +![Huey hoodie laying on a washing machine, instead of on a human](https://posts.freesewing.org/uploads/ricos_huey_ricos2_d8c625b557.jpg "Huey hoodie laying on a washing machine, instead of on a human") diff --git a/markdown/org/showcase/ricos-huey/es.md b/markdown/org/showcase/ricos-huey/es.md new file mode 100644 index 00000000000..513d25fea7d --- /dev/null +++ b/markdown/org/showcase/ricos-huey/es.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "A FreeSewing user wearing their new Huey" +date: "2020-11-03" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/33aca2362964edd5ea4ea2363fefbdc3ce255a68-2000x1857.jpg" +intro: "Another view" +title: "Huey by Ricos [No traducido]" +--- + +Another view + +![Huey hoodie laying on a washing machine, instead of on a human](https://posts.freesewing.org/uploads/ricos_huey_ricos2_d8c625b557.jpg "Huey hoodie laying on a washing machine, instead of on a human") diff --git a/markdown/org/showcase/ricos-huey/fr.md b/markdown/org/showcase/ricos-huey/fr.md new file mode 100644 index 00000000000..f6b47317cdf --- /dev/null +++ b/markdown/org/showcase/ricos-huey/fr.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Un utilisateur de FreeSewing portant son nouveau Huey" +date: "2020-11-03" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/33aca2362964edd5ea4ea2363fefbdc3ce255a68-2000x1857.jpg" +intro: "Une autre vue" +title: "Huey par Ricos" +--- + +Une autre vue + +![Sweat à capuche Huey posé sur une machine à laver au lieu d'un humain](https://posts.freesewing.org/uploads/ricos_huey_ricos2_d8c625b557.jpg "Sweat à capuche Huey posé sur une machine à laver au lieu d'un humain") diff --git a/markdown/org/showcase/ricos-huey/nl.md b/markdown/org/showcase/ricos-huey/nl.md new file mode 100644 index 00000000000..c849687c283 --- /dev/null +++ b/markdown/org/showcase/ricos-huey/nl.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "A FreeSewing user wearing their new Huey" +date: "2020-11-03" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/33aca2362964edd5ea4ea2363fefbdc3ce255a68-2000x1857.jpg" +intro: "Another view" +title: "Huey by Ricos [Niet vertaald]" +--- + +Another view + +![Huey hoodie laying on a washing machine, instead of on a human](https://posts.freesewing.org/uploads/ricos_huey_ricos2_d8c625b557.jpg "Huey hoodie laying on a washing machine, instead of on a human") diff --git a/markdown/org/showcase/ricos-sven/de.md b/markdown/org/showcase/ricos-sven/de.md new file mode 100644 index 00000000000..ca3b43c1751 --- /dev/null +++ b/markdown/org/showcase/ricos-sven/de.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "A top-notch Sven, but just wait..." +date: "2020-11-03" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f208ab781d22f74c91cc37a31249fd88a94a2aab-2000x2198.jpg" +intro: "There's more! Check out the sleeves and stripes on this Sven!" +title: "[auf Englisch] Sven by Ricos" +--- + +There's more! Check out the sleeves and stripes on this Sven! + +![Side view, showing sleeves with colorblocked stripes](https://posts.freesewing.org/uploads/ricos_sven_ricos2_d350f988c8.jpg "Side view, showing sleeves with colorblocked stripes") + +![Rückansicht](https://posts.freesewing.org/uploads/ricos_sven_ricos3_74928145d7.jpg "Rückansicht") diff --git a/markdown/org/showcase/ricos-sven/en.md b/markdown/org/showcase/ricos-sven/en.md new file mode 100644 index 00000000000..da2ea3bc28c --- /dev/null +++ b/markdown/org/showcase/ricos-sven/en.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "A top-notch Sven, but just wait..." +date: "2020-11-03" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f208ab781d22f74c91cc37a31249fd88a94a2aab-2000x2198.jpg" +intro: "There's more! Check out the sleeves and stripes on this Sven!" +title: "Sven by Ricos" +--- + +There's more! Check out the sleeves and stripes on this Sven! + +![Side view, showing sleeves with colorblocked stripes](https://posts.freesewing.org/uploads/ricos_sven_ricos2_d350f988c8.jpg "Side view, showing sleeves with colorblocked stripes") + +![Back view](https://posts.freesewing.org/uploads/ricos_sven_ricos3_74928145d7.jpg) diff --git a/markdown/org/showcase/ricos-sven/es.md b/markdown/org/showcase/ricos-sven/es.md new file mode 100644 index 00000000000..01d51a903ed --- /dev/null +++ b/markdown/org/showcase/ricos-sven/es.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "A top-notch Sven, but just wait..." +date: "2020-11-03" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f208ab781d22f74c91cc37a31249fd88a94a2aab-2000x2198.jpg" +intro: "There's more! Check out the sleeves and stripes on this Sven!" +title: "Sven by Ricos [No traducido]" +--- + +There's more! Check out the sleeves and stripes on this Sven! + +![Side view, showing sleeves with colorblocked stripes](https://posts.freesewing.org/uploads/ricos_sven_ricos2_d350f988c8.jpg "Side view, showing sleeves with colorblocked stripes") + +![Back view](https://posts.freesewing.org/uploads/ricos_sven_ricos3_74928145d7.jpg) diff --git a/markdown/org/showcase/ricos-sven/fr.md b/markdown/org/showcase/ricos-sven/fr.md new file mode 100644 index 00000000000..43d12d3674c --- /dev/null +++ b/markdown/org/showcase/ricos-sven/fr.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "Un Sven haut de gamme, mais attendez..." +date: "2020-11-03" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f208ab781d22f74c91cc37a31249fd88a94a2aab-2000x2198.jpg" +intro: "Il y en a plus ! Découvrez les manches et les rayures de ce Sven !" +title: "Sven par Ricos" +--- + +Il y en a plus ! Découvrez les manches et les rayures de ce Sven ! + +![Vue latérale, montrant les manches avec des rayures colorées](https://posts.freesewing.org/uploads/ricos_sven_ricos2_d350f988c8.jpg "Vue latérale, montrant les manches avec des rayures colorées") + +![Vue de derrière](https://posts.freesewing.org/uploads/ricos_sven_ricos3_74928145d7.jpg "Vue de derrière") diff --git a/markdown/org/showcase/ricos-sven/nl.md b/markdown/org/showcase/ricos-sven/nl.md new file mode 100644 index 00000000000..ce6b2795fee --- /dev/null +++ b/markdown/org/showcase/ricos-sven/nl.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "A top-notch Sven, but just wait..." +date: "2020-11-03" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f208ab781d22f74c91cc37a31249fd88a94a2aab-2000x2198.jpg" +intro: "There's more! Check out the sleeves and stripes on this Sven!" +title: "Sven by Ricos [Niet vertaald]" +--- + +There's more! Check out the sleeves and stripes on this Sven! + +![Side view, showing sleeves with colorblocked stripes](https://posts.freesewing.org/uploads/ricos_sven_ricos2_d350f988c8.jpg "Side view, showing sleeves with colorblocked stripes") + +![Back view](https://posts.freesewing.org/uploads/ricos_sven_ricos3_74928145d7.jpg) diff --git a/markdown/org/showcase/sample-wahid/de.md b/markdown/org/showcase/sample-wahid/de.md new file mode 100644 index 00000000000..2bc213192c3 --- /dev/null +++ b/markdown/org/showcase/sample-wahid/de.md @@ -0,0 +1,11 @@ +--- +maker: "Joost De Cock" +caption: "I made this as a sample when designing the pattern. The default neckline has been lowered since." +date: "2016-05-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/011e43976f08ac8c84004a40173d438a12eed8ea-2048x2048.jpg" +intro: "FIXME_no_intro" +title: "[auf Englisch] A blue/greenish Wahid waistcoat by joostdecock" +--- + + + diff --git a/markdown/org/showcase/sample-wahid/en.md b/markdown/org/showcase/sample-wahid/en.md new file mode 100644 index 00000000000..9e71d88e126 --- /dev/null +++ b/markdown/org/showcase/sample-wahid/en.md @@ -0,0 +1,10 @@ +--- +maker: "Joost De Cock" +caption: "I made this as a sample when designing the pattern. The default neckline has been lowered since." +date: "2016-05-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/011e43976f08ac8c84004a40173d438a12eed8ea-2048x2048.jpg" +intro: "FIXME_no_intro" +title: "A blue/greenish Wahid waistcoat by joostdecock" +--- + + diff --git a/markdown/org/showcase/sample-wahid/es.md b/markdown/org/showcase/sample-wahid/es.md new file mode 100644 index 00000000000..5a860f314e2 --- /dev/null +++ b/markdown/org/showcase/sample-wahid/es.md @@ -0,0 +1,10 @@ +--- +maker: "Joost De Cock" +caption: "I made this as a sample when designing the pattern. The default neckline has been lowered since." +date: "2016-05-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/011e43976f08ac8c84004a40173d438a12eed8ea-2048x2048.jpg" +intro: "FIXME_no_intro" +title: "A blue/greenish Wahid waistcoat by joostdecock [No traducido]" +--- + + diff --git a/markdown/org/showcase/sample-wahid/fr.md b/markdown/org/showcase/sample-wahid/fr.md new file mode 100644 index 00000000000..dcdfc735c8f --- /dev/null +++ b/markdown/org/showcase/sample-wahid/fr.md @@ -0,0 +1,11 @@ +--- +maker: "Joost De Cock" +caption: "Je l'ai fait à titre d'essai lors de la conception du patron. L'encolure par défaut a été abaissée depuis." +date: "2016-05-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/011e43976f08ac8c84004a40173d438a12eed8ea-2048x2048.jpg" +intro: "FIXME_no_intro" +title: "Un gilet Wahid bleu/vert par joostdecock" +--- + + + diff --git a/markdown/org/showcase/sample-wahid/nl.md b/markdown/org/showcase/sample-wahid/nl.md new file mode 100644 index 00000000000..cf67b09cd83 --- /dev/null +++ b/markdown/org/showcase/sample-wahid/nl.md @@ -0,0 +1,11 @@ +--- +maker: "Joost De Cock" +caption: "Ik maakte dit als voorbeeld bij het ontwerpen van het patroon. De standaard halslijn is sindsdien verlaagd." +date: "2016-05-02" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/011e43976f08ac8c84004a40173d438a12eed8ea-2048x2048.jpg" +intro: "FIXME_no_intro" +title: "Een blauwgrijze Wahid gilet door joostdecock" +--- + + + diff --git a/markdown/org/showcase/sandy-by-adam/de.md b/markdown/org/showcase/sandy-by-adam/de.md new file mode 100644 index 00000000000..b01396f73b0 --- /dev/null +++ b/markdown/org/showcase/sandy-by-adam/de.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "A simple Sandy skirt made from an old curtain." +date: "2018-10-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/2319bafd94f986504f6ee2e4916d548b2ab1c323-1125x2000.jpg" +intro: "FIXME_no_intro" +title: "[auf Englisch] Sandy Skirt by Adam" +--- + + + diff --git a/markdown/org/showcase/sandy-by-adam/en.md b/markdown/org/showcase/sandy-by-adam/en.md new file mode 100644 index 00000000000..f7589a9df40 --- /dev/null +++ b/markdown/org/showcase/sandy-by-adam/en.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "A simple Sandy skirt made from an old curtain." +date: "2018-10-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/2319bafd94f986504f6ee2e4916d548b2ab1c323-1125x2000.jpg" +intro: "FIXME_no_intro" +title: "Sandy Skirt by Adam" +--- + + diff --git a/markdown/org/showcase/sandy-by-adam/es.md b/markdown/org/showcase/sandy-by-adam/es.md new file mode 100644 index 00000000000..97748b50759 --- /dev/null +++ b/markdown/org/showcase/sandy-by-adam/es.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "A simple Sandy skirt made from an old curtain." +date: "2018-10-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/2319bafd94f986504f6ee2e4916d548b2ab1c323-1125x2000.jpg" +intro: "FIXME_no_intro" +title: "Sandy Skirt by Adam [No traducido]" +--- + + diff --git a/markdown/org/showcase/sandy-by-adam/fr.md b/markdown/org/showcase/sandy-by-adam/fr.md new file mode 100644 index 00000000000..d058c7016a6 --- /dev/null +++ b/markdown/org/showcase/sandy-by-adam/fr.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Une jupe Sandy simple faite à partir d'un vieux rideau." +date: "2018-10-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/2319bafd94f986504f6ee2e4916d548b2ab1c323-1125x2000.jpg" +intro: "FIXME_no_intro" +title: "Jupe Sandy par Adam" +--- + + + diff --git a/markdown/org/showcase/sandy-by-adam/nl.md b/markdown/org/showcase/sandy-by-adam/nl.md new file mode 100644 index 00000000000..35a895576a9 --- /dev/null +++ b/markdown/org/showcase/sandy-by-adam/nl.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Een simpele Sandy rok, gemaakt uit een oud gordijn." +date: "2018-10-08" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/2319bafd94f986504f6ee2e4916d548b2ab1c323-1125x2000.jpg" +intro: "FIXME_no_intro" +title: "Sandy rok door Adam" +--- + + + diff --git a/markdown/org/showcase/sandy-by-anneke/de.md b/markdown/org/showcase/sandy-by-anneke/de.md new file mode 100644 index 00000000000..f646dd3e152 --- /dev/null +++ b/markdown/org/showcase/sandy-by-anneke/de.md @@ -0,0 +1,18 @@ +--- +maker: "Anneke Caramin" +caption: "back view of Anneke's shiny black Sandy skirt" +date: "2020-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f17b554dceedcfa01572346e5032e4836deb6f52-1080x1080.jpg" +intro: "Read Anneke's extensive 2018 blogpost about her new Sandy skirt , including how she added pockets and a curved waistband." +title: "[auf Englisch] Anneke's shiny black Sandy circle skirt" +--- + +Read Anneke's extensive 2018 [blogpost about her new Sandy skirt](http://www.annekecaramin.com/2018/08/garbage-dragon.html), including how she added pockets and a curved waistband. + +Other views: + +![full length of the outfit](https://posts.freesewing.org/uploads/sandy_by_anneke_front_fulllength_76df5afe47.jpg "full length of the outfit") + +![dramatic side view](https://posts.freesewing.org/uploads/sandy_by_anneke_sideview_7cde00b133.jpg "dramatic side view") + +![close up of the exposed back zipper](https://posts.freesewing.org/uploads/sandy_by_anneke_zipper_e2f30b94dd.jpg "close up of the exposed back zipper") diff --git a/markdown/org/showcase/sandy-by-anneke/en.md b/markdown/org/showcase/sandy-by-anneke/en.md new file mode 100644 index 00000000000..6f65dc6bf2d --- /dev/null +++ b/markdown/org/showcase/sandy-by-anneke/en.md @@ -0,0 +1,18 @@ +--- +maker: "Anneke Caramin" +caption: "back view of Anneke's shiny black Sandy skirt" +date: "2020-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f17b554dceedcfa01572346e5032e4836deb6f52-1080x1080.jpg" +intro: "Read Anneke's extensive 2018 blogpost about her new Sandy skirt , including how she added pockets and a curved waistband." +title: "Anneke's shiny black Sandy circle skirt" +--- + +Read Anneke's extensive 2018 [blogpost about her new Sandy skirt](http://www.annekecaramin.com/2018/08/garbage-dragon.html), including how she added pockets and a curved waistband. + +Other views: + +![full length of the outfit](https://posts.freesewing.org/uploads/sandy_by_anneke_front_fulllength_76df5afe47.jpg "full length of the outfit") + +![dramatic side view](https://posts.freesewing.org/uploads/sandy_by_anneke_sideview_7cde00b133.jpg "dramatic side view") + +![close up of the exposed back zipper](https://posts.freesewing.org/uploads/sandy_by_anneke_zipper_e2f30b94dd.jpg "close up of the exposed back zipper") diff --git a/markdown/org/showcase/sandy-by-anneke/es.md b/markdown/org/showcase/sandy-by-anneke/es.md new file mode 100644 index 00000000000..33fdf8e1df7 --- /dev/null +++ b/markdown/org/showcase/sandy-by-anneke/es.md @@ -0,0 +1,18 @@ +--- +maker: "Anneke Caramin" +caption: "back view of Anneke's shiny black Sandy skirt" +date: "2020-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f17b554dceedcfa01572346e5032e4836deb6f52-1080x1080.jpg" +intro: "Read Anneke's extensive 2018 blogpost about her new Sandy skirt , including how she added pockets and a curved waistband." +title: "Anneke's shiny black Sandy circle skirt [No traducido]" +--- + +Read Anneke's extensive 2018 [blogpost about her new Sandy skirt](http://www.annekecaramin.com/2018/08/garbage-dragon.html), including how she added pockets and a curved waistband. + +Other views: + +![full length of the outfit](https://posts.freesewing.org/uploads/sandy_by_anneke_front_fulllength_76df5afe47.jpg "full length of the outfit") + +![dramatic side view](https://posts.freesewing.org/uploads/sandy_by_anneke_sideview_7cde00b133.jpg "dramatic side view") + +![close up of the exposed back zipper](https://posts.freesewing.org/uploads/sandy_by_anneke_zipper_e2f30b94dd.jpg "close up of the exposed back zipper") diff --git a/markdown/org/showcase/sandy-by-anneke/fr.md b/markdown/org/showcase/sandy-by-anneke/fr.md new file mode 100644 index 00000000000..3070d111f3f --- /dev/null +++ b/markdown/org/showcase/sandy-by-anneke/fr.md @@ -0,0 +1,18 @@ +--- +maker: "Anneke Caramin" +caption: "vue zoomée de la jupe Sandy noire brillante d'Anneke" +date: "2020-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f17b554dceedcfa01572346e5032e4836deb6f52-1080x1080.jpg" +intro: "Lisez le complément en 2018 d'Anneke sur l' article de blog à propos de sa nouvelle jupe Sandy , qui inclue la façon dont elle a ajouté des poche et une ceinture courbée." +title: "Jupe circulaire noire et brillante d'Anneke" +--- + +Lisez le complément en 2018 d'Anneke sur l' [article de blog à propos de sa nouvelle jupe Sandy](http://www.annekecaramin.com/2018/08/garbage-dragon.html), qui inclue la façon dont elle a ajouté des poche et une ceinture courbée. + +Autres vues + +![vue de la tenue complète](https://posts.freesewing.org/uploads/sandy_by_anneke_front_fulllength_76df5afe47.jpg "vue de la tenue complète") + +![vue latérale spectaculaire](https://posts.freesewing.org/uploads/sandy_by_anneke_sideview_7cde00b133.jpg "vue latérale spectaculaire") + +![zoom sur la fermeture éclair du dos](zipper.jpg) diff --git a/markdown/org/showcase/sandy-by-anneke/nl.md b/markdown/org/showcase/sandy-by-anneke/nl.md new file mode 100644 index 00000000000..ff4fb75764c --- /dev/null +++ b/markdown/org/showcase/sandy-by-anneke/nl.md @@ -0,0 +1,18 @@ +--- +maker: "Anneke Caramin" +caption: "back view of Anneke's shiny black Sandy skirt" +date: "2020-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/f17b554dceedcfa01572346e5032e4836deb6f52-1080x1080.jpg" +intro: "Read Anneke's extensive 2018 blogpost about her new Sandy skirt , including how she added pockets and a curved waistband." +title: "Anneke's shiny black Sandy circle skirt [Niet vertaald]" +--- + +Read Anneke's extensive 2018 [blogpost about her new Sandy skirt](http://www.annekecaramin.com/2018/08/garbage-dragon.html), including how she added pockets and a curved waistband. + +Other views: + +![full length of the outfit](https://posts.freesewing.org/uploads/sandy_by_anneke_front_fulllength_76df5afe47.jpg "full length of the outfit") + +![dramatic side view](https://posts.freesewing.org/uploads/sandy_by_anneke_sideview_7cde00b133.jpg "dramatic side view") + +![close up of the exposed back zipper](https://posts.freesewing.org/uploads/sandy_by_anneke_zipper_e2f30b94dd.jpg "close up of the exposed back zipper") diff --git a/markdown/org/showcase/sandy-by-jv/de.md b/markdown/org/showcase/sandy-by-jv/de.md new file mode 100644 index 00000000000..68bedc06a05 --- /dev/null +++ b/markdown/org/showcase/sandy-by-jv/de.md @@ -0,0 +1,18 @@ +--- +maker: "RedBlaqueGolden" +caption: "JV in a Sandy with matching mask" +date: "2020-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/35daf9e79d06a8a12972a1e0bd87bce6f3c92028-1536x2048.jpg" +intro: "JV shared their new dress using the Sandy skirt on Twitter." +title: "[auf Englisch] JV's dress made using a Sandy circle skirt" +--- + +JV shared their [new dress using the Sandy skirt](https://twitter.com/RedBlaqueGolden/status/1317752221933633537) on Twitter. + +Here are some other views. + +![full length of the outfit](https://posts.freesewing.org/uploads/sandy_by_jv_jv_sandy_fulllength_3553786a5c.jpg "full length of the outfit") + +![mid twirl](jv_sandy_midtwirl.jpg) + +![close up of the key fabric](jv_sandy_fabric_closeup.jpg) diff --git a/markdown/org/showcase/sandy-by-jv/en.md b/markdown/org/showcase/sandy-by-jv/en.md new file mode 100644 index 00000000000..0333d50c733 --- /dev/null +++ b/markdown/org/showcase/sandy-by-jv/en.md @@ -0,0 +1,18 @@ +--- +maker: "RedBlaqueGolden" +caption: "JV in a Sandy with matching mask" +date: "2020-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/35daf9e79d06a8a12972a1e0bd87bce6f3c92028-1536x2048.jpg" +intro: "JV shared their new dress using the Sandy skirt on Twitter." +title: "JV's dress made using a Sandy circle skirt" +--- + +JV shared their [new dress using the Sandy skirt](https://twitter.com/RedBlaqueGolden/status/1317752221933633537) on Twitter. + +Here are some other views. + +![full length of the outfit](https://posts.freesewing.org/uploads/sandy_by_jv_jv_sandy_fulllength_3553786a5c.jpg "full length of the outfit") + +![mid twirl](https://posts.freesewing.org/uploads/sandy_by_jv_jv_sandy_midtwirl_d5dccbb1d1.jpg) + +![close up of the key fabric](https://posts.freesewing.org/uploads/sandy_by_jv_jv_sandy_fabric_closeup_1fa49dfcad.jpg) diff --git a/markdown/org/showcase/sandy-by-jv/es.md b/markdown/org/showcase/sandy-by-jv/es.md new file mode 100644 index 00000000000..95032420560 --- /dev/null +++ b/markdown/org/showcase/sandy-by-jv/es.md @@ -0,0 +1,18 @@ +--- +maker: "RedBlaqueGolden" +caption: "JV in a Sandy with matching mask" +date: "2020-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/35daf9e79d06a8a12972a1e0bd87bce6f3c92028-1536x2048.jpg" +intro: "JV shared their new dress using the Sandy skirt on Twitter." +title: "JV's dress made using a Sandy circle skirt [No traducido]" +--- + +JV shared their [new dress using the Sandy skirt](https://twitter.com/RedBlaqueGolden/status/1317752221933633537) on Twitter. + +Here are some other views. + +![full length of the outfit](https://posts.freesewing.org/uploads/sandy_by_jv_jv_sandy_fulllength_3553786a5c.jpg "full length of the outfit") + +![mid twirl](https://posts.freesewing.org/uploads/sandy_by_jv_jv_sandy_midtwirl_d5dccbb1d1.jpg) + +![close up of the key fabric](https://posts.freesewing.org/uploads/sandy_by_jv_jv_sandy_fabric_closeup_1fa49dfcad.jpg) diff --git a/markdown/org/showcase/sandy-by-jv/fr.md b/markdown/org/showcase/sandy-by-jv/fr.md new file mode 100644 index 00000000000..f6ab331a5a2 --- /dev/null +++ b/markdown/org/showcase/sandy-by-jv/fr.md @@ -0,0 +1,18 @@ +--- +maker: "RedBlaqueGolden" +caption: "JV dans une Sandy avec un masque assorti" +date: "2020-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/35daf9e79d06a8a12972a1e0bd87bce6f3c92028-1536x2048.jpg" +intro: "JV a partagé sa nouvelle robe en utilisant la jupe Sandy sur Twitter." +title: "Robe de JV fabriquée à l'aide d'une jupe en cercle Sandy" +--- + +JV a partagé sa[nouvelle robe en utilisant la jupe Sandy](https://twitter.com/RedBlaqueGolden/status/1317752221933633537) sur Twitter. + +Voici d'autres vues. + +![vue de la tenue complète](https://posts.freesewing.org/uploads/sandy_by_jv_jv_sandy_fulllength_3553786a5c.jpg "vue de la tenue complète") + +![tourbillon du milieu](https://posts.freesewing.org/uploads/sandy_by_jv_jv_sandy_midtwirl_d5dccbb1d1.jpg "tourbillon du milieu") + +![zoom sur le tissu](https://posts.freesewing.org/uploads/sandy_by_jv_jv_sandy_fabric_closeup_1fa49dfcad.jpg "zoom sur le tissu") diff --git a/markdown/org/showcase/sandy-by-jv/nl.md b/markdown/org/showcase/sandy-by-jv/nl.md new file mode 100644 index 00000000000..dc753874662 --- /dev/null +++ b/markdown/org/showcase/sandy-by-jv/nl.md @@ -0,0 +1,18 @@ +--- +maker: "RedBlaqueGolden" +caption: "JV in a Sandy with matching mask" +date: "2020-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/35daf9e79d06a8a12972a1e0bd87bce6f3c92028-1536x2048.jpg" +intro: "JV shared their new dress using the Sandy skirt on Twitter." +title: "JV's dress made using a Sandy circle skirt [Niet vertaald]" +--- + +JV shared their [new dress using the Sandy skirt](https://twitter.com/RedBlaqueGolden/status/1317752221933633537) on Twitter. + +Here are some other views. + +![full length of the outfit](https://posts.freesewing.org/uploads/sandy_by_jv_jv_sandy_fulllength_3553786a5c.jpg "full length of the outfit") + +![mid twirl](https://posts.freesewing.org/uploads/sandy_by_jv_jv_sandy_midtwirl_d5dccbb1d1.jpg) + +![close up of the key fabric](https://posts.freesewing.org/uploads/sandy_by_jv_jv_sandy_fabric_closeup_1fa49dfcad.jpg) diff --git a/markdown/org/showcase/sandy-by-karin/de.md b/markdown/org/showcase/sandy-by-karin/de.md new file mode 100644 index 00000000000..a13216a369a --- /dev/null +++ b/markdown/org/showcase/sandy-by-karin/de.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Karin poses by the water in her new skirt" +date: "2018-11-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6e2a1b1b2b2935542f32a362aa7876deb36f89fd-2000x1500.jpg" +intro: "After her previous showcase of Hugo , Karin is back with another freesewing make: this Sandy skirt." +title: "[auf Englisch] Sandy by Karin" +--- + + +After [her previous showcase of Hugo](/showcase/hugo-by-karin), Karin is back with another freesewing make: this Sandy skirt. + +![Eine andere Ansicht](https://posts.freesewing.org/uploads/sandy_by_karin_view2_8711bae2d1.jpg "Eine andere Ansicht") + +![A view of the lining](https://posts.freesewing.org/uploads/sandy_by_karin_view3_0b7fdc87cd.jpg "A view of the lining") + +More details [on Karin's blog](https://www.karinkay.nl/sandy-een-gratis-patroon-voor-een-cirkelrok-op-maat/) (in Dutch); + diff --git a/markdown/org/showcase/sandy-by-karin/en.md b/markdown/org/showcase/sandy-by-karin/en.md new file mode 100644 index 00000000000..13074df40fb --- /dev/null +++ b/markdown/org/showcase/sandy-by-karin/en.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Karin poses by the water in her new skirt" +date: "2018-11-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6e2a1b1b2b2935542f32a362aa7876deb36f89fd-2000x1500.jpg" +intro: "Sandy by Karin" +title: "Sandy by Karin" +--- + +After [her previous showcase of Hugo](/showcase/hugo-by-karin), Karin is back with another freesewing make: +this Sandy skirt. + +![Another view](https://posts.freesewing.org/uploads/sandy_by_karin_view2_8711bae2d1.jpg "Another view") + +![A view of the lining](https://posts.freesewing.org/uploads/sandy_by_karin_view3_0b7fdc87cd.jpg "A view of the lining") + +More details [on Karin's blog](https://www.karinkay.nl/sandy-een-gratis-patroon-voor-een-cirkelrok-op-maat/) (in Dutch); diff --git a/markdown/org/showcase/sandy-by-karin/es.md b/markdown/org/showcase/sandy-by-karin/es.md new file mode 100644 index 00000000000..91af9099da2 --- /dev/null +++ b/markdown/org/showcase/sandy-by-karin/es.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Karin poses by the water in her new skirt" +date: "2018-11-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6e2a1b1b2b2935542f32a362aa7876deb36f89fd-2000x1500.jpg" +intro: "Sandy by Karin [No traducido]" +title: "Sandy by Karin [No traducido]" +--- + +After [her previous showcase of Hugo](/showcase/hugo-by-karin), Karin is back with another freesewing make: +this Sandy skirt. + +![Another view](https://posts.freesewing.org/uploads/sandy_by_karin_view2_8711bae2d1.jpg "Another view") + +![A view of the lining](https://posts.freesewing.org/uploads/sandy_by_karin_view3_0b7fdc87cd.jpg "A view of the lining") + +More details [on Karin's blog](https://www.karinkay.nl/sandy-een-gratis-patroon-voor-een-cirkelrok-op-maat/) (in Dutch); diff --git a/markdown/org/showcase/sandy-by-karin/fr.md b/markdown/org/showcase/sandy-by-karin/fr.md new file mode 100644 index 00000000000..ba45e1f0afd --- /dev/null +++ b/markdown/org/showcase/sandy-by-karin/fr.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "Karin pose près de l'eau dans sa nouvelle jupe" +date: "2018-11-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6e2a1b1b2b2935542f32a362aa7876deb36f89fd-2000x1500.jpg" +intro: "Après sa présentation précédente de Hugo , Karin est de retour avec une autre réalisation de freesewing : cette jupe Sandy." +title: "Sandy par Karin" +--- + + +Après [sa présentation précédente de Hugo](/showcase/hugo-by-karin), Karin est de retour avec une autre réalisation de freesewing : cette jupe Sandy. + + +![Une autre vue](https://posts.freesewing.org/uploads/sandy_by_karin_view2_8711bae2d1.jpg "Une autre vue") + +![Une vue de la doublure](https://posts.freesewing.org/uploads/sandy_by_karin_view3_0b7fdc87cd.jpg "Une vue de la doublure") + +Plus de détails sur [le blog de Karin](https://www.karinkay.nl/sandy-een-gratis-patroon-voor-een-cirkelrok-op-maat/) (en néerlandais) ; + diff --git a/markdown/org/showcase/sandy-by-karin/nl.md b/markdown/org/showcase/sandy-by-karin/nl.md new file mode 100644 index 00000000000..484768a301f --- /dev/null +++ b/markdown/org/showcase/sandy-by-karin/nl.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "Karin poses by the water in her new skirt" +date: "2018-11-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/6e2a1b1b2b2935542f32a362aa7876deb36f89fd-2000x1500.jpg" +intro: "After her previous showcase of Hugo , Karin is back with another freesewing make: this Sandy skirt." +title: "Sandy door Karin" +--- + + +After [her previous showcase of Hugo](/showcase/hugo-by-karin), Karin is back with another freesewing make: this Sandy skirt. + +![Een ander zicht](https://posts.freesewing.org/uploads/sandy_by_karin_view2_8711bae2d1.jpg "Een ander zicht") + +![De voering](https://posts.freesewing.org/uploads/sandy_by_karin_view3_0b7fdc87cd.jpg "De voering") + + +Meer details [op de blog van Karin](https://www.karinkay.nl/sandy-een-gratis-patroon-voor-een-cirkelrok-op-maat/) (in het Nederlands). + diff --git a/markdown/org/showcase/sandy-by-sunshine/de.md b/markdown/org/showcase/sandy-by-sunshine/de.md new file mode 100644 index 00000000000..4cd3b0b65cc --- /dev/null +++ b/markdown/org/showcase/sandy-by-sunshine/de.md @@ -0,0 +1,20 @@ +--- +maker: "unknown" +caption: "Paneled Sandy skirt by Sunshine" +date: "2021-02-15" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4d38d6837e8125276522abb62d44a99e191fd8a0-1477x1969.jpg" +intro: "This lovely Sandy skirt was made by Sunshine. The maker shared more information about the project:" +title: "[auf Englisch] Sandy skirt by Sunshine" +--- + + +This lovely Sandy skirt was made by Sunshine. The maker shared more information about the project: + +"I couldn't fit the Sandy pattern on the 44"fabric I bought, so I ended up folding it a few times and using it to cut sections for a panel skirt using alternating colors instead that I had dyed last week. I added a strip on the bottom to increase the length. Then, I added a trim that I had sitting in my sewing basket for 2 years. I hadn't previously considered using a section of the Sandy as a panel segment, but it worked super well!!! I'm not perfect at sewing, but I think it turned out alright!" + + + +This project is from [the FreeSewing Discord](https://discord.freesewing.org/) and has been shared here with permission. + + + diff --git a/markdown/org/showcase/sandy-by-sunshine/en.md b/markdown/org/showcase/sandy-by-sunshine/en.md new file mode 100644 index 00000000000..a1744205e59 --- /dev/null +++ b/markdown/org/showcase/sandy-by-sunshine/en.md @@ -0,0 +1,20 @@ +--- +maker: "unknown" +caption: "Paneled Sandy skirt by Sunshine" +date: "2021-02-15" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4d38d6837e8125276522abb62d44a99e191fd8a0-1477x1969.jpg" +intro: "This lovely Sandy skirt was made by Sunshine. The maker shared more information about the project:" +title: "Sandy skirt by Sunshine" +--- + + +This lovely Sandy skirt was made by Sunshine. The maker shared more information about the project: + +"I couldn't fit the Sandy pattern on the 44"fabric I bought, so I ended up folding it a few times and using it to cut sections for a panel skirt using alternating colors instead that I had dyed last week. I added a strip on the bottom to increase the length. Then, I added a trim that I had sitting in my sewing basket for 2 years. I hadn't previously considered using a section of the Sandy as a panel segment, but it worked super well!!! I'm not perfect at sewing, but I think it turned out alright!" + + + +This project is from [the FreeSewing Discord](https://discord.freesewing.org/) and has been shared here with permission. + + + diff --git a/markdown/org/showcase/sandy-by-sunshine/es.md b/markdown/org/showcase/sandy-by-sunshine/es.md new file mode 100644 index 00000000000..3ca057d6d67 --- /dev/null +++ b/markdown/org/showcase/sandy-by-sunshine/es.md @@ -0,0 +1,20 @@ +--- +maker: "unknown" +caption: "Paneled Sandy skirt by Sunshine" +date: "2021-02-15" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4d38d6837e8125276522abb62d44a99e191fd8a0-1477x1969.jpg" +intro: "This lovely Sandy skirt was made by Sunshine. The maker shared more information about the project:" +title: "Sandy skirt by Sunshine [No traducido]" +--- + + +This lovely Sandy skirt was made by Sunshine. The maker shared more information about the project: + +"I couldn't fit the Sandy pattern on the 44"fabric I bought, so I ended up folding it a few times and using it to cut sections for a panel skirt using alternating colors instead that I had dyed last week. I added a strip on the bottom to increase the length. Then, I added a trim that I had sitting in my sewing basket for 2 years. I hadn't previously considered using a section of the Sandy as a panel segment, but it worked super well!!! I'm not perfect at sewing, but I think it turned out alright!" + + + +This project is from [the FreeSewing Discord](https://discord.freesewing.org/) and has been shared here with permission. + + + diff --git a/markdown/org/showcase/sandy-by-sunshine/fr.md b/markdown/org/showcase/sandy-by-sunshine/fr.md new file mode 100644 index 00000000000..49c82c49874 --- /dev/null +++ b/markdown/org/showcase/sandy-by-sunshine/fr.md @@ -0,0 +1,20 @@ +--- +maker: "unknown" +caption: "Jupe Sandy à panneaux par Sunshine" +date: "2021-02-15" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4d38d6837e8125276522abb62d44a99e191fd8a0-1477x1969.jpg" +intro: "Cette jolie jupe Sandy a été réalisée par Sunshine. La créatrice a fourni plus d'informations sur ce projet :" +title: "Jupe Sandy par Sunshine" +--- + + +Cette jolie jupe Sandy a été réalisée par Sunshine. La créatrice a fourni plus d'informations sur ce projet : + +Je ne pouvais pas adapter le patron Sandy sur le tissu de 44" (112 cm) de laize que j'ai acheté. J'ai donc fini par le plier à plusieurs reprises et l'utiliser pour couper des sections pour une jupe en panneaux, en utilisant des couleurs alternatives plutôt que ce que j'avais teint la semaine dernière. J'ai ajouté une bande en bas pour la rallonger. Ensuite, j'ai ajouté un ruban que j'avais dans mon stock depuis 2 ans. Je n'avais pas pensé au début à utiliser les section du patron Sandy en tant que panneaux, mais finalement ça a très bien fonctionné !!! Je ne suis pas experte pour la couture, mais je pense que le résultat est réussi !" + + + +Ce projet provient du [Discord FreeSewing](https://discord.freesewing.org/) et a été partagée ici avec permission. + + + diff --git a/markdown/org/showcase/sandy-by-sunshine/nl.md b/markdown/org/showcase/sandy-by-sunshine/nl.md new file mode 100644 index 00000000000..95b0b6b9b9c --- /dev/null +++ b/markdown/org/showcase/sandy-by-sunshine/nl.md @@ -0,0 +1,20 @@ +--- +maker: "unknown" +caption: "Paneled Sandy skirt by Sunshine" +date: "2021-02-15" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4d38d6837e8125276522abb62d44a99e191fd8a0-1477x1969.jpg" +intro: "This lovely Sandy skirt was made by Sunshine. The maker shared more information about the project:" +title: "Sandy skirt by Sunshine [Niet vertaald]" +--- + + +This lovely Sandy skirt was made by Sunshine. The maker shared more information about the project: + +"I couldn't fit the Sandy pattern on the 44"fabric I bought, so I ended up folding it a few times and using it to cut sections for a panel skirt using alternating colors instead that I had dyed last week. I added a strip on the bottom to increase the length. Then, I added a trim that I had sitting in my sewing basket for 2 years. I hadn't previously considered using a section of the Sandy as a panel segment, but it worked super well!!! I'm not perfect at sewing, but I think it turned out alright!" + + + +This project is from [the FreeSewing Discord](https://discord.freesewing.org/) and has been shared here with permission. + + + diff --git a/markdown/org/showcase/simon-by-mick/de.md b/markdown/org/showcase/simon-by-mick/de.md new file mode 100644 index 00000000000..3dc898e973f --- /dev/null +++ b/markdown/org/showcase/simon-by-mick/de.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "This matching shirt and mask are coordinated perfection" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fa6dc530445d2457e8b91320af38c4ef8389a369-750x750.jpg" +intro: "Micheál made this fantastic Simon shirt in multicolored dots, with Florence face mask to match!" +title: "[auf Englisch] Speckled Simon Shirt by Mick" +--- + + +Micheál made this fantastic Simon shirt in multicolored dots, with Florence face mask to match! + + +This picture is from the instagram feed of [Micheál](https://www.instagram.com/popshaped/). It is posted here with permission. + + diff --git a/markdown/org/showcase/simon-by-mick/en.md b/markdown/org/showcase/simon-by-mick/en.md new file mode 100644 index 00000000000..70524971229 --- /dev/null +++ b/markdown/org/showcase/simon-by-mick/en.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "This matching shirt and mask are coordinated perfection" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fa6dc530445d2457e8b91320af38c4ef8389a369-750x750.jpg" +intro: "Micheál made this fantastic Simon shirt in multicolored dots, with Florence face mask to match!" +title: "Speckled Simon Shirt by Mick" +--- + +Micheál made this fantastic Simon shirt in multicolored dots, with Florence face mask to match! + + +This picture is from the instagram feed of [Micheál](https://www.instagram.com/popshaped/). It is posted here with permission. + + diff --git a/markdown/org/showcase/simon-by-mick/es.md b/markdown/org/showcase/simon-by-mick/es.md new file mode 100644 index 00000000000..5fa6400b773 --- /dev/null +++ b/markdown/org/showcase/simon-by-mick/es.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "This matching shirt and mask are coordinated perfection" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fa6dc530445d2457e8b91320af38c4ef8389a369-750x750.jpg" +intro: "Micheál made this fantastic Simon shirt in multicolored dots, with Florence face mask to match!" +title: "Speckled Simon Shirt by Mick [No traducido]" +--- + +Micheál made this fantastic Simon shirt in multicolored dots, with Florence face mask to match! + + +This picture is from the instagram feed of [Micheál](https://www.instagram.com/popshaped/). It is posted here with permission. + + diff --git a/markdown/org/showcase/simon-by-mick/fr.md b/markdown/org/showcase/simon-by-mick/fr.md new file mode 100644 index 00000000000..9f90f1e6689 --- /dev/null +++ b/markdown/org/showcase/simon-by-mick/fr.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "Cette chemise et ce masque assorti sont coordonnés la perfection" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fa6dc530445d2457e8b91320af38c4ef8389a369-750x750.jpg" +intro: "Micheál a fait cette fantastique chemise Simon dans un tissu à pois multicolores, avec le masque de Florence pour être assorti !" +title: "Chemise Simon mouchetée par Mick" +--- + + +Micheál a fait cette fantastique chemise Simon dans un tissu à pois multicolores, avec le masque de Florence pour être assorti ! + + +Cette image provient du flux Instagram de [Micheál](https://www.instagram.com/popshaped/). Elle est publiée ici avec son autorisation. + + diff --git a/markdown/org/showcase/simon-by-mick/nl.md b/markdown/org/showcase/simon-by-mick/nl.md new file mode 100644 index 00000000000..cdf4f820a44 --- /dev/null +++ b/markdown/org/showcase/simon-by-mick/nl.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "This matching shirt and mask are coordinated perfection" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fa6dc530445d2457e8b91320af38c4ef8389a369-750x750.jpg" +intro: "Micheál made this fantastic Simon shirt in multicolored dots, with Florence face mask to match!" +title: "Speckled Simon Shirt by Mick [Niet vertaald]" +--- + +Micheál made this fantastic Simon shirt in multicolored dots, with Florence face mask to match! + + +This picture is from the instagram feed of [Micheál](https://www.instagram.com/popshaped/). It is posted here with permission. + + diff --git a/markdown/org/showcase/simon-by-sewandrew/de.md b/markdown/org/showcase/simon-by-sewandrew/de.md new file mode 100644 index 00000000000..8f20f7f49fc --- /dev/null +++ b/markdown/org/showcase/simon-by-sewandrew/de.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Simon shirt by Andrew" +date: "2021-01-22" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/582ebfb48a506d583b6654cd296736c21f37807a-746x746.jpg" +intro: "This excellent Simon shirt was made by Andrew, who also blogged about the process ." +title: "[auf Englisch] Simon by Andrew" +--- + + +This excellent Simon shirt was made by Andrew, who also [blogged about the process](https://sewandrew.com/2019/03/13/spiderweb-paper-a-freesewing-shirt/). + + + +This picture is from [the Instagram feed of @sewandrew](https://www.instagram.com/sewandrew/). It is reposted here with permission. + + + diff --git a/markdown/org/showcase/simon-by-sewandrew/en.md b/markdown/org/showcase/simon-by-sewandrew/en.md new file mode 100644 index 00000000000..c7d38410d1f --- /dev/null +++ b/markdown/org/showcase/simon-by-sewandrew/en.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Simon shirt by Andrew" +date: "2021-01-22" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/582ebfb48a506d583b6654cd296736c21f37807a-746x746.jpg" +intro: "This excellent Simon shirt was made by Andrew, who also blogged about the process ." +title: "Simon by Andrew" +--- + + +This excellent Simon shirt was made by Andrew, who also [blogged about the process](https://sewandrew.com/2019/03/13/spiderweb-paper-a-freesewing-shirt/). + + + +This picture is from [the Instagram feed of @sewandrew](https://www.instagram.com/sewandrew/). It is reposted here with permission. + + + diff --git a/markdown/org/showcase/simon-by-sewandrew/es.md b/markdown/org/showcase/simon-by-sewandrew/es.md new file mode 100644 index 00000000000..524b257e30d --- /dev/null +++ b/markdown/org/showcase/simon-by-sewandrew/es.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Simon shirt by Andrew" +date: "2021-01-22" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/582ebfb48a506d583b6654cd296736c21f37807a-746x746.jpg" +intro: "This excellent Simon shirt was made by Andrew, who also blogged about the process ." +title: "Simon by Andrew [No traducido]" +--- + + +This excellent Simon shirt was made by Andrew, who also [blogged about the process](https://sewandrew.com/2019/03/13/spiderweb-paper-a-freesewing-shirt/). + + + +This picture is from [the Instagram feed of @sewandrew](https://www.instagram.com/sewandrew/). It is reposted here with permission. + + + diff --git a/markdown/org/showcase/simon-by-sewandrew/fr.md b/markdown/org/showcase/simon-by-sewandrew/fr.md new file mode 100644 index 00000000000..185315467ab --- /dev/null +++ b/markdown/org/showcase/simon-by-sewandrew/fr.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Chemise Simon par Andrew" +date: "2021-01-22" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/582ebfb48a506d583b6654cd296736c21f37807a-746x746.jpg" +intro: "Cet excellent chemise Simon a été fabriqué par Andrew, qui a aussi blogué sur le processus de réalisation ." +title: "Simon par Andrew" +--- + + +Cet excellent chemise Simon a été fabriqué par Andrew, qui a aussi [blogué sur le processus de réalisation](https://sewandrew.com/2019/03/13/spiderweb-paper-a-freesewing-shirt/). + + + +Cette image provient du [flux Instagram de @sewandrew](https://www.instagram.com/sewandrew/). Elle est publiée ici avec son autorisation. + + + diff --git a/markdown/org/showcase/simon-by-sewandrew/nl.md b/markdown/org/showcase/simon-by-sewandrew/nl.md new file mode 100644 index 00000000000..7d27253a077 --- /dev/null +++ b/markdown/org/showcase/simon-by-sewandrew/nl.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Simon hemd door Andrew" +date: "2021-01-22" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/582ebfb48a506d583b6654cd296736c21f37807a-746x746.jpg" +intro: "Dit uitstekende Simon hemd werd gemaakt door Andrew, die ook een blogpost schreef over het proces ." +title: "Simon door Andrew" +--- + + +Dit uitstekende Simon hemd werd gemaakt door Andrew, die ook [een blogpost schreef over het proces](https://sewandrew.com/2019/03/13/spiderweb-paper-a-freesewing-shirt/). + + + +Deze foto is komt van [de Instagram feed van @sewandrew](https://www.instagram.com/sewandrew/). Hij werd hier gepost met toestemming. + + + diff --git a/markdown/org/showcase/simon-by-stefan/de.md b/markdown/org/showcase/simon-by-stefan/de.md new file mode 100644 index 00000000000..873f21a6094 --- /dev/null +++ b/markdown/org/showcase/simon-by-stefan/de.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Stefan wearing Simon shirt, holding his grandson" +date: "2020-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/92109efedf33b53ac0664aa70d6c5e160da81e28-1200x1600.jpg" +intro: "[auf Englisch] Simon shirt by Stefan" +title: "[auf Englisch] Simon shirt by Stefan" +--- + + +Stefan's Simon shirt review is unambiguous - as he puts it, "Simon shirt is what I love most". This is his first Simon, made around 2 years ago. + diff --git a/markdown/org/showcase/simon-by-stefan/en.md b/markdown/org/showcase/simon-by-stefan/en.md new file mode 100644 index 00000000000..7bd4ecabdc8 --- /dev/null +++ b/markdown/org/showcase/simon-by-stefan/en.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Stefan wearing Simon shirt, holding his grandson" +date: "2020-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/92109efedf33b53ac0664aa70d6c5e160da81e28-1200x1600.jpg" +intro: "Simon shirt by Stefan" +title: "Simon shirt by Stefan" +--- + + +Stefan's Simon shirt review is unambiguous - as he puts it, "Simon shirt is what I love most". This is his first Simon, made around 2 years ago. + diff --git a/markdown/org/showcase/simon-by-stefan/es.md b/markdown/org/showcase/simon-by-stefan/es.md new file mode 100644 index 00000000000..32b35c98791 --- /dev/null +++ b/markdown/org/showcase/simon-by-stefan/es.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Stefan wearing Simon shirt, holding his grandson" +date: "2020-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/92109efedf33b53ac0664aa70d6c5e160da81e28-1200x1600.jpg" +intro: "Simon shirt by Stefan [No traducido]" +title: "Simon shirt by Stefan [No traducido]" +--- + + +Stefan's Simon shirt review is unambiguous - as he puts it, "Simon shirt is what I love most". This is his first Simon, made around 2 years ago. + diff --git a/markdown/org/showcase/simon-by-stefan/fr.md b/markdown/org/showcase/simon-by-stefan/fr.md new file mode 100644 index 00000000000..0361b066154 --- /dev/null +++ b/markdown/org/showcase/simon-by-stefan/fr.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Stefan porte une chemise Simon en tenant son petit-fils" +date: "2020-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/92109efedf33b53ac0664aa70d6c5e160da81e28-1200x1600.jpg" +intro: "Chemise Simon par Stefan" +title: "Chemise Simon par Stefan" +--- + + +L'avis de Stefan sur la chemise Simon est sans ambiguïté - comme il le dit, "la chemise Simon est ce que j'aime le plus". C'est son premier Simon, réalisé il y a environ 2 ans. + diff --git a/markdown/org/showcase/simon-by-stefan/nl.md b/markdown/org/showcase/simon-by-stefan/nl.md new file mode 100644 index 00000000000..261a1581538 --- /dev/null +++ b/markdown/org/showcase/simon-by-stefan/nl.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Stefan wearing Simon shirt, holding his grandson" +date: "2020-10-20" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/92109efedf33b53ac0664aa70d6c5e160da81e28-1200x1600.jpg" +intro: "Simon shirt by Stefan [Niet vertaald]" +title: "Simon shirt by Stefan [Niet vertaald]" +--- + + +Stefan's Simon shirt review is unambiguous - as he puts it, "Simon shirt is what I love most". This is his first Simon, made around 2 years ago. + diff --git a/markdown/org/showcase/simon-for-schorsch/de.md b/markdown/org/showcase/simon-for-schorsch/de.md new file mode 100644 index 00000000000..d49bbce36f0 --- /dev/null +++ b/markdown/org/showcase/simon-for-schorsch/de.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "A Simon for Schorsch" +date: "2020-12-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/242723e896e21decb6f7363a4defa62654165546-1536x2048.jpg" +intro: "Perhaps the most adorable Simon to date, this shirt was made for a FreeSewing user's baby frog, Schorsch." +title: "[auf Englisch] A Simon for Schorsch" +--- + + +Perhaps the most adorable Simon to date, this shirt was made for a FreeSewing user's baby frog, Schorsch. + +This picture was originally posted on Twitter and is reproduced here with permission. + + diff --git a/markdown/org/showcase/simon-for-schorsch/en.md b/markdown/org/showcase/simon-for-schorsch/en.md new file mode 100644 index 00000000000..87a0bc02c25 --- /dev/null +++ b/markdown/org/showcase/simon-for-schorsch/en.md @@ -0,0 +1,14 @@ +--- +maker: "unknown" +caption: "A Simon for Schorsch" +date: "2020-12-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/242723e896e21decb6f7363a4defa62654165546-1536x2048.jpg" +intro: "Perhaps the most adorable Simon to date, this shirt was made for a FreeSewing user's baby frog, Schorsch." +title: "A Simon for Schorsch" +--- + + +Perhaps the most adorable Simon to date, this shirt was made for a FreeSewing user's baby frog, Schorsch. + +This picture was originally posted on Twitter and is reproduced here with permission. + diff --git a/markdown/org/showcase/simon-for-schorsch/es.md b/markdown/org/showcase/simon-for-schorsch/es.md new file mode 100644 index 00000000000..6076e27fe1f --- /dev/null +++ b/markdown/org/showcase/simon-for-schorsch/es.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "A Simon for Schorsch" +date: "2020-12-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/242723e896e21decb6f7363a4defa62654165546-1536x2048.jpg" +intro: "Perhaps the most adorable Simon to date, this shirt was made for a FreeSewing user's baby frog, Schorsch." +title: "A Simon for Schorsch [No traducido]" +--- + + +Perhaps the most adorable Simon to date, this shirt was made for a FreeSewing user's baby frog, Schorsch. + +This picture was originally posted on Twitter and is reproduced here with permission. + + diff --git a/markdown/org/showcase/simon-for-schorsch/fr.md b/markdown/org/showcase/simon-for-schorsch/fr.md new file mode 100644 index 00000000000..8fa07a0a035 --- /dev/null +++ b/markdown/org/showcase/simon-for-schorsch/fr.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Un Simon pour Schorsch" +date: "2020-12-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/242723e896e21decb6f7363a4defa62654165546-1536x2048.jpg" +intro: "Peut-être le plus adorable Simon à ce jour, cette chemise a été faite pour la grenouille du bébé d'un utilisateur de FreeSewing, Schorsch." +title: "Un Simon pour Schorsch" +--- + + +Peut-être le plus adorable Simon à ce jour, cette chemise a été faite pour la grenouille du bébé d'un utilisateur de FreeSewing, Schorsch. + +Cette photo a été postée à l'origine sur Twitter et est reproduite ici avec permission. + + diff --git a/markdown/org/showcase/simon-for-schorsch/nl.md b/markdown/org/showcase/simon-for-schorsch/nl.md new file mode 100644 index 00000000000..ad3ad19c006 --- /dev/null +++ b/markdown/org/showcase/simon-for-schorsch/nl.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "A Simon for Schorsch" +date: "2020-12-28" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/242723e896e21decb6f7363a4defa62654165546-1536x2048.jpg" +intro: "Perhaps the most adorable Simon to date, this shirt was made for a FreeSewing user's baby frog, Schorsch." +title: "A Simon for Schorsch [Niet vertaald]" +--- + + +Perhaps the most adorable Simon to date, this shirt was made for a FreeSewing user's baby frog, Schorsch. + +This picture was originally posted on Twitter and is reproduced here with permission. + + diff --git a/markdown/org/showcase/simon-on-snook/de.md b/markdown/org/showcase/simon-on-snook/de.md new file mode 100644 index 00000000000..3c7f095c9fc --- /dev/null +++ b/markdown/org/showcase/simon-on-snook/de.md @@ -0,0 +1,20 @@ +--- +maker: "unknown" +caption: "If your partner's name was Snook, you'd call him snook too." +date: "2017-11-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/adbe9f0fb465866669913ed393d77c0ae48a59f7-2000x2667.jpg" +intro: "[auf Englisch] A Simon shirt by Kris for her Snook" +title: "[auf Englisch] A Simon shirt by Kris for her Snook" +--- + +![View of the back](https://posts.freesewing.org/uploads/simon_on_snook_high_back_405a53e578.jpg "View of the back") + + + +###### See the original on [@web_goddess](/users/web_goddess)'s blog +This picture is from [this blog post](https://www.web-goddess.org/archive/18117) +on [web-goddess.org](https://www.web-goddess.org/). + +It is reposted here with permission. + + diff --git a/markdown/org/showcase/simon-on-snook/en.md b/markdown/org/showcase/simon-on-snook/en.md new file mode 100644 index 00000000000..fbce0bea948 --- /dev/null +++ b/markdown/org/showcase/simon-on-snook/en.md @@ -0,0 +1,20 @@ +--- +maker: "unknown" +caption: "If your partner's name was Snook, you'd call him snook too." +date: "2017-11-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/adbe9f0fb465866669913ed393d77c0ae48a59f7-2000x2667.jpg" +intro: "A Simon shirt by Kris for her Snook" +title: "A Simon shirt by Kris for her Snook" +--- + +![View of the back](https://posts.freesewing.org/uploads/simon_on_snook_high_back_405a53e578.jpg "View of the back") + + + +###### See the original on [@web_goddess](/users/web_goddess)'s blog +This picture is from [this blog post](https://www.web-goddess.org/archive/18117) +on [web-goddess.org](https://www.web-goddess.org/). + +It is reposted here with permission. + + diff --git a/markdown/org/showcase/simon-on-snook/es.md b/markdown/org/showcase/simon-on-snook/es.md new file mode 100644 index 00000000000..1732212f8b0 --- /dev/null +++ b/markdown/org/showcase/simon-on-snook/es.md @@ -0,0 +1,20 @@ +--- +maker: "unknown" +caption: "If your partner's name was Snook, you'd call him snook too." +date: "2017-11-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/adbe9f0fb465866669913ed393d77c0ae48a59f7-2000x2667.jpg" +intro: "A Simon shirt by Kris for her Snook [No traducido]" +title: "A Simon shirt by Kris for her Snook [No traducido]" +--- + +![View of the back](https://posts.freesewing.org/uploads/simon_on_snook_high_back_405a53e578.jpg "View of the back") + + + +###### See the original on [@web_goddess](/users/web_goddess)'s blog +This picture is from [this blog post](https://www.web-goddess.org/archive/18117) +on [web-goddess.org](https://www.web-goddess.org/). + +It is reposted here with permission. + + diff --git a/markdown/org/showcase/simon-on-snook/fr.md b/markdown/org/showcase/simon-on-snook/fr.md new file mode 100644 index 00000000000..d908129b5ca --- /dev/null +++ b/markdown/org/showcase/simon-on-snook/fr.md @@ -0,0 +1,20 @@ +--- +maker: "unknown" +caption: "Si le nom de votre partenaire était Snook, vous l'appelleriez aussi snook." +date: "2017-11-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/adbe9f0fb465866669913ed393d77c0ae48a59f7-2000x2667.jpg" +intro: "Une chemise Simon par Kris pour son Snook" +title: "Une chemise Simon par Kris pour son Snook" +--- + +![Vue du dos](https://posts.freesewing.org/uploads/simon_on_snook_high_back_405a53e578.jpg "Vue du dos") + + + +###### Voir l'original sur le blog de [@web_goddess](/users/web_goddess) +Cette image provient de [ce billet de blog](https://www.web-goddess.org/archive/18117) +sur [web-goddess.org](https://www.web-goddess.org/). + +Elle est publiée ici avec son autorisation. + + diff --git a/markdown/org/showcase/simon-on-snook/nl.md b/markdown/org/showcase/simon-on-snook/nl.md new file mode 100644 index 00000000000..574e5da7109 --- /dev/null +++ b/markdown/org/showcase/simon-on-snook/nl.md @@ -0,0 +1,20 @@ +--- +maker: "unknown" +caption: "Als jouw partner Snook heette zou je hem ook zo noemen." +date: "2017-11-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/adbe9f0fb465866669913ed393d77c0ae48a59f7-2000x2667.jpg" +intro: "Een Simon hemd van Kris voor haar Snook" +title: "Een Simon hemd van Kris voor haar Snook" +--- + +![Zicht op de achterkant](https://posts.freesewing.org/uploads/simon_on_snook_high_back_405a53e578.jpg "Zicht op de achterkant") + + + +###### See the original on [@web_goddess](/users/web_goddess)'s blog +This picture is from [this blog post](https://www.web-goddess.org/archive/18117) +on [web-goddess.org](https://www.web-goddess.org/). + +Hij werd hier gepost met toestemming. + + diff --git a/markdown/org/showcase/simon-white-stripe/de.md b/markdown/org/showcase/simon-white-stripe/de.md new file mode 100644 index 00000000000..bacd7ed88b9 --- /dev/null +++ b/markdown/org/showcase/simon-white-stripe/de.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "Looking sharp in a striped Simon" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8eab7c7af8d12449b5763eb6747a2d7ba27fb637-1080x1080.jpg" +intro: "Michele made this Simon shirt in a white cotton with thin blue stripes. Don't miss the dark blue thread they used to add a little extra interest!" +title: "[auf Englisch] White Striped Simon Shirt by Michele" +--- + + +Michele made this Simon shirt in a white cotton with thin blue stripes. Don't miss the dark blue thread they used to add a little extra interest! + + +This picture is from the instagram feed of [Michele](https://www.instagram.com/swissarmywife/). It is posted here with permission. + + diff --git a/markdown/org/showcase/simon-white-stripe/en.md b/markdown/org/showcase/simon-white-stripe/en.md new file mode 100644 index 00000000000..0a3d7f0a393 --- /dev/null +++ b/markdown/org/showcase/simon-white-stripe/en.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Looking sharp in a striped Simon" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8eab7c7af8d12449b5763eb6747a2d7ba27fb637-1080x1080.jpg" +intro: "Michele made this Simon shirt in a white cotton with thin blue stripes. Don't miss the dark blue thread they used to add a little extra interest!" +title: "White Striped Simon Shirt by Michele" +--- + +Michele made this Simon shirt in a white cotton with thin blue stripes. Don't miss the dark blue thread they used to add a little extra interest! + + +This picture is from the instagram feed of [Michele](https://www.instagram.com/swissarmywife/). It is posted here with permission. + + diff --git a/markdown/org/showcase/simon-white-stripe/es.md b/markdown/org/showcase/simon-white-stripe/es.md new file mode 100644 index 00000000000..7750b5d7795 --- /dev/null +++ b/markdown/org/showcase/simon-white-stripe/es.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Looking sharp in a striped Simon" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8eab7c7af8d12449b5763eb6747a2d7ba27fb637-1080x1080.jpg" +intro: "Michele made this Simon shirt in a white cotton with thin blue stripes. Don't miss the dark blue thread they used to add a little extra interest!" +title: "White Striped Simon Shirt by Michele [No traducido]" +--- + +Michele made this Simon shirt in a white cotton with thin blue stripes. Don't miss the dark blue thread they used to add a little extra interest! + + +This picture is from the instagram feed of [Michele](https://www.instagram.com/swissarmywife/). It is posted here with permission. + + diff --git a/markdown/org/showcase/simon-white-stripe/fr.md b/markdown/org/showcase/simon-white-stripe/fr.md new file mode 100644 index 00000000000..b4783e737ad --- /dev/null +++ b/markdown/org/showcase/simon-white-stripe/fr.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "A l'air chic dans un Simon rayé" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8eab7c7af8d12449b5763eb6747a2d7ba27fb637-1080x1080.jpg" +intro: "Michele a fabriqué cette chemise Simon en coton blanc avec de fines rayures bleues. Ne manquez pas le fil bleu foncé qu'ils ont utilisé pour ajouter un peu d'intérêt supplémentaire !" +title: "Chemise Simon blanche rayée par Michele" +--- + + +Michele a fabriqué cette chemise Simon en coton blanc avec de fines rayures bleues. Ne manquez pas le fil bleu foncé qu'ils ont utilisé pour ajouter un peu d'intérêt supplémentaire ! + + +Cette image provient du flux Instagram de [Michele](https://www.instagram.com/swissarmywife/). Elle est publiée ici avec son autorisation. + + diff --git a/markdown/org/showcase/simon-white-stripe/nl.md b/markdown/org/showcase/simon-white-stripe/nl.md new file mode 100644 index 00000000000..64e5c3ae706 --- /dev/null +++ b/markdown/org/showcase/simon-white-stripe/nl.md @@ -0,0 +1,15 @@ +--- +maker: "unknown" +caption: "Looking sharp in a striped Simon" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/8eab7c7af8d12449b5763eb6747a2d7ba27fb637-1080x1080.jpg" +intro: "Michele made this Simon shirt in a white cotton with thin blue stripes. Don't miss the dark blue thread they used to add a little extra interest!" +title: "White Striped Simon Shirt by Michele [Niet vertaald]" +--- + +Michele made this Simon shirt in a white cotton with thin blue stripes. Don't miss the dark blue thread they used to add a little extra interest! + + +This picture is from the instagram feed of [Michele](https://www.instagram.com/swissarmywife/). It is posted here with permission. + + diff --git a/markdown/org/showcase/speckles-simon/de.md b/markdown/org/showcase/speckles-simon/de.md new file mode 100644 index 00000000000..cc74d0e0695 --- /dev/null +++ b/markdown/org/showcase/speckles-simon/de.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "That constrasting buttonhole packet is a great touch." +date: "2018-03-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/42a90db048975ca7afdcebe7c2d19e9c9e524b5c-1080x1194.jpg" +intro: "Allie writes:" +title: "[auf Englisch] A speckled simon by Allie for her husband" +--- + + +Allie writes: + +> Have you heard of freesewing.org? It’s pretty much the greatest thing ever! + + +This image and the quote above are from [the Aspiring Seamstress blog](https://theaspiringseamstress.wordpress.com/2018/03/01/freesewing-org-simon/) It is published here with permission. + +Follow the link above for a review of the pattern. + diff --git a/markdown/org/showcase/speckles-simon/en.md b/markdown/org/showcase/speckles-simon/en.md new file mode 100644 index 00000000000..c8f769b73ae --- /dev/null +++ b/markdown/org/showcase/speckles-simon/en.md @@ -0,0 +1,20 @@ +--- +maker: "unknown" +caption: "That constrasting buttonhole packet is a great touch." +date: "2018-03-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/42a90db048975ca7afdcebe7c2d19e9c9e524b5c-1080x1194.jpg" +intro: "Allie writes:" +title: "A speckled simon by Allie for her husband" +--- + + +Allie writes: + +> Have you heard of freesewing.org? It’s pretty much the greatest thing ever! + + +This image and the quote above are from [the Aspiring Seamstress blog](https://theaspiringseamstress.wordpress.com/2018/03/01/freesewing-org-simon/) +It is published here with permission. + +Follow the link above for a review of the pattern. + diff --git a/markdown/org/showcase/speckles-simon/es.md b/markdown/org/showcase/speckles-simon/es.md new file mode 100644 index 00000000000..cc7ee950cfa --- /dev/null +++ b/markdown/org/showcase/speckles-simon/es.md @@ -0,0 +1,20 @@ +--- +maker: "unknown" +caption: "That constrasting buttonhole packet is a great touch." +date: "2018-03-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/42a90db048975ca7afdcebe7c2d19e9c9e524b5c-1080x1194.jpg" +intro: "Allie writes:" +title: "A speckled simon by Allie for her husband [No traducido]" +--- + + +Allie writes: + +> Have you heard of freesewing.org? It’s pretty much the greatest thing ever! + + +This image and the quote above are from [the Aspiring Seamstress blog](https://theaspiringseamstress.wordpress.com/2018/03/01/freesewing-org-simon/) +It is published here with permission. + +Follow the link above for a review of the pattern. + diff --git a/markdown/org/showcase/speckles-simon/fr.md b/markdown/org/showcase/speckles-simon/fr.md new file mode 100644 index 00000000000..3629d5f80d7 --- /dev/null +++ b/markdown/org/showcase/speckles-simon/fr.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "Ces boutonnières contrastée ajoutent une excellente touche." +date: "2018-03-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/42a90db048975ca7afdcebe7c2d19e9c9e524b5c-1080x1194.jpg" +intro: "Allie écrit :" +title: "Un Simon moucheté par Allie pour son mari" +--- + + +Allie écrit : + +> Avez-vous entendu parler de freesewing.org ? C’est à peu près la meilleure chose qui ait jamais été ! + + +Cette photo et la citation ci-dessus proviennent du [blog Aspirant Seamstress](https://theaspiringseamstress.wordpress.com/2018/03/01/freesewing-org-simon/) Il est publié ici avec sa permission. + +Suivez le lien ci-dessus pour une revue du patron. + diff --git a/markdown/org/showcase/speckles-simon/nl.md b/markdown/org/showcase/speckles-simon/nl.md new file mode 100644 index 00000000000..e0f806f3d7a --- /dev/null +++ b/markdown/org/showcase/speckles-simon/nl.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "Dat contrasterende knoopsgatenpat is een mooi accent." +date: "2018-03-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/42a90db048975ca7afdcebe7c2d19e9c9e524b5c-1080x1194.jpg" +intro: "Allie schrijft:" +title: "Een gespikkelde Simon door Allie voor haar man" +--- + + +Allie schrijft: + +> Heb je al gehoord van freesewing.org? Het is zo ongeveer het beste ding ooit! + + +De foto en quote hierboven komen van de blog [the Aspiring Seamstress](https://theaspiringseamstress.wordpress.com/2018/03/01/freesewing-org-simon/). Ze zijn hier gepost met toestemming. + +Volg de link hierboven voor een review van het patroon. + diff --git a/markdown/org/showcase/sven-nr1/de.md b/markdown/org/showcase/sven-nr1/de.md new file mode 100644 index 00000000000..8a30770e400 --- /dev/null +++ b/markdown/org/showcase/sven-nr1/de.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "hashtag resist" +date: "2017-02-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/570d480fb537020b631203b4f4f2c3817e843e2e-1080x1080.jpg" +intro: "FIXME_no_intro" +title: "[auf Englisch] An era-appropriate Sven" +--- + + + diff --git a/markdown/org/showcase/sven-nr1/en.md b/markdown/org/showcase/sven-nr1/en.md new file mode 100644 index 00000000000..e1a1a30f10e --- /dev/null +++ b/markdown/org/showcase/sven-nr1/en.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "hashtag resist" +date: "2017-02-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/570d480fb537020b631203b4f4f2c3817e843e2e-1080x1080.jpg" +intro: "FIXME_no_intro" +title: "An era-appropriate Sven" +--- + + diff --git a/markdown/org/showcase/sven-nr1/es.md b/markdown/org/showcase/sven-nr1/es.md new file mode 100644 index 00000000000..5226b060a98 --- /dev/null +++ b/markdown/org/showcase/sven-nr1/es.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "hashtag resist" +date: "2017-02-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/570d480fb537020b631203b4f4f2c3817e843e2e-1080x1080.jpg" +intro: "FIXME_no_intro" +title: "An era-appropriate Sven [No traducido]" +--- + + diff --git a/markdown/org/showcase/sven-nr1/fr.md b/markdown/org/showcase/sven-nr1/fr.md new file mode 100644 index 00000000000..ce86497f1c4 --- /dev/null +++ b/markdown/org/showcase/sven-nr1/fr.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "hashtag résiste" +date: "2017-02-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/570d480fb537020b631203b4f4f2c3817e843e2e-1080x1080.jpg" +intro: "FIXME_no_intro" +title: "Un Sven dans l'air du temps" +--- + + + diff --git a/markdown/org/showcase/sven-nr1/nl.md b/markdown/org/showcase/sven-nr1/nl.md new file mode 100644 index 00000000000..b30b8e7a07b --- /dev/null +++ b/markdown/org/showcase/sven-nr1/nl.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "hashtag resist" +date: "2017-02-12" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/570d480fb537020b631203b4f4f2c3817e843e2e-1080x1080.jpg" +intro: "FIXME_no_intro" +title: "Een Sven van deze tijd" +--- + + + diff --git a/markdown/org/showcase/sven-nr2/de.md b/markdown/org/showcase/sven-nr2/de.md new file mode 100644 index 00000000000..2a0135c310a --- /dev/null +++ b/markdown/org/showcase/sven-nr2/de.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "This fabric has wool in it a is super warm." +date: "2017-02-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/75cfbc8d9b9d3e7615b5a9a2fe71d290656a00f3-1080x720.jpg" +intro: "FIXME_no_intro" +title: "[auf Englisch] The world's most boring sweater, perfect for the office" +--- + + + diff --git a/markdown/org/showcase/sven-nr2/en.md b/markdown/org/showcase/sven-nr2/en.md new file mode 100644 index 00000000000..ecaa1e7d671 --- /dev/null +++ b/markdown/org/showcase/sven-nr2/en.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "This fabric has wool in it a is super warm." +date: "2017-02-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/75cfbc8d9b9d3e7615b5a9a2fe71d290656a00f3-1080x720.jpg" +intro: "FIXME_no_intro" +title: "The world's most boring sweater, perfect for the office" +--- + + diff --git a/markdown/org/showcase/sven-nr2/es.md b/markdown/org/showcase/sven-nr2/es.md new file mode 100644 index 00000000000..d36dcf71f00 --- /dev/null +++ b/markdown/org/showcase/sven-nr2/es.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "This fabric has wool in it a is super warm." +date: "2017-02-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/75cfbc8d9b9d3e7615b5a9a2fe71d290656a00f3-1080x720.jpg" +intro: "FIXME_no_intro" +title: "The world's most boring sweater, perfect for the office [No traducido]" +--- + + diff --git a/markdown/org/showcase/sven-nr2/fr.md b/markdown/org/showcase/sven-nr2/fr.md new file mode 100644 index 00000000000..a4de0e46bfe --- /dev/null +++ b/markdown/org/showcase/sven-nr2/fr.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Ce tissu contient de la laine et il est super chaud." +date: "2017-02-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/75cfbc8d9b9d3e7615b5a9a2fe71d290656a00f3-1080x720.jpg" +intro: "FIXME_no_intro" +title: "Le chandail le plus ennuyeux au monde, parfait pour le bureau" +--- + + + diff --git a/markdown/org/showcase/sven-nr2/nl.md b/markdown/org/showcase/sven-nr2/nl.md new file mode 100644 index 00000000000..7bffe28790e --- /dev/null +++ b/markdown/org/showcase/sven-nr2/nl.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Deze stof bevat wol en is super warm." +date: "2017-02-18" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/75cfbc8d9b9d3e7615b5a9a2fe71d290656a00f3-1080x720.jpg" +intro: "FIXME_no_intro" +title: "De saaiste trui ter wereld, perfect voor op kantoor" +--- + + + diff --git a/markdown/org/showcase/sven-nr3/de.md b/markdown/org/showcase/sven-nr3/de.md new file mode 100644 index 00000000000..be8a7435858 --- /dev/null +++ b/markdown/org/showcase/sven-nr3/de.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "This fabric has wool in it a is super warm." +date: "2017-02-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/cd455112195f16c3e9e972e099831d228209769c-1080x1080.jpg" +intro: "FIXME_no_intro" +title: "[auf Englisch] A green Sven with a black shoulder detail and ribbing" +--- + + + diff --git a/markdown/org/showcase/sven-nr3/en.md b/markdown/org/showcase/sven-nr3/en.md new file mode 100644 index 00000000000..26d4df8a30c --- /dev/null +++ b/markdown/org/showcase/sven-nr3/en.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "This fabric has wool in it a is super warm." +date: "2017-02-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/cd455112195f16c3e9e972e099831d228209769c-1080x1080.jpg" +intro: "FIXME_no_intro" +title: "A green Sven with a black shoulder detail and ribbing" +--- + + diff --git a/markdown/org/showcase/sven-nr3/es.md b/markdown/org/showcase/sven-nr3/es.md new file mode 100644 index 00000000000..aa2ca72065c --- /dev/null +++ b/markdown/org/showcase/sven-nr3/es.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "This fabric has wool in it a is super warm." +date: "2017-02-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/cd455112195f16c3e9e972e099831d228209769c-1080x1080.jpg" +intro: "FIXME_no_intro" +title: "A green Sven with a black shoulder detail and ribbing [No traducido]" +--- + + diff --git a/markdown/org/showcase/sven-nr3/fr.md b/markdown/org/showcase/sven-nr3/fr.md new file mode 100644 index 00000000000..c83342a80c9 --- /dev/null +++ b/markdown/org/showcase/sven-nr3/fr.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Ce tissu contient de la laine et il est super chaud." +date: "2017-02-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/cd455112195f16c3e9e972e099831d228209769c-1080x1080.jpg" +intro: "FIXME_no_intro" +title: "Un Sven vert avec un détail d'épaule de bande noire" +--- + + + diff --git a/markdown/org/showcase/sven-nr3/nl.md b/markdown/org/showcase/sven-nr3/nl.md new file mode 100644 index 00000000000..5c4eb1d4396 --- /dev/null +++ b/markdown/org/showcase/sven-nr3/nl.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Deze stof bevat wol en is super warm." +date: "2017-02-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/cd455112195f16c3e9e972e099831d228209769c-1080x1080.jpg" +intro: "FIXME_no_intro" +title: "Een groene Sven met zwarte schouderdetails en boord" +--- + + + diff --git a/markdown/org/showcase/tartan-fu-mask/de.md b/markdown/org/showcase/tartan-fu-mask/de.md new file mode 100644 index 00000000000..0d05909c7f7 --- /dev/null +++ b/markdown/org/showcase/tartan-fu-mask/de.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "Sorcha wears a red and blue tartan Florence face mask" +date: "2020-03-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/36e7302d2cbddb4d0d739d8c25e7b0c388c1fee9-2000x1500.jpg" +intro: "Sorcha ist eine Angestellte der Universitätsklinik Antwerpen , eines der beiden belgischen Referenzzentren für Coronaviren." +title: "[auf Englisch] A Florence face mask in red and blue" +--- + + +Sorcha ist eine Angestellte der [Universitätsklinik Antwerpen](https://www.uza.be/), eines der beiden belgischen Referenzzentren für Coronaviren. + +At work, she wears a medical-grade face mask. This [Florence face mask](/designs/florence/) is for her commute to work on public transport. + + + diff --git a/markdown/org/showcase/tartan-fu-mask/en.md b/markdown/org/showcase/tartan-fu-mask/en.md new file mode 100644 index 00000000000..3d350565a75 --- /dev/null +++ b/markdown/org/showcase/tartan-fu-mask/en.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "Sorcha wears a red and blue tartan Florence face mask" +date: "2020-03-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/36e7302d2cbddb4d0d739d8c25e7b0c388c1fee9-2000x1500.jpg" +intro: "A Florence face mask in red and blue" +title: "A Florence face mask in red and blue" +--- + +Sorcha is a healthcare provider working in the [Antwerp University Hospital](https://www.uza.be/), +one of Belgium's two centres of reference for coronavirus. + +At work, she wears a medical-grade face mask. This [Florence face mask](/designs/florence/) is for her commute to work on public transport. + + + diff --git a/markdown/org/showcase/tartan-fu-mask/es.md b/markdown/org/showcase/tartan-fu-mask/es.md new file mode 100644 index 00000000000..7730bbf42be --- /dev/null +++ b/markdown/org/showcase/tartan-fu-mask/es.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "Sorcha wears a red and blue tartan Florence face mask" +date: "2020-03-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/36e7302d2cbddb4d0d739d8c25e7b0c388c1fee9-2000x1500.jpg" +intro: "A Florence face mask in red and blue [No traducido]" +title: "A Florence face mask in red and blue [No traducido]" +--- + +Sorcha is a healthcare provider working in the [Antwerp University Hospital](https://www.uza.be/), +one of Belgium's two centres of reference for coronavirus. + +At work, she wears a medical-grade face mask. This [Florence face mask](/designs/florence/) is for her commute to work on public transport. + + + diff --git a/markdown/org/showcase/tartan-fu-mask/fr.md b/markdown/org/showcase/tartan-fu-mask/fr.md new file mode 100644 index 00000000000..43a199586b7 --- /dev/null +++ b/markdown/org/showcase/tartan-fu-mask/fr.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "Sorcha porte un masque Florence en tissu écossais rouge et bleu" +date: "2020-03-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/36e7302d2cbddb4d0d739d8c25e7b0c388c1fee9-2000x1500.jpg" +intro: "Sorcha est une professionnelle de santé travaillant à l'hôpital universitaire d'Anvers , un des deux centres de référence belges pour le coronavirus." +title: "Un masque Florence en rouge et bleu" +--- + + +Sorcha est une professionnelle de santé travaillant à l'hôpital universitaire [d'Anvers](https://www.uza.be/), un des deux centres de référence belges pour le coronavirus. + +Au travail, elle porte un masque de qualité médicale. Elle utilise ce masque [Florence](/designs/florence/) dans les transports en commun qu'elle prend pour aller travailler. + + + diff --git a/markdown/org/showcase/tartan-fu-mask/nl.md b/markdown/org/showcase/tartan-fu-mask/nl.md new file mode 100644 index 00000000000..c87d9bacb11 --- /dev/null +++ b/markdown/org/showcase/tartan-fu-mask/nl.md @@ -0,0 +1,16 @@ +--- +maker: "unknown" +caption: "Sorcha draagt een rood en blauw geruit Florence mondmasker" +date: "2020-03-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/36e7302d2cbddb4d0d739d8c25e7b0c388c1fee9-2000x1500.jpg" +intro: "Sorcha is a healthcare provider working in the Antwerp University Hospital , one of Belgium's two centres of reference for coronavirus." +title: "Een Florence mondmasker in rood en blauw" +--- + + +Sorcha is a healthcare provider working in the [Antwerp University Hospital](https://www.uza.be/), one of Belgium's two centres of reference for coronavirus. + +Op haar werk draagt ze een medisch mondmasker. Dit [Florence mondmasker](/designs/florence/) is voor haar woon-werkverplaatsing met het openbaar vervoer. + + + diff --git a/markdown/org/showcase/teagan-karen/de.md b/markdown/org/showcase/teagan-karen/de.md new file mode 100644 index 00000000000..4f0f6bf0b35 --- /dev/null +++ b/markdown/org/showcase/teagan-karen/de.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Karen in her Teagan T-shirt" +date: "2020-10-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/065f4c5cf9977fa2a24938964fb1e700a2dd1ea2-2048x2048.jpg" +intro: "Karen made this version of the Teagan T-shirt drafted for high-bust measurements, one of several options for making the Teagan T-shirt just right for you!" +title: "[auf Englisch] Teagan T-Shirt by Karen" +--- + + +Karen made this version of [the Teagan T-shirt](/designs/teagan/) drafted for high-bust measurements, one of several options for making the Teagan T-shirt just right for you! + diff --git a/markdown/org/showcase/teagan-karen/en.md b/markdown/org/showcase/teagan-karen/en.md new file mode 100644 index 00000000000..0c7d0838da5 --- /dev/null +++ b/markdown/org/showcase/teagan-karen/en.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Karen in her Teagan T-shirt" +date: "2020-10-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/065f4c5cf9977fa2a24938964fb1e700a2dd1ea2-2048x2048.jpg" +intro: "Karen made this version of the Teagan T-shirt drafted for high-bust measurements, one of several options for making the Teagan T-shirt just right for you!" +title: "Teagan T-Shirt by Karen" +--- + +Karen made this version of [the Teagan T-shirt](/designs/teagan/) drafted for high-bust measurements, one of several options for making the Teagan T-shirt just right for you! + diff --git a/markdown/org/showcase/teagan-karen/es.md b/markdown/org/showcase/teagan-karen/es.md new file mode 100644 index 00000000000..6f1e491f08a --- /dev/null +++ b/markdown/org/showcase/teagan-karen/es.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Karen in her Teagan T-shirt" +date: "2020-10-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/065f4c5cf9977fa2a24938964fb1e700a2dd1ea2-2048x2048.jpg" +intro: "Karen made this version of the Teagan T-shirt drafted for high-bust measurements, one of several options for making the Teagan T-shirt just right for you!" +title: "Teagan T-Shirt by Karen [No traducido]" +--- + +Karen made this version of [the Teagan T-shirt](/designs/teagan/) drafted for high-bust measurements, one of several options for making the Teagan T-shirt just right for you! + diff --git a/markdown/org/showcase/teagan-karen/fr.md b/markdown/org/showcase/teagan-karen/fr.md new file mode 100644 index 00000000000..8f258efff96 --- /dev/null +++ b/markdown/org/showcase/teagan-karen/fr.md @@ -0,0 +1,12 @@ +--- +maker: "unknown" +caption: "Karen dans son T-shirt Teagan" +date: "2020-10-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/065f4c5cf9977fa2a24938964fb1e700a2dd1ea2-2048x2048.jpg" +intro: "Karen a fait cette version du le T-shirt Teagan dessiné avec l'option pour mesures du dessus de poitrine, l'une des nombreuses options pour faire le T-shirt Teagan parfait pour vous !" +title: "T-shirt Teagan par Karen" +--- + + +Karen a fait cette version du [le T-shirt Teagan](/designs/teagan/) dessiné avec l'option pour mesures du dessus de poitrine, l'une des nombreuses options pour faire le T-shirt Teagan parfait pour vous ! + diff --git a/markdown/org/showcase/teagan-karen/nl.md b/markdown/org/showcase/teagan-karen/nl.md new file mode 100644 index 00000000000..3b4878d517f --- /dev/null +++ b/markdown/org/showcase/teagan-karen/nl.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Karen in her Teagan T-shirt" +date: "2020-10-19" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/065f4c5cf9977fa2a24938964fb1e700a2dd1ea2-2048x2048.jpg" +intro: "Karen made this version of the Teagan T-shirt drafted for high-bust measurements, one of several options for making the Teagan T-shirt just right for you!" +title: "Teagan T-Shirt by Karen [Niet vertaald]" +--- + +Karen made this version of [the Teagan T-shirt](/designs/teagan/) drafted for high-bust measurements, one of several options for making the Teagan T-shirt just right for you! + diff --git a/markdown/org/showcase/theo-by-theodore/de.md b/markdown/org/showcase/theo-by-theodore/de.md new file mode 100644 index 00000000000..38895dba477 --- /dev/null +++ b/markdown/org/showcase/theo-by-theodore/de.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Cropped trousers by Theodore" +date: "2019-06-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e575a527685d83546061ac9508fd6ec83cd5bbfc-2160x3840.jpg" +intro: "Theodore writes on Reddit :" +title: "[auf Englisch] Theodore makes cropped Theo trousers" +--- + + +Theodore writes [on Reddit](https://www.reddit.com/r/sewing/comments/c1fue3/cropped_pants_for_the_summer_weather/): + +> Are capris cool again yet? I don't care, I like them. +> +> Used some nice olive green Armani cotton fabric with a customized pattern from FreeSewing.org, the Theo model. Drafted for a higher rise, they fit really nice! + + diff --git a/markdown/org/showcase/theo-by-theodore/en.md b/markdown/org/showcase/theo-by-theodore/en.md new file mode 100644 index 00000000000..7d2f9c4786b --- /dev/null +++ b/markdown/org/showcase/theo-by-theodore/en.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Cropped trousers by Theodore" +date: "2019-06-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e575a527685d83546061ac9508fd6ec83cd5bbfc-2160x3840.jpg" +intro: "Theodore writes on Reddit :" +title: "Theodore makes cropped Theo trousers" +--- + + +Theodore writes [on Reddit](https://www.reddit.com/r/sewing/comments/c1fue3/cropped_pants_for_the_summer_weather/): + +> Are capris cool again yet? I don't care, I like them. +> +> Used some nice olive green Armani cotton fabric with a customized pattern from FreeSewing.org, the Theo model. Drafted for a higher rise, they fit really nice! + + diff --git a/markdown/org/showcase/theo-by-theodore/es.md b/markdown/org/showcase/theo-by-theodore/es.md new file mode 100644 index 00000000000..d98e7d50996 --- /dev/null +++ b/markdown/org/showcase/theo-by-theodore/es.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Cropped trousers by Theodore" +date: "2019-06-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e575a527685d83546061ac9508fd6ec83cd5bbfc-2160x3840.jpg" +intro: "Theodore writes on Reddit :" +title: "Theodore makes cropped Theo trousers [No traducido]" +--- + + +Theodore writes [on Reddit](https://www.reddit.com/r/sewing/comments/c1fue3/cropped_pants_for_the_summer_weather/): + +> Are capris cool again yet? I don't care, I like them. +> +> Used some nice olive green Armani cotton fabric with a customized pattern from FreeSewing.org, the Theo model. Drafted for a higher rise, they fit really nice! + + diff --git a/markdown/org/showcase/theo-by-theodore/fr.md b/markdown/org/showcase/theo-by-theodore/fr.md new file mode 100644 index 00000000000..059727ed807 --- /dev/null +++ b/markdown/org/showcase/theo-by-theodore/fr.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Pantacourt par Theodore" +date: "2019-06-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e575a527685d83546061ac9508fd6ec83cd5bbfc-2160x3840.jpg" +intro: "Theodore écrit sur Reddit :" +title: "Theodore réalise un pantalon Theo raccourci" +--- + + +Theodore écrit [sur Reddit](https://www.reddit.com/r/sewing/comments/c1fue3/cropped_pants_for_the_summer_weather/) : + +> Les corsaires sont-ils encore cool ? Je m'en fiche, je les aime. +> +> Utilisé un joli tissu de coton Armani vert olive avec un patron personnalisé de FreeSewing.org, le modèle Theo. Conçu pour une hauteur plus élevée, il tombe vraiment bien ! + + diff --git a/markdown/org/showcase/theo-by-theodore/nl.md b/markdown/org/showcase/theo-by-theodore/nl.md new file mode 100644 index 00000000000..835bffc2723 --- /dev/null +++ b/markdown/org/showcase/theo-by-theodore/nl.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Cropped trousers by Theodore" +date: "2019-06-17" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e575a527685d83546061ac9508fd6ec83cd5bbfc-2160x3840.jpg" +intro: "Theodore writes on Reddit :" +title: "Theodore makes cropped Theo trousers [Niet vertaald]" +--- + + +Theodore writes [on Reddit](https://www.reddit.com/r/sewing/comments/c1fue3/cropped_pants_for_the_summer_weather/): + +> Are capris cool again yet? I don't care, I like them. +> +> Used some nice olive green Armani cotton fabric with a customized pattern from FreeSewing.org, the Theo model. Drafted for a higher rise, they fit really nice! + + diff --git a/markdown/org/showcase/theo-jeroen/de.md b/markdown/org/showcase/theo-jeroen/de.md new file mode 100644 index 00000000000..0bca66b7278 --- /dev/null +++ b/markdown/org/showcase/theo-jeroen/de.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Red plaid perfection" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/89782b1ed572a5348c9ad925471f7e5252f630f7-750x750.jpg" +intro: "Jeroen made these shortened Theo trousers in a bright, bold red plaid. We love the way they turned out!" +title: "[auf Englisch] Red Plaid Theo Shorts by Jeroen" +--- + + +Jeroen made these shortened Theo trousers in a bright, bold red plaid. We love the way they turned out! + +Check out the matching Wahid waistcoat Jeroen made [here](https://freesewing.org/showcase/wahid-jeroen/)! + + +This picture is from the instagram feed of [Jeroen Keerl](https://www.instagram.com/jeroenkeerl/). It is posted here with permission. + + diff --git a/markdown/org/showcase/theo-jeroen/en.md b/markdown/org/showcase/theo-jeroen/en.md new file mode 100644 index 00000000000..7d99b8b94ac --- /dev/null +++ b/markdown/org/showcase/theo-jeroen/en.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Red plaid perfection" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/89782b1ed572a5348c9ad925471f7e5252f630f7-750x750.jpg" +intro: "Jeroen made these shortened Theo trousers in a bright, bold red plaid. We love the way they turned out!" +title: "Red Plaid Theo Shorts by Jeroen" +--- + +Jeroen made these shortened Theo trousers in a bright, bold red plaid. We love the way they turned out! + +Check out the matching Wahid waistcoat Jeroen made [here](https://freesewing.org/showcase/wahid-jeroen/)! + + +This picture is from the instagram feed of [Jeroen Keerl](https://www.instagram.com/jeroenkeerl/). It is posted here with permission. + + diff --git a/markdown/org/showcase/theo-jeroen/es.md b/markdown/org/showcase/theo-jeroen/es.md new file mode 100644 index 00000000000..fa93d3e45fd --- /dev/null +++ b/markdown/org/showcase/theo-jeroen/es.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Red plaid perfection" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/89782b1ed572a5348c9ad925471f7e5252f630f7-750x750.jpg" +intro: "Jeroen made these shortened Theo trousers in a bright, bold red plaid. We love the way they turned out!" +title: "Red Plaid Theo Shorts by Jeroen [No traducido]" +--- + +Jeroen made these shortened Theo trousers in a bright, bold red plaid. We love the way they turned out! + +Check out the matching Wahid waistcoat Jeroen made [here](https://freesewing.org/showcase/wahid-jeroen/)! + + +This picture is from the instagram feed of [Jeroen Keerl](https://www.instagram.com/jeroenkeerl/). It is posted here with permission. + + diff --git a/markdown/org/showcase/theo-jeroen/fr.md b/markdown/org/showcase/theo-jeroen/fr.md new file mode 100644 index 00000000000..ff95d89c19e --- /dev/null +++ b/markdown/org/showcase/theo-jeroen/fr.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "La perfection du tartan rouge" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/89782b1ed572a5348c9ad925471f7e5252f630f7-750x750.jpg" +intro: "Jeroen a fait ce pantalon Theo raccourci dans un tartan rouge vif et audacieux. Nous aimons la façon dont ça a évolué !" +title: "Short Theo en tartan rouge par Jeroen" +--- + + +Jeroen a fait ce pantalon Theo raccourci dans un tartan rouge vif et audacieux. Nous aimons la façon dont ça a évolué ! + +Jetez un coup d’œil au gilet Wahid assorti que Jeroen a fait [ici](https://freesewing.org/showcase/wahid-jeroen/)! + + +Cette image provient du flux instagram de [Jeroen Keerl](https://www.instagram.com/jeroenkeerl/). Elle est publiée ici avec son autorisation. + + diff --git a/markdown/org/showcase/theo-jeroen/nl.md b/markdown/org/showcase/theo-jeroen/nl.md new file mode 100644 index 00000000000..736d6f74348 --- /dev/null +++ b/markdown/org/showcase/theo-jeroen/nl.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Red plaid perfection" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/89782b1ed572a5348c9ad925471f7e5252f630f7-750x750.jpg" +intro: "Jeroen made these shortened Theo trousers in a bright, bold red plaid. We love the way they turned out!" +title: "Red Plaid Theo Shorts by Jeroen [Niet vertaald]" +--- + +Jeroen made these shortened Theo trousers in a bright, bold red plaid. We love the way they turned out! + +Check out the matching Wahid waistcoat Jeroen made [here](https://freesewing.org/showcase/wahid-jeroen/)! + + +This picture is from the instagram feed of [Jeroen Keerl](https://www.instagram.com/jeroenkeerl/). It is posted here with permission. + + diff --git a/markdown/org/showcase/tight-aaron/de.md b/markdown/org/showcase/tight-aaron/de.md new file mode 100644 index 00000000000..464fa745c02 --- /dev/null +++ b/markdown/org/showcase/tight-aaron/de.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "I misjudged the stretch on this fabric, and it's super clingy" +date: "2016-08-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3227be9fe8d84a9c1fa4891bb343571ec979a150-2048x2047.jpg" +intro: "FIXME_no_intro" +title: "[auf Englisch] Aaron in signature purple, but arguably too tight" +--- + + + diff --git a/markdown/org/showcase/tight-aaron/en.md b/markdown/org/showcase/tight-aaron/en.md new file mode 100644 index 00000000000..0107b82333d --- /dev/null +++ b/markdown/org/showcase/tight-aaron/en.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "I misjudged the stretch on this fabric, and it's super clingy" +date: "2016-08-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3227be9fe8d84a9c1fa4891bb343571ec979a150-2048x2047.jpg" +intro: "FIXME_no_intro" +title: "Aaron in signature purple, but arguably too tight" +--- + + diff --git a/markdown/org/showcase/tight-aaron/es.md b/markdown/org/showcase/tight-aaron/es.md new file mode 100644 index 00000000000..f2c867bea0a --- /dev/null +++ b/markdown/org/showcase/tight-aaron/es.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "I misjudged the stretch on this fabric, and it's super clingy" +date: "2016-08-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3227be9fe8d84a9c1fa4891bb343571ec979a150-2048x2047.jpg" +intro: "FIXME_no_intro" +title: "Aaron in signature purple, but arguably too tight [No traducido]" +--- + + diff --git a/markdown/org/showcase/tight-aaron/fr.md b/markdown/org/showcase/tight-aaron/fr.md new file mode 100644 index 00000000000..7b38c1e6f13 --- /dev/null +++ b/markdown/org/showcase/tight-aaron/fr.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "J'ai mal jugé l'élasticité sur ce tissu, et c'est super tendu" +date: "2016-08-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3227be9fe8d84a9c1fa4891bb343571ec979a150-2048x2047.jpg" +intro: "FIXME_no_intro" +title: "Aaron en violet signature, mais sans doute trop serré" +--- + + + diff --git a/markdown/org/showcase/tight-aaron/nl.md b/markdown/org/showcase/tight-aaron/nl.md new file mode 100644 index 00000000000..16d5c03c21b --- /dev/null +++ b/markdown/org/showcase/tight-aaron/nl.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Ik schatte de stretch van deze stof verkeerd in, en de boel spant" +date: "2016-08-16" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/3227be9fe8d84a9c1fa4891bb343571ec979a150-2048x2047.jpg" +intro: "FIXME_no_intro" +title: "Aaron in typisch paars, maar misschien wat strak" +--- + + + diff --git a/markdown/org/showcase/titan-by-deby/de.md b/markdown/org/showcase/titan-by-deby/de.md new file mode 100644 index 00000000000..580f90e25e6 --- /dev/null +++ b/markdown/org/showcase/titan-by-deby/de.md @@ -0,0 +1,12 @@ +--- +maker: "Deby" +caption: "A Titan block turned pants by Deby" +date: "2020-07-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/7a2406d93f4b40575b7c000e651a40a4b3191a74-2154x1280.jpg" +intro: "Deby tried out our Titan trouser block and liked the fit so much that she promptly turned it into proper trousers. She added a waistband and pockets to the basic block." +title: "[auf Englisch] Titan by Deby" +--- + + +Deby tried out our Titan trouser block and liked the fit so much that she promptly turned it into proper trousers. She added a waistband and pockets to the basic block. + diff --git a/markdown/org/showcase/titan-by-deby/en.md b/markdown/org/showcase/titan-by-deby/en.md new file mode 100644 index 00000000000..70faec324c7 --- /dev/null +++ b/markdown/org/showcase/titan-by-deby/en.md @@ -0,0 +1,13 @@ +--- +maker: "Deby" +caption: "A Titan block turned pants by Deby" +date: "2020-07-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/7a2406d93f4b40575b7c000e651a40a4b3191a74-2154x1280.jpg" +intro: "Titan by Deby" +title: "Titan by Deby" +--- + + +Deby tried out our Titan trouser block and liked the fit so much that she promptly turned it into proper trousers. +She added a waistband and pockets to the basic block. + diff --git a/markdown/org/showcase/titan-by-deby/es.md b/markdown/org/showcase/titan-by-deby/es.md new file mode 100644 index 00000000000..ae7d3efbf0f --- /dev/null +++ b/markdown/org/showcase/titan-by-deby/es.md @@ -0,0 +1,13 @@ +--- +maker: "Deby" +caption: "A Titan block turned pants by Deby" +date: "2020-07-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/7a2406d93f4b40575b7c000e651a40a4b3191a74-2154x1280.jpg" +intro: "Titan by Deby [No traducido]" +title: "Titan by Deby [No traducido]" +--- + + +Deby tried out our Titan trouser block and liked the fit so much that she promptly turned it into proper trousers. +She added a waistband and pockets to the basic block. + diff --git a/markdown/org/showcase/titan-by-deby/fr.md b/markdown/org/showcase/titan-by-deby/fr.md new file mode 100644 index 00000000000..23c4fc2a740 --- /dev/null +++ b/markdown/org/showcase/titan-by-deby/fr.md @@ -0,0 +1,12 @@ +--- +maker: "Deby" +caption: "Un bloc Titan transformé en pantalon par Deby" +date: "2020-07-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/7a2406d93f4b40575b7c000e651a40a4b3191a74-2154x1280.jpg" +intro: "Deby a essayé notre bloc de pantalon Titan et aimait tellement sa tenue qu'elle l'a rapidement transformé en vrai pantalon. Elle a ajouté une ceinture et des poches au bloc de base." +title: "Titan par Deby" +--- + + +Deby a essayé notre bloc de pantalon Titan et aimait tellement sa tenue qu'elle l'a rapidement transformé en vrai pantalon. Elle a ajouté une ceinture et des poches au bloc de base. + diff --git a/markdown/org/showcase/titan-by-deby/nl.md b/markdown/org/showcase/titan-by-deby/nl.md new file mode 100644 index 00000000000..f2f31cbf6a5 --- /dev/null +++ b/markdown/org/showcase/titan-by-deby/nl.md @@ -0,0 +1,12 @@ +--- +maker: "Deby" +caption: "Een Titan basispatroon werd een broek dankzij Deby" +date: "2020-07-25" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/7a2406d93f4b40575b7c000e651a40a4b3191a74-2154x1280.jpg" +intro: "Deby probeerde ons Titan basispatroon voor een broek en vond de pasvorm zo goed dat ze er meteen een echte broek van maakte. Ze voegde een tailleband en zakken toe aan het basispatroon." +title: "Titan door Deby" +--- + + +Deby probeerde ons Titan basispatroon voor een broek en vond de pasvorm zo goed dat ze er meteen een echte broek van maakte. Ze voegde een tailleband en zakken toe aan het basispatroon. + diff --git a/markdown/org/showcase/wahid-by-adam/de.md b/markdown/org/showcase/wahid-by-adam/de.md new file mode 100644 index 00000000000..75882b28587 --- /dev/null +++ b/markdown/org/showcase/wahid-by-adam/de.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "Adam looking spectacularly dapper in his Wahid" +date: "2020-07-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ab68d41354448f2149dcdce2cbf3b0222f58012d-2160x1080.jpg" +intro: "You'd be forgiven to think we cut this out of a high-fashion magazine, but it's a picture from Adam who made this gorgeous Wahid for himself." +title: "[auf Englisch] Wahid by Adam" +--- + + +You'd be forgiven to think we cut this out of a high-fashion magazine, but it's a picture from Adam who made this gorgeous Wahid for himself. + + + +This picture is from the [the Instagram feed](https://www.instagram.com/p/CCGnNvQBxJe/) of [Adam Bradley](https://www.instagram.com/grandmarquess/). +It is posted here with permission. + + + diff --git a/markdown/org/showcase/wahid-by-adam/en.md b/markdown/org/showcase/wahid-by-adam/en.md new file mode 100644 index 00000000000..01ec777cd8b --- /dev/null +++ b/markdown/org/showcase/wahid-by-adam/en.md @@ -0,0 +1,20 @@ +--- +maker: "unknown" +caption: "Adam looking spectacularly dapper in his Wahid" +date: "2020-07-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ab68d41354448f2149dcdce2cbf3b0222f58012d-2160x1080.jpg" +intro: "Wahid by Adam" +title: "Wahid by Adam" +--- + + +You'd be forgiven to think we cut this out of a high-fashion magazine, but it's a picture +from Adam who made this gorgeous Wahid for himself. + + + +This picture is from the [the Instagram feed](https://www.instagram.com/p/CCGnNvQBxJe/) of [Adam Bradley](https://www.instagram.com/grandmarquess/). +It is posted here with permission. + + + diff --git a/markdown/org/showcase/wahid-by-adam/es.md b/markdown/org/showcase/wahid-by-adam/es.md new file mode 100644 index 00000000000..633256e49cc --- /dev/null +++ b/markdown/org/showcase/wahid-by-adam/es.md @@ -0,0 +1,20 @@ +--- +maker: "unknown" +caption: "Adam looking spectacularly dapper in his Wahid" +date: "2020-07-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ab68d41354448f2149dcdce2cbf3b0222f58012d-2160x1080.jpg" +intro: "Wahid by Adam [No traducido]" +title: "Wahid by Adam [No traducido]" +--- + + +You'd be forgiven to think we cut this out of a high-fashion magazine, but it's a picture +from Adam who made this gorgeous Wahid for himself. + + + +This picture is from the [the Instagram feed](https://www.instagram.com/p/CCGnNvQBxJe/) of [Adam Bradley](https://www.instagram.com/grandmarquess/). +It is posted here with permission. + + + diff --git a/markdown/org/showcase/wahid-by-adam/fr.md b/markdown/org/showcase/wahid-by-adam/fr.md new file mode 100644 index 00000000000..49ef6c0101e --- /dev/null +++ b/markdown/org/showcase/wahid-by-adam/fr.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "Adam a l'air spectaculairement zappé dans son Wahid" +date: "2020-07-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ab68d41354448f2149dcdce2cbf3b0222f58012d-2160x1080.jpg" +intro: "On vous pardonnerait de penser que nous l'avons pris dans un magazine de haute mode, mais c'est une photo d'Adam qui a fait ce magnifique Wahid pour lui-même." +title: "Wahid par Adam" +--- + + +On vous pardonnerait de penser que nous l'avons pris dans un magazine de haute mode, mais c'est une photo d'Adam qui a fait ce magnifique Wahid pour lui-même. + + + +Cette image provient du [flux Instagram ](https://www.instagram.com/p/CCGnNvQBxJe/) de [Adam Bradley](https://www.instagram.com/grandmarquess/). +Elle est publiée ici avec son autorisation. + + + diff --git a/markdown/org/showcase/wahid-by-adam/nl.md b/markdown/org/showcase/wahid-by-adam/nl.md new file mode 100644 index 00000000000..ba4b1ba3d40 --- /dev/null +++ b/markdown/org/showcase/wahid-by-adam/nl.md @@ -0,0 +1,19 @@ +--- +maker: "unknown" +caption: "Adam ziet er spectaculair afgeborsteld uit in zijn Wahid" +date: "2020-07-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/ab68d41354448f2149dcdce2cbf3b0222f58012d-2160x1080.jpg" +intro: "Je zou denken dat we dit uit een modetijdschrift geknipt hebben, maar het is een foto van Adam die deze prachtige Wahid voor zichzelf maakte." +title: "Wahid door Adam" +--- + + +Je zou denken dat we dit uit een modetijdschrift geknipt hebben, maar het is een foto van Adam die deze prachtige Wahid voor zichzelf maakte. + + + +Deze foto komt van de [de Instagram feed](https://www.instagram.com/p/CCGnNvQBxJe/) van [Adam Bradley](https://www.instagram.com/grandmarquess/). +Ze is hier gepost met toestemming. + + + diff --git a/markdown/org/showcase/wahid-by-minty/de.md b/markdown/org/showcase/wahid-by-minty/de.md new file mode 100644 index 00000000000..65cd9c2a3d1 --- /dev/null +++ b/markdown/org/showcase/wahid-by-minty/de.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Wahid waistcoat by Minty" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0858bf75b632746e1316ac7850d4fb2d04228956-770x567.jpg" +intro: "This classy Wahid waistcoat was made by Minty!" +title: "[auf Englisch] Wahid by Minty" +--- + + +This classy Wahid waistcoat was made by Minty! + + + +This picture is from Minty on Discord. It is reposted here with permission. + + + diff --git a/markdown/org/showcase/wahid-by-minty/en.md b/markdown/org/showcase/wahid-by-minty/en.md new file mode 100644 index 00000000000..f48f87b9b3e --- /dev/null +++ b/markdown/org/showcase/wahid-by-minty/en.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Wahid waistcoat by Minty" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0858bf75b632746e1316ac7850d4fb2d04228956-770x567.jpg" +intro: "This classy Wahid waistcoat was made by Minty!" +title: "Wahid by Minty" +--- + + +This classy Wahid waistcoat was made by Minty! + + + +This picture is from Minty on Discord. It is reposted here with permission. + + + diff --git a/markdown/org/showcase/wahid-by-minty/es.md b/markdown/org/showcase/wahid-by-minty/es.md new file mode 100644 index 00000000000..6f5e60cb7fc --- /dev/null +++ b/markdown/org/showcase/wahid-by-minty/es.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Wahid waistcoat by Minty" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0858bf75b632746e1316ac7850d4fb2d04228956-770x567.jpg" +intro: "This classy Wahid waistcoat was made by Minty!" +title: "Wahid by Minty [No traducido]" +--- + + +This classy Wahid waistcoat was made by Minty! + + + +This picture is from Minty on Discord. It is reposted here with permission. + + + diff --git a/markdown/org/showcase/wahid-by-minty/fr.md b/markdown/org/showcase/wahid-by-minty/fr.md new file mode 100644 index 00000000000..96a8f50b3d2 --- /dev/null +++ b/markdown/org/showcase/wahid-by-minty/fr.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Gilet Wahid par Minty" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0858bf75b632746e1316ac7850d4fb2d04228956-770x567.jpg" +intro: "Ce joli gilet Wahid a été réalisé par Minty !" +title: "Wahid par Minty" +--- + + +Ce joli gilet Wahid a été réalisé par Minty ! + + + +Cette photo provient de Minty sur Discord. Elle est publiée ici avec son autorisation. + + + diff --git a/markdown/org/showcase/wahid-by-minty/nl.md b/markdown/org/showcase/wahid-by-minty/nl.md new file mode 100644 index 00000000000..a63b608fd24 --- /dev/null +++ b/markdown/org/showcase/wahid-by-minty/nl.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Wahid waistcoat by Minty" +date: "2021-03-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/0858bf75b632746e1316ac7850d4fb2d04228956-770x567.jpg" +intro: "This classy Wahid waistcoat was made by Minty!" +title: "Wahid by Minty [Niet vertaald]" +--- + + +This classy Wahid waistcoat was made by Minty! + + + +This picture is from Minty on Discord. It is reposted here with permission. + + + diff --git a/markdown/org/showcase/wahid-by-pho/de.md b/markdown/org/showcase/wahid-by-pho/de.md new file mode 100644 index 00000000000..e964602d715 --- /dev/null +++ b/markdown/org/showcase/wahid-by-pho/de.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "Wahid waistcoat by Pho" +date: "2021-05-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e172985d483a277509c6cbaf64fcd58ded7a95ea-521x800.jpg" +intro: "Pho made this stellar Wahid! They shared:" +title: "[auf Englisch] Wahid by Pho" +--- + +Pho made this stellar Wahid! They shared: + +> Wahid to my measurements. I opted out of buttons since I sit a lot at work and a completely fitted garment for me wouldn't be able to stay buttoned. I also did the pocket bags as one long piece of fabric which was easiest for me to understand under guidance of a sewing teacher. I might opt for snaps or just leave it open. My size stomach wise is bigger than my chest. Amazing how a garment my size makes me look great! Thanks for the pattern! + +One more picture of their fantastic work: + +![Side view](https://posts.freesewing.org/uploads/wahid_by_pho_wahidbypho2_ba0be6a31c.jpg "Side view") + + + +This picture is from Pho on Discord. It is reposted here with permission. + + diff --git a/markdown/org/showcase/wahid-by-pho/en.md b/markdown/org/showcase/wahid-by-pho/en.md new file mode 100644 index 00000000000..bc2b4fbe5e0 --- /dev/null +++ b/markdown/org/showcase/wahid-by-pho/en.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "Wahid waistcoat by Pho" +date: "2021-05-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e172985d483a277509c6cbaf64fcd58ded7a95ea-521x800.jpg" +intro: "Pho made this stellar Wahid! They shared:" +title: "Wahid by Pho" +--- + +Pho made this stellar Wahid! They shared: + +> Wahid to my measurements. I opted out of buttons since I sit a lot at work and a completely fitted garment for me wouldn't be able to stay buttoned. I also did the pocket bags as one long piece of fabric which was easiest for me to understand under guidance of a sewing teacher. I might opt for snaps or just leave it open. My size stomach wise is bigger than my chest. Amazing how a garment my size makes me look great! Thanks for the pattern! + +One more picture of their fantastic work: + +![Side view](https://posts.freesewing.org/uploads/wahid_by_pho_wahidbypho2_ba0be6a31c.jpg "Side view") + + + +This picture is from Pho on Discord. It is reposted here with permission. + + diff --git a/markdown/org/showcase/wahid-by-pho/es.md b/markdown/org/showcase/wahid-by-pho/es.md new file mode 100644 index 00000000000..608d4df15d5 --- /dev/null +++ b/markdown/org/showcase/wahid-by-pho/es.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "Wahid waistcoat by Pho" +date: "2021-05-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e172985d483a277509c6cbaf64fcd58ded7a95ea-521x800.jpg" +intro: "Pho made this stellar Wahid! They shared:" +title: "Wahid by Pho [No traducido]" +--- + +Pho made this stellar Wahid! They shared: + +> Wahid to my measurements. I opted out of buttons since I sit a lot at work and a completely fitted garment for me wouldn't be able to stay buttoned. I also did the pocket bags as one long piece of fabric which was easiest for me to understand under guidance of a sewing teacher. I might opt for snaps or just leave it open. My size stomach wise is bigger than my chest. Amazing how a garment my size makes me look great! Thanks for the pattern! + +One more picture of their fantastic work: + +![Side view](https://posts.freesewing.org/uploads/wahid_by_pho_wahidbypho2_ba0be6a31c.jpg "Side view") + + + +This picture is from Pho on Discord. It is reposted here with permission. + + diff --git a/markdown/org/showcase/wahid-by-pho/fr.md b/markdown/org/showcase/wahid-by-pho/fr.md new file mode 100644 index 00000000000..f0bab24e913 --- /dev/null +++ b/markdown/org/showcase/wahid-by-pho/fr.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "Wahid waistcoat by Pho" +date: "2021-05-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e172985d483a277509c6cbaf64fcd58ded7a95ea-521x800.jpg" +intro: "Pho made this stellar Wahid! They shared:" +title: "[En anglais] Wahid by Pho" +--- + +Pho made this stellar Wahid! They shared: + +> Wahid to my measurements. I opted out of buttons since I sit a lot at work and a completely fitted garment for me wouldn't be able to stay buttoned. I also did the pocket bags as one long piece of fabric which was easiest for me to understand under guidance of a sewing teacher. I might opt for snaps or just leave it open. My size stomach wise is bigger than my chest. Amazing how a garment my size makes me look great! Thanks for the pattern! + +One more picture of their fantastic work: + +![Side view](https://posts.freesewing.org/uploads/wahid_by_pho_wahidbypho2_ba0be6a31c.jpg "Side view") + + + +This picture is from Pho on Discord. Elle est publiée ici avec son autorisation. + + diff --git a/markdown/org/showcase/wahid-by-pho/nl.md b/markdown/org/showcase/wahid-by-pho/nl.md new file mode 100644 index 00000000000..d029762f690 --- /dev/null +++ b/markdown/org/showcase/wahid-by-pho/nl.md @@ -0,0 +1,22 @@ +--- +maker: "unknown" +caption: "Wahid waistcoat by Pho" +date: "2021-05-10" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/e172985d483a277509c6cbaf64fcd58ded7a95ea-521x800.jpg" +intro: "Pho made this stellar Wahid! They shared:" +title: "Wahid by Pho [Niet vertaald]" +--- + +Pho made this stellar Wahid! They shared: + +> Wahid to my measurements. I opted out of buttons since I sit a lot at work and a completely fitted garment for me wouldn't be able to stay buttoned. I also did the pocket bags as one long piece of fabric which was easiest for me to understand under guidance of a sewing teacher. I might opt for snaps or just leave it open. My size stomach wise is bigger than my chest. Amazing how a garment my size makes me look great! Thanks for the pattern! + +One more picture of their fantastic work: + +![Side view](https://posts.freesewing.org/uploads/wahid_by_pho_wahidbypho2_ba0be6a31c.jpg "Side view") + + + +This picture is from Pho on Discord. It is reposted here with permission. + + diff --git a/markdown/org/showcase/wahid-jeroen/de.md b/markdown/org/showcase/wahid-jeroen/de.md new file mode 100644 index 00000000000..9afd3bc054c --- /dev/null +++ b/markdown/org/showcase/wahid-jeroen/de.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Red plaid perfection" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/03e55c42fb0bb6109af5ab0dbf58ad9e6f5a8110-1080x1080.jpg" +intro: "Jeroen made this stunning Wahid waistcoat in a beautiful red plaid." +title: "[auf Englisch] Red Plaid Wahid Waistcoat by Jeroen" +--- + + +Jeroen made this stunning Wahid waistcoat in a beautiful red plaid. + +Check out the matching Theo shorts Jeroen made [here](https://freesewing.org/showcase/theo-jeroen/)! + + +This picture is from the instagram feed of [Jeroen Keerl](https://www.instagram.com/jeroenkeerl/). It is posted here with permission. + + diff --git a/markdown/org/showcase/wahid-jeroen/en.md b/markdown/org/showcase/wahid-jeroen/en.md new file mode 100644 index 00000000000..03d64ad50b8 --- /dev/null +++ b/markdown/org/showcase/wahid-jeroen/en.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Red plaid perfection" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/03e55c42fb0bb6109af5ab0dbf58ad9e6f5a8110-1080x1080.jpg" +intro: "Jeroen made this stunning Wahid waistcoat in a beautiful red plaid." +title: "Red Plaid Wahid Waistcoat by Jeroen" +--- + +Jeroen made this stunning Wahid waistcoat in a beautiful red plaid. + +Check out the matching Theo shorts Jeroen made [here](https://freesewing.org/showcase/theo-jeroen/)! + + +This picture is from the instagram feed of [Jeroen Keerl](https://www.instagram.com/jeroenkeerl/). It is posted here with permission. + + diff --git a/markdown/org/showcase/wahid-jeroen/es.md b/markdown/org/showcase/wahid-jeroen/es.md new file mode 100644 index 00000000000..2b0c20d59b0 --- /dev/null +++ b/markdown/org/showcase/wahid-jeroen/es.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Red plaid perfection" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/03e55c42fb0bb6109af5ab0dbf58ad9e6f5a8110-1080x1080.jpg" +intro: "Jeroen made this stunning Wahid waistcoat in a beautiful red plaid." +title: "Red Plaid Wahid Waistcoat by Jeroen [No traducido]" +--- + +Jeroen made this stunning Wahid waistcoat in a beautiful red plaid. + +Check out the matching Theo shorts Jeroen made [here](https://freesewing.org/showcase/theo-jeroen/)! + + +This picture is from the instagram feed of [Jeroen Keerl](https://www.instagram.com/jeroenkeerl/). It is posted here with permission. + + diff --git a/markdown/org/showcase/wahid-jeroen/fr.md b/markdown/org/showcase/wahid-jeroen/fr.md new file mode 100644 index 00000000000..d3ab49940c8 --- /dev/null +++ b/markdown/org/showcase/wahid-jeroen/fr.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "La perfection du tartan rouge" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/03e55c42fb0bb6109af5ab0dbf58ad9e6f5a8110-1080x1080.jpg" +intro: "Jeroen a fait ce magnifique gilet Wahid dans un beau tartan rouge." +title: "Gilet Wahid en tartan rouge par Jeroen" +--- + + +Jeroen a fait ce magnifique gilet Wahid dans un beau tartan rouge. + +Jetez un coup d’œil au short Theo assorti que Jeroen a fait [ici](https://freesewing.org/showcase/theo-jeroen/)! + + +Cette image provient du flux instagram de [Jeroen Keerl](https://www.instagram.com/jeroenkeerl/). Elle est publiée ici avec son autorisation. + + diff --git a/markdown/org/showcase/wahid-jeroen/nl.md b/markdown/org/showcase/wahid-jeroen/nl.md new file mode 100644 index 00000000000..7a25d4ef320 --- /dev/null +++ b/markdown/org/showcase/wahid-jeroen/nl.md @@ -0,0 +1,17 @@ +--- +maker: "unknown" +caption: "Red plaid perfection" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/03e55c42fb0bb6109af5ab0dbf58ad9e6f5a8110-1080x1080.jpg" +intro: "Jeroen made this stunning Wahid waistcoat in a beautiful red plaid." +title: "Red Plaid Wahid Waistcoat by Jeroen [Niet vertaald]" +--- + +Jeroen made this stunning Wahid waistcoat in a beautiful red plaid. + +Check out the matching Theo shorts Jeroen made [here](https://freesewing.org/showcase/theo-jeroen/)! + + +This picture is from the instagram feed of [Jeroen Keerl](https://www.instagram.com/jeroenkeerl/). It is posted here with permission. + + diff --git a/markdown/org/showcase/wahid-kaena/de.md b/markdown/org/showcase/wahid-kaena/de.md new file mode 100644 index 00000000000..90b094ed7b7 --- /dev/null +++ b/markdown/org/showcase/wahid-kaena/de.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Purple, floral, utterly delightful Wahid waistcoat" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4aa2526bd8de543f32ed5f9470e1728d876aa568-750x750.jpg" +intro: "Kaena made her husband a Wahid waistcoat to go to a wedding, and we just love it!" +title: "[auf Englisch] Purple Wahid by Kaena" +--- + +Kaena made her husband a Wahid waistcoat to go to a wedding, and we just love it! + +![Kaena's husband rocking their Wahid waistcoat](https://posts.freesewing.org/uploads/wahid_kaena_wahid_kaena_2_ad16bc1ad6.jpg "Kaena's husband rocking their Wahid waistcoat") + + + +These pictures are from the instagram feed of [Kaena](https://www.instagram.com/kaena.mackinnon/). They are posted here with permission. + + diff --git a/markdown/org/showcase/wahid-kaena/en.md b/markdown/org/showcase/wahid-kaena/en.md new file mode 100644 index 00000000000..7dda7f725b3 --- /dev/null +++ b/markdown/org/showcase/wahid-kaena/en.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Purple, floral, utterly delightful Wahid waistcoat" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4aa2526bd8de543f32ed5f9470e1728d876aa568-750x750.jpg" +intro: "Kaena made her husband a Wahid waistcoat to go to a wedding, and we just love it!" +title: "Purple Wahid by Kaena" +--- + +Kaena made her husband a Wahid waistcoat to go to a wedding, and we just love it! + +![Kaena's husband rocking their Wahid waistcoat](https://posts.freesewing.org/uploads/wahid_kaena_wahid_kaena_2_ad16bc1ad6.jpg "Kaena's husband rocking their Wahid waistcoat") + + + +These pictures are from the instagram feed of [Kaena](https://www.instagram.com/kaena.mackinnon/). They are posted here with permission. + + diff --git a/markdown/org/showcase/wahid-kaena/es.md b/markdown/org/showcase/wahid-kaena/es.md new file mode 100644 index 00000000000..b4bf1def1cf --- /dev/null +++ b/markdown/org/showcase/wahid-kaena/es.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Purple, floral, utterly delightful Wahid waistcoat" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4aa2526bd8de543f32ed5f9470e1728d876aa568-750x750.jpg" +intro: "Kaena made her husband a Wahid waistcoat to go to a wedding, and we just love it!" +title: "Purple Wahid by Kaena [No traducido]" +--- + +Kaena made her husband a Wahid waistcoat to go to a wedding, and we just love it! + +![Kaena's husband rocking their Wahid waistcoat](https://posts.freesewing.org/uploads/wahid_kaena_wahid_kaena_2_ad16bc1ad6.jpg "Kaena's husband rocking their Wahid waistcoat") + + + +These pictures are from the instagram feed of [Kaena](https://www.instagram.com/kaena.mackinnon/). They are posted here with permission. + + diff --git a/markdown/org/showcase/wahid-kaena/fr.md b/markdown/org/showcase/wahid-kaena/fr.md new file mode 100644 index 00000000000..bae5b4ba502 --- /dev/null +++ b/markdown/org/showcase/wahid-kaena/fr.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Violet, floral, tout à fait délicieux Gilet Wahid" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4aa2526bd8de543f32ed5f9470e1728d876aa568-750x750.jpg" +intro: "Kaena a fait de son mari un gilet Wahid pour aller à un mariage, et on l'adore !" +title: "Wahid Violet par Kaena" +--- + +Kaena a fait de son mari un gilet Wahid pour aller à un mariage, et on l'adore ! + +![Le mari de Kaena qui en jette avec son gilet Wahid](https://posts.freesewing.org/uploads/wahid_kaena_wahid_kaena_2_ad16bc1ad6.jpg "Le mari de Kaena qui en jette avec son gilet Wahid") + + + +Ces images proviennent du flux Instagram de [Kaena](https://www.instagram.com/kaena.mackinnon/). Elles sont postées ici avec autorisation. + + diff --git a/markdown/org/showcase/wahid-kaena/nl.md b/markdown/org/showcase/wahid-kaena/nl.md new file mode 100644 index 00000000000..e5be5f127ce --- /dev/null +++ b/markdown/org/showcase/wahid-kaena/nl.md @@ -0,0 +1,18 @@ +--- +maker: "unknown" +caption: "Purple, floral, utterly delightful Wahid waistcoat" +date: "2020-11-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/4aa2526bd8de543f32ed5f9470e1728d876aa568-750x750.jpg" +intro: "Kaena made her husband a Wahid waistcoat to go to a wedding, and we just love it!" +title: "Purple Wahid by Kaena [Niet vertaald]" +--- + +Kaena made her husband a Wahid waistcoat to go to a wedding, and we just love it! + +![Kaena's husband rocking their Wahid waistcoat](https://posts.freesewing.org/uploads/wahid_kaena_wahid_kaena_2_ad16bc1ad6.jpg "Kaena's husband rocking their Wahid waistcoat") + + + +These pictures are from the instagram feed of [Kaena](https://www.instagram.com/kaena.mackinnon/). They are posted here with permission. + + diff --git a/markdown/org/showcase/waralee-by-wouter/de.md b/markdown/org/showcase/waralee-by-wouter/de.md new file mode 100644 index 00000000000..f11e4bebf2d --- /dev/null +++ b/markdown/org/showcase/waralee-by-wouter/de.md @@ -0,0 +1,14 @@ +--- +maker: "Wouter.vdub" +caption: "Wouter in his Waralee wrap pants" +date: "2019-08-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fa3240c988c8399cbde1cd248901e0596f749a1d-500x792.jpg" +intro: "This is the first version Wouter made after completing the Waralee pattern." +title: "[auf Englisch] Waralee by Wouter" +--- + +This is the first version Wouter made after completing the Waralee pattern. + +Nice for staying cool when it's warm: + +![Yard work](https://posts.freesewing.org/uploads/waralee_by_wouter_waralee2_5391f3d653.jpg "Yard work") diff --git a/markdown/org/showcase/waralee-by-wouter/en.md b/markdown/org/showcase/waralee-by-wouter/en.md new file mode 100644 index 00000000000..91a4e5a33fd --- /dev/null +++ b/markdown/org/showcase/waralee-by-wouter/en.md @@ -0,0 +1,14 @@ +--- +maker: "Wouter.vdub" +caption: "Wouter in his Waralee wrap pants" +date: "2019-08-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fa3240c988c8399cbde1cd248901e0596f749a1d-500x792.jpg" +intro: "This is the first version Wouter made after completing the Waralee pattern." +title: "Waralee by Wouter" +--- + +This is the first version Wouter made after completing the Waralee pattern. + +Nice for staying cool when it's warm: + +![Yard work](https://posts.freesewing.org/uploads/waralee_by_wouter_waralee2_5391f3d653.jpg "Yard work") diff --git a/markdown/org/showcase/waralee-by-wouter/es.md b/markdown/org/showcase/waralee-by-wouter/es.md new file mode 100644 index 00000000000..f0d1b27dd5f --- /dev/null +++ b/markdown/org/showcase/waralee-by-wouter/es.md @@ -0,0 +1,14 @@ +--- +maker: "Wouter.vdub" +caption: "Wouter in his Waralee wrap pants" +date: "2019-08-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fa3240c988c8399cbde1cd248901e0596f749a1d-500x792.jpg" +intro: "This is the first version Wouter made after completing the Waralee pattern." +title: "Waralee by Wouter [No traducido]" +--- + +This is the first version Wouter made after completing the Waralee pattern. + +Nice for staying cool when it's warm: + +![Yard work](https://posts.freesewing.org/uploads/waralee_by_wouter_waralee2_5391f3d653.jpg "Yard work") diff --git a/markdown/org/showcase/waralee-by-wouter/fr.md b/markdown/org/showcase/waralee-by-wouter/fr.md new file mode 100644 index 00000000000..eeecae40d7a --- /dev/null +++ b/markdown/org/showcase/waralee-by-wouter/fr.md @@ -0,0 +1,14 @@ +--- +maker: "Wouter.vdub" +caption: "Wouter dans son pantalon Waralee" +date: "2019-08-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fa3240c988c8399cbde1cd248901e0596f749a1d-500x792.jpg" +intro: "Il s'agit de la première version de Wouter faite après avoir complété le patron Waralee." +title: "Waralee par Wouter" +--- + +Il s'agit de la première version de Wouter faite après avoir complété le patron Waralee. + +Idéal pour rester frais quand il est chaud : + +![Jardinage](https://posts.freesewing.org/uploads/waralee_by_wouter_waralee2_5391f3d653.jpg "Jardinage") diff --git a/markdown/org/showcase/waralee-by-wouter/nl.md b/markdown/org/showcase/waralee-by-wouter/nl.md new file mode 100644 index 00000000000..fe6dfa99e65 --- /dev/null +++ b/markdown/org/showcase/waralee-by-wouter/nl.md @@ -0,0 +1,14 @@ +--- +maker: "Wouter.vdub" +caption: "Wouter in his Waralee wrap pants" +date: "2019-08-27" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/fa3240c988c8399cbde1cd248901e0596f749a1d-500x792.jpg" +intro: "This is the first version Wouter made after completing the Waralee pattern." +title: "Waralee by Wouter [Niet vertaald]" +--- + +This is the first version Wouter made after completing the Waralee pattern. + +Nice for staying cool when it's warm: + +![Yard work](https://posts.freesewing.org/uploads/waralee_by_wouter_waralee2_5391f3d653.jpg "Yard work") diff --git a/markdown/org/showcase/wonder-warrior-jacket/de.md b/markdown/org/showcase/wonder-warrior-jacket/de.md new file mode 100644 index 00000000000..c8d8b2115dd --- /dev/null +++ b/markdown/org/showcase/wonder-warrior-jacket/de.md @@ -0,0 +1,12 @@ +--- +maker: "RedBlaqueGolden" +caption: "This is the Wonder Warrior jacket, looking pretty great" +date: "2017-10-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/682710e51155b4fa6ee19d98322aa6d9c7f9fc40-2320x1656.jpg" +intro: "This image was republished (with permission) from the Twitter account of @MyxterHyde" +title: "[auf Englisch] A wonder woman themed jacket based on the Brian Body Block by Myxter Hyde" +--- + + +This image was republished (with permission) from [the Twitter account](https://twitter.com/MyxterHyde/status/914274197345570816) of [@MyxterHyde](https://twitter.com/MyxterHyde) + diff --git a/markdown/org/showcase/wonder-warrior-jacket/en.md b/markdown/org/showcase/wonder-warrior-jacket/en.md new file mode 100644 index 00000000000..ae8b3534152 --- /dev/null +++ b/markdown/org/showcase/wonder-warrior-jacket/en.md @@ -0,0 +1,14 @@ +--- +maker: "RedBlaqueGolden" +caption: "This is the Wonder Warrior jacket, looking pretty great" +date: "2017-10-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/682710e51155b4fa6ee19d98322aa6d9c7f9fc40-2320x1656.jpg" +intro: "This image was republished (with permission) from the Twitter account of @MyxterHyde" +title: "A wonder woman themed jacket based on the Brian Body Block by Myxter Hyde" +--- + + +This image was republished (with permission) from +[the Twitter account](https://twitter.com/MyxterHyde/status/914274197345570816) of +[@MyxterHyde](https://twitter.com/MyxterHyde) + diff --git a/markdown/org/showcase/wonder-warrior-jacket/es.md b/markdown/org/showcase/wonder-warrior-jacket/es.md new file mode 100644 index 00000000000..8402cec31ec --- /dev/null +++ b/markdown/org/showcase/wonder-warrior-jacket/es.md @@ -0,0 +1,14 @@ +--- +maker: "RedBlaqueGolden" +caption: "This is the Wonder Warrior jacket, looking pretty great" +date: "2017-10-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/682710e51155b4fa6ee19d98322aa6d9c7f9fc40-2320x1656.jpg" +intro: "This image was republished (with permission) from the Twitter account of @MyxterHyde" +title: "A wonder woman themed jacket based on the Brian Body Block by Myxter Hyde [No traducido]" +--- + + +This image was republished (with permission) from +[the Twitter account](https://twitter.com/MyxterHyde/status/914274197345570816) of +[@MyxterHyde](https://twitter.com/MyxterHyde) + diff --git a/markdown/org/showcase/wonder-warrior-jacket/fr.md b/markdown/org/showcase/wonder-warrior-jacket/fr.md new file mode 100644 index 00000000000..0e2efcb0a1d --- /dev/null +++ b/markdown/org/showcase/wonder-warrior-jacket/fr.md @@ -0,0 +1,12 @@ +--- +maker: "RedBlaqueGolden" +caption: "Voici la veste de super guerrier(e), avec un super rendu" +date: "2017-10-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/682710e51155b4fa6ee19d98322aa6d9c7f9fc40-2320x1656.jpg" +intro: "Cette image a été republiée (avec autorisation) à partir du compte Twitter de @MyxterHyde" +title: "Une veste sur le thème de Wonder Woman basée sur le patron de base Brian réalisé par Myxter Hyde" +--- + + +Cette image a été republiée (avec autorisation) à partir du [compte Twitter](https://twitter.com/MyxterHyde/status/914274197345570816) de [@MyxterHyde](https://twitter.com/MyxterHyde) + diff --git a/markdown/org/showcase/wonder-warrior-jacket/nl.md b/markdown/org/showcase/wonder-warrior-jacket/nl.md new file mode 100644 index 00000000000..67bd1a2e544 --- /dev/null +++ b/markdown/org/showcase/wonder-warrior-jacket/nl.md @@ -0,0 +1,12 @@ +--- +maker: "RedBlaqueGolden" +caption: "Dit is het Wonder Warrior jasje, en het ziet er vrij fantastisch uit" +date: "2017-10-01" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/682710e51155b4fa6ee19d98322aa6d9c7f9fc40-2320x1656.jpg" +intro: "Deze afbeelding is hier (met toestemming) gepubliceerd en verscheen eerst op de Twitter account van @MyxterHyde" +title: "Een wonder woman jasje gebaseerd op de Brian basisvorm, door Myxter Hyde" +--- + + +Deze afbeelding is hier (met toestemming) gepubliceerd en verscheen eerst op de [Twitter account](https://twitter.com/MyxterHyde/status/914274197345570816) van [@MyxterHyde](https://twitter.com/MyxterHyde) + diff --git a/markdown/org/showcase/wonder-woman-simon/de.md b/markdown/org/showcase/wonder-woman-simon/de.md new file mode 100644 index 00000000000..1c323bb4c96 --- /dev/null +++ b/markdown/org/showcase/wonder-woman-simon/de.md @@ -0,0 +1,21 @@ +--- +maker: "RedBlaqueGolden" +caption: "There's some really quality posing in this set." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5084bf9ead668c3ddd3a8ff4fd9a9ea4866d3d1a-1080x1080.jpg" +intro: "[auf Englisch] A Wonder Women simon by JV" +title: "[auf Englisch] A Wonder Women simon by JV" +--- + +![Eine andere Ansicht](https://posts.freesewing.org/uploads/wonder_woman_simon_view2_a8f4c2e951.jpg "Eine andere Ansicht") + + + +###### See the originals on the Instragram feed of funloveadventure + +These images are from +[the Instagram feed](https://www.instagram.com/myxterhyde/) +of [@MyxterHyde](/users/MyxterHyde). +They are published here with permission. + + diff --git a/markdown/org/showcase/wonder-woman-simon/en.md b/markdown/org/showcase/wonder-woman-simon/en.md new file mode 100644 index 00000000000..7ed64b5f3c8 --- /dev/null +++ b/markdown/org/showcase/wonder-woman-simon/en.md @@ -0,0 +1,24 @@ +--- +maker: "RedBlaqueGolden" +caption: "There's some really quality posing in this set." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5084bf9ead668c3ddd3a8ff4fd9a9ea4866d3d1a-1080x1080.jpg" +intro: " " +title: "A Wonder Women simon by JV" +--- + +![Another view](https://posts.freesewing.org/uploads/wonder_woman_simon_view2_a8f4c2e951.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/wonder_woman_simon_view3_c4357bf70f.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/wonder_woman_simon_view4_b6b74a2fe6.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/wonder_woman_simon_view5_6e42e949af.jpg "Another view") + + + +###### See the originals on the Instragram feed of funloveadventure + +These images are from +[the Instagram feed](https://www.instagram.com/myxterhyde/) +of [@MyxterHyde](/users/MyxterHyde). +They are published here with permission. + + diff --git a/markdown/org/showcase/wonder-woman-simon/es.md b/markdown/org/showcase/wonder-woman-simon/es.md new file mode 100644 index 00000000000..2d84b07c2ad --- /dev/null +++ b/markdown/org/showcase/wonder-woman-simon/es.md @@ -0,0 +1,24 @@ +--- +maker: "RedBlaqueGolden" +caption: "There's some really quality posing in this set." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5084bf9ead668c3ddd3a8ff4fd9a9ea4866d3d1a-1080x1080.jpg" +intro: " " +title: "A Wonder Women simon by JV [No traducido]" +--- + +![Another view](https://posts.freesewing.org/uploads/wonder_woman_simon_view2_a8f4c2e951.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/wonder_woman_simon_view3_c4357bf70f.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/wonder_woman_simon_view4_b6b74a2fe6.jpg "Another view") +![Another view](https://posts.freesewing.org/uploads/wonder_woman_simon_view5_6e42e949af.jpg "Another view") + + + +###### See the originals on the Instragram feed of funloveadventure + +These images are from +[the Instagram feed](https://www.instagram.com/myxterhyde/) +of [@MyxterHyde](/users/MyxterHyde). +They are published here with permission. + + diff --git a/markdown/org/showcase/wonder-woman-simon/fr.md b/markdown/org/showcase/wonder-woman-simon/fr.md new file mode 100644 index 00000000000..f2470c6217b --- /dev/null +++ b/markdown/org/showcase/wonder-woman-simon/fr.md @@ -0,0 +1,21 @@ +--- +maker: "RedBlaqueGolden" +caption: "Il y a une vraie qualité en posant dans cet ensemble." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5084bf9ead668c3ddd3a8ff4fd9a9ea4866d3d1a-1080x1080.jpg" +intro: "Une chemise Simon Wonder Woman par JV" +title: "Une chemise Simon Wonder Woman par JV" +--- + +![Une autre vue](https://posts.freesewing.org/uploads/wonder_woman_simon_view2_a8f4c2e951.jpg "Une autre vue") + + + +###### Voir les originaux sur le feed Instragram de funloveadventure + +Ces images proviennent du +[feed Instagram](https://www.instagram.com/myxterhyde/) +de [@MyxterHyde](/users/MyxterHyde). +Elles sont repostées ici avec autorisation. + + diff --git a/markdown/org/showcase/wonder-woman-simon/nl.md b/markdown/org/showcase/wonder-woman-simon/nl.md new file mode 100644 index 00000000000..30458ef36ca --- /dev/null +++ b/markdown/org/showcase/wonder-woman-simon/nl.md @@ -0,0 +1,21 @@ +--- +maker: "RedBlaqueGolden" +caption: "Hier wordt geweldig goed geposeerd." +date: "2018-02-05" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/5084bf9ead668c3ddd3a8ff4fd9a9ea4866d3d1a-1080x1080.jpg" +intro: "Een Wonder Woman Simon door JV" +title: "Een Wonder Woman Simon door JV" +--- + +![Een andere kant](https://posts.freesewing.org/uploads/wonder_woman_simon_view2_a8f4c2e951.jpg "Een andere kant") + + + +###### See the originals on the Instragram feed of funloveadventure + +These images are from +[the Instagram feed](https://www.instagram.com/myxterhyde/) +of [@MyxterHyde](/users/MyxterHyde). +They are published here with permission. + + diff --git a/markdown/org/showcase/yellow-button-simon/de.md b/markdown/org/showcase/yellow-button-simon/de.md new file mode 100644 index 00000000000..33c55b8f948 --- /dev/null +++ b/markdown/org/showcase/yellow-button-simon/de.md @@ -0,0 +1,12 @@ +--- +maker: "RedBlaqueGolden" +caption: "That's one dapper gentleman" +date: "2016-12-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/50752fcd5fe40123200407c57a60a483a4c83efc-1080x1080.jpg" +intro: "This picture is from the Instagram feed of JV Hampton-VanSant ." +title: "[auf Englisch] Just look how happy JV is with his Simon shirt" +--- + + +This picture is from [the Instagram feed](https://www.instagram.com/p/BNsGBSVho4u/) of [JV Hampton-VanSant](http://jvhvs.com/). + diff --git a/markdown/org/showcase/yellow-button-simon/en.md b/markdown/org/showcase/yellow-button-simon/en.md new file mode 100644 index 00000000000..395bc167cec --- /dev/null +++ b/markdown/org/showcase/yellow-button-simon/en.md @@ -0,0 +1,12 @@ +--- +maker: "RedBlaqueGolden" +caption: "That's one dapper gentleman" +date: "2016-12-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/50752fcd5fe40123200407c57a60a483a4c83efc-1080x1080.jpg" +intro: "This picture is from the Instagram feed of JV Hampton-VanSant ." +title: "Just look how happy JV is with his Simon shirt" +--- + + +This picture is from [the Instagram feed](https://www.instagram.com/p/BNsGBSVho4u/) of [JV Hampton-VanSant](http://jvhvs.com/). + diff --git a/markdown/org/showcase/yellow-button-simon/es.md b/markdown/org/showcase/yellow-button-simon/es.md new file mode 100644 index 00000000000..9ef68faee6a --- /dev/null +++ b/markdown/org/showcase/yellow-button-simon/es.md @@ -0,0 +1,12 @@ +--- +maker: "RedBlaqueGolden" +caption: "That's one dapper gentleman" +date: "2016-12-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/50752fcd5fe40123200407c57a60a483a4c83efc-1080x1080.jpg" +intro: "This picture is from the Instagram feed of JV Hampton-VanSant ." +title: "Just look how happy JV is with his Simon shirt [No traducido]" +--- + + +This picture is from [the Instagram feed](https://www.instagram.com/p/BNsGBSVho4u/) of [JV Hampton-VanSant](http://jvhvs.com/). + diff --git a/markdown/org/showcase/yellow-button-simon/fr.md b/markdown/org/showcase/yellow-button-simon/fr.md new file mode 100644 index 00000000000..62cb1fbb09a --- /dev/null +++ b/markdown/org/showcase/yellow-button-simon/fr.md @@ -0,0 +1,12 @@ +--- +maker: "RedBlaqueGolden" +caption: "Voilà un élégant monsieur" +date: "2016-12-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/50752fcd5fe40123200407c57a60a483a4c83efc-1080x1080.jpg" +intro: "Cette image provient du feed Instagram de JV Hampton-VanSant ." +title: "Regardez à quel point JV est heureux avec sa chemise Simon" +--- + + +Cette image provient du [feed Instagram](https://www.instagram.com/p/BNsGBSVho4u/) de [JV Hampton-VanSant](http://jvhvs.com/). + diff --git a/markdown/org/showcase/yellow-button-simon/nl.md b/markdown/org/showcase/yellow-button-simon/nl.md new file mode 100644 index 00000000000..9cb953f4200 --- /dev/null +++ b/markdown/org/showcase/yellow-button-simon/nl.md @@ -0,0 +1,12 @@ +--- +maker: "RedBlaqueGolden" +caption: "Dat is nogal een gentleman" +date: "2016-12-06" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/50752fcd5fe40123200407c57a60a483a4c83efc-1080x1080.jpg" +intro: "Deze foto komt van de Instagram feed van JV Hampton-VanSant ." +title: "Kijk gewoon hoe blij JV is met zijn Simon hemd" +--- + + +Deze foto komt van [de Instagram feed](https://www.instagram.com/p/BNsGBSVho4u/) van [JV Hampton-VanSant](http://jvhvs.com/). + diff --git a/markdown/org/showcase/yoga-set-by-paul/de.md b/markdown/org/showcase/yoga-set-by-paul/de.md new file mode 100644 index 00000000000..0b18432b1bf --- /dev/null +++ b/markdown/org/showcase/yoga-set-by-paul/de.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Aaron and Bruce yoga set with stripes by Paul (up-side-down)" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/395281947410787d883184b63ebd54f5dc2e7256-2000x2991.jpg" +intro: "FIXME_no_intro" +title: "[auf Englisch] Yoga Outfit by Paul" +--- + + + diff --git a/markdown/org/showcase/yoga-set-by-paul/en.md b/markdown/org/showcase/yoga-set-by-paul/en.md new file mode 100644 index 00000000000..938fe26069b --- /dev/null +++ b/markdown/org/showcase/yoga-set-by-paul/en.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "Aaron and Bruce yoga set with stripes by Paul (up-side-down)" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/395281947410787d883184b63ebd54f5dc2e7256-2000x2991.jpg" +intro: "FIXME_no_intro" +title: "Yoga Outfit by Paul" +--- + + diff --git a/markdown/org/showcase/yoga-set-by-paul/es.md b/markdown/org/showcase/yoga-set-by-paul/es.md new file mode 100644 index 00000000000..d5e2a6c6db7 --- /dev/null +++ b/markdown/org/showcase/yoga-set-by-paul/es.md @@ -0,0 +1,10 @@ +--- +maker: "unknown" +caption: "Aaron and Bruce yoga set with stripes by Paul (up-side-down)" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/395281947410787d883184b63ebd54f5dc2e7256-2000x2991.jpg" +intro: "FIXME_no_intro" +title: "Yoga Outfit by Paul [No traducido]" +--- + + diff --git a/markdown/org/showcase/yoga-set-by-paul/fr.md b/markdown/org/showcase/yoga-set-by-paul/fr.md new file mode 100644 index 00000000000..b4da61e831d --- /dev/null +++ b/markdown/org/showcase/yoga-set-by-paul/fr.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Ensemble de yoga Aaron et Bruce avec bandes par Paul (tête en bas)" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/395281947410787d883184b63ebd54f5dc2e7256-2000x2991.jpg" +intro: "FIXME_no_intro" +title: "Tenue de yoga par Paul" +--- + + + diff --git a/markdown/org/showcase/yoga-set-by-paul/nl.md b/markdown/org/showcase/yoga-set-by-paul/nl.md new file mode 100644 index 00000000000..9b336b717b6 --- /dev/null +++ b/markdown/org/showcase/yoga-set-by-paul/nl.md @@ -0,0 +1,11 @@ +--- +maker: "unknown" +caption: "Aaron en Bruce yoga set met strepen door Paul (ondersteboven)" +date: "2018-09-29" +image: "https://cdn.sanity.io/images/hl5bw8cj/site-content/395281947410787d883184b63ebd54f5dc2e7256-2000x2991.jpg" +intro: "FIXME_no_intro" +title: "Yoga Outfit door Paul" +--- + + +