One of the best decisions I made during a very turbulent 2020 was to leave conventional coding behind and embrace the #nocode movement. @bubble made this a reality. Although my own journey thus far is premature, I’ve learned a lot so here’s a power thread on....

‘How I created @buildcamp sales funnel landing page in under 2hours’.

Preview here 👇

https://t.co/s9P5JodSHe

Power thread here 👇
1. Started with a vanilla bubble app ensuring that all styles and UI elements were removed. Created a new page called funnel and set the page size to 960px as this allows the page to render proportionately on both web and mobile when hitting responsive breakpoints.
2. Began dropping elements onto the page to ‘find the style’. These had to be closely aligned to our @buildcamp branding so included text, buttons and groups - nothing too heavy. Played around with a few fonts, colors and gradients and thus pinned down the following style guide.
3. Started to map out sections using groups as my ‘containers’ to hold the relevant information and imagery needed to pad out the sales pitch. At this point, they were merely blocks of color #ff6600 with reduced opacity set to 5% to ease page flair.
4. Working from top down, I created the page structure using the containers as placeholders and part-filled each with some dummy lipsum content. By using lipsum enables you to not get bogged down with sniffy content creation. A designer's thorn!
5. Fired up Photoshop and started to create some complimentary images to be used in some of the placeholders. Using the colors I defined in the style guide, I was able to create the following custom imagery to retain page uniform/consistency.
6. At this point I had a firm understanding on how I envisaged the final page to render so my wingman @_gregoryjohn crafted out the content which allowed me to scale and set the correct placeholder heights.
7. Instead of having large open white-space in between sections, I opted to set an image as the groups background to draw attention to certain CTAs and aid page flow. With the parent page itself having its own isometric master-background image.
8. I then created a transparent floating header with a conditional to set the background color to #FFFFFF when the current page scrolling is/or above 160. Created 4 anchor text elements which onclick scroll to X_container further down the page.
9. Added some further minor UI/UX enhancements. These inc the guide cover shadow by applying an outset shadow style to 20/20/20/0 with #000000 20% opacity.
10. A pro-active call-out floating group which is hidden on page load. When current page scrolling is/or above 160 > animate (NoBounceLeftIn) floating group > with the reverse being done to hide when current page scrolling is/or below 160.
A simple tweet could never portray how much gratitude I have for @estraschnov and @jphaas1 in pursuing their vision into such a powerful and scalable product. @bubble thank you, I applaud you.

More from Tech

After getting good feedback on yesterday's thread on #routemobile I think it is logical to do a bit in-depth technical study. Place #twilio at center, keep #routemobile & #tanla at the periphery & see who is each placed.


This thread is inspired by one of the articles I read on the-ken about #postman API & how they are transforming & expediting software product delivery & consumption, leading to enhanced developer productivity.

We all know that #Twilio offers host of APIs that can be readily used for faster integration by anyone who wants to have communication capabilities. Before we move ahead, let's get a few things cleared out.

Can anyone build the programming capability to process payments or communication capabilities? Yes, but will they, the answer is NO. Companies prefer to consume APIs offered by likes of #Stripe #twilio #Shopify #razorpay etc.

This offers two benefits - faster time to market, of course that means no need to re-invent the wheel + not worrying of compliance around payment process or communication regulations. This makes entire ecosystem extremely agile

You May Also Like

This is a pretty valiant attempt to defend the "Feminist Glaciology" article, which says conventional wisdom is wrong, and this is a solid piece of scholarship. I'll beg to differ, because I think Jeffery, here, is confusing scholarship with "saying things that seem right".


The article is, at heart, deeply weird, even essentialist. Here, for example, is the claim that proposing climate engineering is a "man" thing. Also a "man" thing: attempting to get distance from a topic, approaching it in a disinterested fashion.


Also a "man" thing—physical courage. (I guess, not quite: physical courage "co-constitutes" masculinist glaciology along with nationalism and colonialism.)


There's criticism of a New York Times article that talks about glaciology adventures, which makes a similar point.


At the heart of this chunk is the claim that glaciology excludes women because of a narrative of scientific objectivity and physical adventure. This is a strong claim! It's not enough to say, hey, sure, sounds good. Is it true?