[GitHub] [camel-website] fvaleri opened a new pull request #382: Fix directory scheme for all blog posts

classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] fvaleri opened a new pull request #382: Fix directory scheme for all blog posts

GitBox

fvaleri opened a new pull request #382:
URL: https://github.com/apache/camel-website/pull/382


   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] oscerd commented on pull request #382: Fix directory scheme for all blog posts

GitBox

oscerd commented on pull request #382:
URL: https://github.com/apache/camel-website/pull/382#issuecomment-638456131


   Makes sense. Let's close this


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] fvaleri commented on pull request #382: Fix directory scheme for all blog posts

GitBox
In reply to this post by GitBox

fvaleri commented on pull request #382:
URL: https://github.com/apache/camel-website/pull/382#issuecomment-638461004


   > This will lead to broken links. We can't do this without adding redirects from existing URLs to the new ones.
   
   Right.
   
   Given that our 404 page URL is like this:
   ```
   https://camel.apache.org/blog/TestZero/
   ```
   We could add something as simple as:
   ```
   var baseUrl = "https://camel.apache.org/blog/";
   var redirects = {
       'TestZero': baseUrl + '2019/12/TestZero/',
       'TestOne': baseUrl + '2020/01/TestOne/'
   };
   
   var url = window.location.href.replace(/\/$/, '');
   var oldPath = url.substr(url.lastIndexOf('/') + 1);
   
   var newPath = redirects[oldPath];
   if (newPath) {
       console.log('Redirecting ' + oldPath + ' to '+ newPath);
       window.location.replace(newPath);
   }
   ```
   
   It's just plain JS, but I'm not familiar with the website framework, so I don't know if something like this can be easily added. Such small feature could be useful in other situations too.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] fvaleri commented on pull request #382: Fix directory scheme for all blog posts

GitBox
In reply to this post by GitBox

fvaleri commented on pull request #382:
URL: https://github.com/apache/camel-website/pull/382#issuecomment-638465677


   @zregvart Just saw your comment about `static/.htaccess`, will add redirects there.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] fvaleri removed a comment on pull request #382: Fix directory scheme for all blog posts

GitBox
In reply to this post by GitBox

fvaleri removed a comment on pull request #382:
URL: https://github.com/apache/camel-website/pull/382#issuecomment-638461004


   > This will lead to broken links. We can't do this without adding redirects from existing URLs to the new ones.
   
   Right.
   
   Given that our 404 page URL is like this:
   ```
   https://camel.apache.org/blog/TestZero/
   ```
   We could add something as simple as:
   ```
   var baseUrl = "https://camel.apache.org/blog/";
   var redirects = {
       'TestZero': baseUrl + '2019/12/TestZero/',
       'TestOne': baseUrl + '2020/01/TestOne/'
   };
   
   var url = window.location.href.replace(/\/$/, '');
   var oldPath = url.substr(url.lastIndexOf('/') + 1);
   
   var newPath = redirects[oldPath];
   if (newPath) {
       console.log('Redirecting ' + oldPath + ' to '+ newPath);
       window.location.replace(newPath);
   }
   ```
   
   It's just plain JS, but I'm not familiar with the website framework, so I don't know if something like this can be easily added. Such small feature could be useful in other situations too.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] fvaleri edited a comment on pull request #382: Fix directory scheme for all blog posts

GitBox
In reply to this post by GitBox

fvaleri edited a comment on pull request #382:
URL: https://github.com/apache/camel-website/pull/382#issuecomment-638465677


   @zregvart Just saw your comment about `static/.htaccess`, will add redirects there.
   
   I see that some posts (releases) have the url property, i.e. `url: /blog/release-2-24-0.html`. This doesn't seems to map with directory content. How does it work? Can't we just use this property to maintain old URLs?


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] fvaleri edited a comment on pull request #382: Fix directory scheme for all blog posts

GitBox
In reply to this post by GitBox

fvaleri edited a comment on pull request #382:
URL: https://github.com/apache/camel-website/pull/382#issuecomment-638465677


   @zregvart Just saw your comment about `static/.htaccess`, will add redirects there.
   
   I see that some posts (releases) have the url property, i.e. `url: /blog/release-2-24-0.html`. This doesn't seems to map with directory content. How does it work? Can't we just use this property to keep old URLs?


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] fvaleri commented on pull request #382: Fix directory scheme for all blog posts

GitBox
In reply to this post by GitBox

fvaleri commented on pull request #382:
URL: https://github.com/apache/camel-website/pull/382#issuecomment-638651867


   @zregvart just tried to set the url property on my last post and run the website locally. It seems to work fine.
   
   If I add `url: /blog/CdcWithCamelAndDebezium` to the `index.md`, then I get:
   ```
   ├── 2020
   │   ├── 05
   │   │   └── CdcWithCamelAndDebezium
   │   │       ├── camel-featured.jpg
   │   │       ├── camel-featured_hua29054ae124e0a556509e94b698dcf1b_122153_800x0_resize_q95_gaussian.jpg
   │   │       └── index.html
   ├── CdcWithCamelAndDebezium
   │   ├── camel-featured.jpg
   │   ├── camel-featured_hua29054ae124e0a556509e94b698dcf1b_122153_800x0_resize_q95_gaussian.jpg
   │   └── index.html
   ```
   
   So no redirect would be needed for release posts (they all have url set), while for the other posts we would just need to add the url property. What do you think?


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] fvaleri edited a comment on pull request #382: Fix directory scheme for all blog posts

GitBox
In reply to this post by GitBox

fvaleri edited a comment on pull request #382:
URL: https://github.com/apache/camel-website/pull/382#issuecomment-638651867


   @zregvart just tried to set the url property on my last post and run the website locally. It seems to work fine.
   
   If I add `url: /blog/CdcWithCamelAndDebezium` to the `index.md`, this is the output I get in public folder after build:
   ```
   ├── 2020
   │   ├── 05
   │   │   └── CdcWithCamelAndDebezium
   │   │       ├── camel-featured.jpg
   │   │       ├── camel-featured_hua29054ae124e0a556509e94b698dcf1b_122153_800x0_resize_q95_gaussian.jpg
   │   │       └── index.html
   ├── CdcWithCamelAndDebezium
   │   ├── camel-featured.jpg
   │   ├── camel-featured_hua29054ae124e0a556509e94b698dcf1b_122153_800x0_resize_q95_gaussian.jpg
   │   └── index.html
   ```
   
   So no redirect would be needed for release posts (they all have url set), while for the other posts we would just need to add the url property. What do you think?


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] zregvart commented on pull request #382: Fix directory scheme for all blog posts

GitBox
In reply to this post by GitBox

zregvart commented on pull request #382:
URL: https://github.com/apache/camel-website/pull/382#issuecomment-639751012


   @fvaleri, not sure what would would we gain with organizing the `content/blog` by date and leaving the URLs as is, if anything that might be a bit confusing. Not sure if you cleared the `public` folder before you built, there should not be two copies of the blog post.
   
   I think both the URLs and the organization in the repository need to follow the same convention. So if there's merit in doing that then it needs to be done by adding redirects for existing content and configuring the [permalinks](https://gohugo.io/content-management/urls/#permalinks-configuration-example) for blog posts.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] fvaleri commented on pull request #382: Fix directory scheme for all blog posts

GitBox
In reply to this post by GitBox

fvaleri commented on pull request #382:
URL: https://github.com/apache/camel-website/pull/382#issuecomment-640057846


   Hi @zregvart , I think this is a pretty common scheme for organizing blog posts and there seems to be consensus around it. I fully agree with your suggestions, so now there are redirects for all old posts (we already have one published with the new layout) and permalinks configuration.
   
   All links and redirects seem to work fine. Note that the `url` property has been removed in each release post and relative redirect rules has been created. This is to have the same behavior for all posts. If this PR is merged, all future releases should not have `url` property or it should follow the `blog/aaaa/mm/folder-name` layout.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] fvaleri edited a comment on pull request #382: Fix directory scheme for all blog posts

GitBox
In reply to this post by GitBox

fvaleri edited a comment on pull request #382:
URL: https://github.com/apache/camel-website/pull/382#issuecomment-640057846


   Hi @zregvart , I think this is a pretty common scheme for organizing blog posts and there seems to be consensus around it. I fully agree with your suggestions, so now there are redirects for all old posts (we already have one published with the new layout) and permalinks configuration.
   
   All links and redirects seem to work fine. Note that the `url` property has been removed in each release post and relative redirect rules has been created. This is to have the same behavior for all posts. If this PR is merged, all future releases should not have `url` property or it should follow the `blog/aaaa/mm/folder-name` scheme.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] zregvart commented on a change in pull request #382: Fix directory scheme for all blog posts

