Thank you, didn't notice it at all. 🙏🏻

Thank you for your valuable insights. I believe I have addressed most of the issues you raised. Please let me know if there is anything else I can do before moving to the front-end. Thanks again for your help!

• Update main file header
• Add code conventions
• Update license to BSD-2
• Remove unwanted comments
• Correct markdown syntax
• Remove unwanted files

In T1842#27788, @dereckson wrote:

Can you give an example of what you wish to store as information and how you wish to use it?

@dereckson hey, we forgot about id addresses, so do you think it would be wise to simply add a new column in the service table?

Add EOF new line

In M15#201, @dereckson wrote:

To be coherent with new table names, incident_post.step_id -> incident_post.status_id?

In M16#197, @dereckson wrote:

Nice to see it takes shape :)

In T1848#27049, @dereckson wrote:

So, one of the best candidate from the brainstorming is ServPulse.

In T1843#26693, @dereckson wrote:

CSS

Most Nasqueron projects use Foundation as CSS framework, and that's convenient to get for example our standard footer.

How to integrate Vue and Foundation?

I've noticed there is a project to ease development of components, vue-foundation, it offers Vue components for most used Foundation widgets, see https://vue-foundation.github.io/vue-foundation/ for a demo.

Those components are available at https://github.com/vue-foundation/vue-foundation/tree/master/src/components but there are 6 years old, so double check it against Vue syntax and against current Foundation framework syntax.

I generally start from this template to build static sites, what is great with this approach is you can easily customize the SCSS code to build your CSS + it automates tasks like webpack / minimizing / adding -moz -webkit and other prefix for custom features.