-
Not found
-
Oops! This page doesn't exist. Try going back to the home page.
-
You can learn how to make a 404 page like this in Custom 404 Pages.
-
This project has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No 101004719
-{{% /blocks/section %}}
-
-
-
-
diff --git a/content/en/about/index.md b/content/en/about/index.md
deleted file mode 100644
index 38f08f4..0000000
--- a/content/en/about/index.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: About
-linkTitle: About
-menu: {main: {weight: 10}}
----
-
-{{% blocks/cover title="About Polaris" image_anchor="bottom" height="auto" %}}
-
-Polaris is a toolkit for creating and managing astronomical proposals for observing time
-{.mt-5}
-
-{{% /blocks/cover %}}
-
-{{% blocks/lead %}}
-
-Polaris is a toolkit for creating and managing astronomical observing proposals.
-
-{{% /blocks/lead %}}
-
-{{% blocks/section %}}
-
-# Deployments
-{.text-center}
-
-There is an experimental deployment at
-
-{{% /blocks/section %}}
-
-{{% blocks/section %}}
-
-# History
-{.text-center}
-
-Polaris was created as part of the [
](https://www.orp-h2020.eu)
-
-{{% /blocks/section %}}
\ No newline at end of file
diff --git a/content/en/blog/_index.md b/content/en/blog/_index.md
deleted file mode 100644
index 95ccb91..0000000
--- a/content/en/blog/_index.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Blog
-menu: {main: {weight: 30}}
----
-
-This is the **blog** section. It has two categories: News and Releases.
-
-Files in these directories will be listed in reverse chronological order.
diff --git a/content/en/blog/news/_index.md b/content/en/blog/news/_index.md
deleted file mode 100644
index c609aa2..0000000
--- a/content/en/blog/news/_index.md
+++ /dev/null
@@ -1,4 +0,0 @@
----
-title: News
-weight: 20
----
diff --git a/content/en/blog/news/first-post/featured-sunset-get.png b/content/en/blog/news/first-post/featured-sunset-get.png
deleted file mode 100644
index db3373c..0000000
Binary files a/content/en/blog/news/first-post/featured-sunset-get.png and /dev/null differ
diff --git a/content/en/blog/news/first-post/index.md b/content/en/blog/news/first-post/index.md
deleted file mode 100644
index e7a2d53..0000000
--- a/content/en/blog/news/first-post/index.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-date: 2023-11-06
-title: Easy proposals with Polaris
-linkTitle: Announcing Polaris
-description: >
- The Docsy Hugo theme lets project maintainers and contributors focus on content,
- not on reinventing a website infrastructure from scratch
-author: Riona MacNamara ([@rionam](https://twitter.com/bepsays))
-resources:
- - src: "**.{png,jpg}"
- title: "Image #:counter"
- params:
- byline: "Photo: Riona MacNamara / CC-BY-CA"
----
-
-**This is a typical blog post that includes images.**
-
-The front matter specifies the date of the blog post, its title, a short description that will be displayed on the blog landing page, and its author.
-
-## Including images
-
-Here's an image (`featured-sunset-get.png`) that includes a byline and a caption.
-
-{{< imgproc sunset Fill "600x300" >}}
-Fetch and scale an image in the upcoming Hugo 0.43.
-{{< /imgproc >}}
-
-The front matter of this post specifies properties to be assigned to all image resources:
-
-```
-resources:
-- src: "**.{png,jpg}"
- title: "Image #:counter"
- params:
- byline: "Photo: Riona MacNamara / CC-BY-CA"
-```
-
-To include the image in a page, specify its details like this:
-
-```
-{{< imgproc sunset Fill "600x300" >}}
-Fetch and scale an image in the upcoming Hugo 0.43.
-{{< /imgproc >}}
-```
-
-The image will be rendered at the size and byline specified in the front matter.
-
-
diff --git a/content/en/blog/releases/_index.md b/content/en/blog/releases/_index.md
deleted file mode 100644
index 9143a23..0000000
--- a/content/en/blog/releases/_index.md
+++ /dev/null
@@ -1,4 +0,0 @@
----
-title: Releases
-weight: 20
----
diff --git a/content/en/blog/releases/alpha.md b/content/en/blog/releases/alpha.md
deleted file mode 100755
index eeaf122..0000000
--- a/content/en/blog/releases/alpha.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Alpha Release
-date: 2023-11-04
-description: >
- A short lead description about this content page. Text here can also be
- **bold** or _italic_ and can even be split over multiple paragraphs.
----
-
-# Alpha
-
-```
-This is the final element on the page and there should be no margin below this.
-```
diff --git a/content/en/community/_index.md b/content/en/community/_index.md
deleted file mode 100644
index 3f237b8..0000000
--- a/content/en/community/_index.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Community
-menu: {main: {weight: 40}}
----
-
-
diff --git a/content/en/docs/Concepts/_index.md b/content/en/docs/Concepts/_index.md
deleted file mode 100644
index 4a5d175..0000000
--- a/content/en/docs/Concepts/_index.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Concepts
-weight: 4
-description: >
- What does your user need to understand about your project in order to use it - or potentially contribute to it?
----
-
-{{% pageinfo %}}
-This is a placeholder page that shows you how to use this template site.
-{{% /pageinfo %}}
-
-For many projects, users may not need much information beyond the information in the [Overview](/docs/overview/), so this section is **optional**. However if there are areas where your users will need a more detailed understanding of a given term or feature in order to do anything useful with your project (or to not make mistakes when using it) put that information in this section. For example, you may want to add some conceptual pages if you have a large project with many components and a complex architecture.
-
-Remember to focus on what the user needs to know, not just what you think is interesting about your project! If they don’t need to understand your original design decisions to use or contribute to the project, don’t put them in, or include your design docs in your repo and link to them. Similarly, most users will probably need to know more about how features work when in use rather than how they are implemented. Consider a separate architecture page for more detailed implementation and system design information that potential project contributors can consult.
diff --git a/content/en/docs/Contribution guidelines/_index.md b/content/en/docs/Contribution guidelines/_index.md
deleted file mode 100644
index 1f9fd09..0000000
--- a/content/en/docs/Contribution guidelines/_index.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-title: Contribution Guidelines
-weight: 10
-description: How to contribute to the docs
----
-
-{{% pageinfo %}}
-These basic sample guidelines assume that your Docsy site is deployed using Netlify and your files are stored in GitHub. You can use the guidelines "as is" or adapt them with your own instructions: for example, other deployment options, information about your doc project's file structure, project-specific review guidelines, versioning guidelines, or any other information your users might find useful when updating your site. [Kubeflow](https://github.com/kubeflow/website/blob/master/README.md) has a great example.
-
-Don't forget to link to your own doc repo rather than our example site! Also make sure users can find these guidelines from your doc repo README: either add them there and link to them from this page, add them here and link to them from the README, or include them in both locations.
-{{% /pageinfo %}}
-
-We use [Hugo](https://gohugo.io/) to format and generate our website, the
-[Docsy](https://github.com/google/docsy) theme for styling and site structure,
-and [Netlify](https://www.netlify.com/) to manage the deployment of the site.
-Hugo is an open-source static site generator that provides us with templates,
-content organisation in a standard directory structure, and a website generation
-engine. You write the pages in Markdown (or HTML if you want), and Hugo wraps them up into a website.
-
-All submissions, including submissions by project members, require review. We
-use GitHub pull requests for this purpose. Consult
-[GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
-information on using pull requests.
-
-## Quick start with Netlify
-
-Here's a quick guide to updating the docs. It assumes you're familiar with the
-GitHub workflow and you're happy to use the automated preview of your doc
-updates:
-
-1. Fork the [Goldydocs repo](https://github.com/google/docsy-example) on GitHub.
-1. Make your changes and send a pull request (PR).
-1. If you're not yet ready for a review, add "WIP" to the PR name to indicate
- it's a work in progress. (**Don't** add the Hugo property
- "draft = true" to the page front matter, because that prevents the
- auto-deployment of the content preview described in the next point.)
-1. Wait for the automated PR workflow to do some checks. When it's ready,
- you should see a comment like this: **deploy/netlify — Deploy preview ready!**
-1. Click **Details** to the right of "Deploy preview ready" to see a preview
- of your updates.
-1. Continue updating your doc and pushing your changes until you're happy with
- the content.
-1. When you're ready for a review, add a comment to the PR, and remove any
- "WIP" markers.
-
-## Updating a single page
-
-If you've just spotted something you'd like to change while using the docs, Docsy has a shortcut for you:
-
-1. Click **Edit this page** in the top right hand corner of the page.
-1. If you don't already have an up to date fork of the project repo, you are prompted to get one - click **Fork this repository and propose changes** or **Update your Fork** to get an up to date version of the project to edit. The appropriate page in your fork is displayed in edit mode.
-1. Follow the rest of the [Quick start with Netlify](#quick-start-with-netlify) process above to make, preview, and propose your changes.
-
-## Previewing your changes locally
-
-If you want to run your own local Hugo server to preview your changes as you work:
-
-1. Follow the instructions in [Getting started](/docs/getting-started) to install Hugo and any other tools you need. You'll need at least **Hugo version 0.45** (we recommend using the most recent available version), and it must be the **extended** version, which supports SCSS.
-1. Fork the [Goldydocs repo](https://github.com/google/docsy-example) repo into your own project, then create a local copy using `git clone`. Don’t forget to use `--recurse-submodules` or you won’t pull down some of the code you need to generate a working site.
-
- ```
- git clone --recurse-submodules --depth 1 https://github.com/google/docsy-example.git
- ```
-
-1. Run `hugo server` in the site root directory. By default your site will be available at http://localhost:1313/. Now that you're serving your site locally, Hugo will watch for changes to the content and automatically refresh your site.
-1. Continue with the usual GitHub workflow to edit files, commit them, push the
- changes up to your fork, and create a pull request.
-
-## Creating an issue
-
-If you've found a problem in the docs, but you're not sure how to fix it yourself, please create an issue in the [Goldydocs repo](https://github.com/google/docsy-example/issues). You can also create an issue about a specific page by clicking the **Create Issue** button in the top right hand corner of the page.
-
-## Useful resources
-
-* [Docsy user guide](https://www.docsy.dev/docs/): All about Docsy, including how it manages navigation, look and feel, and multi-language support.
-* [Hugo documentation](https://gohugo.io/documentation/): Comprehensive reference for Hugo.
-* [Github Hello World!](https://guides.github.com/activities/hello-world/): A basic introduction to GitHub concepts and workflow.
-
-
diff --git a/content/en/docs/Developer/_index.md b/content/en/docs/Developer/_index.md
deleted file mode 100644
index 9050be2..0000000
--- a/content/en/docs/Developer/_index.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Developer
-description: Developer level documentation
-weight: 8
----
-
-{{% pageinfo %}}
-Information for developers
-{{% /pageinfo %}}
-
-
diff --git a/content/en/docs/Examples/_index.md b/content/en/docs/Examples/_index.md
deleted file mode 100755
index 2b4a0f0..0000000
--- a/content/en/docs/Examples/_index.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Examples
-weight: 3
-date: 2017-01-05
-description: See your project in action!
----
-
-{{% 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.
diff --git a/content/en/docs/Overview/_index.md b/content/en/docs/Overview/_index.md
deleted file mode 100644
index 5c51c56..0000000
--- a/content/en/docs/Overview/_index.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Overview
-description: Here's where your user finds out if your project is for them.
-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 User Guide).
-
-Try answering these questions for your user in this page:
-
-## What is it?
-
-Introduce your project, including what it does or lets you do, why you would use it, and its primary goal (and how it achieves it). This should be similar to your README description, though you can go into a little more detail here if you want.
-
-## Why do I want it?
-
-Help your user know if your project will help them. Useful information can include:
-
-* **What is it good for?**: What types of problems does your project solve? What are the benefits of using it?
-
-* **What is it not good for?**: For example, point out situations that might intuitively seem suited for your project, but aren't for some reason. Also mention known limitations, scaling issues, or anything else that might let your users know if the project is not for them.
-
-* **What is it *not yet* good for?**: Highlight any useful features that are coming soon.
-
-## Where should I go next?
-
-Give your users next steps from the Overview. For example:
-
-* [Getting Started](/docs/getting-started/): Get started with $project
-* [Examples](/docs/examples/): Check out some example code!
-
diff --git a/content/en/docs/Reference/_index.md b/content/en/docs/Reference/_index.md
deleted file mode 100644
index e414a42..0000000
--- a/content/en/docs/Reference/_index.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Reference
-description: Low level reference docs for your project.
-weight: 9
----
-
-{{% pageinfo %}}
-This is a placeholder page that shows you how to use this template site.
-{{% /pageinfo %}}
-
-If your project has an API, configuration, or other reference - anything that users need to look up that’s at an even lower level than a single task - put (or link to it) here. You can serve and link to generated reference docs created using Doxygen,
-Javadoc, or other doc generation tools by putting them in your `static/` directory. Find out more in [Adding static content](https://docsy.dev/docs/adding-content/content/#adding-static-content). For OpenAPI reference, Docsy also provides a [Swagger UI layout and shortcode](https://www.docsy.dev/docs/adding-content/shortcodes/#swaggerui) that renders [Swagger UI](https://swagger.io/tools/swagger-ui/) using any OpenAPI YAML or JSON file as source.
diff --git a/content/en/docs/Reference/parameter-reference.md b/content/en/docs/Reference/parameter-reference.md
deleted file mode 100644
index 1f3f5cf..0000000
--- a/content/en/docs/Reference/parameter-reference.md
+++ /dev/null
@@ -1,211 +0,0 @@
----
-title: Parameter Reference
-description: >
- A short lead description about this content page. It can be **bold** or _italic_ and can be split over multiple paragraphs.
-date: 2017-01-05
----
-
-{{% pageinfo %}}
-This is a placeholder page. Replace it with your own content.
-{{% /pageinfo %}}
-
-Text can be **bold**, _italic_, or ~~strikethrough~~. [Links](https://gohugo.io) should be blue with no underlines (unless hovered over).
-
-There should be whitespace between paragraphs. Vape migas chillwave sriracha poutine try-hard distillery. Tattooed shabby chic small batch, pabst art party heirloom letterpress air plant pop-up. Sustainable chia skateboard art party banjo cardigan normcore affogato vexillologist quinoa meggings man bun master cleanse shoreditch readymade. Yuccie prism four dollar toast tbh cardigan iPhone, tumblr listicle live-edge VHS. Pug lyft normcore hot chicken biodiesel, actually keffiyeh thundercats photo booth pour-over twee fam food truck microdosing banh mi. Vice activated charcoal raclette unicorn live-edge post-ironic. Heirloom vexillologist coloring book, beard deep v letterpress echo park humblebrag tilde.
-
-90's four loko seitan photo booth gochujang freegan tumeric listicle fam ugh humblebrag. Bespoke leggings gastropub, biodiesel brunch pug fashion axe meh swag art party neutra deep v chia. Enamel pin fanny pack knausgaard tofu, artisan cronut hammock meditation occupy master cleanse chartreuse lumbersexual. Kombucha kogi viral truffaut synth distillery single-origin coffee ugh slow-carb marfa selfies. Pitchfork schlitz semiotics fanny pack, ugh artisan vegan vaporware hexagon. Polaroid fixie post-ironic venmo wolf ramps **kale chips**.
-
-> There should be no margin above this first sentence.
->
-> Blockquotes should be a lighter gray with a border along the left side in the secondary color.
->
-> There should be no margin below this final sentence.
-
-## First Header 2
-
-This is a normal paragraph following a header. Knausgaard kale chips snackwave microdosing cronut copper mug swag synth bitters letterpress glossier **craft beer**. Mumblecore bushwick authentic gochujang vegan chambray meditation jean shorts irony. Viral farm-to-table kale chips, pork belly palo santo distillery activated charcoal aesthetic jianbing air plant woke lomo VHS organic. Tattooed locavore succulents heirloom, small batch sriracha echo park DIY af. Shaman you probably haven't heard of them copper mug, crucifix green juice vape *single-origin coffee* brunch actually. Mustache etsy vexillologist raclette authentic fam. Tousled beard humblebrag asymmetrical. I love turkey, I love my job, I love my friends, I love Chardonnay!
-
-Deae legum paulatimque terra, non vos mutata tacet: dic. Vocant docuique me plumas fila quin afuerunt copia haec o neque.
-
-On big screens, paragraphs and headings should not take up the full container width, but we want tables, code blocks and similar to take the full width.
-
-Scenester tumeric pickled, authentic crucifix post-ironic fam freegan VHS pork belly 8-bit yuccie PBR&B. **I love this life we live in**.
-
-
-## Second Header 2
-
-> This is a blockquote following a header. Bacon ipsum dolor sit amet t-bone doner shank drumstick, pork belly porchetta chuck sausage brisket ham hock rump pig. Chuck kielbasa leberkas, pork bresaola ham hock filet mignon cow shoulder short ribs biltong.
-
-### Header 3
-
-```
-This is a code block following a header.
-```
-
-Next level leggings before they sold out, PBR&B church-key shaman echo park. Kale chips occupy godard whatever pop-up freegan pork belly selfies. Gastropub Belinda subway tile woke post-ironic seitan. Shabby chic man bun semiotics vape, chia messenger bag plaid cardigan.
-
-#### Header 4
-
-* This is an unordered list following a header.
-* This is an unordered list following a header.
-* This is an unordered list following a header.
-
-##### Header 5
-
-1. This is an ordered list following a header.
-2. This is an ordered list following a header.
-3. This is an ordered list following a header.
-
-###### Header 6
-
-| What | Follows |
-|-----------|-----------------|
-| A table | A header |
-| A table | A header |
-| A table | A header |
-
-----------------
-
-There's a horizontal rule above and below this.
-
-----------------
-
-Here is an unordered list:
-
-* Liverpool F.C.
-* Chelsea F.C.
-* Manchester United F.C.
-
-And an ordered list:
-
-1. Michael Brecker
-2. Seamus Blake
-3. Branford Marsalis
-
-And an unordered task list:
-
-- [x] Create a Hugo theme
-- [x] Add task lists to it
-- [ ] Take a vacation
-
-And a "mixed" task list:
-
-- [ ] Pack bags
-- ?
-- [ ] Travel!
-
-And a nested list:
-
-* Jackson 5
- * Michael
- * Tito
- * Jackie
- * Marlon
- * Jermaine
-* TMNT
- * Leonardo
- * Michelangelo
- * Donatello
- * Raphael
-
-Definition lists can be used with Markdown syntax. Definition headers are bold.
-
-Name
-: Godzilla
-
-Born
-: 1952
-
-Birthplace
-: Japan
-
-Color
-: Green
-
-
-----------------
-
-Tables should have bold headings and alternating shaded rows.
-
-| Artist | Album | Year |
-|-------------------|-----------------|------|
-| Michael Jackson | Thriller | 1982 |
-| Prince | Purple Rain | 1984 |
-| Beastie Boys | License to Ill | 1986 |
-
-If a table is too wide, it should scroll horizontally.
-
-| Artist | Album | Year | Label | Awards | Songs |
-|-------------------|-----------------|------|-------------|----------|-----------|
-| Michael Jackson | Thriller | 1982 | Epic Records | Grammy Award for Album of the Year, American Music Award for Favorite Pop/Rock Album, American Music Award for Favorite Soul/R&B Album, Brit Award for Best Selling Album, Grammy Award for Best Engineered Album, Non-Classical | Wanna Be Startin' Somethin', Baby Be Mine, The Girl Is Mine, Thriller, Beat It, Billie Jean, Human Nature, P.Y.T. (Pretty Young Thing), The Lady in My Life |
-| Prince | Purple Rain | 1984 | Warner Brothers Records | Grammy Award for Best Score Soundtrack for Visual Media, American Music Award for Favorite Pop/Rock Album, American Music Award for Favorite Soul/R&B Album, Brit Award for Best Soundtrack/Cast Recording, Grammy Award for Best Rock Performance by a Duo or Group with Vocal | Let's Go Crazy, Take Me With U, The Beautiful Ones, Computer Blue, Darling Nikki, When Doves Cry, I Would Die 4 U, Baby I'm a Star, Purple Rain |
-| Beastie Boys | License to Ill | 1986 | Mercury Records | noawardsbutthistablecelliswide | Rhymin & Stealin, The New Style, She's Crafty, Posse in Effect, Slow Ride, Girls, (You Gotta) Fight for Your Right, No Sleep Till Brooklyn, Paul Revere, Hold It Now, Hit It, Brass Monkey, Slow and Low, Time to Get Ill |
-
-----------------
-
-Code snippets like `var foo = "bar";` can be shown inline.
-
-Also, `this should vertically align` ~~`with this`~~ ~~and this~~.
-
-Code can also be shown in a block element.
-
-```
-foo := "bar";
-bar := "foo";
-```
-
-Code can also use syntax highlighting.
-
-```go
-func main() {
- input := `var foo = "bar";`
-
- lexer := lexers.Get("javascript")
- iterator, _ := lexer.Tokenise(nil, input)
- style := styles.Get("github")
- formatter := html.New(html.WithLineNumbers())
-
- var buff bytes.Buffer
- formatter.Format(&buff, style, iterator)
-
- fmt.Println(buff.String())
-}
-```
-
-```
-Long, single-line code blocks should not wrap. They should horizontally scroll if they are too long. This line should be long enough to demonstrate this.
-```
-
-Inline code inside table cells should still be distinguishable.
-
-| Language | Code |
-|-------------|--------------------|
-| Javascript | `var foo = "bar";` |
-| Ruby | `foo = "bar"{` |
-
-----------------
-
-Small images should be shown at their actual size.
-
-
-
-Large images should always scale down and fit in the content container.
-
-
-
-_The photo above of the Spruce Picea abies shoot with foliage buds: Bjørn Erik Pedersen, CC-BY-SA._
-
-
-## Components
-
-### Alerts
-
-{{< alert >}}This is an alert.{{< /alert >}}
-{{< alert title="Note" >}}This is an alert with a title.{{< /alert >}}
-{{% alert title="Note" %}}This is an alert with a title and **Markdown**.{{% /alert %}}
-{{< alert color="success" >}}This is a successful alert.{{< /alert >}}
-{{< alert color="warning" >}}This is a warning.{{< /alert >}}
-{{< alert color="warning" title="Warning" >}}This is a warning with a title.{{< /alert >}}
-
-
-## Another Heading
diff --git a/content/en/docs/Tasks/Deployment/_index.md b/content/en/docs/Tasks/Deployment/_index.md
deleted file mode 100755
index 3594686..0000000
--- a/content/en/docs/Tasks/Deployment/_index.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Deploying Polaris
-description: >
- A short lead description about this section page. Text here can also be **bold** or _italic_ and can even be split over multiple paragraphs.
-date: 2013-11-01
----
-
-{{% pageinfo %}}
-This is a placeholder page. Replace it with your own content.
-{{% /pageinfo %}}
-
-Various tasks for time allocation committees.
diff --git a/content/en/docs/Tasks/Reviewing Proposals/_index.md b/content/en/docs/Tasks/Reviewing Proposals/_index.md
deleted file mode 100755
index 7e6544d..0000000
--- a/content/en/docs/Tasks/Reviewing Proposals/_index.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Reviewing Proposals
-description: >
- A short lead description about this section page. Text here can also be **bold** or _italic_ and can even be split over multiple paragraphs.
-date: 2013-11-01
----
-
-{{% pageinfo %}}
-This is a placeholder page. Replace it with your own content.
-{{% /pageinfo %}}
-
-Various tasks for time allocation committees.
diff --git a/content/en/docs/Tasks/Reviewing Proposals/tac-chair.md b/content/en/docs/Tasks/Reviewing Proposals/tac-chair.md
deleted file mode 100644
index 35a3ca7..0000000
--- a/content/en/docs/Tasks/Reviewing Proposals/tac-chair.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: TAC Chair
-description: >
- Tasks for the TAC Chair
-date: 2017-01-05
-weight: 2
----
-
-{{% pageinfo %}}
-This is a placeholder page. Replace it with your own content.
-{{% /pageinfo %}}
-
diff --git a/content/en/docs/Tasks/Reviewing Proposals/tac-member.md b/content/en/docs/Tasks/Reviewing Proposals/tac-member.md
deleted file mode 100644
index 01c636a..0000000
--- a/content/en/docs/Tasks/Reviewing Proposals/tac-member.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: TAC Member
-description: >
- Tasks for TAC Members
-date: 2017-01-05
-weight: 3
----
-
-{{% pageinfo %}}
-This is a placeholder page. Replace it with your own content.
-{{% /pageinfo %}}
-
diff --git a/content/en/docs/Tasks/_index.md b/content/en/docs/Tasks/_index.md
deleted file mode 100755
index 9d2b855..0000000
--- a/content/en/docs/Tasks/_index.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Core Tasks
-description: What can your user do with your project?
-date: 2017-01-05
-weight: 6
----
-
-{{% pageinfo %}}
-This is a placeholder page that shows you how to use this template site.
-{{% /pageinfo %}}
-
-Think about your project’s features and use cases. Use these to choose your core tasks. Each granular use case (enable x, configure y) should have a corresponding tasks page or tasks page section. Users should be able to quickly refer to your core tasks when they need to find out how to do one specific thing, rather than having to look for the instructions in a bigger tutorial or example. Think of your tasks pages as a cookbook with different procedures your users can combine to create something more substantial.
-
-You can give each task a page, or you can group related tasks together in a page, such as tasks related to a particular feature. As well as grouping related tasks in single pages, you can also group task pages in nested folders with an index page as an overview, as seen in this example site. Or if you have a small docset like the [Docsy User Guide](https://docsy.dev/docs/) with no Tutorials or Concepts pages, consider adding your feature-specific pages at the top level of your docs rather than in a Tasks section.
-
-Each task should give the user
-
-* The prerequisites for this task, if any (this can be specified at the top of a multi-task page if they're the same for all the page's tasks. "All these tasks assume that you understand....and that you have already....").
-* What this task accomplishes.
-* Instructions for the task. If it involves editing a file, running a command, or writing code, provide code-formatted example snippets to show the user what to do! If there are multiple steps, provide them as a numbered list.
-* If appropriate, links to related concept, tutorial, or example pages.
diff --git a/content/en/docs/Tasks/task.md b/content/en/docs/Tasks/task.md
deleted file mode 100644
index a413328..0000000
--- a/content/en/docs/Tasks/task.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Another Task
-description: >
- A short lead description about this content page. It can be **bold** or _italic_ and can be split over multiple paragraphs.
-date: 2023-11-01
-weight: 5
----
-
-{{% pageinfo %}}
-This is a placeholder page. Replace it with your own content.
-{{% /pageinfo %}}
-
-
-Text can be **bold**, _italic_, or ~~strikethrough~~. [Links](https://gohugo.io) should be blue with no underlines (unless hovered over).
diff --git a/content/en/docs/Tutorials/_index.md b/content/en/docs/Tutorials/_index.md
deleted file mode 100755
index 7cd4d1e..0000000
--- a/content/en/docs/Tutorials/_index.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Tutorials
-description: Show your user how to work through some end to end examples.
-date: 2017-01-04
-weight: 8
----
-
-{{% pageinfo %}}
-This is a placeholder page that shows you how to use this template site.
-{{% /pageinfo %}}
-
-Tutorials are **complete worked examples** made up of **multiple tasks** that guide the user through a relatively simple but realistic scenario: building an application that uses some of your project’s features, for example. If you have already created some Examples for your project you can base Tutorials on them. This section is **optional**. However, remember that although you may not need this section at first, having tutorials can be useful to help your users engage with your example code, especially if there are aspects that need more explanation than you can easily provide in code comments.
-
diff --git a/content/en/docs/Tutorials/create-proposal.md b/content/en/docs/Tutorials/create-proposal.md
deleted file mode 100644
index 7aef9cb..0000000
--- a/content/en/docs/Tutorials/create-proposal.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Create Proposal
-description: >
- A short lead description about this content page. It can be **bold** or _italic_ and can be split over multiple paragraphs.
-date: 2023-11-01
-weight: 4
----
-
-{{% pageinfo %}}
-This is a placeholder page. Replace it with your own content.
-{{% /pageinfo %}}
diff --git a/content/en/docs/Tutorials/tutorial2.md b/content/en/docs/Tutorials/tutorial2.md
deleted file mode 100644
index f22609a..0000000
--- a/content/en/docs/Tutorials/tutorial2.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Another Tutorial
-description: >
- A short lead description about this content page. It can be **bold** or _italic_ and can be split over multiple paragraphs.
-date: 2017-01-05
-weight: 5
----
-
-{{% pageinfo %}}
-This is a placeholder page. Replace it with your own content.
-{{% /pageinfo %}}
-
-Text can be **bold**, _italic_, or ~~strikethrough~~. [Links](https://gohugo.io) should be blue with no underlines (unless hovered over).
diff --git a/content/en/docs/_index.md b/content/en/docs/_index.md
deleted file mode 100755
index e4a577e..0000000
--- a/content/en/docs/_index.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Documentation
-linkTitle: Docs
-menu: {main: {weight: 20}}
-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.
-
-Other content such as marketing material, case studies, and community updates
-should live in the [About](/about/) and [Community](/community/) pages.
-
-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/).
diff --git a/content/en/orp_background_image_small.png b/content/en/orp_background_image_small.png
deleted file mode 100644
index 7319fbf..0000000
Binary files a/content/en/orp_background_image_small.png and /dev/null differ
diff --git a/content/en/search.md b/content/en/search.md
deleted file mode 100644
index 394feea..0000000
--- a/content/en/search.md
+++ /dev/null
@@ -1,4 +0,0 @@
----
-title: Search Results
-layout: search
----
diff --git a/docker-compose.yaml b/docker-compose.yaml
deleted file mode 100644
index c6e212f..0000000
--- a/docker-compose.yaml
+++ /dev/null
@@ -1,13 +0,0 @@
-version: "3.3"
-
-services:
-
- site:
- image: orppst/guide
- build:
- context: .
- command: server
- ports:
- - "1313:1313"
- volumes:
- - .:/src
diff --git a/docs/Deployment/index.md b/docs/Deployment/index.md
new file mode 100644
index 0000000..3f7d666
--- /dev/null
+++ b/docs/Deployment/index.md
@@ -0,0 +1,4 @@
+Deploying Polaris
+=================
+
+Polaris is designed to be deployed into a [kubernetes cluster](https://github.com/orppst/k8setup)
\ No newline at end of file
diff --git a/content/en/docs/Developer/api.md b/docs/Developer/api.md
similarity index 100%
rename from content/en/docs/Developer/api.md
rename to docs/Developer/api.md
diff --git a/content/en/docs/Developer/architecture.md b/docs/Developer/architecture.md
similarity index 100%
rename from content/en/docs/Developer/architecture.md
rename to docs/Developer/architecture.md
diff --git a/docs/Developer/index.md b/docs/Developer/index.md
new file mode 100644
index 0000000..0e5d6de
--- /dev/null
+++ b/docs/Developer/index.md
@@ -0,0 +1,20 @@
+# Starting Development on Polaris
+
+requirements
+
+* JDK 17+ installed
+* node
+* yarn v1.x
+* quarkus (is optional)
+* Docker
+
+
+Need to clone the following projects in sibling directories
+
+```shell
+git clone git@github.com:orppst/build-logic.git
+git clone git@github.com:orppst/pst-lib.git
+git clone git@github.com:orppst/pst-api-service.git
+git clone https://github.com/orppst/pst-gui
+```
+
diff --git a/content/en/docs/Developer/use-cases.md b/docs/Developer/use-cases.md
similarity index 100%
rename from content/en/docs/Developer/use-cases.md
rename to docs/Developer/use-cases.md
diff --git a/docs/Observatory/index.md b/docs/Observatory/index.md
new file mode 100644
index 0000000..509b715
--- /dev/null
+++ b/docs/Observatory/index.md
@@ -0,0 +1,4 @@
+Observatory Administrators
+==========================
+
+Functions available to observatory administrators
\ No newline at end of file
diff --git a/content/en/docs/Getting started/Creating Proposals/adding-targets.md b/docs/Observer/Creating Proposals/adding-targets.md
similarity index 80%
rename from content/en/docs/Getting started/Creating Proposals/adding-targets.md
rename to docs/Observer/Creating Proposals/adding-targets.md
index 79cff7f..db1546b 100644
--- a/content/en/docs/Getting started/Creating Proposals/adding-targets.md
+++ b/docs/Observer/Creating Proposals/adding-targets.md
@@ -1,25 +1,14 @@
----
-title: Adding Targets
-date: 2024-03-04
-description: >
- _Guide to adding observational **Targets** to your proposal_
-categories: [Examples]
-tags: [test, sample, docs]
----
# Add a Target
A fresh proposal will have no **Targets** added, and you will be presented with the following page:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
](https://www.orp-h2020.eu)
+
+