GitBox
In reply to this post by GitBox

zregvart commented on a change in pull request #382:
URL: https://github.com/apache/camel-website/pull/382#discussion_r436363571



##########
File path: static/.htaccess
##########
@@ -1053,6 +1053,46 @@ Redirect 301 /zip-file-dataformat.html /components/latest/dataformats/zipfile-da
 Redirect 301 /zookeeper.html /components/latest/zookeeper-component.html
 Redirect 301 /docs/getting-started /manual/latest/getting-started.html
 
+# old blog posts redirects to not break published links that do not conform with the new blog layout
+Redirect /blog/release-2-24-0.html /blog/2019/05/RELEASE-2.24.0/
+Redirect /blog/ApacheConNA-2019/ /blog/2019/09/ApacheConNA-2019/
+Redirect /blog/release-2-23-4.html /blog/2019/09/RELEASE-2.23.4/
+Redirect /blog/release-2-24-2.html /blog/2019/09/RELEASE-2.24.2/
+Redirect /blog/release-3-0-0-RC1.html /blog/2019/09/RELEASE-3.0.0-RC1/
+Redirect /blog/release-2-24-0.html /blog/2019/05/RELEASE-2.24.0/
+Redirect /blog/Camel3-2monthsaway/ /blog/2019/10/Camel3-2monthsaway/
+Redirect /blog/release-3-0-0-RC2.html /blog/2019/10/RELEASE-3.0.0-RC2/
+Redirect /blog/release-3-0-0-RC3.html /blog/2019/10/RELEASE-3.0.0-RC3/
+Redirect /blog/ASF-Report-2019/ /blog/2019/11/ASF-Report-2019/
+Redirect /blog/release-3-0-0.html /blog/2019/11/RELEASE-3.0.0/
+Redirect /blog/2019-Numbers/ /blog/2019/12/2019-Numbers/
+Redirect /blog/Camel-Kafka-connector-intro/ /blog/2019/12/Camel-Kafka-connector-intro/
+Redirect /blog/Camel3-Whatsnew/ /blog/2019/12/Camel3-Whatsnew/
+Redirect /blog/LanguageSupportTooling-0.0.20/ /blog/2019/12/LanguageSupportTooling-0.0.20/
+Redirect /blog/Podcast47/ /blog/2019/12/Podcast47/
+Redirect /blog/release-2-24-3.html /blog/2019/12/RELEASE-2.24.3/
+Redirect /blog/capi-gateway/ /blog/2020/01/capi-gateway/
+Redirect /blog/CustomWebApiComponent/ /blog/2020/01/CustomWebApiComponent/
+Redirect /blog/FOSDEM-2020/ /blog/2020/01/FOSDEM-2020/
+Redirect /blog/release-2-25-0.html /blog/2020/01/RELEASE-2.25.0/
+Redirect /blog/release-3-0-1.html /blog/2020/01/RELEASE-3.0.1/
+Redirect /blog/ApacheConNA-2020-CFP/ /blog/2020/02/ApacheConNA-2020-CFP/
+Redirect /blog/GSoC-2020-announced/ /blog/2020/02/GSoC-2020-announced/
+Redirect /blog/release-3-1-0.html /blog/2020/02/RELEASE-3.1.0/
+Redirect /blog/Camel3-AWS2-Whatsnew/ /blog/2020/03/Camel3-AWS2-Whatsnew/
+Redirect /blog/LTS-Release-Schedule/ /blog/2020/03/LTS-Release-Schedule/
+Redirect /blog/Outreachy-May2020/ /blog/2020/03/Outreachy-May2020/
+Redirect /blog/Outreachy-May2020-Update/ /blog/2020/03/Outreachy-May2020-Update/
+Redirect /blog/100Camels/ /blog/2020/04/100Camels/
+Redirect /blog/Camel-Kafka-connector-release-0.1.0/ /blog/2020/04/Camel-Kafka-connector-release-0.1.0/
+Redirect /blog/Camel-Quarkus-release-1.0.0-M7/ /blog/2020/04/Camel-Quarkus-release-1.0.0-M7/
+Redirect /blog/Camel32-Whatsnew/ /blog/2020/04/Camel32-Whatsnew/
+Redirect /blog/release-2-25-1.html /blog/2020/04/RELEASE-2.25.1/
+Redirect /blog/release-3-2-0.html /blog/2020/04/RELEASE-3.2.0/
+Redirect /blog/Camel33-Whatsnew/ /blog/2020/05/Camel33-Whatsnew/
+Redirect /blog/CdcWithCamelAndDebezium/ /blog/2020/05/CdcWithCamelAndDebezium/
+Redirect /blog/release-3-3-0.html /blog/2020/05/RELEASE-3.3.0/

