Ensure all appropriate test cases are met and exceptions gracefully handled. If required attributes are missing, let the user know through detailed yet concise error messages in the console output. Include validation on specific attributes if they need to fit a certain format.

Will need to also replace the current Mix version with the latest version, and swap out Sass for PostCSS.

Create a simple cleaver-blog-starter template that contains a few test posts, and a basic centered text roll layout. Highlight the content, but create spaces to add featured images, meta information, author attributes, etc.

Thank you for making this awesome tool!

I can see in the release-notes that:
External JSON files can now be imported into content by storing them in a resources/data directory and then referencing their path in your content file's JSON (see hello-world.json for an example of this)

I see "imports": "/data/example.json", but how do I reference it in the view?

The entire codebase leaves a lot to be desired and is honestly kind of a mess. It could stand to be refactored from the ground up, and would make a nice addition to the next major version (2.0).

Additionally, it should utilize PHP 8.0 or even 8.1 methods and as such will require the necessary version on release.

Describe the issue

Hi there,
There is no reference to laravel-mix on package.json and none of the scripts is working as they all are using mix.

To reproduce the bug

Run npm install and then run npm run dev

Environment details:
N/A

Screenshots
If applicable, add screenshots to give more details about the bug. This will greatly improve the ability to debug and troubleshoot the issue.

Additional info
If you have any other information that would be helpful to know about this, please write it here!

Use case and scenario would be something like, a catalog site with multiple different products. Instead of copying/pasting different sections of products for each page and having to maintain those files, have one large JSON file of products that can be imported to each page under a variable name. Then using collections, filter off the ones desired on each page.

Related to #5

Format and organize the data coming out of the terminal to both look better and be more relevant to build information.

Current output looks something like:

+ /Users/andrew/sites/cleaver.test/resources/content/index.json built successfully.
+ /Users/andrew/sites/cleaver.test/resources/content/posts/test-post.json built successfully.
- /Users/andrew/sites/cleaver.test/resources/content/hello-error.json could not be rendered, skipping this page.
* 2 pages built in 31.51ms *

Updated might look something like:

+ hello-world.json rendered to /
+ test-post.json rendered to /posts/test-post
- hello-error.json missing path attribute, skipping

• Build Summary •
+ 2 pages built in 31.51ms
- 1 page could not be built

Additionally, should also ensure formatting is a bit more spaced out, leaving room for commands above/below. Take notes for how Laravel mix outputs compiled asset info.

By default in the build process, include tailwind-css-purge to remove unused classes from the built CSS. Should significantly reduce overall asset size.

From: https://twitter.com/TeamJakic/status/1209441873829519361

During the process of compiling JSON (from either flat JSON files or Markdown), add in the ability to pass through filters/organizers/modifiers to that data before it gets returned to the Blade templates. Maybe look into collections?

Hello,
I have my own assets workflow and I just want to process data without other extensions.
Thank you.

E.g. Netlify or Vercel. Additionally, include documentation or a link on the README to enable users to deploy their own site directly from this repo.

Hello,

I just tried a fresh install, but the website does not load.
localhost:3000 turns forever whereas the browsersync ui loads perfectly.

It did not tried to tweak anything, yet. It's out-of-the-box.
I cannot understand what I'm doing wrong.
Can you help, please ?

I'm using MacOS 10.15.5 and PHP 7.4

As an additional command to the build sequence, give the ability to build only specific pages by providing either a content filepath/name (e.g. docs.json), or the path specified in the file (e.g. /docs).

One of the largest features to be added to Cleaver so far, this would give users the ability to quickly scaffold a starter site with example content and assets. The flow would look something like this:

• Install Cleaver from the command line via composer create-project aschmelyun/cleaver project-name
• cd into the project directory
• Run php cleaver make blog or php cleaver make docs
• Edit and add to the newly-added resources/content and resources/views files
• Build your site with php cleaver or npm run dev

How this should work in the background is fairly simple. The make command will take an argument after it, and determine if it is:

1. Listed as a shortcode for an official Cleaver scaffold (e.g. blog, docs) that ties to a GitHub URL in the source
2. A valid GitHub URL

If either of those is true, the application removes all files from inside the resources directory (or the directory itself), and replaces them with the contents of the cloned git repository, passed in or accessed via shortcodes. The git repositories should be organized and set up as an incredibly simple structure, laid out the same way that the resources directory is.

This allows for people to create their own Cleaver starter templates and let other developers use them without having to manually clone the git repository, download the content files, or open a PR for command-line additions.

Include a package or functionality to automatically add RSS feed of all items to /feed. This should be stored as a setting and can be turned on or off with a boolean value.

Like with hard-coded data files included in the src directory, give the user the ability to pull in data from an external URL's source. Should fire the call off with zttp, headers for JSON data, and reject if it's not in the proper format instead of erroring out.

Using a combination of Lighthouse scores and the Accessibility Insights for Web extension, ensure accessibility standards on all pre-created templates and demo sites are met.

This includes proper semantics in HTML, color contrast, font size and placement, etc.

command.get('php cleaver build', (error, stdout, stderr) => {
^

TypeError: command.get is not a function

when running npm run watch and trying to save a file

Include in a resources/views/components directory, use purely anonymous (e.g. classless) components for now.

Right now, the path attribute is required in all content files. Instead of throwing an error if that is missing, auto-generate the output based on the file structure in the resources/content directory.

For example:

• resources/content/posts/test-post.json should automatically render out an HTML file to dist/posts/test-post/index.html if there's no path attribute available
• If a path attribute is present, that acts as an override to the path/name of the content file

Add support for using .env files, with vlucas/phpdotenv

Create a simple cleaver-catalog-starter template that highlights Cleaver's ability to generate and build data-driven sites via JSON. An online catalog of various products with specific attributes (think mechanical keyboards, computer parts, auto accessories), would be perfect for example content used alongside this.

e.g. ability to pull content down from headless, hosted CMS platforms like Contentful, Prismic, or even WordPress's REST API.

The goal is to be able to pull content down from those platforms, and then use it to build out pages in a predictable manner instead of using flat JSON files. This should boost the usability of Cleaver up significantly higher 🚀

#49 will need to be implemented first, for storing things like access tokens to the above platforms.

Is there any reasons as to why Cleaver doesn't use parsedown-extra by default?

Rather than having ugly CSS where you're selecting the nth-type of an element on a page, it could be solved by adding the classes to the markdown file as such:

[Click Me](https://aschmelyun.com/){.btn}

Switching out the standard parsedown package for parsedown-extra doesn't seem to break anything out of the box, and all the tests pass as before.

Create a simple cleaver-docs-starter template that works similar to the current usecleaver.com/docs page. Ensure at least a few test pages of content are included, and potentially add some interactivity via Vue.