Guide: move content intro to main guide

Author: distantnative

content/docs/1_guide/4_content/1_introduction/guide.txt

@@ -6,8 +6,88 @@ Description: Learn how to create pages and how to fill them with content.
 
 ----
 
+Intro: Files and folders are Kirby's primary data source in which you can organize your content exactly how you need it. If you need to build to scale, you can go beyond and add data from any data source.
+
+----
+
 Category: Creating your site
 
 ----
 
-Icon: copy
+Screencast:
+
+(screencast: https://www.youtube.com/watch?v=zUPqqrhbcR8 title: The content folder text: The heart and soul of your Kirby installation: Let's learn how to create pages and add content with simple text files and folders. )
+
+
+----
+
+Text:
+
+## Files and folders
+
+Since Kirby is a flat-file CMS, all content is stored in files and folders within the `content` folder. Each folder you create represents a page that is accessible via its own URL.
+
+If you create a folder called `blog` as direct child of the `content` folder, it will be accessible via `https://yourdomain.com/blog` etc.
+
+Page folders can serve as pages in their own right, i.e. only contain the content from their own folder, or they can serve as data containers for their parents, or they can be used in other parts of the project.
+
+
+All content you create in the backend can also just serve as a data store, ready to be consumed in your SPA or other types of media.
+
+<success>
+Content in Kirby can also come from a database, from an external API, Excel sheets or any other data source. We will cover this in (link: docs/guide/virtual-content text: other parts of the documentation).
+</success>
+
+
+## Editing content
+
+The flat-file architecture of Kirby makes creating and editing content in Kirby highly flexible. You can create content in three ways in Kirby, in fact, all three ways can be used in parallel.
+
+1. You can use the (glossary: panel text: Panel) to edit content and upload files.
+
+2. You can create files and folders manually in the file system and edit content files with the text editor of your choice.
+
+3. You can create and modify content programmatically using Kirby's API, for example, create pages from `.csv` files or from form content on the front-end.
+
+(link: docs/guide/content/creating-pages text: Read more ›)
+
+
+## Publishing workflow
+
+Customizable page states give you maximum control over your workflow, from drafts over unreviewed to published pages. Choose what you need and start creating.
+
+In Kirby, pages can have three states:
+
+- draft
+- listed
+- unlisted
+
+
+Drafts are only accessible to logged-in users, while listed and unlisted pages are accessible via their URL.
+
+You can use these states to filter files in the frontend or to implement a multi-step publishing workflow for drafts, in-review and published pages.
+
+
+(link: docs/guide/content/publishing-workflow text: Read more ›)
+
+## Structuring content
+
+Your content is your biggest asset, and structuring it in a way that makes it easily accessible and ideally reusable across different types of media ([Single Source Publishing](https://en.wikipedia.org/wiki/Single-source_publishing)) is therefore important.
+
+Organize content your way. Every page type or data entry can have the completely unique data structure that your project demands.
+
+(link: docs/guide/content/fields text: Read more ›)
+
+## Media files
+
+Kirby stores media files in the same folder as the page content instead of putting everything into a huge media library. In addition, you can store media files in the `site` object, i.e. directly in the `content` folder.
+
+Kirby works with all types of media files and allows you to store meta data for each file in the same flexible way you can store information for pages.
+
+(link: docs/guide/files text: Read more ›)
+
+## Text formatting
+
+When writing for the web, nobody really wants to wrap HTML tags around text. On the other hand, most WYSIWYG editors produce awful HTML output and have tons of other issues. In Kirby, content is therefore marked up and formatted in Markdown or our extended version of it, which we call KirbyText.
+
+(link: docs/guide/content/text-formatting text: Read more ›)

content/docs/1_guide/4_content/4_fields/guide.txt content/docs/1_guide/4_content/3_fields/guide.txt

@@ -28,7 +28,7 @@ Text:
 
 ## What are UUIDs?
 
-Kirby is built on (link: docs/guide/content/introduction text: just files and folders), which is great for flexibility in structuring your content, performance and rapid development. Referring to a page or file from elsewhere by its file path works, but makes the site structure pretty rigid and takes away a lot of the flexibility of the content structure. Because as soon as a page or file gets renamed or moved, its file path changes – and immediately the reference to it will break.
+Kirby is built on (link: docs/guide/content text: just files and folders), which is great for flexibility in structuring your content, performance and rapid development. Referring to a page or file from elsewhere by its file path works, but makes the site structure pretty rigid and takes away a lot of the flexibility of the content structure. Because as soon as a page or file gets renamed or moved, its file path changes – and immediately the reference to it will break.
 
 UUIDs (universally unique identifiers) are an additional way to refer to any model in Kirby – be it a page, a file or a user. UUIDs look something like `page://Eesj89FnbMzMMvs0`. In contrast to file paths, UUIDs never change. They are randomly generated when the model gets first created. It is so unlikely that two models ever share the same UUID that they can be considered unique (in fact, it will take millions of years to reach a 1% probability of a collision on any given site). These properties make UUIDs the ideal candidate for robust and persistent references.
 

content/docs/1_guide/4_content/3_publishing-workflow/changes.png content/docs/1_guide/4_content/4_publishing-workflow/changes.png

@@ -6,4 +6,4 @@ Entry:
 Content can refer either to the content folder or to anything within the content folder: text files, media files or metadata files.
 
 ----
-Link: docs/guide/content/introduction
+Link: docs/guide/content