Re: [Discussion] Apache Ignite Blog Migration

[Mauricio Stekl]

Hey, these plans for the blog migration and other updates look awesome! If
you need any help or assistance along the way, just give me a shout. I'd be
more than happy to lend a hand.

Best,
Mauricio Stekl

On Mon, Mar 13, 2023 at 3:07 AM Erlan Aytpaev  wrote:

> Hi Igniters!
>
> I will be able to implement a new design and features.
>
> On Sat, Mar 11, 2023 at 12:53 AM Kseniya Romanova 
> wrote:
>
> > Hi Igniters!
> >
> > Recently Apache INFRA notified that they would no longer support Roller
> as
> > a blogging platform. We must copy all the posts from
> > https://blogs.apache.org/ignite/ and put them on Ignite website with the
> > URL ignite.apache.org/blog.
> >
> > The only tech requirement is this URL which will be used later for
> > aggregating our posts to some Apache feeds. So we can keep the same
> > principle for the blog as for all other pages - updating them via PR on
> > GitHub.
> >
> > I will gladly create the ticket and keep watching this migration.
> > Please see the possible design for the blog page:
> > https://github.com/apache/ignite-website/blob/master/images/blog.jpg
> >
> > As for the top menu, I suggest moving the "Resources"
> > https://ignite.apache.org/resources.html to the top. Now, this item is
> in
> > the "Get Started" which is inconvenient. Please see here
> >
> >
> https://github.com/apache/ignite-website/blob/master/images/menue%20resources.png
> > And here's how the Get Started will look after this change
> >
> >
> https://github.com/apache/ignite-website/blob/master/images/menue%20started.png
> >
> >
> > WDYT?
> >
> > Cheers,
> > Kseniya
> >
>

Re: New Ignite Website: Released and Check the Dev Instructions

[Mauricio Stekl]

Thank you, Erlan. I merged your first commit into the prod website.
Welcome to the Ignite community!

Best,
Mauricio

On Tue, Dec 14, 2021 at 4:40 AM Erlan Aytpaev  wrote:

> Hi Igniters,
>
> I've added the "Extensions" section on the "Downloads" page. Please review
> my pull request https://github.com/apache/ignite-website/pull/91.
> This is my first commit. And I'm going to continue contributing updates on
> the website.
>
> Best Regards,
> Erlan.
>
> On Tue, Dec 14, 2021 at 9:55 AM Mauricio Stekl 
> wrote:
>
> > Hi,
> > I noticed the "Extensions" section was not merged correctly into the
> > Downloads page. I have created a ticket
> > https://issues.apache.org/jira/browse/IGNITE-16112, and we'll be solving
> > this as soon as possible. My apologies for the inconvenience
> >
> > Best,
> > Mauricio
> >
> > On Mon, Dec 13, 2021 at 4:46 PM Denis Magda  wrote:
> >
> > > Igniters,
> > >
> > > Please welcome the new Ignite website: https://ignite.apache.org
> > > Hope you like it!
> > >
> > > The website uses gulpjs to simplify the dev/maintenance cycles, thus, I
> > > would encourage all of you who release Ignite (and update the downloads
> > > page) or edit any other pages to check the updated instruction:
> > > https://cwiki.apache.org/confluence/display/IGNITE/Website+Development
> > >
> > >
> > > -
> > > Denis
> > >
> >
>

Re: New Ignite Website: Released and Check the Dev Instructions

[Mauricio Stekl]

Hi,
I noticed the "Extensions" section was not merged correctly into the
Downloads page. I have created a ticket
https://issues.apache.org/jira/browse/IGNITE-16112, and we'll be solving
this as soon as possible. My apologies for the inconvenience

Best,
Mauricio

On Mon, Dec 13, 2021 at 4:46 PM Denis Magda  wrote:

> Igniters,
>
> Please welcome the new Ignite website: https://ignite.apache.org
> Hope you like it!
>
> The website uses gulpjs to simplify the dev/maintenance cycles, thus, I
> would encourage all of you who release Ignite (and update the downloads
> page) or edit any other pages to check the updated instruction:
> https://cwiki.apache.org/confluence/display/IGNITE/Website+Development
>
>
> -
> Denis
>

Re: Ignite Website UI and UX improvements

[Mauricio Stekl]

Hi,
I completed merging the code and the new website is live now.  Also updated
the wiki instructions to build and test the site locally:
https://cwiki.apache.org/confluence/display/IGNITE/Website+Development

Please let me know if you have any questions or comments.

Best,
Mauricio


On Mon, Dec 13, 2021 at 9:31 AM Mauricio Stekl  wrote:

> Hi all,
>
> I'm happy to let you know the new website is ready, and I will start
> merging the code and do the launch today. Please avoid committing new
> changes to the current website until this process is ready.
>
> I will share an update once it's live.
>
> Thanks!
>
> Mauricio
>
> On Tue, Nov 9, 2021 at 9:00 PM Denis Magda  wrote:
>
>> Igniters,
>>
>> I'm pleased to share a piece of good news with you. The next version of
>> the
>> website is ready and deployed on staging:
>>
>> https://test2.heavenweb.ru/
>> username: apache
>> passwd: ignite
>>
>> In the course of the next 5-10 days, I'll be collaborating with the design
>> and dev teams on required improvements. Please pass on any feedback that
>> you might have.
>>
>> -
>> Denis
>>
>>
>> On Mon, Sep 13, 2021 at 8:46 AM Denis Magda  wrote:
>>
>> > Hi Saikat,
>> >
>> > Thanks for the suggestions. I'll pass them over to the design team.
>> >
>> >
>> > -
>> > Denis
>> >
>> >
>> > On Sun, Sep 12, 2021 at 10:43 AM Saikat Maitra > >
>> > wrote:
>> >
>> >> Hi Denis, Kseniya
>> >>
>> >> Thank you for leading the effort in designing and revamping the
>> website.
>> >>
>> >> I wanted to share a few thoughts and ideas:
>> >> 1. Will it be suitable if the rocket exhaust fire/gases are replaced
>> with
>> >> the Ignite spark from the Ignite logo. I really like the red Ignite
>> spark.
>> >> It may symbolize that the rocket's journey is powered / fueled by
>> Ignite.
>> >> 2. Can we rewrite the sentence "We appreciate any help and track every
>> >> contribution" to "We appreciate any help and value every contribution".
>> >> The
>> >> word track felt a bit intrusive like if the user's actions are
>> monitored.
>> >> 3. Similarly here we may replace the word track "Top contributors are
>> >> tracked at Github" to "Top contributors @ Github".
>> >> 4. If it is ok with PMC members and committers then we can use face
>> shots
>> >> for committers and PMC members like here
>> >> https://kafka.apache.org/committers.
>> >> It will be nice to see a face and recognize them in person when we all
>> >> meet
>> >> again in person.
>> >>
>> >> Warm regards,
>> >> Saikat
>> >>
>> >>
>> >>
>> >> On Wed, Sep 8, 2021 at 11:34 AM Denis Magda  wrote:
>> >>
>> >> > Folks, an update for you. We keep prototyping new pages and you can
>> >> find a
>> >> > reference to the mockups in the ticket.
>> >> >
>> >> > Need to hear your opinion on one of the mockups. Kseniya and I worked
>> >> with
>> >> > the design studio on a Community page, and this is what we have
>> >> prepared so
>> >> > far:
>> >> > https://app.moqups.com/4WR00aUZ8z/view/page/a7e1c85f0
>> >> >
>> >> > The page tells a brief story about the project, has a "meet the
>> >> community"
>> >> > section, explains how to start contributing or ask a question. All
>> those
>> >> > sections will have anchors and will be added as separate menu items
>> for
>> >> > quick navigation.
>> >> >
>> >> > Any suggestions before we send the mockup to editors and designers?
>> >> >
>> >> > --
>> >> > Denis
>> >> >
>> >> > -
>> >> > Denis
>> >> >
>> >> > On Mon, Aug 16, 2021 at 4:35 PM Denis Magda 
>> wrote:
>> >> >
>> >> > > Folks,
>> >> > >
>> >> > > 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've just started bringing those changes to life:
>> >> > > https://issues.apache.org/jira/browse/IGNITE-15320
>> >> > >
>> >> > > I'll keep you posted on the progress and intermediate results. Let
>> me
>> >> > know
>> >> > > if:
>> >> > > a) you have any questions or suggestions
>> >> > > b) you want to be involved in this effort and brief the team (the
>> same
>> >> > > vendor) on the structure/content of the community and other pages.
>> I
>> >> meet
>> >> > > with the folks several days a week to help them finish the project
>> by
>> >> > late
>> >> > > September- early October.
>> >> > >
>> >> > > --
>> >> > > Denis
>> >> > >
>> >> > > -
>> >> > > Denis
>> >> > >
>> >> >
>> >>
>> >
>>
>

Re: Ignite Website UI and UX improvements

[Mauricio Stekl]

Hi all,

I'm happy to let you know the new website is ready, and I will start
merging the code and do the launch today. Please avoid committing new
changes to the current website until this process is ready.

I will share an update once it's live.

Thanks!

Mauricio

On Tue, Nov 9, 2021 at 9:00 PM Denis Magda  wrote:

> Igniters,
>
> I'm pleased to share a piece of good news with you. The next version of the
> website is ready and deployed on staging:
>
> https://test2.heavenweb.ru/
> username: apache
> passwd: ignite
>
> In the course of the next 5-10 days, I'll be collaborating with the design
> and dev teams on required improvements. Please pass on any feedback that
> you might have.
>
> -
> Denis
>
>
> On Mon, Sep 13, 2021 at 8:46 AM Denis Magda  wrote:
>
> > Hi Saikat,
> >
> > Thanks for the suggestions. I'll pass them over to the design team.
> >
> >
> > -
> > Denis
> >
> >
> > On Sun, Sep 12, 2021 at 10:43 AM Saikat Maitra 
> > wrote:
> >
> >> Hi Denis, Kseniya
> >>
> >> Thank you for leading the effort in designing and revamping the website.
> >>
> >> I wanted to share a few thoughts and ideas:
> >> 1. Will it be suitable if the rocket exhaust fire/gases are replaced
> with
> >> the Ignite spark from the Ignite logo. I really like the red Ignite
> spark.
> >> It may symbolize that the rocket's journey is powered / fueled by
> Ignite.
> >> 2. Can we rewrite the sentence "We appreciate any help and track every
> >> contribution" to "We appreciate any help and value every contribution".
> >> The
> >> word track felt a bit intrusive like if the user's actions are
> monitored.
> >> 3. Similarly here we may replace the word track "Top contributors are
> >> tracked at Github" to "Top contributors @ Github".
> >> 4. If it is ok with PMC members and committers then we can use face
> shots
> >> for committers and PMC members like here
> >> https://kafka.apache.org/committers.
> >> It will be nice to see a face and recognize them in person when we all
> >> meet
> >> again in person.
> >>
> >> Warm regards,
> >> Saikat
> >>
> >>
> >>
> >> On Wed, Sep 8, 2021 at 11:34 AM Denis Magda  wrote:
> >>
> >> > Folks, an update for you. We keep prototyping new pages and you can
> >> find a
> >> > reference to the mockups in the ticket.
> >> >
> >> > Need to hear your opinion on one of the mockups. Kseniya and I worked
> >> with
> >> > the design studio on a Community page, and this is what we have
> >> prepared so
> >> > far:
> >> > https://app.moqups.com/4WR00aUZ8z/view/page/a7e1c85f0
> >> >
> >> > The page tells a brief story about the project, has a "meet the
> >> community"
> >> > section, explains how to start contributing or ask a question. All
> those
> >> > sections will have anchors and will be added as separate menu items
> for
> >> > quick navigation.
> >> >
> >> > Any suggestions before we send the mockup to editors and designers?
> >> >
> >> > --
> >> > Denis
> >> >
> >> > -
> >> > Denis
> >> >
> >> > On Mon, Aug 16, 2021 at 4:35 PM Denis Magda 
> wrote:
> >> >
> >> > > Folks,
> >> > >
> >> > > 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've just started bringing those changes to life:
> >> > > https://issues.apache.org/jira/browse/IGNITE-15320
> >> > >
> >> > > I'll keep you posted on the progress and intermediate results. Let
> me
> >> > know
> >> > > if:
> >> > > a) you have any questions or suggestions
> >> > > b) you want to be involved in this effort and brief the team (the
> same
> >> > > vendor) on the structure/content of the community and other pages. I
> >> meet
> >> > > with the folks several days a week to help them finish the project
> by
> >> > late
> >> > > September- early October.
> >> > >
> >> > > --
> >> > > Denis
> >> > >
> >> > > -
> >> > > Denis
> >> > >
> >> >
> >>
> >
>

Re: [DISCUSSION] Documentation feedback button

[Mauricio Stekl]

Hi,
Just ss a heads up, I added the button to the online docs template and
rebuilt the latest version & 3.0.0a docs.
Please let me know if you have any questions or suggestions.


Best,
Mauricio Stekl




On Fri, Aug 6, 2021 at 12:17 PM Denis Magda  wrote:

> There is no such a way. Notifications are always sent to an email address
> used by a bugyard account. Anyway, I don’t see any harm in this - usually
> you’ll get a 1-2 notifications a week. Plus, many more community members
> prepare documentation for features they build these days, thus, it’s good
> to receive feedback for your work.
>
>
> On Friday, August 6, 2021, Ivan Pavlukhin  wrote:
>
> > Is there an easy way to subscribe personally for such notifications? I
> > forsee complaints that the majority of developers are not interested
> > in documentation feedback notifications.
> >
> > 2021-08-04 12:40 GMT+03:00, Denis Magda :
> > > Nikita,
> > >
> > > We created a bugyard account for the Ignite community. I'm suggesting
> > using
> > > a shared account bound to 'dev@ignite.apache.org'. That will allow
> > everyone
> > > on the dev list to receive and process documentation feedback.
> > > https://svn.apache.org/repos/private/pmc/ignite/credentials/bugyard.io
> > >
> > > Mauricio will add the button to the website shortly. I'll let you
> update
> > > the documentation process.
> > >
> > > --
> > > Denis
> > >
> > >
> > > -
> > > Denis
> > >
> > > On Tue, Jul 27, 2021 at 5:24 PM Nikita Safonov <
> > vlasovpavel2...@gmail.com>
> > > wrote:
> > >
> > >> Hello Igniters,
> > >>
> > >> I would like to proceed with implementing the feedback service for the
> > >> Ignite documentation website.
> > >> If nobody objects, let's start the work.
> > >> The details are described here:
> > >> https://issues.apache.org/jira/browse/IGNITE-15198
> > >>
> > >> With best regards,
> > >> Nikita
> > >>
> > >> ср, 17 мар. 2021 г. в 15:50, Mauricio Stekl :
> > >>
> > >> > Hi,
> > >> > I agree with Nikita, it would be a very simple way of getting
> feedback
> > >> > to
> > >> > improve the documentation.
> > >> > This tool in particular is quite easy to integrate into the online
> > docs
> > >> > template.
> > >> >
> > >> > Best,
> > >> > Mauricio
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > On Tue, Mar 16, 2021 at 4:46 PM Denis Magda 
> > wrote:
> > >> >
> > >> > > Nikita, thanks for starting the conversation. I'll just cast my
> vote
> > >> for
> > >> > > the bugyard.io for its ability to select and comment on a
> specific
> > >> > > problematic point on a documentation page (a paragraph, sentence,
> > >> > picture,
> > >> > > code snippet, etc.). It makes it trivial to share feedback and
> then
> > >> it's
> > >> > > easy to process it on the other side. Those who'd like to
> experience
> > >> it,
> > >> > > click the "Documentation Feedback" button on the GridGain docs:
> > >> > > https://www.gridgain.com/docs/latest/getting-started/what-
> > is-gridgain
> > >> > >
> > >> > > -
> > >> > > Denis
> > >> > >
> > >> > >
> > >> > > On Tue, Mar 16, 2021 at 3:14 PM Никита Сафонов <
> > >> > vlasovpavel2...@gmail.com>
> > >> > > wrote:
> > >> > >
> > >> > > > Hello Igniters,
> > >> > > >
> > >> > > > I would like to propose an enhancement that can significantly
> > >> > > > improve
> > >> > the
> > >> > > > quality of our documentation.
> > >> > > >
> > >> > > > I suggest adding a feedback button (let’s call it a
> «Documentation
> > >> > > > feedback» button) to the web site documentation pages so
> everyone
> > >> could
> > >> > > > leave a comment to what is already published.
> > >> > > >
> > >> > > > The feedback may refer to the Ignite documentation in general or
> > to
> > >> > > > a
> > >> > > > particular section, paragraph, or even term or value.
> > >> > > >
> > >> > > > I do believe that we would harvest dozens and hundreds of ideas,
> > >> > > > suggestions, and observations.
> > >> > > >
> > >> > > > I would also suggest using bugyard.io as a solid service for
> > >> gathering
> > >> > > > feedback (I’m quite familiar with it, it is easy to implement,
> > use,
> > >> and
> > >> > > > maintain).
> > >> > > >
> > >> > > > So folks, what do you think of this?
> > >> > > >
> > >> > > > With best regards,
> > >> > > > Nikita
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
> >
> >
> > --
> >
> > Best regards,
> > Ivan Pavlukhin
> >
>
>
> --
> -
> Denis
>

Re: [DISCUSSION] Documentation feedback button

[Mauricio Stekl]

Hi,
I agree with Nikita, it would be a very simple way of getting feedback to
improve the documentation.
This tool in particular is quite easy to integrate into the online docs
template.

Best,
Mauricio





On Tue, Mar 16, 2021 at 4:46 PM Denis Magda  wrote:

> Nikita, thanks for starting the conversation. I'll just cast my vote for
> the bugyard.io for its ability to select and comment on a specific
> problematic point on a documentation page (a paragraph, sentence, picture,
> code snippet, etc.). It makes it trivial to share feedback and then it's
> easy to process it on the other side. Those who'd like to experience it,
> click the "Documentation Feedback" button on the GridGain docs:
> https://www.gridgain.com/docs/latest/getting-started/what-is-gridgain
>
> -
> Denis
>
>
> On Tue, Mar 16, 2021 at 3:14 PM Никита Сафонов 
> wrote:
>
> > Hello Igniters,
> >
> > I would like to propose an enhancement that can significantly improve the
> > quality of our documentation.
> >
> > I suggest adding a feedback button (let’s call it a «Documentation
> > feedback» button) to the web site documentation pages so everyone could
> > leave a comment to what is already published.
> >
> > The feedback may refer to the Ignite documentation in general or to a
> > particular section, paragraph, or even term or value.
> >
> > I do believe that we would harvest dozens and hundreds of ideas,
> > suggestions, and observations.
> >
> > I would also suggest using bugyard.io as a solid service for gathering
> > feedback (I’m quite familiar with it, it is easy to implement, use, and
> > maintain).
> >
> > So folks, what do you think of this?
> >
> > With best regards,
> > Nikita
> >
>

[jira] [Created] (IGNITE-14287) Ignite Accessibility Check: Broken links

[Mauricio Stekl (Jira)]

Mauricio Stekl created IGNITE-14287:
---

 Summary: Ignite Accessibility Check: Broken links
 Key: IGNITE-14287
 URL: https://issues.apache.org/jira/browse/IGNITE-14287
 Project: Ignite
  Issue Type: Bug
  Components: website
Reporter: Mauricio Stekl
Assignee: Mauricio Stekl
 Attachments: Broken links (Outbound).xlsx

While doing Ignite's usability audit, We have figured out that there's a small 
bunch of broken links on the website, leading to 404 pages. The attached report 
indicates the origin of these.
 
 



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

Enable Lucky Orange and Yandex Metrics on Java API docs

[Mauricio Stekl]

Hi devs,

Per this ticket: https://issues.apache.org/jira/browse/IGNITE-14215, I have
enabled these on the general website and also on the online documentation,
but I am stuck with  adding these metrics to the templates used for API
docs and rebuild them.

Could someone please help?

Thanks in advance.

Mauricio

[jira] [Created] (IGNITE-13988) Version dropdown on docs is not aligned to the right on Safari

[Mauricio Stekl (Jira)]

Mauricio Stekl created IGNITE-13988:
---

 Summary: 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
 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)

Ignite as a Distributed Database - Home Page Updates

[Mauricio Stekl]

Hi Everyone,

After the vote we had a few weeks ago to define Ignite as a distributed
database[1], we stepped forward, with Denis Magda and Nikita Ivanov, to
rework the home page in order to reflect these changes.

During this process we also made improvements to the main navigation for
the website as well as technical documentation. You will notice now there
are direct links to easily access the different APIs and docs translations.

I hope you enjoy the new updates, and please let us know if you wish to
suggest any changes.

Happy New Year!

Regards,
Mauricio Stekl



[1]
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html

Website related tickets on JIRA

[Mauricio Stekl]

Hi Ignite Community,
For those of you who do not know me, my name is Mauricio and I have been
doing contributions related to the website for a long time now. Generally I
have coordinated these updates directly with some community members.
However, for future contributions I would like to see if it is possible to
start creating tickets on JIRA using the 'website' component. This will
help me to better organize the tasks where I can contribute, and, of
course, it will help us all track what is going on around the website.

Please let me know if you have any questions or suggestions. Otherwise I
look forward to seeing those tickets on JIRA.


Thanks.

Mauricio

[jira] [Created] (IGNITE-13157) Upgrade build process for Javadocs

[Mauricio Stekl (Jira)]

Mauricio Stekl created IGNITE-13157:
---

 Summary: Upgrade build process for Javadocs
 Key: IGNITE-13157
 URL: https://issues.apache.org/jira/browse/IGNITE-13157
 Project: Ignite
  Issue Type: Improvement
  Components: documentation
Reporter: Mauricio Stekl
 Attachments: gsc_mobile_errors.png

I am reaching out to you all to see if you could help fix some issues with 
mobile usability in the Javadocs sections for Ignite website.
 
I know you might think most users will not read the API doc using their 
smartphones, and that is true. But as you can see in the attached screenshot 
gsc_mobile_errors.png, we have errors related to mobile usability reported by 
Google itself through GSC. Obviously this affects our performance on search 
results, as Google is giving more and more priority to mobile friendly websites.
For Apache Ignite website we basically have the largest part of the website 
with issues, since we only have around 30 pages mobile friendly, and 1000+ 
pages which are not. 
 
