Publish fast, secure & easy to manage websites built from your Google Docs. You can use Nocode for your Blog, Product Documentation, Portfolio or Company Intranet. Basically, you can publish anything.
Replies
Best
I've been enjoying this for the past month and have to say it is spot on when it comes to getting something online quick. my only qualm was they didnt have sure a blogger friendly layout in the beginning but have since updated and there is a bit more flexibility especially for the simple stuff i am looking to do
@demetrios_brinkmann We will be spending the rest of the year focusing on making the selection of templates better and letting users tell us which ones they would like!
Report
Really love the nocode movement. Thanks for making this and appreciate the emphasis on making it super easy to set up static pages!
@jonathan_lee_kch Thanks Jonathan! Yes, although I picked the name Nocode 2 years ago when the nocode movement didn't really exist! I was in two minds as to whether we might need to change it to avoid confusion, but I think we have let people build sites without knowing any code whatsoever. So I do think we fit in the movement too :)
Very interesting. I have a typeform i want a user to fill in and then display the answers he/she provides on a webpage. I wonder if this can do this for me?
@adam_knight so you can add a picture of what the user submits in a form? Not sure i follow, will check out your website - this is a feature ive been struggling to find, so am super keen to learn
@rawoyemi Hi Richard. Thanks! It was harder than we initially though tbh! We're at v1 and we will make the system better as we can see more people using it. Fingers crossed people like it.
@priya_samuel1 thank you. We have tried to take that hassle completely out of it. We host the sites in high-spec Google Cloud servers. They are static sites so also load really quickly.
@olia_buliga lovely of you to say so Olia, thank you!
Report
Really nice concept, especially for multi-user editing
I am concerned about a few things
1. Image optimization - even your own home page has images almost 1MB in size which significantly slows down page loading speed (though your pages overall are very fast) - you need to have image optimization
2. Bandwidth - with only 1GB on the middle plan your users are going to exceed that very fast just from their own test browsing. Add to that bots coming crawling - I used to budget 15GB just for bot traffic on a relatively small blog (500 pages/posts - optimized), and that was 10 years ago.
You need to have a much better solution because even the top plan, 10 GB is going to be eaten up very fast, and you don't have any details of bandwidth costs after that.
3. You are using Cloudflare for your main site. Is that something your users can use as well? That might offset some of the bandwidth costs
4. SEO/Social/Accessibility - no descriptions, no social meta, no alt tags for images (on your own site), no schema
There may also be issues with unique titles because many of your own pages don't have unique title tags. I am assuming that was just being lazy.
If a site was ever ranking a nasty blackhat is going to have a field day creating duplicate content without any canonical set or parameter validation.
The first link from the home page of a blog to a post is an image without an alt attribute. No No No.
5. Dogfooding - you have a screenshot of a blog example at Astonish email, which is your other product. That blog is running on Squarespace.
If you can't use it there for technical reasons I understand but give potential users real example sites to look at using your platform.
To be fair to you I haven't pointed any tools at the sites beyond a quick code inspection by eyeball mk1 and 1 Lighthouse report.
I understand it is a MVP but for me it isn't a "Minimum Loveable Product"
Any product with major bandwidth costs is just a huge no.
To me it seems you should maybe be publishing using a customer's own netlify account so you can forget about bandwidth costs and charge based on features.
@andybeard Thanks for the feedback!
Some reponses to your excellent points:
1. image optimzation
You are correct about this - we will run through images and apply size optimzations so they are smaller. This also applies to images uploaded by users - we do not currently do any processing on those images so a 2MB image will be served as is. This is something we have on our roadmap however.
2. Bandwidth
Yes this is an excellent point - and I totally agree that a paying customer shouldn't have to worry about bandwidth limits. We put those limits on to prevent bots eating all of our bandwidth for free sites. I totally agree that the limits for paid sites are very stingy however and the cost of a pro or ultimate plan would easily cover a 10x (or more) increase in the bandwidth quota and so we will look at this right away.
3. Interesting - yes would be possible to route published sites via cloudflare and this would (like you say) help with bandwidth and all of the other security related features that cloudflare offers! (great point thank you)
4. SEO/Social/Accessibility - you are entirely correct about these points. We have an issue on our roadmap for all the things you have said. I will now put this at the top of the list for things we focus on next so thank you for pointing that out :-)
5. Dogfooding - the Astonish documentation is using nocode but the Astonish blog currently does not - I can see the confusion because we have a blog template. Our own documentation (https://guide.nocode.works/) and blog (https://blog.nocode.works/) *are* running on nocode however so there is some degree of dogfooding going on :-) (and it was really easy to put together the nocode docs using nocode)
> To me it seems you should maybe be publishing using a customer's own netlify account so you can forget about bandwidth costs and charge based on features.
^^ that is an *excellent* point - using nocode as the builder and another hosting provider for the hosting. A nocode site is very much just a folder of static files (no server other than basic HTTP server required) so it would be very possible for us to integrate with existing hosting providers (like netlify) - thank you for this it is really good feedback!
Report
Looks fabulous...think you forgot AUD currency pricing ;)
Replies
Helix.ml
Helix.ml
Mirro
Helix.ml
VYVE
Helix.ml
VYVE
Nack AI
Helix.ml
Helix.ml
Helix.ml
Helix.ml
Helix.ml