That should be the territory where committers deal with their websites.
>>>> Enabled GitHub Issues for the project? Edit `support.adoc` in the `main`
>>>> branch. Is there a typo in the "Getting Started" page? Edit
>>>> `getting-started.adoc` i
ody just needs to spearhead this effort
>> and put a handful of strongly-opinionated guys on the same page.
>>
>> *Saving the day*
>>
>> Do you just want to save the day? Go ahead, JBake and AsciiDoc are a great
>> combo. People will appreciate it. It will c
will
>>> enable the committers to stop worrying about the website and its
>>> intricacies once and for all. As a bonus, Logging Services will have a one
>>> uniform beautifully-dressed look to the outside world where they can
>>> navigate with ease. The good news
vigate with ease. The good news is, the tooling is there and it is called
>> Antora <https://antora.org/>. Somebody just needs to spearhead this effort
>> and put a handful of strongly-opinionated guys on the same page.
>>
>> *Saving the day*
>>
>>
eier
> wrote:
>
>> Hello,
>>
>> the current landing page:
>> https://logging.apache.org/
>>
>> is done with JBake. We have rather complicated instructions on how to
>> re-generate the landing page:
>>
>> https://cwiki.apache.org/conf
plicated instructions on how to
> re-generate the landing page:
>
> https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Sites
>
> The Infra team recommends Pelican or Jekyll to create these kinds of
> pages. I have in-depth knowledge of Jekyll and would like to
>> I understand you don't like static site generators, but in this case, a
>>>>> less frequently updated website, I see benefits: easy blogging support
>>>>> and ASF support. Additionally, Docker support.
>>>>>
>>>>> The
ooling because I like Jekyll better, but because it
>>>> is a standard, I have autodeploy tools ready and it generally is better
>>>> understood than JBake.
>>>>
>>>> Kind regards,
>>>> Christian
>>>>
>>>>
&
cause I like Jekyll better, but because it
>>> is a standard, I have autodeploy tools ready and it generally is better
>>> understood than JBake.
>>>
>>> Kind regards,
>>> Christian
>>>
>>>
>>>>
>>>> Ralph
>
>> Kind regards,
>> Christian
>>
>>
>>>
>>> Ralph
>>>
>>>>> On Sep 22, 2023, at 11:47 AM, Christian Grobmeier
>>>>> wrote:
>>>>
>>>> Hello,
>>>>
>>>> the curren
rg> wrote:
> >>>
> >>> Hello,
> >>>
> >>> the current landing page:
> >>> https://logging.apache.org/
> >>>
> >>> is done with JBake. We have rather complicated instructions on how to
> re-generate the landi
>>> the current landing page:
>>> https://logging.apache.org/
>>>
>>> is done with JBake. We have rather complicated instructions on how to
>>> re-generate the landing page:
>>> https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Loggin
nerate the landing page:
>> https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Sites
>>
>> The Infra team recommends Pelican or Jekyll to create these kinds of pages.
>> I have in-depth knowledge of Jekyll and would like to propose migrat
he.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Sites
>
> The Infra team recommends Pelican or Jekyll to create these kinds of pages. I
> have in-depth knowledge of Jekyll and would like to propose migrating the
> current landing page to Jekyll.
>
> The b
> have in-depth knowledge of Jekyll and would like to propose migrating the
> current landing page to Jekyll.
>
> The benefits:
>
> - autodeploy of our changes
> - great support of blogging (I'd like to create one)
> - easy handling and supported by Infra
> - writing con
or Jekyll to create these kinds of pages. I
have in-depth knowledge of Jekyll and would like to propose migrating the
current landing page to Jekyll.
The benefits:
- autodeploy of our changes
- great support of blogging (I'd like to create one)
- easy handling and supported by Infra
- writing content
16 matches
Mail list logo
