[jira] [Commented] (IGNITE-13781) Ignite Website: rework Ignite features section

["Denis A. Magda (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-13781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243524#comment-17243524 ] 

Denis A. Magda commented on IGNITE-13781:
-----------------------------------------

*Feature #1 - Multi-Tier Storage*

Description:
By default, Ignite operates in a pure in-memory mode. However, with its multi-tier storage engine, you can request Ignite to utilize given disk resources. With a switch of a single configuration setting, you can turn an in-memory cluster into a distributed database that operates across memory and disk tiers:

Example:

{code:xml}
<bean class="org.apache.ignite.configuration.IgniteConfiguration">
    <property name="dataStorageConfiguration">
        <bean class="org.apache.ignite.configuration.DataStorageConfiguration">
            <property name="defaultDataRegionConfiguration">
                <bean class="org.apache.ignite.configuration.DataRegionConfiguration">
                    <property name="persistenceEnabled" value="true"/>
                </bean>
            </property>
        </bean>
    </property>
</bean>
{code}

Learn More Button goes to this page: https://ignite.apache.org/docs/latest/memory-architecture



> Ignite Website: rework Ignite features section
> ----------------------------------------------
>
>                 Key: IGNITE-13781
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13781
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: website
>            Reporter: Denis A. Magda
>            Assignee: Mauricio Stekl
>            Priority: Critical
>
> Presently, the features section introduces a distinguishing capability of Ignite with a short paragraph. This is enough for the SEO but not for a developer who came to the website from a Google search result and hopes to learn more details on the main page.
> The features section needs to be reworked as follows (see a sketch attached):
> * Top-5 features are arranged in stacked blocks to the left of the section. The right part of the section covers details about a selected feature.
> * Once a feature is selected, the right part of the section is updated with the feature details.
> * The feature details include a short paragraph about the feature, a code snippet showing how to use or activate the feature, the Learn More button that navigates to a dedicated feature page.
> * The code snippets section needs to support Java, C#, C++, Python, Node.JS, SQL, XML, YAML syntaxes. A single code snippet can consist of multiple tabs (for instance, one tab is for Java while the other is for Python).
> Check the *A full-stack data platform, from the creators of Apache Druid* section of Imply's main page to get a sense of how the section can look like:
> https://imply.io



--
This message was sent by Atlassian Jira
(v8.3.4#803005)