forked from projects/fipamo
The official repo for Fipamo
ro
ceeb4a2573
routing needed more nuance than what was possible in the web routing controller, so a new RouteContoller was created to identify requests and then sending them to the correct controller to get the appropriatie page this was necessary because routing the previous was erroring out because when the system was looking for pages to display with dynamic page creation it would get confused with prexisting routes and choose to display whatever the Start Controller was capturing, ignoring routes defined in the web controller. but that's been cleaned up without having to re-write everything and continues to use existing controllers |
||
|---|---|---|
| app | ||
| bootstrap | ||
| config | ||
| content/themes/fipamo-default-v2 | ||
| database | ||
| public | ||
| resources | ||
| routes | ||
| storage | ||
| tests | ||
| .babelrc | ||
| .editorconfig | ||
| .env.example | ||
| .eslintrc | ||
| .gitattributes | ||
| .gitignore | ||
| .php-cs-fixer.php | ||
| .prettierignore | ||
| .prettierrc | ||
| artisan | ||
| composer.json | ||
| composer.lock | ||
| LICENSE | ||
| package.json | ||
| phpunit.xml | ||
| README.md | ||
| vite.config.js | ||
Fipamo means to save
The Fipamo project was born from a need for a simple, easy to use no data blog platform that doesn't require much effort to set up and maintain. Fipamo uses Markdown to handle posts and renders them to flat html so you can serve them from anywhere. No complicated set ups. No long list of dependencies. Just set up and go.
Because it's the 21 century. This should be easy.