polish README closes #158 #178
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
question
S
UX research
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: local-it/mitgliederverwaltung#178
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/#158-polish-README"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Generated a new polished README by running analyzation over the repository.
up for discussion:
what do you think?
@ -4,0 +107,4 @@# Inside the repo folder:mix local.hex 2.1.1mix archive.install hex phx_new 1.7.20We use phoenix 1.8 now
I think we could even leave out the versions here completely and just assume the newest version of hex should work 🤔
WIP: polish READMEto WIP: polish README closes #158Great work! It's a good overview of the important things you'd want to know, both as a potential user and as a developer. I've added a few ideas here and there, but from my point of view this can be merged once you feel like it's ready.
@ -4,0 +27,4 @@* **Simple**: Focused on what clubs really need — members, dues, communication.* **Usable**: Clean, accessible UI, GDPR-compliant, designed with everyday volunteers in mind.* **Flexible**: Custom fields, role-based permissions, and self-service for members.I'm not sure if everyone reading this will know what "Custom fields" means. Maybe we could say something like
or
@ -4,0 +58,4 @@- Tested with: `asdf 0.16.5`- Required versions are documented in `.tool-versions` in this repo<details>Using the details element is a nice touch! We should be aware that it has some accessibility limitations. I think for the README it's fine though, since folks can easily read the source instead of the rendered variant :)
@ -19,0 +161,4 @@## 🏗️ Architecture- **Backend:** Elixir, Phoenix 1.8, LiveView 1.1, Ash FrameworkI think we could leave out the versions here, they don't add much relevant information and will become outdated quickly.
@ -19,0 +162,4 @@## 🏗️ Architecture- **Backend:** Elixir, Phoenix 1.8, LiveView 1.1, Ash Framework- **Frontend:** Phoenix LiveView + TailwindCSS + HeroiconsI'd say DaisyUI instead of tailwind here, it's what you'll typically interact with most as a developer :)
@ -19,0 +194,4 @@We welcome contributions!- Open issues and PRs in this repo.- Please follow existing code style and conventions.Idea for the future: We could add a
CONTRIBUTING.mdfile that documents the code style and conventions we follow.WIP: polish README closes #158to polish README closes #158