16

Let's take your questions one by one: How To Customize Checkout Page Using One Page Checkout extension Call IWD Agency Magento 2.2.6 Maybe you don't get an answer to this one because it's not a core related question and not a lot of people used the extension you are using. Geting Error In Checkout Page Magento 2.2.6 This is the same question as the next ...


14

Yes, you can ask questions that contain "Magento 2" in the title. It is not encouraged because version numbers can be added in the tags as you say, but it is not forbidden. As for SEO, I don't know if it helps or not. I think the SE network does a good job for SEO anyway.


11

you can go to https://magento.stackexchange.com/users/preferences/ and at the bottom of the page you will see Ignored Tags. Fill in magento2 in there and you should not see those questions anymore.


9

You couldn't have asked this at a better moment than right now. Today the 6th MageStackDay has started and the MageStackDay tradition addresses an issue you are running into. Let's start with stating that there are many many more people asking questions than there are people who provide (quality) answers. That's part of your problem, because that means that ...


6

Magento 2 questions are allowed. They should just be tagged with the proper version to make a difference between pre-alpha, alpha, beta, rc and official release.


6

Magento will remain same as now. It will remain as an Open source platform as per Matt Asay who is the Head of Developer Ecosystem for the Adobe. From below sources, you will get more information regarding Magento future with Adobe. Check out the tweet of @MattAsay which showers hope. Check out @Abobe official blog regarding acquiring of Magento. Article ...


6

Do you find it complex too? No, I think the documentation is very clear, but you should not read it from the beginning to the end at one time, just use it as a handbook. Do you think a newbie can understand it well? Yes. In case you are interested in "How the plugins work?" you can find the answer in the documentation and you can understand it. ...


5

Sure, even if iam not sure who you meant with "we". For a community with this size its ok to have multiple different chat/communication channels. To list some of them: irc, reddit, magechat( slack), gitter. Even stackexchange has an own chat system Some of them have dedicated mage2 channels, others not (yet). I did not look yet how discord works, but i ...


5

Price Question is open Now. As a moderator, I don't think the close votes over this question are not wrong since the user did not post some other details. On the first post of the question, the user only asked he has customized, as per as MSE rules it went to too broad and unclear what you're asking rules. This question is not clear what he/She want. If ...


4

Great, approved by 2/3 mods. So if anybody wants to actively help out, these are the tags that I could find: magento2-pre-alpha magento2-alpha magento2-alpha93 magento2-alpha96 magento2-alpha105 magento2-dev-beta magento2-merchant-beta magento2-rc 2.0.0.0-dev55


4

from what I see your questions tend to be quite broad feature requests. These seldom get proper answers here. I can recommend narrowing them down and adding things like what you have tried so far. Any code that is failing, specific errors the community can help you with.


4

We will bow down to the all mighty Dependency Injection. Here is preview: http://inchoo.net/magento-2/basics-dependency-injection-usage-magento-2/ Here is the full "holly book": http://devdocs.magento.com/


3

Magento is going to be supported 3 more years after v2 is out.


3

I think some question which fit squarely into the "issues" bucket belong on GitHub. But for questions which do not rise to the level of "hey something's broken" or "hey I have an architectural suggestion / improvement" are noise in a GitHub context. My opinion of course, and curious to hear the opinions of others.


3

I'm in favor of the dev* number because it's very clear what version the answer applies to. We should take care to prod the OPs for the version when answering Magento 2 questions.


3

Magento 2 community is not dead but there are few reason for not getting response very soon as you get on stackoverflow because: There are less number of Magento developer as compared to core PHP web developers and more less developers of Magento 2 framework who are expert. Writing code of Magento 2 questions requires more effort. Even if developer knows ...


2

You are right that this edit made the title more clear and the majority of the reviewers agreed, so don't worry. The one reviewer who disagreed might have not looked closely enough because on first sight it doesn't look like a very useful edit: only minor change, redundant adding of "Magento 2" in the title (this is what tags are for) and it's an old ...


2

A shortcut to this user preference is in the sidebar for all Stack Exchange communities, though it's not labeled terribly well. Select the "edit" link next to "Favorite Tags". Once you click "edit", you'll see an area to select Favorite Tags as well as Ignored Tags:


2

I've done my share on a few tags. I have also removed the tags from closed questions because if you are tagging your question and type "magento2-" you still see them appearing in the suggestions with a >0 count. Only magento2-dev-beta is still left with a large number of questions. magento2-pre-alpha > 0 questions magento2-alpha > 0 questions ...


1

Also, maybe we should create tag synonyms for those tags so no one use them in the future.


Only top voted, non community-wiki answers of a minimum length are eligible