[website] Fix file path in build_docs

[waytrue17]

Description

The restricted-website-build-master pipeline is failing due to files not found issue:https://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/restricted-website-build-master/activity.
By inspecting the build, the missing files blog, ecosystem and features were moved from html/ to html/pages.
This PR fix the file paths in build_docs

Checklist

Essentials

• PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
• Changes are complete (i.e. I finished coding on this PR)
• All changes have test coverage
• Code is well-documented

Changes

• Feature1, tests, (and when applicable, API doc)
• Feature2, tests, (and when applicable, API doc)

Comments

• If this change is a backward incompatible change, why must this change be made.
• Interesting edge cases to note here

[mxnet-bot]

Hey @waytrue17 , Thanks for submitting the PR
All tests are already queued to run once. If tests fail, you can trigger one or more tests again with the following commands:

• To trigger all jobs: @mxnet-bot run ci [all]
• To trigger specific jobs: @mxnet-bot run ci [job1, job2]

---

CI supported jobs: [windows-cpu, centos-cpu, miscellaneous, windows-gpu, website, unix-cpu, unix-gpu, clang, sanity, edge, centos-gpu]

---

Note:
Only following 3 categories can trigger CI :PR Author, MXNet Committer, Jenkins Admin.
All CI tests must pass before the PR can be merged.

[waytrue17]

@ys2843 @mseth10 Could you please review?

[ys2843]

Looks good. 1 quick question, does it work if replacing blog ecosystem features with pages in the first for loop?

[waytrue17]

Looks good. 1 quick question, does it work if replacing blog ecosystem features with pages in the first for loop?

I am not sure. That will change the file structure of versions/master/ from

blog
ecosystem
features
...

to

pages
----blog
----ecosystem
----features
...

[waytrue17]

@mxnet-bot run ci [windows-gpu]

[mxnet-bot]

Jenkins CI successfully triggered : [windows-gpu]

[ys2843]

@waytrue17 Thanks for clarifying. It would be great if we can identify the root cause of this file location change. Is it caused by the build script change?

[leezu]

The last good pipeline is https://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/restricted-website-build-master/detail/restricted-website-build-master/1955/pipeline/ based on fee6a6a
First bad one is https://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/restricted-website-build-master/detail/restricted-website-build-master/1956/pipeline/ based on https://github.com/apache/incubator-mxnet/commits/19ede063c4756fa49cfe741e654180aee33991c6

19ede063c4756fa49cfe741e654180aee33991c6o does not remove any files but adds comment headers: 19ede06#diff-cd4e818f3274524f236f238d7e53d33e0a92c831bdb44106b8fe9a28b7815319 so @waytrue17 this PR may not fix the problem