Getting Started • Roadmap • License
- Elixir and Erlang latest version
- Node.js version > 18
- Rust version 2021 (stable) toolchain installed
Below is an example of how you can instruct your audience on installing and setting up your app. This template doesn't rely on any external dependencies or services.
# Clone this repository
$ git clone https://github.com/abehidek/hidek.xyz
# Go into the repository
$ cd hidek.xyz
# Setup developer environment
$ mix setup
# the command above will:
# - install all dependencies from Elixir/Rust/Node.js
# - prepare SQLite3 database
# - build assets
# - run migrations
# - seed database.
# Run the Phoenix server
$ mix phx.server- fully dark mode
- same font for everything
- content > features
- each publication is an article, which are defined in the /content folder
- create pers design system for all my side projects (including this one)
- penpot or quant-ux?
- similar to shadcn/ui but for phx?
- do some security stuff (paraxial.io) to not explore app
- mdx or web-components inside content articles
- use turso as sqlite db and change deploy from fly.io to another host plataform (for better speed)
- embbed 3D model using blender? and three.js
- blurred image placeholder?
- use rustler with rust functions for better parsing of markdown
- use rust for parsing MDX into HTML + JS
- convert obsidian vault into pages
- hidek pronunciation using IPA (International Phonetic Alphabet)
- fav music/movie/books
- my gear page
- resume: my cv and job history
- receive crypto page
- signal boost (friends and people looking for job)
- my self hosted stuff
- projects page
- guestbook
- live components
- what I'm currently working on
- what I'm hearing
- home server status
- website status (number of req/s, commit, build info and other monitoring stuff)
- first principles thinking
- pers rice and why we should aim for simplicity
- future of livebook
- brilliance of impermanence systems
- zfs stuff?
- rss could be better, but it's the best we have today
- nostr status?
- pers recommended topics for depthing compsci understading
- about clean code and other "industry" practices
- using elixir for simplifying infra
- self-hosting stuff
- disclaimers about self-hosting
- tunneling and how to properly expose your self-hosted service
- network basics for self-hosting
- why you should replace your ISP router
- show your work!
- elixir future on dx
- opinions on economics/finance
- hacking remarkable 2
- why type systems are important
- microservice, nosql and etc...
- obsidian for knowledge management
- re: email vs capitalism, or, Why we can't have nice things
- content: why you should you use nix
- feat: add liveview components such as like, view count, presence
- presence
- view count
- like
- feat: rss.xml generated automatically
- feat: use liveview for page transition (smooth)
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!
- Fork the project
- Clone it open the repository in command line
- Create your feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add some amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a pull request from your feature branch from your repository into this repository main branch, and provide a description of your changes
Copyright (c) 2023 Guilherme Hidek Abe
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
hidek.xyz · GitHub @abehidek · Twitter @guilhermehabe