Update docs with Forem instead of dev.to (#9316 )

* Rename all GitHub links from thepracticaldev/dev.to to forem/forem

* Use new site name

* Rename to Forem

* Rename more dev.to to forem

* Remove unnecessary redirects

* Rename DEV to Forem

* Use Forem instead of DEV for branding

* Use Forem instead of DEV for licensing

* Use seedling instead of DEV logo

2020-07-15 13:29:11 -04:00

1.3 KiB

Raw Blame History

title
JavaScript and Initializers

JavaScript and Initializers

Forem has two JavaScript codebases.

One is located in the directory app/assets/javascripts and contains plain JavaScript (mostly ES5+) being served using Sprockets which packages static assets.

Webpacker manages the other one, which you can read more about in this guide.

This source code is not transpiled, only packaged and minified, and will be limited to whatever flavor of JavaScript can run on the user's web browser.

app/assets/javascripts/application.js contains the manifest JavaScript file which is included globally in the primary template, app/views/layouts/application.html.erb.

application.js automatically includes all JS files via the statement:

//= require_tree .

One JS file in particular, app/assets/javascripts/initializePage.js.erb, boostraps the majority of the functionality. You will notice, within this file, that major sections of the websites are bootstrapped, for example:

initializeBaseTracking();
initializeTouchDevice();
initializeCommentsPage();
initEditorResize();
initLeaveEditorWarning();
initializeArticleReactions();
initNotifications();
initializeSplitTestTracking();

All the "initializers" are in /app/assets/javascripts/initializers.

1.3 KiB Raw Blame History

JavaScript and Initializers

1.3 KiB

Raw Blame History