Basic App Layout

[flashback2k14]

Should we use:

• a sidebar or
  • always visible or
  • always invisible or
  • only icons visible
• tabs or
• tabs for desktop and sidebar for mobile?

What did you think @hetec

[patrick-hebner]

A more generell question would be mobile or desktop First. After this we should concentrate in oben of These Layouts. I think this would make decissions easier

[patrick-hebner]

Ist the Travis File mit in the repo

[patrick-hebner]

Ist it possible to share the cofig for linting Travis and auch things between frontend and Backend?

[flashback2k14]

I think mobile first should be our strategy. Everybody has every time the smartphone on the hands. :-)

[flashback2k14]

The travis file is inside the root folder. We need to install angular-cli inside the travis container and call the ng commands.

[patrick-hebner]

I also think is a Lot easier to expand the layout from a mobile approache aß a basis

[patrick-hebner]

So lets make mobile fist settled

[flashback2k14]

Yes. Now, we should sketch some mockups!?

[patrick-hebner]

Maybe we should also create a wiki page for this. There we can upload images and discuss the designs / mockups ?!

[flashback2k14]

i have added this pages. It only need some content. ;-P

[patrick-hebner]

What do you think, should we first collect some information about what will be displayed in the different areas? Like Landing page, profile, Ingredients, recipes and so on. I think especially general places like the landing page (after login) are bit more complicated since there can go anything and nothing.

[flashback2k14]

That's a good idea. First collect some data and maybe sketch some mockups if we have nice ideas.

[patrick-hebner]

Minimum device size? 360?

[flashback2k14]

I think this is a good reference.

[flashback2k14]

What did you think @hetec?

[flashback2k14]

@hetec to recap: collect some information what we want to display inside your wiki and sketch some mockups!?

[patrick-hebner]

yes let's do this

[patrick-hebner]

I currently thought about the the layout and it could be a little bit difficult to implement something like editing a recipe for mobile. And I'm also not 100% sure if it makes sense to add/edit a recipe on mobile (since it so much to enter)

What do you think 🤔? Makes it sense, or do we need another approach? Maybe like GitHub: not fully mobile desktop version + mobile version / app or so (could be created later). The mobile version could then provide a different feature set e.g. readonly or so

[flashback2k14]

Hmmm, what did you think about this sketch? Simple responsive column layout.

[flashback2k14]

I don't like that GitHub has limited features on mobile devices.

[patrick-hebner]

Yeah, let's stay with the full mobile version! Looks fine