marsbased / marsman Goto Github PK

Migrate the messaging system from TimeMarket.

MarsMan currently uses Middleman 3. We need to upgrade it to Middleman 4.

---
title: Welcome to marsman
body: home
active: home
css: home
---

refactor and improve the following code

    <% if (class_active = current_page.metadata[:page][:css].to_s) %>
      <% class_active.split(',').map(&:lstrip).each do |item| %>
        <%= stylesheet_pack_tag item %>
      <% end %>
    <% end %>

https://github.com/MarsBased/marstyle

Our Login type of pages (Login, Sign Up, Forgot Password) have a title and a subtitle. However, if we want to have just one title, without subtitle, the title should look centered at the middle of the header.

We need to update the Gemfile to include the middleman-email gem.

In the Login page, the Login button is too small, it should be wider. This doesn't happen in the Sign Up page, where the Sign Up button has the correct width.

Implement progress circles.

Refactor using events that allow you to refresh programming when interacting with the DOM.

MarsMan is a collection of pages and components used commonly in web applications, such as login and signup pages, a navigation bar, a settings page, email notifications, etc.

Its goal is to provide you most of the pages and components that you need to develop a web application, reducing the cost of the development and its time to market, bypassing the design stage. We can define it as a starter kit created with best practices in mind, targeting MVPs and companies that don't want to spend too much money on the product design.

@MarsBased/marsbased Do you agree with this definition? If so, how should we change the project's architecture to be able to meet its goal more easily and be usable for other companies?

Currently, the only documentation of the project is the Middleman's index page, where we can see a list of all the pages styled, and the toolkit. The toolkit contains an example of each one of the components used to create the different pages.

We need to define:

• What kind of documentation does the project need? (toolkit, page examples, how to install, style guidelines, etc.).
• What do we use the toolkit for?

We need a layout for email notifications.

MarsMan Sketch file:

https://drive.google.com/open?id=0B2hqI8lAn4m2aS1CSnpuaXA4RGs

Implement a heatman table, including the order-number and sort block mechanisms

Review the MarsMan design and define new issues to improve it, if needed.

The project is currently under the MIT license. Is it right? Is there any other better license? We need to do some research and figure out if we leave it this way or if we change the project's license.

Change the ruby ​​version to deploy faster in netlify

We need to create new issues for each one of the pages designed in the MarsMan Sketch file (except for the ones that have been already implemented):

https://drive.google.com/open?id=0B2hqI8lAn4m2aS1CSnpuaXA4RGs

All websites hosted in the EU have to show a cookies alert frame to new users. We need to incorporate a cookies alert component here.

We can take the example of the MarsBased website cookies alert frame:

The current toolkit has some sections empty, like Profile Picture, Uploader or Dropdown. Implement the missing components and remove the ones that don't need to appear in the toolkit (dropdown?).

Design:

https://drive.google.com/open?id=0B2hqI8lAn4m2aS1CSnpuaXA4RGs

Implemented toolkit:

gem developer for the MB website needs to be added here.

We need a Settings page with a left-sided menu. We can use the Settings page that we implemented for some of our clients and migrate it here. However, we should also look at the MarsMan Sketch file and see that all the designed components are included.

MarsMan Sketch file:

https://drive.google.com/open?id=0B2hqI8lAn4m2aS1CSnpuaXA4RGs

People can't find the project's Waffle board right now. We can make it more accessible by adding the Waffle badges to the project's readme. At the same time, we can add badges for the license as well.

*Related issue:

• #28

People showed some interest in MarsMan when we did a bit of marketing, and other companies have used it to develop their own projects. For that reason, it'd be good to define a versioning system as soon as possible. People using MarsMan need to know which version are they using, what changes have been made in each version, if there are dependencies in a given version, etc.

We need to create a new layout that includes a fixed navbar at the top of the screen. The navbar should contain the typical components like a dropdown menu, a search box and a username, among others.

https://drive.google.com/open?id=0B2hqI8lAn4m2aS1CSnpuaXA4RGs

Follow structure as in https://github.com/MarsBased/middleman-webpack-sample

For marketing purposes, we prefer to call this tool just MarsMan, instead of MarsMan Template. We have to replace every MarsMan Template copy for MarsMan and replace all the logos.