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

Run content tests from raku/doc on templates #103

Open
coke opened this issue Feb 17, 2023 · 3 comments
Open

Run content tests from raku/doc on templates #103

coke opened this issue Feb 17, 2023 · 3 comments

Comments

@coke
Copy link
Contributor

coke commented Feb 17, 2023

Now that content templates and web-specific pages exist in doc-website, we should run many of the content tests in raku/doc also on raku-doc-website.

We should do this in a way which avoids duplication of the tests and configs (e.g. list of allowed words).

Includes spelling, preferred phrasing, duplicated words, etc.

@coke coke added this to the Cleanup milestone Feb 17, 2023
@finanalyst
Copy link
Collaborator

I entirely agree with a division of content and visualisation.
The web-specific pages are in Website/structure-sources/. These are rakudoc / pod6 format. So whatever utilities run on raku/doc will run on raku/doc-website. I suggest that these binaries are all placed in binary-files, rather than create another directory.

@coke coke modified the milestones: Cleanup, 2023-Quarter 1 Feb 24, 2023
@coke
Copy link
Contributor Author

coke commented Mar 11, 2023

See Raku/doc#4263

@finanalyst
Copy link
Collaborator

I don't see how to do this without some form of duplication of files

Is it possible to put the test utilities in a 'sub-repo' so that both Raku/doc and Raku/doc-website can source the utilities from the same place? Then the utilities can be run in their own work flows.

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

2 participants