Review comment:
       These need to be `Redirect 301` to be permanent redirects




----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] fvaleri commented on a change in pull request #382: Fix directory scheme for all blog posts

GitBox
In reply to this post by GitBox

fvaleri commented on a change in pull request #382:
URL: https://github.com/apache/camel-website/pull/382#discussion_r436369194



##########
File path: static/.htaccess
##########
@@ -1053,6 +1053,46 @@ Redirect 301 /zip-file-dataformat.html /components/latest/dataformats/zipfile-da
 Redirect 301 /zookeeper.html /components/latest/zookeeper-component.html
 Redirect 301 /docs/getting-started /manual/latest/getting-started.html
 
+# old blog posts redirects to not break published links that do not conform with the new blog layout
+Redirect /blog/release-2-24-0.html /blog/2019/05/RELEASE-2.24.0/
+Redirect /blog/ApacheConNA-2019/ /blog/2019/09/ApacheConNA-2019/
+Redirect /blog/release-2-23-4.html /blog/2019/09/RELEASE-2.23.4/
+Redirect /blog/release-2-24-2.html /blog/2019/09/RELEASE-2.24.2/
+Redirect /blog/release-3-0-0-RC1.html /blog/2019/09/RELEASE-3.0.0-RC1/
+Redirect /blog/release-2-24-0.html /blog/2019/05/RELEASE-2.24.0/
+Redirect /blog/Camel3-2monthsaway/ /blog/2019/10/Camel3-2monthsaway/
+Redirect /blog/release-3-0-0-RC2.html /blog/2019/10/RELEASE-3.0.0-RC2/
+Redirect /blog/release-3-0-0-RC3.html /blog/2019/10/RELEASE-3.0.0-RC3/
+Redirect /blog/ASF-Report-2019/ /blog/2019/11/ASF-Report-2019/
+Redirect /blog/release-3-0-0.html /blog/2019/11/RELEASE-3.0.0/
+Redirect /blog/2019-Numbers/ /blog/2019/12/2019-Numbers/
+Redirect /blog/Camel-Kafka-connector-intro/ /blog/2019/12/Camel-Kafka-connector-intro/
+Redirect /blog/Camel3-Whatsnew/ /blog/2019/12/Camel3-Whatsnew/
+Redirect /blog/LanguageSupportTooling-0.0.20/ /blog/2019/12/LanguageSupportTooling-0.0.20/
+Redirect /blog/Podcast47/ /blog/2019/12/Podcast47/
+Redirect /blog/release-2-24-3.html /blog/2019/12/RELEASE-2.24.3/
+Redirect /blog/capi-gateway/ /blog/2020/01/capi-gateway/
+Redirect /blog/CustomWebApiComponent/ /blog/2020/01/CustomWebApiComponent/
+Redirect /blog/FOSDEM-2020/ /blog/2020/01/FOSDEM-2020/
+Redirect /blog/release-2-25-0.html /blog/2020/01/RELEASE-2.25.0/
+Redirect /blog/release-3-0-1.html /blog/2020/01/RELEASE-3.0.1/
+Redirect /blog/ApacheConNA-2020-CFP/ /blog/2020/02/ApacheConNA-2020-CFP/
+Redirect /blog/GSoC-2020-announced/ /blog/2020/02/GSoC-2020-announced/
+Redirect /blog/release-3-1-0.html /blog/2020/02/RELEASE-3.1.0/
+Redirect /blog/Camel3-AWS2-Whatsnew/ /blog/2020/03/Camel3-AWS2-Whatsnew/
+Redirect /blog/LTS-Release-Schedule/ /blog/2020/03/LTS-Release-Schedule/
+Redirect /blog/Outreachy-May2020/ /blog/2020/03/Outreachy-May2020/
+Redirect /blog/Outreachy-May2020-Update/ /blog/2020/03/Outreachy-May2020-Update/
+Redirect /blog/100Camels/ /blog/2020/04/100Camels/
+Redirect /blog/Camel-Kafka-connector-release-0.1.0/ /blog/2020/04/Camel-Kafka-connector-release-0.1.0/
+Redirect /blog/Camel-Quarkus-release-1.0.0-M7/ /blog/2020/04/Camel-Quarkus-release-1.0.0-M7/
+Redirect /blog/Camel32-Whatsnew/ /blog/2020/04/Camel32-Whatsnew/
+Redirect /blog/release-2-25-1.html /blog/2020/04/RELEASE-2.25.1/
+Redirect /blog/release-3-2-0.html /blog/2020/04/RELEASE-3.2.0/
+Redirect /blog/Camel33-Whatsnew/ /blog/2020/05/Camel33-Whatsnew/
+Redirect /blog/CdcWithCamelAndDebezium/ /blog/2020/05/CdcWithCamelAndDebezium/
+Redirect /blog/release-3-3-0.html /blog/2020/05/RELEASE-3.3.0/

Review comment:
       OK




----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] zregvart commented on a change in pull request #382: Fix directory scheme for all blog posts

GitBox
In reply to this post by GitBox

zregvart commented on a change in pull request #382:
URL: https://github.com/apache/camel-website/pull/382#discussion_r436387561



##########
File path: README.md
##########
@@ -199,9 +199,11 @@ areas of the website:
 
 Use the `blog` archetype to create a new markdown content file in `content/blog`:
 
-    $ yarn hugp new --kind blog blog/URL-SLUG/index.md # replace URL-SLUG with URL slug for the blog post
+    $ yarn hugp new --kind blog blog/POST-HOME/index.md # replace POST-HOME with the pattern aaaa/mm/url-slug

Review comment:
       Perhaps we can make it a bit more clear:
   ```suggestion
       $ yarn hugp new --kind blog blog/YYYY/MM/index.md # replace YYYY with the year and MM with the month
   ```




----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] zregvart commented on a change in pull request #382: Fix directory scheme for all blog posts

GitBox
In reply to this post by GitBox

zregvart commented on a change in pull request #382:
URL: https://github.com/apache/camel-website/pull/382#discussion_r436387561



##########
File path: README.md
##########
@@ -199,9 +199,11 @@ areas of the website:
 
 Use the `blog` archetype to create a new markdown content file in `content/blog`:
 
-    $ yarn hugp new --kind blog blog/URL-SLUG/index.md # replace URL-SLUG with URL slug for the blog post
+    $ yarn hugp new --kind blog blog/POST-HOME/index.md # replace POST-HOME with the pattern aaaa/mm/url-slug

Review comment:
       Perhaps we can make it a bit more clear:
   ```suggestion
       $ yarn hugo new --kind blog blog/YYYY/MM/index.md # replace YYYY with the year and MM with the month
   ```




----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] fvaleri commented on a change in pull request #382: Fix directory scheme for all blog posts

GitBox
In reply to this post by GitBox

fvaleri commented on a change in pull request #382:
URL: https://github.com/apache/camel-website/pull/382#discussion_r436391100



##########
File path: README.md
##########
@@ -199,9 +199,11 @@ areas of the website:
 
 Use the `blog` archetype to create a new markdown content file in `content/blog`:
 
-    $ yarn hugp new --kind blog blog/URL-SLUG/index.md # replace URL-SLUG with URL slug for the blog post
+    $ yarn hugp new --kind blog blog/POST-HOME/index.md # replace POST-HOME with the pattern aaaa/mm/url-slug

Review comment:
       Thanks. We also need the PostName in the URL scheme in addition to YYYY and MM.




----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] zregvart merged pull request #382: refactor: use year/month in blog post URLs

GitBox
In reply to this post by GitBox

zregvart merged pull request #382:
URL: https://github.com/apache/camel-website/pull/382


   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] zregvart commented on pull request #382: refactor: use year/month in blog post URLs

GitBox
In reply to this post by GitBox

zregvart commented on pull request #382:
URL: https://github.com/apache/camel-website/pull/382#issuecomment-640534867


   Thanks  @fvaleri!


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[hidden email]