You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 23, 2022. It is now read-only.
As I'm looking at the execution in gitpod of our first post. I'm struck with worrying about writing us into corner when it comes to future stubs over the life of the blog. What's the a) feasibility and b) reasonability of having it go: /blog/20xx/0Y/stub as the URL?
Related, do we have the capacity of assigning a stub that isn't autogenerated? I don't see that in the current demos, so I'm not sure what the YAML var is for that.
The text was updated successfully, but these errors were encountered:
As I'm looking at the execution in gitpod of our first post. I'm struck with worrying about writing us into corner when it comes to future stubs over the life of the blog. What's the a) feasibility and b) reasonability of having it go: /blog/20xx/0Y/stub as the URL?
Related, do we have the capacity of assigning a stub that isn't autogenerated? I don't see that in the current demos, so I'm not sure what the YAML var is for that.
The text was updated successfully, but these errors were encountered: