1
0
Fork 0

feat: Flat import of markdown repo

This is a flat (without history) import of (some of) the content
from our markdown module.

We've imported this without history because the repo contains our
blog posts and showcases posts content prior to porting them to strapi.

Since this contains many images, it would balloon the size of this repo
to import the full history.

Instead, please refer to the history of the (archived) markdown repo
at: https://github.com/freesewing/markdown
This commit is contained in:
Joost De Cock 2021-08-25 16:09:31 +02:00
parent 1671a896b5
commit b34a2ee2ed
6132 changed files with 244167 additions and 0 deletions

View file

@ -0,0 +1,15 @@
---
title: Crowdin
---
We use [crowdin](https://crowdin.com/) to manage all translations for FreeSewing.
It's an online platform that makes translation a breeze.
There's a good deal of documentation on Crowdin online, so we won't try to replicate that here.
To get started, you will need to be invited as a translator. No need to worry,
simply [let us know you'd like to help out](https://discord.freesewing.org/) and we'll add you.
We have two projects on Crowdin that each handle a specific type of content:
<ReadMore list />

View file

@ -0,0 +1,43 @@
---
title: Translating strings
---
Crowdin makes translations of strings very easy. If you provide the translation, Crowdin will make sure your changes make it back into our repository, where they will be picked up and merged by one of the development people.
Here's what you need to know to get started:
- Crowdin link: https://crowdin.com/project/freesewing
- Request an invite: https://gitter.im/freesewing/translation
## Syntax
Most strings are just text, but sometimes you'll find a little markup sprinkled in.
### HTML formatting
When you encounter HTML tags, simply translate around them. For example:
```markup
<b>No</b>, never.
```
looks like this in Spanish:
```markup
<b>No</b>, nunca.
```
### Placeholders
When you encounter a `{key}` between curly braces, leave it as-is. These will be filled in later with the correct value. For example:
```markup
{field} saved
```
looks like this in Spanish
```yaml
{field} guardado
```

View file

@ -0,0 +1,15 @@
---
title: freesewing
---
This Crowdin project holds all the *strings* that are used to make the FreeSewing software multilingual.
Crowdin makes translations of such strings very easy.
If you provide the translation, Crowdin will make sure your changes make it back
into our repository, where they will be picked up and merged by one of the development people.
Here's what you need to know to get started:
- Crowdin link: https://crowdin.com/project/freesewing
- Request an invite: https://discord.freesewing.org/

View file

@ -0,0 +1,43 @@
---
title: Translating strings
---
Crowdin makes translations of strings very easy. If you provide the translation, Crowdin will make sure your changes make it back into our repository, where they will be picked up and merged by one of the development people.
Here's what you need to know to get started:
- Crowdin link: https://crowdin.com/project/freesewing
- Request an invite: https://gitter.im/freesewing/translation
## Syntax
Most strings are just text, but sometimes you'll find a little markup sprinkled in.
### HTML formatting
When you encounter HTML tags, simply translate around them. For example:
```markup
<b>No</b>, never.
```
looks like this in Spanish:
```markup
<b>No</b>, nunca.
```
### Placeholders
When you encounter a `{key}` between curly braces, leave it as-is. These will be filled in later with the correct value. For example:
```markup
{field} saved
```
looks like this in Spanish
```yaml
{field} guardado
```

View file

@ -0,0 +1,43 @@
---
title: Translating strings
---
Crowdin makes translations of strings very easy. If you provide the translation, Crowdin will make sure your changes make it back into our repository, where they will be picked up and merged by one of the development people.
Here's what you need to know to get started:
- Crowdin link: https://crowdin.com/project/freesewing
- Request an invite: https://gitter.im/freesewing/translation
## Syntax
Most strings are just text, but sometimes you'll find a little markup sprinkled in.
### HTML formatting
When you encounter HTML tags, simply translate around them. Par exemple :
```markup
<b>No</b>, never.
```
looks like this in Spanish:
```markup
<b>No</b>, nunca.
```
### Placeholders
When you encounter a `{key}` between curly braces, leave it as-is. These will be filled in later with the correct value. Par exemple :
```markup
{field} saved
```
looks like this in Spanish
```yaml
{field} guardado
```

View file

@ -0,0 +1,43 @@
---
title: Translating strings
---
Crowdin makes translations of strings very easy. If you provide the translation, Crowdin will make sure your changes make it back into our repository, where they will be picked up and merged by one of the development people.
Hier is wat je moet weten om aan de slag te gaan:
- Crowdin link: https://crowdin.com/project/freesewing
- Request an invite: https://gitter.im/freesewing/translation
## Syntax
Most strings are just text, but sometimes you'll find a little markup sprinkled in.
### HTML formatting
When you encounter HTML tags, simply translate around them. For example:
```markup
<b>No</b>, never.
```
looks like this in Spanish:
```markup
<b>No</b>, nunca.
```
### Placeholders
When you encounter a `{key}` between curly braces, leave it as-is. These will be filled in later with the correct value. For example:
```markup
{field} saved
```
looks like this in Spanish
```yaml
{field} guardado
```

View file

@ -0,0 +1,35 @@
---
title: Syntax
---
Most strings are just text, but sometimes you'll find a little markup sprinkled in.
#### HTML formatting
When you encounter HTML tags, simply translate around them. For example:
```yaml
<b>No</b>, never.
```
looks like this in Spanish:
```yaml
<b>No</b>, nunca.
```
#### Placeholders
When you encounter a `{key}` between curly braces, leave it as-is.
These will be filled in later with the correct value. For example:
```yaml
{field} saved
```
looks like this in Spanish
```yaml
{field} guardado
```

View file

@ -0,0 +1,37 @@
---
title: Translating content
---
Crowdin makes translations of strings very easy. If you provide the translation, Crowdin will make sure your changes make it back into our repository, where they will be picked up and merged by one of the development people.
Here's what you need to know to get started:
- Crowdin link: https://crowdin.com/project/fs-markdown
- Request an invite: https://gitter.im/freesewing/help
<Tip>
When translating content, please give priority to the content of freesewing.org,
before tackling developer documentation for freesewing.dev.
In other words, do the `org` folder first.
</Tip>
## Content as strings
Translating content used to be very different from translating strings, because you had to translate entire pages in one go, adapt links and so on.
Today, they are much the same as Crowdin breaks down all content (blog posts, documentation, and so on) into individual sentences. This may seem weird at first, but it actually has a number of benefits:
- You never have to tackle an enourmous page of documentation. Whenever you have a few minutes to spare, you can just jump in, and translate a few sentences. This makes it much simpler to collaborate with others.
- When (part) of the original (English) content is changed, Crowdin will detect that and let you know exactly what sentences need to be updated.
- It's easier to keep track of how much has been done/remains to be done
- Content is more consistent across languages
## Syntax
Content will contain MarkDown syntax. MarkDown is a straight-forward way to format text to turn it into HTML. Youll be familiar with it in no time.
The [official MarkDown documentation](https://daringfireball.net/projects/markdown/syntax) is a bit dry, but there's plenty of MarkDown guides out there.
If you have any questions, [we're here to help](https://gitter.im/freesewing/translation).

View file

@ -0,0 +1,23 @@
---
title: Markdown
---
This Crowdin project holds all our *markdown content*.
Crowdin makes translations of content very easy by breaking it apart into sentences and paragraphs.
This may seem weird at first, but it actually has a number of benefits:
- You never have to tackle an enourmous page of documentation. Whenever you have a few
minutes to spare, you can just jump in, and translate a few sentences. This makes it much
simpler to collaborate with others.
- When (part) of the original (English) content is changed, Crowdin will detect that and let you know exactly what sentences need to be updated.
- It's easier to keep track of how much has been done/remains to be done
- Content is more consistent across languages
Once you provide the translation, Crowdin will make sure your changes make it back
into our repository, where they will be picked up and merged by one of the development people.
Here's what you need to know to get started:
- Crowdin link: https://crowdin.com/project/fs-markdown
- Request an invite: https://discord.freesewing.org/

View file

@ -0,0 +1,37 @@
---
title: Translating content
---
Crowdin makes translations of strings very easy. If you provide the translation, Crowdin will make sure your changes make it back into our repository, where they will be picked up and merged by one of the development people.
Here's what you need to know to get started:
- Crowdin link: https://crowdin.com/project/fs-markdown
- Request an invite: https://gitter.im/freesewing/help
<Tip>
When translating content, please give priority to the content of freesewing.org,
before tackling developer documentation for freesewing.dev.
In other words, do the `org` folder first.
</Tip>
## Content as strings
Translating content used to be very different from translating strings, because you had to translate entire pages in one go, adapt links and so on.
Today, they are much the same as Crowdin breaks down all content (blog posts, documentation, and so on) into individual sentences. This may seem weird at first, but it actually has a number of benefits:
- You never have to tackle an enourmous page of documentation. Whenever you have a few minutes to spare, you can just jump in, and translate a few sentences. This makes it much simpler to collaborate with others.
- When (part) of the original (English) content is changed, Crowdin will detect that and let you know exactly what sentences need to be updated.
- It's easier to keep track of how much has been done/remains to be done
- Content is more consistent across languages
## Syntax
Content will contain MarkDown syntax. MarkDown is a straight-forward way to format text to turn it into HTML. Youll be familiar with it in no time.
The [official MarkDown documentation](https://daringfireball.net/projects/markdown/syntax) is a bit dry, but there's plenty of MarkDown guides out there.
If you have any questions, [we're here to help](https://gitter.im/freesewing/translation).

View file

@ -0,0 +1,37 @@
---
title: Translating content
---
Crowdin makes translations of strings very easy. If you provide the translation, Crowdin will make sure your changes make it back into our repository, where they will be picked up and merged by one of the development people.
Here's what you need to know to get started:
- Crowdin link: https://crowdin.com/project/fs-markdown
- Request an invite: https://gitter.im/freesewing/help
<Tip>
When translating content, please give priority to the content of freesewing.org,
before tackling developer documentation for freesewing.dev.
In other words, do the `org` folder first.
</Tip>
## Content as strings
Translating content used to be very different from translating strings, because you had to translate entire pages in one go, adapt links and so on.
Today, they are much the same as Crowdin breaks down all content (blog posts, documentation, and so on) into individual sentences. This may seem weird at first, but it actually has a number of benefits:
- You never have to tackle an enourmous page of documentation. Whenever you have a few minutes to spare, you can just jump in, and translate a few sentences. This makes it much simpler to collaborate with others.
- When (part) of the original (English) content is changed, Crowdin will detect that and let you know exactly what sentences need to be updated.
- It's easier to keep track of how much has been done/remains to be done
- Content is more consistent across languages
## Syntax
Content will contain MarkDown syntax. MarkDown is a straight-forward way to format text to turn it into HTML. Youll be familiar with it in no time.
The [official MarkDown documentation](https://daringfireball.net/projects/markdown/syntax) is a bit dry, but there's plenty of MarkDown guides out there.
If you have any questions, [we're here to help](https://gitter.im/freesewing/translation).

View file

@ -0,0 +1,36 @@
---
title: Materiaal vertalen
---
Crowdin makes translations of strings very easy. If you provide the translation, Crowdin will make sure your changes make it back into our repository, where they will be picked up and merged by one of the development people.
Hier is wat je moet weten om aan de slag te gaan:
- Crowdin link: https://crowdin.com/project/fs-markdown
- Request an invite: https://gitter.im/freesewing/help
<Tip>
Als je gaat vertalen, geef dan voorang aan de inhoud van freesewing.org, voordat je aan de ontwikkel inhoud van freesewing.dev gaat denken.
In other words, do the `org` folder first.
</Tip>
## Inhoud als tekst
Translating content used to be very different from translating strings, because you had to translate entire pages in one go, adapt links and so on.
Tegenwoordig worden ze vrijwel hetzelfde behandeld, want Crowdin breek alle inhoud (blog posts, documentatie, enzovoort) op in individuele zinnen. Dit lijkt vreemd in het begin, maar het heeft een aantal voordelen:
- Je hoeft nooit een grote heoveelheid tekst in een keer te vertalen. Als je wat tijd hebt kun je gewoon een paar zinnen vertalen. Dit maakt het een stuk makkelijker om met anderen samen te werken.
- When (part) of the original (English) content is changed, Crowdin will detect that and let you know exactly what sentences need to be updated.
- It's easier to keep track of how much has been done/remains to be done
- Content is more consistent across languages
## Syntax
Content will contain MarkDown syntax. MarkDown is a straight-forward way to format text to turn it into HTML. Youll be familiar with it in no time.
The [official MarkDown documentation](https://daringfireball.net/projects/markdown/syntax) is a bit dry, but there's plenty of MarkDown guides out there.
If you have any questions, [we're here to help](https://gitter.im/freesewing/translation).

View file

@ -0,0 +1,11 @@
---
title: Syntax
---
# Syntax
Content will contain MarkDown syntax. MarkDown is a straight-forward way to format text
to turn it into HTML. Youll be familiar with it in no time.
Our [guide on Markdown](/editors/markdown/) covers all you need to know.
If you have any questions, [we're here to help](https://discord.freesewing.org/).

View file

@ -0,0 +1,14 @@
---
title: For translators
order: 1140
---
Freesewing is proudly multilingual, and for this we depend on translators to help us.
We use [crowdin](https://crowdin.com/) to manage translations for FreeSewing,
and current support 5 languages.
Find out more with the links below:
<ReadMore list />

View file

@ -0,0 +1,19 @@
---
title: Languages
---
English is our origin language. Which means that everything is written in English
and then translated from English into other languages.
We currently support the following five languages:
- **en** : English (our origin language)
- **de** : German
- **es** : Spanish
- **fr** : French
- **nl** : Dutch
If you'd like to start working on a new language, that's great, but a bit
beyond the scope of this documentation. So in that case,
please [come and talk to us on Discord](https://discord.freesewing.org).