2 ms·
i know why it's not this way, and love what you've built, but find it vaguely dissatisfying that with the structured and hierarchical organization, the URLs don
by Terretta 5y ago
i know why it's not this way, and love what you've built, but find it vaguely dissatisfying that with the structured and hierarchical organization, the URLs don't convey that affordance
also decent weight still goes to URL keywords in SERPs
(and yes, many to many links to leaves attached more than one place seems a problem, but that's what canonical URLs are for)
- kevinslin 5y agowe actually have a solution in the works - adding a human friendly URL label followed by the guid (eg. wiki.dendron.so/notes/tutorial-{guid}) server side, we only parse the last component of the url which will be the guid. the reason we don't do this now is because we're focused on making static publishing smooth (most people use github pages to host their dendron sites) before we start on work on the server enhanced solution
- Terretta 5y agoGreat, the amazon.com product URL approach works for a pretty big many-to-many hierarchy! e.g. - https://www.amazon.com/Moleskine-Classic-Cover-Notebook-Ruled/dp/8883701127 https://www.amazon.com/Moleskine-Classic-Cover-Notebook-Rule... - https://www.amazon.com/dp/8883701127 https://www.amazon.com/dp/8883701127