Re: [discussion] Website - information on supported versions

think it would be worth of exploring. (1) https://dist.apache.org/repos/dist/release/cassandra/ From: Tibor Répási Sent: Tuesday, January 31, 2023 12:52 To: dev@cassandra.apache.org Subject: Re: [discussion] Website - information on supported versions

Re: [discussion] Website - information on supported versions

providing these information authoritatively and participate on endoflife.date. Nevertheless, the main issues are * Cassandra’s release process should automatically update that information * the website should be auto-generated using that * some kind of Grafana integration would be appreciated

Re: [discussion] Website - information on supported versions

From: Tibor Répási Sent: Tuesday, January 31, 2023 11:56 To: dev@cassandra.apache.org Subject: [discussion] Website - information on supported versions NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the

[discussion] Website - information on supported versions

Hy Everyone, I was thinking about the information available on https://cassandra.apache.org/_/download.html about current and former releases, release dates, supported and unsupported versions of Apache Cassandra. These information are all availab

Re: Website fixes PR

fixes for the website dev documentation: > > https://github.com/apache/cassandra-website/pull/179 > > I've tested these locally using the docker scripts, although antora seems > to create broken links and navigation (confirmed this behavior even without > my commit). I was told

Website fixes PR

I put together some minor fixes for the website dev documentation: https://github.com/apache/cassandra-website/pull/179 I've tested these locally using the docker scripts, although antora seems to create broken links and navigation (confirmed this behavior even without my commit). I was

Re: [jira] [Created] (CASSANDRA-17761) WEBSITE - June 2022 blog "Apache Cassandra 4.1 Features: Pluggable Memtable Implementations"

Unsubscribe On Wed, Jul 20, 2022, 01:03 Diogenese Topper (Jira) wrote: > Diogenese Topper created CASSANDRA-17761: > > > Summary: WEBSITE - June 2022 blog "Apache Cassandra 4.1 > Features: Pluggable Memt

Re: [jira] [Updated] (CASSANDRA-17761) WEBSITE - July 2022 blog "Apache Cassandra 4.1 Features: Pluggable Memtable Implementations"

ed CASSANDRA-17761: > - > Summary: WEBSITE - July 2022 blog "Apache Cassandra 4.1 Features: > Pluggable Memtable Implementations" (was: WEBSITE - June 2022 blog "Apache > Cassandra 4.1 Features: Pluggable Memtable Implementations") > > > WEBSITE - July 202

Cassandra website update: Ecosystem page

