Repository navigation
Thinking about Organization #1
Replies: 3 comments 7 replies
|
Personally, I think prefix with site name (based on URL) makes sense, as the URL will (usually) be unique, and the main "template trigger". Might be a combination with schema.org (that I'm not using), but the URL will always be unique, hence easy for users to understand what (and where) the template is to be used? Example template triggers I've use for GitHub, is e.g. Example on (only) prefixed template names, with some info/type: We could possibly add some kind of suffix with multiple variants of same template, or maybe just add author username, or something - mainly to differentiate on "duplicate" site templates, but with different variants/preferences? IDK - kinda depends if we want different "ready templates" and/or just showcase what's possible. For suffix, e.g. if we have multiple "conflicting" (variations/personal preference on template), we could do something like: Benefit will be easy to add similar templates, but with a personal touch, though keeping the prefix. |
|
I think I will start on the PR side first. This has some format with #6 What we need:
This means we need a system that helps:
|
|
Hi can you add please more clarification on how to use the template of Youtube timestamps ? I can't figure out how do we add that timestamps in an existing note |
Uh oh!
There was an error while loading. Please reload this page.
We just started, so this is not set in stone yet, but organization is likely going to need to be thought about from day one.
Sort:
By function?
By site?
By category?
What are your thoughts?
All reactions