## Background We will use Gitlab.com capabilities to create the website with pages. ## Task description ### Technical tasks Execute at least the following technical tasks: * [x] Choose a static website generator * [x] Use GitLab Pages to host a website based on the contents of this repo at https://buildstream.gitlab.io/website/ * [x] Configure `buildstream.build` domain to point to https://buildstream.gitlab.io/website/ * [x] Configure a certificate for encrypted communication using Let's Encrypt for `buildstream.build` * [x] Base the design from pelican * [x] Evaluate the changes introduced by @foobarzz in [his web](https://www.devcurmudgeon.com) and [trustable web](https://www.trustable.io) * [x] Can we create ToC with Pelican? * If yes, how? * If no, can we install a plugin? If not, we should use HTML syntax for titles. * [x] Add license.md file to the website repo. Extract the license from the official [CC page](https://creativecommons.org/2014/01/07/plaintext-versions-of-creative-commons-4-0-licenses/) * [x] Fix post broken links * [x] Evaluate the following potential changes * Justify the text on both sides. * Reduce the difference in size between titles of section and paragraph font. * [x] Make sure the domain works with www and https these tasks are led by @tacgomes ### Pages creation These tasks are related with the creation of the structure and the pages that will be published on the website for the BuildStream 1.2 release: * [x] Create the sitemap. * [ ] Create the following pages, based on the proposal to the mailing list * [x] Home page: #12 * [x] Project page: #11 * [x] Portfolio page (Landing page): #3 * [x] Feature page: #1 * [x] BuildStream in detail: #5 * [x] Installation and deployment page: #16 * [x] BuildStream glossary: #6 * [x] Known issues page: #4 * [x] Download page: #2 * [x] FAQ: #7 * [ ] Roadmap page: #13 * [x] Release announcement: #17 * [x] Wiki home page: #20 * [x] Meetings and events: this will be for now the [wiki page](https://wiki.gnome.org/Projects/BuildStream/Monthly-Meeting). * [x] List of redirections Theses tasks are led by @toscalix ### Content These tasks refer to actual content creation on each page that has been previously created and structured. The content that should be created is (lead person - help): * [x] Home page: @toscalix and * [x] Project page: @toscalix and @Qinusty * [x] Portfolio page (Landing page): @toscalix and @tristanvb * [x] Feature page: @valentindavid and * [ ] BuildStream in detail: @tristanvb and @valentindavid * [x] Installation and deployment page: @valentindavid and @tacgomes * [ ] BuildStream glossary: @Qinusty and * [ ] Known issues page:@valentindavid and * [x] Download page: @tacgomes and @Qinusty * [x] FAQ: @tristanvb and @tacgomes and @Qinusty * [ ] Roadmap page: @toscalix and @tristanvb * [x] Release announcement: @toscalix * [x] Wiki home page Check this Markdown guide to better understand about the content format we would like to have: * [Guide](https://daringfireball.net/projects/markdown/syntax) * [Guide source](https://daringfireball.net/projects/markdown/syntax.text):the guide was done in markdown ### Design * [x] Substitute the top banner message from BuildStream to BuildStream, the software integration tool. * The word software can be erased in the near future, once we get more popular. Sadly build is confused with construction industry. ## Acceptance Criteria * Link to the sitemap: * Link to the following pages: * Home page: * Project page: * Portfolio page (Landing page): * Feature page: * BuildStream in detail: * Installation and deployment page: * BuildStream glossary: * Known issues page: * Download page: * FAQ: * Roadmap page: * Release announcement: * Wiki home page ----