I'm DONE with Webflow 

For Pinegrow? forum.pinegrow.com

And that’s all I can ask for. Good luck!

Thank you. I try to be objective and enjoy all aspects of software so that I can give a balanced opinion on this stuff. I wish more would be less dogmatic about Webflow. It’s just one tool in the belt!

Depends what you mean by “secure”. Assuming it’s related to things like memberstack etc? It’s normally done by building a backend API and a login auth system. I’m not sure who you are but I’d say this would definitely be a dev job. There are ways to be more secure on the front end but this is not normally something a Webflow designer knows about to implement safely and correctly.

It’s definitely more interesting. I like mixing and making the most out of both worlds where I can

Is this a serious question? I make tutorials and videos to help and entertain my community. Unfortunately, I get paid zilch for it.

😂😂😂💣

I’m not really the right person to ask. I do believe there’s a limit on how many products you can have in a store. For this, contact Webflow sales. If that’s not enough, there are store alternatives that you can use with Webflow. The general consensus though is that Webflow e-commerce is immature and you’re better off going with Shopify.

@@webflowandcode Thanks Samuel, what do think about Elementor Cloud?

I’ve not looked into that either unfortunately

You’re not going to get rid of the JavaScript library that Webflow uses for interactions so you may well use it otherwise if you import GSAP into Webflow you’re loading 2 JavaScript animation libraries so I would just write vanilla JavaScript to add the ARIA roles. It’s worth checking that if you were to avoid Webflow interactions completely, they may be smart enough to not include their interactions library therefore importing GSAP wouldn’t be as big of a deal and then you could just use GSAP. Unfortunately Pinegrow has its own proprietary way to create its GSAP animation’s. You cannot export them although this is a great feature request and I wouldn’t be surprised if this could get integrated sooner rather than later.

Thanks (I think). No sponsor though and not the only reason I quit (see part 2).

Thanks Craig! Glad to have you on board. I just need to see 1 website you’re proud of and that demonstrates your best code. Then I would ask you questions on why you chose certain HTML elements, I’d look at some of your CSS and then walk through some JavaScript with you. This is judging pure technical ability. Obviously attitude and passion play a huge role as a junior because if you’re anything like me you’d fail miserably at the above questions. if you activity participate or engage in the “scene” is always 👌. Hope this helps.

Bore

He has one from 6 months ago. Go to his YT homepage

As @funkywaffle says I have a few live coding sessions where I go through basics in the interface. I agree there could be a more streamlined version so maybe I can start to build on this newfound interest in Pinegrow. A CMS I’ve used is Netlify CMS which uses Jekyll as a site builder. Not the nicest of solutions and I’m still trying to figure that out before I settle on a CMS route.

Are you referring to a separate designer coming into a Webflow project and “cleaning” up?

I'm not quite sure what your point is but maybe knowing that I too live by that standard will help. Thank you for checking out my video!

Just takes time. If there are bugs, you should report it! I personally like the UI. Webflow as a tool is very restricted hence why they can get away with a simpler UI.

I think If you intend on relying heavily on interactions that make content appear and disappear (sliders, dialogs, tab systems) anything interactive then you should look elsewhere. Webflow’s own interactive components are accessible so you could rely on them but if you’re building them bespoke, i’d avoid. There are platforms other than Pinegrow but I do like Pinegrow for my needs.

@@webflowandcode hi Samuel, out of curiosity, is the GSAP inegration in Pinegrow not good for heavy animations? It is still GSAP right?

How do you define “heavy animations”? Yes it’s 100% GSAP

@@webflowandcodewhat about teleporthq?

@@ertoorule what?

Old video. We’re now live!

@@webflowandcode would you replace the link in description with the new one?

Answered in the Discord!

@@webflowandcode got it, thanks 💪🏽

Exactly. This is my opinion. Take it or leave it

I can’t answer that for you

@@webflowandcode Of course you can't smh.

You asked the question. I don’t know what you expected

I re-watched this episode today for reasons so this is fresh on my mind. I disagree. All I'll say is accessibility has been the cornerstone of the web for the longest time and I think Webflow and its community do not have a grasp of how importance accessibility is. It's not odd for the 'rest' of the industry, only Webflow users.

@@webflowandcode Of course accessibility is important, but as he's still using Webflow I think I've made my point.

Pinegrow is capable of building you a native Wordpress theme. A lot more control too!

@@webflowandcode Yes, thanks, that is what I am thinking. That´s why I am looking for someone who can create a Webflow Site with Pinegrow in a WordPress theme.

That sucks. Use whatever gets the job done. When you say "Wordpress" do you mean Oxygen/Elementor?

Try Bricks

I’m the exact same, Wordpress is doing my head in.

​@@webflowandcodeI've been using Elementor

Sorry I don’t understand the question?

Not quite sure what you’re even saying here. Happy to take feedback but only when it’s articulated well.

Lucky you! No reason its should do that. It’s progressive but not THAT progressive. Probably something else.

@@webflowandcode Visited your site again using latest Firefox. Unresponsive, links don't work. Zilch!

Thanks for checking but what site are you looking at?

Great to see you again!

@@webflowandcode I keep finding rocks to live under ha ha!

And hopefully criticism like this will help push the platform forward 🤞. I would disagree that a platform that provides an interactions panel should do it properly. Why should I have to write extra code to make up for its shortcomings?

Infancy? It was launched in 2013.

I can say with 100% certainty I will not return to Webflow. I may move from Pinegrow though!

