Create category pages

[furilo]

Broad categories thought so far:

• NGOs
• Software
• Crowdfundings
• ?? Patronages

Probably each of them should have categories of their own. How to tackle them?

[furilo]

Quick sketch:

Categories: I've been thinking about the three main types (ngos, software and crowdfundings) and how/if we should have subcategories for each. While exploring which subcategories could have each, I've come upon http://www.globalgiving.org/ taxonomy, which I think can cover the three categories at once. Let me know what you think. Apart from this fixed categories, maybe we should let people add tags to projects.

More filters: I would not add much more for the time being.

Main column: very simple, I'm not in love 100% with that but I think for a start we should not complicate it much more.

Thoughts? @ferblape @jorgesancha

[ferblape]

I'd remove the last project added section to keep it even more simpler. In the beginning there won't be so many projects, and we can highlight the new ones just by adding a "NEW!" tag close to the name.

The taxonomy looks correct to me.

[furilo]

ok...

regarding taxonomy and tags about projects, how should we implement that?

[jorgesancha]

Looks great, @furilo. This now looks like a proper projects page.

Agreed with @ferblape. If we found a good use case to see the latest projects added, you could also add a sorting option like "Alphabetically - Recently Added"?

On Thu, Jan 8, 2015 at 4:20 PM, Álvaro Ortiz notifications@github.com wrote:

ok...

regarding taxonomy and tags about projects, how should we implement that?

— Reply to this email directly or view it on GitHub https://github.com/furilo/trackdons/issues/15#issuecomment-69193463.

[furilo]

So...

[jorgesancha]

:+1: but not sure about "With most donations", sounds a bit convoluted. How about "Popular"?

Or:

Or if "popular" doesn't work, maybe just:

[jorgesancha]

I don't know why I've assumed A-Z would be the default option. Maybe "Latest" should go first

[furilo]

Popular is perfect.

Regarding implementation... would it make sense that we save the categories as tags, and control is some place which are the "official tags" so we show only them in a select, and then we have another field where people can add as many tags as they need? (I'm trying to avoid having tags and then another thing for categories... but I'm not sure if its too ñapas)

[jorgesancha]

In my opinion (and I totally yield to @ferblape here), it is generally better to use different constructions for different things. A tag is a tag (it helps describe the content openly) and a category is a category (it helps classify the content), and using the same construct for both is probably premature optimisation.

If you are feeling the urge to use the same construct for both, it might be a smell that we only need one for now (tags or categories)?

[ferblape]

I agree with Jorge that we should go with separated models. It'll be easier in the future merge both that separate both, and the code will be cleaner.

On Sun, Jan 11, 2015 at 5:04 PM, Jorge Gomez Sancha < notifications@github.com> wrote:

In my opinion (and I totally yield to @ferblape https://github.com/ferblape here), it is generally better to use different constructions for different things. A tag is a tag (it helps describe the content openly) and a category is a category (it helps classify the content), and using the same construct for both is probably premature optimisation.

If you are feeling the urge to use the same construct for both, it might be a smell that we only need one for now (tags or categories)?

— Reply to this email directly or view it on GitHub https://github.com/furilo/trackdons/issues/15#issuecomment-69499405.

[furilo]

OK, perfect!

On Mon, Jan 12, 2015 at 11:31 PM, Fernando Blat notifications@github.com wrote:

I agree with Jorge that we should go with separated models. It'll be easier in the future merge both that separate both, and the code will be cleaner.

On Sun, Jan 11, 2015 at 5:04 PM, Jorge Gomez Sancha < notifications@github.com> wrote:

In my opinion (and I totally yield to @ferblape https://github.com/ferblape here), it is generally better to use different constructions for different things. A tag is a tag (it helps describe the content openly) and a category is a category (it helps classify the content), and using the same construct for both is probably premature optimisation.

If you are feeling the urge to use the same construct for both, it might be a smell that we only need one for now (tags or categories)?

— Reply to this email directly or view it on GitHub https://github.com/furilo/trackdons/issues/15#issuecomment-69499405.

— Reply to this email directly or view it on GitHub https://github.com/furilo/trackdons/issues/15#issuecomment-69659796.

http://www.mumumio.com http://www.furilo.com

[furilo]

I have loaded the categories in production, and classified the projects we had: everything makes sense, no project has been left without category, and have projects in many categories!