Skip to content
Permalink
Browse files

[WIP] QOR Article

  • Loading branch information...
Depado committed Feb 12, 2019
1 parent b637522 commit 538e026cfeafcb8b634d677c68cae148f63c6d6d
Showing with 21 additions and 10 deletions.
  1. +21 −10 pages/qor-admin-tips-and-tricks.md
@@ -11,7 +11,7 @@ tags: [go,dev,admin,qor]

# Introduction

## What is QOR and QOR Admin?
## What is QOR?

> QOR is a set of libraries written in Go that abstracts common features needed
> for business applications, CMSs, and E-commerce systems.
@@ -22,24 +22,33 @@ QOR is basically everything we need to run a full e-commerce website. But what
interests us here is the admin interface. Let's say we're creating an API
and store our data (stuff like your users, products, etc...) in a database. You
just don't need QOR to do that, you can use whatever router you're used to work
with for example. One thing to remember though is that QOR is using
[gorm](http://gorm.io/) to do most its processing, so if your project isn't
using it, it may be difficult to implement QOR Admin in your project.

QOR is a full framework, if you want to look at everything it can do, head to
the [getqor website](https://getqor.com/) and prepare to be amazed because it
can do so many awesome things:
with for example. But QOR is a full framework, if you want to look at everything
it can do, head to the [getqor website](https://getqor.com/) and prepare
yourself to be amazed because it can do so many things:

![qor features](/assets/qor-admin/qor-features.png)

But let's get back to our admin interface.
Although this article isn't sponsored by QOR or anything like that, I think it's
a great piece of technology and the people behind it are quite amazing. They
even have an [enterprise package](https://getqor.com/en/enterprise)!

## QOR Admin?

Frameworks like [Django](https://www.djangoproject.com/) give you an admin
interface to manage your data. This is great because it allows you to display
data in a web interface, modify them or execute one-shot actions on some
records. For example, it's rather easy to create a CSV export of one of your
tables in the form a single button that any admin can click on, thus avoiding
the usual SQL query to export data, if you know what I mean.

It also enables to modify data and more importantly **keep it consistent** by
writing your business rules as part of your admin interface. So we can prevent
someone from modifying one of our products and set the price to $0 (or 0€, or
whatever the currency, you get my point). Or prevent data loss. Or set specific
behavior for certain fields. The admin interface use case is then completely
different of a dashboard that does only "read" operations to generate insights
like [Metabase](https://www.metabase.com/) (which is an amazing tool too!).

So QOR Admin is a component of the QOR stack. And the great news is: You don't
need the whole QOR stack to make QOR Admin work! Plus, let's face it, QOR Admin
is really gorgeous with its material design theme (but that's subjective). The
@@ -51,7 +60,9 @@ following screenshot is from the [QOR Admin Demo](http://demo.getqor.com/admin):

Although QOR Admin is an amazing open-source lib and product, sometimes the
documentation lacks of a clear way to do things. This article's goal is to act
as a kind of enhanced documentation and tutorial.
as a kind of enhanced documentation and tutorial. We'll try to leverage the
annoying steps of setting up QOR following its best practices and create some
kind of package that could be reused quickly without having to overthink things.

# First Steps

0 comments on commit 538e026

Please sign in to comment.
You can’t perform that action at this time.