I don't think Samuel's video is an injunction to use Pinegrow, but an informed opinion that he shares. At the end of the day, if everyone can find what they want in the tool they choose, that's absolutely fine. As for the mocking mention "pinegrow website doesn't look like something made by designers", that's your subjective opinion. We don't know your experience nor have we ever seen your own designs. However, I would say that this remark is perfectly appropriate for 98% of the production of sites created with nocode/lowcode tools and for which the webmasters did not choose to use/customize third party templates sold by talented designers (I obviously include sites created with Webflow). The tool doesn't make the talent and no matter how perfect it is, if the designer is not inspired nor experienced in web development, the result will always be average or even bad.

Sometimes it's not worth explaining or even entering a discussion, Emmanuel. Clearly this person hasn't seen that I've made over a years worth of Webflow content and so have indeed experienced the 'power of Webflow' and the fact they're using design as an argument shows to me they don't understand why Webflow isn't a viable tool. I'd rather not bother with this one.

How so? Is accessibility not important to you?

@@webflowandcode it is important, but it might be your niche, hence you’re so eager to switch. That being said, accessibility in web affects like 5-7% of people? We cannot focus on every person, every disability, every case - it will cost a lot to businesses right now. That being said, Webflow does offer accessibility features, they are committed to it - sure, not everything is possible right now, but is it a problem? How many no-code tools offer such functionality in a simple to implement way? I know just Webflow. Does Pinegrow allow users to do it in a similar easy fashion? I’m not sure since it might require HTML/CSS/JS skills. My point is that if creating sites with accessibility is your niche, then, sure go for it - Webflow might not be your tool of choice. But for lots of people it is because it is clean, polished, and overall a great tool with amazing community. Not perfect for any cases and it is fine since you won’t use a hammer to cook soup. P.S: Can you backup your statement about “2 billion people with disabilities (that is related to the web)” by providing any source? Sounds like a huge and bold overstatement.

Georgy- this is such a toxic perspective to have. In the 20+ years I’ve been hand-building websites accessibility has been the cornerstone to the successful web experience you have today. Maybe not the JavaScript interactions in the scenario I’ve presented but in general it’s allowed the web to survive as long as it has. Remember, accessibility stretches far beyond interactions. It’s your document structure, UI, copywriting and much more. Accessibility is not 5%-7% of people, it’s everyone! But this idea and these practices just seemed to have escaped the Webflow community and it’s destroying the web. Any well established advocate who’s been building websites for a long time will tell you the importance of accessibility. I can see what you’re saying as my ‘niche’ but accessibility is not a niche. We can’t let this responsibility drop from building websites. Once you know patterns, they take only a short amount of time to implement and in my opinion is a fundamental to even calling yourself a web developer. As I said in my video, Pinegrow allows this. Pinegrow is NOT the tool I’m trying to get people to switch to, I just want to push Webflow as a platform forward and their community to learn how important accessibility is. It’s been a pleasure articulating this to you as you have taken the time to articulate your counter argument well. I appreciate that. Thanks. Source is in a pinned comment.

@@webflowandcode By niche I think he means that not every website needs to be "accessible". This also begs the question: Is the definition of accessible different for both of you? To me it sounds like Georgy is referring to blind people, people with other vision impairments, language barriers, etc. These are issues for example creative companies won't have to worry about too much as their clients are unlikely to be people that have those impairments. The points you raised regarding document structure, UI, etc aren't specific to webflow. That comes down to the designer/developer and how they do it. I'd love to hear both of your opinions in terms of what you consider "accessibility". Cuz maybe you both actually agree w each other, but its getting lost in mis-understanding of the word.

I don’t actually have any evidence to suggest that a significant percentage of my clients use screenreaders but I know that regardless of this, by thinking about accessibility establishes good web development practices ensures the longevity of my site. This video focuses on specifically blind/visually usage of an interactive website but my portfolio of RU-vid content describes accessibility as “building websites that are visually, SEO, disabled and any future technology-friendly”. (Websites that can be understood by everyone). I guess I’m trying to rephrase peoples perception that accessibility simply means “the other half of building a website, other than the visual design”, the bit that seems to be completely omitted from a typical Webflow designers development. They often think that they can just design and Webflow “takes care of the rest” but that’s just untrue. Hope this answers your question?

Who says we don’t already do this?

Please check the pinned comment, dude. Besides, what does it matter? Accessibility on the web is a non-issue to you?

@@webflowandcode Ok sorry but I am short-sighted and wear contacts, but that doesn't fit with accessibility features in Webflow. Being blind or having protanopia would be a problem though. One of which is already adressed by Webflow. It is an issue, but as it is something that concerns less than 5% of people, it can make sense that corporations spend less time on this subject than pure features or any other product related topic. It makes sense. Plus they are openly commited to work on these problems, they do get better, and have already been addressing many accessibility issues. They could've done more, but they could've done way less.

Dude. I found a tool that ALREADY ADDRESSES THESE NEEDS so I moved on. I don’t need to wait for Webflow.

@@webflowandcode yep, alright, it's fine chill out

Accessibility is blown WAY out of proportion of the web by people who stand to make a buck. There are just not enough blind people or people missing arms to justify the extra work and worry. Building a business is hard enough as it is not to worry about fringe things. And people with glasses aren't blind.

Mate this video is 6 months old. It’s dead already. Thanks for bring up something painful. Unsubscribed.

@@webflowandcode RIP :/