User Manual

A guide for visitors and administrators of the LUDA website.

1. Getting around

  • Use the top menu for Blog (AI Trends, OWASP Security), Events & Press, Education, Open Source, Ask LUDA and About LUDA (branches, donate).
  • Switch language with the EN / KO toggle in the top-right corner. Blog lists only show posts written in the selected language.
  • On mobile, tap ☰; items with sub-menus expand when tapped.

2. Ask LUDA inquiries

  • After sending an inquiry you get a private link that only you can see. Keep it to read the reply.
  • If you lose the link, send a new inquiry with the same email or contact luda@ludaresearch.org.

3. Sign up and log in

  • A verification email is sent when you register. You can log in after clicking its link.
  • If it did not arrive, use "Resend verification email" on the login page. Repeated requests are briefly rate limited.

4. Admin: blog

  • Write and edit posts in Admin → Blog. A post is visible only when "Published" is checked.
  • Admin → Blog data import loads the markdown posts in blog_data. Re-import to fix older posts whose lists show as "- " text.
  • Posts without a thumbnail show a category image.

5. Admin: events, press, education

  • Events move to "Past events" automatically once their day has passed (site timezone SITE_TIMEZONE, New Zealand by default). Check "Past event" to move one regardless of date.
  • Press articles, courses and resources are managed from their Admin menus.

6. Registering Open Source

  • After logging in, go to Open Source → Register and fill in title, product introduction (KO/EN), development tool (e.g. Devin), Git URL (github.com), service URL and language.
  • A development tool adds a "Built with Devin" badge to the card; a service URL adds a "Live" marker and an "Open service" button.
  • On the server, `python seed_sources.py` registers the six Devin-built services at once. Re-running it overwrites entries with the same Git URL.

7. Admin: answering inquiries

  • Read and answer inquiries in Admin → Ask LUDA. The sender sees the answer through their private link.