You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

There are many ways stay up-to-date with Magnolia. Choose the options that best suit your work style and requirements.

Official documentation

We update the documentation site continually and you can set preferences in your personal space for update notifications. Use your JIRA credentials to log in and go to <Your Name> > Settings > Email to set your preferences. Register a JIRA account if you don't have one. There are numerous email options and you can also Favorite other users and Watch pages for updates. 

On each documentation page, you can Like and Comment. Feel free to comment and show your support. We welcome your feedback. Pages are monitored continuously and a staff or community member will answer promptly. Posing technical questions on our forums is often a better alternative to commenting, because your issue is exposed to a broader base - Magnolia staff and highly-skilled community members, who are always happy to lend a hand.

Academy

Magnolia Academy is an online learning resource aimed at newbies and advanced users alike! It's not only free, you can get Magnolia certified too. Learn Magnolia at your own pace. There are video tutorials, step-by-step guides, tests and more.

Forums

Magnolia Community Forums are active. Post your questions and they'll be answered by members of the Magnolia community and staff.

Mailing lists

Mailing list subscribers receive constant updates in their inbox:

  • Users list: Intended for Magnolia users of all technical levels. Here you can find help, help others and share your experiences. Forum posts in the Get help with Magnolia forum are also sent to this list. Subscribe to Users list.
  • Developers list: This is where Magnolia developers exchange information and keep up-to-date on development status. Notifications from the JIRA issue tracker are included which makes this a extremely busy list. If you don't want your inbox flooded, choose and alternative. Subscribe to Developers list.

Once subscribed, email user-list@magnolia-cms.com to ask a question or share your knowledge. While you can email the Developers list at dev-list@magnolia-cms.com, a far better alternative is to create a JIRA issue.

You can unsubscribe at any time by emailing user-list-unsubscribe@magnolia-cms.com or dev-list-unsubscribe@magnolia-cms.com.

Mailing lists are archived in the Get help with Magnolia and Development forums

Newsletter

The Magnolia newsletter is published  once a month. Subscribe to stay up-to-date on major developments. In addition to company news, the newsletter includes documentation updates and recent blog posts. Browse recent newsletters to see sample content. Newsletter subscribers also receive the Doc News newsletter that is sent when there are important documentation updates.

Blogs

Magnolia has an active blogging community. You'll find many "pearls of wisdom", and insider tips and tricks. Here are a few of the latest posts.

  • The Development blog provides regular updates from our development team.

    Could not retrieve http://dev.magnolia-cms.com/blog/feed/ - Page not found.

  • At Planet Magnolia you can read an aggregated feed of individual Magnolia bloggers.

    Error rendering macro 'rss'

    com.atlassian.sal.api.net.ResponseException: java.net.UnknownHostException: planet.magnolia-cms.com: Name or service not known

Community wiki

The Community wiki is where Magnolia developers and experienced partners and clients share their knowledge. There's are "How tos", tutorials and more. You can participate and share your knowledge with others by creating useful pages.

Developer wiki

The Developer wiki is where our developers document new concepts, ideas and projects.

Social

Follow Magnolia on the best social networks for the latest news and periodic events. Our YouTube channel has tutorials, webinar recordings and more.

       

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels