-
Notifications
You must be signed in to change notification settings - Fork 26
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
Website: case studies list: add a link to the source code too #3668
Comments
Great idea! |
I just have a brief understanding, and I guess this is the expected result: (Same structure as the example beyond, just inserting a new link) |
@balacij Jason, Can you give me an example of |
(@daijingz Jason will eventually answer you, but he's got important deadlines right now, so he is ignoring the Drasil repo for this week). |
@balacij @JacquesCarette There is one thing I forget: There are three different reference structures in this program: |
I think you should be able to create a new Have a look at Drasil/code/drasil-website/lib/Drasil/Website/Example.hs Lines 163 to 184 in 04a5f3b
|
@balacij @JacquesCarette Here is the last problem: I tried to use some new This is because I have not defined the reference Here is the code: (Same form as To fix it, I need to find the place to define a reference, and likely it is in the Here is my attempt:
In this attempt, I tried to insert my created reference |
Co-authored-by: Jingze Dai <[email protected]>
Website: add links to the source code for each generated example #3668
See the below image. In our list of “Generated Examples”/case studies, we show the final fruits of the projects, but not the inputs. We should somehow link to the relevant source code folder too. For example, for
DblPend
, we should add a bullet item: "Source Code" that is clickable tohttps://github.com/JacquesCarette/Drasil/tree/master/code/drasil-example/dblpend
(at the relevant commit tree however, similar to the stable code linked), or we could make the shown names clickable themselves to the same link.The text was updated successfully, but these errors were encountered: