Core-Styles 3

Welcome to the 3rd major release of Webstop's grocery website front-end design system.

You can find the latest documentation at guides.webstop.com, which represents the latest code in the master branch.

Setup

Before you run the development server for the first time run the following command:

./setup

Development Server

You'll want to open two terminal tabs/windows in the root of this project.

• Tab 1 run: ./serve
• Tab 2 run: ./watch

The first tab runs a Hugo we server. This monitors the markdown files in the documentation site and recompiles them everytime a change is made.

The second tab runs watches the Sass files and recompiles them into CSS everytime a change is made.

Once you've started the webserver visit localhost:1313 to see the documentation website.

Important Developer Notes

Development Folders

The following folders are the primary places you work when creating CSS and documentation.

• site
• scss

site

This folder contains the source files for CS3 documentation. The directory you want to work in is found at site/content/docs/3.0.

scss

This folder contains the source files for CS3 stylesheets.

Generated Content Folders

Some content is generate from source files and placed into special directories.

Do NOT edit the files in the following folders:

• dist
• docs
• node_modules

The files in the above folders are generated from files in other places. As described below.

dist

Short for distribution, the dist folder contains the production ready CSS and JS produced by core-styles. It is the end product of core-styles that can be used as a node module and/or placed on a CDN.

Files modified in the scss and js folders are processed (linted, compiled, minified, concatenated, & etc.) and are then placed in the dist folder. Once we tag a release on the Github site the contents of dist become available as a node module, and can be installed with NPM or Yarn.

docs

Short for documentation, this is the developer documentation website hosted on Github pages. Github has a special feature you can enable that serves the content of the docs folder as a website. This is how we are publishing the documentation found at guides.webstop.com

Files modified in the site folder are processed (converted to html, with headers, navitagion, & etc.) and are placed in the 'docs' folder. Once the core-styles repo is deployed to the Webstop Github account the documentation site is deployed.

node_modules

This is where all the 3rd party node modules are stored. This folder is not checked into git. The files found in the node_modules folder are defined in the package.json file. Node modules are how we include 3rd party libraries and frameworks for JavaScript and CSS, things like Bootstrap 5.

Creating New Javascript files

When you want to add a new javascript file, the following must be done in order to use it:

• List the new file in the site/content/docs/3.0/getting-started/introduciton.md page.
• Add the file to the documentation website at site/layouts/_default/baseof.html.
• Add the file to the core-lasso and tops-lasso websites
• Add the file to the styler gem (2 templates, used for core-rails).

Docker Notes

The base hugo image runs the hugo command everytime you start a container. You can't do things like docker compose run build bash $@. Therefore our you can only use bash through the special bash container. The bash container is based on the same Hugo image as the other containers but it starts with the bash command instead of the hugo command, and it installs Sass in a global context to you have access to the sass command.

Deploying

Follow these steps to deploy the Framework.

1. Update the version number in the package.json file & current_verison number in the config.yml file (remember the new version number).
2. Run the CSS compile script. We will launch a node container and run the script that moves all our latest CSS and JavaScript into the dist folder.

• Run the ./bash command.
• then run npm run pushable.
• then type exit to leave the node container.

3. Commit & Push

• Do a git add -A.
• then a git commit -m "some message".
• then git push origin master.
  • go to github and make a pull request, or git push webstop master.

4. Tag the Release

• Visit core-styles-3 releases in a web browser.
• Click the Draft New Release button.
• Enter the same version number you used in step 1 with a v appended to the front (e.g. 1.0.2 is v1.0.2).
• Write a Helpful Title, and optionally a description.
• Click Publish Release.

5. Publish on the Main-Core CDN

• Using an S3 client like Transmit got to the bucket called core_app_assets, within there you'll want to visit the following path core-repos/core-styles-3 inside there you should see a bunch of folders with names that match tagged releases like the one made in the previous step.
• Create a folder that matches the name of the tagged release you made in the last step.
• Copy the dist folder from this repo into the new tag folder.
• Create a folder named src in the same new tag folder, it should be on the same level as the dist folder.
• Copy the js folder from the root of this repo into the src folder.

6. Publish on the Ace-Core CDN

• Repeat step 5, but on the Ace AWS account.

At this point you've deployed the code and tagged it. It is ready and available to be installed as a Node module via a package manager like NPM or Yarn.

Installing via NPM

In the project you'd like to include the new version of core-styles-3 in:

1. Update the version in the package.json file (in the project root).

Your package.json file will looks something like this, likely with a lot more stuff in it.

{
  "name": "core-customizations",
  "version": "0.0.1",
  "private": true,
  "dependencies": {
    "bootstrap": "5.3.1",
    "core-styles-3": "github:webstop/core-styles-3#v1.0.2",
    "jquery": "3.7.0",
    "@popperjs/core": "^2.11.8"
  }
}

On the line that reads "core-styles-3": "github:webstop/core-styles-3#v1.0.2", you'll want to change that version number at the end of the line from v1.0.2 to whatever version number you used when tagging a release on the Github website.

2. Then run npm update

Now you should have the latest version of the node module installed in your app.

CSS Compiling issue

There is currently an issue with the recompiling scripts. Although they seem to run, they do not actually automatically compile the css as desired. In order to work around this, use the bash container mentioned above and run the following

• npm run css-compile-docs: manually compiles the css for the documentation & development site.
• npm run css-compile: manually compiles the css for production distribution (places it in the dist folder).