-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Versioning of examples #9
Comments
The only thing I can think of is having a footer link to the Git Commit history or Git Blame, seeing as it's automatically versioned here and it would be an easily maintainable (no maintenance required) way of doing it. All you would have to do is put something like this in the template:
|
Thanks for the suggestion @MattGreyDesign. This method would create quite a granular version history of the examples even if small changes (such as typos or more additions) are added. I'm wondering how we'd version a significant change. Maybe the solution as simple as submitting a new set of principles if an organisation updates them and reevaluates things. Perhaps having a publish I think for the time being it's probably too early to think about how to do this since there are few examples that have changed and few sources that show this change. |
I love this idea for versioning major changes to any design principles that might communicate something critical was learned which changed someone's approach / philosophy. At a personal level I like to document that type of change and see that being useful here too. Would also be cool to note why the change happened (if that is known information). Suggestion - a way to demote a page so it doesn't show up as a full page. I'm working on my design principles and this resource was shared by my school and I really appreciate this project! |
Design principles are designed to iterate and change over time. It would be good to factor in how to display changes over time. I can't quite think about how to do that in a simple way for contributors. Needs some thought.
The text was updated successfully, but these errors were encountered: