-
Notifications
You must be signed in to change notification settings - Fork 25
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
Contributes to issue: Should add Well-Understood paper to front page description #3360 (Attempt) #3705
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes to the Website are far from pretty... but at (unfortunately) quite consistent with just how bad this code is. So those two changes are ok. Just the change to README needs improved.
README.md
Outdated
@@ -21,7 +21,7 @@ Generate all the Things! Visit [our website](https://jacquescarette.github.io/Dr | |||
|
|||
## What is Drasil? | |||
|
|||
For well understood domains, building software ought to be a matter of engineering, based on solid scientific foundations. The ultimate test of "well understood" is being able to teach the domain language to a computer. Drasil is a framework for generating all of the software artifacts for (well understood) research software, from the natural knowledge base of the domain. | |||
For well understood domains, building software ought to be a matter of engineering, based on solid scientific foundations. The ultimate test of "well understood" is being able to teach the domain language to a computer. Drasil is a framework for generating all of the software artifacts for (well understood) research software, from the natural knowledge base of the domain. The exhaustive summary of [well-understood](https://github.com/JacquesCarette/Drasil/blob/master/Papers/WellUnderstood/wu.pdf) domains and our original ideas include Drasil's primary information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rather than this, I would make "(well understood) research software" in the previous line be a link to the paper, and skip this whole new sentence.
There are two existing branches in my personal machine for other issues, and I will use your described tools. |
namedRef icsePositionPaper (S "Old Position Paper") +:+ S "outlining our original ideas, a" +:+ | ||
namedRef danPoster (S "Drasil Poster") +:+ S ", and a" +:+ | ||
namedRef wellUnderstoodPaper (S "Well-Understood Paper") +:+ S "discussing key concepts." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should use foldlList
, or something similar. I seem to remember describing how to do this, as well as some other improvements, in a previous PR; you can use that as reference!
Sorry everyone, there are some non-personal issues taking place on my PC, and I am going to go to repair stores tomorrow. I will get back tomorrow. |
@samm82 Newest update: have built two reusable wiki page sentences. This modification has some naming problems, and I am checking. For the Can you show me the corresponding |
Up to now my PR has a lot of commits, do not worry, later I will |
@daijingz You should search the repo for " |
Before I notice there is an example on the second paragraph: For tonight's update, I use |
aboutParagraph9 papersWiki icsePositionPaper danPoster wellUnderstoodPaper = | ||
S "A list of papers and documents written about Drasil can be found on the" +:+ | ||
namedRef papersWiki (S "Drasil papers and documents") +:+. wikiSentence +:+ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I previously asked if "papers" and "documents" should be capitalized; I now realize that "Drasil Papers and Documents" is the name of the wiki page being referenced here, so they should be capitalized. Other than this, this PR looks good to me!
@samm82 Today I realized that webpage text inconsistencies may become a problem, so I inspected the existing text in the website to find any possible improvement places. Scope: the whole
These are Grammarly suggestions. If you feel there is no need to change this, I can stay without any further changes, but I suggest modifying these words. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Super minor nitpick, but this looks good to me! We should wait on Dr. Carette's review though.
\a specific purpose so that knowledge may be used in generated models, definitions, and theories. Chunks are usually made up of several \ | ||
\lower-level types that hold lower-lever information; when contained together, these pieces of lower-level information hold a new specific \ | ||
\purpose. The structure of a chunk can be thought of as a wrapper of information, and this is all implemented using Haskell's record-type \ | ||
\syntax. Recipes transform the acquired knowledge into a usable format." | ||
|
||
-- | Paragraph describing recipes | ||
aboutParagraph7 :: Reference -> Sentence | ||
aboutParagraph7 recipesWiki= S "As described in the" +:+ namedRef recipesWiki (S "Recipes") +:+ S "wiki page, recipes are instructions that \ | ||
\unpackage necessary information from chunks and send \ | ||
aboutParagraph7 recipesWiki= S "As described in the" +:+ namedRef recipesWiki (S "Recipes") +:+ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
aboutParagraph7 recipesWiki= S "As described in the" +:+ namedRef recipesWiki (S "Recipes") +:+ | |
aboutParagraph7 recipesWiki = S "As described in the" +:+ namedRef recipesWiki (S "Recipes") +:+ |
Let me think about more possible improvements. (Updating) |
@samm82 Wait a moment for the new updates.
Inherited from previous PR #3686, but with some changes. Please wait for some further checks.
Corresponding Issue: #3360
Newest inspection: Coding style requirements.