Remove unnecessary content and start filling in content pages of website

Author: ndgrigorian

content/en/docs/_index.md

@@ -1,28 +1,13 @@
 ---
-title: Details
+title: SciPy 2024 poster content
 linkTitle: Details
 menu: {main: {weight: 20}}
 ---
 
-{{% pageinfo %}}
-This is a placeholder page that shows you how to use this template site.
-{{% /pageinfo %}}
-
-This section is where the user documentation for your project lives - all the
-information your users need to understand and successfully use your project.
-
-For large documentation sets we recommend adding content under the headings in
-this section, though if some or all of them don’t apply to your project feel
-free to remove them or add your own. You can see an example of a smaller Docsy
-documentation site in the [Docsy User Guide](https://docsy.dev/docs/), which
-lives in the [Docsy theme
-repo](https://github.com/google/docsy/tree/master/userguide) if you'd like to
-copy its docs section.
+Portable Data-Parallel Extensions with oneAPI
+---
+by [Nikita Grigorian](https://github.com/ndgrigorian) and [Oleksandr Pavlyk](https://github.com/oleksandr-pavlyk)
 
-Other content such as marketing material, case studies, and community updates
-should live in the [About](/about/) and [Community](/community/) pages.
+This poster is intended to introduce writing portable data-parallel Python extensions using oneAPI.
 
-Find out how to use the Docsy theme in the [Docsy User
-Guide](https://docsy.dev/docs/). You can learn more about how to organize your
-documentation (and how we organized this site) in [Organizing Your
-Content](https://docsy.dev/docs/best-practices/organizing-content/).
+We present several examples, starting with the basics of initializing a USM (universal shared memory) array, then a KDE (kernel density estimation) with pure DPC++/Sycl, then a KDE Python extension, and finally how to write a portable Python extension which uses oneMKL.

content/en/docs/examples.md renamed to content/en/docs/first-app.md

@@ -1,8 +1,8 @@
 ---
-title: Examples
-description: See your project in action!
+title: First DPC++ app
+description: A SYCL and DPC++ "Hello, World!" example.
 date: 2017-01-05
-weight: 3
+weight: 2
 ---
 
 {{% pageinfo %}}

content/en/docs/getting-started/_index.md

@@ -1,7 +1,7 @@
 ---
-title: Contribution Guidelines
-description: How to contribute to the docs
-weight: 10
+title: KDE DPC++ example
+description: KDE (kernel density estimation) example using SYCL and DPC++.
+weight: 2
 ---
 
 {{% pageinfo %}}

content/en/docs/getting-started/example-page.md

@@ -1,8 +1,7 @@
 ---
-title: Concepts
-description: >
-  What does your user need to understand about your project in order to use it - or potentially contribute to it?
-weight: 4
+title: KDE Python extension
+description: KDE (kernel density estimation) Python extension example.
+weight: 3
 ---
 
 {{% pageinfo %}}

content/en/docs/contribution-guidelines.md renamed to content/en/docs/kde-cpp.md

@@ -1,15 +1,10 @@
 ---
-title: Overview
-description: Here's where your user finds out if your project is for them.
+title: About oneAPI
+linkTitle: About oneAPI
+description: A brief overview of oneAPI and the programming model.
 weight: 1
 ---
 
-{{% pageinfo %}}
-
-This is a placeholder page that shows you how to use this template site.
-
-{{% /pageinfo %}}
-
 The Overview is where your users find out about your project. Depending on the
 size of your docset, you can have a separate overview page (like this one) or
 put your overview contents in the Documentation landing page (like in the Docsy

content/en/docs/concepts.md renamed to content/en/docs/kde-python.md

@@ -0,0 +1,15 @@
+---
+title: oneMKL Python extension
+description: A Python extension written using oneMKL interfaces.
+date: 2017-01-05
+weight: 4
+---
+
+{{% pageinfo %}}
+
+This is a placeholder page that shows you how to use this template site.
+
+{{% /pageinfo %}}
+
+Do you have any example **applications** or **code** for your users in your repo
+or elsewhere? Link to your examples here.