y you think should be included, please forward me the necessary information and they can be included in the next website pull request (include the addition's title, link, description, and ecosystem section that it belongs in). I plan to have a pull request with the changes submitted *no later th

Re: Adding RSS feed to the Apache Cassandra website.

gt; > > Sent from my Verizon, Samsung Galaxy smartphone > > > Original message > From: Ekaterina Dimitrova > 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

Re: Adding RSS feed to the Apache Cassandra website.

e.org Subject: Re: Adding RSS feed to the Apache Cassandra website. +1 for option 2On Tue, 31 May 2022 at 12:21, Patrick McFadin 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 wrote:+1 to Anthony, that

Re: Adding RSS feed to the Apache Cassandra website.

+1 for option 2 On Tue, 31 May 2022 at 12:21, Patrick McFadin 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 wrote: > >> +1 to Anthony, that seems like the best path to me too. >> >> On Tue, May 3

Re: Adding RSS feed to the Apache Cassandra website.

+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 wrote: > +1 to Anthony, that seems like the best path to me too. > > On Tue, May 31, 2022, 7:15 AM Anthony Grasso > wrote: > >> This is a good idea! >> >> I think o

Re: Adding RSS feed to the Apache Cassandra website.

+1 to Anthony, that seems like the best path to me too. On Tue, May 31, 2022, 7:15 AM Anthony Grasso 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 adding more > manual wo

Re: Adding RSS feed to the Apache Cassandra website.

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 adding more manual work. We could implement option 2 either by: - Bolting on JavaScript for Anotra to use to generate the RSS XML - A

Re: Adding RSS feed to the Apache Cassandra website.

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 -- h

Re: Adding RSS feed to the Apache Cassandra website.

Nice initiative! All options look good to me in this preference order: 2, 1, 3. Em seg., 30 de mai. de 2022 às 06:34, Benjamin Lerer escreveu: > Hi everybody, > > Chris has been looking with the web design team about adding an RSS feed > to our website. Unfortunately th

Adding RSS feed to the Apache Cassandra website.

Hi everybody, Chris has been looking with the web design team about adding an RSS feed to our website. Unfortunately there are some complications due to Antora. We currently have 3 options: 1. Have an XML file on the site that can get updated manually whenever a new blog post gets added. As we

Re: [GitHub] [cassandra-website] ossarga commented on a diff in pull request #121: move and prepare files for content folder

I just did the same for cassandra-accord, I guess some config was lost in the upgrade https://issues.apache.org/jira/projects/INFRA/issues/INFRA-23074 From: Mick Semb Wever Date: Monday, 4 April 2022 at 08:55 To: dev@cassandra.apache.org Subject: Re: [GitHub] [cassandra-website] ossarga

Re: [GitHub] [cassandra-website] ossarga commented on a diff in pull request #121: move and prepare files for content folder

these notifications should be going to pr@ have created https://issues.apache.org/jira/browse/INFRA-23073 On Mon, 4 Apr 2022 at 03:09, GitBox wrote: > > ossarga commented on code in PR #121: > URL: > https://github.com/apache/cassandra-website/pull/121#discussio

[GitHub] [cassandra-website] ossarga commented on a diff in pull request #121: move and prepare files for content folder

ossarga commented on code in PR #121: URL: https://github.com/apache/cassandra-website/pull/121#discussion_r841307849 ## site-content/docker-entrypoint.sh: ## @@ -241,10 +314,41 @@ run_preview_mode() { } +log_level_str_to_int() { + local log_level_int + case $1 in

[GitHub] [cassandra-website] ossarga commented on a diff in pull request #121: move and prepare files for content folder

ossarga commented on code in PR #121: URL: https://github.com/apache/cassandra-website/pull/121#discussion_r841307662 ## site-content/docker-entrypoint.sh: ## @@ -196,14 +196,87 @@ generate_site_yaml() { render_site_content_to_html() { pushd "${CASSANDRA_WEBSITE_DIR}

Antora built cassandra-website about to be merged (Was: Switching the website to a temporary static html version of the new design)

On 2021/04/21 21:24:03, Mick Semb Wever wrote: > tl;dr Can we switch the website over to a temporary static-html > version of the new design, while work on the final antora generated > version continues? > https://cassandra.staged.apache.org/ > The antora build (by Antho

Re: Switching the website to a temporary static html version of the new design

Thank you Mick et al! If you have feedback on the new site, please let us know here or on Slack and we will address. On Mon, Apr 26, 2021 at 8:50 AM Michael Semb Wever wrote: > > > > tl;dr Can we switch the website over to a temporary static-html > > version of the new des

Re: Switching the website to a temporary static html version of the new design

> tl;dr Can we switch the website over to a temporary static-html > version of the new design, while work on the final antora generated > version continues? done. - To unsubscribe, e-mail: dev

Re: Switching the website to a temporary static html version of the new design

> is this version of the web page already "analytics friendly"? In the > context of https://plausible.cassandra.apache.org/cassandra.apache.org It is! it is still getting hacked in, but it will soon be formally part of the design and we

Re: Switching the website to a temporary static html version of the new design

Hi, is this version of the web page already "analytics friendly"? In the context of https://plausible.cassandra.apache.org/cassandra.apache.org On Sun, 25 Apr 2021 at 13:44, Michael Semb Wever wrote: > > > > As a risk mitigator, I was hoping we could preserve > > the sub-URIs so the switch doesn

Re: Switching the website to a temporary static html version of the new design

> As a risk mitigator, I was hoping we could preserve > the sub-URIs so the switch doesn't impact current users: > - make sure /doc/3.11/ (and other supported versions) still works > - rename /doc/latest/ to /doc/4.0/ but pointing to the existing version of > the site just to be sure we have a wo

Re: Switching the website to a temporary static html version of the new design

If we're moving to it eventually I don't see any reason we can't test in production now. +1 On Wed, Apr 21, 2021 at 4:24 PM Mick Semb Wever wrote: > > tl;dr Can we switch the website over to a temporary static-html > version of the new design, while work on the final an

Re: Switching the website to a temporary static html version of the new design

; on the antora version will be completed. And in the unthinkable and > improbable situation where it doesn't we can always roll back to the > current website. > I'm a +1 to the switch. As a risk mitigator, I was hoping we could preserve the sub-URIs so the switch doesn't

Re: Switching the website to a temporary static html version of the new design

> tl;dr Can we switch the website over to a temporary static-html > version of the new design, while work on the final antora generated > version continues? > https://cassandra.staged.apache.org/ FTR i'm +1 to make the switch (early next week). Generally, this would make

Re: Switching the website to a temporary static html version of the new design

Considering the time it is taking to release 4.0, I believe that any sign that shows that the project is still alive is nice to have. So I would be in favor of temporarily using a static-html version of the new design. As I am not much involved in the website, I would not be the most impacted by

Switching the website to a temporary static html version of the new design

tl;dr Can we switch the website over to a temporary static-html version of the new design, while work on the final antora generated version continues? https://cassandra.staged.apache.org/ In February a preview of the new website was announced¹. Melissa Logan and co have been working hard at

Re: Project website analytics

Nice. :-) Le jeu. 25 mars 2021 à 11:14, Mick Semb Wever a écrit : > Plausible tracking is currently (temporarily) enabled on every html page on > both the live and staged website. > > Website statistics are public at > https://plausible.cassandra.apache.org/cassandra.apache.org?period=realtime >

