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

chore: Add initial documentation to Docusaurus site #897

Merged
merged 19 commits into from Mar 2, 2022
Merged

Conversation

cmumatt
Copy link
Contributor

@cmumatt cmumatt commented Feb 28, 2022

Description

This PR updates the TypeDoc dependency, adds the TypeDoc Markdown plugin, and begins to fill out the documentation on the Docusaurus site. It also removes the empty Blog and adds a team page, currently without headshots.

Due to poor results auto-generating Markdown docs from TypeDoc function dictionaries, this PR does not include an automated pipeline for function doc generation. This and language documentation will be addressed in subsequent PRs.

Implementation strategy and design decisions

Load initial documentation into Docusaurus site.

Checklist

  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new ESLint warnings
  • I have reviewed any generated changes to the diagrams/ folder

Open questions

  • Auto-generate function documentation, possibly using the JSON output from TypeDoc
  • Add language documentation

@codecov
Copy link

codecov bot commented Feb 28, 2022

Codecov Report

Merging #897 (e577d4b) into main (cf8cf79) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #897   +/-   ##
=======================================
  Coverage   67.79%   67.79%           
=======================================
  Files          62       62           
  Lines        8120     8120           
  Branches     1769     1769           
=======================================
  Hits         5505     5505           
  Misses       2608     2608           
  Partials        7        7           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ce0a2da...e577d4b. Read the comment docs.

@cloudflare-pages
Copy link

cloudflare-pages bot commented Feb 28, 2022

Deploying with  Cloudflare Pages  Cloudflare Pages

Latest commit: e577d4b
Status: ✅  Deploy successful!
Preview URL: https://2b256015.penrose-panes.pages.dev

View logs

@cmumatt cmumatt changed the title Add initial documentation to Docusaurus site chore: Add initial documentation to Docusaurus site Feb 28, 2022
@cmumatt cmumatt marked this pull request as ready for review February 28, 2022 16:11
@maxkrieger
Copy link
Member

maxkrieger commented Feb 28, 2022

Copy link
Collaborator

@samestep samestep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks awesome, thanks so much for writing this up @cmumatt!

I wrote a few comments/suggestions (mostly just typo corrections).

Comment on lines +23 to +24
!Style
!Substance
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you clarify what exactly these are referring to? I don't see any files or folders in this PR whose name is Style or Substance (with a leading capital S).

packages/docs-site/docs/tutorial/basics.md Outdated Show resolved Hide resolved
@@ -85,9 +85,9 @@ forall Set x {
}
```

So, what are the shapes we can use? Currently, the system supports 12 different shapes, and you can find the specs for every shape [here](/docs/api/). It is a page that you will visit frequently as you work in Penrose.
So, what are the shapes we can use? Currently, the system supports 12 different shapes, and you can find the specs for every shape [here](/docs/ref/). It is a page that you will visit frequently as you work in Penrose.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to create a parent page for "Shape Library", and link to that? Currently this just links to the root documentation page, and if someone doesn't already have "Style" expanded in the sidebar, it's unclear where they're supposed to go from here.

@@ -113,7 +113,7 @@ Now it's time to see all of our hard work (drumroll please 🥁)! To compile you

## Exercise

We have now covered the differences between and usage of the `.dsl`, `.sub` and `sty` files. We have provided 3 exercises for you to help solidify the basics. You can work on each of these within the existing files - no need to make new ones. **Hint:** Make use of the shape specs [here](/docs/api/).
We have now covered the differences between and usage of the `.dsl`, `.sub` and `sty` files. We have provided 3 exercises for you to help solidify the basics. You can work on each of these within the existing files - no need to make new ones. **Hint:** Make use of the shape specs [here](/docs/ref/).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same question here.

@@ -129,7 +129,7 @@ _Since we are not defining all the properties that control how the shape will lo

![](/img/tutorial/tutorial1c3.png)

- **Challenge 4:** Keep 3 sets. For each set, represent `Set` as both a `Circle` and a square. There should be 6 objects on your canvas. (Hint: you will need to initialize another [Shape](/docs/api/) object!)
- **Challenge 4:** Keep 3 sets. For each set, represent `Set` as both a `Circle` and a square. There should be 6 objects on your canvas. (Hint: you will need to initialize another [Shape](/docs/ref/) object!)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here too

@@ -1,5 +1,6 @@
import { makeCanvas, shapedefs } from "@penrose/core";
import React from "react";
import seedrandom from "seedrandom";
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this! Weird that it didn't already show up in CI or something?

packages/docs-site/docs/ref/index.mdx Outdated Show resolved Hide resolved
packages/docs-site/docs/ref/index.mdx Outdated Show resolved Hide resolved
packages/docs-site/docs/ref/index.mdx Outdated Show resolved Hide resolved
packages/docs-site/docs/ref/style/index.mdx Outdated Show resolved Hide resolved
@cmumatt
Copy link
Contributor Author

cmumatt commented Mar 1, 2022

@cmumatt have you seen https://github.com/tgreyuk/typedoc-plugin-markdown/tree/master/packages/docusaurus-plugin-typedoc ? Not sure how well it works 😄

Yes, that is a good one!

That plugin is what generated the MD output for the functions. Unfortunately, the output is not useful just for function dictionaries; hence, the manual transformation step. The plan is to eliminate that step and automate the flow in a future PR. Appreciate the other links -- I will look through them, too!

cmumatt and others added 7 commits March 1, 2022 13:15
Co-authored-by: Sam Estep <sam@samestep.com>
Co-authored-by: Sam Estep <sam@samestep.com>
Co-authored-by: Sam Estep <sam@samestep.com>
Co-authored-by: Sam Estep <sam@samestep.com>
Co-authored-by: Sam Estep <sam@samestep.com>
@cmumatt cmumatt merged commit 33c882d into main Mar 2, 2022
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

Successfully merging this pull request may close these issues.

None yet

3 participants