Create website
Background
We will use Gitlab.com capabilities to create the website with pages.
Task description
Technical tasks
Execute at least the following technical tasks:
-
Choose a static website generator -
Use GitLab Pages to host a website based on the contents of this repo at https://buildstream.gitlab.io/website/ -
Configure buildstream.build
domain to point to https://buildstream.gitlab.io/website/ -
Configure a certificate for encrypted communication using Let's Encrypt for buildstream.build
-
Base the design from pelican -
Evaluate the changes introduced by @foobarzz in his web and trustable web
-
-
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.
-
Add license.md file to the website repo. Extract the license from the official CC page -
Fix post broken links -
Evaluate the following potential changes - Justify the text on both sides.
- Reduce the difference in size between titles of section and paragraph font.
-
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:
-
Create the sitemap. -
Create the following pages, based on the proposal to the mailing list -
Home page: #12 (closed) -
Project page: #11 -
Portfolio page (Landing page): #3 (closed) -
Feature page: #1 (closed) -
BuildStream in detail: #5 -
Installation and deployment page: #16 (closed) -
BuildStream glossary: #6 -
Known issues page: #4 (closed) -
Download page: #2 (closed) -
FAQ: #7 (closed) -
Roadmap page: #13 -
Release announcement: #17 (closed) -
Wiki home page: #20 -
Meetings and events: this will be for now the wiki page.
-
-
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):
-
Home page: @toscalix and -
Project page: @toscalix and @Qinusty -
Portfolio page (Landing page): @toscalix and @tristanvb -
Feature page: @valentindavid and -
BuildStream in detail: @tristanvb and @valentindavid -
Installation and deployment page: @valentindavid and @tacgomes -
BuildStream glossary: @Qinusty and -
Known issues page:@valentindavid and -
Download page: @tacgomes and @Qinusty -
FAQ: @tristanvb and @tacgomes and @Qinusty -
Roadmap page: @toscalix and @tristanvb -
Release announcement: @toscalix -
Wiki home page
Check this Markdown guide to better understand about the content format we would like to have:
- Guide
- Guide source:the guide was done in markdown
Design
-
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
Edited by toscalix