Re: Project website analytics

Plausible tracking is currently (temporarily) enabled on every html page on both the live and staged website. Website statistics are public at https://plausible.cassandra.apache.org/cassandra.apache.org?period=realtime

Re: Project website analytics

Excited to have this capability! Lorina Poland On Thu, Mar 11, 2021 at 6:16 AM Berenguer Blasi wrote: > Thx a lot indeed! > > On 11/3/21 14:59, Benjamin Lerer wrote: > > Thanks a lot to Stefan, Mick and Instaclustr. :-) > > > > On Wed, Mar 10, 2021 at 2:28 PM Mick Semb Wever wrote: > > > >>

Re: Project website analytics

Thx a lot indeed! On 11/3/21 14:59, Benjamin Lerer wrote: > Thanks a lot to Stefan, Mick and Instaclustr. :-) > > On Wed, Mar 10, 2021 at 2:28 PM Mick Semb Wever wrote: > >>> >>> The box this service runs at is donated by Instaclustr, we are glad to >>> help! >>> >> >> This is really awesome of y

Re: Project website analytics

Thanks a lot to Stefan, Mick and Instaclustr. :-) On Wed, Mar 10, 2021 at 2:28 PM Mick Semb Wever wrote: > > > > > > The box this service runs at is donated by Instaclustr, we are glad to > > help! > > > > > This is really awesome of you, Stefan and Instaclustr. Thanks! >

Re: Project website analytics

Thanks Stefan, Instaclustr and everyone involved!

Re: Project website analytics

> > > The box this service runs at is donated by Instaclustr, we are glad to > help! > This is really awesome of you, Stefan and Instaclustr. Thanks!

Re: Project website analytics

Hi all, I have managed to deploy an instance of Plausible (1) service for the upcoming, brand new Cassandra web page (2 and 3). Please keep in mind that the current figures for staging web were aggregated just during our testing just to see how it all actually works, the integration for cassandr

Re: New Cassandra website for review

On 2021-02-26 18:48, Melissa Logan wrote: We are excited to share the almost-complete Cassandra website design (CASSANDRA-16115). The new website is so cool! PS: I noticed the Apple case study says "A year ago, Apple said that it was running over 75,000" but it is quoting an ar

Re: New Cassandra website for review

A huge thanks to everybody that contributed to the new website. All your efforts have paid off. That is truly an amazing work! Le lun. 1 mars 2021 à 03:08, Ben Bromhead a écrit : > Awesome stuff, looks great! > > On Mon, Mar 1, 2021 at 9:33 AM Nate McCall wrote: > > > Th

Re: New Cassandra website for review

Awesome stuff, looks great! On Mon, Mar 1, 2021 at 9:33 AM Nate McCall wrote: > Thanks Melissa! This looks really good. Excited to see it happen. > > On Sat, Feb 27, 2021 at 10:36 AM Melissa Logan > wrote: > > > Hi all, > > > > We are excited to share the

Re: New Cassandra website for review

Thanks Melissa! This looks really good. Excited to see it happen. On Sat, Feb 27, 2021 at 10:36 AM Melissa Logan wrote: > Hi all, > > We are excited to share the almost-complete Cassandra website design > (CASSANDRA-16115). Huge thanks to Lorina Poland, Anthony Grosso, Mick Semb &g

Re: New Cassandra website for review

Nice work, looks great! Thanks, Aaron > On Feb 26, 2021, at 3:36 PM, Melissa Logan wrote: > > Hi all, > > We are excited to share the almost-complete Cassandra website design > (CASSANDRA-16115). Huge thanks to Lorina Poland, Anthony Grosso, Mick Semb > Weaver, Josh

RE: New Cassandra website for review

Look great! Best, Chris -Original Message- From: Melissa Logan Sent: Friday, February 26, 2021 12:48 PM To: dev@cassandra.apache.org Subject: New Cassandra website for review Hi all, We are excited to share the almost-complete Cassandra website design (CASSANDRA-16115). Huge thanks

Re: New Cassandra website for review

Awesome!! On Fri, Feb 26, 2021 at 3:32 PM Benedict Elliott Smith wrote: > Very nice. > > On 26/02/2021, 21:36, "Melissa Logan" wrote: > > Hi all, > > We are excited to share the almost-complete Cassandra website design > (CASSANDRA-16115). Hug

Re: New Cassandra website for review

Very nice. On 26/02/2021, 21:36, "Melissa Logan" wrote: Hi all, We are excited to share the almost-complete Cassandra website design (CASSANDRA-16115). Huge thanks to Lorina Poland, Anthony Grosso, Mick Semb Weaver, Josh Levy, Chris Thornett, Diogenese Topper, and a

Re: New Cassandra website for review

Fantastic! Can't wait for it to go live. On Sat, 27 Feb 2021 at 08:36, Melissa Logan wrote: > Hi all, > > We are excited to share the almost-complete Cassandra website design > (CASSANDRA-16115). Huge thanks to Lorina Poland, Anthony Grosso, Mick Semb > Weaver, Josh

Re: New Cassandra website for review

gt; > Hi all, > > > > We are excited to share the almost-complete Cassandra website design > > (CASSANDRA-16115). Huge thanks to Lorina Poland, Anthony Grosso, Mick > Semb > > Weaver, Josh Levy, Chris Thornett, Diogenese Topper, and a few others who > > contributed

Re: New Cassandra website for review

Looks great, congrats! On Fri, 26 Feb 2021 at 22:36, Melissa Logan wrote: > > Hi all, > > We are excited to share the almost-complete Cassandra website design > (CASSANDRA-16115). Huge thanks to Lorina Poland, Anthony Grosso, Mick Semb > Weaver, Josh Levy, Chris Thornett, Dioge

New Cassandra website for review

Hi all, We are excited to share the almost-complete Cassandra website design (CASSANDRA-16115). Huge thanks to Lorina Poland, Anthony Grosso, Mick Semb Weaver, Josh Levy, Chris Thornett, Diogenese Topper, and a few others who contributed to this effort. Note: There are a few updates to be made

Re: Renaming master to trunk on cassandra-builds, cassandra-website, cassandra-dtest

Thanks Mick, language matters, big ups for taking care of this. On Tue, Oct 27, 2020 at 5:37 AM Mick Semb Wever wrote: > > The general preference there was trunk over main, so to match the > cassandra repository. > > > All Cassandra code repositories have trunk now as their default branch. > > A

Re: Renaming master to trunk on cassandra-builds, cassandra-website, cassandra-dtest

Thanks for this, Mick! Everything looks good to me. On Tue, Oct 27, 2020 at 7:37 AM Mick Semb Wever wrote: > > > The general preference there was trunk over main, so to match the cassandra > > repository. > > > All Cassandra code repositories have trunk now as their default branch. > > All mast

Re: Renaming master to trunk on cassandra-builds, cassandra-website, cassandra-dtest

Thank you for your efforts! On Tue, 27 Oct 2020 at 8:37, Mick Semb Wever wrote: > > The general preference there was trunk over main, so to match the > cassandra repository. > > > All Cassandra code repositories have trunk now as their default branch. > > All master branches have been removed. >

Re: Renaming master to trunk on cassandra-builds, cassandra-website, cassandra-dtest

