forked from projects/fipamo
The official repo for Fipamo
ro
3c6322ec12
the last ui page that needed to be added was managing the main navigation menu for rendered pages, so that's been turned on. menu items can be added by pinning pages to the menu when editing them and can be removed by unpinning them or deleting them from the navigation edit ui it touched quite a few systems so all of those classes needed to be edited as well tweaking the front end script to work with the new modular script format |
||
|---|---|---|
| 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 | ||
| 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.