-
Notifications
You must be signed in to change notification settings - Fork 5
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
web: "Related Cards" inconsistencies #7
Comments
The related cards were, originally, a section at the bottom of the document. I've come to prefer to have them throughout the text where relevant, like links on Wikipedia. I believe that will make it more likely that people stay on the site for longer. |
Why not both? I was thinking of adding a YAML front matter array of related cards, which would be added to be bottom when generating the site. |
That sounds like a nice addition. |
Create a pull request with a proof of contept on http://essentials.xebia.com/two-minute-rule/
|
Possible improvement: Define a markdown extension for cards, say [%], e.g. [%two-minute-rule]. This would transform:
Into: Some TextA reference to Card From The Text References |
Implemented my previous suggestion, see http://essentials.xebia.com/what-you-measure/ and be38a37#diff-ba6b642bd92f2aa59313bae53eb5eb81 Cards can now be either prefixed with an array of references, or references can be created inline with %. Both will be added under the 'references' section. |
Any feedback on this? Examples can be seen in the source and generated pages for Upside: I think it's pretty nice Downside: Someone will have to go through all cards and implement this |
I like the way of browsing the cards throughout the text directly. It's very nice. Should we distinguish somehow (icon/color?) links that lead to different cards from links to external sites, or is it unnecessary? |
How to handle "related card" references?
Should we specify them in their own section, in a single-line entry (as in hurt-often, poutsma-principle), or in multiple entries (as in acceptance-criteria) ?
Some other inconsistencies:
## Code Review
by### References
The text was updated successfully, but these errors were encountered: