Alternatives to GitLab Pages logo

Alternatives to GitLab Pages

GitHub Pages, GitHub, GitLab, Netlify, and Confluence are the most popular alternatives and competitors to GitLab Pages.
241
288
+ 1
10

What is GitLab Pages and what are its top alternatives?

Host your static websites on GitLab.com for free, or on your own GitLab Enterprise Edition instance. Use any static website generator: Jekyll, Middleman, Hexo, Hugo, Pelican, and more
GitLab Pages is a tool in the Static Web Hosting category of a tech stack.

Top Alternatives to GitLab Pages

  • GitHub Pages
    GitHub Pages

    Public webpages hosted directly from your GitHub repository. Just edit, push, and your changes are live. ...

  • GitHub
    GitHub

    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together. ...

  • GitLab
    GitLab

    GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers. ...

  • Netlify
    Netlify

    Netlify is smart enough to process your site and make sure all assets gets optimized and served with perfect caching-headers from a cookie-less domain. We make sure your HTML is served straight from our CDN edge nodes without any round-trip to our backend servers and are the only ones to give you instant cache invalidation when you push a new deploy. Netlify is also the only static hosting service with integrated continuous deployment. ...

  • Confluence
    Confluence

    Capture the knowledge that's too often lost in email inboxes and shared network drives in Confluence instead – where it's easy to find, use, and update. ...

  • Gitbook
    Gitbook

    It is a modern documentation platform where teams can document everything from products, to APIs and internal knowledge-bases. It is a place to think and track ideas for you & your team. ...

  • Vercel
    Vercel

    A cloud platform for serverless deployment. It enables developers to host websites and web services that deploy instantly, scale automatically, and require no supervision, all with minimal configuration. ...

  • Webflow
    Webflow

    Webflow is a responsive design tool that lets you design, build, and publish websites in an intuitive interface. Clean code included! ...

GitLab Pages alternatives & related posts

GitHub Pages logo

GitHub Pages

15.9K
11.6K
1.1K
Public webpages freely hosted and easily published.
15.9K
11.6K
+ 1
1.1K
PROS OF GITHUB PAGES
  • 290
    Free
  • 217
    Right out of github
  • 185
    Quick to set up
  • 108
    Instant
  • 107
    Easy to learn
  • 58
    Great way of setting up your project's website
  • 47
    Widely used
  • 41
    Quick and easy
  • 37
    Great documentation
  • 4
    Super easy
  • 3
    Easy setup
  • 2
    Instant and fast Jekyll builds
  • 2
    Great customer support
  • 2
    Great integration
CONS OF GITHUB PAGES
  • 4
    Not possible to perform HTTP redirects
  • 3
    Supports only Jekyll
  • 3
    Limited Jekyll plugins
  • 1
    Jekyll is bloated

related GitHub Pages posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 5M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Dale Ross
Independent Contractor at Self Employed · | 22 upvotes · 1.2M views

I've heard that I have the ability to write well, at times. When it flows, it flows. I decided to start blogging in 2013 on Blogger. I started a company and joined BizPark with the Microsoft Azure allotment. I created a WordPress blog and did a migration at some point. A lot happened in the time after that migration but I stopped coding and changed cities during tumultuous times that taught me many lessons concerning mental health and productivity. I eventually graduated from BizSpark and outgrew the credit allotment. That killed the WordPress blog.

I blogged about writing again on the existing Blogger blog but it didn't feel right. I looked at a few options where I wouldn't have to worry about hosting cost indefinitely and Jekyll stood out with GitHub Pages. The Importer was fairly straightforward for the existing blog posts.

Todo * Set up redirects for all posts on blogger. The URI format is different so a complete redirect wouldn't work. Although, there may be something in Jekyll that could manage the redirects. I did notice the old URLs were stored in the front matter. I'm working on a command-line Ruby gem for the current plan. * I did find some of the lost WordPress posts on archive.org that I downloaded with the waybackmachinedownloader. I think I might write an importer for that. * I still have a few Disqus comment threads to map

See more
GitHub logo

GitHub

