| Re: [birt-dev] Website |
No problem you can have look at any time. Besides this, I think we should have a phone call, because there are misunderstandings on the way. Docusaurus works like hugo. The process I described is nothing else then the process eclipse describes in the pages you indicated. The process you now proposed is the one I proposed at the beginning. Here what I originally proposed: Let’s save (commit and push) the sources of the website without the content in a sub dir of BIRT e.g.: ./website/… Publish the static website and md-files for acceptance to the existing github birt/website repo, once accepted sync the gh-pages with https://www.eclipse.org/birt/. The md-files can be downloaded (pulled) from der gh-pages, edited, the website rebuilded and pushed to the gh-pages…. So far OK? Von: birt-dev [mailto:birt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Wim Jongman 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:
|
