For some reason I thought that the site code might also be in the GitHub mirror
of the main bloodhound.
Anyway, personally I would be happy enough to support moving the site to its
own repo and using pelican. Very good suggestions.
Cheers,
Gary
On 22/08/2023 03:19, Greg Stein wrote:
> Rather than using pure HTML/etc, I would suggest that we switch to using
> Pelican for site generation (sources move to markdown). Infra has provided
> an automated workflow to move edits to published pages. See:
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#Git.asf.yamlfeatures-PelicanCMS
>
> We can create a git repo named "bloodhound-site", and an edit/push of a .md
> file would publish the page within a few seconds.
>
> There are a few publishing options, but Pelican is straightforward,
> supported by Infra, and the tool is Python-based which is a "nice to have"
> for this community (to better understand the tooling).
>
> Thoughts?
>
> Cheers,
> -g
>
> On Mon, Aug 21, 2023 at 12:08 PM Greg Stein <[email protected]> wrote:
>
>
>> https://svn.apache.org/repos/asf/bloodhound/site/
>>
>> It is read-only, but I can override that to apply any patches you send to
>> dev@
>>
>> Cheers,
>> -g
>>
>> On Mon, Aug 21, 2023, 01:17 Daniel Brownridge <[email protected]>
>> wrote:
>>
>>
>>> Hi Gary,
>>>
>>> Untill we can get live back it might be a good idea tput some more basic
>>> info on the landing page and remove the dead links etc.
>>>
>>> How is the website (bloodhound.apache.org) hosted / updated / where does
>>> the code live?
>>>
>>> Happy to take on maintenance if that helps would just need some help
>>> getting started?
>>>
>>> If this can be done by email great but also can co-ordinate a time when
>>> both on-line if that helps?
>>>
>>> Cheers,
>>> Daniel
>>>
>>>
>> [snip]
>>
>
