Split out documentation into subfolders.

[platform/upstream/gstreamer.git] / markdown / manual / advanced / autoplugging.md

diff --git a/manual-autoplugging.md b/markdown/manual/advanced/autoplugging.md
similarity index 94%
rename from manual-autoplugging.md
rename to markdown/manual/advanced/autoplugging.md
index 60d65de..cd82fef 100644 (file)
--- a/manual-autoplugging.md
+++ b/markdown/manual/advanced/autoplugging.md
@@ -4,7 +4,7 @@ title: Autoplugging
 
 # Autoplugging
 
-In [Your first application](manual-helloworld.md), you've learned to
+In [Your first application](manual/building/helloworld.md), you've learned to
 build a simple media player for Ogg/Vorbis files. By using alternative
 elements, you are able to build media players for other media types,
 such as Ogg/Speex, MP3 or even video formats. However, you would rather
@@ -13,7 +13,7 @@ type of a stream and automatically generate the best possible pipeline
 by looking at all available elements in a system. This process is called
 autoplugging, and GStreamer contains high-quality autopluggers. If
 you're looking for an autoplugger, don't read any further and go to
-[Playback Components](manual-playback-components.md). This chapter will
+[Playback Components](manual/highlevel/playback-components.md). This chapter will
 explain the *concept* of autoplugging and typefinding. It will explain
 what systems GStreamer includes to dynamically detect the type of a
 media stream, and how to generate a pipeline of decoder elements to
@@ -34,7 +34,7 @@ to another, for example for media decoding.
 We have previously introduced the concept of capabilities as a way for
 elements (or, rather, pads) to agree on a media type when streaming data
 from one element to the next (see [Capabilities of a
-pad](manual-pads.md#capabilities-of-a-pad)). We have explained that a
+pad](manual/building/pads.md#capabilities-of-a-pad)). We have explained that a
 capability is a combination of a media type and a set of properties. For
 most container formats (those are the files that you will find on your
 hard disk; Ogg, for example, is a container format), no properties are
@@ -49,7 +49,7 @@ elements and what type of data they expect and emit through the
 GStreamer registry. This allows for very dynamic and extensible element
 creation as we will see.
 
-In [Your first application](manual-helloworld.md), we've learned to
+In [Your first application](manual/building/helloworld.md), we've learned to
 build a music player for Ogg/Vorbis files. Let's look at the media types
 associated with each pad in this pipeline. [The Hello world pipeline
 with media types](#the-hello-world-pipeline-with-media-types) shows what
@@ -130,7 +130,7 @@ cb_typefound (GstElement *typefind,
   g_idle_add (idle_exit_loop, loop);
 }
 
-gint 
+gint
 main (gint   argc,
       gchar *argv[])
 {
@@ -174,7 +174,7 @@ main (gint   argc,
 
   return 0;
 }
-    
+
 ```
 
 Once a media type has been detected, you can plug an element (e.g. a
@@ -183,6 +183,5 @@ decoding of the media stream will start right after.
 
 ## Dynamically autoplugging a pipeline
 
-See [Playback Components](manual-playback-components.md) for using the
+See [Playback Components](manual/highlevel/playback-components.md) for using the
 high level object that you can use to dynamically construct pipelines.
-