diff --git a/assets/css/custom.css b/assets/css/custom.css index e1e4b20..551b888 100644 --- a/assets/css/custom.css +++ b/assets/css/custom.css @@ -40,26 +40,6 @@ position: static } -.absolute { - position: absolute -} - -.relative { - position: relative -} - -.top-0 { - top: 0px -} - -.right-0 { - right: 0px -} - -.m-8 { - margin: 2rem -} - .mt-0 { margin-top: 0px } @@ -72,10 +52,6 @@ margin-bottom: 2rem } -.mt-8 { - margin-top: 2rem -} - .inline-block { display: inline-block } @@ -100,6 +76,10 @@ flex-direction: column } +.justify-end { + justify-content: flex-end +} + .justify-center { justify-content: center } @@ -172,11 +152,6 @@ line-height: 1.75rem } -.text-2xl { - font-size: 1.5rem; - line-height: 2rem -} - .font-extrabold { font-weight: 800 } @@ -214,12 +189,6 @@ background-color: var(--color-primary-700) !important } -@media (min-width: 640px) { - .sm\:flex-row { - flex-direction: row - } -} - @media (min-width: 768px) { .md\:grid-cols-2 { grid-template-columns: repeat(2, minmax(0, 1fr)) diff --git a/content/_data/works/laravel-rad-stack.md b/content/_data/works/laravel-rad-stack.md index a36bdc9..a858835 100644 --- a/content/_data/works/laravel-rad-stack.md +++ b/content/_data/works/laravel-rad-stack.md @@ -1,4 +1,4 @@ -A heavily customized `Laravel 8` boilerplate starter-kit with complete BO solution, with posts management as main demo feature. On frontend/assets side it's relies on last technologies, i.e. `pnpm` + `Vue 3` + `Typescript` with nice [template setup](https://v3.vuejs.org/api/sfc-script-setup.html) as default syntactic sugar, and finally `WindiCSS` as CSS utility framework. You can easily ditch WindiCSS for `Tailwind` if you prefer, as it's almost the same API. +A heavily customized `Laravel 8` boilerplate starter-kit with complete BO solution, with posts management as main demo feature. On frontend/assets side it's relies on last technologies, i.e. `pnpm` + `Vue 3` + `Typescript` with nice [template setup](https://v3.vuejs.org/api/sfc-script-setup.html) as default syntactic sugar, and finally `Windi CSS` as CSS utility framework. You can easily ditch Windi CSS for `Tailwind` if you prefer, as it's almost the same API. The BO dev API is similar to my last `Vuetify Admin` project but rewritten in more customizable components. You have complete **DataTable** with pagination, sorts, global search, filters, Excel export, customizable row actions with nice Dev-side API. It has a nice **BaseForm** which reduces forms code boilerplate, with a few supported form inputs (you can easily create your own). It's also support direct right-aside editing with proper URL context (see users management on demo). All BO relies on [Inertia](https://inertiajs.com/) for minimal API glue boilerplate. diff --git a/content/_index.md b/content/_index.md index 1c41f5a..5d83ffc 100644 --- a/content/_index.md +++ b/content/_index.md @@ -7,12 +7,14 @@ description: "This is adr1enbe4udou1n blog." A 🧔🌍💻 aka senior web developer @Bretagne 🇫🇷 {{< /lead >}} -Hi folks, I'm a web lover working [@Cesson-Sévigné](https://fr.wikipedia.org/wiki/Cesson-S%C3%A9vign%C3%A9). Mastering `Vue 3` with `Typescript` for frontend as well as `Laravel` and `Symfony` as main backend frameworks on modern `PHP 8+`. +Hi folks, I'm a french web lover actually working [@Cesson-Sévigné](https://fr.wikipedia.org/wiki/Cesson-S%C3%A9vign%C3%A9), mastering `Vue 3` and `Typescript` on frontend side as well as `Laravel` and `ASP.NET Core` as main backend frameworks. Use preferably utility-first CSS framework as `Tailwind` / `Windi CSS`, but also comfortable with `Sass` with **BEM** implementation. -I love develop proper API design following `DDD` + `Hexa` principles if applicable. My favorite backend stack is `ASP.NET Core` and `C#`. I'm also comfortable on [`Nest.js`](https://nestjs.com/) with combination on [`MikroORM`](https://mikro-orm.io/). I also used [`FastAPI`](https://fastapi.tiangolo.com/) as well as `Spring Boot` (*Java*). +I love develop proper API design following `DDD` + `Hexa` principles if applicable. My favorite backend stack is `ASP.NET Core` and `C#`. I'm also comfortable with [`Nest.js`](https://nestjs.com/) associated to [`MikroORM`](https://mikro-orm.io/) (*Typescript*), [`FastAPI`](https://fastapi.tiangolo.com/) (*Python*), and [`Spring Boot`](https://spring.io/projects/spring-boot) (*Java*). -Furthermore, I encourage `TDD` or at least proper **integration tests** on all types of backend frameworks, following `AAA` aka *Arrange Act Assert* principle. Mastering `PHPUnit` or [`Pest`](https://pestphp.com/) for *PHP*, `xUnit.net` with [`Fluent Assertions`](https://github.com/fluentassertions/fluentassertions) for *.NET Core*, `JUnit` with [`REST Assured`](https://rest-assured.io/) for *Spring Boot*, `Jest` and `pytest` on respective *NodeJS* end *Python* stacks. +I encourage `TDD` or at least proper **integration tests** on any backend frameworks, following `AAA` aka *Arrange Act Assert* principle. Mastering `PHPUnit` or [`Pest`](https://pestphp.com/) for *PHP*, `xUnit.net` with [`Fluent Assertions`](https://github.com/fluentassertions/fluentassertions) for *.NET Core*, `JUnit` with [`REST Assured`](https://rest-assured.io/) for *Spring Boot*, `Jest` and `pytest` on respective *NodeJS* end *Python* stacks. -Fully embracing app containerization as `Docker`, from local, staging to production. I push to use `CI/CD` whenever is possible with proper configuration. I personally use [`Drone CI`](https://www.drone.io/) and `GitLab` as main CI/CD solutions. +Fully embracing app containerization with `Docker`, from local, staging to production. I push to use properly configured `CI/CD` whenever is possible in order to enforce linting and coding standard at any languages ([`ESLint`](https://eslint.org/), [`Prettier`](https://prettier.io/), [`PHP CS fixer`](https://cs.symfony.com/), [`PHPStan`](https://github.com/phpstan/phpstan), [`Black`](https://black.readthedocs.io/en/stable/), [`mypy`](http://mypy-lang.org/), and so on...). I personally use [`Drone CI`](https://www.drone.io/) and `GitLab` as main CI/CD solutions. -Mastering installations of `Docker Swarm` clusters with [`Traefik`](https://traefik.io/traefik/) as cloud proxy and [`Portainer`](https://www.portainer.io/) as proper GUI system for cluster management. I personally use combinations of `Grafana`, `Loki`, `Prometheus`, `Jaeger` as main *logging*, *metrics* and *tracing* tools. +Mastering installations of `Docker Swarm` clusters with [`Traefik`](https://traefik.io/traefik/) as cloud proxy and [`Portainer`](https://www.portainer.io/) as nice GUI for cluster management. I use `Loki`, `Prometheus` and `Jaeger` as respective *logging*, *metrics* and *tracing* tools, all combined to `Grafana` as GUI dashboard builder for *Ops*. Have some experiences with many cloud providers as [Digital Ocean](https://www.digitalocean.com/), [Hetzner](https://www.hetzner.com/), [OVH](https://www.ovhcloud.com/), [Scaleway](https://www.scaleway.com/). + +See some of [my open sourced works]({{< ref "works" >}} "Okami101 Works"). diff --git a/layouts/works/single.html b/layouts/works/single.html index 251276b..5ef111f 100644 --- a/layouts/works/single.html +++ b/layouts/works/single.html @@ -21,19 +21,18 @@
{{ range .projects }}
-
+

{{ .title }}

- - {{ if .date }} -
- {{ partial "badge.html" (print "Date : " .date) }} -
- {{ end }}
+ {{ if .date }} +
+ {{ partial "badge.html" (print "Date : " .date) }} +
+ {{ end }}
{{ readFile (print "_data/works/" .name ".md") | markdownify }}