Skip to main content
This section answers common questions regarding where to place your code. These recommendations are found to be working well at digitally induced. In general, remember that all specific web app logic should stay in the Web/ space. The Application/ space is for sharing code across all your different applications. E.g. code shared between your web application and your admin back-end.

​
Directory Structure

File or DirectoryPurpose
Config/
Config/Config.hsConfiguration for the framework and your application
Config/nix/nixpkgs-config.nixConfiguration for the Nix package manager
Application/Your domain logic lives here
Application/Schema.sqlModels and database tables are defined here
Web/ControllerWeb application controllers
Web/View/Web application HTML template files
Web/Types.hsCentral place for all web application types
static/Images, CSS, and JavaScript files
.ghciDefault config file for the Haskell interpreter
.gitignoreList of files to be ignored by git
App.cabal, Setup.hsConfig for the cabal package manager
default.nixDeclares your app dependencies (like package.json for NPM or composer.json for PHP)
MakefileDefault config file for the make build system

​
Common Questions

​
Where to place a function I want to use in all my views?

If the function is only used in a single application and is a building block for your layout, place it in Web/View/Layout.hs. The module is already imported in all your views (just don’t forget to add the function to the export list). If the function is used across multiple applications or more like a helper function, place it in Application/Helper/View.hs. This module is also already included in your view files.

​
Where to place a function I want to use in all my controllers?

Place it in Application/Helper/Controller.hs. This module is already imported into your controllers.

​
Where to place a custom type?

Place it in Web/Types.hs.

​
Next to my main web application, I’m also building an admin back-end application. Where to place it?

An IHP project can consist of multiple applications. Run new-application admin inside a nix-shell to generate a new admin application. The logic for the new application is located in the Admin/ directory. You can find it on the web at http://localhost:8000/admin/ (all actions are prefixed with /admin/).

​
Organizing Assets

​
How to structure my CSS?

CSS files, as all your other static assets, should be placed in the static directory. Create a static/app.css. In there use CSS imports to import your other style sheets. An example app.css could look like this: 
@import "/layout.css";
@import "/widget.css";
@import "/form.css";
@import "/button.css";
@import "/users.css";

​
Page-specific CSS rules

Place page-specific CSS used by e.g. views of the Web.Controller.Users controller in users.css. Use currentViewId to scope your CSS rules to the view. Given the view: 
module Web.View.Projects.Show where

render = [hsx|
    <div id={currentViewId}>
        <h1>Hello World!</h1>
    </div>
|]
This will render like: 
<div id="projects-show">
    <h1>Hello World!</h1>
</div>
So in your projects.css you can just do rules like: 
#projects-show h1 {
    color: blue;
}
We discourage the use of tools like SASS or Webpack because they have too much overhead.

​
Library CSS

CSS files from external libraries or components should be placed in static/vendor/.

​
How to structure my JavaScript Code?

JavaScript files, as well as your other static assets, should be placed in the static directory. In general, we follow an approach where most of the business logic resides on the Haskell server. Only for small interactions, or client-side GUI niceness, we try to use a small isolated bit of JavaScript. Your global, non-page specific, JavaScript code can be placed in app.js. E.g. the app.js could look like this: 
$(function () {
    initNavbarEffects();
});

function initNavbarEffects() {
    // ...
}
In your Web.View.Layout just import the app.js: 
<script src="/app.js"></script>

​
Page-specific JavaScript

Place page-specific JavaScript used by e.g. views of the Web.Controller.Users controller in the users.js. In the views, just import the JavaScript with <script src="/users.js"></script>.
We discourage the use of Webpack or any other bundler because they have too much overhead. Of course, this advice only applies if you follow the approach to use as little JavaScript as possible.

​
Library JavaScript

JavaScript files from external libraries or components should be placed in static/vendor/. For simplicity, it might make sense to just download the JavaScript bundle of the library you want to use, and then just commit it into git instead of using NPM. For more complex use-cases with lots of JavaScript, you should not follow this advice and just use NPM instead.

​
Where to place static images?

Place your images in the static folder. We recommend using SVG images.

Build docs developers (and LLMs) love

Get started for freeTalk to us