Hey, so this this works pretty well but some things to note:

• The GH action workflow will re-commit changes after it generates the commands list. This sometimes (well, many times) creates a race condition situation. I added a retry but maybe you have a better approach. Might also be good enough as-is though, as you can just re-run the job if needed and it should work. ie. It won't break anything.

• The packages and versions are updated in the manifest file.

• I left the styling for you but added some sensible defaults.

• The packages don't install on anything below 8.x as it would require some logic to reconcile the version numbers. Composer throws dependency requirement error, but it won't crash the workflow. Probably not worth adding support?

Feel free to take ever the PR of course, but if there's anything you want me to tweak let me know. And of course if you hate it, no need to merge it ha ha. It seems like a lot of work but I took it on to practice a complex GH action workflow, so it time well spent regardless!

https://user-images.githubusercontent.com/1478421/105506846-1264a880-5cfd-11eb-87f8-2bcb3fb18d4b.mp4

Hey James! 😄

This PR adds a dark mode to the site. I'm by no means a designer so you might not be happy with the changes I've made, but hopefully, it can at least provide a good starting point. I've also not got too much experience with Nuxt so there's a possibility that some of the stuff I've done can be done much better.

I also couldn't get npm run dev to run because I kept getting this error:

Error: Cannot find module 'tailwindcss/defaultTheme'

Running npm install tailwindcss seemed to fix it. I don't know if this was an issue with the repo or just something on my end that I wasn't doing right? But if it needs removing again from the package.json, I'll make sure to revert that back.

I've attached some images to give you a comparison of the light and dark modes. Hopefully, you're happy with the general approach. If this is something that you might consider merging but you want some changes making first, let me know and I'll do them ASAP :)

In order to quickly use documentation provided by artisan.page via external sources like Alfred, it would be great if a search could be made through the query params. This commit will allow a user to find documentation by adding ?search={query} to the URL and actually making a search. The value of the search field will then be populated by the query param.

Thank you for your consideration.

Wanted to write some Vue code and saw someone request this on twitter so I figured why not. Let me know if I missed something!

https://user-images.githubusercontent.com/1478421/105005995-9fdb9a80-5a68-11eb-9e8f-41d691e0e3f5.mp4

For an enhancement if #9 merges in, you could remove the manifest file and add a composer.json file, and set up dependabot to auto run the build process when a package makes a release (I think dependabot triggers action, but not 100% sure). That way you won't have to monitor any changes, and only need to update the supported packages/ laravel versions as needed.

It might also help the build run faster as I don't think composer is currently being cached since there is no lock file.

I'm happy to implement this if you'd like. Would be good practice for me.

Hey @jbrooksuk! This is just a small PR that makes a couple of tiny changes.

The first change I've made is enabling smooth scrolling across the entire page. My thinking behind this is that it will make the page feel smoother when clicking on the links in the side navbar (and match the smooth scroll behaviour of the "back to top" button).

The second change I've made is to add some counts to the navbar groups (like in the screenshots below). My thinking behind this is that it could make it easier for people to spot when new commands have been added to the framework. I like this feature because I'm a bit of a sucker for counts/numbers everywhere and they help me to visualise things, but that might not be the same for everyone else haha!

If you think these are worth merging, feel free to give me a shout if anything needs changing. If you'd prefer not to merge them though, that's totally cool! 😄

Hey James!

This PR adds a list of the commands to the left-hand side of the page in the desktop view. I thought it'd be a pretty nice way of being able to quickly view the available commands.

I've taken the same sort of approach with how php artisan would work if you ran it in your console (like in the screenshot). So, the 'ungrouped' commands that don't have a prefix before : will be placed at the top of the list. Any after that will then be grouped by their prefix.

Each of the commands on the left-hand side take you straight you to the command info when clicked on, so it acts as a form of navigation.

I've not added anything for the mobile view because I thought it might just get in the way more than anything. If you think a mobile list would be useful though, I'd be happy to get one added.

By the way, I'm by no means a JS developer, so if there's anything that I've done that looks a bit odd, I apologise in advance haha!

Hopefully it's something that you'll consider pulling in, but if you do need any changes making for it, please let me know 😄

I added a basic config for eslint. If you want, I can probably automate it to auto fix on pre-commit or something like that (so you don't have to rely on the editor)

Not sure if you left it for later or if you wanted to avoid using the official one.

I think it's better than the default Nuxt one for now anyway ¯_(ツ)_/¯

If you look for "Cache" you will get the command "optimize" as it has "Cache" in its description instead of "cache:clear" that has "cache" in the title.

In mobiles (using Gboard, and some other keyboards) the v-model does not work until you hide the keyboard.

Here is a comment from Evan You: https://github.com/vuejs/vue/issues/9777#issuecomment-478831263

Hey James, this PR adds an api endpoint to query the docs. I also upgraded Nuxt 2 to Nuxt bridge, which essentially adds v3 features to v2.

Files changed followed the migration guide here: https://v3.nuxtjs.org/bridge/overview

I've only tested this locally so far so there could be further cors setup required.

List all commands:

GET /api

Search for a command:

GET /api?s=database

Specify a version:

GET /api?v=8.x

closes #25

Have you though about adding api endpoints that show available commands and descriptions?

I think if you upgrade to nuxt 3 it's built in (maybe even in nuxt 2, I just don't know).

https://v3.nuxtjs.org/guide/features/server-routes

It could then be consumed by something like Alfred or Raycast. I wrote a Forge Raycast extension and was thinking to show available artisan commands by Laravel version that can execute via the site command endpoint.

I thought about getting the commands from the server like the build command here does, but that might be too intrusive, while an API would be perfect (or I do both and have the former be opt in).