Re: [PR] [DOCS] Move the binder notebooks to docs and enable notebook rendering in Sedona website [sedona]
jiayuasu merged PR #1336: URL: https://github.com/apache/sedona/pull/1336 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [DOCS] Move the binder notebooks to docs and enable notebook rendering in Sedona website [sedona]
jiayuasu opened a new pull request, #1336: URL: https://github.com/apache/sedona/pull/1336 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - No, this is a documentation update. The PR name follows the format `[DOCS] my subject`. ## What changes were proposed in this PR? 1. Moved the notebooks in `binder` folder to `docs/usecases` 2. Updated the dockerfile 3. Update all reference links 4. Enabled the notebook rendering on Sedona website ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I have updated the documentation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [CI] Address the race condition among multiple CI deploying to the website branch [sedona]
jiayuasu merged PR #1318: URL: https://github.com/apache/sedona/pull/1318 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [CI] Address the race condition among multiple CI deploying to the website branch [sedona]
jiayuasu opened a new pull request, #1318: URL: https://github.com/apache/sedona/pull/1318 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - No, this is a documentation update. The PR name follows the format `[DOCS] my subject`. ## What changes were proposed in this PR? Prepull the website branch before deploying to the website branch, as recommended by https://github.com/jimporter/mike ## How was this patch tested? Tested in the CI ## Did this PR include necessary documentation updates? - No, this PR does not affect any public API so no need to change the documentation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [DOCS][CI] Auto push docs to the website branch [sedona]
jiayuasu merged PR #1305: URL: https://github.com/apache/sedona/pull/1305 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [DOCS][CI] Auto push docs to the website branch [sedona]
jiayuasu opened a new pull request, #1305: URL: https://github.com/apache/sedona/pull/1305 ## Did you read the Contributor Guide? - Yes, I have read [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) - No, I haven't read it. ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-XXX. The PR name follows the format `[SEDONA-XXX] my subject`. - No, this is a documentation update. The PR name follows the format `[DOCS] my subject`. ## What changes were proposed in this PR? ## How was this patch tested? ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in since `vX.Y.Z` format. - Yes, I have updated the documentation update. - No, this PR does not affect any public API so no need to change the docs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Sedona website right sidebar menu is missing the title [sedona]
jiayuasu closed issue #1102: Sedona website right sidebar menu is missing the title URL: https://github.com/apache/sedona/issues/1102 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Sedona website `latest-snapshot` page has a warning message saying it's not the latest snapshot [sedona]
jiayuasu closed issue #1101: Sedona website `latest-snapshot` page has a warning message saying it's not the latest snapshot URL: https://github.com/apache/sedona/issues/1101 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] Sedona website right sidebar menu is missing the title [sedona]
jbampton opened a new issue, #1102: URL: https://github.com/apache/sedona/issues/1102 ## Expected behavior The title of the menu in the right side bar should be correct. ## Actual behavior The menu title says "toc.title" on all pages that have this right sidebar menu. For example shown in the image below:  ## Steps to reproduce the problem Go here: https://sedona.apache.org/1.5.0/setup/maven-coordinates/ or any other page that has the right sidebar menu. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] Sedona website `latest-snapshot` page has a warning message saying it's not the latest snapshot [sedona]
jbampton opened a new issue, #1101: URL: https://github.com/apache/sedona/issues/1101 ## Expected behavior For the website the `latest-snapshot` page should not have the "yellow bar warning" at the top of the page saying: `You're not viewing the latest snapshot version. Click here to go to the latest snapshot.` ## Actual behavior Shown in the next image  ## Steps to reproduce the problem Go here: https://sedona.apache.org/latest-snapshot/ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sedona] jiayuasu merged pull request #802: [DOCS] Update Sedona website, examples, jupyter notebooks to 1.4.0
jiayuasu merged PR #802: URL: https://github.com/apache/sedona/pull/802 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sedona] jiayuasu opened a new pull request, #802: [DOCS] Update Sedona website, examples, jupyter notebooks to 1.4.0
jiayuasu opened a new pull request, #802: URL: https://github.com/apache/sedona/pull/802 ## Did you read the Contributor Guide? - Yes, I have read [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - No, this is a documentation update. The PR name follows the format `[DOCS] my subject`. ## What changes were proposed in this PR? * Update Sedona docs to show the latest news * Update Sedona example projects to 1.4.0 * Update Sedona binder jupyter notebooks to 1.4.0 ## How was this patch tested? Pass CI and manual check ## Did this PR include necessary documentation updates? - Yes, I have updated the documentation update. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-sedona] jiayuasu merged pull request #689: [DOCS] Make the website compliant with the ASF requirement
jiayuasu merged PR #689: URL: https://github.com/apache/incubator-sedona/pull/689 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-sedona] jiayuasu opened a new pull request, #689: [DOCS] Make the website compliant with the ASF requirement
jiayuasu opened a new pull request, #689: URL: https://github.com/apache/incubator-sedona/pull/689 ## Did you read the Contributor Guide? - Yes, I have read [Contributor Rules](https://sedona.apache.org/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/community/develop/) ## Is this PR related to a JIRA ticket? - No, this is a documentation update. The PR name follows the format `[DOCS] my subject`. ## What changes were proposed in this PR? ## How was this patch tested? ## Did this PR include necessary documentation updates? - Yes, I have updated the documentation update. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: Website
Hi Felix, I have fixed the website: https://whimsy.apache.org/pods/project/sedona However: 1. The trademarks are already shown on Sedona website as required but not sure why the website check cannot detect them. Probably because the TM characters are not in HTML format. It is a bit hard to fix. 2. Only GitHub APIs are used in external resources. GitHub resources are allowed according to ASF privacy policy [1] The bottom of the report shows that we didn't provide a wiki on Confluence, but I think it is optional so I didn't fix it: https://incubator.apache.org/clutch/sedona.html [1] https://privacy.apache.org/policies/privacy-policy-public.html On Tue, Sep 13, 2022 at 1:44 AM Jia Yu wrote: > I am working on it. Will confirm it once all issues are resolved. > > On Sun, Sep 11, 2022 at 5:41 PM Felix Cheung > wrote: > >> Please take a look at the bottom of this report >> https://incubator.apache.org/clutch/sedona.html >> >> And esp at >> https://whimsy.apache.org/pods/project/sedona >> >
Re: Website
I am working on it. Will confirm it once all issues are resolved. On Sun, Sep 11, 2022 at 5:41 PM Felix Cheung wrote: > Please take a look at the bottom of this report > https://incubator.apache.org/clutch/sedona.html > > And esp at > https://whimsy.apache.org/pods/project/sedona >
[GitHub] [incubator-sedona] jiayuasu merged pull request #687: [DOCS] Fix Sedona website to be compliant with ASF requirement
jiayuasu merged PR #687: URL: https://github.com/apache/incubator-sedona/pull/687 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-sedona] jiayuasu opened a new pull request, #687: [DOCS] Fix Sedona website to be compliant with ASF requirement
jiayuasu opened a new pull request, #687: URL: https://github.com/apache/incubator-sedona/pull/687 ## Did you read the Contributor Guide? - Yes, I have read [Contributor Rules](https://sedona.apache.org/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/community/develop/) ## Is this PR related to a JIRA ticket? - No, this is a documentation update. The PR name follows the format `[DOCS] my subject`. ## Did this PR include necessary documentation updates? - Yes, I have updated the documentation update. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Website
Please take a look at the bottom of this report https://incubator.apache.org/clutch/sedona.html And esp at https://whimsy.apache.org/pods/project/sedona
Status from website checks
https://whimsy.apache.org/pods/project/sedona
Sedona new website is online
Hi folks, I just refactored the sedona website: http://sedona.apache.org/ I eventually choose to still use mkdocs to manage our documentation website. Since we already use mkdocs before, re-build everything using Jekyll requires too much work. The documentation source code is still in "docs" and "docs-override". You can still build it using "mkdocs serve" and make sure you have "material" theme installed: https://squidfunk.github.io/mkdocs-material/getting-started/ Thanks, Jia
Re: Sedona project website template
Sounds good. You can request on https://selfserve.apache.org/ To create a repo for incubator-sedona-website.git From: Jia Yu Sent: Friday, July 31, 2020 4:37:15 PM To: dev@sedona.apache.org Subject: Sedona project website template Hi folks, We are creating a website for Apache Sedona. The new website will inherit most of the old tutorials and API docs from GeoSpark website: https://datasystemslab.github.io/GeoSpark/ which was written in pure markdown + MkDocs Material. But apparently, the one template was too simple for an incubator project. We may have multiple different sections including tutorials and blog posts. And each release should have its own API web pages as well. Also, it should require minimal efforts to mitigate our markdown-based tutorials to it. After looking at several Apache project websites, http://spark.apache.org/ http://zeppelin.apache.org/ http://mesos.apache.org/ https://mxnet.apache.org/ I feel that Jekyll may be a better choice. Any suggestions? Jia
Sedona project website template
Hi folks, We are creating a website for Apache Sedona. The new website will inherit most of the old tutorials and API docs from GeoSpark website: https://datasystemslab.github.io/GeoSpark/ which was written in pure markdown + MkDocs Material. But apparently, the one template was too simple for an incubator project. We may have multiple different sections including tutorials and blog posts. And each release should have its own API web pages as well. Also, it should require minimal efforts to mitigate our markdown-based tutorials to it. After looking at several Apache project websites, http://spark.apache.org/ http://zeppelin.apache.org/ http://mesos.apache.org/ https://mxnet.apache.org/ I feel that Jekyll may be a better choice. Any suggestions? Jia
