Dear community,

I just merged PR 27 into branch “docusaurus” as the checks went green in 
preparation of relaunching our new project site. We didn’t switch to the new 
CMS since the vote is running, but nevertheless the community needs to have the 
time and code to check the new setup.

You can now simply checkout the website repo [1] and switch to the branch 
“docusuarus” locally:

`git checkout docusaurus` 

And fire up `yarn` followed by `yarn start` to have a local environment. 

Structure:
- the main page is in src/pages.index.tsx
        - submodules (the three boxes + coloring) in components/HomepageFeatures
- the navbar is defined by /docusaurus.config.ts
- the content is under /docs:
        - community -> project information, orga and how to contribute etc
        - guide -> documentation
        - introduction -> about the project, high-level info
        - start -> download wayang 
- the blog is under /blog
        - self-ordering, add blogposts according to the example one: 
YYYY-MM-DD-name-of-the blog

Adding new pages always needs a header, like this:

---
id: download
title: Download Apache Wayang
sidebar_position: 1
—

id -> page-slug, needed to reference in other pages when content should be 
linked to each other
title -> the H1 title as default, can be overwritten by ## Better Title 
sidebar -> defines the position on the sidebar 

Deliver content in .md files in the normal markup definition. They show up well 
formatted. I take the initial maintainer role the the webpage, would love when 
we find another one who takes that together with me. PR’s need than approval 
from the maintainer team.

—alex

[1] https://github.com/apache/incubator-wayang-website


-- 
databloom AI, Inc.  

3401 N. MIAMI AVE. STE 230
33127 Miami, Florida 
United States


--  Please consider the environment before printing this 
email --



Disclaimer:
The content of this message is confidential. If you 
have received it by mistake, please inform us by an email reply and then 
delete the message. It is forbidden to copy, forward, or in any way reveal 
the contents of this message to anyone. The integrity and security of this 
email cannot be guaranteed over the Internet. Therefore, the sender will 
not be held liable for any damage caused by the message.

Reply via email to