aboutsummaryrefslogtreecommitdiffstats
path: root/root
diff options
context:
space:
mode:
authors-ol <s-ol@users.noreply.github.com>2019-10-26 19:46:25 +0000
committers-ol <s-ol@users.noreply.github.com>2019-10-26 19:46:25 +0000
commitf5eca9e9be25ba3251d49f0e1a72f322c6faf837 (patch)
tree2af3880887bf86d3ba7931129a3ac26dece5a3ed /root
parentfrontpage fixes (diff)
downloadmmm-f5eca9e9be25ba3251d49f0e1a72f322c6faf837.tar.gz
mmm-f5eca9e9be25ba3251d49f0e1a72f322c6faf837.zip
small change in why_redirectly
Diffstat (limited to 'root')
-rw-r--r--root/blog/why_redirectly/text$markdown.md9
1 files changed, 7 insertions, 2 deletions
diff --git a/root/blog/why_redirectly/text$markdown.md b/root/blog/why_redirectly/text$markdown.md
index 4157a0a..4bddd0e 100644
--- a/root/blog/why_redirectly/text$markdown.md
+++ b/root/blog/why_redirectly/text$markdown.md
@@ -31,8 +31,13 @@ instead of directly linking to the content.
This way, whenever I make changes to my content's adressing scheme,
I simply change the URL location, and any old links that are floating around remain functional.
-Should I ever change to another domain, I will consider simply leaving the redirection service running on this domain anyhow,
-to keep old links alive. At least for a few years :)
+It's also helpful to direct people to the best documentation for a particular project:
+when I start working on something, it might exist only as a git repo,
+but later in the project's lifecycle I may add a descriptive article on my website or as part of the blog.
+Perhaps one of my projects will outgrow this website and need its own domain some time.
+By always linking using a canonical project-URL, I can make sure that old links always point to the best place.
+Also if I ever decide to move to a different domain again,
+I can simply leave the redirection service running on here, at least for a few years :)
Of course all of this doesn't work when visitors of my page navigate around by themselves,
and then share the URL from their address bar.