Tweet
Day 17 of #100DaysOfCode:

We fixed three bugs related to the UX. Getting closer every day…

#buildinpublic
Day 16 of #100DaysOfCode:

Today we continued to work on creating smooth transitions between iframes of different heights as we swipe between them on mobile.

#buildinpublic
Day 17 of #100DaysOfCode:

Today we continued to work on creating smooth transitions between iframes of different heights as we swipe between them on mobile.

#buildinpublic
Day 15 of #100DaysOfCode:

Today we decided to try loading the first two iframes in a slider section for better transitions between swiped iframes. It seems better, so we are going to keep this change and continue to trying to improve the UX.

#buildinpublic
Ugh. Did not work yesterday, as home, yard and church swallowed the day.

Today, day 14 of #100DaysOfCode:

Solved an issue in which the page did not load properly when being reloaded in the browser. Also explored various potential use cases for our product.

#buildinpublic
Day 13 of #100DaysOfCode:

Well, today we seemed to be on track to smooth out some kinks for when a user adds a section, then we ran into a fresh crop of issues. Documented them and called it a day. Off tomorrow for a sabbath rest, then back at it on Sunday.

#buildinpublic
Day 12 of #100DaysOfCode (late post):

On day 12 we eliminated a “flicker” that was happening when a user adds a new section. We also came up with a method to load custom CSS and apply it to a unique body class in each iframe.

#buildinpublic
Day 11 of #100DaysOfCode:

Today we fixed a few issues on the site and experimented with a preloader gif we’ve been using on the parent page and iframes. We took the preloader off the iframes and liked the faster action when swiping between iframes.

#buildinpublic
Day 10 of #100DaysOfCode (late post):

Our recent work allowing iframe heights to be passed along to parent divs caused an issue when the user would add a new section to the page. Today we fixed that issue and updated our project roadmap.

#buildinpublic
Day 9 of #100DaysOfCode:

Breakthrough! Today we figured out how to pass our resized iframe heights to parent divs, so all iframes now appear full-sized.

#buildinpublic
Day 8 of #100DaysOfCode (late post):

Began digging into the CSS in our iframes. I want to see how many auto-generated styles we never use and think about ways to be more efficient.

#buildinpublic
Day 7 of #100DaysOfCode:

We continued our work passing along the height of a resized iframe to the parent page. We were able to get this working on a local install, but not on our live project. More work to do. We also resolved a minor bug on our project.

#buildinpublic
Day 6 of #100DaysOfCode:

We’ve been using iframe-resizer (github.com/davidjbradshaw…) to fit scaled iframes to a device width. It allows us to set the height of the iframe. But we can’t always pass that height along to the parent div, so we worked on that today.

#buildinpublic
Day 5 of #100DaysOfCode:

Today we finished lazy losing iframes on scroll. Onward!

#buildinpublic
Day 4 of #100DaysOfCode:

Today we hit a roadblock on implementing lazy load on scroll, so we took a break from that.

Instead, we worked on extending the lazy load slider changes we made last week to sliders that the user can add to the page.

#buildinpublic
Welp. Didn’t work yesterday. Circumstances conspired to fill my day with other good things.

Today: Day 3 of #100DaysOfCode

Worked on loading various iframe sliders as they appear in the viewport. Almost there. Hope to finish tomorrow.

#buildinpublic
Day 2 of #100DaysOfCode

Finished the lazy loading of iframes in sliders—huge performance improvement!

Note: I'll be taking Saturdays off—we'll pick it up again Sunday. I still need to post details on this project but again ran out of time. Coming soon, I promise. #buildinpublic
Day 1 of #100DaysOfCode

Not day one of this project, but my first day tweeting. Today was spent trying to lazy load iframes in a slider to improve performance—we have several such sliders on the page.

More details on the nature of the project coming tomorrow. #buildinpublic
📌 Enough Twitter lurking! Starting here, I'm hoping to share my product-building story and engage with other builders.

My history:
▫️Writer➡️SEO➡️design➡️dev
▫️Gen X➡️married➡️8 kids(!)
▫️Freelancer➡️FT web dev

Can I side-hustle my way to an MVP? Let’s find out! #buildinpublic
📌 Enough Twitter lurking! Starting here, I'm hoping to share my product-building story and engage with other builders.

My path:
▫️Writer➡️SEO➡️design➡️dev
▫️Gen X➡️married➡️8 kids(!)
▫️Freelancer➡️FT web dev

Can I side-hustle my way to an MVP? Follow my journey! #buildinpublic