238.2K
203.8K
10.2K
Powerful collaboration, review, and code management for open source and private development projects
238.2K
203.8K
+ 1
10.2K
PROS OF GITHUB
  • 1.8K
    Open source friendly
  • 1.5K
    Easy source control
  • 1.2K
    Nice UI
  • 1.1K
    Great for team collaboration
  • 864
    Easy setup
  • 502
    Issue tracker
  • 484
    Great community
  • 480
    Remote team collaboration
  • 449
    Great way to share
  • 440
    Pull request and features planning
  • 144
    Just works
  • 131
    Integrated in many tools
  • 118
    Free Public Repos
  • 114
    Github Gists
  • 109
    Github pages
  • 82
    Easy to find repos
  • 61
    Open source
  • 59
    Easy to find projects
  • 59
    It's free
  • 56
    Network effect
  • 48
    Extensive API
  • 42
    Organizations
  • 41
    Branching
  • 33
    Developer Profiles
  • 32
    Git Powered Wikis
  • 29
    Great for collaboration
  • 23
    It's fun
  • 22
    Community SDK involvement
  • 22
    Clean interface and good integrations
  • 19
    Learn from others source code
  • 15
    Because: Git
  • 14
    It integrates directly with Azure
  • 9
    Standard in Open Source collab
  • 9
    Newsfeed
  • 8
    It integrates directly with Hipchat
  • 7
    Fast
  • 7
    Beautiful user experience
  • 6
    Cloud SCM
  • 6
    Easy to discover new code libraries
  • 5
    Smooth integration
  • 5
    It's awesome
  • 5
    Integrations
  • 5
    Graphs
  • 5
    Nice API
  • 4
    Quick Onboarding
  • 4
    Remarkable uptime
  • 4
    Hands down best online Git service available
  • 4
    CI Integration
  • 4
    Reliable
  • 3
    Loved by developers
  • 3
    Free HTML hosting
  • 3
    Security options
  • 3
    Simple but powerful
  • 3
    Uses GIT
  • 3
    Unlimited Public Repos at no cost
  • 3
    Version Control
  • 3
    Easy to use and collaborate with others
  • 2
    Nice to use
  • 2
    IAM
  • 2
    Ci
  • 1
    Easy and efficient maintainance of the projects
  • 1
    Good tools support
  • 1
    Beautiful
  • 1
    Free HTML hostings
  • 1
    Self Hosted
  • 1
    All in one development service
  • 1
    Easy to use
  • 1
    Easy source control and everything is backed up
  • 1
    Leads the copycats
  • 1
    Never dethroned
  • 1
    IAM integration
  • 1
    Issues tracker
  • 1
    Very Easy to Use
  • 1
    Easy deployment via SSH
  • 1
    Free private repos
  • 0
    Profound
CONS OF GITHUB
  • 51
    Owned by micrcosoft
  • 37
    Expensive for lone developers that want private repos
  • 15
    Relatively slow product/feature release cadence
  • 10
    API scoping could be better
  • 8
    Only 3 collaborators for private repos
  • 3
    Limited featureset for issue management
  • 2
    GitHub Packages does not support SNAPSHOT versions
  • 2
    Does not have a graph for showing history like git lens
  • 1
    Have to use a token for the package registry
  • 1
    No multilingual interface
  • 1
    Takes a long time to commit

related GitHub posts

Johnny Bell

I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 5M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
GitLab logo

GitLab

