8

Proposal: Magento

So, we have a lot of work ahead of us to prove that we will be a successful community apart from Stack Overflow. In addition to the public commitment & beta requirements, there is an independent (read: StackExchange-internal) review process which will decide whether the Magento SE site does not overlap too much with / add too much noise to the excellent StackOverflow forum. One of the things which we can do at this point to demonstrate the differentiating needs is to define a tag taxonomy which will found our site. I think that doing this now can also help us to focus our scope.

Example tags might be admin-gui, enterprise-feature, catalog-management, extensions, themes, etc. I draw significant inspiration (and justification) from the WordPress SE site's tag list.

6 Answers 6

Reset to default
10

Off the top of my head (coffee hasn't happened yet), and with the two caveat that I'm not all that wedded to the names below, but more to the ideas/descriptions therein

order-workflow -- any question dealing with data and workflow of taking a placed order and getting it to a state where it's paid for, shipped, and off to the customer. Roughly anything under the sales menu.

payment-modules -- any question dealing with the creation of, integration of, and support of payment modules. The things that let you interact with money making systems (AuthorizeNET, PayPal, Stripe, etc.)

shipping-modules -- any question dealing with the creation, integration of, and support of shipping modules. (UPS, USPS, FedEX, etc.)

tax-rules -- any question dealing with Magento robust yet arcane systems for managing state-wide and product specific (weee!) tax systems

catalog-promotions -- any questions dealing with the setup of catalog (side wide) promotional rules

shoppingcart-promotions -- any question dealing with the setup of shopping cart promotions (coupons)

cms -- any question dealing with Magento's CMS and static block features, as well as questions related to integration with third party CMS systems

widgets -- any question dealing with Magento's CMS Content-Type/Widget features (widgets feel complicated enough to warrant their own tags)

reporting -- any questions dealing with Magento's internal reporting system, as well as questions about integrating with third party reporting systems

inventory-management -- any questions dealing with integrating Magento with inventory management systems, or attempting to use Magento itself as the source of truth for inventory management

magento2 -- any question dealing with Magento 2, which will be out a few quarters from now. For reals.

developer -- questions oriented toward someone attempting to extend Magneto's functionality, or features that require extending it

site-builder -- questions oriented towards someone attempting to use Magento (+ 3rd party extension functionality?) to build out their store/system

transactional-email -- questions related to the design, sending, and management of the many transactional emails sent out by magento

api-soap-xmlrpc -- questions related to using Magento's original SOAP/XML-RPC API

api-rest -- questions related to using Magento newer oAuth/REST API.

3
  • Would it be worthwhile to have two tags to differentiate between technical and administration questions? I do like your rough breakdown, btw.
    – davidalger
    Jan 3, 2013 at 17:33
  • @DavidAlger Good call — I added developer/site-builder above
    – Alana Storm
    Jan 3, 2013 at 17:42
  • 1
    You wrote a book on it Alan... Where's layout?
    – pspahn
    Jan 11, 2013 at 16:50
5

Here are some of my suggestions, some might be too broad or specific:

caching - questions related to magento cache (e.g. how do I add my own custom cache that can be cleared in the admin?) or other forms of cache (e.g. memcache, varnish)

performance - questions related to performance optimization

migration - migration related questions (e.g. qa/staging -> production)

crons - cron job related questions

indexes - magento index related questions

frontend - questions related to frontend development (extending core frontend JS)

configuration - questions related to configuration of the platform

seo - questions related to SEO topics

pci - PCI compliance related questions

api - magento API related questions (e.g. rpc or rest)

search - questions related to mysql's fulltext search functionality or with Enterprise Solr

internationalization - questions related to localizing and multinational site dev/setup

sysadmin - environment related questions (e.g. setup with nginx or another web server, apache configuration)

dashboard - modifying the admin dashboard

1
  • +1 for the simpleness and to the point
    – Matt Humphrey
    Jan 4, 2013 at 9:20
2

For those who have been tasked with the lovely job of data migration...

data-migration - For general migration of data in/out of Magento, through means of core utilities, or extensions/scripts.

import-export - For importing/exporting products or customers using the default import/export tools.

dataflow-profiles - For importing/exporting entities through the dataflow profiles system.

2
  • How would something like Magmi fit into the data migration "family" ? Should it have it's own tag?
    – CCBlackburn
    Jan 3, 2013 at 21:45
  • @CCBlackburn I would probably tag it in something like data-migration extensions. Edited original answer to include data-migration tag.
    – Dan LaManna
    Jan 3, 2013 at 22:54
2

I think CE EE GO tags would be helpful. I don't see thing related to extension builders: packing, connect (should Magento Connect stuff be there as well? I think so)

2

You might be getting a little ahead of yourself. Consider this:

What will make your site look like a viable community is to have a large degree of interest both from Stack Exchange users as well as users from outside the community. Considering this was only proposed more than a week ago, has already passed the proposal phase, and has 60% of the committment needed to move to beta, I'd say there's a strong likelihood this site will make it to beta.

However, the scope in Area 51 is merely the proposed scope. Once you land in the private beta and start asking real questions about real, actual problems you're facing, that's when the real nature of the site and community will begin to surface.

Tagging is one of those things that really depends on the types of questions that are asked, and to try and list them all out now may not be helpful later on when it comes time to create tags based on the actual content on the site.

What makes a great Stack Exchange site is great questions and great answers, and committing to ensuring that the content is helpful to future visitors. If there's a strong community, good community participation and moderation, and good content, then it's okay if the site overlaps somewhat with other Stack Exchange sites.

With that said, it's good to see so many people excited about this topic. There's a lot of positive energy here. Good luck! :)

1
  • 1
    I have to admit that my main reason for asking this question was to highlight the types of topics which fall outside of the StackOverflow scope, knowing that this issue would (rightfully) be considered in the SE office. The information that you present here is valuable as well, so I am glad that you have shared it!
    – benmarks
    Jan 5, 2013 at 3:23
0

I think there should be a different tag when you're asking help developing an extension

extension-development

versus when you're asking for help with an extension

thirdparty-extension

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .