meichthys/church
1
0
Fork 0
mirror of https://github.com/meichthys/church.git synced 2026-02-04 08:05:39 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix links and clarify doctype naming convention

Browse Source 
Update doctype naming guidelines and roadmap link
This commit is contained in:
MeIchthys 2025-11-07 17:06:37 -05:00 committed by GitHub
parent 8bf5bde083
commit be4bbefb39
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -26,7 +26,7 @@ If you would like to test out the current state of the application, you can try
## ✨ Features
The following features have been implemented in this app (see the [🗺️ Roadmap](#🗺️-roadmap) below for future plans):
The following features have been implemented in this app (see the [🗺️ Roadmap](##🗺️-feature-roadmap) below for future plans):
- Built-in Documentation for each module
- Portal for users with a login:
@ -142,7 +142,7 @@ If you need help setting up the app or configuring it, you can reach out in our
Contributions are very welcome! If you plan any large contributions, please let me know first so we can coordinate and make the chances of a merged pull-request more likely.
- Doctype Naming: I've generally been using a single fieldname for the doctype names when the records in the doctype have low chance of clashing. If there is a higher chance of clashing, I've been using multiple fields in the name along with a `{##}` auto increment. The number of digits in the auto-increment are just sane values that should never be exceeded. I then specify the Title Field in the View Settings, and check the `Show Title in LInk Fields` option. This mostly hides the autonumber name from the user and lets the user only see the not-so-confusing name specified in the `Title Field` (sometimes I create a custom field to concatenate values - since the `Title Field` cannot take multiple fields at once afaik.)
- Doctype Naming: I've generally been using a single fieldname for the doctype names when the records in the doctype have low chance of clashing. If there is a higher chance of clashing, I've been using multiple fields in the name along with a `{#}` auto increment. The number of digits in the auto-increment are just sane values that should never be exceeded. I then specify the Title Field in the View Settings, and check the `Show Title in LInk Fields` option. This mostly hides the autonumber name from the user and lets the user only see the not-so-confusing name specified in the `Title Field` (sometimes I create a custom field to concatenate values - since the `Title Field` cannot take multiple fields at once afaik.)
## Steps for adding a new doctype:
- Make sure the doctype name is pre-pended with `Church `
@ -158,4 +158,4 @@ Contributions are very welcome! If you plan any large contributions, please let
>You can copy, translate, modify, and distribute this resource, without restriction, and without needing to ask permission. This resource is freely given (Matt 10:8) for the sake of the gospel.
![Freely given](church/public/media/freely_given.svg)
![Freely given](church/public/media/freely_given.svg)