forked from projects/fipamo
The official repo for Fipamo
ro
efb2e4f0bd
theme controller was getting top heavy, so an asset service class was plugged in to handle moving assets around for theme testing and eventually to production when HTML rendering is set up |
||
|---|---|---|
| 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 | ||
| .stylelintrc | ||
| artisan | ||
| composer.json | ||
| composer.lock | ||
| 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.