forked from projects/fipamo
The official repo for Fipamo
ro
252059df19
turned on the abiity to save settings to config file via the settings page the current member session needs to updated by the data coming in but that will be handled by a specific member service that hasn't been built yet, so just commenting it out for now also fixed a minor bug that was stopping the save on render toggle from working correctly, so now it's saving and updating the status properly now |
||
|---|---|---|
| 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.