> The general preference there was trunk over main, so to match the cassandra > repository. All Cassandra code repositories have trunk now as their default branch. All master branches have been removed. The cassandra-dtest repo was referenced in a few places. Please let me know if I missed upd

Re: Project website analytics

I'm sure I could hide a server like that in our AWS bill somewhere and also happy to help out with getting it set up if there is general agreement to go ahead. Cheers Ben --- *Ben Slater**Chief Product Officer* <

Re: Project website analytics

> Yes, we would need a server donated. And (Brandon) I'm trying to chase > down what specs would be required for our traffic numbers. I see other > users mentioning 1-4GB ram server, but I have no idea what traffic > they are dealing with. One of the founders did a test that seems to confirm such

Re: Project website analytics

> I'm a bit unclear what you're looking for here - someone to donate a > server, someone to do admin or both? Or have I missed the point altogether? Yeah, I threw this out there quite prematurely, but kinda intentionally to be as inclusive as possible about it. I might be making a fool of myself,

Re: Project website analytics

Hi Mick I'm a bit unclear what you're looking for here - someone to donate a server, someone to do admin or both? Or have I missed the point altogether? Cheers Ben --- *Ben Slater**Chief Product Officer*

Re: Project website analytics

> It may help gauge what's needed if we have some kind of ballpark idea > for what kind of resources may be needed for this. (The irony that > having analytics here could tell us is not lost on me.) > > For monthly traffic, if what we're seeing from ASF is a 30-day moving > average, then the site s

Re: Project website analytics

So asf infra has given us a go ahead to do website analytics with a self-hosted plausible.io (with the warning that a forthcoming GDPR policy from the ASF might revert it later on). ref INFRA-20748 > Outstanding! It may help gauge what's needed if we have some kind of ballpark idea for w

Re: Project website analytics

ahead to do website analytics with a > self-hosted plausible.io (with the warning that a forthcoming GDPR > policy from the ASF might revert it later on). ref INFRA-20748 > > A few folk have asked for this, and it would certainly make website > updates, blogs and updates much easier in

Project website analytics

So asf infra has given us a go ahead to do website analytics with a self-hosted plausible.io (with the warning that a forthcoming GDPR policy from the ASF might revert it later on). ref INFRA-20748 A few folk have asked for this, and it would certainly make website updates, blogs and updates

Re: Renaming master to trunk on cassandra-builds, cassandra-website, cassandra-dtest

> cassandra-website, cassandra-trunk, and cassandra-diff now have trunk as > their main branches. > s/cassandra-trunk/cassandra-builds/ :-)

Re: Renaming master to trunk on cassandra-builds, cassandra-website, cassandra-dtest

> > > This was discussed in > https://lists.apache.org/thread.html/r54db4cd870d2d665060d5fb50d925843be4b4d54dc64f3d21f04c367%40%3Cdev.cassandra.apache.org%3E > > The general preference there was trunk over main, so to match the > cassandra repository. > cassandra-websi

Re: [DISCUSS] Updating the C* website design

Thanks to those who provided input on the new site layout. #3 was the winner with some additional comments, which we'll work to integrate. In tandem with the new website design, page content has been updated and/or created as new. Input would be greatly appreciated. The content doc, plus

Re: Renaming master to trunk on cassandra-builds, cassandra-website, cassandra-dtest

ter branches on the cassandra-builds, >> cassandra-website and cassandra-dtest repositories to trunk. >> >> This was discussed in >> https://lists.apache.org/thread.html/r54db4cd870d2d665060d5fb50d925843be4b4d54dc64f3d21f04c367%40%3Cdev.cassandra.apache.org%3E >> &g

Re: Renaming master to trunk on cassandra-builds, cassandra-website, cassandra-dtest

+1 generally. We should do this for the sidecar repo as well. Dinesh > On Oct 2, 2020, at 2:17 AM, Mick Semb Wever wrote: > > Next week I plan to rename master branches on the cassandra-builds, > cassandra-website and cassandra-dtest repositories to trunk. > > This was di

Renaming master to trunk on cassandra-builds, cassandra-website, cassandra-dtest

Next week I plan to rename master branches on the cassandra-builds, cassandra-website and cassandra-dtest repositories to trunk. This was discussed in https://lists.apache.org/thread.html/r54db4cd870d2d665060d5fb50d925843be4b4d54dc64f3d21f04c367%40%3Cdev.cassandra.apache.org%3E The general

