Re: [birt-dev] Website

[Wim Jongman <wim.jongman@xxxxxxxxx>]

Editing pages with Docusaurus sounds like a complicated workflow. Let me know when we can look at a prototype. Alternatively, we just edit the MD documents directly.

Regarding the extra repo. I think we should just push the static content to the gh-pages branch. Then after accepting the PR, we can sync the gh-pages branch with the eclipse website.

We must make sure that search engines will not index the "github.io" content.

Workflow:

1. People make PR

2. Github action runs and publishes to gh-pages brancg

3. PR is approved, main branch is updated

4. Static content pushed to Eclipse website

On Mon, Apr 12, 2021 at 7:47 PM Loetz, Christophe <ChLoetz@xxxxxxxxxxxxxxxxxxx> wrote:

Hi Wim,

 

Yes I confirm.

 

For the moment I implemented following possibilities:

 

The web-server which hosts the website contains the static web pages as wells as the corresponding md.files which are either located in git/github or in a distinct directory on the website. Clicking on the “Edit this page” link on a web page calls a md editor. If php is activate on the website you can edit the md.file and submit it either to git/gihub or back to is directory from where it was loaded. If there is no php available the md.file can be locally downloaded, edited and from there pushed to git/github again. Github has two roles it’s a repo and a webserver.

 

That’s what I tried to show in the graphic below:

 

In short: local development with git. If there are more than one person working on the website the md-files are to be merged and versioned with github. The deployment and life-test is don on a staged website. If everything is ok the result is deployed to the life website.

 

I hope that my explanation was understandable. Don’t hesitate to ask any question.

 

Best

Christophe

_______________________________________________
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev