| Re: [birt-dev] Website |
_______________________________________________Hi Wim !
I hope you are doing well… J
For your information I solved the edit issue and I can edit the web pages with the edit link at the bottom of each page. Next I will work on implementing the save functionality. Once this done I will be able to implement a blog…
For the moment I am waiting for the answer to my mail below as I would like to publish the new BIRT website.
Thank you in advance.
Best
Christophe
Von: birt-dev [mailto:birt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Loetz, Christophe
Gesendet: Donnerstag, 8. April 2021 09:39
An: For developers on the BIRT project
Betreff: Re: [birt-dev] Website
Hi Wim !
I agree on option 1. It was just meant as a quick workaround.
Option 3: As far as I can see, there is no migration path or tool from Docusaurus to Hugo. The *md files can't be easily migrated because of the different structures of both tools.
To migrate the BIRT website, I would have to learn Hugo first. At the moment this is not an option for me as it would take a larger amount of time.
After reading all available docs on the Eclipse webpages, I think we should proceed as follows in analogy to the Eclipse boilerplate procedure and finally deliver the pages where they should be. That’s how I managed the OSBP and OS.bea projects internet pages and it worked fine. Eclipse should be able to arrange the appropriate repos, etc.
Let’s host the development environment in a repo which is to be defined. Built pages shall be pushed to github’s BIRT-website as staging test environment (https://github.com/eclipse/birt-website). Once tested and green let’s push the pages to the production/life environment https://www.eclipse.org/birt/.
Best
Christophe
Von: birt-dev [mailto:birt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Wim Jongman
Gesendet: Mittwoch, 7. April 2021 11:26
An: For developers on the BIRT project
Betreff: Re: [birt-dev] Website
Option 1 sounds messy
Option 2 (a new repo) is a better alternative. Let me know when option 3 does not work.
Option 3: Hugo would be great. If we are lucky you only need to copy the MD sources.
I have worked extensively with the webmasters[1] and they have created a very simple process[2] that is working (I tested it[3]).
An added benefit is that this process enables:
- a local website for testing (also the case with docusaurus)
- a "staging" website that we can use to test before the changes go live. ( I am working on revamping the Eclipse Platform website with this technology:[3])
- hosted at https://eclipse.org/birt
- Can use the Solstice theme of the Eclipse foundation
More information about the process here:
[3] https://testuser:plaintext@staging.eclipse.org/eclipse
On Wed, Apr 7, 2021 at 8:44 AM Loetz, Christophe <ChLoetz@xxxxxxxxxxxxxxxxxxx> wrote:
Reading id=572631 I suggest the following
Option 1
Let’s keep ../birt-website as our root dir for the birt websit
I will move my dev env to the directory birt-website/development/…
And after building the static web pages in birt-website/development/build/
I will “copy” the /buid/… to birt-web-site.
Option 2
Let’s use two repos. One for the website: gh-pages/birt-website
And one for the dev env either in a new repo or as part of the birt sources repo.
Option 3
I will try to migrate my pages to Hugo and, if this was successful, then we can use the process described by Eclipse.
I will try option 3 and give a feedback if I succeeded or gout stuck, because I think that the closer we are to Eclipse’s processes the better it is.
OK?
Von: birt-dev [mailto:birt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Wim Jongman
Gesendet: Dienstag, 6. April 2021 19:10
An: For developers on the BIRT project
Betreff: Re: [birt-dev] Website
I created the main branch and filed: https://bugs.eclipse.org/bugs/show_bug.cgi?id=572631
On Tue, Apr 6, 2021 at 7:05 PM Wim Jongman <wim.jongman@xxxxxxxxx> wrote:
After re-reading [1] we should drop the gh-pages branch and use the main branch. Publish from main/build
On Tue, Apr 6, 2021 at 7:02 PM Wim Jongman <wim.jongman@xxxxxxxxx> wrote:
The webmasters have a process in place to copy a hugo website to the main site (e.g. https://eclipse.org/birt). That was one of the reasons why we were excited to use hugo.
The updated plan (after the engine switch to docusaurus) is to use https://eclipse.github.io/birt-website
Cheers,
Wim
On Tue, Apr 6, 2021 at 5:33 PM Loetz, Christophe <ChLoetz@xxxxxxxxxxxxxxxxxxx> wrote:
1. Already done. I pushed my current dev env to gh-pages. The /build is among others updated.
2. Where are the new birt home page going to be hosted? Currently it’s here: https://www.eclipse.org/birt/. Where shall it be for the new pages?
Shall the gh-pages replace https://www.eclipse.org/birt/ or shall I push the directories and files of /build to https://www.eclipse.org/birt/ or is another procedure to be respected? I remember that Wayne sent me some info, but I cleaned up my laptop over Easter…
Sorry, but I obviously have not understood where the new website will be hosted and how it’s is going to replace the present website and how the exact procedure from gh-pages to productive website repo or env shall work.
Concerning wiki respectively editing internet pages, I am working on the following PoC:
Von: birt-dev [mailto:birt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Wim Jongman
Gesendet: Dienstag, 6. April 2021 15:45
An: For developers on the BIRT project
Betreff: Re: [birt-dev] Website
I can ask this but then we have another repo to juggle. Maybe we can just keep everything as it is. Regenerate, and then just push the new /build contents. This should only push changed content.
WDYT?
On Tue, Apr 6, 2021 at 2:25 PM Loetz, Christophe <ChLoetz@xxxxxxxxxxxxxxxxxxx> wrote:
Hi Wim,
I just wanted to execute
1. Run static website creation
2. Copy /build to a temp directory
3. Switch to gh-pages branch
4. Push /build result into gh-pages branch
but as you asked for, I’ve already transfered my website development environment to eclipse/birt-website (github.com) gh-pages branch before you wrote the above mentioned lines. You can find in the sub dir /build the updated website pages.
If I now execute 1.-4. this will mix the dev environment with the runtime pages. I don’t think that this is a good solution.
Shouldn’t the dev environment and the runtime pages be in separate repos?
Best
Christophe
Von: birt-dev [mailto:birt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Wim Jongman
Gesendet: Sonntag, 4. April 2021 16:48
An: For developers on the BIRT project
Betreff: Re: [birt-dev] Website
Hi Christophe,
Please go ahead.
Cheers, Wim
On Sat, Apr 3, 2021, 5:47 PM Loetz, Christophe <ChLoetz@xxxxxxxxxxxxxxxxxxx> wrote:
@win:
Did you try to push the /build to gh-pages?
Or shall I try?
Von: birt-dev [mailto:birt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Loetz, Christophe
Gesendet: Mittwoch, 31. März 2021 09:23
An: For developers on the BIRT project
Betreff: Re: [birt-dev] Website
If it works it is fine with me J
Von: birt-dev [mailto:birt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Wim Jongman
Gesendet: Mittwoch, 31. März 2021 09:08
An: For developers on the BIRT project
Betreff: Re: [birt-dev] Website
Hi Christophe,
They do, however it means that we also have to check-in the ./build directory. I don't think this is wanted.
I think we can do the following when we pull changes into the website:
1. Run static website creation
2. Copy /build to a temp directory
3. Switch to gh-pages branch
4. Push /build result into gh-pages branch
WDYT?
Cheers,
Wim
On Wed, Mar 31, 2021 at 7:40 AM Loetz, Christophe <ChLoetz@xxxxxxxxxxxxxxxxxxx> wrote:
Hi Wim,
in addition to the mail below. By adapting the structure of the Eclipse’s website repo to my development environment, Eclipse would need to adapt github to set up ./build as a test website environment.
With thanks in advance.
Best regards
Christophe
Von: birt-dev [mailto:birt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Loetz, Christophe
Gesendet: Dienstag, 30. März 2021 18:31
An: For developers on the BIRT project
Betreff: Re: [birt-dev] Website
Hi Wim !
I pushed my dev env to eclipse/birt-website (github.com)
You can find the BIRT website pages in ./build
Please check if everything is OK so far.
Best
Christophe
Von: birt-dev [mailto:birt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Wim Jongman
Gesendet: Dienstag, 30. März 2021 10:52
An: For developers on the BIRT project
Betreff: Re: [birt-dev] Website
There is confusion :)
Your repository to ( chloetz (Christophe Loetz) (github.com) ) must be pushed to https://github.com/eclipse/birt-website -> main branch
Let's do this first. Then from there, we can figure out how to host the website.
Cheers,
Wim
On Tue, Mar 30, 2021 at 9:07 AM Loetz, Christophe <ChLoetz@xxxxxxxxxxxxxxxxxxx> wrote:
Maybe I misunderstood: Shall the root dir for the web page dev be: https://docs.github.com/en/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site ?
Or where exactly is the root dir, you meant for the web page development environment. You can have a look on my repo and see how I organized the web page dev. chloetz (Christophe Loetz) (github.com)
Von: birt-dev [mailto:birt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Wim Jongman
Gesendet: Dienstag, 30. März 2021 08:36
An: For developers on the BIRT project
Betreff: Re: [birt-dev] Website
Sorry, I don't understand :)
I think you just put the sources in the root and generate the static content in a "static" directory or something?
Cheers,
Wim
On Tue, Mar 30, 2021 at 6:10 AM Loetz, Christophe <ChLoetz@xxxxxxxxxxxxxxxxxxx> wrote:
OK.
I will put my sources into the directory you indicated (the name could’t have been shorter :) later on today.
Von: birt-dev [mailto:birt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Wim Jongman
Gesendet: Montag, 29. März 2021 23:45
An: For developers on the BIRT project
Betreff: Re: [birt-dev] Website
Christophe, the webmasters suggest putting all sources in this repository and generate the static content in a directory. Github Pages is able to publish from a directory:
On Sun, Mar 28, 2021 at 2:44 PM Loetz, Christophe <ChLoetz@xxxxxxxxxxxxxxxxxxx> wrote:
Hi Wim !
I do absolutely agree. I already asked the question before starting designing the new logo, but nobody answered. I took this as an OK.
From my point of view there are a couple of argument for the new logo:
1. The new logo marks the restart and make clear that everything is moving forward again with renewed vigor.
2. The logo symbolizes BI and reporting. An octagon has nothing to do with neither one.
3. The colors are modern (the pink of the octagon is old fashion)
4. The new logo works in normal and dark mode
5. The red “i” make clear that we are talking about BI (!) and reporting
I do also believe that somebody should revise my pages. I did my best regarding updating all info, but I am not an expert. I would also appreciate if a person of English mother tongue would revise my English.
Christophe
Von: birt-dev [mailto:birt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Wim Jongman
Gesendet: Sonntag, 28. März 2021 12:41
An: For developers on the BIRT project
Betreff: Re: [birt-dev] Website
Hi Christopher,
About the Logo. Shouldn't we ask the community for input before we decide on a new logo?
I suggest opening a separate thread about this topic. If you agree, could you start one?
Cheers,
Wim
_______________________________________________
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev_______________________________________________
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev_______________________________________________
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev_______________________________________________
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev_______________________________________________
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev_______________________________________________
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev_______________________________________________
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev_______________________________________________
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev
