Finished the screen and logic for joining a space with an invitation link. Different variations for already used links or if you are already an member are needed.
Deployed the first version of my landing page for fibunu.com. I have lots of ideas to try out and implement - but that’s not on top of the priority list.
Tomorrow is my last day of my vacation in Italy. I enjoyed every day of it and was able to recharge my batteries. I’m highly motivated and can’t wait to to work on my app again.
European GDPR requires a privacy policy that shows transparently which data you collect and how you use it. Yet any of those generators that create legally safe policies throw out a bunch of texts nobody reads and understands. Why can’t we show this in a nice way?
Added the members screen to the space settings. Create links to enable friends, family members or other persons to join your space. Let them see your financial situation or let them help track everything.
Added a basic profile page. It’s not the most important part to add the functionality to delete your account. But I hate it when I have to call somewhere/write an email to get my account deleted. Will also add a text field where you can give reasons for deletion.
I am really struggling to find time for my sidehustle this month. So much other stuff going on in my life right now. I appreciate every minute I can work on my app 😍
Started to work on the website for @fibunuapp. I want to keep it simple with just the most important info on it. The website is built with @nuxt_js and @tailwindcss.
Current folder structure of my monorepo. It‘s divided into „apps“ (the consuming packages that have a build step) and „packages“ (shared code that can be used in any app). For now I use @vite_js for all build steps and the dev server.
Follow up showing the folder structure of the server application. The sql folder inside the src folder contains code to preload and provide the available queries from the root sql folder.
Current folder structure of my monorepo. It‘s divided into „apps“ (the consuming packages that have a build step) and „packages“ (shared code that can be used in any app). For now I use @vite_js for all build steps and the dev server.
Current folder structure of my monorepo. It‘s divided into „apps“ (the consuming packages that have a build step) and „packages“ (shared code that can be used in any app). For now I use @vite_js for all build steps and the dev server.
A post from @pie6k about local packages inside a monorepo let me rethink my current setup. I decided to remove the build step from each shared package and build it together with the app that is consuming it.