forked from projects/fipamo
The official repo for Fipamo
ro
36d04c8f68
service classes are beginning to swell as there functionality is being fleshed out, so a new organizational structure was needed to make sure class sizes don't become too large and to increase site managability and legibilty as more features get added and the code base grows. data is for retrieving, managing site information, assets interact with external files and upkeep is for maintenance. some additional tweaks were also made to the options menu template to prep it for it's transition to a toolbar component |
||
|---|---|---|
| app | ||
| bootstrap | ||
| config | ||
| content | ||
| 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.