Re: [DISCUSS] Create a new repo for website template
PR is ready - https://github.com/apache/apache-website-template/pull/19 I'll invest time to develop the Docu template in the next weeks. Best, tison. Zili Chen 于2024年2月26日周一 11:48写道： > > Go into the implementation stage. I plan to submit a patch for updating the > master branch this week. Welcome to leave your comment at - > https://github.com/apache/apache-website-template/issues/18. > > The Docu branch is under development; I'm going to create more wip issues for > you to follow. > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [DISCUSS] Create a new repo for website template
Go into the implementation stage. I plan to submit a patch for updating the master branch this week. Welcome to leave your comment at - https://github.com/apache/apache-website-template/issues/18. The Docu branch is under development; I'm going to create more wip issues for you to follow. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [DISCUSS] Create a new repo for website template
On Wed, Feb 21, 2024, 12:40 Christian Grobmeier wrote: > > On Wed, Feb 21, 2024, at 10:43, tison wrote: > > Hi Chris, > > > > Thanks you. Now we found a volunteer to improve the jekyll template and > > it's good :D > > Haha ok great, I will send a patch as suggested. I can also commit > directly if this repo is using CTR > Yep. Comdev in general is CTR.
Re: [DISCUSS] Create a new repo for website template
On Wed, Feb 21, 2024, at 10:43, tison wrote: > Hi Chris, > > Thanks you. Now we found a volunteer to improve the jekyll template and > it's good :D Haha ok great, I will send a patch as suggested. I can also commit directly if this repo is using CTR > > Daniel wrote: >> This feels like we are over-engineering the solution to a simple >> problem. Just use the existing website-template repository, have the >> default branch be an empty branch with a README that tells you what the >> different examples are, each in their own branch or directory. > > I'm OK with this. And it seems a solution that no direct reasonable > objection. > > Although Sebb comments in the other thread [1] that such a Rip Down commit > can be suboptimal due to the irrelevant history, with INFRA's help we can > use a brand new README branch and make it the default. > > I'm going to move forward with the development in docusaurus branch and > recommend Chris to send the patch against the jekyll branch (I'll review it > if you need). > > For the master branch tech solution, I'm fine to wait a minutes to rip it > down, switch with a brand new history, or any other suggestions. > > Best, > tison. > > [1] > https://lists.apache.org/thread/jjmb1jnl67rr5qnhdb047tms9ksd0yqq > > > Christian Grobmeier 于2024年2月21日 周三16:07写道： > >> Hello, >> >> I love we are picking up this template idea again. >> >> Previously I proposed to add some Docker files to help with quick setup. >> I could add this straightaway to the Jekyll branch. >> >> Does this sound like a good idea? >> >> It could look like what I did for Privacy: >> https://github.com/apache/privacy-website >> >> Please let me know, then I will add it (or forget about it) >> >> Kind regards, >> Christian >> >> On Tue, Feb 20, 2024, at 23:38, Willem Jiang wrote: >> > From my recent experience, it could save the developer lots of time if >> > they can work on the website's content by adding some markdown files >> > directly. >> > Following the website policy and turning the features of the website >> > engine are one-time work. The ROI would be good if we could share >> > these through the website template. >> > >> > Thanks, >> > >> > Willem Jiang >> > >> > On Tue, Feb 20, 2024 at 8:20 PM tison wrote: >> >> >> >> > And/or just point to the source code of existing ASF websites which >> >> > can serve as living examples. >> >> >> >> You can check the original mailing list thread [1]. I recommend Fury as >> an >> >> example there because it's just started. Living examples can be >> supplements >> >> but customized a lot to prevent new podlings from catching up. >> >> >> >> This is my initial motivation to create a template and even >> self-contained >> >> docs to share how to switch features while being compliant with ASF >> >> policies :D >> >> >> >> Best, >> >> tison. >> >> >> >> [1] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx >> >> >> >> >> >> Bertrand Delacretaz 于2024年2月20日周二 19:32写道： >> >> >> >> > On Tue, Feb 20, 2024 at 10:45 AM Daniel Gruno >> >> > wrote: >> >> > > ...Just use the existing website-template repository, have the >> >> > > default branch be an empty branch with a README that tells you what >> the >> >> > > different examples are, each in their own branch or directory... >> >> > >> >> > And/or just point to the source code of existing ASF websites which >> >> > can serve as living examples. >> >> > >> >> > And encourage people to add GitHub topics to their website >> >> > repositories, so that queries like >> >> > >> >> > >> https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories >> >> > >> >> > can give you a list of real live examples that use your favorite >> >> > website generation tool, "hugo" in this example. >> >> > >> >> > -Bertrand >> >> > >> >> > - >> >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> >> > For additional commands, e-mail: dev-h...@community.apache.org >> >> > >> >> > >> > >> > - >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> > For additional commands, e-mail: dev-h...@community.apache.org >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >> - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [DISCUSS] Create a new repo for website template
Hi On Wed, Feb 21, 2024, at 17:06, Dave Fisher wrote: > Hi Tison, > > Some future ideas. > > (1) The web templates - html, js, css, and fonts are likely to be > similar between the branches. (Well not all the js that docusaurus > produces, but the site design will be similar.) This could lead to a > branch with multiple designs. The question is what template language is > used by docusaurus and jekyl? JINJA2? Jekyll uses Liquid, Docusaurus uses a JSX like thing. I never used it, but it is basically a React application that is rendered to static files. I don’t think templates can be reused Kind regards Christian > > (2) Once those two examples are complete. I think that an ASF Pelican > example can be done as well. There are a number of examples like > apache.org, http.apache.org, etc. > > I’m following along and will have a look later on. > > Best, > Dave > >> On Feb 21, 2024, at 1:43 AM, tison wrote: >> >> Hi Chris, >> >> Thanks you. Now we found a volunteer to improve the jekyll template and >> it's good :D >> >> Daniel wrote: >>> This feels like we are over-engineering the solution to a simple >>> problem. Just use the existing website-template repository, have the >>> default branch be an empty branch with a README that tells you what the >>> different examples are, each in their own branch or directory. >> >> I'm OK with this. And it seems a solution that no direct reasonable >> objection. >> >> Although Sebb comments in the other thread [1] that such a Rip Down commit >> can be suboptimal due to the irrelevant history, with INFRA's help we can >> use a brand new README branch and make it the default. >> >> I'm going to move forward with the development in docusaurus branch and >> recommend Chris to send the patch against the jekyll branch (I'll review it >> if you need). >> >> For the master branch tech solution, I'm fine to wait a minutes to rip it >> down, switch with a brand new history, or any other suggestions. >> >> Best, >> tison. >> >> [1] >> https://lists.apache.org/thread/jjmb1jnl67rr5qnhdb047tms9ksd0yqq >> >> >> Christian Grobmeier 于2024年2月21日 周三16:07写道： >> >>> Hello, >>> >>> I love we are picking up this template idea again. >>> >>> Previously I proposed to add some Docker files to help with quick setup. >>> I could add this straightaway to the Jekyll branch. >>> >>> Does this sound like a good idea? >>> >>> It could look like what I did for Privacy: >>> https://github.com/apache/privacy-website >>> >>> Please let me know, then I will add it (or forget about it) >>> >>> Kind regards, >>> Christian >>> >>> On Tue, Feb 20, 2024, at 23:38, Willem Jiang wrote: From my recent experience, it could save the developer lots of time if they can work on the website's content by adding some markdown files directly. Following the website policy and turning the features of the website engine are one-time work. The ROI would be good if we could share these through the website template. Thanks, Willem Jiang On Tue, Feb 20, 2024 at 8:20 PM tison wrote: > >> And/or just point to the source code of existing ASF websites which >> can serve as living examples. > > You can check the original mailing list thread [1]. I recommend Fury as >>> an > example there because it's just started. Living examples can be >>> supplements > but customized a lot to prevent new podlings from catching up. > > This is my initial motivation to create a template and even >>> self-contained > docs to share how to switch features while being compliant with ASF > policies :D > > Best, > tison. > > [1] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx > > > Bertrand Delacretaz 于2024年2月20日周二 19:32写道： > >> On Tue, Feb 20, 2024 at 10:45 AM Daniel Gruno >> wrote: >>> ...Just use the existing website-template repository, have the >>> default branch be an empty branch with a README that tells you what >>> the >>> different examples are, each in their own branch or directory... >> >> And/or just point to the source code of existing ASF websites which >> can serve as living examples. >> >> And encourage people to add GitHub topics to their website >> repositories, so that queries like >> >> >>> https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories >> >> can give you a list of real live examples that use your favorite >> website generation tool, "hugo" in this example. >> >> -Bertrand >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >> - To unsubscribe, e-mail: dev-unsubscr...@community.a
Re: [DISCUSS] Create a new repo for website template
Hi Tison, Some future ideas. (1) The web templates - html, js, css, and fonts are likely to be similar between the branches. (Well not all the js that docusaurus produces, but the site design will be similar.) This could lead to a branch with multiple designs. The question is what template language is used by docusaurus and jekyl? JINJA2? (2) Once those two examples are complete. I think that an ASF Pelican example can be done as well. There are a number of examples like apache.org, http.apache.org, etc. I’m following along and will have a look later on. Best, Dave > On Feb 21, 2024, at 1:43 AM, tison wrote: > > Hi Chris, > > Thanks you. Now we found a volunteer to improve the jekyll template and > it's good :D > > Daniel wrote: >> This feels like we are over-engineering the solution to a simple >> problem. Just use the existing website-template repository, have the >> default branch be an empty branch with a README that tells you what the >> different examples are, each in their own branch or directory. > > I'm OK with this. And it seems a solution that no direct reasonable > objection. > > Although Sebb comments in the other thread [1] that such a Rip Down commit > can be suboptimal due to the irrelevant history, with INFRA's help we can > use a brand new README branch and make it the default. > > I'm going to move forward with the development in docusaurus branch and > recommend Chris to send the patch against the jekyll branch (I'll review it > if you need). > > For the master branch tech solution, I'm fine to wait a minutes to rip it > down, switch with a brand new history, or any other suggestions. > > Best, > tison. > > [1] > https://lists.apache.org/thread/jjmb1jnl67rr5qnhdb047tms9ksd0yqq > > > Christian Grobmeier 于2024年2月21日 周三16:07写道： > >> Hello, >> >> I love we are picking up this template idea again. >> >> Previously I proposed to add some Docker files to help with quick setup. >> I could add this straightaway to the Jekyll branch. >> >> Does this sound like a good idea? >> >> It could look like what I did for Privacy: >> https://github.com/apache/privacy-website >> >> Please let me know, then I will add it (or forget about it) >> >> Kind regards, >> Christian >> >> On Tue, Feb 20, 2024, at 23:38, Willem Jiang wrote: >>> From my recent experience, it could save the developer lots of time if >>> they can work on the website's content by adding some markdown files >>> directly. >>> Following the website policy and turning the features of the website >>> engine are one-time work. The ROI would be good if we could share >>> these through the website template. >>> >>> Thanks, >>> >>> Willem Jiang >>> >>> On Tue, Feb 20, 2024 at 8:20 PM tison wrote: > And/or just point to the source code of existing ASF websites which > can serve as living examples. You can check the original mailing list thread [1]. I recommend Fury as >> an example there because it's just started. Living examples can be >> supplements but customized a lot to prevent new podlings from catching up. This is my initial motivation to create a template and even >> self-contained docs to share how to switch features while being compliant with ASF policies :D Best, tison. [1] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx Bertrand Delacretaz 于2024年2月20日周二 19:32写道： > On Tue, Feb 20, 2024 at 10:45 AM Daniel Gruno > wrote: >> ...Just use the existing website-template repository, have the >> default branch be an empty branch with a README that tells you what >> the >> different examples are, each in their own branch or directory... > > And/or just point to the source code of existing ASF websites which > can serve as living examples. > > And encourage people to add GitHub topics to their website > repositories, so that queries like > > >> https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories > > can give you a list of real live examples that use your favorite > website generation tool, "hugo" in this example. > > -Bertrand > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > > >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >>> For additional commands, e-mail: dev-h...@community.apache.org >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >> - To unsubscribe, e-mail: dev-unsubscr...@community.a
Re: [DISCUSS] Create a new repo for website template
Hi Chris, Thanks you. Now we found a volunteer to improve the jekyll template and it's good :D Daniel wrote: > This feels like we are over-engineering the solution to a simple > problem. Just use the existing website-template repository, have the > default branch be an empty branch with a README that tells you what the > different examples are, each in their own branch or directory. I'm OK with this. And it seems a solution that no direct reasonable objection. Although Sebb comments in the other thread [1] that such a Rip Down commit can be suboptimal due to the irrelevant history, with INFRA's help we can use a brand new README branch and make it the default. I'm going to move forward with the development in docusaurus branch and recommend Chris to send the patch against the jekyll branch (I'll review it if you need). For the master branch tech solution, I'm fine to wait a minutes to rip it down, switch with a brand new history, or any other suggestions. Best, tison. [1] https://lists.apache.org/thread/jjmb1jnl67rr5qnhdb047tms9ksd0yqq Christian Grobmeier 于2024年2月21日 周三16:07写道： > Hello, > > I love we are picking up this template idea again. > > Previously I proposed to add some Docker files to help with quick setup. > I could add this straightaway to the Jekyll branch. > > Does this sound like a good idea? > > It could look like what I did for Privacy: > https://github.com/apache/privacy-website > > Please let me know, then I will add it (or forget about it) > > Kind regards, > Christian > > On Tue, Feb 20, 2024, at 23:38, Willem Jiang wrote: > > From my recent experience, it could save the developer lots of time if > > they can work on the website's content by adding some markdown files > > directly. > > Following the website policy and turning the features of the website > > engine are one-time work. The ROI would be good if we could share > > these through the website template. > > > > Thanks, > > > > Willem Jiang > > > > On Tue, Feb 20, 2024 at 8:20 PM tison wrote: > >> > >> > And/or just point to the source code of existing ASF websites which > >> > can serve as living examples. > >> > >> You can check the original mailing list thread [1]. I recommend Fury as > an > >> example there because it's just started. Living examples can be > supplements > >> but customized a lot to prevent new podlings from catching up. > >> > >> This is my initial motivation to create a template and even > self-contained > >> docs to share how to switch features while being compliant with ASF > >> policies :D > >> > >> Best, > >> tison. > >> > >> [1] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx > >> > >> > >> Bertrand Delacretaz 于2024年2月20日周二 19:32写道： > >> > >> > On Tue, Feb 20, 2024 at 10:45 AM Daniel Gruno > >> > wrote: > >> > > ...Just use the existing website-template repository, have the > >> > > default branch be an empty branch with a README that tells you what > the > >> > > different examples are, each in their own branch or directory... > >> > > >> > And/or just point to the source code of existing ASF websites which > >> > can serve as living examples. > >> > > >> > And encourage people to add GitHub topics to their website > >> > repositories, so that queries like > >> > > >> > > https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories > >> > > >> > can give you a list of real live examples that use your favorite > >> > website generation tool, "hugo" in this example. > >> > > >> > -Bertrand > >> > > >> > - > >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> > For additional commands, e-mail: dev-h...@community.apache.org > >> > > >> > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: [DISCUSS] Create a new repo for website template
Hello, I love we are picking up this template idea again. Previously I proposed to add some Docker files to help with quick setup. I could add this straightaway to the Jekyll branch. Does this sound like a good idea? It could look like what I did for Privacy: https://github.com/apache/privacy-website Please let me know, then I will add it (or forget about it) Kind regards, Christian On Tue, Feb 20, 2024, at 23:38, Willem Jiang wrote: > From my recent experience, it could save the developer lots of time if > they can work on the website's content by adding some markdown files > directly. > Following the website policy and turning the features of the website > engine are one-time work. The ROI would be good if we could share > these through the website template. > > Thanks, > > Willem Jiang > > On Tue, Feb 20, 2024 at 8:20 PM tison wrote: >> >> > And/or just point to the source code of existing ASF websites which >> > can serve as living examples. >> >> You can check the original mailing list thread [1]. I recommend Fury as an >> example there because it's just started. Living examples can be supplements >> but customized a lot to prevent new podlings from catching up. >> >> This is my initial motivation to create a template and even self-contained >> docs to share how to switch features while being compliant with ASF >> policies :D >> >> Best, >> tison. >> >> [1] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx >> >> >> Bertrand Delacretaz 于2024年2月20日周二 19:32写道： >> >> > On Tue, Feb 20, 2024 at 10:45 AM Daniel Gruno >> > wrote: >> > > ...Just use the existing website-template repository, have the >> > > default branch be an empty branch with a README that tells you what the >> > > different examples are, each in their own branch or directory... >> > >> > And/or just point to the source code of existing ASF websites which >> > can serve as living examples. >> > >> > And encourage people to add GitHub topics to their website >> > repositories, so that queries like >> > >> > https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories >> > >> > can give you a list of real live examples that use your favorite >> > website generation tool, "hugo" in this example. >> > >> > -Bertrand >> > >> > - >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> > For additional commands, e-mail: dev-h...@community.apache.org >> > >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [DISCUSS] Create a new repo for website template
>From my recent experience, it could save the developer lots of time if they can work on the website's content by adding some markdown files directly. Following the website policy and turning the features of the website engine are one-time work. The ROI would be good if we could share these through the website template. Thanks, Willem Jiang On Tue, Feb 20, 2024 at 8:20 PM tison wrote: > > > And/or just point to the source code of existing ASF websites which > > can serve as living examples. > > You can check the original mailing list thread [1]. I recommend Fury as an > example there because it's just started. Living examples can be supplements > but customized a lot to prevent new podlings from catching up. > > This is my initial motivation to create a template and even self-contained > docs to share how to switch features while being compliant with ASF > policies :D > > Best, > tison. > > [1] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx > > > Bertrand Delacretaz 于2024年2月20日周二 19:32写道： > > > On Tue, Feb 20, 2024 at 10:45 AM Daniel Gruno > > wrote: > > > ...Just use the existing website-template repository, have the > > > default branch be an empty branch with a README that tells you what the > > > different examples are, each in their own branch or directory... > > > > And/or just point to the source code of existing ASF websites which > > can serve as living examples. > > > > And encourage people to add GitHub topics to their website > > repositories, so that queries like > > > > https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories > > > > can give you a list of real live examples that use your favorite > > website generation tool, "hugo" in this example. > > > > -Bertrand > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [DISCUSS] Create a new repo for website template
> I don't want us to make people believe that there > is a preferred option for building websites. My two cents: 1. I'm very glad to list any wonderful sites as examples. 2. Take the existing template as an example; it mainly helps those projects/podlings who get lost in bootstrapping their website. If a project knows how to build a website, they don't go here. We can anyway add a note that the template is not _preferred_ but for getting started if you don't know how to start :D > The existing https://infra.apache.org/project-site.html page lists a > number of options, pointing to it could be useful, or we might suggest > simplifying that page to expose only what ASF infra manages, and move > the "website building options" to the comdev website. Hey! Thank you. Then I'm leaning to the solution reuse the apache-website-template repo, change the default branch a README only content to listing this. And it just happens to have some branches (jekyell, docusaurus) that have some content to get start with. Best, tison. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [DISCUSS] Create a new repo for website template
On Tue, Feb 20, 2024 at 1:20 PM tison wrote: > > > And/or just point to the source code of existing ASF websites which > > can serve as living examples. > > You can check the original mailing list thread [1]. I recommend Fury as an > example there because it's just started... The beauty of the ASF websites setup is that people can use any tool to build their website, as long as the output is static files, and there are many examples from our projects for the various tools. The existing https://infra.apache.org/project-site.html page lists a number of options, pointing to it could be useful, or we might suggest simplifying that page to expose only what ASF infra manages, and move the "website building options" to the comdev website. I am not against having a website template, but I don't think it's terribly useful and I don't want us to make people believe that there is a preferred option for building websites. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [DISCUSS] Create a new repo for website template
> And/or just point to the source code of existing ASF websites which > can serve as living examples. You can check the original mailing list thread [1]. I recommend Fury as an example there because it's just started. Living examples can be supplements but customized a lot to prevent new podlings from catching up. This is my initial motivation to create a template and even self-contained docs to share how to switch features while being compliant with ASF policies :D Best, tison. [1] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx Bertrand Delacretaz 于2024年2月20日周二 19:32写道： > On Tue, Feb 20, 2024 at 10:45 AM Daniel Gruno > wrote: > > ...Just use the existing website-template repository, have the > > default branch be an empty branch with a README that tells you what the > > different examples are, each in their own branch or directory... > > And/or just point to the source code of existing ASF websites which > can serve as living examples. > > And encourage people to add GitHub topics to their website > repositories, so that queries like > > https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories > > can give you a list of real live examples that use your favorite > website generation tool, "hugo" in this example. > > -Bertrand > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: [DISCUSS] Create a new repo for website template
On Tue, Feb 20, 2024 at 10:45 AM Daniel Gruno wrote: > ...Just use the existing website-template repository, have the > default branch be an empty branch with a README that tells you what the > different examples are, each in their own branch or directory... And/or just point to the source code of existing ASF websites which can serve as living examples. And encourage people to add GitHub topics to their website repositories, so that queries like https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories can give you a list of real live examples that use your favorite website generation tool, "hugo" in this example. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [DISCUSS] Create a new repo for website template
On 2/20/24 11:29, tison wrote: Hi Daniel, This is my original proposal. See "Reject Alternative" for more details. Sebb stated "Could perhaps be compared to changing from Java to Kotlin." This is a moot discussion. The repository serves as a static folder of various site templates. There is no reasonable argument to be made that anything needs to be preserved as is in perpetuity. Rip down the default branch, put in a readme, have examples in their own branches. We have a term at the ASF, and it's JFDI. I wish more people would practice it at times :) Or at least we let COMDEV PMC "own" apache/apache-website-template? My major object is to publish the docu template under ASF namespace, and not as a secondary source behind an unmaintained one, which is unreasonable. the apache-website-template is owned by "the foundation", and not a single project. If comdev wants to be the primary maintainer, it could be moved to maybe comdev-website-templayes, but there is nothing currently preventing you from treating the repository as a comdev repo. You (and everyone else at the ASF) have write access to it. Best, tison. Daniel Gruno 于2024年2月20日周二 17:45写道： On 2/20/24 10:34, tison wrote: ## Background ## More background can be found in [1][2]. The current website template [3] has not been updated for six years and uses outdated tech that can hardly be used for new podlings. I developed a new template[4], and it's been used for a few podlings already. All of them are glad to see this improvement. ## Proposal ## Create a new repo under COMDEV PMC to host the new website template. Such a template is mainly for new podlings setup but is also suitable for any TLPs. The name is to be determined. Following the self-serve rules, we can only create repo with comdev- prefix, so perhaps comdev-website-template. Or from why I create an INFRA ticket, apache/website-template-docusaurus, with INFRA's help. ## Reject Alternative ## 1. Create a new branch under apache/apache-website-template. It's discussed in [5][6] and doesn't seem a good direction. 2. Create a new repo under Incubator PMC. I'm hesitant about this, actually. But Andrew Wetmore wrote: This is not the purview of the Incubator, and it's not the purview of Infra. It's kind of reasonable, so I reached out here first. Best, tison. [1] https://issues.apache.org/jira/browse/INFRA-25494 [2] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx [3] https://github.com/apache/apache-website-template/ [4] github.com/tisonkun/apache-website-template/tree/docusaurus [5] https://issues.apache.org/jira/browse/INFRA-25486 [6] https://github.com/apache/apache-website-template/pull/17 This feels like we are over-engineering the solution to a simple problem. Just use the existing website-template repository, have the default branch be an empty branch with a README that tells you what the different examples are, each in their own branch or directory. The repository is meant to show examples, it's not being used in production or dynamically pulled in on other website builds, so breaking existing structures is perfectly reasonable. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [DISCUSS] Create a new repo for website template
Hi Daniel, This is my original proposal. See "Reject Alternative" for more details. Sebb stated "Could perhaps be compared to changing from Java to Kotlin." Or at least we let COMDEV PMC "own" apache/apache-website-template? My major object is to publish the docu template under ASF namespace, and not as a secondary source behind an unmaintained one, which is unreasonable. Best, tison. Daniel Gruno 于2024年2月20日周二 17:45写道： > On 2/20/24 10:34, tison wrote: > > ## Background ## > > > > More background can be found in [1][2]. The current website template [3] > > has not been updated for six years and uses outdated tech that can hardly > > be used for new podlings. > > > > I developed a new template[4], and it's been used for a few podlings > > already. All of them are glad to see this improvement. > > > > ## Proposal ## > > > > Create a new repo under COMDEV PMC to host the new website template. > Such a > > template is mainly for new podlings setup but is also suitable for any > TLPs. > > > > The name is to be determined. Following the self-serve rules, we can only > > create repo with comdev- prefix, so perhaps comdev-website-template. > > > > Or from why I create an INFRA ticket, apache/website-template-docusaurus, > > with INFRA's help. > > > > ## Reject Alternative ## > > > > 1. Create a new branch under apache/apache-website-template. > > It's discussed in [5][6] and doesn't seem a good direction. > > > > 2. Create a new repo under Incubator PMC. > > I'm hesitant about this, actually. But Andrew Wetmore wrote: > > > >> This is not the purview of the Incubator, and it's not the purview of > > Infra. > > > > It's kind of reasonable, so I reached out here first. > > > > Best, > > tison. > > > > [1] https://issues.apache.org/jira/browse/INFRA-25494 > > [2] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx > > [3] https://github.com/apache/apache-website-template/ > > [4] github.com/tisonkun/apache-website-template/tree/docusaurus > > [5] https://issues.apache.org/jira/browse/INFRA-25486 > > [6] https://github.com/apache/apache-website-template/pull/17 > > > > This feels like we are over-engineering the solution to a simple > problem. Just use the existing website-template repository, have the > default branch be an empty branch with a README that tells you what the > different examples are, each in their own branch or directory. > > The repository is meant to show examples, it's not being used in > production or dynamically pulled in on other website builds, so breaking > existing structures is perfectly reasonable. > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: [DISCUSS] Create a new repo for website template
On 2/20/24 10:34, tison wrote: ## Background ## More background can be found in [1][2]. The current website template [3] has not been updated for six years and uses outdated tech that can hardly be used for new podlings. I developed a new template[4], and it's been used for a few podlings already. All of them are glad to see this improvement. ## Proposal ## Create a new repo under COMDEV PMC to host the new website template. Such a template is mainly for new podlings setup but is also suitable for any TLPs. The name is to be determined. Following the self-serve rules, we can only create repo with comdev- prefix, so perhaps comdev-website-template. Or from why I create an INFRA ticket, apache/website-template-docusaurus, with INFRA's help. ## Reject Alternative ## 1. Create a new branch under apache/apache-website-template. It's discussed in [5][6] and doesn't seem a good direction. 2. Create a new repo under Incubator PMC. I'm hesitant about this, actually. But Andrew Wetmore wrote: This is not the purview of the Incubator, and it's not the purview of Infra. It's kind of reasonable, so I reached out here first. Best, tison. [1] https://issues.apache.org/jira/browse/INFRA-25494 [2] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx [3] https://github.com/apache/apache-website-template/ [4] github.com/tisonkun/apache-website-template/tree/docusaurus [5] https://issues.apache.org/jira/browse/INFRA-25486 [6] https://github.com/apache/apache-website-template/pull/17 This feels like we are over-engineering the solution to a simple problem. Just use the existing website-template repository, have the default branch be an empty branch with a README that tells you what the different examples are, each in their own branch or directory. The repository is meant to show examples, it's not being used in production or dynamically pulled in on other website builds, so breaking existing structures is perfectly reasonable. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[DISCUSS] Create a new repo for website template
## Background ## More background can be found in [1][2]. The current website template [3] has not been updated for six years and uses outdated tech that can hardly be used for new podlings. I developed a new template[4], and it's been used for a few podlings already. All of them are glad to see this improvement. ## Proposal ## Create a new repo under COMDEV PMC to host the new website template. Such a template is mainly for new podlings setup but is also suitable for any TLPs. The name is to be determined. Following the self-serve rules, we can only create repo with comdev- prefix, so perhaps comdev-website-template. Or from why I create an INFRA ticket, apache/website-template-docusaurus, with INFRA's help. ## Reject Alternative ## 1. Create a new branch under apache/apache-website-template. It's discussed in [5][6] and doesn't seem a good direction. 2. Create a new repo under Incubator PMC. I'm hesitant about this, actually. But Andrew Wetmore wrote: > This is not the purview of the Incubator, and it's not the purview of Infra. It's kind of reasonable, so I reached out here first. Best, tison. [1] https://issues.apache.org/jira/browse/INFRA-25494 [2] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx [3] https://github.com/apache/apache-website-template/ [4] github.com/tisonkun/apache-website-template/tree/docusaurus [5] https://issues.apache.org/jira/browse/INFRA-25486 [6] https://github.com/apache/apache-website-template/pull/17
