You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b19b01f
Browse filesBrowse the repository at this point in the historyBrowse files
title: Learning Builder.io from a Developers Perspective
12
12
---
13
+
13
14
I sat down with Tim Benniks, who is a professional developer advocate, to introduce him to Builder.io. It was great to hear what questions a developer might have when being first introduced to the tool. I know Tim is well versed in all things Jamstack, so he wasn't coming into the conversation completely blind.
14
15
15
16
## Key Takeaways
@@ -90,16 +91,15 @@ Then when this data passes into the system it is in two different areas of Build
90
91
91
92
```jsx
92
93
<BuilderComponent
93
-
options={{ includeRefs: true }}
94
-
model={model}
95
-
content={modelData}
96
-
data={{
97
-
recentPosts,
98
-
modelData,
99
-
courseData,
100
-
}}
101
-
/>
102
-
94
+
options={{ includeRefs: true }}
95
+
model={model}
96
+
content={modelData}
97
+
data={{
98
+
recentPosts,
99
+
modelData,
100
+
courseData
101
+
}}
102
+
/>
103
103
```
104
104
105
105
Below is a breakdown that I made so that you can understand what all the props for the `BuilderComponent` actually do. As you can see data is meant to include dynamically changing state data, and content will be your pages data as Described by the Builder.ioJSON.
@@ -114,125 +114,133 @@ Below is an example of what that JSON looks like (again available directly withi
114
114
115
115
```json
116
116
{
117
-
"ownerId": "303fa35cceca49e6ab548071602c8ebd",
118
-
"lastUpdateBy": null,
119
-
"createdDate": 1649885165355,
120
-
"id": "df677f1d384f4c708cf2e64d41038d33",
121
-
"@version": 3,
122
-
"name": "Learning Builder.io from a Developers Perspective",
"title": "Learning Builder.io from a Developers Perspective",
139
-
"authors": [
140
-
{
141
-
"author": {
142
-
"@type": "@builder.io/core:Reference",
143
-
"id": "d4652e9fa73543dc8a422e20608fc7d2",
144
-
"model": "author" }
145
-
}
146
-
],
147
-
"frameworks": [],
148
-
"excerpt": "I sat down with Tim Benniks who is a developer advocate, for his first time ever checking out Builder.io. It was great to hear what questions a developer might have about creating pages with a Visual Editor.",
"title": "Learning Builder.io from a Developers Perspective",
141
+
"authors": [
142
+
{
143
+
"author": {
144
+
"@type": "@builder.io/core:Reference",
145
+
"id": "d4652e9fa73543dc8a422e20608fc7d2",
146
+
"model": "author"
147
+
}
148
+
}
149
+
],
150
+
"frameworks": [],
151
+
"excerpt": "I sat down with Tim Benniks who is a developer advocate, for his first time ever checking out Builder.io. It was great to hear what questions a developer might have about creating pages with a Visual Editor.",
The "blocks" item is where ever single item that is in our layers panel will be described as a unique block component. It is far too large to show everything. Below is an example of one of those blocks. In this case it is our custom Next.js component called NextImage.
I can't come close to teaching you everything about Builder.ioin a single post, but my team is building out documentation, courses, and videos to help developers be successful!
246
+
I can't come close to teaching you everything about Builder.ioin a single post, but my team is building out documentation, courses, and videos to help developers be successful!
0 commit comments