Skip to content
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 - Introduction #1599

Closed
danscime opened this issue Jun 21, 2019 · 7 comments
Closed

Website - Introduction #1599

danscime opened this issue Jun 21, 2019 · 7 comments

Comments

@danscime
Copy link
Collaborator

Building from #1527.

@smiths @oluowoj

For the introduction to the site, we said we wanted a brief intro of what Drasil is.
Currently we do not have any sort of intro, we only have descriptions of the sections on the webpage.

@oluowoj
Copy link
Collaborator

oluowoj commented Jun 21, 2019

Yes, I think we should have some sort of intro. Can you put something together and we can review and possibly edit? Just some few start up lines for a start.

@danscime
Copy link
Collaborator Author

Some pieces from the main README file.

Drasil is a framework for generating all of the software artifacts from a stable knowledge base, focusing currently on scientific software. The main goals are to reduce knowledge duplication and improve traceability.

Drasil is used to generate all requisite software artifacts from a common knowledge-base using recipes written in a Domain-Specific Language (DSL). These recipes allow us to specify which pieces of knowledge should be used in which artifacts, how to transform them, and more.

@oluowoj
Copy link
Collaborator

oluowoj commented Jun 24, 2019

Yes, I was going to suggest texts from the readme file, I think its a good start.

@danscime danscime self-assigned this Jul 2, 2019
@danscime
Copy link
Collaborator Author

danscime commented Jul 2, 2019

Updated via c6a3af2.

My intro paragraph currently is:

Drasil is a framework for generating all of the software artifacts from a stable knowledge base, focusing currently on scientific software. The main goals are to reduce knowledge duplication and improve traceability. The atifacts are generated from a common knowledge-base using recipes written in a Domain-Specific Language (DSL). These recipes allow us to specify which pieces of knowledge should be used in which artifacts, how to transform them, and more.

@smiths
Copy link
Collaborator

smiths commented Jul 10, 2019

@danscime, I like your intro text, but I think we can say more. I wrote the following document (for another purpose) that I think you can borrow from.

OutcomesAndBenefitsOfDrasil.txt

@peter-michalski
Copy link
Collaborator

peter-michalski commented Aug 18, 2022

From meeting #3038

I will review the Wiki for any items that should be added to the website, and the team will review and discuss in this issue thread.

Potential items:

  • Information regarding getting started with Drasil
  • What can, or could in the future be created with Drasil (generate specific artifacts/documents, code - in various languages)
  • Regarding the future consider other artifacts listed in Olu's work
  • Quantify number of artifacts that Drasil can produce (quantify other information?)
  • Consider adding things that will encourage people to help develop Drasil (and use Drasil)
  • Consider adding an introductory blurb that explains Drasil in plain language (Before the current into? Move current intro to another section? As an abstract?)

@smiths
Copy link
Collaborator

smiths commented Aug 18, 2022

The original description of the issue doesn't really match the expanded scope of our discussion (in #3038). Therefore, I'll close this issue and create a new one that includes the points listed by @peter-michalski.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants