Planning the next steps

[escamoteur]

Hi,

I finally decided to make a bigger, maybe last attempt to bring my packages to a wider audience attention and trying to build a community around them.
First step was creating a new verified publisher flutter-it.dev
Next will be:

• rebranding
  flutter_command -> command_it
  functional_listeners -> listen_it

• creating a sound documentation site under the domain using http://docs.pages

• a focused social media campaign in english and spanish to get more attention

I haven't yet developed a full concept for the docs site yet and I need to get a bit more comfortable with docs.page but here are some ideas:

• easy tutorials for the different packages with different levels of expertise
• availablility in english and spanish
• additional articles on how to write whole apps with them

How you can help:

• It would be awesome if we could get a nice logo for the organisation
• A pretty color scheme would also be nice for light and dark mode
• We will need small sample projects for the tutorials so users can easily getting started
• talk about this on social media

Please share your ideas here

[Feichtmeier]

Very cool! Super hyped excited for this 😎🚀

@Jupi007 @madsrh @ubuntujaggers could you help out with an icon, a color scheme and/or maybe some basic design for a website?

I'll can help write docs and implement the website and create starter and pro projects to showcase and guide though using get_it and watch_it
First examples, though the first ones not trivial are

https://github.com/ubuntu-flutter-community/musicpod
https://github.com/ubuntu-flutter-community/nebuchadnezzar
and
https://github.com/ubuntu-flutter-community/pulse
Which are all made with watch_it

[escamoteur]

I think we don't need a lot of design for the website when using docs.page but a good idea for the overall structure

[escamoteur]

forking, and republishing of command_it and listen_it is done

[pulyaevskiy]

Nice effort!

I'm no designer but I had some plans to write a few articles on how I use get_it / watch_it in Breeze.

[escamoteur]

Hi friends, I was was unfortunately busy with some private issues but I will try to focus more now again on making progress here

[ubuntujaggers]

Hi all, apologies, currently on my holiday and only have phone - thanks @Feichtmeier for tagging me, will have a look when I'm back!

[escamoteur]

I just pushed a new version of the docs. I already splitted the get_it readme into smaller chunks. Next step would be improving the getting started section and replacing the package readme with a more simpe version that point to the doc site.

Happy for every input. @FMorschel made this correct observation flutter-it/get_it#412
Also I realised that the current readme does not cover all functions or get_it

[escamoteur]

We are live under flutter-it-dev
Now using https://vitepress.dev/

[Feichtmeier]

very nice! cool that you found a solution that is better maintained

[Jupi007]

Sorry for the very late reply @Feichtmeier, here is a quick experiment around Flutter logo design and the "it" letters :)

[escamoteur]

Hmm, a bit arbitrary, don't you think?
Can you maby pick up the philosophy that my packages are used like LEGO that you can plug them together and make something out of that?

[escamoteur]

Oh, and color scheme for flutter-it.dev would be nice

[escamoteur]

We already use symbols for the different packages that could be displayed on the bricks then we could use the single bricks as logo for the separate packages or a variation of the full logo where only one brick is colored to stand out but keepin the link to the collection.

[escamoteur]

Alternative I would like to use this cute dragon in Flutter colors if that can be done nicely. Because it's so friendly

[dabblingwithcode]

I'm not a graphic designer, but I had a talk with @escamoteur about this and find a lego brick metaphore quite fitting to the concept of the packages. For every package the front size would take another symbol (like bullseye for get_it, binoculars for watch_it). These are some variations I drafted to show what I mean (it surely can be done better than this):.



Maybe someone has a better idea or a better hand at this.

[escamoteur]

I got two design proposals, that look quire nice, I would like to know your thoughts mainly 2D/3D
Colors for the different packages

Mock Up 1.pdf
Mock UP 2.pdf

[SirusCodes]

I prefer the simplicity of the 1st mock up but would not like the blue background color for the website.
It would be better if you can follow material white and black for background as it would make it easy for eyes

[escamoteur]

OK, this goes into the right direction, what do you think about the color selection and symbols for each package? @Feichtmeier @FMorschel

[FMorschel]

I like it!

I'd probably review the colour for listen_it though. It is too close to the flutter_it one and they are so close together that it feels a bit off.

Other than that this looks great!

[escamoteur]

will get more polished but I too like it

[Feichtmeier]

looks nice! cool colors!

[escamoteur]

the get_it part of the new documentation is finished

https://flutter-it.dev/documentation/get_it/getting_started

I am happy for every feedback

[FMorschel]

Looking great!

[escamoteur]

check out the new get_it and listen_it docs now with the new logos
https://flutter-it.dev/

[escamoteur]

we now use this one :-)

[dabblingwithcode]

Nice butterfly!