Re: [DISCUSS] Updating the C* website design

Hi folks, As there were no dissenting votes, based on lazy consensus we have moved forward with the project as outlined in CASSANDRA-16115: https://issues.apache.org/jira/browse/CASSANDRA-16115 If you need a break from 4.0 debugging, would really love folks’ thoughts on new design concepts. Eleme

Re: [DISCUSS] Updating the C* website design

Seems like even Antora uses another SSG called middleman for their “marketing” home page. https://gitlab.com/antora/antora.org If the convenience of having both content and docs all in one SSG for code maintenance is compatible with the aesthetic/ content / taxonomy strategy need for the site

Re: [DISCUSS] Updating the C* website design

Folks, I applaud the choice of Antora for documentation but I’m not sure it is the best choice for generating an appealing site. Antora’s self professed strength is in technical documentation. Do we want to stick to a “documentation” / utility look for the front facing site or for a blog? htt

Re: [DISCUSS] Updating the C* website design

Thanks for the comments, Mick. Yes, I think you are correct in what you have to say about versioned vs non-versioned docs for the website. It's such an obvious comment that I can only say I must have been half-asleep when Anthony and I discussed the topic. (Maybe he was, too!) Since Anto

Re: [DISCUSS] Updating the C* website design

As part of the work, I think all content files should be moved to > cassandra/doc. This would give a clear separation of concerns; > - cassandra/doc contains the material (asciidoc) that is converted to the > website content. > - cassandra-website hosts the live content and contain

Re: [DISCUSS] Updating the C* website design

ould give a clear separation of concerns; - cassandra/doc contains the material (asciidoc) that is converted to the website content. - cassandra-website hosts the live content and contains all the UI resources (html templates, css, js, images) that style the content. Document authors only need t

Re: [DISCUSS] Updating the C* website design

