<commit_before># !-- in development, not suitable for anything yet -- !

# BpCustomFields

1. Add Choices and Gallery
- update flatpickr to latest release
2. editor - toolbar
3. Add Template more complex/Hierarchy fields 
4. audio (how are you handling this? - soundmanger?)
5. errors and notifications
6. How to handle default style... default theme, perhaps.

There are a number of reasons why I've wanted to use some sort of custom fields in Rails applications:

1. Often my clients want to display content that isn't really tied to any resource.  For instance, a portfolio site:  Where do we stick a field for displaying contact information?  Or an about me paragraph?  Some like to create a Page model, but then you have different attributes for each page: one page requires several images, while another another might need several small snippets of text.  There are other solutions, but my Wordpress development experience wants to reach for custom fields.
2. Settings/Options/Preferences pages.  It's a big question in Rails apps.  Some end up creating a Setting singletonish model or define settings in a .yml file.  I've always found these methods less than fitting solutions.  
3. Content that only gets displayed on certin instances of resources.  Let's say you only want to display a certain field on Post id 10.  Or a post with the slug "breakfast."  You could write some conditional logic in the view, but then you've got a field in your model that's only used for one instance. 
4. Gives a little more control to web admins who aren't rails developers.

### 
- hierarchy of fields for repeaters and nested (ancestry)
- locations.
- jSON?
- for settings, pages, options, preferences maybe a different gem with custom pages is the way to go
- there's also the option of allowing a route/location based custom field in addition as a quick way to create settings pages...

##### Fields to add
(basically just look at acf pro)
- Choices:
 - Checkbox
 - Select
 - True / False

- Gallery
- Color Select
- Map?
- Better date/datetime selects
- oEmbed (replace video?)

Layout:
 - Flexible Content
 - Repeater
 - Tab

Relational:
  Page Link/Route
  Resource or instance
  Relationship
  Tags
<commit_msg>bump readme<commit_after># !-- in development, not suitable for anything yet -- !


# BpCustomFields

1. Gallery
- update flatpickr to latest release
2. editor - toolbar
3. Add Template more complex/Hierarchy fields 
4. audio (how are you handling this? - soundmanger?)
5. errors and notifications
6. How to handle default style... default theme, perhaps.

There are a number of reasons why I've wanted to use some sort of custom fields in Rails applications:

1. Often my clients want to display content that isn't really tied to any resource.  For instance, a portfolio site:  Where do we stick a field for displaying contact information?  Or an about me paragraph?  Some like to create a Page model, but then you have different attributes for each page: one page requires several images, while another another might need several small snippets of text.  There are other solutions, but my Wordpress development experience wants to reach for custom fields.
2. Settings/Options/Preferences pages.  It's a big question in Rails apps.  Some end up creating a Setting singletonish model or define settings in a .yml file.  I've always found these methods less than fitting solutions.  
3. Content that only gets displayed on certin instances of resources.  Let's say you only want to display a certain field on Post id 10.  Or a post with the slug "breakfast."  You could write some conditional logic in the view, but then you've got a field in your model that's only used for one instance. 
4. Gives a little more control to web admins who aren't rails developers.

### 
- hierarchy of fields for repeaters and nested (ancestry)
- locations.
- jSON?
- for settings, pages, options, preferences maybe a different gem with custom pages is the way to go
- there's also the option of allowing a route/location based custom field in addition as a quick way to create settings pages...

##### Fields to add

GALLERY

Field Template = Gallery
Parent Field - acts as anchor - value is either the name of the gallery or blank
children fields - each image in the gallery, field_template is automatically set to image


REPEATER

Field Template - Repeater
Parent Field - groups fields together and acts as anchor - value is probably blank
Children Fields - Each field_template can be changed.  


TABS
Parent Field - Acts as anchor
1st Children - First set of children are the layout for each tab
2nd Children - these are the fields within each.


FLEX CONTENT - Later!  Will have to think about this after you implement everything else.


- Gallery
- Color Select
- Map?
- Better date/datetime selects
- oEmbed (replace video?)

Layout:
 - Flexible Content
 - Repeater
 - Tab

Relational:
  Page Link/Route
  Resource or instance
  Relationship
  Tags

{'fraction_non_alphanumeric': 0.049878836833602586, 'fraction_numerical': 0.005250403877221325, 'mean_word_length': 3.7579250720461097, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3123054', 'n_tokens_mistral': 1288, 'n_tokens_neox': 1218, 'n_words': 757}