53K
44.8K
2.4K
Open source self-hosted Git management software
53K
44.8K
+ 1
2.4K
PROS OF GITLAB
  • 501
    Self hosted
  • 428
    Free
  • 336
    Has community edition
  • 241
    Easy setup
  • 239
    Familiar interface
  • 133
    Includes many features, including ci
  • 109
    Nice UI
  • 82
    Good integration with gitlabci
  • 55
    Simple setup
  • 33
    Has an official mobile app
  • 32
    Free private repository
  • 29
    Continuous Integration
  • 20
    Open source, great ui (like github)
  • 16
    Slack Integration
  • 12
    Full CI flow
  • 10
    Free and unlimited private git repos
  • 8
    User, group, and project access management is simple
  • 7
    Intuitive UI
  • 7
    Built-in CI
  • 7
    All in one (Git, CI, Agile..)
  • 4
    Both public and private Repositories
  • 3
    Integrated Docker Registry
  • 3
    CI
  • 3
    Full DevOps suite with Git
  • 3
    It's powerful source code management tool
  • 3
    Excellent
  • 3
    Build/pipeline definition alongside code
  • 3
    Mattermost Chat client
  • 3
    Issue system
  • 3
    So easy to use
  • 2
    Because is the best remote host for git repositories
  • 2
    Dockerized
  • 2
    Free private repos
  • 2
    Great for team collaboration
  • 2
    Unlimited free repos & collaborators
  • 2
    It's fully integrated
  • 2
    I like the its runners and executors feature
  • 2
    One-click install through DigitalOcean
  • 2
    Security and Stable
  • 2
    Low maintenance cost due omnibus-deployment
  • 2
    On-premises
  • 1
    Kubernetes integration with GitLab CI
  • 1
    Multilingual interface
  • 1
    Review Apps feature
  • 1
    Powerful software planning and maintaining tools
  • 1
    Groups of groups
  • 1
    Built-in Docker Registry
  • 1
    Beautiful
  • 1
    Wounderful
  • 1
    Opensource
  • 1
    Not Microsoft Owned
  • 1
    Many private repo
  • 1
    Published IP list for whitelisting (gl-infra#434)
  • 1
    The dashboard with deployed environments
  • 1
    Powerful Continuous Integration System
  • 1
    Kubernetes Integration
  • 1
    Native CI
  • 1
    HipChat intergration
  • 1
    It includes everything I need, all packaged with docker
  • 0
    Supports Radius/Ldap & Browser Code Edits
CONS OF GITLAB
  • 27
    Slow ui performance
  • 7
    Introduce breaking bugs every release
  • 5
    Insecure (no published IP list for whitelisting)
  • 1
    Built-in Docker Registry
  • 0
    Review Apps feature

related GitLab posts

Tim Abbott
Shared insights
on
GitHubGitHubGitLabGitLab
at

I have mixed feelings on GitHub as a product and our use of it for the Zulip open source project. On the one hand, I do feel that being on GitHub helps people discover Zulip, because we have enough stars (etc.) that we rank highly among projects on the platform. and there is a definite benefit for lowering barriers to contribution (which is important to us) that GitHub has such a dominant position in terms of what everyone has accounts with.

But even ignoring how one might feel about their new corporate owner (MicroSoft), in a lot of ways GitHub is a bad product for open source projects. Years after the "Dear GitHub" letter, there are still basic gaps in its issue tracker:

  • You can't give someone permission to label/categorize issues without full write access to a project (including ability to merge things to master, post releases, etc.).
  • You can't let anyone with a GitHub account self-assign issues to themselves.
  • Many more similar issues.

It's embarrassing, because I've talked to GitHub product managers at various open source events about these things for 3 years, and they always agree the thing is important, but then nothing ever improves in the Issues product. Maybe the new management at MicroSoft will fix their product management situation, but if not, I imagine we'll eventually do the migration to GitLab.

We have a custom bot project, http://github.com/zulip/zulipbot, to deal with some of these issues where possible, and every other large project we talk to does the same thing, more or less.

See more
Joshua Dean Küpper
CEO at Scrayos UG (haftungsbeschränkt) · | 20 upvotes · 444.1K views

We use GitLab CI because of the great native integration as a part of the GitLab framework and the linting-capabilities it offers. The visualization of complex pipelines and the embedding within the project overview made Gitlab CI even more convenient. We use it for all projects, all deployments and as a part of GitLab Pages.

While we initially used the Shell-executor, we quickly switched to the Docker-executor and use it exclusively now.

We formerly used Jenkins but preferred to handle everything within GitLab . Aside from the unification of our infrastructure another motivation was the "configuration-in-file"-approach, that Gitlab CI offered, while Jenkins support of this concept was very limited and users had to resort to using the webinterface. Since the file is included within the repository, it is also version controlled, which was a huge plus for us.

See more
Netlify logo

Netlify

2.7K
1.9K
204
Build, deploy and host your static site or app with a drag and drop interface and automatic delpoys...
2.7K
1.9K
+ 1
204
PROS OF NETLIFY
  • 44
    Easy deploy
  • 43
    Fastest static hosting and continuous deployments
  • 22
    Free SSL support
  • 22
    Super simple deploys
  • 15
    Easy Setup and Continous deployments
  • 10
    Free plan for personal websites
  • 10
    Faster than any other option in the market
  • 8
    Deploy previews
  • 6
    Free Open Source (Pro) plan
  • 4
    Great loop-in material on a blog
  • 4
    Analytics
  • 4
    Easy to use and great support
  • 3
    Great drag and drop functionality
  • 3
    Custom domains support
  • 3
    Fastest static hosting and continuous deployments
  • 1
    Tech oriented support
  • 1
    Supports static site generators
  • 1
    Canary Releases (Split Tests)
CONS OF NETLIFY
  • 7
    It's expensive
  • 1
    Bandwidth limitation

related Netlify posts

Johnny Bell

I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

See more
Stephen Gheysens
Lead Solutions Engineer at Inscribe · | 14 upvotes · 977.3K views

Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

See more
Confluence logo

Confluence

22.9K
16.5K
200
One place to share, find, and collaborate on information
22.9K
16.5K
+ 1
200
PROS OF CONFLUENCE
  • 93
    Wiki search power
  • 62
    WYSIWYG editor
  • 42
    Full featured, works well with embedded docs
  • 3
    Expensive licenses
CONS OF CONFLUENCE
  • 3
    Expensive license

related Confluence posts

David Ritsema
Frontend Architect at Herman Miller · | 11 upvotes · 648.6K views

We knew how we wanted to build our Design System, now it was time to choose the tools to get us there. The essence of Scrum is a small team of people. The team is highly flexible and adaptive. Perfect, so we'll work in 2 week sprints where each sprint can be a mix of new R&D stories, a presentation of decisions made, and showcasing key development milestones.

We are also able to run content stories in parallel, focusing development efforts around key areas of the site that our authors need first. Our stories would exist in a Jira backlog, documentation would be hosted in Confluence , and GitHub would host our codebase. If developers identify technical improvements during the sprint, they can be added as GitHub issues and transferred to Jira if we decide to represent them as stories for the Backlog. For Sprint Retrospectives, @groupmap proved to be a great way to include our remote members of the dev team.

This worked well for our team and allowed us to be flexible in what we wanted to build and how we wanted to build it. As we further defined our Backlog and estimated each story, we could accurately measure the team's capacity (velocity) and confidently estimate a launch date.

See more
Priit Kaasik
Engineering Lead at Katana MRP · | 9 upvotes · 497.7K views

As a new company we could early adopt and bet on #RemoteTeam setup without cultural baggage derailing us. Our building blocks for developing remote working culture are:

  • Hiring people who are self sufficient, self-disciplined and excel at video and written communication to work remotely
  • Set up periodic ceremonies ( #DailyStandup, #Grooming, Release calls and chats etc) to keep the company rhythm / heartbeat going across remote cells
  • Regularly train your leaders to take into account remote working aspects of organizing f2f calls, events, meetups, parties etc. when communicating and organizing workflows
  • And last, but not least - select the right tools to support effective communication and collaboration:
  1. All feeds and conversations come together in Slack
  2. #Agile workflows in Jira
  3. InProductCommunication and #CustomerSupportChat in Intercom
  4. #Notes, #Documentation and #Requirements in Confluence
  5. #SourceCode and ContinuousDelivery in Bitbucket
  6. Persistent video streams between locations, demos, meetings run on appear.in
  7. #Logging and Alerts in Papertrail
See more
Gitbook logo

Gitbook

187
312
6
Document Everything! For you, your users and your team
187
312
+ 1
6
PROS OF GITBOOK
  • 4
    Prueba
  • 2
    Integrated high-quality editor
CONS OF GITBOOK
  • 1
    No longer Git or Open
  • 1
    Just sync with GitHub

related Gitbook posts

Vercel logo

Vercel

851
671
76
It makes serverless application deployment easy
851
671
+ 1
76
PROS OF VERCEL
  • 18
    Simple deployment
  • 15
    Free tier
  • 13
    Free SSL
  • 10
    Simple setup
  • 8
    Easy custom domain setup
  • 4
    Build and deploy via git push
  • 4
    One tap build
  • 3
    SSR
  • 1
    SSG
CONS OF VERCEL
  • 1
    Pricing Unclear

related Vercel posts

Stephen Gheysens
Lead Solutions Engineer at Inscribe · | 14 upvotes · 977.3K views

Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

See more
Jesus Dario Rivera Rubio
Telecomm Engineering at Netbeast · | 13 upvotes · 269.7K views

This time I want to share something different. For those that have read my stack decisions, it's normal to expect some advice on infrastructure or React Native. Lately my mind has been focusing more on product as a experience than what's it made of (anatomy). As a tech leader, I have to worry about things like: are we taking enough time for reviews? Are we improving over time? Are we faster now? Is our code of higher quality?

For all these questions you can add many great recommendations on your pipeline. We use Trello for bug-tracking and project management. We use https://danger.systems/js/ to add checks for linting, type-enforcing and other quality dimensions in our PRs and a great feature from Vercel that let's you previsualize deployments directly in a PR. However it's not easy to measure this improvements over time. For customer matters we have Amplitude or Firebase analytics, but for our internal process? That's a little bit more complicated.

I collaborated recently with some folks in a small startup as an early adopter to create a metrics dashboard for engineers. I tried to add the tool to stackshare.io but still it doesn't appear as one of the options, please take a look on it over product hunt and let us know https://www.producthunt.com/posts/scope-6

See more
Webflow logo

Webflow

660
701
52
Build responsive websites visually
660
701
+ 1
52
PROS OF WEBFLOW
  • 13
    Interactions and Animations
  • 7
    Builds clean code in the background
  • 7
    Fast development of html and css layouts/design
  • 6
    Free plan
  • 6
    Fully Customizable
  • 5
    Simple
  • 4
    Prototype
  • 2
    Built on web standards
  • 2
    Next Gen
CONS OF WEBFLOW
  • 1
    Freemium
  • 1
    No Audio Support

related Webflow posts

I would like to build a community-based customer review platform for a niche industry where users can sign up for a forum, as well as post detailed reviews of their experience with a company/product, including a rating system for pre-selected features. Something like niche.com or areavibes.com with curated information/data, ratings, reviews, and comparison functionalities.

Is this possible to build using no-code tools? I have read about the possibility of using Webflow with Memberstack, Airtable, and Elfsight through Zapier / Integromat, which may allow for good design and functionality. Is it possible with Bubble or Bildr?

I have no problems with a bit of a learning curve as long as what I want is possible. Since I have 0 coding experience, I am not sure how to go about it.

Any advice would be greatly appreciated!

See more
Khalid Joharji
Business Developer at Joharji MVPs · | 6 upvotes · 208.9K views
Shared insights
on
WordPressWordPressWebflowWebflowBubbleBubble

So I've been working as a freelancer building websites using Wordpress, limiting myself to available templates and customizing it (drag and drop no code involvement) and blending between plugins to get the requirements as much as possible. and I have spent my day job doing everything related to web portals (business case, business plans, marketing, back-office operations, project management, product management) but never got my hands into code yet. I heard of zero-code solutions such as Bubble and Webflow and I would like to be able to develop an MVP (Minimal Viable Product) to launch those ideas quickly to make sure that I make some sales before we invest into building a state of the art app.

Those MVPs are a struggle since most of it has its own unique processes therefore WordPress doesn't come in handy most of the time. This is where Bubble and Webflow come to the fore. Before I start my journey to learn one of these tools, where I imagine I will spend weeks to months learning, I need to know which road I should take while I am standing at the crossroads.

Objective: 1- Build MVPs with unique workflows to secure sales and transactions to confirm the product is viable

Requirements: 1- No coding knowledge required 2- Drag and drop workflows 3- Can use RTL (right to left) and build websites in Arabic 4- Cost-effective 5- High-quality online courses (free/paid) are available

Your advice is much appreciated.

See more