The one issue I see with your suggestion about versioned/non-versioned docs is that the cassandra/doc repo will have asciidoc files, and currently, all the items in the cassandra-website repo are in markdown. There are possible solutions (use antora for the website, put the non-versioned docs in

Re: [DISCUSS] Updating the C* website design

to see all non-versioned docs moved out of the cassandra repository and into the cassandra-website repository (where they become easier to update). - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands

Re: [DISCUSS] Updating the C* website design

Great idea and I think a new fresh design combined with new release gives a great vibe. The proposed incremental approach sounds reasonable to me. @Lorina - is the document open for comments or should we send any here? I will try to go through it in the next few days. Thank you Ekaterina On Wed,

Re: [DISCUSS] Updating the C* website design

Perhaps I should start another thread, but I have started to outline a more solution-based approach to the docs that I was considering implementing. See that here: https://docs.google.com/document/d/1aeNtgyPAsKcNa0GSKvl2ywlFEj30714ry4Sb5turWeE/edit?usp=sharing This outline is not complete, just m

Re: [DISCUSS] Updating the C* website design

> I would offer that design is important, but content matters more -- so > would suggest adding content strategy/development and information > architecture to the checkpoints list. For example, an ecosystem page could > be highly beneficial to end users (what does C* work with?), as well as a > use

Re: [DISCUSS] Updating the C* website design

That all makes sense, Lorina! My thought was to add a consideration for content/IA to the checklist Mick had shared (in addition to the UI/design), but no need if that's already being handled. On Wed, Jul 29, 2020 at 1:28 PM Brandon Williams wrote: > On Wed, Jul 29, 2020 at 3:06 PM Lorina Polan

Re: [DISCUSS] Updating the C* website design

On Wed, Jul 29, 2020 at 3:06 PM Lorina Poland wrote: > UI bundle, but I'm a copier of design, not a designer. To accomplish a UI > that is more modern, like say, https://spark.apache.org or Interesting choice, we used to look more like that in the past: https://web.archive.org/web/20100511183402

Re: [DISCUSS] Updating the C* website design

signer. To accomplish a UI that is more modern, like say, https://spark.apache.org or https://ignite.apache.org/, is beyond my expertise. So, an effort to do website UI design would be concurrent with my continued work to improve the content of both the docs pages and the other pages on the Cassandra websit

Re: [DISCUSS] Updating the C* website design

/case studies page. On Wed, Jul 29, 2020 at 7:49 AM Mick Semb Wever wrote: > We have funds on offer to the project to hire a contractor to update > the website. > > Personally I think this is a fantastic opportunity, it would be great > to see the website afresh in coordination with

[DISCUSS] Updating the C* website design

We have funds on offer to the project to hire a contractor to update the website. Personally I think this is a fantastic opportunity, it would be great to see the website afresh in coordination with the 4.0 release. With no up-front defining goals or improvements specified, if we go forth with

Re: Staging website at cassandra.staged.apache.org

> > Rather than serving the production site from the *content/* directory on > the master branch, is there any objection to serving it from the asf-site > branch? This would mean that the last step in the above process would be > performed on the asf-site branch rather than the master branch. In >

Re: Staging website at cassandra.staged.apache.org

> Hi everyone, > > > > Thanks to hard work by Mick every push to the cassandra-website *src/* > > directory in master is now automatically deployed to > > https://cassandra.staged.apache.org/. The automation is carried out by a > > Jenkins job at https://ci-cassandr

Re: Staging website at cassandra.staged.apache.org

> Thanks to hard work by Mick every push to the cassandra-website *src/* > directory in master is now automatically deployed to > https://cassandra.staged.apache.org/. The automation is carried out by a > Jenkins job at https://ci-cassandra.apache.org/job/cassandra-website/. > This >

Re: Staging website at cassandra.staged.apache.org

Hi everyone, Thanks to hard work by Mick every push to the cassandra-website *src/* directory in master is now automatically deployed to https://cassandra.staged.apache.org/. The automation is carried out by a Jenkins job at https://ci-cassandra.apache.org/job/cassandra-website/. This is really

Re: Staging website at cassandra.staged.apache.org

There's instructions on https://github.com/apache/cassandra-website which I found out from Mick earlier this week. Cheers!

Re: Staging website at cassandra.staged.apache.org

Thanks Mick, if there documentation somewhere on how we update the website ? A - Aaron Morton New Zealand @aaronmorton CEO Apache Cassandra Consulting http://www.thelastpickle.com On Tue, 21 Apr 2020 at 18:40, Mick Semb Wever wrote: > For our cassandra-website reposit

Staging website at cassandra.staged.apache.org

For our cassandra-website repository, any changes to our website can now first be staged at https://cassandra.staged.apache.org/ The staged website comes from the content/ directory on the `asf-staging` branch. regards, Mick

[GitHub] [cassandra-website] ossarga commented on issue #3: Symlink for 3.11 should point to latest 3.11*

ossarga commented on issue #3: URL: https://github.com/apache/cassandra-website/pull/3#issuecomment-616872518 Change looks good to me. I ran the changed bash code on the master branch of the repo inside a Ubuntu docker container. The change works as expected. I am happy for

Re: [GitHub] [cassandra-website] michaelsembwever opened a new pull request #3: Symlink for 3.11 should point to latest 3.11*

> michaelsembwever opened a new pull request #3: > URL: https://github.com/apache/cassandra-website/pull/3 Created INFRA-20155 to move these notifications to pr@cassandra.a.o - To unsubscribe, e-mail: dev-un

[GitHub] [cassandra-website] michaelsembwever opened a new pull request #3: Symlink for 3.11 should point to latest 3.11*

michaelsembwever opened a new pull request #3: URL: https://github.com/apache/cassandra-website/pull/3 Previously the 3.11 was getting symlink'd to the earliest 3.11, which was obviously wrong. This is an automated me

[GitHub] [cassandra-website] mshuler merged pull request #2: Run container build steps as non-root user

mshuler merged pull request #2: Run container build steps as non-root user URL: https://github.com/apache/cassandra-website/pull/2 This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [cassandra-website] mshuler opened a new pull request #2: Run container build steps as non-root user

mshuler opened a new pull request #2: Run container build steps as non-root user URL: https://github.com/apache/cassandra-website/pull/2 This is an automated message from the Apache Git Service. To respond to the message

Re: putting the alphas on the website downloads section

Seems reasonable. I can set up that wiki page and update the website at the end of the week, unless someone else gets to it first. Maybe I should know this already - is there a nightly build that's already created we could also point people to? Jon On Mon, Nov 4, 2019 at 2:59 PM Mi

  1   2   >