1<!DOCTYPE html> 2<html lang="en"> 3<head> 4 <meta charset="UTF-8"> 5 <meta name="viewport" content="width=device-width, initial-scale=1"> 6 <title>Conference | AESON</title> 7 <meta name="description" content="Conference â Agricultural Extension Society of Nigeria (AESON)"> 8 <link rel="icon" href="/images/logo.png" type="image/png"> 9
9<script type="module" crossorigin src="/assets/main-BwpRrD0t.js"></script>
9 10 <link rel="stylesheet" crossorigin href="/assets/main-CgOcyfCk.css"> 11</head> 12<body class="" data-path="/conference/"> 13 <div id="site-header"></div> 14 <main id="main" class="site-main"> 15 <section class="page-hero"> 16 <div class="container"> 17 <h1>Conference</h1> 18 </div> 19 </section> 20 <section class="content-section"> 21 <div class="container prose"> 22 <p>AESON convenes a regular annual conference that brings together extension practitioners, researchers, academics, policymakers, development partners, and students from across Nigeria and beyond.</p> 23 24 <h2>Why attend</h2> 25 <ul> 26 <li>Engage with current debates in extension policy and practice</li> 27 <li>Present and discuss peer-reviewed research papers</li> 28 <li>Network with public, private, NGO, and academic stakeholders</li> 29 <li>Contribute to proceedings that document national extension discourse</li> 30 </ul> 31 32 <h2>Registration</h2> 33 <p>Conference registration and related fees can be completed through AESONâs payment channels.</p> 34 <p><a href="/payment/">Pay dues & register â</a></p> 35 36 <h2>After the conference</h2> 37 <p>Accepted papers are collated into the <a href="https://www.ajol.info/index.php/jae" target="_blank" rel="noopener noreferrer">conference proceedings</a>. Broader research continues to appear in the <a href="https://journal.aesonnigeria.org/" target="_blank" rel="noopener noreferrer">Journal of Agricultural Extension</a>.</p> 38 <p><a href="/past-conferences/">Browse past conferences â</a></p> 39 </div> 40 </section> 41 </main> 42 <div id="site-footer"></div> 43</body> 44</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.