Open paul-millar opened 10 years ago
Response to critical questions:
1) Song and Post were separated in my branch in order address a few problems. The first of these problems was constructing a workflow for post writing that made sense with our 3 types of written content: 1. Quick Hit 2. Review 3. Long form (more later). Having a 2 step process to post writting REQUIRES at least a written description for the song. This would be considered ourDisqus hit", and if the author does not want to write a full review, they stop there. If the author chooses to write a review of the song, they can now do this right on the page of the song they just created in step one. This allows for the writer to listen to the song right from the embed on the page, or return to an older post as a "retro-review" of sorts. Comments has also been moved to belongto songs. The second problem this new issue addresses is the lack of focus on "song and artist first". I would describe radcircle right now as "written post" first, which removes the attention of the user from the song the author is curating (my opinion obviously). Song first approach of my branch is built to be driven by attention placed on the song and argument by the curator rather than a song and artist field in a post.
Feature is the long form, its built to be separate from the song and post as a longer piece should not be attached to one song. This is an area I would like to be better defined in order to better address what the authors want out of a longer post.
2) We can go ahead and strip out the admin model, that is a hold over from just trying to get something built up quickly and better understand devise.
3) my admittedly limited web development experience wants clarification on this question. My initial response is no, BC i built it as a has many association for categories and songs. Tags are not categories (categories would be electronic, rock, pop, hip hop, etc), but I could see tags as being the more specific subgenres of the larger genres found in categories.
Radcircle is a place for users to come discover great music from all genres curated by our authors. Radcircle is also a site that should allow artists to market themselves and be discovered. (I know its a little open ended, something that has been discussedbut absolutely needs to be defined so it can be built).
Thanks Austin
Hi Austin,
Thanks for your feedback. To put my thoughts onto the issues:
The above is what we need to get creative with. This is what will set us apart from 'just a review website'.
Awesome! In a few hours, if you like, I can open the readying_user_function branch on my nitrous box so you can play with it.
All good - as its on a github branch I can pull it.
Hi Team,
Whilst this is mainly directed at the changes in Austin's feature branch, I figured it was best to start discussion on on the architecture / intention of Radcircle. I'm aware there is a development doc going about but its not super specific as is. If everyone could chip in on this issue it would be great.
I am fully aware that some of these may be because everyone here is learning and you simply don't know any better. In which case, please dont be bummed out by the following questions I have. We're all learning here and the some constructive criticism is the way to move forward! : )
In terms of nitpicking / specifics:
A lot of the above relies around naming / intentions. There are a few principles in software development we should all be aware of:
Also, naming things is often described as one of the hardest things in software development. Now we're all working in a team, we should be naming things and writing code so that it can be interpreted easily be other team members.
The above specifics are key points in me merging everyones commits together so we can move forward as a team. If we can get some active discussion around this and decide on the way forward that would be ace.
As such, what is everyones 'vision' of Radcircle and what exactly should it be doing in terms of goals / intensions / features.
Cheers