documentation for non-developers

[jazzband]

documentation for non-developers

[ababic]

Hi @longwuyuan. I'm glad to have been able to help. I think this could be that the pages you have chosen for menu items aren't set to appear in menus. Check the 'Promote' tab in the edit page for those pages... there should be a checkbox there for you to check. It's a common gotcha... It still trips me up every now and then :)

[ababic]

Hey @longwuyuan,

The installation takes care of the migrations etc, but to get a main menu to show up, you need to define what the menu items are for your site via the Wagtail admin area. The instructions are a little bit further down in the README here:

https://github.com/rkhleics/wagtailmenus/blob/master/README.md#1-defining-root-level-main-menu-items-in-the-cms

Hope that helps :)

[longwuyuan]

My mistake for not providing enough data.
I did define 5 items (products,services,support...) visible in attached screenshot.

Thanks tons for confirming that all I need is documented install of the extension + creating items in Main Menu. I will try now one more time and update.

[longwuyuan]

I got the menu and the root cause was the checkbox for "show in menus".
Hope I can give back. Lot of heartfelt gratitude.
I have goosepimples just thinking of what I can do now by just inserting the CSS CDN URLs etc.
Tons of thanks.

[ababic]

You're very kind @longwuyuan. I'm glad you managed to make some progress. Happy wagtailing! :)

[longwuyuan]

Extremely extremely happy wagtailing from now on. :-) Automatic menus is a dream come true.
Do I need to code css or will I get dropdowns for submenus.
Also, can you point me to some docs on how to paste in a sitewide CSS.
Basically, like I said, wagtail's beauty & awesomeness is being held back only because a non-developer like me needs to rely on a developer fpr menus and css. So 50% roadblock removed because of this here extension. Wishful thinking is to have another extension for CSS (or theming if you will) and I can produce 1 production website everyweek with all the other wagtail*** addons.

[ababic]

If you look around, you'll probably find that the CSS side of things is deliberately left up to developers to work how they'd like to handle static assets, as there are a number of options out there. Developers could argue eternally about what the best overall solution is, but it will really come down to preference, and may even vary from project to project.

For example, you could use something like https://github.com/django-compressor/django-compressor or https://github.com/jazzband/django-pipeline/ to compile and combine assets at run-time, or compile assets using node, perhaps with something like gulp or grunt.

The django docs should be able to help with the basics though: https://docs.djangoproject.com/en/1.10/intro/tutorial06/

[longwuyuan]

i learnt more in one day today than I did in months/years. thanks tons. am good for now. basically better to learn django well. I was avoiding it because could not figure out where to spend time in flask vs django vs tornado.
sorry for all noobie nonsense. much thanks again. am good for now.

[ababic]

Don't sweat it @longwuyuan. We're all noobies until we need not to be :)

[georgiana-gligor]

Thanks @ababic for the common gotcha, I fell into the same trap. I should probably think of contributing to the documentation to make this more visible.

[ababic]

Thanks @georgiana-gligor. I'd be very grateful for any contributions to improve the documentation. As the developer, it's always tricky to write for an audience that isn't familiar with all the finer points of the implementation. Some insight from real users would be a great help to other devs!