Specifically with Javadocs, the main problem is it contains old html frames for 
layout and navigation, among other markup bad practices, and this would make 
impossible to update any css to be responsive for small screens.  From what I 
was able to find [[1]|https://bugs.openjdk.java.net/browse/JDK-8215599] 
[[2]|https://bugs.openjdk.java.net/browse/JDK-8196202], starting with JDK 9 
there is a '--no-frames' option which fixes this problem. And with version 11 
this option is enabled by default and other features included. You can see here 
how the new layout looks: 
[https://docs.oracle.com/en/java/javase/11/docs/api/index.html]
 
Would it be possible to upgrade Java to version 11 only for building the 
javadocs? This might be a great starting point to fix these problems. Later we 
could update the .css to adjust font sizes and other details.



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

Re: Missing Scaladoc for 2.8.1

[Mauricio Stekl]

Denis,
Not yet. I am sending a PR in a moment with the GA, and also some fixes for
404 errors.

Thanks for the reminder, though.

Best
Mauricio

On Mon, Jun 15, 2020 at 1:21 PM Denis Magda  wrote:

> Mauricio, Nikolay,
>
> Have we added google analytics tags to the new docs? Just checking
> because we used to oversee this step before.
>
> -
> Denis
>
>
> On Mon, Jun 15, 2020 at 12:23 AM Nikolay Izhikov 
> wrote:
>
> > Fixed.
> >
> > > 12 июня 2020 г., в 20:10, Mauricio Stekl 
> > написал(а):
> > >
> > > Hi Nikolay,
> > > I just noticed that the Scaladoc API doc is missing for release 2.8.1.
> I
> > am
> > > getting some 404 alerts for URLs like:
> > > https://ignite.apache.org/releases/latest/scaladoc/scalar/
> > >
> > > Could you please help deploy it back?
> > >
> > > Please let me know if you have any questions.
> > >
> > > Thank you!
> > >
> > > Regards,
> > > Mauricio Stekl
> >
> >
>

Missing Scaladoc for 2.8.1

[Mauricio Stekl]

Hi Nikolay,
I just noticed that the Scaladoc API doc is missing for release 2.8.1. I am
getting some 404 alerts for URLs like:
https://ignite.apache.org/releases/latest/scaladoc/scalar/

Could you please help deploy it back?

Please let me know if you have any questions.

Thank you!

Regards,
Mauricio Stekl

Re: [RESULT] [VOTE] Release Apache Ignite 2.7.5-rc4

[Mauricio Stekl]

Thanks, Dmitriy. Everything looks good to me.




On Tue, Jun 25, 2019 at 6:32 PM Dmitriy Pavlov  wrote:

> Hi Mauricio,
>
> I've applied the patch, Committed revision 1862086. Could you please check
> docs have required SEO changes.
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 24 июн. 2019 г. в 13:58, Dmitriy Pavlov :
>
> > Hi Denis,
> >
> > I see docs now have the correct version.
> >
> > Open issues I list at the end of the document about the release
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-OpenIssues
> >
> > Now issues 3, 5, 6 need to be addressed.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 20 июн. 2019 г. в 16:24, Dmitriy Pavlov :
> >
> >> Hi Denis,
> >> Artem explained to me what to do, but I need permissions for all
> >> supplementary docs to switch version.
> >>
> >> Could you please grant it for
> >> C#/.NET
> >> C++
> >> SQL
> >> Integrations*
> >> Ignite for Spark
> >> Tools
> >> ?
> >>
> >> вт, 11 июн. 2019 г. в 23:21, Dmitriy Pavlov :
> >>
> >>> Thank you, Mauricio,
> >>>
> >>> I'm going to apply this patch on Monday. I will be traveling with
> >>> limited access to the Internet.
> >>>
> >>> I'll also add more explanation on why we should update these tags to
> the
> >>> wiki.
> >>>
> >>> вт, 11 июн. 2019 г. в 20:57, Mauricio Stekl :
> >>>
> >>>> Hi Dmitriy,
> >>>> Yes, that would be enough to set the URL for latest docs.
> >>>>
> >>>> Additionally I usually do some SEO updates to new/old .html files,
> like
> >>>> adding NOINDEX metatag to older version; add canonical URL to latest
> docs;
> >>>> and add GA code.
> >>>>
> >>>> I am attaching a svn patch which includes all these updates, including
> >>>> the .htaccess one.
> >>>>
> >>>>
> >>>> Thanks.
> >>>> Mauricio Stekl
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On Tue, Jun 11, 2019 at 1:38 PM Dmitriy Pavlov 
> >>>> wrote:
> >>>>
> >>>>> Ok, Denis, thank you.
> >>>>>
> >>>>> Garrett, could you please advice me on how to do a copy of 2.7.0 docs
> >>>>> to
> >>>>> 2.7.5? I have an account on the readme.io, so I would like to do it
> >>>>> and
> >>>>> describe in the Release process
> >>>>> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> >>>>>
> >>>>> Mauricio, is my understanding correct?
> >>>>> in the htaccess I can replace
> >>>>>
> >>>>> RewriteRule ^releases/latest/(.*)$ /releases/2.7.0/$1 [L]
> >>>>>
> >>>>> to
> >>>>>
> >>>>> RewriteRule ^releases/latest/(.*)$ /releases/2.7.5/$1 [L]
> >>>>>
> >>>>> and that's it?
> >>>>>
> >>>>> Sincerely
> >>>>> Dmitriy Pavlov
> >>>>>
> >>>>> вт, 11 июн. 2019 г. в 19:26, Denis Magda :
> >>>>>
> >>>>> > Igniters,
> >>>>> >
> >>>>> > We have to create version 2.7.5 for readme.io even if the changes
> >>>>> are
> >>>>> > minimal. That's a general practice. Copying Garrett and Artem who
> can
> >>>>> > facilitate on the documentation end.
> >>>>> >
> >>>>> > Also, feel free to reach out Mauricio (copied) who can help to run
> >>>>> the
> >>>>> > scripts that will make JavaDocs 2.7.5 latest for Ignite website.
> >>>>> >
> >>>>> > -
> >>>>> > Denis
> >>>>> >
> >>>>> >
> >>>>> > On Tue, Jun 11, 2019 at 6:00 AM Dmitriy Pavlov  >
> >>>>> wrote:
> >>>>> >
> >>>>> > > Sorry for the second email. I want to clarify: I've already
> >>>>> uploaded
> >>>>> > > Javadoc,scaladoc,c++ docs (generated). Question is related 

Re: Generate release notes for Apache Ignite 2.3.0

[Mauricio Stekl]

Hi, 
Attached you can find the patch that updates the default docs to v2.3. 

Please merge it into the repo and let me know if you have any question.

Best,
Mauricio




docupdate-release-2.3.0.patch.bz2
Description: BZip2 compressed data



> On Oct 31, 2017, at 14:23, Vladimir Ozerov  wrote:
> 
> Hi Mauricio,
> 
> Could you please generate release notes for AI 2.3.0 and publish them on the 
> site?
> 
> Vladimir.

Optimizations on titles and h1

[Mauricio Stekl]

Hi Igniters, 
I am attaching a patch with keyword optimizations on several page titles and H1 
across the website.

I would appreciate if any of the committers could merge this to the website.  
Please let me know if you have any question.


Thanks in advance. 

Best, 
Mauricio Stekl





h1-and-titles-improvements.patch.bz2
Description: BZip2 compressed data

Re: More SEO and API doc cleanup

[Mauricio Stekl]

Hi Denis, Thanks for taking care of the marge! About the latest doc reference, when a new version is released it would be necessary to do 2 things:1. Update the new version number on the .htaccess file: RewriteRule ^releases/latest/(.*)$ /releases/1.9.0/$1 [L]2. Add the following tag to all .html files:rel="canonical" href="https://ignite.apache.org/releases/latest/LANGUAGE-DIR/FILENAME.html" />Bear in mind to change the url accordingly. For example, for java index version would be: /releases/latest/javadoc/index.htmlThis 2nd step can be done with any simple script. In particular I wrote/use the attached .php scripts which, besides this task, also does other things related to SEO (adding noindex, GA tracking code, etc). It contains some basic comments with instructions.Anyway, I do volunteer to do these 2 simple steps every time a new release is done. Best,Mauricio Stekl

apidocs-scripts.tar.bz2
Description: BZip2 compressed data
On Mar 10, 2017, at 19:37, Denis Magda <dma...@apache.org> wrote:Hello Mauricio,Thanks a lot, I’ve reviewed and merged your changes!	- Setup rewrite rule on .htaccess so latest API doc can have always the same URL ( for example https://ignite.apache.org/releases/latest/javadoc/<https://ignite.apache.org/releases/latest/javadoc/>)  In this case I pointed it to version 1.9.0. This will prevent having to manually change all inbound links every time a new release is done. Also will help search engines to correctly identify the latest documentation that should be listed on results.Many special thanks for this improvement. I wish we did this earlier.BTW, what we need to do to update this latest doc reference when a new version is rolled out? Could you share the instructions?—DenisOn Mar 10, 2017, at 1:54 PM, Mauricio Stekl <mauri...@gridgain.com> wrote:Hello Igniters, I am sending a .patch file attached with some changes related to SEO that I have done to Apache Ignite website. Here are some details: 	- Setup rewrite rule on .htaccess so latest API doc can have always the same URL ( for example https://ignite.apache.org/releases/latest/javadoc/<https://ignite.apache.org/releases/latest/javadoc/>)  In this case I pointed it to version 1.9.0. This will prevent having to manually change all inbound links every time a new release is done. Also will help search engines to correctly identify the latest documentation that should be listed on results.	- Added NOINDEX meta tag to all API documentation for versions <= 1.8.0. This will help crawlers to give more page authority to latest version of the doc, and will avoid indexing more than 25.000 URLs.	- Added canonical url tags and GA tracking code to all .html files for 1.9.0. 	- Updated some anchor tags on the homepage which were linking to the features using only the icons and not the feature's title text.	- Updated sitemap.xml with 1.9.0 URLs.	- Updated the links on navigation so they point to latest version of API documentation.I will appreciate if any of the committers could merge this on website’s repo.Please let me know if you have any question.Thanks in advance.Best,Mauricio Stekl

Clean sitemap.xml for the website

[Mauricio Stekl]

Hello Igniters, 

Based on the SEO analysis we reported earlier, I have cleaned up the 
sitemap.xml for the website, maintaining the amount of URLs to the minimum 
recommended. I am attaching a patch with all the changes

Could any of the committers please apply this patch to the website repo?

Let me know if you have any question.


Best,
Mauricio Stekl





cleaned-up-sitemap.patch.bz2
Description: BZip2 compressed data

Re: Patches for Website

[Mauricio Stekl]

Hi Denis, 

I have updated my local repo and it seems the patch to htaccess was not 
committed. Attached you can find the .patch file just in case you didn’t 
receive it ok.

Thanks.
Mauricio






> On Feb 9, 2017, at 18:37, Denis Magda <dma...@apache.org> wrote:
> 
> Hi Mauricio,
> 
> I’ve committed the changes. Thanks!
> 
> —
> Denis
> 
>> On Feb 9, 2017, at 9:55 AM, Mauricio Stekl <mauri...@gridgain.com> wrote:
>> 
>> Hi Denis, 
>> I am sorry about that. I have now checked out the repo from trunk/ and built 
>> the patches again. These are attached. 
>> Please let me know if you have any other issue.
>> 
>> 
>> Best,
>> Mauricio Stekl
>> 
>> 
>> 
>> 
>> 
>>> On Feb 8, 2017, at 21:52, Denis Magda <dma...@apache.org> wrote:
>>> 
>>> Hi Mauricio,
>>> 
>>> Could you go to the trunk folder of your clone and make the patch from 
>>> there?
>>> 
>>> Presently I can’t merge the changes getting this kind of error:
>>> 
>>> Skipped missing target: 'site/trunk/use-cases/hadoop/hdfs-cache.html'
>>> Skipped missing target: 'site/trunk/use-cases/hadoop/mapreduce.html'
>>> Skipped missing target: 'site/trunk/use-cases/platforms/dotnet.html'
>>> Skipped missing target: 
>>> 'site/trunk/use-cases/spark/shared-memory-layer.html'
>>> Skipped missing target: 'site/trunk/use-cases/spark/sql-queries.html'
>>> Skipped missing target: 'site/trunk/usecases.html'
>>> Summary of conflicts:
>>> Skipped paths: 23376
>>> 
>>> —
>>> Denis
>>> 
>>>> On Feb 8, 2017, at 8:57 AM, Mauricio Stekl <mauri...@gridgain.com> wrote:
>>>> 
>>>> Hi, 
>>>> 
>>>> Attached you can find 2 files with patches fixing some of the SEO issues 
>>>> we reported earlier. 
>>>> 
>>>> One contains the changes to .htaccess to force HTTPS all over the site 
>>>> with 301 redirections.
>>>> 
>>>> The .bz2 file contains the changes to every single html file on the site, 
>>>> adding a canonical URL. And also it adds the GA tracking code to all API 
>>>> documentation, which didn’t contain that JS right now.
>>>> 
>>>> Could any of the committers please apply these to the website?
>>>> 
>>>> Please let me know if you have any question.
>>>> 
>>>> Thanks in advance!
>>>> 
>>>> 
>>>> Mauricio
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>> 
> 

Re: Apache Ignite SEO Audit

[Mauricio Stekl]

No, I’m afraid I can’t use the same file. However it seems there was already a 
GWT account setup for this domain then. So I could be granted access to that 
account instead. Would that be possible?

Thanks.
Mauricio 


> On Jan 23, 2017, at 18:24, Dmitriy Setrakyan <dsetrak...@apache.org> wrote:
> 
> Mauricio, we already have similar file added for google site verification:
> google9276fe2a42313afd.html
> 
> Can you reuse this one?
> 
> D.
> 
> On Mon, Jan 23, 2017 at 12:20 PM, Mauricio Stekl <mauri...@gridgain.com>
> wrote:
> 
>> Hi,
>> In order to setup the Google Webmaster Tools account on ignite.apache.org,
>> I would need to upload the attached .html file to the root of the website.
>> 
>> Could someone with commit privileges help me with this?
>> 
>> Thanks in advance.
>> 
>> Mauricio
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On Jan 19, 2017, at 19:29, Dmitriy Setrakyan <dsetrak...@apache.org>
>> wrote:
>> 
>> Hi Terry, this should not be a problem. I have sent you the credentials
>> privately. Let me know if you need more help.
>> 
>> D.
>> 
>> On Thu, Jan 19, 2017 at 11:35 AM, Terry Erisman <teris...@gridgain.com>
>> wrote:
>> 
>> Hi All,
>> 
>> 
>> 
>> In order to proceed effectively with the SEO audit of the Apache Ignite
>> website, we need admin access to the Google Analytics account for the
>> website. Once we have the Google Analytics account access, we will setup
>> Google Webmaster Tools for the website (it isn't setup currently) which
>> will
>> give us insights into a variety of characteristics of the website.
>> 
>> 
>> 
>> If anyone has any concerns about this, please let me know. I look forward
>> to
>> getting started on this audit.
>> 
>> 
>> 
>> Thanks,
>> 
>> 
>> 
>> Terry
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 

Re: Apache Ignite SEO Audit

[Mauricio Stekl]

Hi Denis, 
Yes, in the docroot of the site so that the file could be access by visiting 
http://ignite.apache.org/googlea0d19c18a89c8306.html 
<http://ignite.apache.org/googlea0d19c18a89c8306.html>

Thanks again.

Mauricio


> On Jan 23, 2017, at 17:23, Denis Magda <dma...@apache.org> wrote:
> 
> Hi Mauricio,
> 
> Do I need to put it under the root folder of the site?
> 
> —
> Denis
> 
>> On Jan 23, 2017, at 12:20 PM, Mauricio Stekl <mauri...@gridgain.com> wrote:
>> 
>> Hi, 
>> In order to setup the Google Webmaster Tools account on ignite.apache.org 
>> <http://ignite.apache.org/>, I would need to upload the attached .html file 
>> to the root of the website. 
>> 
>> Could someone with commit privileges help me with this? 
>> 
>> Thanks in advance. 
>> 
>> Mauricio
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> On Jan 19, 2017, at 19:29, Dmitriy Setrakyan <dsetrak...@apache.org 
>>> <mailto:dsetrak...@apache.org>> wrote:
>>> 
>>> Hi Terry, this should not be a problem. I have sent you the credentials
>>> privately. Let me know if you need more help.
>>> 
>>> D.
>>> 
>>> On Thu, Jan 19, 2017 at 11:35 AM, Terry Erisman <teris...@gridgain.com 
>>> <mailto:teris...@gridgain.com>>
>>> wrote:
>>> 
>>>> Hi All,
>>>> 
>>>> 
>>>> 
>>>> In order to proceed effectively with the SEO audit of the Apache Ignite
>>>> website, we need admin access to the Google Analytics account for the
>>>> website. Once we have the Google Analytics account access, we will setup
>>>> Google Webmaster Tools for the website (it isn't setup currently) which
>>>> will
>>>> give us insights into a variety of characteristics of the website.
>>>> 
>>>> 
>>>> 
>>>> If anyone has any concerns about this, please let me know. I look forward
>>>> to
>>>> getting started on this audit.
>>>> 
>>>> 
>>>> 
>>>> Thanks,
>>>> 
>>>> 
>>>> 
>>>> Terry
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>> 
> 

Re: Apache Ignite SEO Audit

[Mauricio Stekl]

Hi, In order to setup the Google Webmaster Tools account on ignite.apache.org, I would need to upload the attached .html file to the root of the website. Could someone with commit privileges help me with this? Thanks in advance. Mauriciogoogle-site-verification: googlea0d19c18a89c8306.htmlOn Jan 19, 2017, at 19:29, Dmitriy Setrakyan  wrote:Hi Terry, this should not be a problem. I have sent you the credentialsprivately. Let me know if you need more help.D.On Thu, Jan 19, 2017 at 11:35 AM, Terry Erisman wrote:Hi All,In order to proceed effectively with the SEO audit of the Apache Ignitewebsite, we need admin access to the Google Analytics account for thewebsite. Once we have the Google Analytics account access, we will setupGoogle Webmaster Tools for the website (it isn't setup currently) whichwillgive us insights into a variety of characteristics of the website.If anyone has any concerns about this, please let me know. I look forwardtogetting started on this audit.Thanks,Terry