cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (Jira)" <>
Subject [jira] [Commented] (CASSANDRA-16115) New Cassandra website design, content and layout to work with Antora
Date Tue, 15 Sep 2020 20:49:00 GMT


Brandon Williams commented on CASSANDRA-16115:

bq. can we dispense with 2.2?

What is the rationale behind this?

> New Cassandra website design, content and layout to work with Antora
> --------------------------------------------------------------------
>                 Key: CASSANDRA-16115
>                 URL:
>             Project: Cassandra
>          Issue Type: Task
>          Components: Documentation/Website
>            Reporter: Melissa Logan
>            Assignee: Melissa Logan
>            Priority: Normal
>         Attachments: Screen Shot 2020-09-03 at 09.48.53.png
> This task is related to CASSANDRA-16066 (Update and rework the cassandra-website material
to work with Antora). The goal is to update the front-end of the C* website (design, IA and
content) to work with Antora to help modernize the website as discussed on the [mailing list|].
> *Design Concepts:* A minimum of two homepage design concepts will be created and shared
for input, which will help standardize a brand palette for C* and a design language for the
site. This may include custom iconography and graphics. The chosen design language will be
used to develop the remaining templates. 
> *Template Design*: It's estimated that 7 template designs will be needed including the
creation of several new pages: 
>  * Homepage template
>  * Toplevel template - e.g. Community.
>  * General template - Mostly textual with some images, e.g. Intro, Quickstart 
>  * “Library” template - A library of assets (links, downloads, logos etc) that are
sortable by metadata, e.g Resources, or Kafka's Powered By page).
>  * Blog landing template 
>  * Blog single template
>  * Docs template 
> *Website Content:* Along with new design will be a need for new or updated content to
fit the new page layouts. The intention is to use as much as possible from existing content,
and augment with new content where needed.
> *Template Development:* This includes the frontend development, such as any HTML markup
to achieve designs. HTML would be crafted so as to preserve any backend/API calls, such that
content is pulled in as designed. The majority of the frontend work would come in the form
of crafting CSS to bring the designs to life, plus any minor Javascript to add subtle delights
to key pages.
> *Style Guide*: Once all is complete, a Style Guide be added to GitHub for contributors.
> The [cassandra-website|] repository would
need to be modified. Specific changes to be determined. 

This message was sent by Atlassian Jira

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message