Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Admin Functions #4

Open
thequbit opened this issue Jul 7, 2015 · 6 comments
Open

Admin Functions #4

thequbit opened this issue Jul 7, 2015 · 6 comments
Labels

Comments

@thequbit
Copy link
Contributor

thequbit commented Jul 7, 2015

So I had the thought that maybe the Admin functionality of the site should actually be built into each page. So that when someone is viewing the page as an Admin, they have little (+) next to things, where they can just add a new item. I've done this before on a few sites with high success in usability, although the target audience was more technical then I think our Admin's may be ...

The thought would be that if you wanted to add something to the site ( and really everything on the site is a list: people, recordings, stations, etc. ) you would just click a "add" button. And that would then just create a new field right there on the site.

I know this won't work with all things ... but it could be adapted pretty universally I think ( or modals could be used to supplement as needed ). As @GabeIsman said, this site is kinda big, and we haven't even touched on the "how do we get data into it" part yet. We can pre-fill things all day from scripts, but eventually we'll need to push that "burden" onto the stations and users.

@melodykramer
Copy link
Member

Deleted it after seeing the other thread!

@melodykramer
Copy link
Member

I think this is a good idea!

@GabeIsman
Copy link

I like this idea. I think we'll need to be careful designing it so that it doesn't turn into an unholy mess on the code side, but I think it's a usability win. If we do it right, the code ought to be fairly general too.

@thequbit
Copy link
Contributor Author

thequbit commented Jul 8, 2015

I think we can spend some time to, like you said Gabe, 'do it right' and make it pretty clean. Any time there is a list, we can just define the items that go into that list and then make those things into inputs. Something like:

var list_item = [
    {
        name: 'name',
        type: 'input/text',
    },
    {
        name: 'age',
        type: 'input/digit',
    },
    {
        name: 'hair_color',
        type: 'combo',
        combo_contents: [
            {
                text: 'Brown',
                value: 0,
            },
            {
                text: 'Blond',
                value: 1,
            },
            {
                text: 'Red',
                value: 2,
            },
            {
                text: 'White',
                value: 3,
            },
        ]
    }

This way we can just have the code render the fields, and validate them before submit ( that will be done server side as well, but much easier to check them client side first ).

I agree that usability should be one of ( if not our highest ) priority.

@GabeIsman
Copy link

Makes sense to me. I've had some success working with https://github.com/powmedia/backbone-forms (on backbone projects), I'm sure there are tools in other frameworks for turning a JSON representation of a data structure into a working form with validation, etc.

@thequbit
Copy link
Contributor Author

thequbit commented Jul 8, 2015

See, I knew that someone had to have solved that problem already :). That's exactly what I was thinking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants