[jira] [Updated] (IGNITE-15634) Ignite Website: misaligned block with stars and 2.11 promo
[ https://issues.apache.org/jira/browse/IGNITE-15634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-15634: Description: Mauricio, could you please help with the following: * Issue: the block with the stars is misaligned on the home page. See the attached picture. * The promo banner: promote the latest release - "Apache Ignite 2.11 Released: See Why You Need to Upgrade ->" [https://blogs.apache.org/ignite/entry/apache-ignite-2-11-stabilization] was: Mauricio, could you please help with the following: * Issue: the block with the stars is misaligned on the home page. See the attached picture. * The promo banner: promote the latest release - "Apache Ignite 2.11 Released: See What's New and Upgrade ->" https://blogs.apache.org/ignite/entry/apache-ignite-2-11-stabilization > Ignite Website: misaligned block with stars and 2.11 promo > -- > > Key: IGNITE-15634 > URL: https://issues.apache.org/jira/browse/IGNITE-15634 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Attachments: Screenshot 2021-09-27 142144.png > > > Mauricio, could you please help with the following: > * Issue: the block with the stars is misaligned on the home page. See the > attached picture. > * The promo banner: promote the latest release - "Apache Ignite 2.11 > Released: See Why You Need to Upgrade ->" > [https://blogs.apache.org/ignite/entry/apache-ignite-2-11-stabilization] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15634) Ignite Website: misaligned block with stars and 2.11 promo
[ https://issues.apache.org/jira/browse/IGNITE-15634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-15634: Attachment: Screenshot 2021-09-27 142144.png > Ignite Website: misaligned block with stars and 2.11 promo > -- > > Key: IGNITE-15634 > URL: https://issues.apache.org/jira/browse/IGNITE-15634 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Attachments: Screenshot 2021-09-27 142144.png > > > Mauricio, could you please help with the following: > * Issue: the block with the stars is misaligned on the home page. See the > attached picture. > * The promo banner: promote the latest release - "Apache Ignite 2.11 > Released: See What's New and Upgrade ->" > https://blogs.apache.org/ignite/entry/apache-ignite-2-11-stabilization -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15634) Ignite Website: misaligned block with stars and 2.11 promo
Denis A. Magda created IGNITE-15634: --- Summary: Ignite Website: misaligned block with stars and 2.11 promo Key: IGNITE-15634 URL: https://issues.apache.org/jira/browse/IGNITE-15634 Project: Ignite Issue Type: Bug Components: website Reporter: Denis A. Magda Assignee: Mauricio Stekl Attachments: Screenshot 2021-09-27 142144.png Mauricio, could you please help with the following: * Issue: the block with the stars is misaligned on the home page. See the attached picture. * The promo banner: promote the latest release - "Apache Ignite 2.11 Released: See What's New and Upgrade ->" https://blogs.apache.org/ignite/entry/apache-ignite-2-11-stabilization -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15553) Website: the feedback button and banner cover the menu
Denis A. Magda created IGNITE-15553: --- Summary: Website: the feedback button and banner cover the menu Key: IGNITE-15553 URL: https://issues.apache.org/jira/browse/IGNITE-15553 Project: Ignite Issue Type: Bug Components: website Reporter: Denis A. Magda Assignee: Mauricio Stekl Attachments: error_2.png See the attached picture. The button and banner cover a part of the right-hand side navigation menu. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15459) Bugyard feedback #5: Fix Kubernetes installation script
[ https://issues.apache.org/jira/browse/IGNITE-15459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17411284#comment-17411284 ] Denis A. Magda commented on IGNITE-15459: - [~igusev], done, thanks for the contribution! > Bugyard feedback #5: Fix Kubernetes installation script > --- > > Key: IGNITE-15459 > URL: https://issues.apache.org/jira/browse/IGNITE-15459 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.10, 2.11 >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > We need to fix the code sample in [Creating ConfigMap for Node Configuration > File > |[https://ignite.apache.org/docs/latest/installation/kubernetes/gke-deployment#creating-configmap-for-node-configuration-file]] > section of kubernetes installation. > The code snippet does not include full example. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15461) Bugyard feedback #6: Specify that near-caches are not created on thin clients
[ https://issues.apache.org/jira/browse/IGNITE-15461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17411283#comment-17411283 ] Denis A. Magda commented on IGNITE-15461: - [~igusev], done, thanks for the contribution! > Bugyard feedback #6: Specify that near-caches are not created on thin clients > - > > Key: IGNITE-15461 > URL: https://issues.apache.org/jira/browse/IGNITE-15461 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Bugyard feedback 6 asks if near caches are available on thin clients. We > should specify that it only affects thick clients and servers on the near > cache page > https://ignite.apache.org/docs/latest/configuring-caches/near-cache. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15372) Remove companies logos from the homepage
[ https://issues.apache.org/jira/browse/IGNITE-15372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17407586#comment-17407586 ] Denis A. Magda commented on IGNITE-15372: - We can replace the logos with the following text and some eye-catching graphic: * Text: _Your favorite streaming, gaming, banking, travel or shopping application probably uses Apache Ignite. Learn why the elite developers and architects selected Ignite to create applications used by millions of people daily!_ * _Graphics:_ something related to the fact that Ignite remains a top 5 project of the ASF across several categories - https://docs.google.com/document/d/1xZ2cfH_YiuNrf8-YSIsupGU3eU9qovhrfdF0etPhp3c/edit > Remove companies logos from the homepage > > > Key: IGNITE-15372 > URL: https://issues.apache.org/jira/browse/IGNITE-15372 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Priority: Critical > > We have to remove the logos of the companies that use Ignite from the > homepage (this rule doesn't apply to other pages). > WHY: the ASF is strictly vendor-neutral. Listing company names and/or logos > on a project's home page is disallowed as it can imply "ownership" or > preferred status or otherwise imbalanced relationship. Whether this is the > case or not, it is not acceptable. The policy is the same as "thanking" > companies for their support of a project > [http://apache.org/foundation/marks/linking#projectthanks] > As an alternative, we can create a "powered by" section similar to what the > Kafka community has: http://kafka.apache.org > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15320) Ignite Website UX and UI Improvements
[ https://issues.apache.org/jira/browse/IGNITE-15320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17406777#comment-17406777 ] Denis A. Magda commented on IGNITE-15320: - Working on mockups of the main website pages here: [https://app.moqups.com/END79Kh245/edit/page/aec8aa79a] Feel free to review and provide feedback. > Ignite Website UX and UI Improvements > - > > Key: IGNITE-15320 > URL: https://issues.apache.org/jira/browse/IGNITE-15320 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Denis A. Magda >Priority: Major > > In early 2021 a 3rd-party vendor helped us to conduct a usability audit of > the Ignite website. The audit revealed significant user experience and > structure-related gaps that make it harder to understand Ignite, navigate, > consume content. > > We were suggested to implement UI and UX changes to address those gaps. Here > is a new version of the pages that are in progress: > https://drive.google.com/file/d/1cgrkEHEbnXIHpslNFHANP-6Ng1Z5R_sO/view?usp=sharing -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15372) Remove companies logos from the homepage
Denis A. Magda created IGNITE-15372: --- Summary: Remove companies logos from the homepage Key: IGNITE-15372 URL: https://issues.apache.org/jira/browse/IGNITE-15372 Project: Ignite Issue Type: Task Components: website Reporter: Denis A. Magda We have to remove the logos of the companies that use Ignite from the homepage (this rule doesn't apply to other pages). WHY: the ASF is strictly vendor-neutral. Listing company names and/or logos on a project's home page is disallowed as it can imply "ownership" or preferred status or otherwise imbalanced relationship. Whether this is the case or not, it is not acceptable. The policy is the same as "thanking" companies for their support of a project [http://apache.org/foundation/marks/linking#projectthanks] As an alternative, we can create a "powered by" section similar to what the Kafka community has: http://kafka.apache.org -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15349) Fix feedback #4
[ https://issues.apache.org/jira/browse/IGNITE-15349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17402414#comment-17402414 ] Denis A. Magda commented on IGNITE-15349: - [~igusev] - done! > Fix feedback #4 > --- > > Key: IGNITE-15349 > URL: https://issues.apache.org/jira/browse/IGNITE-15349 > Project: Ignite > Issue Type: Improvement >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > We need to update text on > [https://ignite.apache.org/docs/latest/sql-reference/transactions#] to > include ROLLBACK command -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15320) Ignite Website UX and UI Improvements
Denis A. Magda created IGNITE-15320: --- Summary: Ignite Website UX and UI Improvements Key: IGNITE-15320 URL: https://issues.apache.org/jira/browse/IGNITE-15320 Project: Ignite Issue Type: Task Components: website Reporter: Denis A. Magda Assignee: Denis A. Magda In early 2021 a 3rd-party vendor helped us to conduct a usability audit of the Ignite website. The audit revealed significant user experience and structure-related gaps that make it harder to understand Ignite, navigate, consume content. We were suggested to implement UI and UX changes to address those gaps. Here is a new version of the pages that are in progress: https://drive.google.com/file/d/1cgrkEHEbnXIHpslNFHANP-6Ng1Z5R_sO/view?usp=sharing -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14392) Remove the SQL Transactions page from Apache Ignite docs
[ https://issues.apache.org/jira/browse/IGNITE-14392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17335690#comment-17335690 ] Denis A. Magda commented on IGNITE-14392: - [~igusev], could we remove the redirect? Let's keep it in the sources and published so that those who have a direct link to the page can open it up. > Remove the SQL Transactions page from Apache Ignite docs > > > Key: IGNITE-14392 > URL: https://issues.apache.org/jira/browse/IGNITE-14392 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Nikita Safonov >Assignee: Igor Gusev >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The page: > [https://ignite.apache.org/docs/latest/SQL/sql-transactions|https://www.gridgain.com/docs/latest/developers-guide/SQL/sql-transactions] > * We should remove it from the menu (toc.yaml) > * We should make sure it's not indexed by Google -> need to update robot.txt > * We should check references to this page from other pages. The references > do exist. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14525) Empty page in docs
[ https://issues.apache.org/jira/browse/IGNITE-14525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17335688#comment-17335688 ] Denis A. Magda commented on IGNITE-14525: - [~igusev], alright, let's remove it then. I merged the patch. Thanks! > Empty page in docs > -- > > Key: IGNITE-14525 > URL: https://issues.apache.org/jira/browse/IGNITE-14525 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > [https://ignite.apache.org/docs/latest/installation/] page is empty. There > should be some introduction in it, or no page at all. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14404) Highlight that Ignite supports only Java 8 and 11
[ https://issues.apache.org/jira/browse/IGNITE-14404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17318210#comment-17318210 ] Denis A. Magda commented on IGNITE-14404: - Thanks [~igusev], merged! > Highlight that Ignite supports only Java 8 and 11 > - > > Key: IGNITE-14404 > URL: https://issues.apache.org/jira/browse/IGNITE-14404 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Nikita Safonov >Assignee: Igor Gusev >Priority: Major > Labels: docuentation > Time Spent: 10m > Remaining Estimate: 0h > > We need to say that Ignite supports only Java 8 and Java 11. > The current doc implies that it supports Java 8+ > See the table here: > https://ignite.apache.org/docs/latest/quick-start/java#prerequisites -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14491) Docs on ThinClientKubernetesAddressFinder
[
https://issues.apache.org/jira/browse/IGNITE-14491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17317251#comment-17317251
]
Denis A. Magda commented on IGNITE-14491:
-
[~igusev], thanks for the contribution. I've merged the changes. Please reach
out to [~mstekl] who can help to release the change in production. Mauricio can
commit to the Ignite website:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document#HowtoDocument-PublishingtotheWebsite
> Docs on ThinClientKubernetesAddressFinder
> -
>
> Key: IGNITE-14491
> URL: https://issues.apache.org/jira/browse/IGNITE-14491
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Reporter: Nikita Safonov
>Assignee: Igor Gusev
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {color:#00}ThinClientKubernetesAddressFinder is mentioned here:{color}
>
> [[https://ignite.apache.org/docs/latest/thin-clients/java-thin-client#partition-awareness]
> - Please describe when to use it.
> - See the relevant issue below:
> _Check this section of the AWS EKS page:
> [https://ignite.apache.org/docs/latest/installation/kubernetes/amazon-eks-deployment#partition-awareness]_
> __
> _The Partition Awareness is a top-level section and the "Connecting to REST
> API" is placed under it. Which is wrong. The Partition Awareness must be
> located as a sub-section of the "Connecting with Thin Clients" section that
> is above. If it's impossible to have another level under this tree then
> rename:_
> - Remove this statement form the Partition Awareness everywhere. Double
> check with Pavel Tupytsin.
>
> _"Note that for non-Java clients presently you need to provide addresses of
> all the server nodes in the connection properties. This also means that if a
> new server node joins the cluster, you should add the server’s address to the
> connection properties and reconnect the thin client. Otherwise, the thin
> client will not be able to send direct requests to this server. This
> limitation is planned to be addressed before the GA release of the feature."_
>
> * _"Partition Awareness" -> "Connecting with Thin Clients and Partition
> Awareness"_
> - This needs to be done for Azure and Google Pages as well.
> Consult with dev team for more details.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14398) Document thin client support for spring-data integration.
[ https://issues.apache.org/jira/browse/IGNITE-14398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17314024#comment-17314024 ] Denis A. Magda commented on IGNITE-14398: - [~PetrovMikhail] we can say that "replace the ignite-spring-data-ext.version parameter with a version of the extension that corresponds to your version of Ignite. The version is "1.0.0" for Ignite 2.10.0 and earlier versions. See this table for a complete matching of the versions". The table that matches the versions can be under a separate section on this page or we can point out to some page on the Maven Central website. [~nsafonov] please share your inputs as well. > Document thin client support for spring-data integration. > - > > Key: IGNITE-14398 > URL: https://issues.apache.org/jira/browse/IGNITE-14398 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Fix For: 2.11 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > It's needed to document thin client support for spring-data integration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14398) Document thin client support for spring-data integration.
[
https://issues.apache.org/jira/browse/IGNITE-14398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313973#comment-17313973
]
Denis A. Magda commented on IGNITE-14398:
-
[~PetrovMikhail] [~nsafonov]
Check the pull request and see that we're suggesting replacing the following
occurrence ${ignite-spring-data-ext.version} with an actual version. Where the
reader can find the actual version? There needs to be some section that matches
an Ignite version to a compatible version of the extensions.
> Document thin client support for spring-data integration.
> -
>
> Key: IGNITE-14398
> URL: https://issues.apache.org/jira/browse/IGNITE-14398
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mikhail Petrov
>Assignee: Mikhail Petrov
>Priority: Minor
> Fix For: 2.11
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> It's needed to document thin client support for spring-data integration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13029) Support Spring Data repositories initialization with Spring Boot auto-starter
[
https://issues.apache.org/jira/browse/IGNITE-13029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17298305#comment-17298305
]
Denis A. Magda commented on IGNITE-13029:
-
[~sdanilov] could you help to merge the pull-request? Thanks Sergey!
> Support Spring Data repositories initialization with Spring Boot auto-starter
> -
>
> Key: IGNITE-13029
> URL: https://issues.apache.org/jira/browse/IGNITE-13029
> Project: Ignite
> Issue Type: Improvement
> Components: spring, springdata
>Affects Versions: 2.8
>Reporter: Denis A. Magda
>Assignee: Sergey Dorozhkin
>Priority: Major
> Labels: newbie
>
> It's required to use {{@EnableIgniteRepositories}} annotation and follow this
> procedure to enable Ignite Spring Data repositories:
> https://apacheignite-mix.readme.io/docs/spring-data#spring-data-and-apache-ignite-configuration
> Support the Spring Data repositories enablement via the Spring Boot
> auto-starter if Spring Boot is used by a project:
> https://apacheignite-mix.readme.io/docs/spring-boot
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14215) Website: Enable Lucky Orange and Yandex Metrics
[ https://issues.apache.org/jira/browse/IGNITE-14215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296029#comment-17296029 ] Denis A. Magda commented on IGNITE-14215: - [~mstekl] thanks! We won't need Lucky Orange after the audit is over but I would keep Yandex Metrica because it shows heatmaps and other metrics unsupported by Google Metrics. Let's add Yandex Metrica support permanently by adding it to upcoming/future releases of the APIs and technical docs. Ignite 2.10 is coming (check the dev list), so I would implement it for that release and following. > Website: Enable Lucky Orange and Yandex Metrics > --- > > Key: IGNITE-14215 > URL: https://issues.apache.org/jira/browse/IGNITE-14215 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > > We're conducting a usability audit of the Ignite website to better understand > what parts of the site get more attention and what doesn't resonate with > developers landing on the pages. The goal is to introduce and explain Ignite > in the most concise and technical way, and to guide the users from the > landing pages to documentation and other pages so that they can transition > with their Ignite journey seamlessly. > > To better understand how the users perceive the information on the current > web pages, we need to see heatmaps and other advanced metrics that are > supported by the following tools: > * [https://www.luckyorange.com|https://www.luckyorange.com/] > * [https://metrica.yandex.com/about]? > Let's use the tools for the time of the audit. All the data is capture and > kept anonymous. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14260) Replace HomeAway picture with Vrbo
[ https://issues.apache.org/jira/browse/IGNITE-14260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17293146#comment-17293146 ] Denis A. Magda commented on IGNITE-14260: - Thank you Mauricio! > Replace HomeAway picture with Vrbo > -- > > Key: IGNITE-14260 > URL: https://issues.apache.org/jira/browse/IGNITE-14260 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > > HomeAway was rebranded to Vrbo. We need to replace the HomeAway logo on the > main page with the Vrbo one: > https://www.vrbo.com -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14260) Replace HomeAway picture with Vrbo
[ https://issues.apache.org/jira/browse/IGNITE-14260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17293031#comment-17293031 ] Denis A. Magda edited comment on IGNITE-14260 at 3/1/21, 5:10 PM: -- [~mstekl], could help with this please? I've already updated the text on the proven uses cases page. was (Author: dmagda): [~mstekl], could help with this please? I've already update the text on the proven uses cases page. > Replace HomeAway picture with Vrbo > -- > > Key: IGNITE-14260 > URL: https://issues.apache.org/jira/browse/IGNITE-14260 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Priority: Major > > HomeAway was rebranded to Vrbo. We need to replace the HomeAway logo on the > main page with the Vrbo one: > https://www.vrbo.com -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14260) Replace HomeAway picture with Vrbo
[ https://issues.apache.org/jira/browse/IGNITE-14260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17293031#comment-17293031 ] Denis A. Magda commented on IGNITE-14260: - [~mstekl], could help with this please? I've already update the text on the proven uses cases page. > Replace HomeAway picture with Vrbo > -- > > Key: IGNITE-14260 > URL: https://issues.apache.org/jira/browse/IGNITE-14260 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Priority: Major > > HomeAway was rebranded to Vrbo. We need to replace the HomeAway logo on the > main page with the Vrbo one: > https://www.vrbo.com -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14260) Replace HomeAway picture with Vrbo
Denis A. Magda created IGNITE-14260: --- Summary: Replace HomeAway picture with Vrbo Key: IGNITE-14260 URL: https://issues.apache.org/jira/browse/IGNITE-14260 Project: Ignite Issue Type: Task Components: website Reporter: Denis A. Magda HomeAway was rebranded to Vrbo. We need to replace the HomeAway logo on the main page with the Vrbo one: https://www.vrbo.com -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14215) Website: Enable Lucky Orange and Yandex Metrics
[ https://issues.apache.org/jira/browse/IGNITE-14215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17287284#comment-17287284 ] Denis A. Magda commented on IGNITE-14215: - [~mauri...@gridgain.com], could you please help with this? > Website: Enable Lucky Orange and Yandex Metrics > --- > > Key: IGNITE-14215 > URL: https://issues.apache.org/jira/browse/IGNITE-14215 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Priority: Major > > We're conducting a usability audit of the Ignite website to better understand > what parts of the site get more attention and what doesn't resonate with > developers landing on the pages. The goal is to introduce and explain Ignite > in the most concise and technical way, and to guide the users from the > landing pages to documentation and other pages so that they can transition > with their Ignite journey seamlessly. > > To better understand how the users perceive the information on the current > web pages, we need to see heatmaps and other advanced metrics that are > supported by the following tools: > * [https://www.luckyorange.com|https://www.luckyorange.com/] > * [https://metrica.yandex.com/about]? > Let's use the tools for the time of the audit. All the data is capture and > kept anonymous. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14215) Website: Enable Lucky Orange and Yandex Metrics
Denis A. Magda created IGNITE-14215: --- Summary: Website: Enable Lucky Orange and Yandex Metrics Key: IGNITE-14215 URL: https://issues.apache.org/jira/browse/IGNITE-14215 Project: Ignite Issue Type: Bug Components: website Reporter: Denis A. Magda We're conducting a usability audit of the Ignite website to better understand what parts of the site get more attention and what doesn't resonate with developers landing on the pages. The goal is to introduce and explain Ignite in the most concise and technical way, and to guide the users from the landing pages to documentation and other pages so that they can transition with their Ignite journey seamlessly. To better understand how the users perceive the information on the current web pages, we need to see heatmaps and other advanced metrics that are supported by the following tools: * [https://www.luckyorange.com|https://www.luckyorange.com/] * [https://metrica.yandex.com/about]? Let's use the tools for the time of the audit. All the data is capture and kept anonymous. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13029) Support Spring Data repositories initialization with Spring Boot auto-starter
[
https://issues.apache.org/jira/browse/IGNITE-13029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17277336#comment-17277336
]
Denis A. Magda commented on IGNITE-13029:
-
[~sdanilov], could you please review Sergey's changes? You're more experienced
with Spring than I am, so it's much better to have you as a reviewer.
> Support Spring Data repositories initialization with Spring Boot auto-starter
> -
>
> Key: IGNITE-13029
> URL: https://issues.apache.org/jira/browse/IGNITE-13029
> Project: Ignite
> Issue Type: Improvement
> Components: spring, springdata
>Affects Versions: 2.8
>Reporter: Denis A. Magda
>Assignee: Sergey Dorozhkin
>Priority: Major
> Labels: newbie
>
> It's required to use {{@EnableIgniteRepositories}} annotation and follow this
> procedure to enable Ignite Spring Data repositories:
> https://apacheignite-mix.readme.io/docs/spring-data#spring-data-and-apache-ignite-configuration
> Support the Spring Data repositories enablement via the Spring Boot
> auto-starter if Spring Boot is used by a project:
> https://apacheignite-mix.readme.io/docs/spring-boot
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13941) Poor CLS reported for multiple website pages
[ https://issues.apache.org/jira/browse/IGNITE-13941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17268842#comment-17268842 ] Denis A. Magda commented on IGNITE-13941: - [~mstekl] as discussed, let's run an experiment. Please select a few pages and set the width/height there. After that let's see if the CLS score improves for those pages significantly. > Poor CLS reported for multiple website pages > > > Key: IGNITE-13941 > URL: https://issues.apache.org/jira/browse/IGNITE-13941 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Attachments: Screen Shot 2021-01-15 at 12.53.29.png > > > Google reported a poor CLS index for multiple pages: > [https://search.google.com/search-console/core-web-vitals?resource_id=https%3A%2F%2Fignite.apache.org%2F] > > The mobile traffic is affected even more severely. Need to address the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13941) Poor CLS reported for multiple website pages
[ https://issues.apache.org/jira/browse/IGNITE-13941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17266179#comment-17266179 ] Denis A. Magda commented on IGNITE-13941: - [~mstekl] the plug-in link is broken. Could you resend it? Overall, it's not ideal to set a specific size for images. Primarily because an image is automatically adjusted depending on your screen dimension/resolution. > Poor CLS reported for multiple website pages > > > Key: IGNITE-13941 > URL: https://issues.apache.org/jira/browse/IGNITE-13941 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Attachments: Screen Shot 2021-01-15 at 12.53.29.png > > > Google reported a poor CLS index for multiple pages: > [https://search.google.com/search-console/core-web-vitals?resource_id=https%3A%2F%2Fignite.apache.org%2F] > > The mobile traffic is affected even more severely. Need to address the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13941) Poor CLS reported for multiple website pages
[ https://issues.apache.org/jira/browse/IGNITE-13941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17265607#comment-17265607 ] Denis A. Magda commented on IGNITE-13941: - [~mstekl], done! I used this command to rebuild the 2.9.1 docs: ./build.sh --version=2.9.1 --github-branch=ignite-2.9.1 --latest Once you finish with the optimizations, we need to rebuild all published documentation versions. > Poor CLS reported for multiple website pages > > > Key: IGNITE-13941 > URL: https://issues.apache.org/jira/browse/IGNITE-13941 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > > Google reported a poor CLS index for multiple pages: > [https://search.google.com/search-console/core-web-vitals?resource_id=https%3A%2F%2Fignite.apache.org%2F] > > The mobile traffic is affected even more severely. Need to address the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13988) Version dropdown on docs is not aligned to the right on Safari
[ https://issues.apache.org/jira/browse/IGNITE-13988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-13988. - Resolution: Fixed > Version dropdown on docs is not aligned to the right on Safari > -- > > Key: IGNITE-13988 > URL: https://issues.apache.org/jira/browse/IGNITE-13988 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Mauricio Stekl >Assignee: Mauricio Stekl >Priority: Minor > Attachments: Screen Shot 2021-01-13 at 11.10.04.png > > > This can be reproduced only on Safari. Basically caused because > 'text-align-last' doesn't work on this browser. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-13988) Version dropdown on docs is not aligned to the right on Safari
[ https://issues.apache.org/jira/browse/IGNITE-13988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-13988. --- > Version dropdown on docs is not aligned to the right on Safari > -- > > Key: IGNITE-13988 > URL: https://issues.apache.org/jira/browse/IGNITE-13988 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Mauricio Stekl >Assignee: Mauricio Stekl >Priority: Minor > Attachments: Screen Shot 2021-01-13 at 11.10.04.png > > > This can be reproduced only on Safari. Basically caused because > 'text-align-last' doesn't work on this browser. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13988) Version dropdown on docs is not aligned to the right on Safari
[ https://issues.apache.org/jira/browse/IGNITE-13988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17264472#comment-17264472 ] Denis A. Magda commented on IGNITE-13988: - Thanks, confirm that it got fixed on my end! > Version dropdown on docs is not aligned to the right on Safari > -- > > Key: IGNITE-13988 > URL: https://issues.apache.org/jira/browse/IGNITE-13988 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Mauricio Stekl >Assignee: Mauricio Stekl >Priority: Minor > Attachments: Screen Shot 2021-01-13 at 11.10.04.png > > > This can be reproduced only on Safari. Basically caused because > 'text-align-last' doesn't work on this browser. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-3690) Log Message Glossary
[ https://issues.apache.org/jira/browse/IGNITE-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda reassigned IGNITE-3690: -- Assignee: (was: Denis A. Magda) > Log Message Glossary > > > Key: IGNITE-3690 > URL: https://issues.apache.org/jira/browse/IGNITE-3690 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 1.4 >Reporter: Denis A. Magda >Priority: Minor > Labels: ignite-3 > Fix For: 3.0 > > > It's time for Ignite to create a page that lists ALL the log messages, their > common causes, and potential solutions. > Probably it makes sense to assign a unique ID for the most well-known errors > so that a user is able to look up an error in the glossary quicker. > > Oracle's example: > https://docs.oracle.com/cd/B28359_01/server.111/b28278/e0.htm#ORA-0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13982) Add documentation for new checkpoint, cluster and cache metrics
[ https://issues.apache.org/jira/browse/IGNITE-13982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17263461#comment-17263461 ] Denis A. Magda commented on IGNITE-13982: - [~nsafonov], please add this ticket to the review pipeline? > Add documentation for new checkpoint, cluster and cache metrics > --- > > Key: IGNITE-13982 > URL: https://issues.apache.org/jira/browse/IGNITE-13982 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > Add documentation for new metrics: > * LastCheckpointbeforeLockDuration > * LastCheckpointListenersExecuteDuration > * LastCheckpointLockHoldDuration > * LastCheckpointWalCpRecordFsyncDuration > * LastCheckpointWriteCheckpointEntryDuration > * LastCheckpointSplitAndSortPagesDuration > * LastCheckpointStart > * CheckpointBeforeLockHistogram > * CheckpointLockWaitHistogram > * CheckpointListenersExecuteHistogram > * CheckpointMarkHistogram > * CheckpointLockHoldHistogram > * CheckpointPagesWriteHistogram > * CheckpointFsyncHistogram > * CheckpointWalRecordFsyncHistogram > * CheckpointWriteEntryHistogram > * CheckpointSplitAndSortPagesHistogram > * CheckpointHistogram > * TotalBaselineNodes > * TotalServerNodes > * TotalClientNodes > * ActiveBaselineNodes > * Rebalanced > * OffHeapEntriesCount > * OffHeapBackupEntriesCount > * OffHeapPrimaryEntriesCount > * HeapEntriesCount > * CacheSize > * IndexRebuildKeyProcessed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13962) Ignite Docs: broken UI when building docs locally
[ https://issues.apache.org/jira/browse/IGNITE-13962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17262828#comment-17262828 ] Denis A. Magda commented on IGNITE-13962: - [~xtern], thanks for fixing this! [~mstekl] could you review and incorporate this specific fix. The documentation changes are planned to be reviewed by Nikita Safonov. > Ignite Docs: broken UI when building docs locally > - > > Key: IGNITE-13962 > URL: https://issues.apache.org/jira/browse/IGNITE-13962 > Project: Ignite > Issue Type: Bug > Components: documentation, website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Attachments: Screen Shot 2021-01-07 at 11.14.41 AM.png > > > When you build the docs locally from the repository using the run.sh script > ([https://github.com/apache/ignite/blob/master/docs/run.sh]) it seems that > the CSS is not picked up properly which results in a broken UI. > > See the screenshot attached. It used to work before. Probably, we need to > come up with a way of reusing the CSS/header that is stored in the website > repository. > > !Screen Shot 2021-01-07 at 11.14.41 AM.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13962) Ignite Docs: broken UI when building docs locally
[ https://issues.apache.org/jira/browse/IGNITE-13962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-13962: Description: When you build the docs locally from the repository using the [run.sh script|[https://github.com/apache/ignite/blob/master/docs/run.sh]] it seems that the CSS is not picked up properly which results in a broken UI. See the screenshot attached. It used to work before. Probably, we need to come up with a way of reusing the CSS/header that is stored in the website repository. !Screen Shot 2021-01-07 at 11.14.41 AM.png! was: When you build the docs locally from the repository using the [run.sh script|[https://github.com/apache/ignite/blob/master/docs/run.sh],] it seems that the CSS is not picked up properly which results in a broken UI. See the screenshot attached. It used to work before. Probably, we need to come up with a way of reusing the CSS/header that is stored in the website repository. !Screen Shot 2021-01-07 at 11.14.41 AM.png! > Ignite Docs: broken UI when building docs locally > - > > Key: IGNITE-13962 > URL: https://issues.apache.org/jira/browse/IGNITE-13962 > Project: Ignite > Issue Type: Bug > Components: documentation, website >Reporter: Denis A. Magda >Priority: Major > Attachments: Screen Shot 2021-01-07 at 11.14.41 AM.png > > > When you build the docs locally from the repository using the [run.sh > script|[https://github.com/apache/ignite/blob/master/docs/run.sh]] it seems > that the CSS is not picked up properly which results in a broken UI. > > See the screenshot attached. It used to work before. Probably, we need to > come up with a way of reusing the CSS/header that is stored in the website > repository. > > !Screen Shot 2021-01-07 at 11.14.41 AM.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13962) Ignite Docs: broken UI when building docs locally
[ https://issues.apache.org/jira/browse/IGNITE-13962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-13962: Description: When you build the docs locally from the repository using the run.sh script ([https://github.com/apache/ignite/blob/master/docs/run.sh]) it seems that the CSS is not picked up properly which results in a broken UI. See the screenshot attached. It used to work before. Probably, we need to come up with a way of reusing the CSS/header that is stored in the website repository. !Screen Shot 2021-01-07 at 11.14.41 AM.png! was: When you build the docs locally from the repository using the [run.sh script|[https://github.com/apache/ignite/blob/master/docs/run.sh]] it seems that the CSS is not picked up properly which results in a broken UI. See the screenshot attached. It used to work before. Probably, we need to come up with a way of reusing the CSS/header that is stored in the website repository. !Screen Shot 2021-01-07 at 11.14.41 AM.png! > Ignite Docs: broken UI when building docs locally > - > > Key: IGNITE-13962 > URL: https://issues.apache.org/jira/browse/IGNITE-13962 > Project: Ignite > Issue Type: Bug > Components: documentation, website >Reporter: Denis A. Magda >Priority: Major > Attachments: Screen Shot 2021-01-07 at 11.14.41 AM.png > > > When you build the docs locally from the repository using the run.sh script > ([https://github.com/apache/ignite/blob/master/docs/run.sh]) it seems that > the CSS is not picked up properly which results in a broken UI. > > See the screenshot attached. It used to work before. Probably, we need to > come up with a way of reusing the CSS/header that is stored in the website > repository. > > !Screen Shot 2021-01-07 at 11.14.41 AM.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13962) Ignite Docs: broken UI when building docs locally
[ https://issues.apache.org/jira/browse/IGNITE-13962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda reassigned IGNITE-13962: --- Assignee: Mauricio Stekl > Ignite Docs: broken UI when building docs locally > - > > Key: IGNITE-13962 > URL: https://issues.apache.org/jira/browse/IGNITE-13962 > Project: Ignite > Issue Type: Bug > Components: documentation, website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Attachments: Screen Shot 2021-01-07 at 11.14.41 AM.png > > > When you build the docs locally from the repository using the run.sh script > ([https://github.com/apache/ignite/blob/master/docs/run.sh]) it seems that > the CSS is not picked up properly which results in a broken UI. > > See the screenshot attached. It used to work before. Probably, we need to > come up with a way of reusing the CSS/header that is stored in the website > repository. > > !Screen Shot 2021-01-07 at 11.14.41 AM.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13962) Ignite Docs: broken UI when building docs locally
Denis A. Magda created IGNITE-13962: --- Summary: Ignite Docs: broken UI when building docs locally Key: IGNITE-13962 URL: https://issues.apache.org/jira/browse/IGNITE-13962 Project: Ignite Issue Type: Bug Components: documentation, website Reporter: Denis A. Magda Attachments: Screen Shot 2021-01-07 at 11.14.41 AM.png When you build the docs locally from the repository using the [run.sh script|[https://github.com/apache/ignite/blob/master/docs/run.sh],] it seems that the CSS is not picked up properly which results in a broken UI. See the screenshot attached. It used to work before. Probably, we need to come up with a way of reusing the CSS/header that is stored in the website repository. !Screen Shot 2021-01-07 at 11.14.41 AM.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13523) Ignite Docs: the "layout: toc" tag no longer produces a table of content
[ https://issues.apache.org/jira/browse/IGNITE-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-13523: Component/s: website > Ignite Docs: the "layout: toc" tag no longer produces a table of content > > > Key: IGNITE-13523 > URL: https://issues.apache.org/jira/browse/IGNITE-13523 > Project: Ignite > Issue Type: Bug > Components: documentation, website >Reporter: Denis A. Magda >Priority: Major > Labels: new-docs, website > Fix For: 2.10 > > > The "layout: toc" tag that is used on some index pages of a given section is > not taken into account during the HTML generation process. > For instance, the tag is set in sources for this page: > https://github.com/apache/ignite/blob/master/docs/_docs/security/index.adoc > But the TOC is not produced for the HTML output: > https://ignite.apache.org/docs/latest/security/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13523) Ignite Docs: the "layout: toc" tag no longer produces a table of content
[ https://issues.apache.org/jira/browse/IGNITE-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-13523: Labels: new-docs (was: new-docs website) > Ignite Docs: the "layout: toc" tag no longer produces a table of content > > > Key: IGNITE-13523 > URL: https://issues.apache.org/jira/browse/IGNITE-13523 > Project: Ignite > Issue Type: Bug > Components: documentation, website >Reporter: Denis A. Magda >Priority: Major > Labels: new-docs > Fix For: 2.10 > > > The "layout: toc" tag that is used on some index pages of a given section is > not taken into account during the HTML generation process. > For instance, the tag is set in sources for this page: > https://github.com/apache/ignite/blob/master/docs/_docs/security/index.adoc > But the TOC is not produced for the HTML output: > https://ignite.apache.org/docs/latest/security/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13523) Ignite Docs: the "layout: toc" tag no longer produces a table of content
[ https://issues.apache.org/jira/browse/IGNITE-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-13523: Labels: new-docs website (was: new-docs) > Ignite Docs: the "layout: toc" tag no longer produces a table of content > > > Key: IGNITE-13523 > URL: https://issues.apache.org/jira/browse/IGNITE-13523 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: new-docs, website > Fix For: 2.10 > > > The "layout: toc" tag that is used on some index pages of a given section is > not taken into account during the HTML generation process. > For instance, the tag is set in sources for this page: > https://github.com/apache/ignite/blob/master/docs/_docs/security/index.adoc > But the TOC is not produced for the HTML output: > https://ignite.apache.org/docs/latest/security/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-3690) Log Message Glossary
[ https://issues.apache.org/jira/browse/IGNITE-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-3690: --- Description: It's time for Ignite to create a page that lists ALL the log messages, their common causes, and potential solutions. Probably it makes sense to assign a unique ID for the most well-known errors so that a user is able to look up an error in the glossary quicker. Oracle's example: https://docs.oracle.com/cd/B28359_01/server.111/b28278/e0.htm#ORA-0 was: It's time for Ignite to create a page which lists ALL the log messages, their common causes and potential solutions. Probably it makes sense to assign an unique ID for the most well-know errors so that a user is able to look up an error in the glossary quicker. > Log Message Glossary > > > Key: IGNITE-3690 > URL: https://issues.apache.org/jira/browse/IGNITE-3690 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 1.4 >Reporter: Denis A. Magda >Assignee: Denis A. Magda >Priority: Minor > > It's time for Ignite to create a page that lists ALL the log messages, their > common causes, and potential solutions. > Probably it makes sense to assign a unique ID for the most well-known errors > so that a user is able to look up an error in the glossary quicker. > > Oracle's example: > https://docs.oracle.com/cd/B28359_01/server.111/b28278/e0.htm#ORA-0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-3690) Log Message Glossary
[ https://issues.apache.org/jira/browse/IGNITE-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-3690: --- Fix Version/s: 3.0 > Log Message Glossary > > > Key: IGNITE-3690 > URL: https://issues.apache.org/jira/browse/IGNITE-3690 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 1.4 >Reporter: Denis A. Magda >Assignee: Denis A. Magda >Priority: Minor > Fix For: 3.0 > > > It's time for Ignite to create a page that lists ALL the log messages, their > common causes, and potential solutions. > Probably it makes sense to assign a unique ID for the most well-known errors > so that a user is able to look up an error in the glossary quicker. > > Oracle's example: > https://docs.oracle.com/cd/B28359_01/server.111/b28278/e0.htm#ORA-0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13740) Create a "Getting Started" documentation page for Ignite 3.0
[ https://issues.apache.org/jira/browse/IGNITE-13740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17257113#comment-17257113 ] Denis A. Magda commented on IGNITE-13740: - [~vkulichenko], I've committed a couple of changes: # Renamed Linux to Unix in the tabs since those commands work for Linux and macOS distribution. That's basically the convention we follow: [https://ignite.apache.org/docs/latest/quick-start/java#starting-a-node] # In the *Installing Ignite CLI Tool* section*,* added the Windows (CMD) tab for all three steps. That's a better experience (you select Windows (CMD) Tab once in any places and all the other tabs with the same name will be enabled automatically) even though on step 2 the command is repeated. Please check the Windows (CMD) command from step 3 - (set PATH=%cd%;%PATH%), I couldn't restart to windows now. > Create a "Getting Started" documentation page for Ignite 3.0 > > > Key: IGNITE-13740 > URL: https://issues.apache.org/jira/browse/IGNITE-13740 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Valentin Kulichenko >Assignee: Nikita Safonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Need to create a starting page that describes: > # Installation and upgrade process for manual download and RPM/DEB options. > # How to add optional modules (both Ignite and user-provided). > # How to start a node. > # Any other basic ops appropriate for the "Getting Started" page. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13740) Create a "Getting Started" documentation page for Ignite 3.0
[ https://issues.apache.org/jira/browse/IGNITE-13740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256742#comment-17256742 ] Denis A. Magda commented on IGNITE-13740: - *The Documentation Overview page* * Provide references to all the mentioned IEP *The Getting Started* * Add "Windows" tabs for the OS-specific instructions such as a dir creation and curl-like-download. In all the relevant places. * The CLI reference is hard-coded to the staging. This parameter needs to be set in the _config.yaml file. Use the reference to the binary location and the "version" tag in the sources instead of the hard-coded text. * the export command - calculate the local path automatically and add it to the PATH env variable. Unit + Windows. * Extend the Starting a Node section by showing how to start a two-node cluster. * [~vkulichenko] consider changing the default REST port from 8080 to smth less frequently used. * Next steps - the Ignite CLI commands' table and the HOCON config need to be moved to separate pages and documented thoroughly. > Create a "Getting Started" documentation page for Ignite 3.0 > > > Key: IGNITE-13740 > URL: https://issues.apache.org/jira/browse/IGNITE-13740 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Valentin Kulichenko >Assignee: Nikita Safonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Need to create a starting page that describes: > # Installation and upgrade process for manual download and RPM/DEB options. > # How to add optional modules (both Ignite and user-provided). > # How to start a node. > # Any other basic ops appropriate for the "Getting Started" page. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13941) Poor CLS reported for multiple website pages
Denis A. Magda created IGNITE-13941: --- Summary: Poor CLS reported for multiple website pages Key: IGNITE-13941 URL: https://issues.apache.org/jira/browse/IGNITE-13941 Project: Ignite Issue Type: Bug Components: website Reporter: Denis A. Magda Assignee: Mauricio Stekl Google reported a poor CLS index for multiple pages: [https://search.google.com/search-console/core-web-vitals?resource_id=https%3A%2F%2Fignite.apache.org%2F] The mobile traffic is affected even more severely. Need to address the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13935) Update Ignite docker image description
Denis A. Magda created IGNITE-13935: --- Summary: Update Ignite docker image description Key: IGNITE-13935 URL: https://issues.apache.org/jira/browse/IGNITE-13935 Project: Ignite Issue Type: Improvement Reporter: Denis A. Magda Apache Ignite is redefined as "a distributed database for in-memory speed and high-performance computing". Update the [docker image description|https://hub.docker.com/r/apacheignite/ignite]: # The title needs to say "Apache Ignite - Distributed Database" # The description of the "What is Apache Ignite?" section needs to be identical to a similar section of GitHub's README.md (definition + quick links to docs): https://github.com/apache/ignite -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-13779. --- > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > Attachments: Screen Shot 2020-12-24 at 16.57.21.png, > banner_text_issue.PNG, description_alignment_issue.PNG, features_issue.PNG > > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-13779. - Resolution: Fixed > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > Attachments: Screen Shot 2020-12-24 at 16.57.21.png, > banner_text_issue.PNG, description_alignment_issue.PNG, features_issue.PNG > > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13884) Merge docs from ignite-2.9-docs into 2.9.1
[ https://issues.apache.org/jira/browse/IGNITE-13884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-13884. - Resolution: Fixed > Merge docs from ignite-2.9-docs into 2.9.1 > -- > > Key: IGNITE-13884 > URL: https://issues.apache.org/jira/browse/IGNITE-13884 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Yaroslav Molochkov >Assignee: Yaroslav Molochkov >Priority: Major > Fix For: 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > The documentation contained in ignite-2.9-docs branch needs to be merged into > 2.9.1 branch -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-13884) Merge docs from ignite-2.9-docs into 2.9.1
[ https://issues.apache.org/jira/browse/IGNITE-13884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-13884. --- > Merge docs from ignite-2.9-docs into 2.9.1 > -- > > Key: IGNITE-13884 > URL: https://issues.apache.org/jira/browse/IGNITE-13884 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Yaroslav Molochkov >Assignee: Yaroslav Molochkov >Priority: Major > Fix For: 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > The documentation contained in ignite-2.9-docs branch needs to be merged into > 2.9.1 branch -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13884) Merge docs from ignite-2.9-docs into 2.9.1
[ https://issues.apache.org/jira/browse/IGNITE-13884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17255720#comment-17255720 ] Denis A. Magda commented on IGNITE-13884: - Thanks Mauricio! [~mmuzaf], the docs are live and correct. Closing the ticket. > Merge docs from ignite-2.9-docs into 2.9.1 > -- > > Key: IGNITE-13884 > URL: https://issues.apache.org/jira/browse/IGNITE-13884 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Yaroslav Molochkov >Assignee: Yaroslav Molochkov >Priority: Major > Fix For: 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > The documentation contained in ignite-2.9-docs branch needs to be merged into > 2.9.1 branch -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13884) Merge docs from ignite-2.9-docs into 2.9.1
[ https://issues.apache.org/jira/browse/IGNITE-13884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17255705#comment-17255705 ] Denis A. Magda commented on IGNITE-13884: - [~mstekl], I confirm the issue on my end. The odd thing is that 2.9.1 is selected and displayed as the latest on my local version of the website. So the issue is not reproduced locally. But, for some reason, 2.9.1 is not selected as the default on the production website. Could you step in and help to figure it out? Might it be that this symlink is not handled properly by Apache INFRA? https://github.com/apache/ignite-website/blob/master/docs/latest > Merge docs from ignite-2.9-docs into 2.9.1 > -- > > Key: IGNITE-13884 > URL: https://issues.apache.org/jira/browse/IGNITE-13884 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Yaroslav Molochkov >Assignee: Yaroslav Molochkov >Priority: Major > Fix For: 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > The documentation contained in ignite-2.9-docs branch needs to be merged into > 2.9.1 branch -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13884) Merge docs from ignite-2.9-docs into 2.9.1
[ https://issues.apache.org/jira/browse/IGNITE-13884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17255645#comment-17255645 ] Denis A. Magda commented on IGNITE-13884: - [~mstekl], I merged the patch. [~mmuzaf], [~YAMolochkov], I've seen that you published the 2.9.1 docs on the website but the version is not set as the latest one. When I open the docs, the 2.9.0 is selected by default (meaning it's still the latest). Please merge the changes introduced in the latest patch by Mauricio and republish the docs following the process described here: [https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document#HowtoDocument-PublishingNewVersion] (see Mauricio's previous response for more details). > Merge docs from ignite-2.9-docs into 2.9.1 > -- > > Key: IGNITE-13884 > URL: https://issues.apache.org/jira/browse/IGNITE-13884 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Yaroslav Molochkov >Assignee: Yaroslav Molochkov >Priority: Major > Fix For: 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > The documentation contained in ignite-2.9-docs branch needs to be merged into > 2.9.1 branch -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (IGNITE-13884) Merge docs from ignite-2.9-docs into 2.9.1
[ https://issues.apache.org/jira/browse/IGNITE-13884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda reopened IGNITE-13884: - > Merge docs from ignite-2.9-docs into 2.9.1 > -- > > Key: IGNITE-13884 > URL: https://issues.apache.org/jira/browse/IGNITE-13884 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Yaroslav Molochkov >Assignee: Yaroslav Molochkov >Priority: Major > Fix For: 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > The documentation contained in ignite-2.9-docs branch needs to be merged into > 2.9.1 branch -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17254284#comment-17254284 ] Denis A. Magda commented on IGNITE-13779: - [~mstekl], could you improve the following for the mobile screens (tested on iPhone): * features_issus.png: the multi-tiered storage tab is expanded by default, while the SQL tab needs to be opened when I land on the page * description_alignment_issue.png: can we try to align the description text (that starts with "Gain up to 100x acceleration...") to the left so that the whole width is used? I would do this for descriptions of all the use cases. The titles, Learn Mor buttons and pictures of the use cases can remain centered. * banner_text_issue.png: the "in-memory" and"high-performance" breaks into 2 lines, could you ensure it stays on a single line? I used to use the "nobr" tag for that before but it seems to be depricated > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > Attachments: banner_text_issue.PNG, description_alignment_issue.PNG, > features_issue.PNG > > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-13779: Attachment: banner_text_issue.PNG > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > Attachments: banner_text_issue.PNG, description_alignment_issue.PNG, > features_issue.PNG > > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-13779: Attachment: description_alignment_issue.PNG > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > Attachments: description_alignment_issue.PNG, features_issue.PNG > > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-13779: Attachment: (was: feature_white_block_adjustment.png) > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > Attachments: features_issue.PNG > > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-13779: Attachment: features_issue.PNG > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > Attachments: features_issue.PNG > > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13781) Ignite Website: rework Ignite features section
[ https://issues.apache.org/jira/browse/IGNITE-13781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-13781. - Resolution: Fixed > 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)
[jira] [Closed] (IGNITE-13781) Ignite Website: rework Ignite features section
[ https://issues.apache.org/jira/browse/IGNITE-13781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-13781. --- > 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)
[jira] [Updated] (IGNITE-13853) Add APIs, examples, language selector to the docs menu
[ https://issues.apache.org/jira/browse/IGNITE-13853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-13853: Ignite Flags: (was: Docs Required,Release Notes Required) > Add APIs, examples, language selector to the docs menu > -- > > Key: IGNITE-13853 > URL: https://issues.apache.org/jira/browse/IGNITE-13853 > Project: Ignite > Issue Type: Improvement > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Fix For: 2.9.1 > > Attachments: Screen Shot 2020-12-18 at 12.55.15 PM.png > > > There is user feedback that suggests we need to rework our navigation menus > of the website and docs to improve the discoverability of APIs and examples. > Let's do the following. > > *Ignite Website Top-Level Navigation Menu > ([https://ignite.apache.org)|https://ignite.apache.org)/]* > * Add the "Docs" menu item before the "Features" item. The "Docs" _is a > single link_ (not a dropdown menu) that directs to the root of the latest > technical documentation: [https://ignite.apache.org/docs/latest/] > * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation > (Chinese)" and "APIs" from this menu section. > * Remove "Events" from the top-level menu. Add the items/links from the menu > to the "Community" > > *Technical Documentation Top-Level Navigation Menu > ([https://ignite.apache.org/docs/latest/])* > * Remove the Github icon from the menu > * Add "APIs" after the "version" selector. The menu lists "Java", "C#/.NET", > "C++", "Scala". The "version" selector defines what version of an API is to > be opened. For instance, if a user chooses version "2.9.1" (to be released > soon) then "Java" of that version is to be opened. If instead, the user wants > to see the docs and APIs for "2.9.0", he just needs to selects that version > from the version menu. > * Add "Examples" after the "APIs". Add the following menu items: > ** "Java": [https://github.com/apache/ignite/tree/master/examples] > ** "C#/.NET": > [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] > ** "C++": > [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] > ** "Python": > [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] > ** "Node.JS": > [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] > ** "PHP": > [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] > * Add a language selector drop-down list after the "search" text box. See > how it's implemented here: > [https://www.confluent.io.|https://www.confluent.io./] We'll have just two > menu items there: > ** "English": points out to the root of the main docs > [https://ignite.apache.org/docs/latest/] > ** "Chinese": [https://www.ignite-service.cn/doc/java/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13853) Add APIs, examples, language selector to the docs menu
[ https://issues.apache.org/jira/browse/IGNITE-13853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17254280#comment-17254280 ] Denis A. Magda commented on IGNITE-13853: - Thanks Mauricio! Resolving the ticket. Everything looks great. > Add APIs, examples, language selector to the docs menu > -- > > Key: IGNITE-13853 > URL: https://issues.apache.org/jira/browse/IGNITE-13853 > Project: Ignite > Issue Type: Improvement > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Fix For: 2.9.1 > > Attachments: Screen Shot 2020-12-18 at 12.55.15 PM.png > > > There is user feedback that suggests we need to rework our navigation menus > of the website and docs to improve the discoverability of APIs and examples. > Let's do the following. > > *Ignite Website Top-Level Navigation Menu > ([https://ignite.apache.org)|https://ignite.apache.org)/]* > * Add the "Docs" menu item before the "Features" item. The "Docs" _is a > single link_ (not a dropdown menu) that directs to the root of the latest > technical documentation: [https://ignite.apache.org/docs/latest/] > * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation > (Chinese)" and "APIs" from this menu section. > * Remove "Events" from the top-level menu. Add the items/links from the menu > to the "Community" > > *Technical Documentation Top-Level Navigation Menu > ([https://ignite.apache.org/docs/latest/])* > * Remove the Github icon from the menu > * Add "APIs" after the "version" selector. The menu lists "Java", "C#/.NET", > "C++", "Scala". The "version" selector defines what version of an API is to > be opened. For instance, if a user chooses version "2.9.1" (to be released > soon) then "Java" of that version is to be opened. If instead, the user wants > to see the docs and APIs for "2.9.0", he just needs to selects that version > from the version menu. > * Add "Examples" after the "APIs". Add the following menu items: > ** "Java": [https://github.com/apache/ignite/tree/master/examples] > ** "C#/.NET": > [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] > ** "C++": > [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] > ** "Python": > [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] > ** "Node.JS": > [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] > ** "PHP": > [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] > * Add a language selector drop-down list after the "search" text box. See > how it's implemented here: > [https://www.confluent.io.|https://www.confluent.io./] We'll have just two > menu items there: > ** "English": points out to the root of the main docs > [https://ignite.apache.org/docs/latest/] > ** "Chinese": [https://www.ignite-service.cn/doc/java/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13853) Add APIs, examples, language selector to the docs menu
[ https://issues.apache.org/jira/browse/IGNITE-13853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-13853. - Resolution: Fixed > Add APIs, examples, language selector to the docs menu > -- > > Key: IGNITE-13853 > URL: https://issues.apache.org/jira/browse/IGNITE-13853 > Project: Ignite > Issue Type: Improvement > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Fix For: 2.9.1 > > Attachments: Screen Shot 2020-12-18 at 12.55.15 PM.png > > > There is user feedback that suggests we need to rework our navigation menus > of the website and docs to improve the discoverability of APIs and examples. > Let's do the following. > > *Ignite Website Top-Level Navigation Menu > ([https://ignite.apache.org)|https://ignite.apache.org)/]* > * Add the "Docs" menu item before the "Features" item. The "Docs" _is a > single link_ (not a dropdown menu) that directs to the root of the latest > technical documentation: [https://ignite.apache.org/docs/latest/] > * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation > (Chinese)" and "APIs" from this menu section. > * Remove "Events" from the top-level menu. Add the items/links from the menu > to the "Community" > > *Technical Documentation Top-Level Navigation Menu > ([https://ignite.apache.org/docs/latest/])* > * Remove the Github icon from the menu > * Add "APIs" after the "version" selector. The menu lists "Java", "C#/.NET", > "C++", "Scala". The "version" selector defines what version of an API is to > be opened. For instance, if a user chooses version "2.9.1" (to be released > soon) then "Java" of that version is to be opened. If instead, the user wants > to see the docs and APIs for "2.9.0", he just needs to selects that version > from the version menu. > * Add "Examples" after the "APIs". Add the following menu items: > ** "Java": [https://github.com/apache/ignite/tree/master/examples] > ** "C#/.NET": > [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] > ** "C++": > [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] > ** "Python": > [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] > ** "Node.JS": > [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] > ** "PHP": > [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] > * Add a language selector drop-down list after the "search" text box. See > how it's implemented here: > [https://www.confluent.io.|https://www.confluent.io./] We'll have just two > menu items there: > ** "English": points out to the root of the main docs > [https://ignite.apache.org/docs/latest/] > ** "Chinese": [https://www.ignite-service.cn/doc/java/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-13853) Add APIs, examples, language selector to the docs menu
[ https://issues.apache.org/jira/browse/IGNITE-13853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-13853. --- > Add APIs, examples, language selector to the docs menu > -- > > Key: IGNITE-13853 > URL: https://issues.apache.org/jira/browse/IGNITE-13853 > Project: Ignite > Issue Type: Improvement > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Fix For: 2.9.1 > > Attachments: Screen Shot 2020-12-18 at 12.55.15 PM.png > > > There is user feedback that suggests we need to rework our navigation menus > of the website and docs to improve the discoverability of APIs and examples. > Let's do the following. > > *Ignite Website Top-Level Navigation Menu > ([https://ignite.apache.org)|https://ignite.apache.org)/]* > * Add the "Docs" menu item before the "Features" item. The "Docs" _is a > single link_ (not a dropdown menu) that directs to the root of the latest > technical documentation: [https://ignite.apache.org/docs/latest/] > * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation > (Chinese)" and "APIs" from this menu section. > * Remove "Events" from the top-level menu. Add the items/links from the menu > to the "Community" > > *Technical Documentation Top-Level Navigation Menu > ([https://ignite.apache.org/docs/latest/])* > * Remove the Github icon from the menu > * Add "APIs" after the "version" selector. The menu lists "Java", "C#/.NET", > "C++", "Scala". The "version" selector defines what version of an API is to > be opened. For instance, if a user chooses version "2.9.1" (to be released > soon) then "Java" of that version is to be opened. If instead, the user wants > to see the docs and APIs for "2.9.0", he just needs to selects that version > from the version menu. > * Add "Examples" after the "APIs". Add the following menu items: > ** "Java": [https://github.com/apache/ignite/tree/master/examples] > ** "C#/.NET": > [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] > ** "C++": > [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] > ** "Python": > [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] > ** "Node.JS": > [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] > ** "PHP": > [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] > * Add a language selector drop-down list after the "search" text box. See > how it's implemented here: > [https://www.confluent.io.|https://www.confluent.io./] We'll have just two > menu items there: > ** "English": points out to the root of the main docs > [https://ignite.apache.org/docs/latest/] > ** "Chinese": [https://www.ignite-service.cn/doc/java/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13884) Merge docs from ignite-2.9-docs into 2.9.1
[ https://issues.apache.org/jira/browse/IGNITE-13884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253795#comment-17253795 ] Denis A. Magda commented on IGNITE-13884: - [~YAMolochkov], the patch with the fix and your changes is merged. Try to publish the docs yourself, following the instructions updated by Mauricio. Ask a committer/PMC member that is closest to you to publish the changes on the website. If you prefer, I or Mauricio can release the docs too but tomorrow is the last day and then we go on holidays until December 28th. > Merge docs from ignite-2.9-docs into 2.9.1 > -- > > Key: IGNITE-13884 > URL: https://issues.apache.org/jira/browse/IGNITE-13884 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Yaroslav Molochkov >Assignee: Yaroslav Molochkov >Priority: Major > Fix For: 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > The documentation contained in ignite-2.9-docs branch needs to be merged into > 2.9.1 branch -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13884) Merge docs from ignite-2.9-docs into 2.9.1
[ https://issues.apache.org/jira/browse/IGNITE-13884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253616#comment-17253616 ] Denis A. Magda commented on IGNITE-13884: - [~YAMolochkov], understood. I merged the patch. [~mauri...@gridgain.com], I tried to build the 2.9.1 docs locally with this command (./build.sh --version=2.9.1 --github-branch=ignite-2.9.1 --latest) and spotted several issues: * The "2.9.1" version didn't appear in the versions selector from the header of the doc. * the "NOINDEX" tag is not set for the pages of the previous 2.9.0 version. Please help to address these issues. > Merge docs from ignite-2.9-docs into 2.9.1 > -- > > Key: IGNITE-13884 > URL: https://issues.apache.org/jira/browse/IGNITE-13884 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Yaroslav Molochkov >Assignee: Yaroslav Molochkov >Priority: Major > Fix For: 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > The documentation contained in ignite-2.9-docs branch needs to be merged into > 2.9.1 branch -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13884) Merge docs from ignite-2.9-docs into 2.9.1
[ https://issues.apache.org/jira/browse/IGNITE-13884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253535#comment-17253535 ] Denis A. Magda commented on IGNITE-13884: - [~YAMolochkov], the commits history looks accurate to me but do we really need to merge all of them? Considering that the 2.9.1 branch is created from the master, you need to cherry-pick into 2.9.1 only those documentation commits that were added into the master after 2.9.1 creation time. > Merge docs from ignite-2.9-docs into 2.9.1 > -- > > Key: IGNITE-13884 > URL: https://issues.apache.org/jira/browse/IGNITE-13884 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Yaroslav Molochkov >Assignee: Yaroslav Molochkov >Priority: Major > Fix For: 2.9.1 > > Time Spent: 10m > Remaining Estimate: 0h > > The documentation contained in ignite-2.9-docs branch needs to be merged into > 2.9.1 branch -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13876) Update documentation for 2.9.1 release
[ https://issues.apache.org/jira/browse/IGNITE-13876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253141#comment-17253141 ] Denis A. Magda commented on IGNITE-13876: - [~YAMolochkov], I'll appreciate if you join this discussion and share your thoughts as a release manager: http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Allowing-commits-to-a-released-branch-for-documentation-purposes-td50764.html > Update documentation for 2.9.1 release > -- > > Key: IGNITE-13876 > URL: https://issues.apache.org/jira/browse/IGNITE-13876 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Yaroslav Molochkov >Assignee: Yaroslav Molochkov >Priority: Critical > Fix For: 2.9.1 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > The update should reflect changes made to system views(BINARY_METADATA and > METASTORAGE) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-13881) Set up redirects from readme.io to the new Ignite docs
[ https://issues.apache.org/jira/browse/IGNITE-13881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-13881. --- > Set up redirects from readme.io to the new Ignite docs > -- > > Key: IGNITE-13881 > URL: https://issues.apache.org/jira/browse/IGNITE-13881 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Denis A. Magda >Assignee: Denis A. Magda >Priority: Critical > > Google indexed a lot of the readme.io pages and now it's safe to enable > redirects from the legacy to the new documentation location. > > 1) Export all the docs and store them in the Ignite master just for > reference. It's already reported that some docs were not migrated from the > legacy location. > > 2) Remove all the pages and versions from readme, and set up the redirect > rules: > [/docs/(.*)$ -> > https://ignite.apache.org/docs/latest/|https://apacheignite.readme.io/docs/mesos-deployment] > [/v.*/docs/(.*)$ -> > https://ignite.apache.org/docs/latest/|https://apacheignite.readme.io/docs/mesos-deployment] > > 3) Add a custom 404 page that says the following: > Title: Apache Ignite Documentation Is Moved > Description: Apache Ignite documentation is moved to the ignite.apache.org > website! Now, you can find all the required information in a single place: > [https://ignite.apache.org/docs/latest/] > > 4) Create an overview page on readme.io that says the docs were moved to the > new location > Title: Apache Ignite Documentation > Description: Apache Ignite documentation is moved to the ignite.apache.org > website! Now, you can find all the required information in a single place: > [https://ignite.apache.org/docs/latest/] > > 5) Make sure the indexing is disabled for readme.io -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13881) Set up redirects from readme.io to the new Ignite docs
[ https://issues.apache.org/jira/browse/IGNITE-13881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253131#comment-17253131 ] Denis A. Magda commented on IGNITE-13881: - A contributor who is going to work on this ticket can find the archive with the legacy docs in this wiki section: [https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document#HowtoDocument-Overview] The pages were removed from the readme.io. We're shutting down that portal gradually. > Set up redirects from readme.io to the new Ignite docs > -- > > Key: IGNITE-13881 > URL: https://issues.apache.org/jira/browse/IGNITE-13881 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Denis A. Magda >Assignee: Denis A. Magda >Priority: Critical > > Google indexed a lot of the readme.io pages and now it's safe to enable > redirects from the legacy to the new documentation location. > > 1) Export all the docs and store them in the Ignite master just for > reference. It's already reported that some docs were not migrated from the > legacy location. > > 2) Remove all the pages and versions from readme, and set up the redirect > rules: > [/docs/(.*)$ -> > https://ignite.apache.org/docs/latest/|https://apacheignite.readme.io/docs/mesos-deployment] > [/v.*/docs/(.*)$ -> > https://ignite.apache.org/docs/latest/|https://apacheignite.readme.io/docs/mesos-deployment] > > 3) Add a custom 404 page that says the following: > Title: Apache Ignite Documentation Is Moved > Description: Apache Ignite documentation is moved to the ignite.apache.org > website! Now, you can find all the required information in a single place: > [https://ignite.apache.org/docs/latest/] > > 4) Create an overview page on readme.io that says the docs were moved to the > new location > Title: Apache Ignite Documentation > Description: Apache Ignite documentation is moved to the ignite.apache.org > website! Now, you can find all the required information in a single place: > [https://ignite.apache.org/docs/latest/] > > 5) Make sure the indexing is disabled for readme.io -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13881) Set up redirects from readme.io to the new Ignite docs
[ https://issues.apache.org/jira/browse/IGNITE-13881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-13881. - Resolution: Fixed > Set up redirects from readme.io to the new Ignite docs > -- > > Key: IGNITE-13881 > URL: https://issues.apache.org/jira/browse/IGNITE-13881 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Denis A. Magda >Assignee: Denis A. Magda >Priority: Critical > > Google indexed a lot of the readme.io pages and now it's safe to enable > redirects from the legacy to the new documentation location. > > 1) Export all the docs and store them in the Ignite master just for > reference. It's already reported that some docs were not migrated from the > legacy location. > > 2) Remove all the pages and versions from readme, and set up the redirect > rules: > [/docs/(.*)$ -> > https://ignite.apache.org/docs/latest/|https://apacheignite.readme.io/docs/mesos-deployment] > [/v.*/docs/(.*)$ -> > https://ignite.apache.org/docs/latest/|https://apacheignite.readme.io/docs/mesos-deployment] > > 3) Add a custom 404 page that says the following: > Title: Apache Ignite Documentation Is Moved > Description: Apache Ignite documentation is moved to the ignite.apache.org > website! Now, you can find all the required information in a single place: > [https://ignite.apache.org/docs/latest/] > > 4) Create an overview page on readme.io that says the docs were moved to the > new location > Title: Apache Ignite Documentation > Description: Apache Ignite documentation is moved to the ignite.apache.org > website! Now, you can find all the required information in a single place: > [https://ignite.apache.org/docs/latest/] > > 5) Make sure the indexing is disabled for readme.io -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13585) Ignite Docs: Port AWS and GCE deployment docs from readme.io
[ https://issues.apache.org/jira/browse/IGNITE-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253128#comment-17253128 ] Denis A. Magda commented on IGNITE-13585: - A contributor who is going to work on this ticket can find the archive with the legacy docs in this wiki section: [https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document#HowtoDocument-Overview] The pages were removed from the readme.io. We're shutting down that portal gradually. > Ignite Docs: Port AWS and GCE deployment docs from readme.io > > > Key: IGNITE-13585 > URL: https://issues.apache.org/jira/browse/IGNITE-13585 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: Denis A. Magda >Priority: Critical > Labels: new-docs > Fix For: 2.10 > > > We forgot to port the following pages from readme: > * AWS Deployment: https://apacheignite.readme.io/docs/aws-deployment > * GCE Deployment: > https://apacheignite.readme.io/docs/google-compute-deployment > * RPM installation instructions: > https://apacheignite.readme.io/docs/rpm-and-deb-setup > Move the pages to the new docs and update the references on the Ignite > downloads page sot that they point to the new docs: > https://ignite.apache.org/download.cgi -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13528) Ignite Docs: port generic instructions for Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-13528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253130#comment-17253130 ] Denis A. Magda commented on IGNITE-13528: - A contributor who is going to work on this ticket can find the archive with the legacy docs in this wiki section: [https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document#HowtoDocument-Overview] The pages were removed from the readme.io. We're shutting down that portal gradually. > Ignite Docs: port generic instructions for Kubernetes > - > > Key: IGNITE-13528 > URL: https://issues.apache.org/jira/browse/IGNITE-13528 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: new-docs > Fix For: 2.10 > > > The legacy readme.io-based docs had these generic instructions that didn't > make it to the new docs engine: > https://apacheignite.readme.io/docs/generic-configuration > We need to merge all those pages into a single documentation page "Generic > Kubernetes Deployment" that needs to be placed under the "Installation" -> > "Kubernetes" section of the new docs: > https://ignite.apache.org/docs/latest/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13688) Ignite Docs: Port Checkpointing Mapping from readme.io
[ https://issues.apache.org/jira/browse/IGNITE-13688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253126#comment-17253126 ] Denis A. Magda commented on IGNITE-13688: - A contributor who is going to work on this ticket can find the archive with the legacy docs in this wiki section: [https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document#HowtoDocument-Overview] The pages were removed from the readme.io. We're shutting down that portal gradually. > Ignite Docs: Port Checkpointing Mapping from readme.io > - > > Key: IGNITE-13688 > URL: https://issues.apache.org/jira/browse/IGNITE-13688 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: YuJue Li >Priority: Major > Labels: new-docs > Fix For: 2.10 > > > The content in the link below is missing from the new version of the document: > [https://apacheignite.readme.io/docs/continuous-mapping] > [https://apacheignite.readme.io/docs/checkpointing] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13651) Ignite Docs: Port Apache Zeppelin docs from readme.io
[ https://issues.apache.org/jira/browse/IGNITE-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253127#comment-17253127 ] Denis A. Magda commented on IGNITE-13651: - A contributor who is going to work on this ticket can find the archive with the legacy docs in this wiki section: [https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document#HowtoDocument-Overview] The pages were removed from the readme.io. We're shutting down that portal gradually. > Ignite Docs: Port Apache Zeppelin docs from readme.io > - > > Key: IGNITE-13651 > URL: https://issues.apache.org/jira/browse/IGNITE-13651 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: YuJue Li >Priority: Minor > Labels: new-docs > Fix For: 2.10 > > > The content in the link below is missing from the new version of the document: > [https://apacheignite-sql.readme.io/docs/apache-zeppelin] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13773) Ignite Docs: Port SQL Tooling from readme.io
[ https://issues.apache.org/jira/browse/IGNITE-13773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253125#comment-17253125 ] Denis A. Magda commented on IGNITE-13773: - A contributor who is going to work on this ticket can find the archive with the legacy docs in this wiki section: [https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document#HowtoDocument-Overview] The pages were removed from the readme.io. We're shutting down that portal gradually. > Ignite Docs: Port SQL Tooling from readme.io > > > Key: IGNITE-13773 > URL: https://issues.apache.org/jira/browse/IGNITE-13773 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: YuJue Li >Priority: Major > Labels: new-docs > Fix For: 2.10 > > > The content in the link below is missing from the new version of the document: > [https://apacheignite-sql.readme.io/docs/sql-tooling] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13853) Add APIs, examples, language selector to the docs menu
[ https://issues.apache.org/jira/browse/IGNITE-13853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253094#comment-17253094 ] Denis A. Magda commented on IGNITE-13853: - [~mstekl], thanks, exactly what we need! There is one minor thing that we missed. When someone selects an examples repo from the "Examples" menu, the repo needs to be opened in a new tab. Right now, it's opened in the same time and we're loosing the docs sessions. > Add APIs, examples, language selector to the docs menu > -- > > Key: IGNITE-13853 > URL: https://issues.apache.org/jira/browse/IGNITE-13853 > Project: Ignite > Issue Type: Improvement > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Fix For: 2.9.1 > > Attachments: Screen Shot 2020-12-18 at 12.55.15 PM.png > > > There is user feedback that suggests we need to rework our navigation menus > of the website and docs to improve the discoverability of APIs and examples. > Let's do the following. > > *Ignite Website Top-Level Navigation Menu > ([https://ignite.apache.org)|https://ignite.apache.org)/]* > * Add the "Docs" menu item before the "Features" item. The "Docs" _is a > single link_ (not a dropdown menu) that directs to the root of the latest > technical documentation: [https://ignite.apache.org/docs/latest/] > * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation > (Chinese)" and "APIs" from this menu section. > * Remove "Events" from the top-level menu. Add the items/links from the menu > to the "Community" > > *Technical Documentation Top-Level Navigation Menu > ([https://ignite.apache.org/docs/latest/])* > * Remove the Github icon from the menu > * Add "APIs" after the "version" selector. The menu lists "Java", "C#/.NET", > "C++", "Scala". The "version" selector defines what version of an API is to > be opened. For instance, if a user chooses version "2.9.1" (to be released > soon) then "Java" of that version is to be opened. If instead, the user wants > to see the docs and APIs for "2.9.0", he just needs to selects that version > from the version menu. > * Add "Examples" after the "APIs". Add the following menu items: > ** "Java": [https://github.com/apache/ignite/tree/master/examples] > ** "C#/.NET": > [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] > ** "C++": > [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] > ** "Python": > [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] > ** "Node.JS": > [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] > ** "PHP": > [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] > * Add a language selector drop-down list after the "search" text box. See > how it's implemented here: > [https://www.confluent.io.|https://www.confluent.io./] We'll have just two > menu items there: > ** "English": points out to the root of the main docs > [https://ignite.apache.org/docs/latest/] > ** "Chinese": [https://www.ignite-service.cn/doc/java/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13881) Set up redirects from readme.io to the new Ignite docs
Denis A. Magda created IGNITE-13881: --- Summary: Set up redirects from readme.io to the new Ignite docs Key: IGNITE-13881 URL: https://issues.apache.org/jira/browse/IGNITE-13881 Project: Ignite Issue Type: Improvement Components: documentation Reporter: Denis A. Magda Assignee: Denis A. Magda Google indexed a lot of the readme.io pages and now it's safe to enable redirects from the legacy to the new documentation location. 1) Export all the docs and store them in the Ignite master just for reference. It's already reported that some docs were not migrated from the legacy location. 2) Remove all the pages and versions from readme, and set up the redirect rules: [/docs/(.*)$ -> https://ignite.apache.org/docs/latest/|https://apacheignite.readme.io/docs/mesos-deployment] [/v.*/docs/(.*)$ -> https://ignite.apache.org/docs/latest/|https://apacheignite.readme.io/docs/mesos-deployment] 3) Add a custom 404 page that says the following: Title: Apache Ignite Documentation Is Moved Description: Apache Ignite documentation is moved to the ignite.apache.org website! Now, you can find all the required information in a single place: [https://ignite.apache.org/docs/latest/] 4) Create an overview page on readme.io that says the docs were moved to the new location Title: Apache Ignite Documentation Description: Apache Ignite documentation is moved to the ignite.apache.org website! Now, you can find all the required information in a single place: [https://ignite.apache.org/docs/latest/] 5) Make sure the indexing is disabled for readme.io -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13876) Update documentation for 2.9.1 release
[ https://issues.apache.org/jira/browse/IGNITE-13876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17252897#comment-17252897 ] Denis A. Magda commented on IGNITE-13876: - [~YAMolochkov] merge the docs to the "ignite-2.9.1" release branch. The "ignite-2.9-docs" branch was created only because there is the rule that no changes can be merged to a release branch such as "ignite-2.9" after a release happens. While the docs are always updated to address feedback. I'll start a separate discussion to rethink this rule. > Update documentation for 2.9.1 release > -- > > Key: IGNITE-13876 > URL: https://issues.apache.org/jira/browse/IGNITE-13876 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Yaroslav Molochkov >Assignee: Yaroslav Molochkov >Priority: Critical > Fix For: 2.9.1 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > The update should reflect changes made to system views(BINARY_METADATA and > METASTORAGE) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13522) Ignite Docs: Issues with the left-side navigation bar
[ https://issues.apache.org/jira/browse/IGNITE-13522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-13522. - Resolution: Fixed > Ignite Docs: Issues with the left-side navigation bar > - > > Key: IGNITE-13522 > URL: https://issues.apache.org/jira/browse/IGNITE-13522 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: new-docs > Fix For: 2.10 > > > There are several issues related to the left-side navigation menu: > # The navigation menu folds automatically. To reproduce - click on the > "Performance and Troubleshooting" -> "Handling Exceptions" page. The menu > will fold back. > # Make sure the menu behaves properly when you open second-level pages. For > instance, try "Extensions and Integrations"->"Ignite for > Spark"->"Installation" to ensure the menu is unfolded properly. > # The navigation menu is scrolled up automatically. Select "Performance and > Troubleshooting"->"Handling Exceptions" page. The page will be opened and the > navigation menu will be scrolled up again. > # Make sure that the menu is unfolded automatically when a reader opens the > page directly using its full address. Try this page: > https://ignite.apache.org/docs/latest/extensions-and-integrations/ignite-for-spark/ignite-dataframe > # When you select any section of a page using the *right navigation menu* > then the left navigation menu's position will be changed automatically (it > will be either scrolled up or down). To reproduce, select the "Configuring > Memory" -> "Memory Architecture" page with the left-side navigation menu. > Then, select the "Memory Defragmentation" section with the right-hand side > menu. Both the left and right-side menus will be scrolled down. This > shouldn't happen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-13522) Ignite Docs: Issues with the left-side navigation bar
[ https://issues.apache.org/jira/browse/IGNITE-13522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-13522. --- > Ignite Docs: Issues with the left-side navigation bar > - > > Key: IGNITE-13522 > URL: https://issues.apache.org/jira/browse/IGNITE-13522 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: new-docs > Fix For: 2.10 > > > There are several issues related to the left-side navigation menu: > # The navigation menu folds automatically. To reproduce - click on the > "Performance and Troubleshooting" -> "Handling Exceptions" page. The menu > will fold back. > # Make sure the menu behaves properly when you open second-level pages. For > instance, try "Extensions and Integrations"->"Ignite for > Spark"->"Installation" to ensure the menu is unfolded properly. > # The navigation menu is scrolled up automatically. Select "Performance and > Troubleshooting"->"Handling Exceptions" page. The page will be opened and the > navigation menu will be scrolled up again. > # Make sure that the menu is unfolded automatically when a reader opens the > page directly using its full address. Try this page: > https://ignite.apache.org/docs/latest/extensions-and-integrations/ignite-for-spark/ignite-dataframe > # When you select any section of a page using the *right navigation menu* > then the left navigation menu's position will be changed automatically (it > will be either scrolled up or down). To reproduce, select the "Configuring > Memory" -> "Memory Architecture" page with the left-side navigation menu. > Then, select the "Memory Defragmentation" section with the right-hand side > menu. Both the left and right-side menus will be scrolled down. This > shouldn't happen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13853) Add APIs, examples, language selector to the docs menu
[ https://issues.apache.org/jira/browse/IGNITE-13853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-13853: Attachment: Screen Shot 2020-12-18 at 12.55.15 PM.png > Add APIs, examples, language selector to the docs menu > -- > > Key: IGNITE-13853 > URL: https://issues.apache.org/jira/browse/IGNITE-13853 > Project: Ignite > Issue Type: Improvement > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Fix For: 2.9.1 > > Attachments: Screen Shot 2020-12-18 at 12.55.15 PM.png > > > There is user feedback that suggests we need to rework our navigation menus > of the website and docs to improve the discoverability of APIs and examples. > Let's do the following. > > *Ignite Website Top-Level Navigation Menu > ([https://ignite.apache.org)|https://ignite.apache.org)/]* > * Add the "Docs" menu item before the "Features" item. The "Docs" _is a > single link_ (not a dropdown menu) that directs to the root of the latest > technical documentation: [https://ignite.apache.org/docs/latest/] > * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation > (Chinese)" and "APIs" from this menu section. > * Remove "Events" from the top-level menu. Add the items/links from the menu > to the "Community" > > *Technical Documentation Top-Level Navigation Menu > ([https://ignite.apache.org/docs/latest/])* > * Remove the Github icon from the menu > * Add "APIs" after the "version" selector. The menu lists "Java", "C#/.NET", > "C++", "Scala". The "version" selector defines what version of an API is to > be opened. For instance, if a user chooses version "2.9.1" (to be released > soon) then "Java" of that version is to be opened. If instead, the user wants > to see the docs and APIs for "2.9.0", he just needs to selects that version > from the version menu. > * Add "Examples" after the "APIs". Add the following menu items: > ** "Java": [https://github.com/apache/ignite/tree/master/examples] > ** "C#/.NET": > [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] > ** "C++": > [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] > ** "Python": > [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] > ** "Node.JS": > [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] > ** "PHP": > [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] > * Add a language selector drop-down list after the "search" text box. See > how it's implemented here: > [https://www.confluent.io.|https://www.confluent.io./] We'll have just two > menu items there: > ** "English": points out to the root of the main docs > [https://ignite.apache.org/docs/latest/] > ** "Chinese": [https://www.ignite-service.cn/doc/java/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13853) Add APIs, examples, language selector to the docs menu
[ https://issues.apache.org/jira/browse/IGNITE-13853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17252052#comment-17252052 ] Denis A. Magda commented on IGNITE-13853: - [~mstekl], thanks, I merged the patch and noted the following: * The language selector is broken. See the screenshot in the attachment. It's reproduced in Safari and Chrome. * "Examples" are listed under the "APIs" menu. I meant to put "Examples" as a separate menu category that goes after the "APIs". > Add APIs, examples, language selector to the docs menu > -- > > Key: IGNITE-13853 > URL: https://issues.apache.org/jira/browse/IGNITE-13853 > Project: Ignite > Issue Type: Improvement > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Fix For: 2.9.1 > > > There is user feedback that suggests we need to rework our navigation menus > of the website and docs to improve the discoverability of APIs and examples. > Let's do the following. > > *Ignite Website Top-Level Navigation Menu > ([https://ignite.apache.org)|https://ignite.apache.org)/]* > * Add the "Docs" menu item before the "Features" item. The "Docs" _is a > single link_ (not a dropdown menu) that directs to the root of the latest > technical documentation: [https://ignite.apache.org/docs/latest/] > * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation > (Chinese)" and "APIs" from this menu section. > * Remove "Events" from the top-level menu. Add the items/links from the menu > to the "Community" > > *Technical Documentation Top-Level Navigation Menu > ([https://ignite.apache.org/docs/latest/])* > * Remove the Github icon from the menu > * Add "APIs" after the "version" selector. The menu lists "Java", "C#/.NET", > "C++", "Scala". The "version" selector defines what version of an API is to > be opened. For instance, if a user chooses version "2.9.1" (to be released > soon) then "Java" of that version is to be opened. If instead, the user wants > to see the docs and APIs for "2.9.0", he just needs to selects that version > from the version menu. > * Add "Examples" after the "APIs". Add the following menu items: > ** "Java": [https://github.com/apache/ignite/tree/master/examples] > ** "C#/.NET": > [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] > ** "C++": > [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] > ** "Python": > [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] > ** "Node.JS": > [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] > ** "PHP": > [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] > * Add a language selector drop-down list after the "search" text box. See > how it's implemented here: > [https://www.confluent.io.|https://www.confluent.io./] We'll have just two > menu items there: > ** "English": points out to the root of the main docs > [https://ignite.apache.org/docs/latest/] > ** "Chinese": [https://www.ignite-service.cn/doc/java/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17251457#comment-17251457 ] Denis A. Magda commented on IGNITE-13779: - [~mstekl], excellent, just merged it! We're almost done. Let me finalize the text and think about the buttons from the use cases menu. > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > Attachments: feature_white_block_adjustment.png > > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13659) TDE - Phase 3. Documentation
[ https://issues.apache.org/jira/browse/IGNITE-13659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250517#comment-17250517 ] Denis A. Magda commented on IGNITE-13659: - [~nsafonov], could you please help with the review here? Just in case, that's for Ignite 2.10 and not Ignite 2.9.1. So, we can work on this task at a comfortable pace depending on how much time you can allocate for the contribution. > TDE - Phase 3. Documentation > > > Key: IGNITE-13659 > URL: https://issues.apache.org/jira/browse/IGNITE-13659 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Labels: IEP-18, tde-phase-3 > Fix For: 2.10 > > Attachments: html-ver.zip > > Time Spent: 1h > Remaining Estimate: 0h > > Write documentation on the cache encryption key rotation function. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13853) Add APIs, examples, language selector to the docs menu
[ https://issues.apache.org/jira/browse/IGNITE-13853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-13853: Description: There is user feedback that suggests we need to rework our navigation menus of the website and docs to improve the discoverability of APIs and examples. Let's do the following. *Ignite Website Top-Level Navigation Menu ([https://ignite.apache.org)|https://ignite.apache.org)/]* * Add the "Docs" menu item before the "Features" item. The "Docs" _is a single link_ (not a dropdown menu) that directs to the root of the latest technical documentation: [https://ignite.apache.org/docs/latest/] * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation (Chinese)" and "APIs" from this menu section. * Remove "Events" from the top-level menu. Add the items/links from the menu to the "Community" *Technical Documentation Top-Level Navigation Menu ([https://ignite.apache.org/docs/latest/])* * Remove the Github icon from the menu * Add "APIs" after the "version" selector. The menu lists "Java", "C#/.NET", "C++", "Scala". The "version" selector defines what version of an API is to be opened. For instance, if a user chooses version "2.9.1" (to be released soon) then "Java" of that version is to be opened. If instead, the user wants to see the docs and APIs for "2.9.0", he just needs to selects that version from the version menu. * Add "Examples" after the "APIs". Add the following menu items: ** "Java": [https://github.com/apache/ignite/tree/master/examples] ** "C#/.NET": [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] ** "C++": [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] ** "Python": [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] ** "Node.JS": [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] ** "PHP": [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] * Add a language selector drop-down list after the "search" text box. See how it's implemented here: [https://www.confluent.io.|https://www.confluent.io./] We'll have just two menu items there: ** "English": points out to the root of the main docs [https://ignite.apache.org/docs/latest/] ** "Chinese": [https://www.ignite-service.cn/doc/java/] was: There is user feedback that suggests we need to rework our navigation menus of the website and docs to improve the discoverability of APIs and examples. Let's do the following. *Ignite Website Top-Level Navigation Menu ([https://ignite.apache.org)|https://ignite.apache.org)/]* * Add the "Docs" menu item before the "Features" item. The "Docs" _is a single link_ (not a dropdown menu) that directs to the root of the latest technical documentation: [https://ignite.apache.org/docs/latest/] * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation (Chinese)" and "APIs" from this menu section. * Remove "Events" from the top-level menu. Add the items/links from the menu to the "Community" *Technical Documentation Top-Level Navigation Menu ([https://ignite.apache.org/docs/latest/])* * Remove the Github icon from the menu * Add "APIs" after the "version" selector. The menu lists "JavaDocs", "C#/.NET", "C++", "Scala". The "version" selector defines what version of an API is to be opened. For instance, if a user chooses version "2.9.1" (to be released soon) then "JavaDocs" of that version is to be opened. If instead, the user wants to see the docs and APIs for "2.9.0", he just needs to selects that version from the version menu. * Add "Examples" after the "APIs". Add the following menu items: ** "Java": [https://github.com/apache/ignite/tree/master/examples] ** "C#/.NET": [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] ** "C++": [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] ** "Python": [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] ** "Node.JS": [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] ** "PHP": [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] * Add a language selector drop-down list after the "search" text box. See how it's implemented here: [https://www.confluent.io.|https://www.confluent.io./] We'll have just two menu items there: ** "English": points out to the root of the main docs [https://ignite.apache.org/docs/latest/] ** "Chinese": [https://www.ignite-service.cn/doc/java/] > Add APIs, examples, language selector to the docs menu > -- > > Key: IGNITE-13853 > URL: https://issues.apache.org/jira/browse/IGNITE-13853 > Project: Ignite > Issue Type: Improvement >
[jira] [Updated] (IGNITE-13853) Add APIs, examples, language selector to the docs menu
[ https://issues.apache.org/jira/browse/IGNITE-13853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-13853: Description: There is user feedback that suggests we need to rework our navigation menus of the website and docs to improve the discoverability of APIs and examples. Let's do the following. *Ignite Website Top-Level Navigation Menu ([https://ignite.apache.org)|https://ignite.apache.org)/]* * Add the "Docs" menu item before the "Features" item. The "Docs" _is a single link_ (not a dropdown menu) that directs to the root of the latest technical documentation: [https://ignite.apache.org/docs/latest/] * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation (Chinese)" and "APIs" from this menu section. * Remove "Events" from the top-level menu. Add the items/links from the menu to the "Community" *Technical Documentation Top-Level Navigation Menu ([https://ignite.apache.org/docs/latest/])* * Remove the Github icon from the menu * Add "APIs" after the "version" selector. The menu lists "JavaDocs", "C#/.NET", "C++", "Scala". The "version" selector defines what version of an API is to be opened. For instance, if a user chooses version "2.9.1" (to be released soon) then "JavaDocs" of that version is to be opened. If instead, the user wants to see the docs and APIs for "2.9.0", he just needs to selects that version from the version menu. * Add "Examples" after the "APIs". Add the following menu items: ** "Java": [https://github.com/apache/ignite/tree/master/examples] ** "C#/.NET": [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] ** "C++": [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] ** "Python": [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] ** "Node.JS": [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] ** "PHP": [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] * Add a language selector drop-down list after the "search" text box. See how it's implemented here: [https://www.confluent.io.|https://www.confluent.io./] We'll have just two menu items there: ** "English": points out to the root of the main docs [https://ignite.apache.org/docs/latest/] ** "Chinese": [https://www.ignite-service.cn/doc/java/] was: There is user feedback that suggests we need to rework our navigation menus of the website and docs to improve the discoverability of APIs and examples. Let's do the following. *Ignite Website Top-Level Navigation Menu ([https://ignite.apache.org)|https://ignite.apache.org)/]* * Add the "Docs" menu item to the menu placing it before the "Features" item. The "Docs" _is a single link_ (no dropdown menu) that directs to the root of the latest technical documentation: [https://ignite.apache.org/docs/latest/] * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation (Chinese)" and "APIs" from this menu section. * Remove "Events" from the top-level menu. Add the items/links from the menu to the "Community" *Technical Documentation Top-Level Navigation Menu ([https://ignite.apache.org/docs/latest/])* * Remove the Github icon from the menu * Add "APIs" after the "version" selector. The menu lists "JavaDocs", "C#/.NET", "C++", "Scala". The "version" selector defines what version of an API is to be opened. For instance, if a user chooses version "2.9.1" (to be released soon) then "JavaDocs" of that version is to be opened. If instead, the user wants to see the docs and APIs for "2.9.0", he just needs to selects that version from the version menu. * Add "Examples" after the "APIs". Add the following menu items: ** "Java": [https://github.com/apache/ignite/tree/master/examples] ** "C#/.NET": [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] ** "C++": [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] ** "Python": [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] ** "Node.JS": [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] ** "PHP": [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] * Add a language selector drop-down list after the "search" text box. See how it's implemented here: [https://www.confluent.io.|https://www.confluent.io./] We'll have just two menu items there: ** "English": points out to the root of the main docs [https://ignite.apache.org/docs/latest/] ** "Chinese": https://www.ignite-service.cn/doc/java/ > Add APIs, examples, language selector to the docs menu > -- > > Key: IGNITE-13853 > URL: https://issues.apache.org/jira/browse/IGNITE-13853 > Project: Ignite >
[jira] [Created] (IGNITE-13853) Add APIs, examples, language selector to the docs menu
Denis A. Magda created IGNITE-13853: --- Summary: Add APIs, examples, language selector to the docs menu Key: IGNITE-13853 URL: https://issues.apache.org/jira/browse/IGNITE-13853 Project: Ignite Issue Type: Improvement Components: documentation, website Reporter: Denis A. Magda Fix For: 2.9.1 There is user feedback that suggests we need to rework our navigation menus of the website and docs to improve the discoverability of APIs and examples. Let's do the following. *Ignite Website Top-Level Navigation Menu ([https://ignite.apache.org)|https://ignite.apache.org)/]* * Add the "Docs" menu item to the menu placing it before the "Features" item. The "Docs" _is a single link_ (no dropdown menu) that directs to the root of the latest technical documentation: [https://ignite.apache.org/docs/latest/] * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation (Chinese)" and "APIs" from this menu section. * Remove "Events" from the top-level menu. Add the items/links from the menu to the "Community" *Technical Documentation Top-Level Navigation Menu ([https://ignite.apache.org/docs/latest/])* * Remove the Github icon from the menu * Add "APIs" after the "version" selector. The menu lists "JavaDocs", "C#/.NET", "C++", "Scala". The "version" selector defines what version of an API is to be opened. For instance, if a user chooses version "2.9.1" (to be released soon) then "JavaDocs" of that version is to be opened. If instead, the user wants to see the docs and APIs for "2.9.0", he just needs to selects that version from the version menu. * Add "Examples" after the "APIs". Add the following menu items: ** "Java": [https://github.com/apache/ignite/tree/master/examples] ** "C#/.NET": [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] ** "C++": [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] ** "Python": [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] ** "Node.JS": [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] ** "PHP": [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] * Add a language selector drop-down list after the "search" text box. See how it's implemented here: [https://www.confluent.io.|https://www.confluent.io./] We'll have just two menu items there: ** "English": points out to the root of the main docs [https://ignite.apache.org/docs/latest/] ** "Chinese": https://www.ignite-service.cn/doc/java/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13853) Add APIs, examples, language selector to the docs menu
[ https://issues.apache.org/jira/browse/IGNITE-13853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17249466#comment-17249466 ] Denis A. Magda commented on IGNITE-13853: - [~mstekl], could you please help with this task? > Add APIs, examples, language selector to the docs menu > -- > > Key: IGNITE-13853 > URL: https://issues.apache.org/jira/browse/IGNITE-13853 > Project: Ignite > Issue Type: Improvement > Components: documentation, website >Reporter: Denis A. Magda >Priority: Major > Fix For: 2.9.1 > > > There is user feedback that suggests we need to rework our navigation menus > of the website and docs to improve the discoverability of APIs and examples. > Let's do the following. > > *Ignite Website Top-Level Navigation Menu > ([https://ignite.apache.org)|https://ignite.apache.org)/]* > * Add the "Docs" menu item to the menu placing it before the "Features" > item. The "Docs" _is a single link_ (no dropdown menu) that directs to the > root of the latest technical documentation: > [https://ignite.apache.org/docs/latest/] > * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation > (Chinese)" and "APIs" from this menu section. > * Remove "Events" from the top-level menu. Add the items/links from the menu > to the "Community" > > *Technical Documentation Top-Level Navigation Menu > ([https://ignite.apache.org/docs/latest/])* > * Remove the Github icon from the menu > * Add "APIs" after the "version" selector. The menu lists "JavaDocs", > "C#/.NET", "C++", "Scala". The "version" selector defines what version of an > API is to be opened. For instance, if a user chooses version "2.9.1" (to be > released soon) then "JavaDocs" of that version is to be opened. If instead, > the user wants to see the docs and APIs for "2.9.0", he just needs to selects > that version from the version menu. > * Add "Examples" after the "APIs". Add the following menu items: > ** "Java": [https://github.com/apache/ignite/tree/master/examples] > ** "C#/.NET": > [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] > ** "C++": > [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] > ** "Python": > [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] > ** "Node.JS": > [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] > ** "PHP": > [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] > * Add a language selector drop-down list after the "search" text box. See > how it's implemented here: > [https://www.confluent.io.|https://www.confluent.io./] We'll have just two > menu items there: > ** "English": points out to the root of the main docs > [https://ignite.apache.org/docs/latest/] > ** "Chinese": https://www.ignite-service.cn/doc/java/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17248243#comment-17248243 ] Denis A. Magda commented on IGNITE-13779: - [~mstekl], merged, looks really nice! Some other thoughts: * How about making the height of the white block with a feature description adjustable (with the exception that it cannot go beyond some maximum height)? Tried to elucidate with the screenshot in the ticket's attachment area above. * Were you able to test how the features section is displayed on mobile screens? Just in case, check how snowflake's approach looks like (https://www.snowflake.com/). Compare the WAYS TO GET STARTED section on a desktop and mobile. The desktop version is similar to our solution and their mobile arrangement should fit our needs. > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > Attachments: feature_white_block_adjustment.png > > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-13779: Attachment: feature_white_block_adjustment.png > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > Attachments: feature_white_block_adjustment.png > > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-13779: Attachment: Screen Shot 2020-12-10 at 6.28.19 PM.png > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17247603#comment-17247603 ] Denis A. Magda edited comment on IGNITE-13779 at 12/11/20, 2:35 AM: [~mstekl], btw, remember we decided to fix the position of the main menu (header) so that it doesn't disappear even when you scroll a page down? The behavior similar to what we have for the Ignite docs: [https://ignite.apache.org/docs/latest/persistence/external-storage] Let's do it for the rest of the website pages? Also, how about making the height of the white block with a feature description adjustable with the exception that it cannot go beyond some maximum height? Tried to elucidate with the screenshot in the ticket's attachment area above was (Author: dmagda): [~mstekl], btw, remember we decided to fix the position of the main menu (header) so that it doesn't disappear even when you scroll a page down? The behavior similar to what we have for the Ignite docs: https://ignite.apache.org/docs/latest/persistence/external-storage Let's do it for the rest of the website pages? > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-13779: Attachment: (was: Screen Shot 2020-12-10 at 6.28.19 PM.png) > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17247603#comment-17247603 ] Denis A. Magda commented on IGNITE-13779: - [~mstekl], btw, remember we decided to fix the position of the main menu (header) so that it doesn't disappear even when you scroll a page down? The behavior similar to what we have for the Ignite docs: https://ignite.apache.org/docs/latest/persistence/external-storage Let's do it for the rest of the website pages? > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-13780) Ignite Website: update use cases section
[ https://issues.apache.org/jira/browse/IGNITE-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-13780. --- > Ignite Website: update use cases section > > > Key: IGNITE-13780 > URL: https://issues.apache.org/jira/browse/IGNITE-13780 > Project: Ignite > Issue Type: Sub-task > Components: website >Reporter: Denis A. Magda >Assignee: Denis A. Magda >Priority: Critical > > Presently, the website introduces 2 use cases of Ignite - "Ignite as a cache" > and "Ignite as a digital integration hub". After defining Ignite as a > distributed database, we need to update this website section featuring the > following 3 primary usage scenarios of Ignite. > *How Most Developers Use Apache Ignite* > 1. _Applications Acceleration & Data Caching_ > Gain up to 100x acceleration for existing applications using Ignite as an > in-memory cache over a single or multiple backend systems. The cache that you > can query with SQL, transact and compute on. > 2. _Distributed Database for Mixed Workloads_ > Store and process petabytes of operational and historical data using Ignite > as a distributed database for mixed workloads. The database that scales up > and out across available memory, disk, and Intel Optane storage. > 3. _High-Performance Compute Cluster_ > Deploy and execute your kilobyte-size code over petabytes of data. Turn your > Ignite cluster into a limitless supercomputer for low-latency calculations, > complex analytics, and machine learning. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13780) Ignite Website: update use cases section
[ https://issues.apache.org/jira/browse/IGNITE-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-13780. - Resolution: Fixed > Ignite Website: update use cases section > > > Key: IGNITE-13780 > URL: https://issues.apache.org/jira/browse/IGNITE-13780 > Project: Ignite > Issue Type: Sub-task > Components: website >Reporter: Denis A. Magda >Assignee: Denis A. Magda >Priority: Critical > > Presently, the website introduces 2 use cases of Ignite - "Ignite as a cache" > and "Ignite as a digital integration hub". After defining Ignite as a > distributed database, we need to update this website section featuring the > following 3 primary usage scenarios of Ignite. > *How Most Developers Use Apache Ignite* > 1. _Applications Acceleration & Data Caching_ > Gain up to 100x acceleration for existing applications using Ignite as an > in-memory cache over a single or multiple backend systems. The cache that you > can query with SQL, transact and compute on. > 2. _Distributed Database for Mixed Workloads_ > Store and process petabytes of operational and historical data using Ignite > as a distributed database for mixed workloads. The database that scales up > and out across available memory, disk, and Intel Optane storage. > 3. _High-Performance Compute Cluster_ > Deploy and execute your kilobyte-size code over petabytes of data. Turn your > Ignite cluster into a limitless supercomputer for low-latency calculations, > complex analytics, and machine learning. -- This message was sent by Atlassian Jira (v8.3.4#803005)
