Tweet
Day 43 of #100DaysOfCode (late post):

Yesterday we realized our efforts to show different device-sized views were running into some serious challenges and even breaking some of our old code, so we rolled everything back to a previous version then rested today.

#buildinpublic
Day 42 of #100DaysOfCode:

Today we continued work on a toggle for different device previews of our builder tool.

#buildinpublic
Day 41 of #100DaysOfCode:

We have a toggle between mobile, tablet and desktop views and are attempting to make all three views available on any device (like you could even see a mini desktop view on mobile). We worked on this today, but we’re not quite there yet.

#buildinpublic
Day 40 of #100DaysOfCode:

Finally back in the groove after a few days in San Diego for #WCUS, today we fixed a bug where the user could not edit user-added sections in our builder tool.

#buildinpublic
Day 39 of #100DaysOfCode:

I was able to add the missing resources to an optimized iframe. I need to test this at scale. I will try to do this over the next few days, but will be traveling and may not have time.

#buildinpublic
Day 38 of #100DaysOfCode:

After dequeuing styles yesterday, I was able to programmatically add the stylesheet I created on Sunday. But the final result is a bit off—my method of dequeuing styles is stripping other resources too. I hope to resolve this tomorrow.

#buildinpublic
Day 37 of #100DaysOfCode:

Today I worked out how to dequeue all styles from our iframes so we can simply use our minimalcss styles and ensure quick load times.

#buildinpublic
Day 36 of #100DaysOfCode:

Today I finally figured out how to muddle my way through node js and run minimalcss. It cut a ton of CSS from the page. Tested the result, and it looks great. Thanks @peterbe for creating such a cool resource!

#buildinpublic
Day 35 of #100DaysOfCode:

Played around with using jest to run JavaScript tests from the command line today.

#buildinpublic
Day 34 of #100DaysOfCode:

Today we completed the design of our mobile-friendly website builder tool. I’m going to upload some new iframes and record a demo this weekend. Lotta work left to get this off the ground, but super pumped about everything we’ve done!

#buildinpublic
Day 33 of #100DaysOfCode:

Today we found that some of our iframe resizing code that wasn’t fully working was duplicative of a new cleaner method we had recently implemented elsewhere. So we scrapped the buggy method and expanded the clean code to our entire tool.

#buildinpublic
Day 32 of #100DaysOfCode:

Today we took some of the performance improvements from Day 28 and extended them to user-added sections within our tool.

#buildinpublic
Day 31 of #100DaysOfCode:

Decided to try MinimalCSS instead of unCSS to streamline styles on our iframes: github.com/peterbe/minima…

#buildinpublic
Day 30 of #100DaysOfCode:

Started using unCSS to remove unnecessary CSS from iframes to further streamline our tool.

#buildinpublic
Day 29 of #100DaysOfCode, late version (yesterday):

We worked on making all hard-coded parts of our tool dynamic so the page could be customized by the user.

Now, on Saturday, we rest.

#buildinpublic
Day 29 of #100DaysOfCode, late version (yesterday):

We worked on making all hard-coded parts of our tool dynamic so the page could be customized by the user.

#buildinpublic
Day 28 of #100DaysOfCode:

Locked in some huge performance gains today. The tool we have built is looking great.

#buildinpublic
Day 27 of #100DaysOfCode (a little late):

Today we struggled to execute some improvements to reach a final performance goal on our page. This will take time and focus to reach. We will try again tomorrow.

#buildinpublic
Day 26 of #100DaysOfCode:

We made further performance enhancements to the tool we’re building. Hoping to have a demo to share later this week.

#buildinpublic
Rested on Saturday. Sunday was swallowed up by yard work and minor emergencies (like busting and fixing a water pipe in the ground).

Today, day 25 of #100DaysOfCode:

We took Thursday’s improvements and applied them to lazy loaded sections and user-added sections. #buildinpublic