আপনার অনুসন্ধান ফলাফল


    Our volunteers haven't translated this article into বাংলা (বাংলাদেশ) yet. Join us and help get the job done!

    What is the Mozilla Developer Network ?

    Mozilla Developer Network (MDN), formerly Mozilla Developer Center, is the Mozilla-backed community website for development documentation of web standards and Mozilla projects.

    Getting started

    How can I get involved as a new editor ?

    While it can take some time to learn all the finer points of editing on MDN, you can start writing right away. The community engages newcomers to learn new things. Follow these simple steps to get involved.

    1. Create an Account on MDN.
    2. Subscribe to the dev-mdc mailing list (optional but highly recommended).
    3. Start your first contribution by editing articles. (You can also create a new article, but it is a good idea to discuss on the mailing list first, to be sure the article is needed.)
    4. Wait for reviews and learn from them.
    5. Practice and contribute routinely.

    What are the benefits of writing on MDN ?

    It will give such an experience to you how to work with a community and it will improve your written communication skills. Also it will help you to add lines in your resume.

    What are the next steps ?

    Just follow the steps on this article Getting Involved on MDN.

    Writing on MDN

    The easiest way is to use the anch macro. This macro has one required parameter: the name of the section you want to link to. By default, the displayed link text is the title of that section, but you can add a second, optional, parameter indicating alternate text to use instead. Some examples:

    A page is showing out-of-date generated content. How do I fix this?

    MDN's support for KumaScript macros and transclusion of content from one page into another can sometimes be hampered slightly by the need for caching of generated pages for performance reasons. Pages are built from their source, and that output is cached for future requests. From then on, any macros (templates) or transclusions (using the Page macro on that page will not reflect changes made to the macro, the macro's output, or the contents of the transcluded material.

    • To update a page manually, you can do a force-refresh in your browser. MDN detects this and triggers a page rebuild, pulling in updated macro output and transcluded page content.
    • You can also configure pages to periodically be rebuilt automatically. This should not be done unless you expect the page to need updating frequently. See

    What's the best way to copy content from one page to another?

    Sometimes, you need to reuse the same text on multiple pages (or you want to use one page's content as a template for another page). You have three options here:

    • If you want to copy an entire page, use the Gear menu's "Clone This Page" option while viewing the page you want to copy. This will prompt you for a destination; once you've copied the page, you can edit the copy as usual.
    • If you want to copy just part of a page, don't just visit the page and copy from it. This, when pasting, will introduce unwanted additional bits of HTML into the destination page, and either you'll have to clean it up or one of the site moderators will. Nobody wants that. Instead, click the Edit button on the source page, copy the content you want to reuse from within the editor, then click Discard to exit the editor.
    • Sometimes you literally want to use the same content on many pages. In this case, you might be best off placing the content in one page, then using the Page macro to transclude the material from one page into another. This way, whenever the text on the source page is updated, the destination page will update as well (with the caveat that this will only happen on a forced-refresh or when the target page goes through a scheduled rebuild).

    How do I add compatibility information for Edge or another browser?

    For an outright new browser, which is not already covered anywhere on MDN, you should start a discussion on the dev-mdc mailing list so the community can decide if the browser needs to be specifically covered. Once the decision is made to include the browser you want to include,  just add a new column to both the desktop and/or mobile versions of the compatibility table for the new browser on all affected pages. Please put the new column in alphabetical order.

    Note: We are developing a new, more powerful, system for managing compatibility data. See Compatibility tables for details.

    ডকুমেন্ট ট্যাগ এবং অবদানকারী

    Contributors to this page: jswisher, Sheppy, teoli, Uemmra3, mohamednizar
    সর্বশেষ হালনাগাদ করেছেন: Sheppy,
    সাইডবার লুকানো