astrotomic / stancy Goto Github PK

Add a default nginx config to serve static HTML files and Laravel app as fallback.

Add custom exception classes and implement ignition solutions, if possible.

Add a default caddy config to serve static HTML files and Laravel app as fallback.

https://github.com/Astrotomic/stancy-laravel-demo

The demo app should show the basic features and in best case contain some integration tests using spatie/phpunit-snapshot-assertions. Only simple tests like: if I call this url/route I expect this response/html/snapshot.

relates to #8

Generate a forestry.io template file by a page data class.

• _view - the blade view
• _pageData - the page data class
• _sheets - a list of sheets that should be loaded

blocked by spatie/sheets#44

The package should provide a make:page command to simplify the process to create a new page.

The command should create the markdown file including YAML frontmatter head and an optional page data class.

• The make command should only work if the default filesystem repository is used in the sheet collection
• It should use the filesystem of the sheet repository
• It should add the page data class to the YAML frontmatter
• The default namespace for the page data class is App\Pages
• It should accept sheet collection and path as arguments
• The path should be possible with(out) extension
• It should use stub files to generate the files

https://github.com/Astrotomic/stancy-lumen-demo

The demo app should show the basic features and in best case contain some integration tests using spatie/phpunit-snapshot-assertions. Only simple tests like: if I call this url/route I expect this response/html/snapshot.

relates to #9

It should be possible to add macros to the page model.

Add a facade to access the \Astrotomic\Stancy\Factories\PageFactory via \Astrotomic\Stancy\Contracts\PageFactory service bindung.
The Facade should have all relevant methods as doc-tag for IDE support.
The naming of the facade should be PageFactory without any suffix.

blocked by #20

It should be tested if it's compatible with netlify. In best case including the redirects to backend to still support POST requests.

The whole documentation is missing and should be added.
It should cover basic usage but also have sections for every single component which describes it in detail for more advanced usage.

Every single improvement is welcome, so don't mind if you only add a single sentence or a whole section.
Atm the unittests are a good place to see some usage examples. But also the demo apps should get more content to look at.
If there are any questions I will ry to answer all of them.

The workflow stale-issues.yml is referencing action actions/stale using references v2.0.0. However this reference is missing the commit af4072615903a8b031f986d25b1ae3bf45ec44d4 which may contain fix to the some vulnerability.
The vulnerability fix that is missing by actions version could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider to update the reference to the action.

blocked by #18

A possible Integration with sitesauce should be tested. Optional some commands/events/triggers added to deploy after content change.