To start: in the Joomla context every Seblod field is a plugin. Like any other Joomla plugin, installed by the Extension Manager and managed later on with the Plugin Manager, where you set some general parameters and publish/unpublish it. They all live in the "plugin" directory right under you Joomla root.
One thing worth noting about plugins is that they a grouped logically according to what they do, so you'll see (in Plugin manager) Content-plugin_name or System-plugin_name, and in your file system you'll see this structure implemented as directories and subdirectories. The meaning of this categorization of plugins is the option (for developers) to trigger the execution of a whole group of plugins with one instruction in a certain place in their code. And this is what Joomla plugins are all about -
see this guide, it's a good starting point too.
For myself I prefer to think of plugins as little creatures in the Joomla jungle that hide in bushes and listen for something, for some sound, signal. And when they hear it they jump out and act. On the other side they are capable of producing sounds too that will be heard by the other plugins, which will act in their turn.
But with a slight modification to this abstraction, Joomla has a centralized pattern of "speaking out" that every plugin must follow in order to be able to listen and speak: it's another creature called The Dispatcher that is in charge of synchronizing it all. So instead of shouting out loud a plugin is supposed to tell the Dispatcher to spread the word for it. And instead of listening for every possible noise in the jungle every plugin is listening to the Dispatcher only. And when they hear the word they are programmed to listen for - they act. Acting might mean everything in the Joomla context. It might be intercepting and modifying the content that is right about to be displayed. It might be modifying whatever is just about to be saved. It might be calling some function from somewhere - no limit to what you can do. The genius part of this concept is that you can actually "inject" code (functionality) everywhere in Joomla, at every point in time and context. This is the concept of "events" an in Joomla they are usually self-explanatory: onBeforeContentSave, onDisplay, ... (see the above link for a list). These are Joomla "core" events but you can create your own for intercommunication among your own herd (group) of plugins. Your plugin just relays a word to the Dispatcher to say out loud and only the plugins which are programmed to listen for it will react, the others just won't pay any attention. So you can devise your own words (signals) too.
Seblod field plugins are no different.
So by design Seblod introduces the functionality of "fields" to Joomla as plugins. You have to write one, install it and publish it to have it available for use in Seblod. Say you need some specific field type - a field that will get the values of other fields in the same form and compose a string from them. This string you want stored in a specific database table field for later usage. So you write a plugin. Or you just get one and modify it (much easier).
It makes no sense to describe the structure of a Seblod field plugin, you just open an FTP session and explore the many pre-installed ones and get the convention at once.
To cut the story somewhat you could:
- open Plugin manager and chose the "Text" plugin
- open the Advanced panel and click "download" @ export
- you'll get the plugin packed : plg_cck_field_text.zip
- save locally, extract to a directory
- open each file in it to familiarize yourself
- replace all occurrences of "text" with your desired plugin name
- zip back and try installing it to Joomla
You should end up with a new field available in Seblod. Don't pay attention to things like PLG_CCK_FIELD_GROUP_FORM, they'll be fixed later. And now the fun part begins. Open for edit (via FTP or exTplorer or whatever) the xxx.php file in the root of the plugin and try adding an echo or something innocent to feel the plugin responding, to feel control

Then try modifying the value of the field. Or calling some other plugin. Absolutely necessary I find having the JDump tool at hand - waiting for you @ the JED.
And then - well, come back to share your discoveries or proudly announce the birth of a new Seblod field type and of course place it here for download under GNU GPL!
best regards,
Georgi