raupach-e2n commented on PR #737: URL: https://github.com/apache/maven-site/pull/737#issuecomment-2742880264
It's fine. Your project, your call. Just let me address your thoughts: > These are not concepts, but some kind of glossary entries - we have a glossary page Words. A glossary is for words. Maven has terms and concepts that are very relevant to getting started and to work with Maven. Call it terminology, but concepts has a better touch to it. Less academical, less technical. Have seen it used in other English technical documentations, that why I used it. Maven has a glossary page. True. First time I head it. Had to search or google to even find it on the site. The biggest problem with Maven is its complexity. It is very hard to teach Maven to new developers. A documentation that has its glossary or other relevant information hidden somewhere does not help at all. That is not a documentation, that is just a collection of pages. > 2. We already have these information, but with more details in each of their articles. Maybe they are not that visible Not maybe. They are not visible. The navigation on the site is not easy to work with. Yes, you want to change some things, you have some things written down somewhere, to appear someday. Why don't work little by little? Make little changes, see if it works, and revert if it doesn't. I heard that is the better way instead of having a a non-shared feature branch that will be merged with a big bang. Just my two cents. :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
