your personal website on atproto - mirror blento.app

Compare changes

Choose any two refs to compare.

+46 -19
+6 -10
README.md
··· 1 1 # blento 2 2 3 - Alpha version can be tried at https://blento.app 3 + public beta version can be tried at https://blento.app 4 4 5 - Your personal website in a bento style layout, using your bluesky personal data server as a backend. 5 + Your personal website in a bento style layout, using your atproto personal data server (the tech that bluesky runs on) as a backend. 6 6 7 7 made with svelte, tailwind and hosted on cloudflare workers. 8 8 ··· 12 12 13 13 This started as a replacement/alternative for bento.me which is shutting down in a few weeks (Feb 2026) after being bought by a competitor ^^ I wanted to build a version that couldn't just shut down or where it would be very easy to spin up a new version (with all the data) should the old one disappear. 14 14 15 - That's why all your data is saved on your bluesky personal data server, so you can start setting up your website on blento.app, but then anytime you want to start self hosting you easily take your data with you (dedicated forks optimized for self hosting on different platforms coming soon). 15 + That's why all your data is saved on your atproto personal data server, so you can start setting up your website on blento.app, but then anytime you want to start self hosting you easily take your data with you (dedicated forks optimized for self hosting on different platforms on the roadmap). 16 16 17 17 Should blento.app shut down at some point, someone else can also spin up a new version that shows all blentos (note: it's MIT licensed so you _could_ do that now too and offer a competing service, but please don't (except for self-hosting your own profile ofc), legal != nice). 18 18 19 - One other note: for most independence I encourage everyone to get their own domain and either self host or redirect to blento.app/your-profile (still working on a way to make this as easy as possible for non-technical users, if you have any suggestions please reach out). 20 - 21 - ## Selfhosting 22 - 23 - See [docs/Selfhosting](./docs/Selfhosting.md). 19 + One other note: for most independence I encourage everyone to get their own domain see [how to setup a custom domain](./docs/CustomDomain.md), selfhosting on the other hand while currently possible is not encourage *yet* before this project reaches a more stable state (if you do want to selfhost though, see [here](./docs/Selfhosting.md)). 24 20 25 21 ## Making Custom cards 26 22 ··· 28 24 29 25 ## Contributing 30 26 31 - See [docs/Contributing](./docs/Contributing.md) 27 + Contributions are very welcome, see [docs/Contributing](./docs/Contributing.md) for more info. 32 28 33 29 ## Idea for a card? 34 30 35 - Open an issue 31 + Open an issue, see [here](https://github.com/flo-bit/blento/issues/93) for card ideas that are already planned. 36 32 37 33 ## License 38 34
+10 -4
docs/Contributing.md
··· 1 1 # Contributing Guidelines 2 2 3 - Contributions are very welcome ๐ŸŽ‰ 4 - 5 3 For creating new cards see [here](CustomCards.md) (and check out [existing card ideas](CardIdeas.md)) 6 4 7 5 ## Development ··· 16 14 17 15 ## AI assisted development 18 16 19 - You can submit PRs written with AI but please make sure: 17 + You can submit PRs written with AI assistance but please make sure: 20 18 21 19 - there's no extra unnecessary changes/unnecessary verbose code (keep it simple) 22 - - you test everything yourself (in light/dark mode, with and without colored cards, in edit mode and not in edit mode) 20 + - you test everything yourself 21 + - in light/dark mode 22 + - with and without colored cards 23 + - in edit mode and not in edit mode 24 + - on mobile and desktop (note that there's two different mobile "modes", one dependent on screen size and one enabled when pointer: coarse) 25 + 26 + ## Subpages 27 + 28 + currently subpages exist but are not used yet, they are perfect for testing things though (as otherwise your profile on blento.app will show e.g. cards that dont exist on the deployed version yet), in the development verion go to `/your.handle/{pagename}/edit` to edit a subpage (where pagename can be any string that is not "edit" or "api") (note that currently when you login you always get redirected to your main page)
+7 -3
docs/CustomCards.md
··· 1 1 # Custom Cards 2 2 3 - see `src/lib/cards` for how cards are made (and e.g. `src/lib/cards/EmbedCard/` and `src/lib/cards/LivestreamCard/` for examples of implementation). 3 + see `src/lib/cards` for how cards are made. 4 4 5 5 Notes: 6 6 7 - - Cards should be styled to work in light and dark mode (with dark: class modifier) as well as when cards are colorful (= bg-color-500 for the card) (with accent: modifier). 8 - - Please test newly created cards both when editing (/your-user/edit) and in your user profile when saved (/your-user) 7 + - Cards should be styled to work in light and dark mode (with dark: class modifier) as well as when cards are colorful (= bg-color-400/500 for the card) (with accent: modifier). 8 + - Please test newly created cards: 9 + - in light/dark mode 10 + - with and without colored cards 11 + - in edit mode and not in edit mode 12 + - on mobile and desktop (note that there's two different mobile "modes", one dependent on screen size and one enabled when pointer: coarse)
+5
docs/CustomDomain.md
··· 1 + # Custom domain 2 + 3 + For most independence I encourage everyone to get their own domain that redirects to blento.app (with a CNAME redirect), to connect your custom domain, on blento.app click on your profile icon in edit mode (top right corner) and select "custom domain". 4 + 5 + If you want to buy a domain, I suggest cloudflare, as they sell domains at-cost and for root domains (like domain.com instead of blento.domain.com), cloudflare also offers CNAME flattening.
+12
docs/Roadmap.md
··· 1 + # Roadmap 2 + 3 + more specific roadmap coming soon. 4 + 5 + - more cards (especially atmosphere cards) (see https://github.com/flo-bit/blento/issues/93) 6 + - make subpages actually usable for everyone 7 + - basic analytics 8 + - lots of bug fixing/QoL improvements 9 + - maybe: supporter/"pro" features? 10 + - move auth to backend 11 + - lexicon 12 + - general cleanup
+5
docs/Selfhosting.md
··· 1 1 # Selfhosting with cloudflare workers 2 2 3 + I currently advise everyone to *not* selfhost, as long as this project is still in the beginning stages with lots of changes every day, isntead I'd suggest setting up a custom domain (see [here](./CustomDomain.md)) and only later once this project is more stable to selfhost, thanks to the magic of atproto, you'll just have to change where your domain points to and setup the selfhosted version and your content will magically transfer over. 4 + 5 + If you do still want to give selfhosting a try now, some features/cards may break on your selfhosted version, in that case sync with the upstream repo. 6 + 7 + 3 8 1. fork this repo 4 9 2. create a cloudflare worker application and connect it to your fork 5 10 3. change the vars in `wrangler.jsonc` (including https:// in the PUBLIC_DOMAIN var!)
+1 -2
wrangler.jsonc
··· 45 45 }, 46 46 { 47 47 "binding": "CUSTOM_DOMAINS", 48 - "id": "f449b3b5c8a349478405e2c04ed265f0", 49 - "remote": true 48 + "id": "f449b3b5c8a349478405e2c04ed265f0" 50 49 } 51 50 ] 52 51