I want to rewrite URL of categories via nginx, this way:
meta.discourse.org/c/support --> meta.discourse.org/support
Will it make next problems during future updates or something else?
Is there any better replacement method?
1 Like
Yes, this will cause problems, erm, everywhere. I suggest not doing it.
1 Like
I thought it will make problems related to CEO!
Can you illustrate, @riking? I don’t have any idea what kind of problems will be happened.
You mean SEO? Compared to other forum software, Discourse does a good job with following proper SEO url practices out-the-box. It looks like you’re trying to make the url shorter but in the end, google’s algorithms look for the following:
- Original Content.
- Trust & Identity.
- Authority of the site’s subject.
- Visitor receptivity (low bounce rate; links elsewhere that point to your site, ect.)
You should be “worried” more about the content on your pages than the technical semantics.
1 Like
Yeah, I was talking about problems in the sense of “not working”, not SEO snake oil bullshit.
1 Like
Aye, was replying to @reaon with the possible “CEO” typo and clear up that specific tidbit if they are a victim to said snake oil indoctrination propaganda practices.
What kind of problems? plz
For one, Routing.
Changing the URL format of HTTP requests is likely to result in a lot of “Not Found” errors.
Don’t think of them so much as “addresses” identifying locations, but more like instructions on “how to get something”
Rewriting in the manner of redirecting! You request for example.com/A and it is translated as example.com/category/A for the CMS by the web server, here Nginx. Why should we get a 404 error?!
Routing exists in 2 spots, on the server and on the client https://github.com/discourse/discourse/blob/master/app/assets/javascripts/discourse/routes/app-route-map.js.es6 …
A rewrite on the server without doing the needed work on the client will result in stuff breaking
This is beyond your skill level and will cause problems.
4 Likes