-
Notifications
You must be signed in to change notification settings - Fork 7
Description
From @mattheworiordan on this (sent to me via Slack DM, August 2022):
Do you think it’s worth putting a static site generator over this content and hosting on engineering.ably.com. The argument for this is that links are manageable moving forward i.e. if we have engineering.ably.com now and we move to this static site, we can set up redirects for specific pages. If in future we move to another platform or consolidate more of this content somwehere else aagain, we can set up redirects per page. Using a Github repo, we don’t get any of those benefits. Plugging in a static site generator to render Markdown should be trivial, and we could always include the Github icon in the interface to allow people to issue PRs / view the source etc. WDYT
To which I responded with:
I have no objection to publishing to a static site, and there are benefits. My only reason for continuing, for now, with just GitHub-native rendering was the simplicity of it.