[prev in list] [next in list] [prev in thread] [next in thread]
List: cassandra-dev
Subject: Re: Adding RSS feed to the Apache Cassandra website.
From: Benjamin Lerer <b.lerer () gmail ! com>
Date: 2022-06-01 8:18:59
Message-ID: CAAy+TbT=tVxeGHa7Tyb89H6L5V5U1c3CDVTnjrHbZpfVOXoN8Q () mail ! gmail ! com
[Download RAW message or body]
https://antora.zulipchat.com/#narrow/stream/282400-users/topic/ATOM.20or.20=
RSS.20feed/near/284393491
Le mar. 31 mai 2022 =C3=A0 21:59, lorinapoland <lorinapoland@gmail.com> a =
=C3=A9crit :
> I'm sure that someone has an rss feed Javascript that can just be added t=
o
> the antora-ui-docs, as Anthony is suggesting.
>
>
>
> Sent from my Verizon, Samsung Galaxy smartphone
>
>
> -------- Original message --------
> From: Ekaterina Dimitrova <e.dimitrova@gmail.com>
> Date: 5/31/22 09:37 (GMT-08:00)
> To: dev@cassandra.apache.org
> Subject: Re: Adding RSS feed to the Apache Cassandra website.
>
> +1 for option 2
>
> On Tue, 31 May 2022 at 12:21, Patrick McFadin <pmcfadin@gmail.com> wrote:
>
>> +1 on option 2. Anything that eliminates a human step is how it stays up
>> to date.
>>
>> On Tue, May 31, 2022 at 5:25 AM Brandon Williams <driftx@gmail.com>
>> wrote:
>>
>>> +1 to Anthony, that seems like the best path to me too.
>>>
>>> On Tue, May 31, 2022, 7:15 AM Anthony Grasso <anthony.grasso@gmail.com>
>>> wrote:
>>>
>>>> This is a good idea!
>>>>
>>>> I think option 2 is the best way to go. Currently, there are manual
>>>> steps involved to publish a post to the blog. I would like to avoid ad=
ding
>>>> more manual work.
>>>>
>>>> We could implement option 2 either by:
>>>>
>>>> - Bolting on JavaScript for Anotra to use to generate the RSS XML
>>>> - Adding a Python script that gets called (probably after the HTML
>>>> is generated) to generate the RSS XML
>>>>
>>>> The Python script would be the easiest to implement and maintain.
>>>>
>>>> Regards,
>>>>
>>>> On Tue, 31 May 2022 at 10:12, Erick Ramirez <erickramirezau@apache.org=
>
>>>> wrote:
>>>>
>>>>> Thanks for coordinating this. I'm happy to incorporate the manual
>>>>> process (option 1) in my workflow when reviewing/publishing blog PRs
>>>>> immediately as a quick solution if our intention is to go with option=
2.
>>>>>
>>>>> FWIW by "workflow" I mean step 6 of the Pipeline Overview documented
>>>>> in the wiki here -- https://cwiki.apache.org/confluence/x/-6rkCw.
>>>>> Cheers!
>>>>>
>>>>
[Attachment #3 (text/html)]
<div dir="ltr"><a href="https://antora.zulipchat.com/#narrow/stream/282400-users/topic \
/ATOM.20or.20RSS.20feed/near/284393491">https://antora.zulipchat.com/#narrow/stream/282400-users/topic/ATOM.20or.20RSS.20feed/near/284393491</a></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mar. 31 mai 2022 Ã 21:59, \
lorinapoland <<a href="mailto:lorinapoland@gmail.com">lorinapoland@gmail.com</a>> \
a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div \
dir="auto">I'm sure that someone has an rss feed Javascript that can just be \
added to the antora-ui-docs, as Anthony is suggesting. </div><div \
dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div \
id="gmail-m_6637675483518974953composer_signature" dir="auto"><div \
style="font-size:12px;color:rgb(87,87,87)" dir="auto">Sent from my Verizon, Samsung \
Galaxy smartphone</div></div><div dir="auto"><br></div><div><br></div><div dir="auto" \
style="font-size:100%;color:rgb(0,0,0)" align="left"><div>-------- Original message \
--------</div><div>From: Ekaterina Dimitrova <<a \
href="mailto:e.dimitrova@gmail.com" target="_blank">e.dimitrova@gmail.com</a>> \
</div><div>Date: 5/31/22 09:37 (GMT-08:00) </div><div>To: <a \
href="mailto:dev@cassandra.apache.org" target="_blank">dev@cassandra.apache.org</a> \
</div><div>Subject: Re: Adding RSS feed to the Apache Cassandra website. \
</div><div><br></div></div><div dir="auto">+1 for option 2</div><div><br><div \
class="gmail_quote"><div class="gmail_attr" dir="ltr">On Tue, 31 May 2022 at 12:21, \
Patrick McFadin <<a href="mailto:pmcfadin@gmail.com" \
target="_blank">pmcfadin@gmail.com</a>> wrote:<br></div><blockquote \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div dir="ltr">+1 on option 2. \
Anything that eliminates a human step is how it stays up to date. <br></div><br><div \
class="gmail_quote"><div class="gmail_attr" dir="ltr">On Tue, May 31, 2022 at 5:25 AM \
Brandon Williams <<a href="mailto:driftx@gmail.com" \
target="_blank">driftx@gmail.com</a>> wrote:<br></div><blockquote \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div dir="auto">+1 to Anthony, \
that seems like the best path to me too.</div><br><div class="gmail_quote"><div \
class="gmail_attr" dir="ltr">On Tue, May 31, 2022, 7:15 AM Anthony Grasso <<a \
href="mailto:anthony.grasso@gmail.com" \
target="_blank">anthony.grasso@gmail.com</a>> wrote:<br></div><blockquote \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div dir="ltr"><div>This is a \
good idea!<br></div><div><br></div><div>I think option 2 is the best way to go. \
Currently, there are manual steps involved to publish a post to the blog. I would \
like to avoid adding more manual work.</div><div><br></div><div>We could implement \
option 2 either by:</div><div><ul><li>Bolting on JavaScript for Anotra to use to \
generate the RSS XML</li><li>Adding a Python script that gets called (probably after \
the HTML is generated) to generate the RSS XML</li></ul><div>The Python script would \
be the easiest to implement and \
maintain.</div></div><div><br></div><div>Regards,</div></div><br><div \
class="gmail_quote"><div class="gmail_attr" dir="ltr">On Tue, 31 May 2022 at 10:12, \
Erick Ramirez <<a rel="noreferrer" href="mailto:erickramirezau@apache.org" \
target="_blank">erickramirezau@apache.org</a>> wrote:<br></div><blockquote \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div dir="ltr">Thanks for \
coordinating this. I'm happy to incorporate the manual process (option 1) in my \
workflow when reviewing/publishing blog PRs immediately as a quick solution if our \
intention is to go with option 2.<div><br></div><div>FWIW by "workflow" I \
mean step 6 of the Pipeline Overview documented in the wiki here -- <a \
rel="noreferrer" href="https://cwiki.apache.org/confluence/x/-6rkCw" \
target="_blank">https://cwiki.apache.org/confluence/x/-6rkCw</a>. Cheers!</div></div> \
</blockquote></div> </blockquote></div>
</blockquote></div>
</blockquote></div></div>
</div></blockquote></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic